Owasp Asvs

# Section Name Item Description L1 L2 L3 Cwe Nist To Use Comment Source
1 V9 Communications 9.2.5 Verify that backend TLS connection failures are logged. X https://cwe.mitre.org/data/definitions/544.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
2 V9 Communications 9.2.4 Verify that proper certification revocation, such as Online Certificate Status Protocol (OCSP) Stapling, is enabled and configured. X X https://cwe.mitre.org/data/definitions/299.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
3 V9 Communications 9.2.3 Verify that all encrypted connections to external systems that involve sensitive information or functions are authenticated. X X https://cwe.mitre.org/data/definitions/287.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
4 V9 Communications 9.2.2 Verify that encrypted communications such as TLS is used for all inbound and outbound connections, including for management ports, monitoring, authentication, API, or web service calls, database, cloud, serverless, mainframe, external, and partner connections. The server must not fall back to insecure or unencrypted protocols. X X https://cwe.mitre.org/data/definitions/319.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
5 V9 Communications 9.2.1 Verify that connections to and from the server use trusted TLS certificates. Where internally generated or self-signed certificates are used, the server must be configured to only trust specific internal CAs and specific self-signed certificates. All others should be rejected. X X https://cwe.mitre.org/data/definitions/295.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
6 V9 Communications 9.1.3 Verify that old versions of SSL and TLS protocols, algorithms, ciphers, and configuration are disabled, such as SSLv2, SSLv3, or TLS 1.0 and TLS 1.1. The latest version of TLS should be the preferred cipher suite. X X X https://cwe.mitre.org/data/definitions/326.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
7 V9 Communications 9.1.2 Verify using online or up to date TLS testing tools that only strong algorithms, ciphers, and protocols are enabled, with the strongest algorithms and ciphers set as preferred. X X X https://cwe.mitre.org/data/definitions/326.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
8 V9 Communications 9.1.1 Verify that secured TLS is used for all client connectivity, and does not fall back to insecure or unencrypted protocols. ([C8](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/319.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
9 V8 Data 8.3.8 Verify that sensitive personal information is subject to data retention classification, such that old or out of date data is deleted automatically, on a schedule, or as the situation requires. X X https://cwe.mitre.org/data/definitions/285.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
10 V8 Data 8.3.7 Verify that sensitive or private information that is required to be encrypted, is encrypted using approved algorithms that provide both confidentiality and integrity. ([C8](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/327.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
11 V8 Data 8.3.6 Verify that sensitive information contained in memory is overwritten as soon as it is no longer required to mitigate memory dumping attacks, using zeroes or random data. X X https://cwe.mitre.org/data/definitions/226.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
12 V8 Data 8.3.5 Verify accessing sensitive data is audited (without logging the sensitive data itself), if the data is collected under relevant data protection directives or where logging of access is required. X X https://cwe.mitre.org/data/definitions/532.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
13 V8 Data 8.3.4 Verify that all sensitive data created and processed by the application has been identified, and ensure that a policy is in place on how to deal with sensitive data. ([C8](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/200.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
14 V8 Data 8.3.3 Verify that users are provided clear language regarding collection and use of supplied personal information and that users have provided opt-in consent for the use of that data before it is used in any way. X X X https://cwe.mitre.org/data/definitions/285.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
15 V8 Data 8.3.2 Verify that users have a method to remove or export their data on demand. X X X https://cwe.mitre.org/data/definitions/212.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
16 V8 Data 8.3.1 Verify that sensitive data is sent to the server in the HTTP message body or headers, and that query string parameters from any HTTP verb do not contain sensitive data. X X X https://cwe.mitre.org/data/definitions/319.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
17 V8 Data 8.2.3 Verify that authenticated data is cleared from client storage, such as the browser DOM, after the client or session is terminated. X X X https://cwe.mitre.org/data/definitions/922.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
18 V8 Data 8.2.2 Verify that data stored in client side storage (such as HTML5 local storage, session storage, IndexedDB, regular cookies or Flash cookies) does not contain sensitive data or PII. X X X https://cwe.mitre.org/data/definitions/922.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
19 V8 Data 8.2.1 Verify the application sets sufficient anti-caching headers so that sensitive data is not cached in modern browsers. X X X https://cwe.mitre.org/data/definitions/525.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
20 V8 Data 8.1.6 Verify that backups are stored securely to prevent data from being stolen or corrupted. X https://cwe.mitre.org/data/definitions/19.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
21 V8 Data 8.1.5 Verify that regular backups of important data are performed and that test restoration of data is performed. X https://cwe.mitre.org/data/definitions/19.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
22 V8 Data 8.1.4 Verify the application can detect and alert on abnormal numbers of requests, such as by IP, user, total per hour or day, or whatever makes sense for the application. X X https://cwe.mitre.org/data/definitions/770.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
23 V8 Data 8.1.3 Verify the application minimizes the number of parameters in a request, such as hidden fields, Ajax variables, cookies and header values. X X https://cwe.mitre.org/data/definitions/233.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
24 V8 Data 8.1.2 Verify that all cached or temporary copies of sensitive data stored on the server are protected from unauthorized access or purged/invalidated after the authorized user accesses the sensitive data. X X https://cwe.mitre.org/data/definitions/524.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
25 V8 Data 8.1.1 Verify the application protects sensitive data from being cached in server components such as load balancers and application caches. X X https://cwe.mitre.org/data/definitions/524.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
26 V7 Error 7.4.3 Verify that a "last resort" error handler is defined which will catch all unhandled exceptions. ([C10](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/460.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
27 V7 Error 7.4.2 Verify that exception handling (or a functional equivalent) is used across the codebase to account for expected and unexpected error conditions. ([C10](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/544.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
28 V7 Error 7.4.1 Verify that a generic message is shown when an unexpected or security sensitive error occurs, potentially with a unique ID which support personnel can use to investigate. ([C10](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/210.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
29 V7 Error 7.3.4 Verify that time sources are synchronized to the correct time and time zone. Strongly consider logging only in UTC if systems are global to assist with post-incident forensic analysis. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X OWASP Application Security Verification Standard 4.0-en.csv (github) View
30 V7 Error 7.3.3 Verify that security logs are protected from unauthorized access and modification. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/200.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
31 V7 Error 7.3.2 Verify that all events are protected from injection when viewed in log viewing software. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/117.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
32 V7 Error 7.3.1 Verify that the application appropriately encodes user-supplied data to prevent log injection. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/117.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
33 V7 Error 7.2.2 Verify that all access control decisions can be logged and all failed decisions are logged. This should include requests with relevant metadata needed for security investigations. X X https://cwe.mitre.org/data/definitions/285.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
34 V7 Error 7.2.1 Verify that all authentication decisions are logged, without storing sensitive session identifiers or passwords. This should include requests with relevant metadata needed for security investigations. X X https://cwe.mitre.org/data/definitions/778.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
35 V7 Error 7.1.4 Verify that each log event includes necessary information that would allow for a detailed investigation of the timeline when an event happens. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/778.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
36 V7 Error 7.1.3 Verify that the application logs security relevant events including successful and failed authentication events, access control failures, deserialization failures and input validation failures. ([C5, C7](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/778.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
37 V7 Error 7.1.2 Verify that the application does not log other sensitive data as defined under local privacy laws or relevant security policy. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/532.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
38 V7 Error 7.1.1 Verify that the application does not log credentials or payment details. Session tokens should only be stored in logs in an irreversible, hashed form. ([C9, C10](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/532.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
39 V6 Cryptography 6.4.2 Verify that key material is not exposed to the application but instead uses an isolated security module like a vault for cryptographic operations. ([C8](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/320.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
40 V6 Cryptography 6.4.1 Verify that a secrets management solution such as a key vault is used to securely create, store, control access to and destroy secrets. ([C8](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/798.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
41 V6 Cryptography 6.3.3 Verify that random numbers are created with proper entropy even when the application is under heavy load, or that the application degrades gracefully in such circumstances. X https://cwe.mitre.org/data/definitions/338.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
42 V6 Cryptography 6.3.2 Verify that random GUIDs are created using the GUID v4 algorithm, and a cryptographically-secure pseudo-random number generator (CSPRNG). GUIDs created using other pseudo-random number generators may be predictable. X X https://cwe.mitre.org/data/definitions/338.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
43 V6 Cryptography 6.3.1 Verify that all random numbers, random file names, random GUIDs, and random strings are generated using the cryptographic module's approved cryptographically secure random number generator when these random values are intended to be not guessable by an attacker. X X https://cwe.mitre.org/data/definitions/338.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
44 V6 Cryptography 6.2.8 Verify that all cryptographic operations are constant-time, with no 'short-circuit' operations in comparisons, calculations, or returns, to avoid leaking information. X https://cwe.mitre.org/data/definitions/385.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
45 V6 Cryptography 6.2.7 Verify that encrypted data is authenticated via signatures, authenticated cipher modes, or HMAC to ensure that ciphertext is not altered by an unauthorized party. X https://cwe.mitre.org/data/definitions/326.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
46 V6 Cryptography 6.2.6 Verify that nonces, initialization vectors, and other single use numbers must not be used more than once with a given encryption key. The method of generation must be appropriate for the algorithm being used. X X https://cwe.mitre.org/data/definitions/326.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
47 V6 Cryptography 6.2.5 Verify that known insecure block modes (i.e. ECB, etc.), padding modes (i.e. PKCS#1 v1.5, etc.), ciphers with small block sizes (i.e. Triple-DES, Blowfish, etc.), and weak hashing algorithms (i.e. MD5, SHA1, etc.) are not used unless required for backwards compatibility. X X https://cwe.mitre.org/data/definitions/326.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
48 V6 Cryptography 6.2.4 Verify that random number, encryption or hashing algorithms, key lengths, rounds, ciphers or modes, can be reconfigured, upgraded, or swapped at any time, to protect against cryptographic breaks. ([C8](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/326.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
49 V6 Cryptography 6.2.3 Verify that encryption initialization vector, cipher configuration, and block modes are configured securely using the latest advice. X X https://cwe.mitre.org/data/definitions/326.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
50 V6 Cryptography 6.2.2 Verify that industry proven or government approved cryptographic algorithms, modes, and libraries are used, instead of custom coded cryptography. ([C8](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/327.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
51 V6 Cryptography 6.2.1 Verify that all cryptographic modules fail securely, and errors are handled in a way that does not enable Padding Oracle attacks. X X X https://cwe.mitre.org/data/definitions/310.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
52 V6 Cryptography 6.1.3 Verify that regulated financial data is stored encrypted while at rest, such as financial accounts, defaults or credit history, tax records, pay history, beneficiaries, or de-anonymized market or research records. X X https://cwe.mitre.org/data/definitions/311.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
53 V6 Cryptography 6.1.2 Verify that regulated health data is stored encrypted while at rest, such as medical records, medical device details, or de-anonymized research records. X X https://cwe.mitre.org/data/definitions/311.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
54 V6 Cryptography 6.1.1 Verify that regulated private data is stored encrypted while at rest, such as personally identifiable information (PII), sensitive personal information, or data assessed likely to be subject to EU's GDPR. X X https://cwe.mitre.org/data/definitions/311.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
55 V5 Validation 5.5.4 Verify that when parsing JSON in browsers or JavaScript-based backends, JSON.parse is used to parse the JSON document. Do not use eval() to parse JSON. X X X https://cwe.mitre.org/data/definitions/95.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
56 V5 Validation 5.5.3 Verify that deserialization of untrusted data is avoided or is protected in both custom code and third-party libraries (such as JSON, XML and YAML parsers). X X X https://cwe.mitre.org/data/definitions/502.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
57 V5 Validation 5.5.2 Verify that the application correctly restricts XML parsers to only use the most restrictive configuration possible and to ensure that unsafe features such as resolving external entities are disabled to prevent XXE. X X X https://cwe.mitre.org/data/definitions/611.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
58 V5 Validation 5.5.1 Verify that serialized objects use integrity checks or are encrypted to prevent hostile object creation or data tampering. ([C5](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/502.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
59 V5 Validation 5.4.3 Verify that sign, range, and input validation techniques are used to prevent integer overflows. X X https://cwe.mitre.org/data/definitions/190.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
60 V5 Validation 5.4.2 Verify that format strings do not take potentially hostile input, and are constant. X X https://cwe.mitre.org/data/definitions/134.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
61 V5 Validation 5.4.1 Verify that the application uses memory-safe string, safer memory copy and pointer arithmetic to detect or prevent stack, buffer, or heap overflows. X X https://cwe.mitre.org/data/definitions/120.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
62 V5 Validation 5.3.9 Verify that the application protects against Local File Inclusion (LFI) or Remote File Inclusion (RFI) attacks. X X X https://cwe.mitre.org/data/definitions/829.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
63 V5 Validation 5.3.8 Verify that the application protects against OS command injection and that operating system calls use parameterized OS queries or use contextual command line output encoding. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/78.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
64 V5 Validation 5.3.7 Verify that the application protects against LDAP Injection vulnerabilities, or that specific security controls to prevent LDAP Injection have been implemented. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/943.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
65 V5 Validation 5.3.6 Verify that the application projects against JavaScript or JSON injection attacks, including for eval attacks, remote JavaScript includes, CSP bypasses, DOM XSS, and JavaScript expression evaluation. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/830.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
66 V5 Validation 5.3.5 Verify that where parameterized or safer mechanisms are not present, context-specific output encoding is used to protect against injection attacks, such as the use of SQL escaping to protect against SQL injection. ([C3, C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/89.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
67 V5 Validation 5.3.4 Verify that data selection or database queries (e.g. SQL, HQL, ORM, NoSQL) use parameterized queries, ORMs, entity frameworks, or are otherwise protected from database injection attacks. ([C3](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/89.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
68 V5 Validation 5.3.3 Verify that context-aware, preferably automated - or at worst, manual - output escaping protects against reflected, stored, and DOM based XSS. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/79.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
69 V5 Validation 5.3.2 Verify that output encoding preserves the user's chosen character set and locale, such that any Unicode character point is valid and safely handled. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/176.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
70 V5 Validation 5.3.10 Verify that the application protects against XPath injection or XML injection attacks. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/643.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
71 V5 Validation 5.3.1 Verify that output encoding is relevant for the interpreter and context required. For example, use encoders specifically for HTML values, HTML attributes, JavaScript, URL Parameters, HTTP headers, SMTP, and others as the context requires, especially from untrusted inputs (e.g. names with Unicode or apostrophes, such as ねこ or O'Hara). ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/116.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
72 V5 Validation 5.2.8 Verify that the application sanitizes, disables, or sandboxes user-supplied scriptable or expression template language content, such as Markdown, CSS or XSL stylesheets, BBCode, or similar. X X X https://cwe.mitre.org/data/definitions/94.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
73 V5 Validation 5.2.7 Verify that the application sanitizes, disables, or sandboxes user-supplied SVG scriptable content, especially as they relate to XSS resulting from inline scripts, and foreignObject. X X X https://cwe.mitre.org/data/definitions/159.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
74 V5 Validation 5.2.6 Verify that the application protects against SSRF attacks, by validating or sanitizing untrusted data or HTTP file metadata, such as filenames and URL input fields, use whitelisting of protocols, domains, paths and ports. X X X https://cwe.mitre.org/data/definitions/918.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
75 V5 Validation 5.2.5 Verify that the application protects against template injection attacks by ensuring that any user input being included is sanitized or sandboxed. X X X https://cwe.mitre.org/data/definitions/94.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
76 V5 Validation 5.2.4 Verify that the application avoids the use of eval() or other dynamic code execution features. Where there is no alternative, any user input being included must be sanitized or sandboxed before being executed. X X X https://cwe.mitre.org/data/definitions/95.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
77 V5 Validation 5.2.3 Verify that the application sanitizes user input before passing to mail systems to protect against SMTP or IMAP injection. X X X https://cwe.mitre.org/data/definitions/147.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
78 V5 Validation 5.2.2 Verify that unstructured data is sanitized to enforce safety measures such as allowed characters and length. X X X https://cwe.mitre.org/data/definitions/138.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
79 V5 Validation 5.2.1 Verify that all untrusted HTML input from WYSIWYG editors or similar is properly sanitized with an HTML sanitizer library or framework feature. ([C5](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/116.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
80 V5 Validation 5.1.5 Verify that URL redirects and forwards only allow whitelisted destinations, or show a warning when redirecting to potentially untrusted content. X X X https://cwe.mitre.org/data/definitions/601.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
81 V5 Validation 5.1.4 Verify that structured data is strongly typed and validated against a defined schema including allowed characters, length and pattern (e.g. credit card numbers or telephone, or validating that two related fields are reasonable, such as checking that suburb and zip/postcode match). ([C5](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/20.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
82 V5 Validation 5.1.3 Verify that all input (HTML form fields, REST requests, URL parameters, HTTP headers, cookies, batch files, RSS feeds, etc) is validated using positive validation (whitelisting). ([C5](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/20.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
83 V5 Validation 5.1.2 Verify that frameworks protect against mass parameter assignment attacks, or that the application has countermeasures to protect against unsafe parameter assignment, such as marking fields private or similar. ([C5](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/915.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
84 V5 Validation 5.1.1 Verify that the application has defenses against HTTP parameter pollution attacks, particularly if the application framework makes no distinction about the source of request parameters (GET, POST, cookies, headers, or environment variables). X X X https://cwe.mitre.org/data/definitions/235.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
85 V4 Access 4.3.3 Verify the application has additional authorization (such as step up or adaptive authentication) for lower value systems, and / or segregation of duties for high value applications to enforce anti-fraud controls as per the risk of application and past fraud. X X https://cwe.mitre.org/data/definitions/732.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
86 V4 Access 4.3.2 Verify that directory browsing is disabled unless deliberately desired. Additionally, applications should not allow discovery or disclosure of file or directory metadata, such as Thumbs.db, .DS_Store, .git or .svn folders. X X X https://cwe.mitre.org/data/definitions/548.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
87 V4 Access 4.3.1 Verify administrative interfaces use appropriate multi-factor authentication to prevent unauthorized use. X X X https://cwe.mitre.org/data/definitions/419.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
88 V4 Access 4.2.2 Verify that the application or framework enforces a strong anti-CSRF mechanism to protect authenticated functionality, and effective anti-automation or anti-CSRF protects unauthenticated functionality. X X X https://cwe.mitre.org/data/definitions/352.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
89 V4 Access 4.2.1 Verify that sensitive data and APIs are protected against direct object attacks targeting creation, reading, updating and deletion of records, such as creating or updating someone else's record, viewing everyone's records, or deleting all records. X X X https://cwe.mitre.org/data/definitions/639.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
90 V4 Access 4.1.5 Verify that access controls fail securely including when an exception occurs. ([C10](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/285.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
91 V4 Access 4.1.4 Verify that the principle of deny by default exists whereby new users/roles start with minimal or no permissions and users/roles do not receive access to new features until access is explicitly assigned. ([C7](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/276.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
92 V4 Access 4.1.3 Verify that the principle of least privilege exists - users should only be able to access functions, data files, URLs, controllers, services, and other resources, for which they possess specific authorization. This implies protection against spoofing and elevation of privilege. ([C7](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/285.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
93 V4 Access 4.1.2 Verify that all user and data attributes and policy information used by access controls cannot be manipulated by end users unless specifically authorized. X X X https://cwe.mitre.org/data/definitions/639.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
94 V4 Access 4.1.1 Verify that the application enforces access control rules on a trusted service layer, especially if client-side access control is present and could be bypassed. X X X https://cwe.mitre.org/data/definitions/602.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
95 V3 Session 3.7.1 Verify the application ensures a valid login session or requires re-authentication or secondary verification before allowing any sensitive transactions or account modifications. X X X https://cwe.mitre.org/data/definitions/778.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
96 V3 Session 3.6.2 Verify that CSPs inform relying parties of the last authentication event, to allow RPs to determine if they need to re-authenticate the user. X https://cwe.mitre.org/data/definitions/613.html 7.2.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
97 V3 Session 3.6.1 Verify that relying parties specify the maximum authentication time to CSPs and that CSPs re-authenticate the subscriber if they haven't used a session within that period. X https://cwe.mitre.org/data/definitions/613.html 7.2.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
98 V3 Session 3.5.3 Verify that stateless session tokens use digital signatures, encryption, and other countermeasures to protect against tampering, enveloping, replay, null cipher, and key substitution attacks. X X https://cwe.mitre.org/data/definitions/345.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
99 V3 Session 3.5.2 Verify the application uses session tokens rather than static API secrets and keys, except with legacy implementations. X X https://cwe.mitre.org/data/definitions/798.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
100 V3 Session 3.5.1 Verify the application does not treat OAuth and refresh tokens &mdash OWASP Application Security Verification Standard 4.0-en.csv (github) View
101 V3 Session 3.4.5 Verify that if the application is published under a domain name with other applications that set or use session cookies that might override or disclose the session cookies, set the path attribute in cookie-based session tokens using the most precise path possible. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/16.html 7.1.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
102 V3 Session 3.4.4 Verify that cookie-based session tokens use "__Host-" prefix (see references) to provide session cookie confidentiality. X X X https://cwe.mitre.org/data/definitions/16.html 7.1.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
103 V3 Session 3.4.3 Verify that cookie-based session tokens utilize the 'SameSite' attribute to limit exposure to cross-site request forgery attacks. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/16.html 7.1.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
104 V3 Session 3.4.2 Verify that cookie-based session tokens have the 'HttpOnly' attribute set. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/1004.html 7.1.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
105 V3 Session 3.4.1 Verify that cookie-based session tokens have the 'Secure' attribute set. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/614.html 7.1.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
106 V3 Session 3.3.4 Verify that users are able to view and log out of any or all currently active sessions and devices. X X https://cwe.mitre.org/data/definitions/613.html 7.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
107 V3 Session 3.3.3 Verify that the application terminates all other active sessions after a successful password change, and that this is effective across the application, federated login (if present), and any relying parties. X X https://cwe.mitre.org/data/definitions/613.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
108 V3 Session 3.3.2 If authenticators permit users to remain logged in, verify that re-authentication occurs periodically both when actively used or after an idle period. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) 30 days 12 hours or 30 minutes of inactivity, 2FA optional 12 hours or 15 minutes of inactivity, with 2FA https://cwe.mitre.org/data/definitions/613.html 7.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
109 V3 Session 3.3.1 Verify that logout and expiration invalidate the session token, such that the back button or a downstream relying party does not resume an authenticated session, including across relying parties. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/613.html 7.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
110 V3 Session 3.2.4 Verify that session token are generated using approved cryptographic algorithms. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/331.html 7.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
111 V3 Session 3.2.3 Verify the application only stores session tokens in the browser using secure methods such as appropriately secured cookies (see section 3.4) or HTML 5 session storage. X X X https://cwe.mitre.org/data/definitions/539.html 7.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
112 V3 Session 3.2.2 Verify that session tokens possess at least 64 bits of entropy. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/331.html 7.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
113 V3 Session 3.2.1 Verify the application generates a new session token on user authentication. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/384.html 7.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
114 V3 Session 3.1.1 Verify the application never reveals session tokens in URL parameters or error messages. X X X https://cwe.mitre.org/data/definitions/598.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
115 V2 Authentication 2.9.3 Verify that approved cryptographic algorithms are used in the generation, seeding, and verification. X X https://cwe.mitre.org/data/definitions/327.html 5.1.7.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
116 V2 Authentication 2.9.2 Verify that the challenge nonce is at least 64 bits in length, and statistically unique or unique over the lifetime of the cryptographic device. X X https://cwe.mitre.org/data/definitions/330.html 5.1.7.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
117 V2 Authentication 2.9.1 Verify that cryptographic keys used in verification are stored securely and protected against disclosure, such as using a TPM or HSM, or an OS service that can use this secure storage. X X https://cwe.mitre.org/data/definitions/320.html 5.1.7.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
118 V2 Authentication 2.8.7 Verify that biometric authenticators are limited to use only as secondary factors in conjunction with either something you have and something you know. o X https://cwe.mitre.org/data/definitions/308.html 5.2.3 OWASP Application Security Verification Standard 4.0-en.csv (github) View
119 V2 Authentication 2.8.6 Verify physical single factor OTP generator can be revoked in case of theft or other loss. Ensure that revocation is immediately effective across logged in sessions, regardless of location. X X https://cwe.mitre.org/data/definitions/613.html 5.2.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
120 V2 Authentication 2.8.5 Verify that if a time-based multi factor OTP token is re-used during the validity period, it is logged and rejected with secure notifications being sent to the holder of the device. X X https://cwe.mitre.org/data/definitions/287.html 5.1.5.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
121 V2 Authentication 2.8.4 Verify that time-based OTP can be used only once within the validity period. X X https://cwe.mitre.org/data/definitions/287.html 5.1.4.2 / 5.1.5.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
122 V2 Authentication 2.8.3 Verify that approved cryptographic algorithms are used in the generation, seeding, and verification. X X https://cwe.mitre.org/data/definitions/326.html 5.1.4.2 / 5.1.5.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
123 V2 Authentication 2.8.2 Verify that symmetric keys used to verify submitted OTPs are highly protected, such as by using a hardware security module or secure operating system based key storage. X X https://cwe.mitre.org/data/definitions/320.html 5.1.4.2 / 5.1.5.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
124 V2 Authentication 2.8.1 Verify that time-based OTPs have a defined lifetime before expiring. X X X https://cwe.mitre.org/data/definitions/613.html 5.1.4.2 / 5.1.5.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
125 V2 Authentication 2.7.6 Verify that the initial authentication code is generated by a secure random number generator, containing at least 20 bits of entropy (typically a six digital random number is sufficient). X X https://cwe.mitre.org/data/definitions/310.html 5.1.3.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
126 V2 Authentication 2.7.5 Verify that the out of band verifier retains only a hashed version of the authentication code. X X https://cwe.mitre.org/data/definitions/256.html 5.1.3.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
127 V2 Authentication 2.7.4 Verify that the out of band authenticator and verifier communicates over a secure independent channel. X X X https://cwe.mitre.org/data/definitions/523.html 5.1.3.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
128 V2 Authentication 2.7.3 Verify that the out of band verifier authentication requests, codes, or tokens are only usable once, and only for the original authentication request. X X X https://cwe.mitre.org/data/definitions/287.html 5.1.3.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
129 V2 Authentication 2.7.2 Verify that the out of band verifier expires out of band authentication requests, codes, or tokens after 10 minutes. X X X https://cwe.mitre.org/data/definitions/287.html 5.1.3.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
130 V2 Authentication 2.7.1 Verify that clear text out of band (NIST "restricted") authenticators, such as SMS or PSTN, are not offered by default, and stronger alternatives such as push notifications are offered first. X X X https://cwe.mitre.org/data/definitions/287.html 5.1.3.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
131 V2 Authentication 2.6.3 Verify that lookup secrets are resistant to offline attacks, such as predictable values. X X https://cwe.mitre.org/data/definitions/310.html 5.1.2.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
132 V2 Authentication 2.6.2 Verify that lookup secrets have sufficient randomness (112 bits of entropy), or if less than 112 bits of entropy, salted with a unique and random 32-bit salt and hashed with an approved one-way hash. X X https://cwe.mitre.org/data/definitions/330.html 5.1.2.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
133 V2 Authentication 2.6.1 Verify that lookup secrets can be used only once. X X https://cwe.mitre.org/data/definitions/308.html 5.1.2.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
134 V2 Authentication 2.5.7 Verify that if OTP or multi-factor authentication factors are lost, that evidence of identity proofing is performed at the same level as during enrollment. X X https://cwe.mitre.org/data/definitions/308.html 6.1.2.3 OWASP Application Security Verification Standard 4.0-en.csv (github) View
135 V2 Authentication 2.5.6 Verify forgotten password, and other recovery paths use a secure recovery mechanism, such as TOTP or other soft token, mobile push, or another offline recovery mechanism. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/640.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
136 V2 Authentication 2.5.5 Verify that if an authentication factor is changed or replaced, that the user is notified of this event. X X X https://cwe.mitre.org/data/definitions/304.html 6.1.2.3 OWASP Application Security Verification Standard 4.0-en.csv (github) View
137 V2 Authentication 2.5.4 Verify shared or default accounts are not present (e.g. "root", "admin", or "sa"). X X X https://cwe.mitre.org/data/definitions/16.html 5.1.1.2 / A.3 OWASP Application Security Verification Standard 4.0-en.csv (github) View
138 V2 Authentication 2.5.3 Verify password credential recovery does not reveal the current password in any way. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/640.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
139 V2 Authentication 2.5.2 Verify password hints or knowledge-based authentication (so-called "secret questions") are not present. X X X https://cwe.mitre.org/data/definitions/640.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
140 V2 Authentication 2.5.1 Verify that a system generated initial activation or recovery secret is not sent in clear text to the user. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/640.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
141 V2 Authentication 2.4.5 Verify that an additional iteration of a key derivation function is performed, using a salt value that is secret and known only to the verifier. Generate the salt value using an approved random bit generator [SP 800-90Ar1] and provide at least the minimum security strength specified in the latest revision of SP 800-131A. The secret salt value SHALL be stored separately from the hashed passwords (e.g., in a specialized device like a hardware security module). X X https://cwe.mitre.org/data/definitions/916.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
142 V2 Authentication 2.4.4 Verify that if bcrypt is used, the work factor SHOULD be as large as verification server performance will allow, typically at least 13. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/916.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
143 V2 Authentication 2.4.3 Verify that if PBKDF2 is used, the iteration count SHOULD be as large as verification server performance will allow, typically at least 100,000 iterations. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/916.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
144 V2 Authentication 2.4.2 Verify that the salt is at least 32 bits in length and be chosen arbitrarily to minimize salt value collisions among stored hashes. For each credential, a unique salt value and the resulting hash SHALL be stored. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/916.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
145 V2 Authentication 2.4.1 Verify that passwords are stored in a form that is resistant to offline attacks. Passwords SHALL be salted and hashed using an approved one-way key derivation or password hashing function. Key derivation and password hashing functions take a password, a salt, and a cost factor as inputs when generating a password hash. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/916.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
146 V2 Authentication 2.3.3 Verify that renewal instructions are sent with sufficient time to renew time bound authenticators. X X https://cwe.mitre.org/data/definitions/287.html 6.1.4 OWASP Application Security Verification Standard 4.0-en.csv (github) View
147 V2 Authentication 2.3.2 Verify that enrollment and use of subscriber-provided authentication devices are supported, such as a U2F or FIDO tokens. X X https://cwe.mitre.org/data/definitions/308.html 6.1.3 OWASP Application Security Verification Standard 4.0-en.csv (github) View
148 V2 Authentication 2.3.1 Verify system generated initial passwords or activation codes SHOULD be securely randomly generated, SHOULD be at least 6 characters long, and MAY contain letters and numbers, and expire after a short period of time. These initial secrets must not be permitted to become the long term password. X X X https://cwe.mitre.org/data/definitions/330.html 5.1.1.2 / A.3 OWASP Application Security Verification Standard 4.0-en.csv (github) View
149 V2 Authentication 2.2.7 Verify intent to authenticate by requiring the entry of an OTP token or user-initiated action such as a button press on a FIDO hardware key. X https://cwe.mitre.org/data/definitions/308.html 5.2.9 OWASP Application Security Verification Standard 4.0-en.csv (github) View
150 V2 Authentication 2.2.6 Verify replay resistance through the mandated use of OTP devices, cryptographic authenticators, or lookup codes. X https://cwe.mitre.org/data/definitions/308.html 5.2.8 OWASP Application Security Verification Standard 4.0-en.csv (github) View
151 V2 Authentication 2.2.5 Verify that where a credential service provider (CSP) and the application verifying authentication are separated, mutually authenticated TLS is in place between the two endpoints. X https://cwe.mitre.org/data/definitions/319.html 5.2.6 OWASP Application Security Verification Standard 4.0-en.csv (github) View
152 V2 Authentication 2.2.4 Verify impersonation resistance against phishing, such as the use of multi-factor authentication, cryptographic devices with intent (such as connected keys with a push to authenticate), or at higher AAL levels, client-side certificates. X https://cwe.mitre.org/data/definitions/308.html 5.2.5 OWASP Application Security Verification Standard 4.0-en.csv (github) View
153 V2 Authentication 2.2.3 Verify that secure notifications are sent to users after updates to authentication details, such as credential resets, email or address changes, logging in from unknown or risky locations. The use of push notifications - rather than SMS or email - is preferred, but in the absence of push notifications, SMS or email is acceptable as long as no sensitive information is disclosed in the notification. X X X https://cwe.mitre.org/data/definitions/620.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
154 V2 Authentication 2.2.2 Verify that the use of weak authenticators (such as SMS and email) is limited to secondary verification and transaction approval and not as a replacement for more secure authentication methods. Verify that stronger methods are offered before weak methods, users are aware of the risks, or that proper measures are in place to limit the risks of account compromise. X X X https://cwe.mitre.org/data/definitions/304.html 5.2.10 OWASP Application Security Verification Standard 4.0-en.csv (github) View
155 V2 Authentication 2.2.1 Verify that anti-automation controls are effective at mitigating breached credential testing, brute force, and account lockout attacks. Such controls include blocking the most common breached passwords, soft lockouts, rate limiting, CAPTCHA, ever increasing delays between attempts, IP address restrictions, or risk-based restrictions such as location, first login on a device, recent attempts to unlock the account, or similar. Verify that no more than 100 failed attempts per hour is possible on a single account. X X X https://cwe.mitre.org/data/definitions/307.html 5.2.2 / 5.1.1.2 / 5.1.4.2 / 5.1.5.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
156 V2 Authentication 2.10.4 Verify passwords, integrations with databases and third-party systems, seeds and internal secrets, and API keys are managed securely and not included in the source code or stored within source code repositories. Such storage SHOULD resist offline attacks. The use of a secure software key store (L1), hardware trusted platform module (TPM), or a hardware security module (L3) is recommended for password storage. OS assisted HSM https://cwe.mitre.org/data/definitions/798.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
157 V2 Authentication 2.10.3 Verify that passwords are stored with sufficient protection to prevent offline recovery attacks, including local system access. OS assisted HSM https://cwe.mitre.org/data/definitions/522.html 5.1.1.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
158 V2 Authentication 2.10.2 Verify that if passwords are required, the credentials are not a default account. OS assisted HSM https://cwe.mitre.org/data/definitions/255.html 5.1.1.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
159 V2 Authentication 2.10.1 Verify that integration secrets do not rely on unchanging passwords, such as API keys or shared privileged accounts. OS assisted HSM https://cwe.mitre.org/data/definitions/287.html 5.1.1.1 OWASP Application Security Verification Standard 4.0-en.csv (github) View
160 V2 Authentication 2.1.9 Verify that there are no password composition rules limiting the type of characters permitted. There should be no requirement for upper or lower case or numbers or special characters. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/521.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
161 V2 Authentication 2.1.8 Verify that a password strength meter is provided to help users set a stronger password. X X X https://cwe.mitre.org/data/definitions/521.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
162 V2 Authentication 2.1.7 Verify that passwords submitted during account registration, login, and password change are checked against a set of breached passwords either locally (such as the top 1,000 or 10,000 most common passwords which match the system's password policy) or using an external API. If using an API a zero knowledge proof or other mechanism should be used to ensure that the plain text password is not sent or used in verifying the breach status of the password. If the password is breached, the application must require the user to set a new non-breached password. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/521.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
163 V2 Authentication 2.1.6 Verify that password change functionality requires the user's current and new password. X X X https://cwe.mitre.org/data/definitions/620.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
164 V2 Authentication 2.1.5 Verify users can change their password. X X X https://cwe.mitre.org/data/definitions/620.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
165 V2 Authentication 2.1.4 Verify that Unicode characters are permitted in passwords. A single Unicode code point is considered a character, so 12 emoji or 64 kanji characters should be valid and permitted. X X X https://cwe.mitre.org/data/definitions/521.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
166 V2 Authentication 2.1.3 Verify that passwords can contain spaces and truncation is not performed. Consecutive multiple spaces MAY optionally be coalesced. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/521.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
167 V2 Authentication 2.1.2 Verify that passwords 64 characters or longer are permitted. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/521.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
168 V2 Authentication 2.1.12 Verify that the user can choose to either temporarily view the entire masked password, or temporarily view the last typed character of the password on platforms that do not have this as native functionality. X X X https://cwe.mitre.org/data/definitions/521.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
169 V2 Authentication 2.1.11 Verify that "paste" functionality, browser password helpers, and external password managers are permitted. X X X https://cwe.mitre.org/data/definitions/521.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
170 V2 Authentication 2.1.10 Verify that there are no periodic credential rotation or password history requirements. X X X https://cwe.mitre.org/data/definitions/263.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
171 V2 Authentication 2.1.1 Verify that user set passwords are at least 12 characters in length. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/521.html 5.1.1.2 OWASP Application Security Verification Standard 4.0-en.csv (github) View
172 V14 Config 14.5.4 Verify that HTTP headers added by a trusted proxy or SSO devices, such as a bearer token, are authenticated by the application. X X https://cwe.mitre.org/data/definitions/306.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
173 V14 Config 14.5.3 Verify that the cross-domain resource sharing (CORS) Access-Control-Allow-Origin header uses a strict white-list of trusted domains to match against and does not support the "null" origin. X X X https://cwe.mitre.org/data/definitions/346.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
174 V14 Config 14.5.2 Verify that the supplied Origin header is not used for authentication or access control decisions, as the Origin header can easily be changed by an attacker. X X X https://cwe.mitre.org/data/definitions/346.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
175 V14 Config 14.5.1 Verify that the application server only accepts the HTTP methods in use by the application or API, including pre-flight OPTIONS. X X X https://cwe.mitre.org/data/definitions/749.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
176 V14 Config 14.4.7 Verify that a suitable X-Frame-Options or Content-Security-Policy: frame-ancestors header is in use for sites where content should not be embedded in a third-party site. X X X https://cwe.mitre.org/data/definitions/346.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
177 V14 Config 14.4.6 Verify that a suitable "Referrer-Policy" header is included, such as "no-referrer" or "same-origin". X X X https://cwe.mitre.org/data/definitions/116.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
178 V14 Config 14.4.5 Verify that HTTP Strict Transport Security headers are included on all responses and for all subdomains, such as Strict-Transport-Security: max-age=15724800 OWASP Application Security Verification Standard 4.0-en.csv (github) View
179 V14 Config 14.4.4 Verify that all responses contain X-Content-Type-Options: nosniff. X X X https://cwe.mitre.org/data/definitions/116.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
180 V14 Config 14.4.3 Verify that a content security policy (CSPv2) is in place that helps mitigate impact for XSS attacks like HTML, DOM, JSON, and JavaScript injection vulnerabilities. X X X https://cwe.mitre.org/data/definitions/1021.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
181 V14 Config 14.4.2 Verify that all API responses contain Content-Disposition: attachment OWASP Application Security Verification Standard 4.0-en.csv (github) View
182 V14 Config 14.4.1 Verify that every HTTP response contains a content type header specifying a safe character set (e.g., UTF-8, ISO 8859-1). X X X https://cwe.mitre.org/data/definitions/173.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
183 V14 Config 14.3.3 Verify that the HTTP headers or any part of the HTTP response do not expose detailed version information of system components. X X X https://cwe.mitre.org/data/definitions/200.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
184 V14 Config 14.3.2 Verify that web or application server and application framework debug modes are disabled in production to eliminate debug features, developer consoles, and unintended security disclosures. X X X https://cwe.mitre.org/data/definitions/497.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
185 V14 Config 14.3.1 Verify that web or application server and framework error messages are configured to deliver user actionable, customized responses to eliminate any unintended security disclosures. X X X https://cwe.mitre.org/data/definitions/209.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
186 V14 Config 14.2.6 Verify that the attack surface is reduced by sandboxing or encapsulating third party libraries to expose only the required behaviour into the application. ([C2](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/265.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
187 V14 Config 14.2.5 Verify that an inventory catalog is maintained of all third party libraries in use. ([C2](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X OWASP Application Security Verification Standard 4.0-en.csv (github) View
188 V14 Config 14.2.4 Verify that third party components come from pre-defined, trusted and continually maintained repositories. ([C2](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X https://cwe.mitre.org/data/definitions/829.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
189 V14 Config 14.2.3 Verify that if application assets, such as JavaScript libraries, CSS stylesheets or web fonts, are hosted externally on a content delivery network (CDN) or external provider, Subresource Integrity (SRI) is used to validate the integrity of the asset. X X X https://cwe.mitre.org/data/definitions/714.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
190 V14 Config 14.2.2 Verify that all unneeded features, documentation, samples, configurations are removed, such as sample applications, platform documentation, and default or example users. X X X https://cwe.mitre.org/data/definitions/1002.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
191 V14 Config 14.2.1 Verify that all components are up to date, preferably using a dependency checker during build or compile time. ([C2](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) X X X https://cwe.mitre.org/data/definitions/1026.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
192 V14 Config 14.1.5 Verify that authorized administrators can verify the integrity of all security-relevant configurations to detect tampering. X OWASP Application Security Verification Standard 4.0-en.csv (github) View
193 V14 Config 14.1.4 Verify that the application, configuration, and all dependencies can be re-deployed using automated deployment scripts, built from a documented and tested runbook in a reasonable time, or restored from backups in a timely fashion. X X OWASP Application Security Verification Standard 4.0-en.csv (github) View
194 V14 Config 14.1.3 Verify that server configuration is hardened as per the recommendations of the application server and frameworks in use. X X https://cwe.mitre.org/data/definitions/16.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
195 V14 Config 14.1.2 Verify that compiler flags are configured to enable all available buffer overflow protections and warnings, including stack randomization, data execution prevention, and to break the build if an unsafe pointer, memory, format string, integer, or string operations are found. X X https://cwe.mitre.org/data/definitions/120.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
196 V14 Config 14.1.1 Verify that the application build and deployment processes are performed in a secure and repeatable way, such as CI / CD automation, automated configuration management, and automated deployment scripts. X X OWASP Application Security Verification Standard 4.0-en.csv (github) View
197 V13 API 13.4.2 Verify that GraphQL or other data layer authorization logic should be implemented at the business logic layer instead of the GraphQL layer. X X https://cwe.mitre.org/data/definitions/285.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
198 V13 API 13.4.1 Verify that query whitelisting or a combination of depth limiting and amount limiting should be used to prevent GraphQL or data layer expression denial of service (DoS) as a result of expensive, nested queries. For more advanced scenarios, query cost analysis should be used. X X https://cwe.mitre.org/data/definitions/770.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
199 V13 API 13.3.2 Verify that the message payload is signed using WS-Security to ensure reliable transport between client and service. X X https://cwe.mitre.org/data/definitions/345.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
200 V13 API 13.3.1 Verify that XSD schema validation takes place to ensure a properly formed XML document, followed by validation of each input field before any processing of that data takes place. X X X https://cwe.mitre.org/data/definitions/20.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
201 V13 API 13.2.6 Verify that the message headers and payload are trustworthy and not modified in transit. Requiring strong encryption for transport (TLS only) may be sufficient in many cases as it provides both confidentiality and integrity protection. Per-message digital signatures can provide additional assurance on top of the transport protections for high-security applications but bring with them additional complexity and risks to weigh against the benefits. X X https://cwe.mitre.org/data/definitions/345.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
202 V13 API 13.2.5 Verify that REST services explicitly check the incoming Content-Type to be the expected one, such as application/xml or application/JSON. X X https://cwe.mitre.org/data/definitions/436.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
203 V13 API 13.2.4 Verify that REST services have anti-automation controls to protect against excessive calls, especially if the API is unauthenticated. X X https://cwe.mitre.org/data/definitions/779.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
204 V13 API 13.2.3 Verify that RESTful web services that utilize cookies are protected from Cross-Site Request Forgery via the use of at least one or more of the following: triple or double submit cookie pattern (see [references](https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)_Prevention_Cheat_Sheet)), CSRF nonces, or ORIGIN request header checks. X X X https://cwe.mitre.org/data/definitions/352.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
205 V13 API 13.2.2 Verify that JSON schema validation is in place and verified before accepting input. X X X https://cwe.mitre.org/data/definitions/20.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
206 V13 API 13.2.1 Verify that enabled RESTful HTTP methods are a valid choice for the user or action, such as preventing normal users using DELETE or PUT on protected API or resources. X X X https://cwe.mitre.org/data/definitions/650.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
207 V13 API 13.1.5 Verify that requests containing unexpected or missing content types are rejected with appropriate headers (HTTP response status 406 Unacceptable or 415 Unsupported Media Type). X X https://cwe.mitre.org/data/definitions/434.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
208 V13 API 13.1.4 Verify that authorization decisions are made at both the URI, enforced by programmatic or declarative security at the controller or router, and at the resource level, enforced by model-based permissions. X X https://cwe.mitre.org/data/definitions/285.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
209 V13 API 13.1.3 Verify API URLs do not expose sensitive information, such as the API key, session tokens etc. X X X https://cwe.mitre.org/data/definitions/598.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
210 V13 API 13.1.2 Verify that access to administration and management functions is limited to authorized administrators. X X X https://cwe.mitre.org/data/definitions/419.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
211 V13 API 13.1.1 Verify that all application components use the same encodings and parsers to avoid parsing attacks that exploit different URI or file parsing behavior that could be used in SSRF and RFI attacks. X X X https://cwe.mitre.org/data/definitions/116.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
212 V12 Files 12.6.1 Verify that the web or application server is configured with a whitelist of resources or systems to which the server can send requests or load data/files from. X X X https://cwe.mitre.org/data/definitions/918.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
213 V12 Files 12.5.2 Verify that direct requests to uploaded files will never be executed as HTML/JavaScript content. X X X https://cwe.mitre.org/data/definitions/434.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
214 V12 Files 12.5.1 Verify that the web tier is configured to serve only files with specific file extensions to prevent unintentional information and source code leakage. For example, backup files (e.g. .bak), temporary working files (e.g. .swp), compressed files (.zip, .tar.gz, etc) and other extensions commonly used by editors should be blocked unless required. X X X https://cwe.mitre.org/data/definitions/552.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
215 V12 Files 12.4.2 Verify that files obtained from untrusted sources are scanned by antivirus scanners to prevent upload of known malicious content. X X X https://cwe.mitre.org/data/definitions/509.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
216 V12 Files 12.4.1 Verify that files obtained from untrusted sources are stored outside the web root, with limited permissions, preferably with strong validation. X X X https://cwe.mitre.org/data/definitions/922.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
217 V12 Files 12.3.6 Verify that the application does not include and execute functionality from untrusted sources, such as unverified content distribution networks, JavaScript libraries, node npm libraries, or server-side DLLs. X X https://cwe.mitre.org/data/definitions/829.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
218 V12 Files 12.3.5 Verify that untrusted file metadata is not used directly with system API or libraries, to protect against OS command injection. X X X https://cwe.mitre.org/data/definitions/78.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
219 V12 Files 12.3.4 Verify that the application protects against reflective file download (RFD) by validating or ignoring user-submitted filenames in a JSON, JSONP, or URL parameter, the response Content-Type header should be set to text/plain, and the Content-Disposition header should have a fixed filename. X X X https://cwe.mitre.org/data/definitions/641.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
220 V12 Files 12.3.3 Verify that user-submitted filename metadata is validated or ignored to prevent the disclosure or execution of remote files (RFI), which may also lead to SSRF. X X X https://cwe.mitre.org/data/definitions/98.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
221 V12 Files 12.3.2 Verify that user-submitted filename metadata is validated or ignored to prevent the disclosure, creation, updating or removal of local files (LFI). X X X https://cwe.mitre.org/data/definitions/73.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
222 V12 Files 12.3.1 Verify that user-submitted filename metadata is not used directly with system or framework file and URL API to protect against path traversal. X X X https://cwe.mitre.org/data/definitions/22.html OWASP Application Security Verification Standard 4.0-en.csv (github) View
223