acceptable-encryption-policy.md 3.17 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12
# Purpose

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.

# Scope

This policy applies to all OlinData BV employees and affiliates.

# Policy

1. Algorithm Requirements

13
   1. 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](https://csrc.nist.gov/publications/detail/fips/140/2/final), or any superseding documents according to the date of implementation. The use of the Advanced Encryption Standard (AES) is strongly recommended for symmetric encryption.
14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63

   1. 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.

   1. Signature Algorithms

| Algorithm        | Key (min)           | Additional Comment  |
| ------------- |:-------------:| -----:|
| ECDSA      | P-256 | Check the compliances involved before |
| RSA      | 2048      |   Must use the a secure padding |
| LDWM | SHA256      |    Check the internal standard of usage |

1. Hash Function Requirements

   In general, OlinData BV adheres to the NIST Policy on Hash Functions.

1. Key Agreement and Authentication

   1. Key exchanges must use one of the following cryptographic protocols: Diffie-Hellman, IKE, or Elliptic curve Diffie-Hellman (ECDH).

   1. End points must be authenticated prior to the exchange or derivation of session keys.

   1. 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.

   1. All servers used for authentication must have installed a valid certificate signed by a known trusted provider.

   1. All servers and applications using SSL or TLS must have the certificates signed by a known, trusted provider and completely avoid the usage of RC4-based certificates.

1. Key Generation

   1. Cryptographic keys must be generated and stored in a secure manner that prevents loss, theft, or compromise.

   1. 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.  

# Policy Compliance

1. Compliance Measurement

      The Infosec team will verify compliance to this policy through various methods, including but not limited to, periodic walk-thrus, video monitoring, business tool reports, internal and external audits, and feedback to the policy owner.

1. Exceptions

      Any exception to the policy must be approved by the Infosec team in advance.

1. Non-Compliance

      An employee found to have violated this policy may be subject to disciplinary action, up to and including termination of employment.

# Revision History

   Please check the commit history for this file.