+V11.2 Secure Cryptography Implementation
---+V11.2.1 Verify that industry-validated implementations (including libraries and hardware-accelerated …
---+V11.2.2 Verify that the application is designed with crypto agility such that random number, authenticated …
---+V11.2.3 Verify that all cryptographic primitives utilize a minimum of 128-bits of security based on the …
---+V11.2.4 Verify that all cryptographic operations are constant-time, with no 'short-circuit' operations in …
---+V11.2.5 Verify that all cryptographic modules fail securely, and errors are handled in a way that does not …

V11.2 Secure Cryptography Implementation

This section defines the requirements for the selection, implementation, and ongoing management of core cryptographic algorithms for an application. The objective is to ensure that only robust, industry-accepted cryptographic primitives are deployed, in alignment with current standards (e.g., NIST, ISO/IEC) and best practices. Organizations must ensure that each cryptographic component is selected based on peer-reviewed evidence and practical security testing.

1. Resumen

Título Estándar
V11.2.1 Verify that industry-validated implementations (including libraries and hardware-accelerated …

Verify that industry-validated implementations (including libraries and hardware-accelerated implementations) are used for cryptographic operations.

V11.2.2 Verify that the application is designed with crypto agility such that random number, authenticated …

Verify that the application is designed with crypto agility such that random number, authenticated encryption, MAC, or hashing algorithms, key lengths, rounds, ciphers and modes can be reconfigured, upgraded, or swapped at any time, to protect against cryptographic breaks. Similarly, it must also be possible to replace keys and passwords and re-encrypt data. This will allow for seamless upgrades to post-quantum cryptography (PQC), once high-assurance implementations of approved PQC schemes or standards are widely available.

V11.2.3 Verify that all cryptographic primitives utilize a minimum of 128-bits of security based on the …

Verify that all cryptographic primitives utilize a minimum of 128-bits of security based on the algorithm, key size, and configuration. For example, a 256-bit ECC key provides roughly 128 bits of security where RSA requires a 3072-bit key to achieve 128 bits of security.

V11.2.4 Verify that all cryptographic operations are constant-time, with no 'short-circuit' operations in …

Verify that all cryptographic operations are constant-time, with no 'short-circuit' operations in comparisons, calculations, or returns, to avoid leaking information.

V11.2.5 Verify that all cryptographic modules fail securely, and errors are handled in a way that does not …

Verify that all cryptographic modules fail securely, and errors are handled in a way that does not enable vulnerabilities, such as Padding Oracle attacks.

1.1 Referencias

1.2 Requisitos identificados

1.3 Regulaciones relacionadas

2. Requisitos identificados

Requisitos
Fuente Requisito

3. Regulaciones relacionadas

Regulaciones
Fuente Regulación
  • OWASP -

    EN: Publications of the OWASP Foundation, https://owasp.org/. OWASP® is a registered trademark of the OWASP Foundation, Inc.; GRCA is not affiliated with, nor endorsed by, the OWASP Foundation. Only the versions published by OWASP are authoritative.

    DE: Veröffentlichungen der OWASP Foundation, https://owasp.org/. OWASP® ist eine eingetragene Marke der OWASP Foundation, Inc.; GRCA steht in keiner Verbindung zur OWASP Foundation und wird von ihr nicht unterstützt. Maßgeblich sind allein die von OWASP veröffentlichten Fassungen.