+V14 Data Protection
---+V14.1 Data Protection Documentation
------+V14.1.1 Verify that all sensitive data created and processed by the application has been identified and …
------+V14.1.2 Verify that all sensitive data protection levels have a documented set of protection requirements. …
---+V14.2 General Data Protection
------+V14.2.1 Verify that sensitive data is only sent to the server in the HTTP message body or header fields …
------+V14.2.2 Verify that the application prevents sensitive data from being cached in server components, such as …
------+V14.2.3 Verify that defined sensitive data is not sent to untrusted parties (e.g., user trackers) to …
------+V14.2.4 Verify that controls around sensitive data related to encryption, integrity verification …
------+V14.2.5 Verify that caching mechanisms are configured to only cache responses which have the expected …
------+V14.2.6 Verify that the application only returns the minimum required sensitive data for the application's …
------+V14.2.7 Verify that sensitive information is subject to data retention classification, ensuring that …
------+V14.2.8 Verify that sensitive information is removed from the metadata of user-submitted files unless …
---+V14.3 Client-side Data Protection
------+V14.3.1 Verify that authenticated data is cleared from client storage, such as the browser DOM, after the …
------+V14.3.2 Verify that the application sets sufficient anti-caching HTTP response header fields (i.e. …
------+V14.3.3 Verify that data stored in browser storage (such as localStorage, sessionStorage, IndexedDB, or …

V14 Data Protection

Control Objective

Applications cannot account for all usage patterns and user behaviors, and should therefore implement controls to limit unauthorized access to sensitive data on client devices.

This chapter includes requirements related to defining what data needs to be protected, how it should be protected, and specific mechanisms to implement or pitfalls to avoid.

Another consideration for data protection is bulk extraction, modification, or excessive usage. Each system's requirements are likely to be very different, so determining what is "abnormal" must consider the threat model and business risk. From an ASVS perspective, detecting these issues is handled in the "Security Logging and Error Handling" chapter, and setting limits is handled in the "Validation and Business Logic" chapter.

References

For more information, see also:

1. Přehled

Název Standard
V14.1 Data Protection Documentation

A key prerequisite for being able to protect data is to categorize what data should be considered sensitive. There are likely to be several different levels of sensitivity, and for each level, the controls required to protect data at that level will be different.

There are various privacy regulations and laws that affect how applications must approach the storage, use, and transmission of sensitive personal information. This section no longer tries to duplicate these types of data protection or privacy legislation, but rather focuses on key technical considerations for protecting sensitive data. Please consult local laws and regulations, and consult a qualified privacy specialist or lawyer as required.

V14.2 General Data Protection

This section contains various practical requirements related to the protection of data. Most are specific to particular issues such as unintended data leakage, but there is also a general requirement to implement protection controls based on the protection level required for each data item.

V14.3 Client-side Data Protection

This section contains requirements preventing data from leaking in specific ways at the client or user agent side of an application.

1.1 Odkazy

1.2 Identifikované požadavky

1.3 Související regulace

2. Identifikované požadavky

Požadavky
Zdroj Požadavek

3. Související regulace

Regulace
Zdroj Regulace
  • 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.