Scope 17.8.2. This section covers information on the conditions under which IPSec can be used as an Approved Cryptographic Protocol. 17.8.3. When using a product that implements IPSec, requirements for using approved cryptographic protocols will also need to be referenced fromSection 17.3 Approved Cryptographic Protocols. Modes of operation 17.8.4. IPSec can be operated in two modes: transport mode or tunnel mode. Cryptographic algorithms 17.8.5. Most IPSec implementations can accommodate a number of cryptographic algorithms for encrypting data when the Encapsulating Security Payload (ESP) protocol is used. These include 3DES and AES. Key exchange 17.8.6. Most IPSec implementations facilitate a number of methods for sharing keying material used in hashing and encryption processes. Two common methods are manual keying and IKE using the ISAKMP. Both methods are considered suitable for use. ISAKMP authentication 17.8.7. Most IPSec implementations can select from a number of methods for authentication as part of ISAKMP. These can include digital certificates, encrypted nonces or pre-shared keys. All these methods are considered suitable for use. ISAKMP modes 17.8.8. ISAKMP uses two modes to exchange information as part of IKE. These are main mode and aggressive mode. References 17.8.9. Further information on IPSec can be found at: Reference RFC 2401 Title Security Architecture for the IP Publisher Source IETF https://datatracker.ietf.org/doc/html/ overview NIST 800-77 Rev. 1 Guide to IPSec VPNs, June 2020 rfc2401 NIST https://csrc.nist.gov/publications/det ail/sp/800-77/rev-1/final Rationale & Controls 17.8.10. Mode of operation 17.8.10.R.01. Rationale The tunnel mode of operation provides full encapsulation of IP packets whilst the transport mode of operation only encapsulates the payload of the IP packet. 17.8.10.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:2842] Agencies SHOULD use tunnel mode for IPSec connections. 17.8.10.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:2843] Agencies choosing to use transport mode SHOULD additionally use an IP tunnel for IPSec connections. 17.8.11. Protocol 17.8.11.R.01. Rationale In order to provide a secure VPN style connection both authentication and encryption are needed. ESP is the only way of providing encryption yet Authentication Header (AH) and ESP can provide authentication for the entire IP packet and the payload respectively. ESP is generally preferred for authentication though as AH has inherent network address translation limitations. 17.8.11.R.02. Rationale If however, maximum security is desired at the expense of network address translation functionality, then ESP can be wrapped inside of AH which will then authenticate the entire IP packet and not just the encrypted payload. 17.8.11.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:2847] Agencies SHOULD use the ESP protocol for IPSec connections. 17.8.12. ISAKMP modes 17.8.12.R.01. Rationale Using main mode instead of aggressive mode provides greater security since all exchanges are protected. 17.8.12.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:2850] Agencies using ISAKMP SHOULD disable aggressive mode for IKE. 17.8.13. Security association lifetimes 17.8.13.R.01. Rationale Using a secure association lifetime of four hours or 14400 seconds provides a balance between security and usability. 248 Version_3.5__January-2022

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents