forked from fportantier/vulpy
-
Notifications
You must be signed in to change notification settings - Fork 0
Files
/
Copy pathowasp-asvs-4.0.csv
287 lines (287 loc) · 63.5 KB
/
owasp-asvs-4.0.csv
1 | Section | Name | Item | Compliance | Description | L1 | L2 | L3 | CWE | NIST |
|---|---|---|---|---|---|---|---|---|---|---|
2 | V1 | Architecture | 1.1.1 | N/A | Verify the use of a secure software development lifecycle that addresses security in all stages of development. ([C1](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) | X | X | |||
3 | V1 | Architecture | 1.1.2 | N/A | Verify the use of threat modeling for every design change or sprint planning to identify threats, plan for countermeasures, facilitate appropriate risk responses, and guide security testing. | X | X | 1053 | ||
4 | V1 | Architecture | 1.1.3 | N/A | Verify that all user stories and features contain functional security constraints, such as "As a user, I should be able to view and edit my profile. I should not be able to view or edit anyone else's profile" | X | X | 1110 | ||
5 | V1 | Architecture | 1.1.4 | N/A | Verify documentation and justification of all the application's trust boundaries, components, and significant data flows. | X | X | 1059 | ||
6 | V1 | Architecture | 1.1.5 | N/A | Verify definition and security analysis of the application's high-level architecture and all connected remote services. ([C1](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) | X | X | 1059 | ||
7 | V1 | Architecture | 1.1.6 | N/A | Verify implementation of centralized, simple (economy of design), vetted, secure, and reusable security controls to avoid duplicate, missing, ineffective, or insecure controls. ([C10](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) | X | X | 637 | ||
8 | V1 | Architecture | 1.1.7 | N/A | Verify availability of a secure coding checklist, security requirements, guideline, or policy to all developers and testers. | X | X | 637 | ||
9 | V1 | Architecture | 1.10.1 | Yes | Verify that a source code control system is in use, with procedures to ensure that check-ins are accompanied by issues or change tickets. The source code control system should have access control and identifiable users to allow traceability of any changes. | X | X | 284 | ||
10 | V1 | Architecture | 1.11.1 | N/A | Verify the definition and documentation of all application components in terms of the business or security functions they provide. | X | X | 1059 | ||
11 | V1 | Architecture | 1.11.2 | N/A | Verify that all high-value business logic flows, including authentication, session management and access control, do not share unsynchronized state. | X | X | 362 | ||
12 | V1 | Architecture | 1.11.3 | N/A | Verify that all high-value business logic flows, including authentication, session management and access control are thread safe and resistant to time-of-check and time-of-use race conditions. | X | 367 | |||
13 | V1 | Architecture | 1.12.1 | N/A | Verify that user-uploaded files are stored outside of the web root. | X | X | 552 | ||
14 | V1 | Architecture | 1.12.2 | N/A | Verify that user-uploaded files - if required to be displayed or downloaded from the application - are served by either octet stream downloads, or from an unrelated domain, such as a cloud file storage bucket. Implement a suitable content security policy to reduce the risk from XSS vectors or other attacks from the uploaded file. | X | X | 646 | ||
15 | V1 | Architecture | 1.14.1 | N/A | Verify the segregation of components of differing trust levels through well-defined security controls, firewall rules, API gateways, reverse proxies, cloud-based security groups, or similar mechanisms. | X | X | 923 | ||
16 | V1 | Architecture | 1.14.2 | N/A | Verify that if deploying binaries to untrusted devices makes use of binary signatures, trusted connections, and verified endpoints. | X | X | 494 | ||
17 | V1 | Architecture | 1.14.3 | N/A | Verify that the build pipeline warns of out-of-date or insecure components and takes appropriate actions. | X | X | 1104 | ||
18 | V1 | Architecture | 1.14.4 | N/A | Verify that the build pipeline contains a build step to automatically build and verify the secure deployment of the application, particularly if the application infrastructure is software defined, such as cloud environment build scripts. | X | X | |||
19 | V1 | Architecture | 1.14.5 | N/A | Verify that application deployments adequately sandbox, containerize and/or isolate at the network level to delay and deter attackers from attacking other applications, especially when they are performing sensitive or dangerous actions such as deserialization. ([C5](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) | X | X | 265 | ||
20 | V1 | Architecture | 1.14.6 | N/A | Verify the application does not use unsupported, insecure, or deprecated client-side technologies such as NSAPI plugins, Flash, Shockwave, ActiveX, Silverlight, NACL, or client-side Java applets. | X | X | 477 | ||
21 | V1 | Architecture | 1.2.1 | N/A | Verify the use of unique or special low-privilege operating system accounts for all application components, services, and servers. ([C3](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) | X | X | 250 | ||
22 | V1 | Architecture | 1.2.2 | N/A | Verify that communications between application components, including APIs, middleware and data layers, are authenticated. Components should have the least necessary privileges needed. ([C3](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) | X | X | 306 | ||
23 | V1 | Architecture | 1.2.3 | N/A | Verify that the application uses a single vetted authentication mechanism that is known to be secure, can be extended to include strong authentication, and has sufficient logging and monitoring to detect account abuse or breaches. | X | X | 306 | ||
24 | V1 | Architecture | 1.2.4 | N/A | Verify that all authentication pathways and identity management APIs implement consistent authentication security control strength, such that there are no weaker alternatives per the risk of the application. | X | X | 306 | ||
25 | V1 | Architecture | 1.4.1 | N/A | Verify that trusted enforcement points such as at access control gateways, servers, and serverless functions enforce access controls. Never enforce access controls on the client. | X | X | 602 | ||
26 | V1 | Architecture | 1.4.2 | N/A | Verify that the chosen access control solution is flexible enough to meet the application's needs. | X | X | 284 | ||
27 | V1 | Architecture | 1.4.3 | N/A | Verify enforcement of the principle of least privilege in functions, data files, URLs, controllers, services, and other resources. This implies protection against spoofing and elevation of privilege. | X | X | 272 | ||
28 | V1 | Architecture | 1.4.4 | N/A | Verify the application uses a single and well-vetted access control mechanism for accessing protected data and resources. All requests must pass through this single mechanism to avoid copy and paste or insecure alternative paths. ([C7](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) | X | X | 284 | ||
29 | V1 | Architecture | 1.4.5 | N/A | Verify that attribute or feature-based access control is used whereby the code checks the user's authorization for a feature/data item rather than just their role. Permissions should still be allocated using roles. ([C7](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) | X | X | 275 | ||
30 | V1 | Architecture | 1.5.1 | N/A | Verify that input and output requirements clearly define how to handle and process data based on type, content, and applicable laws, regulations, and other policy compliance. | X | X | 1029 | ||
31 | V1 | Architecture | 1.5.2 | N/A | Verify that serialization is not used when communicating with untrusted clients. If this is not possible, ensure that adequate integrity controls (and possibly encryption if sensitive data is sent) are enforced to prevent deserialization attacks including object injection. | X | X | 502 | ||
32 | V1 | Architecture | 1.5.3 | N/A | Verify that input validation is enforced on a trusted service layer. ([C5](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) | X | X | 602 | ||
33 | V1 | Architecture | 1.5.4 | N/A | Verify that output encoding occurs close to or by the interpreter for which it is intended. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) | X | X | 116 | ||
34 | V1 | Architecture | 1.6.1 | N/A | Verify that there is an explicit policy for management of cryptographic keys and that a cryptographic key lifecycle follows a key management standard such as NIST SP 800-57. | X | X | 320 | ||
35 | V1 | Architecture | 1.6.2 | N/A | Verify that consumers of cryptographic services protect key material and other secrets by using key vaults or API based alternatives. | X | X | 320 | ||
36 | V1 | Architecture | 1.6.3 | N/A | Verify that all keys and passwords are replaceable and are part of a well-defined process to re-encrypt sensitive data. | X | X | 320 | ||
37 | V1 | Architecture | 1.6.4 | N/A | Verify that symmetric keys, passwords, or API secrets generated by or shared with clients are used only in protecting low risk secrets, such as encrypting local storage, or temporary ephemeral uses such as parameter obfuscation. Sharing secrets with clients is clear-text equivalent and architecturally should be treated as such. | X | X | 320 | ||
38 | V1 | Architecture | 1.7.1 | N/A | Verify that a common logging format and approach is used across the system. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) | X | X | 1009 | ||
39 | V1 | Architecture | 1.7.2 | N/A | Verify that logs are securely transmitted to a preferably remote system for analysis, detection, alerting, and escalation. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) | X | X | |||
40 | V1 | Architecture | 1.8.1 | N/A | Verify that all sensitive data is identified and classified into protection levels. | X | X | |||
41 | V1 | Architecture | 1.8.2 | N/A | Verify that all protection levels have an associated set of protection requirements, such as encryption requirements, integrity requirements, retention, privacy and other confidentiality requirements, and that these are applied in the architecture. | X | X | |||
42 | V1 | Architecture | 1.9.1 | N/A | Verify the application encrypts communications between components, particularly when these components are in different containers, systems, sites, or cloud providers. ([C3](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering)) | X | X | 319 | ||
43 | V1 | Architecture | 1.9.2 | N/A | Verify that application components verify the authenticity of each side in a communication link to prevent person-in-the-middle attacks. For example, application components should validate TLS certificates and chains. | X | X | 295 | ||
44 | V2 | Authentication | 2.1.1 | Yes | 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 | 521 | 5.1.1.2 |
45 | V2 | Authentication | 2.1.10 | Yes | Verify that there are no periodic credential rotation or password history requirements. | X | X | X | 263 | 5.1.1.2 |
46 | V2 | Authentication | 2.1.11 | Yes | Verify that "paste" functionality, browser password helpers, and external password managers are permitted. | X | X | X | 521 | 5.1.1.2 |
47 | V2 | Authentication | 2.1.12 | No | 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 | 521 | 5.1.1.2 |
48 | V2 | Authentication | 2.1.2 | Yes | 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 | 521 | 5.1.1.2 |
49 | V2 | Authentication | 2.1.3 | Yes | 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 | 521 | 5.1.1.2 |
50 | V2 | Authentication | 2.1.4 | No | 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 | 521 | 5.1.1.2 |
51 | V2 | Authentication | 2.1.5 | Yes | Verify users can change their password. | X | X | X | 620 | 5.1.1.2 |
52 | V2 | Authentication | 2.1.6 | Yes | Verify that password change functionality requires the user's current and new password. | X | X | X | 620 | 5.1.1.2 |
53 | V2 | Authentication | 2.1.7 | Yes | 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 | 521 | 5.1.1.2 |
54 | V2 | Authentication | 2.1.8 | Verify that a password strength meter is provided to help users set a stronger password. | X | X | X | 521 | 5.1.1.2 | |
55 | V2 | Authentication | 2.1.9 | Yes | 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 | 521 | 5.1.1.2 |
56 | 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 | 287 | 5.1.1.1 | ||
57 | V2 | Authentication | 2.10.2 | Verify that if passwords are required, the credentials are not a default account. | OS assisted | HSM | 255 | 5.1.1.1 | ||
58 | 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 | 522 | 5.1.1.1 | ||
59 | 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 | 798 | |||
60 | 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 | 307 | 5.2.2 / 5.1.1.2 / 5.1.4.2 / 5.1.5.2 | |
61 | 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 | 304 | 5.2.10 | |
62 | 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 | 620 | ||
63 | 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 | 308 | 5.2.5 | |||
64 | 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 | 319 | 5.2.6 | |||
65 | V2 | Authentication | 2.2.6 | Verify replay resistance through the mandated use of OTP devices, cryptographic authenticators, or lookup codes. | X | 308 | 5.2.8 | |||
66 | 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 | 308 | 5.2.9 | |||
67 | 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 | 330 | 5.1.1.2 / A.3 | |
68 | 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 | 308 | 6.1.3 | ||
69 | V2 | Authentication | 2.3.3 | Verify that renewal instructions are sent with sufficient time to renew time bound authenticators. | X | X | 287 | 6.1.4 | ||
70 | 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 | 916 | 5.1.1.2 | ||
71 | 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 | 916 | 5.1.1.2 | ||
72 | 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 | 916 | 5.1.1.2 | ||
73 | 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 | 916 | 5.1.1.2 | ||
74 | 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 | 916 | 5.1.1.2 | ||
75 | 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 | 640 | 5.1.1.2 | |
76 | V2 | Authentication | 2.5.2 | Verify password hints or knowledge-based authentication (so-called "secret questions") are not present. | X | X | X | 640 | 5.1.1.2 | |
77 | 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 | 640 | 5.1.1.2 | |
78 | V2 | Authentication | 2.5.4 | Verify shared or default accounts are not present (e.g. "root","admin", or "sa"). | X | X | X | 16 | 5.1.1.2 / A.3 | |
79 | 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 | 304 | 6.1.2.3 | |
80 | 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 | 640 | 5.1.1.2 | |
81 | 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 | 308 | 6.1.2.3 | ||
82 | V2 | Authentication | 2.6.1 | Verify that lookup secrets can be used only once. | X | X | 308 | 5.1.2.2 | ||
83 | 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 | 330 | 5.1.2.2 | ||
84 | V2 | Authentication | 2.6.3 | Verify that lookup secrets are resistant to offline attacks, such as predictable values. | X | X | 310 | 5.1.2.2 | ||
85 | 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 | 287 | 5.1.3.2 | |
86 | 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 | 287 | 5.1.3.2 | |
87 | 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 | 287 | 5.1.3.2 | |
88 | V2 | Authentication | 2.7.4 | Verify that the out of band authenticator and verifier communicates over a secure independent channel. | X | X | X | 523 | 5.1.3.2 | |
89 | V2 | Authentication | 2.7.5 | Verify that the out of band verifier retains only a hashed version of the authentication code. | X | X | 256 | 5.1.3.2 | ||
90 | 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 | 310 | 5.1.3.2 | ||
91 | V2 | Authentication | 2.8.1 | Verify that time-based OTPs have a defined lifetime before expiring. | X | X | X | 613 | 5.1.4.2 / 5.1.5.2 | |
92 | 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 | 320 | 5.1.4.2 / 5.1.5.2 | ||
93 | V2 | Authentication | 2.8.3 | Verify that approved cryptographic algorithms are used in the generation, seeding, and verification. | X | X | 326 | 5.1.4.2 / 5.1.5.2 | ||
94 | V2 | Authentication | 2.8.4 | Verify that time-based OTP can be used only once within the validity period. | X | X | 287 | 5.1.4.2 / 5.1.5.2 | ||
95 | 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 | 287 | 5.1.5.2 | ||
96 | 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 | 613 | 5.2.1 | ||
97 | 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 | 308 | 5.2.3 | ||
98 | 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 | 320 | 5.1.7.2 | ||
99 | 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 | 330 | 5.1.7.2 | ||
100 | V2 | Authentication | 2.9.3 | Verify that approved cryptographic algorithms are used in the generation, seeding, and verification. | X | X | 327 | 5.1.7.2 | ||
101 | V3 | Session | 3.1.1 | Verify the application never reveals session tokens in URL parameters or error messages. | X | X | X | 598 | ||
102 | 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 | 384 | 7.1 | |
103 | 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 | 331 | 7.1 | |
104 | 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 | 539 | 7.1 | |
105 | 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 | 331 | 7.1 | ||
106 | 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 | 613 | 7.1 | |
107 | 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 | 613 | 7.2 | |
108 | 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 | 613 | |||
109 | 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 | 613 | 7.1 | ||
110 | 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 | 614 | 7.1.1 | |
111 | 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 | 1004 | 7.1.1 | |
112 | 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 | 16 | 7.1.1 | |
113 | V3 | Session | 3.4.4 | Verify that cookie-based session tokens use "__Host-" prefix (see references) to provide session cookie confidentiality. | X | X | X | 16 | 7.1.1 | |
114 | 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 | 16 | 7.1.1 | |
115 | V3 | Session | 3.5.1 | Verify the application does not treat OAuth and refresh tokens — on their own — as the presence of the subscriber and allows users to terminate trust relationships with linked applications. | X | X | 290 | 7.1.2 | ||
116 | V3 | Session | 3.5.2 | Verify the application uses session tokens rather than static API secrets and keys, except with legacy implementations. | X | X | 798 | |||
117 | 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 | 345 | |||
118 | 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 | 613 | 7.2.1 | |||
119 | 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 | 613 | 7.2.1 | |||
120 | 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 | 778 | ||
121 | 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 | 602 | ||
122 | 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 | 639 | ||
123 | 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 | 285 | ||
124 | 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 | 276 | ||
125 | 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 | 285 | ||
126 | 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 | 639 | ||
127 | 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 | 352 | ||
128 | V4 | Access | 4.3.1 | Verify administrative interfaces use appropriate multi-factor authentication to prevent unauthorized use. | X | X | X | 419 | ||
129 | 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 | 548 | ||
130 | 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 | 732 | |||
131 | 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 | 235 | ||
132 | 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 | 915 | ||
133 | 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 | 20 | ||
134 | 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 | 20 | ||
135 | 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 | 601 | ||
136 | 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 | 116 | ||
137 | V5 | Validation | 5.2.2 | Verify that unstructured data is sanitized to enforce safety measures such as allowed characters and length. | X | X | X | 138 | ||
138 | 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 | 147 | ||
139 | 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 | 95 | ||
140 | 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 | 94 | ||
141 | 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 | 918 | ||
142 | 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 | 159 | ||
143 | 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 | 94 | ||
144 | 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 | 116 | ||
145 | 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 | 643 | ||
146 | 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 | 176 | ||
147 | 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 | 79 | ||
148 | 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 | 89 | ||
149 | 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 | 89 | ||
150 | 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 | 830 | ||
151 | 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 | 943 | ||
152 | 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 | 78 | ||
153 | V5 | Validation | 5.3.9 | Verify that the application protects against Local File Inclusion (LFI) or Remote File Inclusion (RFI) attacks. | X | X | X | 829 | ||
154 | 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 | 120 | |||
155 | V5 | Validation | 5.4.2 | Verify that format strings do not take potentially hostile input, and are constant. | X | X | 134 | |||
156 | V5 | Validation | 5.4.3 | Verify that sign, range, and input validation techniques are used to prevent integer overflows. | X | X | 190 | |||
157 | 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 | 502 | ||
158 | 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 | 611 | ||
159 | 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 | 502 | ||
160 | 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 | 95 | ||
161 | 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 | 311 | |||
162 | 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 | 311 | |||
163 | 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 | 311 | |||
164 | 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 | 310 | ||
165 | 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 | 327 | |||
166 | V6 | Cryptography | 6.2.3 | Verify that encryption initialization vector, cipher configuration, and block modes are configured securely using the latest advice. | X | X | 326 | |||
167 | 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 | 326 | |||
168 | 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 | 326 | |||
169 | 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 | 326 | |||
170 | 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 | 326 | ||||
171 | 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 | 385 | ||||
172 | 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 | 338 | |||
173 | 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 | 338 | |||
174 | 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 | 338 | ||||
175 | 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 | 798 | |||
176 | 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 | 320 | |||
177 | 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 | 532 | ||
178 | 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 | 532 | ||
179 | 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 | 778 | |||
180 | 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 | 778 | |||
181 | 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 | 778 | |||
182 | 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 | 285 | |||
183 | 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 | 117 | |||
184 | 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 | 117 | |||
185 | 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 | 200 | |||
186 | 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 | ||||
187 | 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 | 210 | ||
188 | 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 | 544 | |||
189 | 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 | 460 | |||
190 | 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 | 524 | |||
191 | 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 | 524 | |||
192 | 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 | 233 | |||
193 | 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 | 770 | |||
194 | V8 | Data | 8.1.5 | Verify that regular backups of important data are performed and that test restoration of data is performed. | X | 19 | ||||
195 | V8 | Data | 8.1.6 | Verify that backups are stored securely to prevent data from being stolen or corrupted. | X | 19 | ||||
196 | 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 | 525 | ||
197 | 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 | 922 | ||
198 | 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 | 922 | ||
199 | 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 | 319 | ||
200 | V8 | Data | 8.3.2 | Verify that users have a method to remove or export their data on demand. | X | X | X | 212 | ||
201 | 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 | 285 | ||
202 | 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 | 200 |