310 likes | 422 Views
National Law Enforcement and Corrections Technology Center Northwest NLECTC-NW Anchorage, Alaska Program of the National Institute of Justice. 5 June 2006 LEIM NIJ Program Review Gaylord, TX. Related NIJ Project Activities. St. Paul Island Satellite Interconnect Test-Bed
E N D
National Law Enforcement and Corrections Technology Center NorthwestNLECTC-NWAnchorage, AlaskaProgram of the National Institute of Justice 5 June 2006 LEIM NIJ Program Review Gaylord, TX
Related NIJ Project Activities • St. Paul Island Satellite Interconnect Test-Bed • Alaska Law Enforcement Information Sharing System (ALEISS)
St. Paul Project Overview • Project Goals and Mechanisms • Why Satcom? • Involved Players • Testing Design • Project Milestones • Project Findings • Summary – What’s next?
Project Goals • Determine if P25 related satcom access is technically feasible, as well as affordable to the public safety community. • Identify & address issues regarding the extension of LMR systems via satellite to remote areas • The promotion of P25 standards language to accommodate the satellite transport of P25 related IP.
Project 25 and Satcom Transport? • Why satellite transport? • Lack of connectivity in rural, remote, areas of the United States. • Rural Alaska and other lower 48 states don’t have access and have limited resources. ‘Bush’ AK LMR connectivity is a perfect example. • Non-terrestrial back-up for emergency communications. • In areas with access, disaster responses may require satcom.
Project Participants • Support for the Test-bed Project: • Dept of Defense (DoD) – Financial support for radio infrastructure • Dept of Justice (DoJ) National Institute of Justice (NIJ) – Project grants awarded. • Communications organizations and agencies within the States of Alaska, California, New York, and New Mexico. • Other organizations who have expressed interest: • DHS: • FEMA • Secret Service • TSA • Customs and Border Patrol CBP • DOJ: • FBI • ATF • DOE • Dept of Interior (DOI) • National Park Service (NPS) • Bureau of Land Management (BLM) • Nuclear Regulatory Commission (NRC) • Dept of Agriculture (USDA) • Defense Information Systems Agency (DISA)
Testing Design Voice ‘throughput quality’ was measured by qualitative comparison of captured voice samples through repeated transmit-receive cycles using differing voices
Project Milestones • Anchorage-based RDT&E of P25 voice traffic via VoIP and RoIP interface devices, VPN firewalls, and satellite services. • Objectives met : • Determine feasibility of connecting remote site to the new Alaska LMR System (ALMR) • digital trunked radio systems can be interconnected through strong-encryption while incurring only a slight degradation in voice quality. • Issues identified regarding • Bandwidth requirements (QOS or Committed Data Rate requirements) • Security concerns • Reliability concerns • P25 User’s Needs Committee is prepared to promote future standards to accommodate satellite connectivity requirements • Final Technical reports are now in peer review / publication process (2/28/06)
Project Findings • Initial testing and evaluation of radio interface products completed • Shared digital satellite services that provide sufficient voice quality of service can/did support trunked radio gateways • Committed Information Rate or a QOS type satellite circuit required • Quality of service ‘5-9s’ reliability not yet verified • Encryption (256 bit AES evaluated) solutions exist and work • Provided secure transfer across a shared satellite network and internet • Verified voice quality w/ optimized VPN solutions • ‘End to End’ encryption solution not yet evaluated. • Minimum required bandwidth needed to support a radio channel, with/without encryption, was 64 kbps.
Summary • Satellite systems can support secure radio transmissions: • There are a few limitations – • Undetermined 5-9s Quality of Service • One manufacturer certifies their gateway product only for “administrative and ICS logistics” communications • Satcom and Internet transport can be encrypted • Identified vulnerabilities likely will not pass DoD requirements for secure communications (but are likely adequate for state and local) • Additional end-to-end devices should be evaluated (they reportedly exist) • Some of the SAT terminals supported simultaneous: • Half-Duplex VoIP LMR transmissions • Full-Duplex VoIP telephone transmissions • Email and internet access
What’s Next? • NLECTC-NW is continuing the Project, as funding allows. • St Paul Island site installed and being operationally evaluated • The public safety, encrypted, VoIP, satcom circuit between the St Paul Island and the Anchorage area (800 mi. ENE of St Paul) will be replaced with a more reliable system, then tested over an extended period • Limited T&E will take place on the Island. Local testing can suffice • Test and evaluate end-to-end AES encryption solutions, • Testing of additional Satcom options For more information, Please contact: Kyle Sinclair (kyle.sinclair@ctsc.net) Bob Griffiths (bob.griffiths@ctsc.net) (907) 569-2969 ● Toll Free (866) 569-2969
The Alaska Law Enforcement Information Sharing System ALEISS Maxine Andrews, Program Manger National Law Enforcement and Corrections Technology Center SystemNLECTC
Prior to computers police departments kept their records in file cabinets. • Collaborating investigators used the telephone • Now most departments have a computerized Records Management System (RMS) • Collaborating investigators still use the telephone because their RMS Systems do not “play well with others.”
Incompatible systems make automated data sharing impossible without a tool that would link these dissimilar systems together. • Many Different Records Management System Vendors equals incompatible systems • Chief’s have no experience with implementing data sharing systems and came to NLECTC-NW for technical assistance.
The Requirements were: • A solution selected should require no additional data entry. • Data already entered into an RMS should become available to investigators in other jurisdictions. • System must provide an analytical tool set • It must be scalable • It must allow for phased deployment • It must be able to be deployed securely on the internet
The ALEISS Consortium was created by MOU and a system selected • NLECTC-NW Currently: • Provides a secure location to house hardware • Provides cleared technical System Admin staff • Conducts routine user and system audits for security compliance • Provides training for users • Captures metrics on effect of system
What is ALEISS? -The Consortium ALEISS is a consortium of Alaska law enforcement agencies committed to working together to help fight and solve crime in Alaska. The ALEISS Consortium formed in 2003 (MOU signed August 2003). Phase One Alaska Department of Public Safety Anchorage Police Department Homer Police Department Kenai Police Department Juneau Police Department Seward Police Department Soldotna Police Department
Since the 8/03 MOU these agencies have joined consortium: • Wasilla Police Department • Fairbanks Police Department • North Pole Police Department • Skagway Police Department • Alaska Department of Correction • Valdez Police Department • Ketchikan Police Department • Palmer Police Department • Sitka Police Department • Kodiak Police Department • Alaska Railroad Police • Unalaska Police Department • Petersburg Police Department • Nome Department of Public Safety • US Marshal Service Alaska Fugitive Task Force
As of June 1 2006 • 22 Participating Agencies: 18 Municipal, 2 State, 1 Federal, 1 Transportation • 9 Data Sources, 7 Different RMS Vendors • 326 users
ALEISS was recognized with the 2005 IACP iXP Leadership in Technology Award for Excellence in Law Enforcement Communications and InteroperabilityRegional Division The IACP Leadership in Technology Award Program recognized law enforcement agencies' superior achievement and innovation in the field of communication and information technology. The program is an international competition that is open to local, tribal, state, provincial, federal, and multi-jurisdictional law enforcement agencies.
Connectivity & Security • Internet based application using Port 443 HTTPs • 256 bit SSL, soon to be AES, FIPS 140-2 compliant • Dual authentication implemented April 24, 2006 using Entrust Identity Guard Matrix card
This one query resulted in data from 5 different municipal police department RMS and represents 4 different RMS vendors.
Instant alert and collaboration tooldelivers email and/or text messages to alert of changes in data or similar queries by other users.
Incident Analyzer - GIS and Temporal Analysis (this module planned for 2006)
What’s Next for ALEISS? A Shared Regional “Open” RMS for agencies with no system (August ’06): • Based upon CAPSIT work funded by NIJ in Texas • 5 Alaskan agencies selected for project • Will be modeled after (and become part of) the ALEISS Consortium • Initially will provide basic RMS functions over secure internet connections • Will be enhanced as development continues on “Open” source-code to be LEITSC full featured RMS • CAD on the horizon
What Else is Next for ALEISS? ALEISS will add Incident Analyzer Module (July 2006)Long term operational plans:ALEISS operations will be assumed by the Alaska Association of Chiefs of Police
Questions or Comments? Thank You! Bob Griffiths NLECTC-NW 3000 C St. STE 304 Anchorage, AK 99503 866-569-2969