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

Search Best Practices

1098 matching practices

Number	Best Practice
13-9-0415	Network Operators, Service Providers, and Public Safety should test the restoral process associated with critical data back-up, as appropriate.
13-9-0416	Network Operators, Service Providers, and Public Safety should design and implement procedures for traffic monitoring, trending and forecasting so that capacity management issues may be addressed.
13-9-0417	Network Operators, Service Providers, and Public Safety should design and implement procedures to evaluate failure and emergency conditions affecting network capacity.
13-9-0422	Network Operators, Service Providers, and Public Safety should collect failure-related data to perform cause analysis, impact and criticality analysis and failure trending.
13-9-0423	Equipment Suppliers should provide cable management features and installation instructions for network elements that maintain cable bend radius, provide strain relief to prevent cable damage, ensure adequate cable connector spacing for maintenance activities, and provide clear access for cable rearrangement (i.e. moves/add/deletes) and FRU (Field Replaceable Unit) swaps.
13-9-0425	Network Operators, Service Providers, and Public Safety should maintain software version deployment records, as appropriate.
13-9-0428	Service Providers, Network Operators, and Public Safety should monitor software and hardware vulnerability reports and take the recommended action(s) to address problems, where appropriate. Reports and recommendations are typically provided by equipment suppliers and Computer Emergency Response Teams (CERTs).
13-9-0442	Service Providers and Public Safety should consider measuring end-to-end path performance and path validity for both active and alternate routes.
13-9-0476	Network Operators, Property Managers, and Public Safety should consider conducting physical site audits after a major event (e.g., weather, earthquake, auto wreck) to ensure the physical integrity and orientation of hardware has not been compromised.
13-9-0504	Network Operators, Service Providers and Public Safety should consider maintaining "hot spares" (e.g., circuit packs electronically plugged in and interfacing with any element management system) as opposed to being stored in a cabinet for mission critical elements in order to facilitate asset management and increase the likelihood of having usable spares in emergency restorations.
13-9-0505	Network Operators, Service Providers, and Public Safety should have procedures in place to process court orders and subpoenas for wire taps or other information.
13-9-0510	Network Operators, Service Providers, Equipment Suppliers and Public Safety should by design and practice, manage critical Network Elements (e.g., Domain Name Servers, Signaling Servers, Gateway Servers) that are essential for network connectivity and subscriber service as critical systems (e.g., secure, redundant, alternative routing).
13-9-0513	Network Operators and Service Providers should maintain a 24x7x365 contact list of other providers and operators for service restoration of inter-connected networks and as appropriate share with Public Safety and Support providers.
13-9-0530	Network Operators, Service Providers, Equipment Suppliers, and Public Safety should participate in interoperability testing (including services), as appropriate, to maintain reliability across connected networks.
13-9-0532	Network Operators and Public Safety should periodically audit the physical and logical diversity called for by network design of their network segment(s) and take appropriate measures as needed.
13-9-0536	Network Operators and Service Providers should deploy security and reliability related software updates (e.g., patches, maintenance releases, dot releases) when available between major software releases. Prior to deployment, appropriate testing should be conducted to ensure that such software updates are ready for deployment in live networks. Equipment Suppliers should include such software updates in the next generic release and relevant previous generic releases.
13-9-0541	Network Operators, Service Providers, Equipment Suppliers, and Public Safety should store multiple software versions for critical network elements and be able to fallback to earlier versions.
13-9-0550	Network Operators, Equipment Suppliers, and Public Safety should implement procedures to ensure synchronization and security of databases.
13-9-0566	Network Operators, Service Providers, and Public Safety should consider placing and maintaining 9-1-1 TDM or IP based networks over diverse interoffice transport facilities (e.g., geographically diverse facility routes, automatically invoked standby routing, diverse digital cross-connect system services, self-healing fiber ring topologies, or any combination thereof).
13-9-0567	Network Operators, Service Providers, and Public Safety should spread 9-1-1 and Next Generation 9-1-1 access connections across similar equipment to avoid single points of failure and clearly mark plug-in level components and termination points as critical essential services that are to be treated with a high level of care.

Download matching Best Practices

Next results