+V12 Secure Communication
---+V12.1 General TLS Security Guidance
------+V12.1.1 Verify that only the latest recommended versions of the TLS protocol are enabled, such as TLS 1.2 …
------+V12.1.2 Verify that only recommended cipher suites are enabled, with the strongest cipher suites set as …
------+V12.1.3 Verify that the application validates that mTLS client certificates are trusted before using the …
------+V12.1.4 Verify that proper certification revocation, such as Online Certificate Status Protocol (OCSP) …
------+V12.1.5 Verify that Encrypted Client Hello (ECH) is enabled in the application's TLS settings to prevent …
---+V12.2 HTTPS Communication with External Facing Services
------+V12.2.1 Verify that TLS is used for all connectivity between a client and external facing, HTTP-based …
------+V12.2.2 Verify that external facing services use publicly trusted TLS certificates.
---+V12.3 General Service to Service Communication Security
------+V12.3.1 Verify that an encrypted protocol such as TLS is used for all inbound and outbound connections to …
------+V12.3.2 Verify that TLS clients validate certificates received before communicating with a TLS server.
------+V12.3.3 Verify that TLS or another appropriate transport encryption mechanism used for all connectivity …
------+V12.3.4 Verify that TLS connections between internal services use trusted certificates. Where internally …
------+V12.3.5 Verify that services communicating internally within a system (intra-service communications) use …

V12 Secure Communication

Control Objective

This chapter includes requirements related to the specific mechanisms that should be in place to protect data in transit, both between an end-user client and a backend service, as well as between internal and backend services.

The general concepts promoted by this chapter include:

  • Ensuring that communications are encrypted externally, and ideally internally as well.
  • Configuring encryption mechanisms using the latest guidance, including preferred algorithms and ciphers.
  • Ensuring that communications are not being intercepted by unauthorized parties through the use of signed certificates.

In addition to outlining general principles and best practices, the ASVS also provides more in-depth technical information about cryptographic strength in Appendix C - Cryptography Standards.

References

For more information, see also:

1. Pregled

Naslov Standard
V12.1 General TLS Security Guidance

This section provides initial guidance on how to secure TLS communications. Up-to-date tools should be used to review TLS configuration on an ongoing basis.

While the use of wildcard TLS certificates is not inherently insecure, a compromise of a certificate that is deployed across all owned environments (e.g., production, staging, development, and test) may lead to a compromise of the security posture of the applications using it. Proper protection, management, and the use of separate TLS certificates in different environments should be employed if possible.

V12.2 HTTPS Communication with External Facing Services

Ensure all HTTP traffic to external-facing services which the application exposes is sent encrypted, with publicly trusted certificates.

V12.3 General Service to Service Communication Security

Server communications (both internal and external) involve more than just HTTP. Connections to and from other systems must also be secure, ideally using TLS.

1.1 Sklici

1.2 Ugotovljene zahteve

1.3 Povezani predpisi

2. Ugotovljene zahteve

Zahteve
Vir Zahteva

3. Povezani predpisi

Predpisi
Vir Regulativa
  • 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.