Search

By number By text StandardPublic Safety & Disaster

Categories (match all selected)Network Operators Service Providers Equipment Suppliers Property Managers Public Safety Government Cable Internet/Data Satellite Wireless Wireline Access Control Buildings Business Continuity Contractors & Vendors Corporate Ethics Cyber Security Disaster Recovery Documentation Emergency Preparedness Essential Services Facilities-Transport Fire Guard Services Hardware Human Resources Industry Cooperation Information Protection Liaison Materials Movement Network Design Network Elements Network Interoperability Network Operations Network Provisioning Pandemic Physical Security Management Policy Power Procedures Public Safety Service Security Systems Software Supervision Technical Support Training and Awareness Visitors Encryption Intrusion Detection

1098 matching practices

Number	Best Practice
13-12-3263	Network Operators, Service Providers and Public Safety should establish SIP Resource-Priority header value "esnet.1" to ensure that NG9-1-1 SIP packets are prioritized throughout the ESinet.
13-12-3264	Network Operators, Service Providers and Public Safety should ensure that policy-based routing controls for NG9-1-1 are implemented and managed to prevent adverse routing conditions.
13-12-3265	Network Operators, Service Providers and Public Safety should establish and enforce policies that ensure Next Gen 9-1-1 services are in compliance with established Next Gen 9-1-1 standards and where possible should utilize an independent validation and verification process to validate Next Gen 9-1-1 standards compliance.
13-12-3266	Public Safety should establish and document a process to plan, test, evaluate and implement major change activities in an NG9-1-1 environment. To include NG9-1-1 implementations and other changes, new IP infrastructure, and NGCS.
13-12-3267	Network Operators, Service Providers and Public Safety should support redundant local DNS servers/resolvers for any element connected to an NG9-1-1 Emergency Services IP Network to support the translation of hostnames to IP addresses. Authoritative DNS servers should be protected by Domain Name System (DNS) Security Extensions (DNSSEC).
13-12-3268	Network Operators, Service Providers, Equipment Suppliers and Public Safety should consider the use of the Department of Homeland Security (DHS) Protected Critical Infrastructure Information (PCII) program as a means of aggregating, sharing and protecting Vulnerability Assessment, Reporting & Remediation information related to private sector infrastructure.
13-12-3269	Network Operators, Service Providers and Public Safety should establish policies governing data, metadata, and other media that hold information that could be used to compromise the security in an NG9-1-1 system.
13-12-3270	Network Operators, Service Providers and Public Safety should establish and enforce policies for log in requirements, password protection, screenlock upon activity timeout, and other physical security measures to prevent visitors and outside contractors from accessing NG 9-1-1 systems.
13-12-3271	Network Operators, Service Providers and Public Safety should support HTTPS transport of dereference requests associated with the acquisition of location information and other additional data associated with an emergency call.
13-12-3272	Network Operators, Service Providers and Public Safety should provide integrity protection with TLS using SHA-256 or stronger for all protocol operations.
13-12-3273	Network Operators, Service Providers and Public Safety should establish and enforce policies that ensure cloud based Next Gen 9-1-1 services provide resilience, performance and security that meet established best practices for public safety and 9-1-1 and that leverage the scalable and enhanced information technology capacities of cloud based Next Gen 9-1-1 services.
13-12-3274	Network Operators, Service Providers should use strong certificate-based authentication ensuring network access, digital content and software services can be secured from unauthorized access. This applies to Public Safety only in an NG9-1-1 environment.
13-12-3275	Network Operators, Service Providers, Equipment Suppliers and Public Safety should support Border Control Functions (BCFs) that provide border firewall functionality including application and network layer protection and scanning, resource and admission control, and Denial of Service (DoS) detection and protection, as well as Session Border Control (SBC) functionality including: identification of emergency call/session and priority handling for the IP flows of emergency call/session traffic; conformance checking and mapping (if applicable) of priority marking based on policy for emergency calls/sessions; SIP protocol normalization; Network Address Translation (NAT) and Network Address and Port Translation (NAPT) Traversal; IPv4/IPv6 Interworking; Signaling Transport Protocol Support; and QoS/Priority Packet Marking.
13-12-3276	Network Operators, Service Providers and Public Safety should where feasible, provide both physical and logical diversity of critical facilities links.
13-12-3277	Network Operators, Service Providers and Public Safety should identify and manage critical network elements and architecture that are essential for network connectivity and subscriber services considering security, functional redundancy and geographical diversity.
13-12-3278	Network Operators, Service Providers, Property Managers and Public Safety should protect their building facilities against external breaches (e.g., vehicles inadvertently or purposefully ramming into the data center, NOC, operations center, etc.).
13-12-3279	Network Operators, Service Providers and Public Safety should use secure network protocols such as TLS for network interconnection for their SIP traffic. This applies to Public Safety only in an NG9-1-1 environment.
13-12-3280	Network Operators, Service Providers and Public Safety should implement policy routing rules for NG9-1-1 that allow 911 calls to be alternate routed to another PSAP due to an abnormal condition at the original PSAP, e.g., PSAP shutdown, abandonment, etc. The PSAP should be responsible for defining these conditions and have access to invoke them.
13-12-3281	Network Operators, Service Providers and Public Safety should if supporting transitional NG9-1-1 architectures and responsible for operating Legacy Network Gateways, Legacy PSAP Gateways, and/or Legacy Selective Router Gateways, ensure that these gateway elements log the beginning (i.e., start time) and end of processing (i.e., end time) of a call, as well as the actual SIP message processed by the gateway element via its IP interface and data related to its legacy interface (e.g., the port or trunk group over which the call was received/sent, the 10-digit pANI received or generated by the gateway system, the legacy protocol used [SS7 or MF]), in accordance with NENA requirements.
13-12-3282	Network Operators, Service Providers and Public Safety should support access to a logging service (also referred to as a “logger”) by all Next Generation Core Services (NGCS) elements and NG PSAPs that are served by an i3 NG9-1-1 Emergency Services IP Network (ESInet) via a standard interface. All significant steps in processing a call should logged, including external events, internal events, media, and messages. Access to at least two loggers must be supported for redundancy purposes, unless jurisdictional requirements differ.

Download matching Best Practices

Next results