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-8-8724	Network Operators should consider implementing dial-back modems with screening lists, communication encryptions (i.e. VPN's) and token-based access control if they are utilizing dial-up connections for maintenance access to Network Elements.
13-8-8726	Network Operators should design their signaling network elements and interfaces consistent with applicable industry security guidelines and policies (e.g. ATIS-300011).
13-8-8730	Network Operators should log changes made to network elements and consider recording the user login, time of day, IP address, associated authentication token, and other pertinent information associated with each change. Policies should be established to audit logs on a periodic bases and update procedures as needed.
13-8-8731	Network Operators should establish policies and procedures to ensure that actions taken on the network can be positively attributed to the person or entity that initiated the action. This may include, but is not limited to electronic logging, access control, physical records, or tickets.
13-8-8733	Service Providers should clearly define and enforce rules, policies and trust model for the federated identity services.
13-8-8735	Service Providers should take reasonable steps to assure that the data, if creating, maintaining, using or disseminating individually identifiable information, is accurate, complete and timely for the purposes for which they are to be used. Organizations should establish appropriate processes or mechanisms so that inaccuracies in material individually identifiable information, such as account or contact information, may be corrected. These processes and mechanisms should be simple and easy to use and provide assurance that inaccuracies have been corrected. Other procedures to assure data quality may include use of reliable sources and collection methods, reasonable and appropriate access and correction, and protections against accidental or unauthorized alteration.
13-8-8738	Network Operators and Service Providers should define, implement, and maintain password management policies as well as the documented process to reduce the risk of compromise of password-based systems.
13-8-8739	Service Providers should act swiftly when a password management system or other source of passwords has been compromised, to mitigate the weaknesses that allowed the compromise, restore the compromised system to a secure state, and require all users to change their passwords immediately. Procedures should be in place to notify all affected users that their passwords have been reset or need to be changed immediately.
13-8-8740	Network Operators and Service Providers should encrypt sensitive data from web servers, and other externally accessible applications, while it is in transit over any networks they do not physically control.
13-8-8741	Equipment Suppliers should implement techniques such as tamper-proof crypto-chips/authentication credentials and (remote) authentication for (service provider) configuration controls, in customer premises equipment. Additionally, capabilities to remotely access or delete sensitive information on these devices is encouraged.
13-8-8743	Service Providers should segregate key management from the cloud provider hosting the data, creating a chain of separation. This protects both the cloud provider and customer from conflicts when compelled to provide data due to a legal mandate.
13-8-8744	Service Providers should provide documentation and enforce role management and separation of duties.
13-8-8745	Service Providers should define processes for key management lifecycle in cases where the cloud provider must perform key management: how keys are generated, used, stored, backed up, recovered, rotated, and deleted. Further, understand whether the same key is used for every customer or if each customer has its own key set.
13-8-8746	Service Providers should use an alternate approach such as a "web of trust" for public key validation / authentication for environments where traditional PKI infrastructures are problematic.
13-8-8747	Service Providers should use layered VPN and encryption strategies to mitigate device vulnerabilities. Traditionally a single layer of cryptography has stood between the data being protected and that of the attacker. While the cryptography itself is rarely the weak link, many times implementation or other originating or terminating cryptographic device vulnerabilities places that information in jeopardy.
13-8-8750	Network Operators and Service Providers should have assigned risk ratings for vulnerabilities and definitions of those risk ratings (i.e. What does a High risk vulnerability mean to the general user public?, etc.) Finally, the security team should have access to an accurate and readily available asset inventory (See Step 1: Asset Inventory) (including the asset owners, and patch levels) and network diagrams.
13-8-8751	Network Operators and Service Providers should test new tools in a lab to identify any false positives and false negatives and use a change control system in case there is a network disruption. They should use a tool that causes minimal disruptions to the network.
13-8-8752	Network Operators, Service Providers, and Equipment Suppliers should use custom policies created by OS, device, or by industry standard (SANS Top 20, Windows Top 10 Vulnerabilities, OWASP Top 10) and specific to your environment. Organizations should identify what scanning methods and operating procedures are best for their company, and document how they would proceed in a standard operating procedure.
13-8-8753	Network Operators and Service Providers should ensure the tools they use are capable of notifying the asset owners that they have vulnerabilities to be fixed. They should be able to provide high-level dashboard type reports to senior management and detailed host reports to system administrators.
13-8-8754	Network Operators, Service Providers, and Equipment Suppliers should focus on the highest risk vulnerabilities by ranking them by the vulnerability risk rating.

Download matching Best Practices

Next results