adding reference on 140-2

66feb2d4 · Marcello Evangelista · 35fbf5f4 · 66feb2d4
Commit 66feb2d4 authored Jul 24, 2018 by Marcello Evangelista
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

security-policy/general-guidelines/acceptable-encryption-policy.md ...policy/general-guidelines/acceptable-encryption-policy.md +1 -1

No files found.
--- a/security-policy/general-guidelines/acceptable-encryption-policy.md
+++ b/security-policy/general-guidelines/acceptable-encryption-policy.md
@@ -10,7 +10,7 @@ This policy applies to all OlinData BV employees and affiliates.

 1. Algorithm Requirements

-   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, or any superseding documents according to the date of implementation. The use of the Advanced Encryption Standard (AES) is strongly recommended for symmetric encryption.
+   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.

   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.