Search
1098 matching practices
| Number | Best Practice |
|---|---|
| 13-8-8623 | Network Operators should where possible, have intrusion prevention software examine traffic coming through mobile devices. |
| 13-8-8624 | Network Operators should where possible, utilize anti-virus software for the mobile devices. |
| 13-8-8625 | Network Operators and Service Providers should ensure connections between Femtocell and Femto Gateway follow industry standardized IPSec protocol. Connection between Femtocell and Femto OAM system must be based on TLS/SSL protocol while management traffic flow is outside of the IPSec tunnel. Optionally, the management traffic may also be transported through Secure Gateway over IPSec once the IPSec tunnel between Femtocell and Secure Gateway is established. |
| 13-8-8626 | Service Providers should ensure that enterprise Femtocell Hardware authentication must be certificate based. |
| 13-8-8627 | Equipment Suppliers should ensure enterprise Femtocell hardware shall be tamper-proof. |
| 13-8-8628 | Service Providers should ensure all Base Transceiver Station (BTS) security relevant events, e.g. apparent security violations, completion status of operations, invalid or unsuccessful logon attempts, userid, logon time, etc are to be recorded. |
| 13-8-8630 | Network Operators and Service Providers should ensure Femtocell access control is flexible to be based on: individual Femtocell; or group of Femtocells; and/or entire Enterprise Femto System. The access control list administration, where feasible should be web GUI based, and userid / password authenticated. |
| 13-8-8631 | Service Providers and Equipment Suppliers should establish application support for cryptography that are based on open and widely reviewed and implemented encryption algorithms and protocols. Examples of acceptable algorithms and protocols include AES, Blowfish, RSA, RC5, IDEA, SSH2, SSLv3, TLSv1, and IPSEC. Products should not rely on proprietary or obscure cryptographic measures for security. |
| 13-8-8632 | Equipment Suppliers should use algorithms with strengths similar to 2,048-bit RSA or Diffie-Hillman algorithms with a prime group of 2,048 in order to secure all key exchange. applications bits be used. Anonymous Diffie-Hillman must not be supported. |
| 13-8-8634 | Network Operators and Service Providers should implement for all symmetric secure data integrity applications, algorithms with strengths similar to HMAC-MD5-96 with 128-bit keys, HMAC-SHA-1-96 with 160-bit keys, or AES-based randomized message authentication code (RMAC) being the standard used. |
| 13-8-8635 | Network Operators and Service Providers should implement Authenticated Key Agreement (AKA) protocol to provide user and network with a session specific random shared-key that can be used for confidential communication. |
| 13-8-8636 | Network Operators and Service Providers should take steps to protect user data from eavesdropping and/or being tampered in transit; ensure user has the correct credentials; accuracy and efficiency of accounting. |
| 13-8-8637 | Network Operators and Service Providers should take steps to ensure all traffic on a 4G network is encrypted using Counter Mode with Cipher Block Chaining Message Authentication Code Protocol (CCMP) which uses AES for transmission security and data integrity authentication. |
| 13-8-8638 | Network Operators and Service Providers should enable the Mobile MiMAX system to provide secure communications by encrypting data traffic and use PKM (Privacy Key Management) Protocol that allows for the Base Station to authenticate the MS/CPE and not vice versa. |
| 13-8-8639 | Network Operators and Service Providers should use strong certificate-based authentication ensuring network access, digital content and software services can be secured from unauthorized access. |
| 13-8-8640 | Network Operators, Service Providers, and Equipment Suppliers should use NSA approved encryption and authentication for all Satcom command uplinks; downlink data encrypted as applicable depending on sensitivity/classification. |
| 13-8-8641 | Network Operators and Service Providers should implement mitigation strategies against physical threat vectors that affect the satellite, the availability of communications, the integrity and confidentiality of satellite, and the performance of communications. |
| 13-8-8643 | Network Operators should sanitize employee mobile devices when removed from service. Mobile devices and other electronic equipment that contain or access sensitive information, or have been used to access sensitive information in the past, should be processed to ensure all data is permanently removed in a manner that prevents recovery before they are disposed of as surplus equipment or returned to the vendor. |
| 13-8-8644 | Network Operators should require Data Encryption for all employee mobile devices that contain sensitive data. If sensitive information must reside on a mobile device, it should be encrypted. The decryption key should be entered manually; this step should not be automated. A means should exist to recover encrypted data when the decryption key is lost. Require the use of laptop encryption and password-protection. |
| 13-8-8645 | Network Operators should set policy that requires any sensitive information transmitted to or from the employee mobile device be encrypted and/or transferred with a secure data transfer utility. Use of a secure connection or protocol, such as SSL, that guarantees end-to-end encryption of all data sent or received should be included in policy. Devices with wireless capability pose an additional risk of unauthorized access and tampering. These capabilities should be disabled, secured, or protected with a firewall. |
Download matching Best Practices
Next results