@cyclonedx/cdxgen
Version:
Creates CycloneDX Software Bill of Materials (SBOM) from source or container image
1,021 lines (1,020 loc) • 127 kB
JSON
{
"metadata": {
"licenses": [
{
"license": {
"id": "CC-BY-SA-4.0",
"url": "https://creativecommons.org/licenses/by-sa/4.0/legalcode.txt"
}
}
]
},
"definitions": {
"standards": [
{
"bom-ref": "ASVS-4.0.3",
"name": "Application Security Verification Standard (ASVS)",
"version": "4.0.3",
"description": "The Application Security Verification Standard is a list of application security requirements or tests that can be used by architects, developers, testers, security professionals, tool vendors, and consumers to define, build, test and verify secure applications.",
"owner": "Application Security Verification Standard Project",
"requirements": [
{
"bom-ref": "V1",
"identifier": "V1",
"title": "Architecture, Design and Threat Modeling"
},
{
"bom-ref": "V1.1",
"identifier": "V1.1",
"title": "Secure Software Development Lifecycle",
"parent": "V1"
},
{
"bom-ref": "V1.1.1",
"identifier": "V1.1.1",
"text": "Verify the use of a secure software development lifecycle that addresses security in all stages of development. ([C1](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V1.1"
},
{
"bom-ref": "V1.1.2",
"identifier": "V1.1.2",
"text": "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.",
"parent": "V1.1"
},
{
"bom-ref": "V1.1.3",
"identifier": "V1.1.3",
"text": "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\"",
"parent": "V1.1"
},
{
"bom-ref": "V1.1.4",
"identifier": "V1.1.4",
"text": "Verify documentation and justification of all the application's trust boundaries, components, and significant data flows.",
"parent": "V1.1"
},
{
"bom-ref": "V1.1.5",
"identifier": "V1.1.5",
"text": "Verify definition and security analysis of the application's high-level architecture and all connected remote services. ([C1](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V1.1"
},
{
"bom-ref": "V1.1.6",
"identifier": "V1.1.6",
"text": "Verify implementation of centralized, simple (economy of design), vetted, secure, and reusable security controls to avoid duplicate, missing, ineffective, or insecure controls. ([C10](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V1.1"
},
{
"bom-ref": "V1.1.7",
"identifier": "V1.1.7",
"text": "Verify availability of a secure coding checklist, security requirements, guideline, or policy to all developers and testers.",
"parent": "V1.1"
},
{
"bom-ref": "V1.2",
"identifier": "V1.2",
"title": "Authentication Architecture",
"parent": "V1"
},
{
"bom-ref": "V1.2.1",
"identifier": "V1.2.1",
"text": "Verify the use of unique or special low-privilege operating system accounts for all application components, services, and servers. ([C3](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V1.2"
},
{
"bom-ref": "V1.2.2",
"identifier": "V1.2.2",
"text": "Verify that communications between application components, including APIs, middleware and data layers, are authenticated. Components should have the least necessary privileges needed. ([C3](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V1.2"
},
{
"bom-ref": "V1.2.3",
"identifier": "V1.2.3",
"text": "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.",
"parent": "V1.2"
},
{
"bom-ref": "V1.2.4",
"identifier": "V1.2.4",
"text": "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.",
"parent": "V1.2"
},
{
"bom-ref": "V1.3",
"identifier": "V1.3",
"title": "Session Management Architecture",
"parent": "V1"
},
{
"bom-ref": "V1.4",
"identifier": "V1.4",
"title": "Access Control Architecture",
"parent": "V1"
},
{
"bom-ref": "V1.4.1",
"identifier": "V1.4.1",
"text": "Verify that trusted enforcement points, such as access control gateways, servers, and serverless functions, enforce access controls. Never enforce access controls on the client.",
"parent": "V1.4"
},
{
"bom-ref": "V1.4.2",
"identifier": "V1.4.2",
"text": "[DELETED, NOT ACTIONABLE]",
"parent": "V1.4"
},
{
"bom-ref": "V1.4.3",
"identifier": "V1.4.3",
"text": "[DELETED, DUPLICATE OF 4.1.3]",
"parent": "V1.4"
},
{
"bom-ref": "V1.4.4",
"identifier": "V1.4.4",
"text": "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://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V1.4"
},
{
"bom-ref": "V1.4.5",
"identifier": "V1.4.5",
"text": "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://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V1.4"
},
{
"bom-ref": "V1.5",
"identifier": "V1.5",
"title": "Input and Output Architecture",
"parent": "V1"
},
{
"bom-ref": "V1.5.1",
"identifier": "V1.5.1",
"text": "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.",
"parent": "V1.5"
},
{
"bom-ref": "V1.5.2",
"identifier": "V1.5.2",
"text": "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.",
"parent": "V1.5"
},
{
"bom-ref": "V1.5.3",
"identifier": "V1.5.3",
"text": "Verify that input validation is enforced on a trusted service layer. ([C5](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V1.5"
},
{
"bom-ref": "V1.5.4",
"identifier": "V1.5.4",
"text": "Verify that output encoding occurs close to or by the interpreter for which it is intended. ([C4](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V1.5"
},
{
"bom-ref": "V1.6",
"identifier": "V1.6",
"title": "Cryptographic Architecture",
"parent": "V1"
},
{
"bom-ref": "V1.6.1",
"identifier": "V1.6.1",
"text": "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.",
"parent": "V1.6"
},
{
"bom-ref": "V1.6.2",
"identifier": "V1.6.2",
"text": "Verify that consumers of cryptographic services protect key material and other secrets by using key vaults or API based alternatives.",
"parent": "V1.6"
},
{
"bom-ref": "V1.6.3",
"identifier": "V1.6.3",
"text": "Verify that all keys and passwords are replaceable and are part of a well-defined process to re-encrypt sensitive data.",
"parent": "V1.6"
},
{
"bom-ref": "V1.6.4",
"identifier": "V1.6.4",
"text": "Verify that the architecture treats client-side secrets--such as symmetric keys, passwords, or API tokens--as insecure and never uses them to protect or access sensitive data.",
"parent": "V1.6"
},
{
"bom-ref": "V1.7",
"identifier": "V1.7",
"title": "Errors, Logging and Auditing Architecture",
"parent": "V1"
},
{
"bom-ref": "V1.7.1",
"identifier": "V1.7.1",
"text": "Verify that a common logging format and approach is used across the system. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V1.7"
},
{
"bom-ref": "V1.7.2",
"identifier": "V1.7.2",
"text": "Verify that logs are securely transmitted to a preferably remote system for analysis, detection, alerting, and escalation. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V1.7"
},
{
"bom-ref": "V1.8",
"identifier": "V1.8",
"title": "Data Protection and Privacy Architecture",
"parent": "V1"
},
{
"bom-ref": "V1.8.1",
"identifier": "V1.8.1",
"text": "Verify that all sensitive data is identified and classified into protection levels.",
"parent": "V1.8"
},
{
"bom-ref": "V1.8.2",
"identifier": "V1.8.2",
"text": "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.",
"parent": "V1.8"
},
{
"bom-ref": "V1.9",
"identifier": "V1.9",
"title": "Communications Architecture",
"parent": "V1"
},
{
"bom-ref": "V1.9.1",
"identifier": "V1.9.1",
"text": "Verify the application encrypts communications between components, particularly when these components are in different containers, systems, sites, or cloud providers. ([C3](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V1.9"
},
{
"bom-ref": "V1.9.2",
"identifier": "V1.9.2",
"text": "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.",
"parent": "V1.9"
},
{
"bom-ref": "V1.10",
"identifier": "V1.10",
"title": "Malicious Software Architecture",
"parent": "V1"
},
{
"bom-ref": "V1.10.1",
"identifier": "V1.10.1",
"text": "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.",
"parent": "V1.10"
},
{
"bom-ref": "V1.11",
"identifier": "V1.11",
"title": "Business Logic Architecture",
"parent": "V1"
},
{
"bom-ref": "V1.11.1",
"identifier": "V1.11.1",
"text": "Verify the definition and documentation of all application components in terms of the business or security functions they provide.",
"parent": "V1.11"
},
{
"bom-ref": "V1.11.2",
"identifier": "V1.11.2",
"text": "Verify that all high-value business logic flows, including authentication, session management and access control, do not share unsynchronized state.",
"parent": "V1.11"
},
{
"bom-ref": "V1.11.3",
"identifier": "V1.11.3",
"text": "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.",
"parent": "V1.11"
},
{
"bom-ref": "V1.12",
"identifier": "V1.12",
"title": "Secure File Upload Architecture",
"parent": "V1"
},
{
"bom-ref": "V1.12.1",
"identifier": "V1.12.1",
"text": "[DELETED, DUPLICATE OF 12.4.1]",
"parent": "V1.12"
},
{
"bom-ref": "V1.12.2",
"identifier": "V1.12.2",
"text": "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 (CSP) to reduce the risk from XSS vectors or other attacks from the uploaded file.",
"parent": "V1.12"
},
{
"bom-ref": "V1.13",
"identifier": "V1.13",
"title": "API Architecture",
"parent": "V1"
},
{
"bom-ref": "V1.14",
"identifier": "V1.14",
"title": "Configuration Architecture",
"parent": "V1"
},
{
"bom-ref": "V1.14.1",
"identifier": "V1.14.1",
"text": "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.",
"parent": "V1.14"
},
{
"bom-ref": "V1.14.2",
"identifier": "V1.14.2",
"text": "Verify that binary signatures, trusted connections, and verified endpoints are used to deploy binaries to remote devices.",
"parent": "V1.14"
},
{
"bom-ref": "V1.14.3",
"identifier": "V1.14.3",
"text": "Verify that the build pipeline warns of out-of-date or insecure components and takes appropriate actions.",
"parent": "V1.14"
},
{
"bom-ref": "V1.14.4",
"identifier": "V1.14.4",
"text": "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.",
"parent": "V1.14"
},
{
"bom-ref": "V1.14.5",
"identifier": "V1.14.5",
"text": "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://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V1.14"
},
{
"bom-ref": "V1.14.6",
"identifier": "V1.14.6",
"text": "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.",
"parent": "V1.14"
},
{
"bom-ref": "V2",
"identifier": "V2",
"title": "Authentication"
},
{
"bom-ref": "V2.1",
"identifier": "V2.1",
"title": "Password Security",
"parent": "V2"
},
{
"bom-ref": "V2.1.1",
"identifier": "V2.1.1",
"text": "Verify that user set passwords are at least 12 characters in length (after multiple spaces are combined). ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V2.1"
},
{
"bom-ref": "V2.1.2",
"identifier": "V2.1.2",
"text": "Verify that passwords of at least 64 characters are permitted, and that passwords of more than 128 characters are denied. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V2.1"
},
{
"bom-ref": "V2.1.3",
"identifier": "V2.1.3",
"text": "Verify that password truncation is not performed. However, consecutive multiple spaces may be replaced by a single space. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V2.1"
},
{
"bom-ref": "V2.1.4",
"identifier": "V2.1.4",
"text": "Verify that any printable Unicode character, including language neutral characters such as spaces and Emojis are permitted in passwords.",
"parent": "V2.1"
},
{
"bom-ref": "V2.1.5",
"identifier": "V2.1.5",
"text": "Verify users can change their password.",
"parent": "V2.1"
},
{
"bom-ref": "V2.1.6",
"identifier": "V2.1.6",
"text": "Verify that password change functionality requires the user's current and new password.",
"parent": "V2.1"
},
{
"bom-ref": "V2.1.7",
"identifier": "V2.1.7",
"text": "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://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V2.1"
},
{
"bom-ref": "V2.1.8",
"identifier": "V2.1.8",
"text": "Verify that a password strength meter is provided to help users set a stronger password.",
"parent": "V2.1"
},
{
"bom-ref": "V2.1.9",
"identifier": "V2.1.9",
"text": "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://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V2.1"
},
{
"bom-ref": "V2.1.10",
"identifier": "V2.1.10",
"text": "Verify that there are no periodic credential rotation or password history requirements.",
"parent": "V2.1"
},
{
"bom-ref": "V2.1.11",
"identifier": "V2.1.11",
"text": "Verify that \"paste\" functionality, browser password helpers, and external password managers are permitted.",
"parent": "V2.1"
},
{
"bom-ref": "V2.1.12",
"identifier": "V2.1.12",
"text": "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 built-in functionality.",
"parent": "V2.1"
},
{
"bom-ref": "V2.2",
"identifier": "V2.2",
"title": "General Authenticator Security",
"parent": "V2"
},
{
"bom-ref": "V2.2.1",
"identifier": "V2.2.1",
"text": "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.",
"parent": "V2.2"
},
{
"bom-ref": "V2.2.2",
"identifier": "V2.2.2",
"text": "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.",
"parent": "V2.2"
},
{
"bom-ref": "V2.2.3",
"identifier": "V2.2.3",
"text": "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.",
"parent": "V2.2"
},
{
"bom-ref": "V2.2.4",
"identifier": "V2.2.4",
"text": "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.",
"parent": "V2.2"
},
{
"bom-ref": "V2.2.5",
"identifier": "V2.2.5",
"text": "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.",
"parent": "V2.2"
},
{
"bom-ref": "V2.2.6",
"identifier": "V2.2.6",
"text": "Verify replay resistance through the mandated use of One-time Passwords (OTP) devices, cryptographic authenticators, or lookup codes.",
"parent": "V2.2"
},
{
"bom-ref": "V2.2.7",
"identifier": "V2.2.7",
"text": "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.",
"parent": "V2.2"
},
{
"bom-ref": "V2.3",
"identifier": "V2.3",
"title": "Authenticator Lifecycle",
"parent": "V2"
},
{
"bom-ref": "V2.3.1",
"identifier": "V2.3.1",
"text": "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.",
"parent": "V2.3"
},
{
"bom-ref": "V2.3.2",
"identifier": "V2.3.2",
"text": "Verify that enrollment and use of user-provided authentication devices are supported, such as a U2F or FIDO tokens.",
"parent": "V2.3"
},
{
"bom-ref": "V2.3.3",
"identifier": "V2.3.3",
"text": "Verify that renewal instructions are sent with sufficient time to renew time bound authenticators.",
"parent": "V2.3"
},
{
"bom-ref": "V2.4",
"identifier": "V2.4",
"title": "Credential Storage",
"parent": "V2"
},
{
"bom-ref": "V2.4.1",
"identifier": "V2.4.1",
"text": "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://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V2.4"
},
{
"bom-ref": "V2.4.2",
"identifier": "V2.4.2",
"text": "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://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V2.4"
},
{
"bom-ref": "V2.4.3",
"identifier": "V2.4.3",
"text": "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://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V2.4"
},
{
"bom-ref": "V2.4.4",
"identifier": "V2.4.4",
"text": "Verify that if bcrypt is used, the work factor SHOULD be as large as verification server performance will allow, with a minimum of 10. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V2.4"
},
{
"bom-ref": "V2.4.5",
"identifier": "V2.4.5",
"text": "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).",
"parent": "V2.4"
},
{
"bom-ref": "V2.5",
"identifier": "V2.5",
"title": "Credential Recovery",
"parent": "V2"
},
{
"bom-ref": "V2.5.1",
"identifier": "V2.5.1",
"text": "Verify that a system generated initial activation or recovery secret is not sent in clear text to the user. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V2.5"
},
{
"bom-ref": "V2.5.2",
"identifier": "V2.5.2",
"text": "Verify password hints or knowledge-based authentication (so-called \"secret questions\") are not present.",
"parent": "V2.5"
},
{
"bom-ref": "V2.5.3",
"identifier": "V2.5.3",
"text": "Verify password credential recovery does not reveal the current password in any way. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V2.5"
},
{
"bom-ref": "V2.5.4",
"identifier": "V2.5.4",
"text": "Verify shared or default accounts are not present (e.g. \"root\", \"admin\", or \"sa\").",
"parent": "V2.5"
},
{
"bom-ref": "V2.5.5",
"identifier": "V2.5.5",
"text": "Verify that if an authentication factor is changed or replaced, that the user is notified of this event.",
"parent": "V2.5"
},
{
"bom-ref": "V2.5.6",
"identifier": "V2.5.6",
"text": "Verify forgotten password, and other recovery paths use a secure recovery mechanism, such as time-based OTP (TOTP) or other soft token, mobile push, or another offline recovery mechanism. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V2.5"
},
{
"bom-ref": "V2.5.7",
"identifier": "V2.5.7",
"text": "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.",
"parent": "V2.5"
},
{
"bom-ref": "V2.6",
"identifier": "V2.6",
"title": "Look-up Secret Verifier",
"parent": "V2"
},
{
"bom-ref": "V2.6.1",
"identifier": "V2.6.1",
"text": "Verify that lookup secrets can be used only once.",
"parent": "V2.6"
},
{
"bom-ref": "V2.6.2",
"identifier": "V2.6.2",
"text": "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.",
"parent": "V2.6"
},
{
"bom-ref": "V2.6.3",
"identifier": "V2.6.3",
"text": "Verify that lookup secrets are resistant to offline attacks, such as predictable values.",
"parent": "V2.6"
},
{
"bom-ref": "V2.7",
"identifier": "V2.7",
"title": "Out of Band Verifier",
"parent": "V2"
},
{
"bom-ref": "V2.7.1",
"identifier": "V2.7.1",
"text": "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.",
"parent": "V2.7"
},
{
"bom-ref": "V2.7.2",
"identifier": "V2.7.2",
"text": "Verify that the out of band verifier expires out of band authentication requests, codes, or tokens after 10 minutes.",
"parent": "V2.7"
},
{
"bom-ref": "V2.7.3",
"identifier": "V2.7.3",
"text": "Verify that the out of band verifier authentication requests, codes, or tokens are only usable once, and only for the original authentication request.",
"parent": "V2.7"
},
{
"bom-ref": "V2.7.4",
"identifier": "V2.7.4",
"text": "Verify that the out of band authenticator and verifier communicates over a secure independent channel.",
"parent": "V2.7"
},
{
"bom-ref": "V2.7.5",
"identifier": "V2.7.5",
"text": "Verify that the out of band verifier retains only a hashed version of the authentication code.",
"parent": "V2.7"
},
{
"bom-ref": "V2.7.6",
"identifier": "V2.7.6",
"text": "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).",
"parent": "V2.7"
},
{
"bom-ref": "V2.8",
"identifier": "V2.8",
"title": "One Time Verifier",
"parent": "V2"
},
{
"bom-ref": "V2.8.1",
"identifier": "V2.8.1",
"text": "Verify that time-based OTPs have a defined lifetime before expiring.",
"parent": "V2.8"
},
{
"bom-ref": "V2.8.2",
"identifier": "V2.8.2",
"text": "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.",
"parent": "V2.8"
},
{
"bom-ref": "V2.8.3",
"identifier": "V2.8.3",
"text": "Verify that approved cryptographic algorithms are used in the generation, seeding, and verification of OTPs.",
"parent": "V2.8"
},
{
"bom-ref": "V2.8.4",
"identifier": "V2.8.4",
"text": "Verify that time-based OTP can be used only once within the validity period.",
"parent": "V2.8"
},
{
"bom-ref": "V2.8.5",
"identifier": "V2.8.5",
"text": "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.",
"parent": "V2.8"
},
{
"bom-ref": "V2.8.6",
"identifier": "V2.8.6",
"text": "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.",
"parent": "V2.8"
},
{
"bom-ref": "V2.8.7",
"identifier": "V2.8.7",
"text": "Verify that biometric authenticators are limited to use only as secondary factors in conjunction with either something you have and something you know.",
"parent": "V2.8"
},
{
"bom-ref": "V2.9",
"identifier": "V2.9",
"title": "Cryptographic Verifier",
"parent": "V2"
},
{
"bom-ref": "V2.9.1",
"identifier": "V2.9.1",
"text": "Verify that cryptographic keys used in verification are stored securely and protected against disclosure, such as using a Trusted Platform Module (TPM) or Hardware Security Module (HSM), or an OS service that can use this secure storage.",
"parent": "V2.9"
},
{
"bom-ref": "V2.9.2",
"identifier": "V2.9.2",
"text": "Verify that the challenge nonce is at least 64 bits in length, and statistically unique or unique over the lifetime of the cryptographic device.",
"parent": "V2.9"
},
{
"bom-ref": "V2.9.3",
"identifier": "V2.9.3",
"text": "Verify that approved cryptographic algorithms are used in the generation, seeding, and verification.",
"parent": "V2.9"
},
{
"bom-ref": "V2.10",
"identifier": "V2.10",
"title": "Service Authentication",
"parent": "V2"
},
{
"bom-ref": "V2.10.1",
"identifier": "V2.10.1",
"text": "Verify that intra-service secrets do not rely on unchanging credentials such as passwords, API keys or shared accounts with privileged access.",
"parent": "V2.10"
},
{
"bom-ref": "V2.10.2",
"identifier": "V2.10.2",
"text": "Verify that if passwords are required for service authentication, the service account used is not a default credential. (e.g. root/root or admin/admin are default in some services during installation).",
"parent": "V2.10"
},
{
"bom-ref": "V2.10.3",
"identifier": "V2.10.3",
"text": "Verify that passwords are stored with sufficient protection to prevent offline recovery attacks, including local system access.",
"parent": "V2.10"
},
{
"bom-ref": "V2.10.4",
"identifier": "V2.10.4",
"text": "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 TPM, or an HSM (L3) is recommended for password storage.",
"parent": "V2.10"
},
{
"bom-ref": "V3",
"identifier": "V3",
"title": "Session Management"
},
{
"bom-ref": "V3.1",
"identifier": "V3.1",
"title": "Fundamental Session Management Security",
"parent": "V3"
},
{
"bom-ref": "V3.1.1",
"identifier": "V3.1.1",
"text": "Verify the application never reveals session tokens in URL parameters.",
"parent": "V3.1"
},
{
"bom-ref": "V3.2",
"identifier": "V3.2",
"title": "Session Binding",
"parent": "V3"
},
{
"bom-ref": "V3.2.1",
"identifier": "V3.2.1",
"text": "Verify the application generates a new session token on user authentication. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V3.2"
},
{
"bom-ref": "V3.2.2",
"identifier": "V3.2.2",
"text": "Verify that session tokens possess at least 64 bits of entropy. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V3.2"
},
{
"bom-ref": "V3.2.3",
"identifier": "V3.2.3",
"text": "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.",
"parent": "V3.2"
},
{
"bom-ref": "V3.2.4",
"identifier": "V3.2.4",
"text": "Verify that session tokens are generated using approved cryptographic algorithms. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V3.2"
},
{
"bom-ref": "V3.3",
"identifier": "V3.3",
"title": "Session Termination",
"parent": "V3"
},
{
"bom-ref": "V3.3.1",
"identifier": "V3.3.1",
"text": "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://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V3.3"
},
{
"bom-ref": "V3.3.2",
"identifier": "V3.3.2",
"text": "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://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V3.3"
},
{
"bom-ref": "V3.3.3",
"identifier": "V3.3.3",
"text": "Verify that the application gives the option to terminate all other active sessions after a successful password change (including change via password reset/recovery), and that this is effective across the application, federated login (if present), and any relying parties.",
"parent": "V3.3"
},
{
"bom-ref": "V3.3.4",
"identifier": "V3.3.4",
"text": "Verify that users are able to view and (having re-entered login credentials) log out of any or all currently active sessions and devices.",
"parent": "V3.3"
},
{
"bom-ref": "V3.4",
"identifier": "V3.4",
"title": "Cookie-based Session Management",
"parent": "V3"
},
{
"bom-ref": "V3.4.1",
"identifier": "V3.4.1",
"text": "Verify that cookie-based session tokens have the 'Secure' attribute set. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V3.4"
},
{
"bom-ref": "V3.4.2",
"identifier": "V3.4.2",
"text": "Verify that cookie-based session tokens have the 'HttpOnly' attribute set. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V3.4"
},
{
"bom-ref": "V3.4.3",
"identifier": "V3.4.3",
"text": "Verify that cookie-based session tokens utilize the 'SameSite' attribute to limit exposure to cross-site request forgery attacks. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V3.4"
},
{
"bom-ref": "V3.4.4",
"identifier": "V3.4.4",
"text": "Verify that cookie-based session tokens use the \"__Host-\" prefix so cookies are only sent to the host that initially set the cookie.",
"parent": "V3.4"
},
{
"bom-ref": "V3.4.5",
"identifier": "V3.4.5",
"text": "Verify that if the application is published under a domain name with other applications that set or use session cookies that might disclose the session cookies, set the path attribute in cookie-based session tokens using the most precise path possible. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V3.4"
},
{
"bom-ref": "V3.5",
"identifier": "V3.5",
"title": "Token-based Session Management",
"parent": "V3"
},
{
"bom-ref": "V3.5.1",
"identifier": "V3.5.1",
"text": "Verify the application allows users to revoke OAuth tokens that form trust relationships with linked applications.",
"parent": "V3.5"
},
{
"bom-ref": "V3.5.2",
"identifier": "V3.5.2",
"text": "Verify the application uses session tokens rather than static API secrets and keys, except with legacy implementations.",
"parent": "V3.5"
},
{
"bom-ref": "V3.5.3",
"identifier": "V3.5.3",
"text": "Verify that stateless session tokens use digital signatures, encryption, and other countermeasures to protect against tampering, enveloping, replay, null cipher, and key substitution attacks.",
"parent": "V3.5"
},
{
"bom-ref": "V3.6",
"identifier": "V3.6",
"title": "Federated Re-authentication",
"parent": "V3"
},
{
"bom-ref": "V3.6.1",
"identifier": "V3.6.1",
"text": "Verify that Relying Parties (RPs) specify the maximum authentication time to Credential Service Providers (CSPs) and that CSPs re-authenticate the user if they haven't used a session within that period.",
"parent": "V3.6"
},
{
"bom-ref": "V3.6.2",
"identifier": "V3.6.2",
"text": "Verify that Credential Service Providers (CSPs) inform Relying Parties (RPs) of the last authentication event, to allow RPs to determine if they need to re-authenticate the user.",
"parent": "V3.6"
},
{
"bom-ref": "V3.7",
"identifier": "V3.7",
"title": "Defenses Against Session Management Exploits",
"parent": "V3"
},
{
"bom-ref": "V3.7.1",
"identifier": "V3.7.1",
"text": "Verify the application ensures a full, valid login session or requires re-authentication or secondary verification before allowing any sensitive transactions or account modifications.",
"parent": "V3.7"
},
{
"bom-ref": "V4",
"identifier": "V4",
"title": "Access Control"
},
{
"bom-ref": "V4.1",
"identifier": "V4.1",
"title": "General Access Control Design",
"parent": "V4"
},
{
"bom-ref": "V4.1.1",
"identifier": "V4.1.1",
"text": "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.",
"parent": "V4.1"
},
{
"bom-ref": "V4.1.2",
"identifier": "V4.1.2",
"text": "Verify that all user and data attributes and policy information used by access controls cannot be manipulated by end users unless specifically authorized.",
"parent": "V4.1"
},
{
"bom-ref": "V4.1.3",
"identifier": "V4.1.3",
"text": "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://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V4.1"
},
{
"bom-ref": "V4.1.4",
"identifier": "V4.1.4",
"text": "[DELETED, DUPLICATE OF 4.1.3]",
"parent": "V4.1"
},
{
"bom-ref": "V4.1.5",
"identifier": "V4.1.5",
"text": "Verify that access controls fail securely including when an exception occurs. ([C10](https://owasp.org/www-project-proactive-controls/#div-numbering))",
"parent": "V4.1"
},
{
"bom-ref": "V4.2",
"identifier": "V4.2",
"title": "Operation Level Access Control",
"parent": "V4"
},
{
"bom-ref": "V4.2.1",
"identifier": "V4.2.1",
"text": "Verify that sensitive data and APIs are protected against Insecure Direct Object Reference (IDOR) 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.",
"parent": "V4.2"
},
{
"bom-ref": "V4.2.2",
"identifier": "V4.2.2",
"text": "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.",
"parent": "V4.2"
},
{
"bom-ref": "V4.3",
"identifier": "V4.3",
"title": "Other Access Control Considerations",
"parent": "V4"
},
{
"bom-ref": "V4.3.1",
"identifier": "V4.3.1",
"text": "Verify administrative interfaces use appropriate multi-factor authentication to prevent unauthorized use.",
"parent": "V4.3"
},
{
"bom-ref": "V4.3.2",
"identifier": "V4.3.2",
"text": "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.",
"parent": "V4.3"
},
{
"bom-ref": "V4.3.3",
"identifier": "V4.3.3",
"text": "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.",
"parent": "V4.3"
},
{
"bom-ref": "V5",