Search
1098 matching practices
| Number | Best Practice |
|---|---|
| 13-8-8646 | Service Providers should devise a means of enforcing security over tethered connections. When tethering via a mobile device for data communication, an encryption methodology, such as IPSEC or SSL/VPN should be utilized to ensure session security. |
| 13-8-8649 | Service Providers should classify their cloud service against one of the defined industry cloud service architecture models (e.g., software as a service [SaaS], platform as a service [PaaS] or infrastructure as a service [IaaS]) and the deployment model being utilized (e.g., private cloud, community cloud, public cloud or hybrid cloud) to determine the general “security” posture of the specific cloud service, how it relates to asset’s assurance and security protection requirements, and define the needed security architecture to mitigate security risks. |
| 13-8-8650 | Service Providers should periodically conduct risk assessments (for their cloud) of their information security governance structure and processes, security controls, information security management processes, and operational processes. |
| 13-8-8651 | Service Providers should have a documented Business Continuity and Disaster Recovery Plan. |
| 13-8-8654 | Network Operators and Service Providers should use explicit static configuration of addresses, routing protocols and parameters at peering point interfaces rather than neighbor discovery or defaults. |
| 13-8-8655 | Network Operators and Service Providers should employ protocol-specific mechanisms or IPSec as applicable. |
| 13-8-8656 | Network Operators and Service Providers should use static neighbor entries rather than neighbor discovery for critical systems. |
| 13-8-8657 | Network Operators and Service Providers should use BGP ingress and egress prefix filtering, TCP MD5 or SHA-1 authentication. |
| 13-8-8658 | Network Operators and Service Providers should use IPv6 BOGON lists to filter un-assigned address blocks at Network boundaries. |
| 13-8-8659 | Network Operators and Service Providers should apply IPv6 and IPv4 anti-spoofing and firewall rules as applicable, wherever tunnel endpoints decapsulate packets. |
| 13-8-8660 | Network Operators and Service Providers should have access control lists for IPv6 that are comparable to those for IPv4, and that also block new IPv6 multicast addresses that ought not to cross the administrative boundary. |
| 13-8-8661 | Network Operators and Service Providers should block tunneling protocols (for example, IP protocol 41 and UDP port 3544) at points where they should not be used. Tunnels can bypass firewall/perimeter security. Use static tunnels where the need for tunneling is known in advance. |
| 13-8-8662 | Network Operators and Service Providers should filter internal-use IPv6 addresses at provider edge and network perimeter. |
| 13-8-8663 | Network Operators and Service Providers should use dedicated VoIP servers for the VOIP service, if possible. |
| 13-8-8664 | Network Operators and Service Providers should block protocols meant for internal VoIP call control use at the VoIP perimeter. |
| 13-8-8665 | Network Operators and Service Providers should proxy remote HTTP access to the VoIP perimeter firewalls. |
| 13-8-8666 | Network Operators and Service Providers should block VoIP firewall administrative/management traffic at the perimeter or Tunnel/encrypt this traffic using VPN technology or administer/manage this traffic out of band. |
| 13-8-8667 | Network Operators and Service Providers should route HTTP access from the VoIP environment through the data environment and use HTTPS if at all possible. |
| 13-8-8668 | Network Operators and Service Providers should establish a business continuity process for information, identify the events that can classified as business interruption, test and update the business continuity plan. |
| 13-8-8669 | Network Operators and Service Providers should ensure that access to shared networks, including those that cross organizational boundaries, as well as internal network and customer management infrastructures, is restricted, as per the Company's access control policy. These restrictions apply to systems, applications, and users, and is enforced via a router, firewall, or similar device allowing for rule-based traffic filtering, thereby ensuring a logical separation of networks. |
Download matching Best Practices
Next results