Encryption Policy Template

Home / Services / Virtual CISO / Policies / Encryption Policy Template

Encryption Policy
The purpose of this policy is to provide guidance that limits the use of encryption to those algorithms that have received substantial public review and have been proven to work effectively. Additionally, this policy provides direction to ensure that UK and EU regulations are followed, and legal authority is granted for the dissemination and use of encryption technologies. This policy is part of the ISMS, aligned with ISO27001:2022.
This policy applies to all members, contractors and interns of the {{company_name}}.
Algorithm Requirements – at Rest
Ciphers in use must meet or exceed the set defined as "AES-compatible" or "partially AES-compatible" according to the IETF/IRTF Cipher Catalog, or the set defined for use in the United States National Institute of Standards and Technology(NIST) publication FIPS 140-2, or any superseding documents according to the date of implementation. The use of the Advanced Encryption Standard (AES) is strongly recommended for symmetric encryption. Algorithms in use must meet the standards defined for use in NIST publication FIPS 140-2 or any superseding document, according to date of implementation. The use of the RSA and Elliptic Curve Cryptography (ECC) algorithms is strongly recommended for asymmetric encryption.
Algorithm Requirements – in Transit
For all information in transit, we mandate TLSv1.3. Where external parties can not accept this, we will regress to TLSv1.2. If the external party is unable to accept TLSv1.2, then we will NOT exchange information..
Hash Function Requirements
In general, we adhere to the NIST Policy on Hash Functions.
Key Agreement and Authentication
Key exchanges must use one of the following cryptographic protocols: Diffie-Hellman, IKE, or Elliptic curve Diffie-Hellman (ECDH). 

End points must be authenticated prior to the exchange or derivation of session keys. Public keys used to establish trust must be authenticated prior to use. Examples of authentication include transmission via cryptographically signed message or manual verification of the public key hash.  

All servers used for authentication (for example, RADIUS or TACACS) must have installed a valid certificate signed by a known trusted provider.  

All servers and applications using SSL or TLS must have the certificates signed by a known, trusted provider and must only use TLSv1.2 or higher. 
Key Generation
Cryptographic keys must be generated and stored in a secure manner that prevents loss, theft, or compromise.

Key generation must be seeded from an industry standard random number generator (RNG). For examples, see NIST Annex C: Approved Random Number Generators for FIPS PUB 140-2
Compliance Measurement
The {{company_name}} Team will verify compliance to this policy through various methods, including but not limited to, business tool reports, internal and external audits, and feedback to the policy owner.
Any exceptions to the policy must be approved by the CEO in advance.
Any employee found to have violated this policy may be subject to disciplinary action, up to and including termination of employment.
  • NIST FIPS 140-2
  • NIST Policy on Hash Functions