diff --git a/README.md b/README.md
index 53dbb8250..31c99be5f 100644
--- a/README.md
+++ b/README.md
@@ -156,8 +156,8 @@ Options:
       --standard               The list of standards which may consist of regulations, industry or organizational-specif
                                ic standards, maturity models, best practices, or any other requirements which can be eva
                                luated against or attested to.
-  [array] [choices: "asvs-4.0.3", "bsimm-v13", "masvs-2.0.0", "nist_ssdf-1.1", "pcissc-secure-slc-1.1", "scvs-1.0.0", "s
-                                                                                                     saf-DRAFT-2023-11"]
+  [array] [choices: "asvs-5.0", "asvs-4.0.3", "bsimm-v13", "masvs-2.0.0", "nist_ssdf-1.1", "pcissc-secure-slc-1.1", "scv
+                                                                                         s-1.0.0", "ssaf-DRAFT-2023-11"]
       --min-confidence         Minimum confidence needed for the identity of a component from 0 - 1, where 1 is 100% con
                                fidence.                                                            [number] [default: 0]
       --technique              Analysis technique to use
diff --git a/bin/cdxgen.js b/bin/cdxgen.js
index 4fc71d1cd..83fdad5b2 100755
--- a/bin/cdxgen.js
+++ b/bin/cdxgen.js
@@ -276,6 +276,7 @@ const args = yargs(hideBin(process.argv))
     description:
       "The list of standards which may consist of regulations, industry or organizational-specific standards, maturity models, best practices, or any other requirements which can be evaluated against or attested to.",
     choices: [
+      "asvs-5.0",
       "asvs-4.0.3",
       "bsimm-v13",
       "masvs-2.0.0",
diff --git a/data/templates/asvs-5.0.cdx.json b/data/templates/asvs-5.0.cdx.json
new file mode 100644
index 000000000..7b4bc13f0
--- /dev/null
+++ b/data/templates/asvs-5.0.cdx.json
@@ -0,0 +1,4790 @@
+{
+  "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-5.0",
+        "name": "Application Security Verification Standard (ASVS)",
+        "version": "5.0",
+        "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": "Security Decision Documentation"
+          },
+          {
+            "bom-ref": "V1.1",
+            "identifier": "V1.1",
+            "title": "Secure Software Development Lifecycle",
+            "parent": "V1"
+          },
+          {
+            "bom-ref": "V1.1.1",
+            "identifier": "V1.1.1",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V1.1"
+          },
+          {
+            "bom-ref": "V1.1.2",
+            "identifier": "V1.1.2",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V1.1"
+          },
+          {
+            "bom-ref": "V1.1.3",
+            "identifier": "V1.1.3",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V1.1"
+          },
+          {
+            "bom-ref": "V1.1.4",
+            "identifier": "V1.1.4",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V1.1"
+          },
+          {
+            "bom-ref": "V1.1.5",
+            "identifier": "V1.1.5",
+            "text": "[MOVED TO 1.14.7]",
+            "parent": "V1.1"
+          },
+          {
+            "bom-ref": "V1.1.6",
+            "identifier": "V1.1.6",
+            "text": "[DELETED, INSUFFICIENT IMPACT]",
+            "parent": "V1.1"
+          },
+          {
+            "bom-ref": "V1.1.7",
+            "identifier": "V1.1.7",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V1.1"
+          },
+          {
+            "bom-ref": "V2",
+            "identifier": "V2",
+            "title": "Authentication"
+          },
+          {
+            "bom-ref": "V1.2",
+            "identifier": "V1.2",
+            "title": "Authentication Documentation",
+            "parent": "V2"
+          },
+          {
+            "bom-ref": "V1.2.1",
+            "identifier": "V1.2.1",
+            "text": "[MOVED TO 14.6.2]",
+            "parent": "V1.2"
+          },
+          {
+            "bom-ref": "V1.2.2",
+            "identifier": "V1.2.2",
+            "text": "[DELETED, MERGED TO 14.7.1]",
+            "parent": "V1.2"
+          },
+          {
+            "bom-ref": "V1.2.3",
+            "identifier": "V1.2.3",
+            "text": "[DELETED, DUPLICATE OF 1.2.4]",
+            "parent": "V1.2"
+          },
+          {
+            "bom-ref": "V1.2.4",
+            "identifier": "V1.2.4",
+            "text": "[MODIFIED, SPLIT TO 2.2.11] Verify that, if the application includes multiple authentication pathways, these are all documented together with the security controls and authentication strength which should be consistently enforced across them.",
+            "parent": "V1.2"
+          },
+          {
+            "bom-ref": "V1.2.5",
+            "identifier": "V1.2.5",
+            "text": "[ADDED] Verify that a list of context specific words are documented in order to prevent their use in passwords.",
+            "parent": "V1.2"
+          },
+          {
+            "bom-ref": "V1.2.6",
+            "identifier": "V1.2.6",
+            "text": "[ADDED, SPLIT FROM 2.2.1] Verify that application documentation defines how controls such as rate limiting, anti-automation, and adaptive response, are used to defend against attacks such as credential stuffing and password brute force. The documentation should make clear how these controls are configured and prevent malicious account lockout.",
+            "parent": "V1.2"
+          },
+          {
+            "bom-ref": "V2.1",
+            "identifier": "V2.1",
+            "title": "Password Security",
+            "parent": "V2"
+          },
+          {
+            "bom-ref": "V2.1.1",
+            "identifier": "V2.1.1",
+            "text": "[MODIFIED] Verify that user set passwords are at least 8 characters in length although a minimum of 15 characters is strongly recommended.",
+            "parent": "V2.1"
+          },
+          {
+            "bom-ref": "V2.1.2",
+            "identifier": "V2.1.2",
+            "text": "[MODIFIED] Verify that passwords of at least 64 characters are permitted.",
+            "parent": "V2.1"
+          },
+          {
+            "bom-ref": "V2.1.3",
+            "identifier": "V2.1.3",
+            "text": "[MODIFIED] Verify that the application verifies the user's password exactly as received from the user, without any modifications such as truncation or case transformation.",
+            "parent": "V2.1"
+          },
+          {
+            "bom-ref": "V2.1.4",
+            "identifier": "V2.1.4",
+            "text": "[DELETED, INSUFFICIENT IMPACT]",
+            "parent": "V2.1"
+          },
+          {
+            "bom-ref": "V2.1.5",
+            "identifier": "V2.1.5",
+            "text": "[GRAMMAR] Verify that 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": "[MODIFIED, SPLIT TO 2.1.13] Verify that passwords submitted during account registration or password change are checked against an available set of, at least, the top 3000 passwords.",
+            "parent": "V2.1"
+          },
+          {
+            "bom-ref": "V2.1.8",
+            "identifier": "V2.1.8",
+            "text": "[DELETED, INSUFFICIENT IMPACT]",
+            "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.",
+            "parent": "V2.1"
+          },
+          {
+            "bom-ref": "V2.1.10",
+            "identifier": "V2.1.10",
+            "text": "[MODIFIED, LEVEL L1 > L2] Verify that a user's password stays valid until it is discovered to be compromised or the user rotates it. The application must not require periodic credential rotation.",
+            "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": "[MODIFIED] Verify that password input fields use type=password to mask the entry. Applications may allow the user to temporarily view the entire masked password, or the last typed character of the password.",
+            "parent": "V2.1"
+          },
+          {
+            "bom-ref": "V2.1.13",
+            "identifier": "V2.1.13",
+            "text": "[ADDED, SPLIT FROM 2.1.7, LEVEL L1 > L3] Verify that passwords submitted during account registration or password changes are checked against a set of breached passwords.",
+            "parent": "V2.1"
+          },
+          {
+            "bom-ref": "V2.1.14",
+            "identifier": "V2.1.14",
+            "text": "[ADDED] Verify that the documented list of context specific words is used to prevent easy to guess passwords being created.",
+            "parent": "V2.1"
+          },
+          {
+            "bom-ref": "V2.2",
+            "identifier": "V2.2",
+            "title": "General Authentication Security",
+            "parent": "V2"
+          },
+          {
+            "bom-ref": "V2.2.1",
+            "identifier": "V2.2.1",
+            "text": "[MODIFIED, SPLIT TO 1.2.6] Verify that controls to prevent attacks such as credential stuffing and password brute force are implemented according to the application's security documentation.",
+            "parent": "V2.2"
+          },
+          {
+            "bom-ref": "V2.2.2",
+            "identifier": "V2.2.2",
+            "text": "[MODIFIED] Verify that email is not used as either a single-factor or multi-factor authentication mechanism.",
+            "parent": "V2.2"
+          },
+          {
+            "bom-ref": "V2.2.3",
+            "identifier": "V2.2.3",
+            "text": "[MODIFIED, SPLIT TO 2.2.10] Verify that users are notified after updates to authentication details, such as credential resets or modification of the username or email address.",
+            "parent": "V2.2"
+          },
+          {
+            "bom-ref": "V2.2.4",
+            "identifier": "V2.2.4",
+            "text": "[MODIFIED, SPLIT TO 2.2.9, MERGED FROM 2.2.7, 2.3.2] Verify that a hardware-based authentication mechanism is supported that provides impersonation resistance against phishing attacks (such as WebAuthn) and verifies intent to authenticate by requiring a user-initiated action (such as a button press on a FIDO hardware key).",
+            "parent": "V2.2"
+          },
+          {
+            "bom-ref": "V2.2.5",
+            "identifier": "V2.2.5",
+            "text": "[MOVED TO 9.3.3]",
+            "parent": "V2.2"
+          },
+          {
+            "bom-ref": "V2.2.6",
+            "identifier": "V2.2.6",
+            "text": "[DELETED, DUPLICATE OF 2.7.3, 2.8.4]",
+            "parent": "V2.2"
+          },
+          {
+            "bom-ref": "V2.2.7",
+            "identifier": "V2.2.7",
+            "text": "[DELETED, MERGED TO 2.2.4]",
+            "parent": "V2.2"
+          },
+          {
+            "bom-ref": "V2.2.8",
+            "identifier": "V2.2.8",
+            "text": "[ADDED] Verify that valid users cannot be deduced from failed authentication challenges, such as by basing on error messages, HTTP response codes, or different response times. Registration and forgot password functionality should also have this protection.",
+            "parent": "V2.2"
+          },
+          {
+            "bom-ref": "V2.2.9",
+            "identifier": "V2.2.9",
+            "text": "[ADDED, SPLIT FROM 2.2.4] Verify that the application requires users to either use a multi-factor authentication mechanism or a requires a combination of single-factor authentication mechanisms.",
+            "parent": "V2.2"
+          },
+          {
+            "bom-ref": "V2.2.10",
+            "identifier": "V2.2.10",
+            "text": "[ADDED, SPLIT FROM 2.2.3] Verify that users are notified of suspicious authentication attempts. This may include successful or unsuccessful authentication from an unusual location or client, partially successful authentication with only one of multiple factors, successful or unsuccessful authentication after a long period of inactivity or successful authentication after several unsuccessful attempts.",
+            "parent": "V2.2"
+          },
+          {
+            "bom-ref": "V2.2.11",
+            "identifier": "V2.2.11",
+            "text": "[ADDED, SPLIT FROM 1.2.4] Verify that, if the application includes multiple authentication pathways, there are no undocumented pathways and that security controls and authentication strength are enforced consistently.",
+            "parent": "V2.2"
+          },
+          {
+            "bom-ref": "V2.3",
+            "identifier": "V2.3",
+            "title": "Authentication Factor Lifecycle",
+            "parent": "V2"
+          },
+          {
+            "bom-ref": "V2.3.1",
+            "identifier": "V2.3.1",
+            "text": "[MODIFIED] Verify that system generated initial passwords or activation codes are securely randomly generated, follow the existing password policy, and expire after a short period of time or after they are initially used. 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": "[DELETED, MERGED TO 2.2.4]",
+            "parent": "V2.3"
+          },
+          {
+            "bom-ref": "V2.3.3",
+            "identifier": "V2.3.3",
+            "text": "[MODIFIED] Verify that renewal instructions for authentication mechanisms which expire are sent with enough time to be carried out before the old authentication mechanism expires, configuring automated reminders if necessary.",
+            "parent": "V2.3"
+          },
+          {
+            "bom-ref": "V2.3.4",
+            "identifier": "V2.3.4",
+            "text": "[ADDED] Verify that administrative users can initiate the password reset process for the user, but that this does not allow them to change or choose the user's password. This prevents a situation where they know the user's password.",
+            "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": "[MOVED TO 6.6.2]",
+            "parent": "V2.4"
+          },
+          {
+            "bom-ref": "V2.4.2",
+            "identifier": "V2.4.2",
+            "text": "[DELETED, INCORRECT]",
+            "parent": "V2.4"
+          },
+          {
+            "bom-ref": "V2.4.3",
+            "identifier": "V2.4.3",
+            "text": "[DELETED, MERGED TO 6.6.2]",
+            "parent": "V2.4"
+          },
+          {
+            "bom-ref": "V2.4.4",
+            "identifier": "V2.4.4",
+            "text": "[DELETED, MERGED TO 6.6.2]",
+            "parent": "V2.4"
+          },
+          {
+            "bom-ref": "V2.4.5",
+            "identifier": "V2.4.5",
+            "text": "[DELETED, INCORRECT]",
+            "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": "[DELETED, INCORRECT]",
+            "parent": "V2.5"
+          },
+          {
+            "bom-ref": "V2.5.2",
+            "identifier": "V2.5.2",
+            "text": "[GRAMMAR] Verify that 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": "[DELETED, DUPLICATE OF 2.4.1]",
+            "parent": "V2.5"
+          },
+          {
+            "bom-ref": "V2.5.4",
+            "identifier": "V2.5.4",
+            "text": "[MOVED TO 14.1.10]",
+            "parent": "V2.5"
+          },
+          {
+            "bom-ref": "V2.5.5",
+            "identifier": "V2.5.5",
+            "text": "[DELETED, DUPLICATE OF 2.2.3]",
+            "parent": "V2.5"
+          },
+          {
+            "bom-ref": "V2.5.6",
+            "identifier": "V2.5.6",
+            "text": "[MODIFIED] Verify that a secure process for resetting a forgotten password is implemented, that does not bypass any enabled multi-factor authentication mechanisms.",
+            "parent": "V2.5"
+          },
+          {
+            "bom-ref": "V2.5.7",
+            "identifier": "V2.5.7",
+            "text": "[GRAMMAR, LEVEL L2 > L1] Verify that if OTP or other 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": "Lookup Secrets",
+            "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": "[MODIFIED, SPLIT TO 2.6.4] Verify that, when being stored in the application's back-end, lookup secrets with less than 112 bits of entropy (19 random alphanumeric characters or 34 random digits) are hashed with an approved password storage hashing algorithm that incorporates a 32-bit random salt. A standard hash function can be used if the secret has 112 bits of entropy or more.",
+            "parent": "V2.6"
+          },
+          {
+            "bom-ref": "V2.6.3",
+            "identifier": "V2.6.3",
+            "text": "[MODIFIED] Verify that lookup secrets are generated using a Cryptographically Secure Pseudorandom Number Generator (CSPRNG) to avoid predictable values.",
+            "parent": "V2.6"
+          },
+          {
+            "bom-ref": "V2.6.4",
+            "identifier": "V2.6.4",
+            "text": "[ADDED, SPLIT FROM 2.6.2] Verify that lookup secrets have a minimum of 20 bits of entropy (typically 4 random alphanumeric characters or 6 random digits is sufficient).",
+            "parent": "V2.6"
+          },
+          {
+            "bom-ref": "V2.7",
+            "identifier": "V2.7",
+            "title": "Out-of-Band authentication mechanisms",
+            "parent": "V2"
+          },
+          {
+            "bom-ref": "V2.7.1",
+            "identifier": "V2.7.1",
+            "text": "[MODIFIED] Verify that authentication mechanisms using the Public Switched Telephone Network (PSTN) to deliver One-time Passwords (OTPs) via phone or SMS are offered only when alternate stronger methods (such as push notifications) are also offered and when the service provides information on their security risks to users.",
+            "parent": "V2.7"
+          },
+          {
+            "bom-ref": "V2.7.2",
+            "identifier": "V2.7.2",
+            "text": "[MODIFIED] Verify that out-of-band authentication requests, codes, or tokens expire within 10 minutes.",
+            "parent": "V2.7"
+          },
+          {
+            "bom-ref": "V2.7.3",
+            "identifier": "V2.7.3",
+            "text": "[GRAMMAR] Verify that out-of-band 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": "[GRAMMAR] Verify that the secondary communications channel being used is secure and independent of the primary channel.",
+            "parent": "V2.7"
+          },
+          {
+            "bom-ref": "V2.7.5",
+            "identifier": "V2.7.5",
+            "text": "[DELETED, INSUFFICIENT IMPACT]",
+            "parent": "V2.7"
+          },
+          {
+            "bom-ref": "V2.7.6",
+            "identifier": "V2.7.6",
+            "text": "[MODIFIED] Verify that codes used in out-of-band authentication are generated using a cryptographically secure random number generator (CSPRNG) and contain at least 20 bits of entropy (typically 4 random alphanumeric characters or 6 random digits is sufficient).",
+            "parent": "V2.7"
+          },
+          {
+            "bom-ref": "V2.7.7",
+            "identifier": "V2.7.7",
+            "text": "[ADDED] Verify that a code based out-of-band authentication mechanism is protected against brute force attacks by using either rate limiting or a code with at least 64 bits of entropy.",
+            "parent": "V2.7"
+          },
+          {
+            "bom-ref": "V2.7.8",
+            "identifier": "V2.7.8",
+            "text": "[ADDED] Verify that, where push notifications are used for multi-factor authentication, rate limiting or number matching is used to prevent push bombing attacks.",
+            "parent": "V2.7"
+          },
+          {
+            "bom-ref": "V2.8",
+            "identifier": "V2.8",
+            "title": "Time based One-time Passwords",
+            "parent": "V2"
+          },
+          {
+            "bom-ref": "V2.8.1",
+            "identifier": "V2.8.1",
+            "text": "[GRAMMAR] Verify that time-based, one-time passwords have a defined lifetime before expiring.",
+            "parent": "V2.8"
+          },
+          {
+            "bom-ref": "V2.8.2",
+            "identifier": "V2.8.2",
+            "text": "[GRAMMAR] Verify that symmetric keys used to verify submitted time-based, one-time passwords 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": "[GRAMMAR] Verify that approved cryptographic algorithms are used in the generation, seeding, and verification of time-based, one-time passwords.",
+            "parent": "V2.8"
+          },
+          {
+            "bom-ref": "V2.8.4",
+            "identifier": "V2.8.4",
+            "text": "[GRAMMAR] Verify that a time-based, one-time password can be used only once within the validity period.",
+            "parent": "V2.8"
+          },
+          {
+            "bom-ref": "V2.8.5",
+            "identifier": "V2.8.5",
+            "text": "[DELETED, INSUFFICIENT IMPACT]",
+            "parent": "V2.8"
+          },
+          {
+            "bom-ref": "V2.8.6",
+            "identifier": "V2.8.6",
+            "text": "[MODIFIED, LEVEL L2 > L3] Verify that physical single-factor OTP generators 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": "[MODIFIED, LEVEL L2 > L3] Verify that biometric authentication mechanisms are only used as secondary factors together with either something you have or something you know.",
+            "parent": "V2.8"
+          },
+          {
+            "bom-ref": "V2.8.8",
+            "identifier": "V2.8.8",
+            "text": "[ADDED] Ensure that generation of the time-based multi-factor OTP token is based on the server's system time and not the client's machine.",
+            "parent": "V2.8"
+          },
+          {
+            "bom-ref": "V2.9",
+            "identifier": "V2.9",
+            "title": "Cryptographic authentication mechanism",
+            "parent": "V2"
+          },
+          {
+            "bom-ref": "V2.9.1",
+            "identifier": "V2.9.1",
+            "text": "[MODIFIED, LEVEL L2 > L3] Verify that the authentication server stores the cryptographic keys used in verification are 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": "[LEVEL L2 > L3] 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": "[MODIFIED, LEVEL L2 > L3] Verify that approved cryptographic algorithms are used in the generation, seeding, and verification of the cryptographic keys.",
+            "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": "[MOVED TO 14.7.1]",
+            "parent": "V2.10"
+          },
+          {
+            "bom-ref": "V2.10.2",
+            "identifier": "V2.10.2",
+            "text": "[MOVED TO 14.7.2]",
+            "parent": "V2.10"
+          },
+          {
+            "bom-ref": "V2.10.3",
+            "identifier": "V2.10.3",
+            "text": "[DELETED, DUPLICATE OF 2.10.4]",
+            "parent": "V2.10"
+          },
+          {
+            "bom-ref": "V2.10.4",
+            "identifier": "V2.10.4",
+            "text": "[DELETED, MERGED TO 14.8.1]",
+            "parent": "V2.10"
+          },
+          {
+            "bom-ref": "V2.11",
+            "identifier": "V2.11",
+            "title": "Authentication with an Identity Providers",
+            "parent": "V2"
+          },
+          {
+            "bom-ref": "V2.11.1",
+            "identifier": "V2.11.1",
+            "text": "[ADDED] Verify that, if the application supports multiple identity providers (IDPs), the user's identity cannot be spoofed via another supported identity provider (eg. by using the same user identifier). Usually, the application should register and identify the user using a combination of the IdP ID (serving as a namespace) and the user's ID in the IDP.",
+            "parent": "V2.11"
+          },
+          {
+            "bom-ref": "V2.11.2",
+            "identifier": "V2.11.2",
+            "text": "[ADDED] Verify that the presence and integrity of digital signatures on authentication assertions (for example on JWTs or SAML assertions) are always validated, rejecting any assertions that are unsigned or have invalid signatures.",
+            "parent": "V2.11"
+          },
+          {
+            "bom-ref": "V2.11.3",
+            "identifier": "V2.11.3",
+            "text": "[ADDED] Verify that SAML assertions are uniquely processed and used only once within the validity period to prevent replay attacks.",
+            "parent": "V2.11"
+          },
+          {
+            "bom-ref": "V3",
+            "identifier": "V3",
+            "title": "Session Management"
+          },
+          {
+            "bom-ref": "V1.3",
+            "identifier": "V1.3",
+            "title": "Session Management Documentation",
+            "parent": "V3"
+          },
+          {
+            "bom-ref": "V1.3.1",
+            "identifier": "V1.3.1",
+            "text": "[ADDED] Verify that the user's session inactivity period and maximum session lifetime before reauthentication are documented, appropriate in combination with other controls, and that documentation includes justification for any deviations from NIST SP 800-63B reauthentication requirements.",
+            "parent": "V1.3"
+          },
+          {
+            "bom-ref": "V1.3.2",
+            "identifier": "V1.3.2",
+            "text": "[ADDED] Verify that the documentation defines how many concurrent (parallel) sessions are allowed for one account as well as the intended behaviours and actions to be taken when the maximum number of active sessions is reached.",
+            "parent": "V1.3"
+          },
+          {
+            "bom-ref": "V1.3.3",
+            "identifier": "V1.3.3",
+            "text": "[ADDED] Verify that all systems that create and manage user sessions as part of a federated identity management ecosystem (such as SSO systems) are documented along with controls to coordinate session lifetimes, termination, and any other condition that should require re-authentication.",
+            "parent": "V1.3"
+          },
+          {
+            "bom-ref": "V3.1",
+            "identifier": "V3.1",
+            "title": "Fundamental Session Management Security",
+            "parent": "V3"
+          },
+          {
+            "bom-ref": "V3.1.1",
+            "identifier": "V3.1.1",
+            "text": "[DELETED, MERGED TO 8.3.1]",
+            "parent": "V3.1"
+          },
+          {
+            "bom-ref": "V3.1.2",
+            "identifier": "V3.1.2",
+            "text": "[ADDED] Verify that the application performs all session token verification using a trusted, back-end service.",
+            "parent": "V3.1"
+          },
+          {
+            "bom-ref": "V3.1.3",
+            "identifier": "V3.1.3",
+            "text": "[MODIFIED, MOVED FROM 3.5.2, LEVEL L2 > L1] Verify that the application uses either self-contained or reference tokens for session management. Static API secrets and keys should be avoided.",
+            "parent": "V3.1"
+          },
+          {
+            "bom-ref": "V3.1.4",
+            "identifier": "V3.1.4",
+            "text": "[MODIFIED, MOVED FROM 3.2.2, MERGED FROM 3.2.4] Verify that if reference tokens are used to represent user sessions, they are unique and generated using a cryptographically secure pseudo-random number generator (CSPRNG) and possess at least 128 bits of entropy.",
+            "parent": "V3.1"
+          },
+          {
+            "bom-ref": "V3.1.5",
+            "identifier": "V3.1.5",
+            "text": "[MODIFIED, MOVED FROM 3.2.1] Verify that the application generates a new session token on user authentication, including re-authentication, and terminates the current session token.",
+            "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": "[MOVED TO 3.1.5]",
+            "parent": "V3.2"
+          },
+          {
+            "bom-ref": "V3.2.2",
+            "identifier": "V3.2.2",
+            "text": "[MOVED TO 3.1.4]",
+            "parent": "V3.2"
+          },
+          {
+            "bom-ref": "V3.2.3",
+            "identifier": "V3.2.3",
+            "text": "[DELETED, MERGED TO 8.2.2]",
+            "parent": "V3.2"
+          },
+          {
+            "bom-ref": "V3.2.4",
+            "identifier": "V3.2.4",
+            "text": "[DELETED, MERGED TO 3.1.4]",
+            "parent": "V3.2"
+          },
+          {
+            "bom-ref": "V3.3",
+            "identifier": "V3.3",
+            "title": "Session Timeout",
+            "parent": "V3"
+          },
+          {
+            "bom-ref": "V3.3.1",
+            "identifier": "V3.3.1",
+            "text": "[MOVED TO 3.8.1]",
+            "parent": "V3.3"
+          },
+          {
+            "bom-ref": "V3.3.2",
+            "identifier": "V3.3.2",
+            "text": "[MODIFIED, SPLIT TO 3.3.5] Verify that there is an absolute maximum session lifetime such that re-authentication is enforced according to risk analysis and documented security decisions.",
+            "parent": "V3.3"
+          },
+          {
+            "bom-ref": "V3.3.3",
+            "identifier": "V3.3.3",
+            "text": "[MOVED TO 3.8.2]",
+            "parent": "V3.3"
+          },
+          {
+            "bom-ref": "V3.3.4",
+            "identifier": "V3.3.4",
+            "text": "[MOVED TO 3.7.2]",
+            "parent": "V3.3"
+          },
+          {
+            "bom-ref": "V3.3.5",
+            "identifier": "V3.3.5",
+            "text": "[ADDED, SPLIT FROM 3.3.2] Verify that there is an inactivity timeout such that re-authentication is enforced according to risk analysis and documented security decisions.",
+            "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": "[MOVED TO 50.2.1]",
+            "parent": "V3.4"
+          },
+          {
+            "bom-ref": "V3.4.2",
+            "identifier": "V3.4.2",
+            "text": "[MOVED TO 50.2.2]",
+            "parent": "V3.4"
+          },
+          {
+            "bom-ref": "V3.4.3",
+            "identifier": "V3.4.3",
+            "text": "[MOVED TO 50.2.3]",
+            "parent": "V3.4"
+          },
+          {
+            "bom-ref": "V3.4.4",
+            "identifier": "V3.4.4",
+            "text": "[MOVED TO 50.2.4]",
+            "parent": "V3.4"
+          },
+          {
+            "bom-ref": "V3.4.5",
+            "identifier": "V3.4.5",
+            "text": "[DELETED, DEPRECATED BY 50.1.1]",
+            "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": "[MOVED TO 51.4.14]",
+            "parent": "V3.5"
+          },
+          {
+            "bom-ref": "V3.5.2",
+            "identifier": "V3.5.2",
+            "text": "[MOVED TO 3.1.3]",
+            "parent": "V3.5"
+          },
+          {
+            "bom-ref": "V3.5.3",
+            "identifier": "V3.5.3",
+            "text": "[MOVED TO 52.1.1]",
+            "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": "[MODIFIED, MERGED FROM 3.6.2] Verify that session lifetime and termination between Relying Parties (RPs) and Credential Service Providers (CSPs) behave as documented, requiring re-authentication as necessary such as when the maximum time between CSP authentication events is reached.",
+            "parent": "V3.6"
+          },
+          {
+            "bom-ref": "V3.6.2",
+            "identifier": "V3.6.2",
+            "text": "[DELETED, MERGED TO 3.6.1]",
+            "parent": "V3.6"
+          },
+          {
+            "bom-ref": "V3.6.3",
+            "identifier": "V3.6.3",
+            "text": "[ADDED] Verify that creation of a session requires either the user's consent or an explicit action, preventing the creation of new application sessions without user interaction.",
+            "parent": "V3.6"
+          },
+          {
+            "bom-ref": "V3.7",
+            "identifier": "V3.7",
+            "title": "Defenses Against Session Abuse",
+            "parent": "V3"
+          },
+          {
+            "bom-ref": "V3.7.1",
+            "identifier": "V3.7.1",
+            "text": "[MODIFIED] Verify that the application requires re-authentication or secondary verification before allowing highly sensitive transactions or modifications to sensitive account attributes such as authentication settings.",
+            "parent": "V3.7"
+          },
+          {
+            "bom-ref": "V3.7.2",
+            "identifier": "V3.7.2",
+            "text": "[MODIFIED, MOVED FROM 3.3.4] Verify that users are able to view and (having re-entered login credentials) terminate any or all currently active sessions.",
+            "parent": "V3.7"
+          },
+          {
+            "bom-ref": "V3.8",
+            "identifier": "V3.8",
+            "title": "Session Termination",
+            "parent": "V3"
+          },
+          {
+            "bom-ref": "V3.8.1",
+            "identifier": "V3.8.1",
+            "text": "[MODIFIED, MOVED FROM 3.3.1] Verify that logout and expiration terminate the user's session, such that the back button or a downstream relying party cannot resume an authenticated session.",
+            "parent": "V3.8"
+          },
+          {
+            "bom-ref": "V3.8.2",
+            "identifier": "V3.8.2",
+            "text": "[MODIFIED, LEVEL L2 > L1, MOVED FROM 3.3.3] Verify that the application gives the option to terminate all other active sessions after a successful change or removal of any authentication factor (including password change via reset or recovery and, if present, an MFA settings update).",
+            "parent": "V3.8"
+          },
+          {
+            "bom-ref": "V3.8.3",
+            "identifier": "V3.8.3",
+            "text": "[ADDED] Verify that all pages that require authentication have easy and visible access to logout functionality.",
+            "parent": "V3.8"
+          },
+          {
+            "bom-ref": "V3.8.4",
+            "identifier": "V3.8.4",
+            "text": "[ADDED] Verify that the application terminates all active sessions when a user account is disabled or deleted (such as an employee leaving the company).",
+            "parent": "V3.8"
+          },
+          {
+            "bom-ref": "V3.8.5",
+            "identifier": "V3.8.5",
+            "text": "[ADDED] Verify that application administrators are able to terminate active sessions for an individual user or for all users.",
+            "parent": "V3.8"
+          },
+          {
+            "bom-ref": "V4",
+            "identifier": "V4",
+            "title": "Access Control"
+          },
+          {
+            "bom-ref": "V1.4",
+            "identifier": "V1.4",
+            "title": "Access Control Documentation",
+            "parent": "V4"
+          },
+          {
+            "bom-ref": "V1.4.1",
+            "identifier": "V1.4.1",
+            "text": "[DELETED, DUPLICATE OF 4.1.1]",
+            "parent": "V1.4"
+          },
+          {
+            "bom-ref": "V1.4.2",
+            "identifier": "V1.4.2",
+            "text": "[DELETED]",
+            "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": "[DELETED, INSUFFICIENT IMPACT]",
+            "parent": "V1.4"
+          },
+          {
+            "bom-ref": "V1.4.5",
+            "identifier": "V1.4.5",
+            "text": "[DELETED, INSUFFICIENT IMPACT]",
+            "parent": "V1.4"
+          },
+          {
+            "bom-ref": "V1.4.6",
+            "identifier": "V1.4.6",
+            "text": "[ADDED] Verify that access control documentation defines controls that incorporate changes to a consumers environmental and contextual attributes (such as time of day, location, IP address, or device) to make security decisions, including those pertaining to authentication and authorization. These changes should be detected both when the consumer tries to start a new session or during an existing session.",
+            "parent": "V1.4"
+          },
+          {
+            "bom-ref": "V1.4.7",
+            "identifier": "V1.4.7",
+            "text": "[ADDED] Verify that access control documentation defines explicit rules for restricting function-level, data-specific, and field-level access based on consumer permissions, specifying relevant consumer and resource attributes, as well as environmental factors involved in decision-making.",
+            "parent": "V1.4"
+          },
+          {
+            "bom-ref": "V4.1",
+            "identifier": "V4.1",
+            "title": "General Access Control Design",
+            "parent": "V4"
+          },
+          {
+            "bom-ref": "V4.1.1",
+            "identifier": "V4.1.1",
+            "text": "[MOVED TO 4.2.3]",
+            "parent": "V4.1"
+          },
+          {
+            "bom-ref": "V4.1.2",
+            "identifier": "V4.1.2",
+            "text": "[DELETED, DUPLICATE OF 4.1.3]",
+            "parent": "V4.1"
+          },
+          {
+            "bom-ref": "V4.1.3",
+            "identifier": "V4.1.3",
+            "text": "[MODIFIED] Verify that the application ensures that function-level access is restricted to consumers with explicit permissions.",
+            "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": "[MOVED TO 7.4.5]",
+            "parent": "V4.1"
+          },
+          {
+            "bom-ref": "V4.1.6",
+            "identifier": "V4.1.6",
+            "text": "[MODIFIED, MOVED FROM 4.2.1] Verify that the application ensures that data-specific access is restricted to consumers with explicit permissions to specific data items to mitigate insecure direct object reference (IDOR) and broken object level authorization (BOLA).",
+            "parent": "V4.1"
+          },
+          {
+            "bom-ref": "V4.1.7",
+            "identifier": "V4.1.7",
+            "text": "[ADDED] Verify that the application ensures that field-level access is restricted to consumers with explicit permissions to specific fields to mitigate broken object property level authorization (BOPLA).",
+            "parent": "V4.1"
+          },
+          {
+            "bom-ref": "V4.1.8",
+            "identifier": "V4.1.8",
+            "text": "[ADDED] Verify that adaptive security controls related to authentication and authorization decisions based on a consumers environmental and contextual attributes (such as time of day, location, IP address, or device) are implemented as defined in access control documentation.",
+            "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": "[MOVED TO 4.1.6]",
+            "parent": "V4.2"
+          },
+          {
+            "bom-ref": "V4.2.2",
+            "identifier": "V4.2.2",
+            "text": "[MOVED TO 50.4.1]",
+            "parent": "V4.2"
+          },
+          {
+            "bom-ref": "V4.2.3",
+            "identifier": "V4.2.3",
+            "text": "[MODIFIED, MOVED FROM 4.1.1] Verify that the application enforces access control rules at a trusted service layer and doesn't rely on controls that an untrusted consumer could manipulate, such as client-side JavaScript.",
+            "parent": "V4.2"
+          },
+          {
+            "bom-ref": "V4.2.4",
+            "identifier": "V4.2.4",
+            "text": "[ADDED] Verify that changes to values on which access control decisions are made are applied immediately. Where changes cannot be applied immediately, (such as when relying on data in self-contained tokens), there must be mitigating controls to alert when a consumer performs an action when they should no longer be able to do so and revert the change. Note that this would be unable to mitigate information leakage.",
+            "parent": "V4.2"
+          },
+          {
+            "bom-ref": "V4.2.5",
+            "identifier": "V4.2.5",
+            "text": "[ADDED] Verify that access to an object is based on the originating subject's (e.g. consumer's) permissions, not on the permissions of any intermediary or service acting on their behalf. For example, if a consumer calls a web service using a self-contained token for authentication, and the service then requests data from a different service, the second service should use the consumer's token, rather than a machine-to-machine token from the first service, to make permission decisions.",
+            "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": "[MODIFIED, LEVEL L1 > L3] Verify that access to administrative interfaces incorporates multiple layers of security, including continuous consumer identity verification, device security posture assessment, and contextual risk analysis, ensuring that network location or trusted endpoints are not the sole factors for authorization even though they may reduce the likelihood of unauthorized access.",
+            "parent": "V4.3"
+          },
+          {
+            "bom-ref": "V4.3.2",
+            "identifier": "V4.3.2",
+            "text": "[SPLIT TO 14.3.4, 14.3.5]",
+            "parent": "V4.3"
+          },
+          {
+            "bom-ref": "V4.3.3",
+            "identifier": "V4.3.3",
+            "text": "[MOVED TO 14.7.3]",
+            "parent": "V4.3"
+          },
+          {
+            "bom-ref": "V4.3.4",
+            "identifier": "V4.3.4",
+            "text": "[ADDED] Verify that multi-tenant applications use cross-tenant controls to ensure consumer operations will never affect tenants with which they do not have permissions to interact.",
+            "parent": "V4.3"
+          },
+          {
+            "bom-ref": "V5",
+            "identifier": "V5",
+            "title": "Validation, Sanitization and Encoding"
+          },
+          {
+            "bom-ref": "V1.5",
+            "identifier": "V1.5",
+            "title": "Input and Output Documentation",
+            "parent": "V5"
+          },
+          {
+            "bom-ref": "V1.5.1",
+            "identifier": "V1.5.1",
+            "text": "[MODIFIED, SPLIT TO 1.5.5, LEVEL L2 > L1] Verify that input validation rules define how to check the validity of data items against an expected structure. This could be common data formats such as credit card numbers, e-mail addresses, telephone numbers, or it could be an internal data format.",
+            "parent": "V1.5"
+          },
+          {
+            "bom-ref": "V1.5.2",
+            "identifier": "V1.5.2",
+            "text": "[DELETED, MERGED TO 5.5.3]",
+            "parent": "V1.5"
+          },
+          {
+            "bom-ref": "V1.5.3",
+            "identifier": "V1.5.3",
+            "text": "[MOVED TO 5.6.2]",
+            "parent": "V1.5"
+          },
+          {
+            "bom-ref": "V1.5.4",
+            "identifier": "V1.5.4",
+            "text": "[MOVED TO 5.6.3]",
+            "parent": "V1.5"
+          },
+          {
+            "bom-ref": "V1.5.5",
+            "identifier": "V1.5.5",
+            "text": "[ADDED, SPLIT FROM 1.5.1] Verify that input validation rules are documented and define how to ensure the logical and contextual consistency of combined data items, such as checking that suburb and zip code match.",
+            "parent": "V1.5"
+          },
+          {
+            "bom-ref": "V5.1",
+            "identifier": "V5.1",
+            "title": "Input Validation",
+            "parent": "V5"
+          },
+          {
+            "bom-ref": "V5.1.1",
+            "identifier": "V5.1.1",
+            "text": "[MODIFIED] 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 (query string, body parameters, cookies, or header fields).",
+            "parent": "V5.1"
+          },
+          {
+            "bom-ref": "V5.1.2",
+            "identifier": "V5.1.2",
+            "text": "[MOVED TO 10.4.4]",
+            "parent": "V5.1"
+          },
+          {
+            "bom-ref": "V5.1.3",
+            "identifier": "V5.1.3",
+            "text": "[MODIFIED] Verify that all input is validated using positive validation, against an allowed list of values, patterns or ranges to enforce business or functional expectations for that input.",
+            "parent": "V5.1"
+          },
+          {
+            "bom-ref": "V5.1.4",
+            "identifier": "V5.1.4",
+            "text": "[MODIFIED, SPLIT TO 5.1.7] Verify that data items with an expected structure are validated according to the pre-defined rules.",
+            "parent": "V5.1"
+          },
+          {
+            "bom-ref": "V5.1.5",
+            "identifier": "V5.1.5",
+            "text": "[MODIFIED, SPLIT TO 50.8.1] Verify that the application will only automatically redirect the user to a different URL directly from an application URL where the destination appears on an allowlist.",
+            "parent": "V5.1"
+          },
+          {
+            "bom-ref": "V5.1.6",
+            "identifier": "V5.1.6",
+            "text": "[ADDED] Verify that the application validates that user-controlled input in HTTP request header fields does not exceed the server's maximum header field size limit (usually 4kB or 8kB) to prevent client-based denial of service attacks.",
+            "parent": "V5.1"
+          },
+          {
+            "bom-ref": "V5.1.7",
+            "identifier": "V5.1.7",
+            "text": "[ADDED, SPLIT FROM 5.1.4] Verify that the application ensures that combinations of related data items are reasonable according to the pre-defined rules.",
+            "parent": "V5.1"
+          },
+          {
+            "bom-ref": "V5.2",
+            "identifier": "V5.2",
+            "title": "Sanitization and Sandboxing",
+            "parent": "V5"
+          },
+          {
+            "bom-ref": "V5.2.1",
+            "identifier": "V5.2.1",
+            "text": "[MODIFIED] Verify that all untrusted HTML input from WYSIWYG editors or similar is properly sanitized using a well-known and secure HTML sanitization library or framework feature.",
+            "parent": "V5.2"
+          },
+          {
+            "bom-ref": "V5.2.2",
+            "identifier": "V5.2.2",
+            "text": "[MODIFIED] Verify that data being passed to a potentially dangerous context is sanitized beforehand to enforce safety measures, such as only allowing characters which are safe for this context and trimming input which is too long.",
+            "parent": "V5.2"
+          },
+          {
+            "bom-ref": "V5.2.3",
+            "identifier": "V5.2.3",
+            "text": "Verify that the application sanitizes user input before passing to mail systems to protect against SMTP or IMAP injection.",
+            "parent": "V5.2"
+          },
+          {
+            "bom-ref": "V5.2.4",
+            "identifier": "V5.2.4",
+            "text": "[MODIFIED] Verify that the application avoids the use of eval() or other dynamic code execution features such as Spring Expression Language (SpEL). Where there is no alternative, any user input being included must be sanitized or sandboxed before being executed.",
+            "parent": "V5.2"
+          },
+          {
+            "bom-ref": "V5.2.5",
+            "identifier": "V5.2.5",
+            "text": "[MODIFIED] Verify that the application protects against template injection attacks by not allowing templates to be built based on untrusted input. Where there is no alternative, any untrusted input being included dynamically during template creation must be sanitized or strictly validated.",
+            "parent": "V5.2"
+          },
+          {
+            "bom-ref": "V5.2.6",
+            "identifier": "V5.2.6",
+            "text": "[MODIFIED] Verify that the application protects against Server-side Request Forgery (SSRF) attacks, by validating untrusted data against an allowlist of protocols, domains, paths and ports and sanitizing potentially dangerous characters before using the data to call another service.",
+            "parent": "V5.2"
+          },
+          {
+            "bom-ref": "V5.2.7",
+            "identifier": "V5.2.7",
+            "text": "Verify that the application sanitizes, disables, or sandboxes user-supplied Scalable Vector Graphics (SVG) scriptable content, especially as they relate to XSS resulting from inline scripts, and foreignObject.",
+            "parent": "V5.2"
+          },
+          {
+            "bom-ref": "V5.2.8",
+            "identifier": "V5.2.8",
+            "text": "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.",
+            "parent": "V5.2"
+          },
+          {
+            "bom-ref": "V5.2.9",
+            "identifier": "V5.2.9",
+            "text": "[ADDED] Verify that the application uses slashes to correctly escape special characters being used in regular expressions to ensure they are not misinterpreted as control characters.",
+            "parent": "V5.2"
+          },
+          {
+            "bom-ref": "V5.2.10",
+            "identifier": "V5.2.10",
+            "text": "[ADDED] Verify that regular expressions are free from elements causing exponential backtracking, and ensure untrusted input is sanitized to mitigate ReDoS or Runaway Regex attacks.",
+            "parent": "V5.2"
+          },
+          {
+            "bom-ref": "V5.2.11",
+            "identifier": "V5.2.11",
+            "text": "[ADDED] Verify that the application appropriately sanitizes untrusted input before use in Java Naming and Directory Interface (JNDI) queries and that JNDI is configured as securely as possible to prevent JNDI injection attacks.",
+            "parent": "V5.2"
+          },
+          {
+            "bom-ref": "V5.2.12",
+            "identifier": "V5.2.12",
+            "text": "[ADDED] Verify that the application sanitizes content before it is sent to memcache to prevent injection attacks.",
+            "parent": "V5.2"
+          },
+          {
+            "bom-ref": "V5.2.13",
+            "identifier": "V5.2.13",
+            "text": "[MODIFIED, MOVED FROM 5.4.2] Verify that format strings which might resolve in an unexpected or malicious way when used are sanitized before being processed.",
+            "parent": "V5.2"
+          },
+          {
+            "bom-ref": "V5.3",
+            "identifier": "V5.3",
+            "title": "Injection Prevention",
+            "parent": "V5"
+          },
+          {
+            "bom-ref": "V5.3.1",
+            "identifier": "V5.3.1",
+            "text": "[MODIFIED, SPLIT TO 5.3.13] Verify that output encoding for an HTTP response, HTML document, or XML document is relevant for the context required, such as encoding the relevant characters for HTML elements, HTML attributes, HTML comments, CSS, or HTTP header fields, to avoid changing the message or document structure.",
+            "parent": "V5.3"
+          },
+          {
+            "bom-ref": "V5.3.2",
+            "identifier": "V5.3.2",
+            "text": "[DELETED, DUPLICATE OF 14.4.1]",
+            "parent": "V5.3"
+          },
+          {
+            "bom-ref": "V5.3.3",
+            "identifier": "V5.3.3",
+            "text": "[MODIFIED, SPLIT TO 50.6.2] Verify that output encoding or escaping is used when dynamically building JavaScript content (including JSON), to avoid changing the message or document structure (to avoid JavaScript and JSON injection).",
+            "parent": "V5.3"
+          },
+          {
+            "bom-ref": "V5.3.4",
+            "identifier": "V5.3.4",
+            "text": "[MODIFIED] Verify that data selection or database queries (e.g. SQL, HQL, NoSQL, Cypher) use parameterized queries, ORMs, entity frameworks, or are otherwise protected from SQL Injection and other database injection attacks. This should also be considered when writing stored procedures.",
+            "parent": "V5.3"
+          },
+          {
+            "bom-ref": "V5.3.5",
+            "identifier": "V5.3.5",
+            "text": "[DELETED, DUPLICATE OF 5.3.4]",
+            "parent": "V5.3"
+          },
+          {
+            "bom-ref": "V5.3.6",
+            "identifier": "V5.3.6",
+            "text": "[DELETED, DUPLICATE OF 5.3.3]",
+            "parent": "V5.3"
+          },
+          {
+            "bom-ref": "V5.3.7",
+            "identifier": "V5.3.7",
+            "text": "Verify that the application protects against LDAP injection vulnerabilities, or that specific security controls to prevent LDAP injection have been implemented.",
+            "parent": "V5.3"
+          },
+          {
+            "bom-ref": "V5.3.8",
+            "identifier": "V5.3.8",
+            "text": "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.",
+            "parent": "V5.3"
+          },
+          {
+            "bom-ref": "V5.3.9",
+            "identifier": "V5.3.9",
+            "text": "[DELETED, MERGED TO 12.3.1]",
+            "parent": "V5.3"
+          },
+          {
+            "bom-ref": "V5.3.10",
+            "identifier": "V5.3.10",
+            "text": "[MODIFIED] Verify that the application is protected against XPath injection attacks by using query parameterization or precompiled queries.",
+            "parent": "V5.3"
+          },
+          {
+            "bom-ref": "V5.3.11",
+            "identifier": "V5.3.11",
+            "text": "[ADDED] Verify that the application is protected against CSV and Formula Injection. The application should follow the escaping rules defined in RFC4180 2.6 and 2.7 when exporting CSV files. The application should escape special characters including '=', '+', '-', '@' '\\t' (tab) and '\\00' (null character) using a single quote, if they are the first character in a field, when exporting CSV files and other spreadsheet formats such as xls, xlsx, odf.",
+            "parent": "V5.3"
+          },
+          {
+            "bom-ref": "V5.3.12",
+            "identifier": "V5.3.12",
+            "text": "[ADDED] Verify that LaTeX processors are configured securely (such as not using the \"--shell-escape\" flag) and an allowlist of commands is used to prevent LaTeX injection attacks.",
+            "parent": "V5.3"
+          },
+          {
+            "bom-ref": "V5.3.13",
+            "identifier": "V5.3.13",
+            "text": "[ADDED, SPLIT FROM 5.3.1] Verify that when dynamically building URLs, untrusted data is encoded according to its context (e.g., URL encoding or base64url encoding for query or path parameters). Ensure that only safe URL protocols are permitted (e.g., disallow javascript: or data:).",
+            "parent": "V5.3"
+          },
+          {
+            "bom-ref": "V5.4",
+            "identifier": "V5.4",
+            "title": "Memory, String, and Unmanaged Code",
+            "parent": "V5"
+          },
+          {
+            "bom-ref": "V5.4.1",
+            "identifier": "V5.4.1",
+            "text": "Verify that the application uses memory-safe string, safer memory copy and pointer arithmetic to detect or prevent stack, buffer, or heap overflows.",
+            "parent": "V5.4"
+          },
+          {
+            "bom-ref": "V5.4.2",
+            "identifier": "V5.4.2",
+            "text": "[MOVED TO 5.2.13]",
+            "parent": "V5.4"
+          },
+          {
+            "bom-ref": "V5.4.3",
+            "identifier": "V5.4.3",
+            "text": "Verify that sign, range, and input validation techniques are used to prevent integer overflows.",
+            "parent": "V5.4"
+          },
+          {
+            "bom-ref": "V5.4.4",
+            "identifier": "V5.4.4",
+            "text": "[ADDED] Verify that dynamically allocated memory and resources are properly released, and that references or pointers to freed memory are removed or set to null to prevent dangling pointers and use-after-free vulnerabilities.",
+            "parent": "V5.4"
+          },
+          {
+            "bom-ref": "V5.5",
+            "identifier": "V5.5",
+            "title": "Safe Deserialization",
+            "parent": "V5"
+          },
+          {
+            "bom-ref": "V5.5.1",
+            "identifier": "V5.5.1",
+            "text": "[DELETED, INCORRECT]",
+            "parent": "V5.5"
+          },
+          {
+            "bom-ref": "V5.5.2",
+            "identifier": "V5.5.2",
+            "text": "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 XML eXternal Entity (XXE) attacks.",
+            "parent": "V5.5"
+          },
+          {
+            "bom-ref": "V5.5.3",
+            "identifier": "V5.5.3",
+            "text": "[MODIFIED, MERGED FROM 1.5.2] Verify that deserialization with untrusted clients enforces safe input handling, such as using an allowlist of object types or restricting client-defined object types, to prevent deserialization attacks. Deserialization mechanisms that are explicitly defined as insecure (such as BinaryFormatter) must not be used with untrusted input.",
+            "parent": "V5.5"
+          },
+          {
+            "bom-ref": "V5.5.4",
+            "identifier": "V5.5.4",
+            "text": "[DELETED, DUPLICATE OF 5.2.4]",
+            "parent": "V5.5"
+          },
+          {
+            "bom-ref": "V5.5.5",
+            "identifier": "V5.5.5",
+            "text": "[MODIFIED, MOVED FROM 13.1.1, LEVEL L1 > L2] Verify that different parsers used in the application for the same data type (e.g. JSON parsers, XML parsers, URL parsers), perform parsing in a consistent way and use the same character encoding mechanism to avoid issues such as JSON Interoperability vulnerabilities or different URI or file parsing behavior being exploited in Remote File Inclusion (RFI) or Server-side Request Forgery (SSRF) attacks.",
+            "parent": "V5.5"
+          },
+          {
+            "bom-ref": "V5.6",
+            "identifier": "V5.6",
+            "title": "Validation and Sanitization Architecture",
+            "parent": "V5"
+          },
+          {
+            "bom-ref": "V5.6.1",
+            "identifier": "V5.6.1",
+            "text": "[ADDED] Verify that input is decoded or unescaped into a canonical form only once, it is only decoded when encoded data in that form is expected, and that this is done before processing the input further, for example it is not performed after input validation or sanitization.",
+            "parent": "V5.6"
+          },
+          {
+            "bom-ref": "V5.6.2",
+            "identifier": "V5.6.2",
+            "text": "[MODIFIED, MOVED FROM 1.5.3, LEVEL L2 > L1] Verify that the application is designed to enforce input validation at a trusted service layer. While client-side validation improves usability, it must not be relied upon as a security control.",
+            "parent": "V5.6"
+          },
+          {
+            "bom-ref": "V5.6.3",
+            "identifier": "V5.6.3",
+            "text": "[MODIFIED, MOVED FROM 1.5.4] Verify that the application performs output encoding and escaping either as a final step before being used by the interpreter for which it is intended or by the interpreter itself.",
+            "parent": "V5.6"
+          },
+          {
+            "bom-ref": "V6",
+            "identifier": "V6",
+            "title": "Cryptography"
+          },
+          {
+            "bom-ref": "V1.6",
+            "identifier": "V1.6",
+            "title": "Cryptographic Inventory and Documentation",
+            "parent": "V6"
+          },
+          {
+            "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": "[DELETED, MERGED TO 14.8.1]",
+            "parent": "V1.6"
+          },
+          {
+            "bom-ref": "V1.6.3",
+            "identifier": "V1.6.3",
+            "text": "[DELETED, MERGED TO 6.2.4]",
+            "parent": "V1.6"
+          },
+          {
+            "bom-ref": "V1.6.4",
+            "identifier": "V1.6.4",
+            "text": "[MODIFIED] Verify that a cryptographic inventory is performed, maintained, regularly updated, and includes all cryptographic keys, algorithms, and certificates used by the application. It should also document where keys can and cannot be used in the system and also the types of data which can and cannot be protected using the keys.",
+            "parent": "V1.6"
+          },
+          {
+            "bom-ref": "V1.6.5",
+            "identifier": "V1.6.5",
+            "text": "[ADDED] Verify that cryptographic discovery mechanisms are employed to identify all instances of cryptography in the system, including encryption, hashing, and signing operations.",
+            "parent": "V1.6"
+          },
+          {
+            "bom-ref": "V6.1",
+            "identifier": "V6.1",
+            "title": "Data Classification",
+            "parent": "V6"
+          },
+          {
+            "bom-ref": "V6.1.1",
+            "identifier": "V6.1.1",
+            "text": "[DELETED, MERGED TO 1.8.1]",
+            "parent": "V6.1"
+          },
+          {
+            "bom-ref": "V6.1.2",
+            "identifier": "V6.1.2",
+            "text": "[DELETED, MERGED TO 1.8.1]",
+            "parent": "V6.1"
+          },
+          {
+            "bom-ref": "V6.1.3",
+            "identifier": "V6.1.3",
+            "text": "[DELETED, DUPLICATE OF 1.8.1]",
+            "parent": "V6.1"
+          },
+          {
+            "bom-ref": "V6.2",
+            "identifier": "V6.2",
+            "title": "Algorithms",
+            "parent": "V6"
+          },
+          {
+            "bom-ref": "V6.2.1",
+            "identifier": "V6.2.1",
+            "text": "[MODIFIED] Verify that all cryptographic modules fail securely, and errors are handled in a way that does not enable vulnerabilities, such as Padding Oracle attacks.",
+            "parent": "V6.2"
+          },
+          {
+            "bom-ref": "V6.2.2",
+            "identifier": "V6.2.2",
+            "text": "Verify that industry proven or government approved cryptographic algorithms, modes, and libraries are used, instead of custom coded cryptography.",
+            "parent": "V6.2"
+          },
+          {
+            "bom-ref": "V6.2.3",
+            "identifier": "V6.2.3",
+            "text": "[DELETED, DUPLICATE OF 6.2.5]",
+            "parent": "V6.2"
+          },
+          {
+            "bom-ref": "V6.2.4",
+            "identifier": "V6.2.4",
+            "text": "[MODIFIED, MERGED FROM 1.6.3] Verify that the application is designed with crypto agility such 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. Similarly, it must also be possible to replace keys and passwords and re-encrypt data. This should allow for seamless upgrades to post-quantum cryptography (PQC), once PQC standards are fully established.",
+            "parent": "V6.2"
+          },
+          {
+            "bom-ref": "V6.2.5",
+            "identifier": "V6.2.5",
+            "text": "[SPLIT TO 6.5.1, 6.5.2, 6.6.3]",
+            "parent": "V6.2"
+          },
+          {
+            "bom-ref": "V6.2.6",
+            "identifier": "V6.2.6",
+            "text": "[MOVED TO 6.5.3]",
+            "parent": "V6.2"
+          },
+          {
+            "bom-ref": "V6.2.7",
+            "identifier": "V6.2.7",
+            "text": "[MOVED TO 6.5.4]",
+            "parent": "V6.2"
+          },
+          {
+            "bom-ref": "V6.2.8",
+            "identifier": "V6.2.8",
+            "text": "Verify that all cryptographic operations are constant-time, with no 'short-circuit' operations in comparisons, calculations, or returns, to avoid leaking information.",
+            "parent": "V6.2"
+          },
+          {
+            "bom-ref": "V6.2.9",
+            "identifier": "V6.2.9",
+            "text": "[ADDED] Verify that all cryptographic primitives utilize a minimum of 128-bits of security based on the algorithm, key size, and configuration. For example, a 256-bit ECC key provides roughly 128 bits of security where RSA requires a 3072-bit key to achieve 128 bits of security.",
+            "parent": "V6.2"
+          },
+          {
+            "bom-ref": "V6.3",
+            "identifier": "V6.3",
+            "title": "Random Values",
+            "parent": "V6"
+          },
+          {
+            "bom-ref": "V6.3.1",
+            "identifier": "V6.3.1",
+            "text": "[GRAMMAR, LEVEL L2 > L1] Verify that all random numbers and strings which are intended to be non-guessable must be generated using a cryptographically-secure pseudo-random number generator (CSPRNG) and have at least 128 bits of entropy. Note that UUIDs do not respect this condition.",
+            "parent": "V6.3"
+          },
+          {
+            "bom-ref": "V6.3.2",
+            "identifier": "V6.3.2",
+            "text": "[DELETED, DUPLICATE OF 6.3.1]",
+            "parent": "V6.3"
+          },
+          {
+            "bom-ref": "V6.3.3",
+            "identifier": "V6.3.3",
+            "text": "[GRAMMAR, LEVEL L3 > L1] Verify that random number generation works properly under heavy system load, or that the system degrades gracefully.",
+            "parent": "V6.3"
+          },
+          {
+            "bom-ref": "V6.4",
+            "identifier": "V6.4",
+            "title": "Secret Management",
+            "parent": "V6"
+          },
+          {
+            "bom-ref": "V6.4.1",
+            "identifier": "V6.4.1",
+            "text": "[MOVED TO 14.8.1]",
+            "parent": "V6.4"
+          },
+          {
+            "bom-ref": "V6.4.2",
+            "identifier": "V6.4.2",
+            "text": "[MOVED TO 14.8.2]",
+            "parent": "V6.4"
+          },
+          {
+            "bom-ref": "V6.5",
+            "identifier": "V6.5",
+            "title": "Cipher Algorithms",
+            "parent": "V6"
+          },
+          {
+            "bom-ref": "V6.5.1",
+            "identifier": "V6.5.1",
+            "text": "[ADDED, SPLIT FROM 6.2.5] Verify that insecure block modes (e.g., ECB) and weak padding schemes (e.g., PKCS#1 v1.5) are not used.",
+            "parent": "V6.5"
+          },
+          {
+            "bom-ref": "V6.5.2",
+            "identifier": "V6.5.2",
+            "text": "[ADDED, SPLIT FROM 6.2.5, LEVEL L2 > L1] Verify that insecure ciphers, including Triple-DES and Blowfish, are not used but secure ciphers and modes such as AES with GCM are.",
+            "parent": "V6.5"
+          },
+          {
+            "bom-ref": "V6.5.3",
+            "identifier": "V6.5.3",
+            "text": "[MODIFIED, MOVED FROM 6.2.6, LEVEL L2 > L3] Verify that nonces, initialization vectors, and other single-use numbers are not used for more than one encryption key/data-element pair. The method of generation must be appropriate for the algorithm being used.",
+            "parent": "V6.5"
+          },
+          {
+            "bom-ref": "V6.5.4",
+            "identifier": "V6.5.4",
+            "text": "[MODIFIED, MOVED FROM 6.2.7] Verify that encrypted data is authenticated via signatures, as well as through authenticated cipher modes or HMAC for protection against unauthorized modification.",
+            "parent": "V6.5"
+          },
+          {
+            "bom-ref": "V6.5.5",
+            "identifier": "V6.5.5",
+            "text": "[ADDED] Verify that any authenticated signatures are operating in encrypt-then-MAC or encrypt-then-hash modes as required.",
+            "parent": "V6.5"
+          },
+          {
+            "bom-ref": "V6.6",
+            "identifier": "V6.6",
+            "title": "Hashing and Hash-based Functions",
+            "parent": "V6"
+          },
+          {
+            "bom-ref": "V6.6.1",
+            "identifier": "V6.6.1",
+            "text": "[ADDED] Verify that only approved hash functions are used for general cryptographic use cases, including digital signatures, HMAC, KDF, and random bit generation.",
+            "parent": "V6.6"
+          },
+          {
+            "bom-ref": "V6.6.2",
+            "identifier": "V6.6.2",
+            "text": "[MODIFIED, MOVED FROM 2.4.1, MERGED FROM 2.4.3, 2.4.4] Verify that passwords are stored using an approved, computationally intensive, hashing algorithm with parameter settings configured based on current guidance. The settings should balance security and performance to make brute-force attacks more challenging.",
+            "parent": "V6.6"
+          },
+          {
+            "bom-ref": "V6.6.3",
+            "identifier": "V6.6.3",
+            "text": "[ADDED, SPLIT FROM 6.2.5] Verify that cryptographic systems avoid the use of disallowed hash functions, such as MD5, SHA-1, or any other insecure hash functions, for any cryptographic purpose.",
+            "parent": "V6.6"
+          },
+          {
+            "bom-ref": "V6.6.4",
+            "identifier": "V6.6.4",
+            "text": "[ADDED] Verify that hash functions used in digital signatures are collision resistant and have appropriate bit-lengths to avoid attacks, such as collision or pre-image attacks.",
+            "parent": "V6.6"
+          },
+          {
+            "bom-ref": "V6.7",
+            "identifier": "V6.7",
+            "title": "Key Exchange Mechanisms",
+            "parent": "V6"
+          },
+          {
+            "bom-ref": "V6.7.1",
+            "identifier": "V6.7.1",
+            "text": "[ADDED] Verify that industry-proven cryptographic algorithms are used for key exchange (such as Diffie-Hellman) with a focus on ensuring that key exchange mechanisms use secure parameters. This should prevent attacks on the key establishment process which could lead to adversary-in-the-middle attacks or cryptographic breaks.",
+            "parent": "V6.7"
+          },
+          {
+            "bom-ref": "V6.8",
+            "identifier": "V6.8",
+            "title": "In-Use Data Cryptography",
+            "parent": "V6"
+          },
+          {
+            "bom-ref": "V6.8.1",
+            "identifier": "V6.8.1",
+            "text": "[ADDED] Verify that full memory encryption is in use that protects sensitive data while it is in use, preventing access by unauthorized users or processes.",
+            "parent": "V6.8"
+          },
+          {
+            "bom-ref": "V6.8.2",
+            "identifier": "V6.8.2",
+            "text": "[ADDED] Verify that data minimization ensures the minimal amount of data is exposed during processing, and ensure that data is encrypted immediately after use or as soon as feasible.",
+            "parent": "V6.8"
+          },
+          {
+            "bom-ref": "V6.9",
+            "identifier": "V6.9",
+            "title": "Post-Quantum Cryptography (PQC)",
+            "parent": "V6"
+          },
+          {
+            "bom-ref": "V6.9.1",
+            "identifier": "V6.9.1",
+            "text": "[ADDED] Verify that a cryptographic inventory is maintained and includes a documented transformation plan or mapping that outlines the migration path from current cryptographic algorithms and systems to those that are post-quantum cryptography/quantum-safe.",
+            "parent": "V6.9"
+          },
+          {
+            "bom-ref": "V6.9.2",
+            "identifier": "V6.9.2",
+            "text": "[ADDED] Verify that advancements in the field of post-quantum cryptography are being monitored in order to ensure that the application is aligned with emerging industry standards, and remains prepared for quantum threats.",
+            "parent": "V6.9"
+          },
+          {
+            "bom-ref": "V7",
+            "identifier": "V7",
+            "title": "Security Logging and Error Handling"
+          },
+          {
+            "bom-ref": "V1.7",
+            "identifier": "V1.7",
+            "title": "Errors, Logging and Auditing Documentation",
+            "parent": "V7"
+          },
+          {
+            "bom-ref": "V1.7.1",
+            "identifier": "V1.7.1",
+            "text": "[MOVED TO 7.1.7]",
+            "parent": "V1.7"
+          },
+          {
+            "bom-ref": "V1.7.2",
+            "identifier": "V1.7.2",
+            "text": "[MOVED TO 7.3.5]",
+            "parent": "V1.7"
+          },
+          {
+            "bom-ref": "V1.7.3",
+            "identifier": "V1.7.3",
+            "text": "[ADDED] Verify that an inventory exists documenting the logging performed at each layer of the application's technology stack, what events are being logged, log formats, where that logging is stored, how it is used, how access to it is controlled and how long logs are kept for.",
+            "parent": "V1.7"
+          },
+          {
+            "bom-ref": "V7.1",
+            "identifier": "V7.1",
+            "title": "General Logging",
+            "parent": "V7"
+          },
+          {
+            "bom-ref": "V7.1.1",
+            "identifier": "V7.1.1",
+            "text": "[MODIFIED, MERGED FROM 7.1.2] Verify that when logging sensitive data, the application considers the protection level of the data. For example, it may not be allowed to log certain data such as credentials or payment details. Other data such as session tokens may only be logged having been hashed or masked, either in full or partially.",
+            "parent": "V7.1"
+          },
+          {
+            "bom-ref": "V7.1.2",
+            "identifier": "V7.1.2",
+            "text": "[DELETED, MERGED TO 7.1.1]",
+            "parent": "V7.1"
+          },
+          {
+            "bom-ref": "V7.1.3",
+            "identifier": "V7.1.3",
+            "text": "[MOVED TO 7.2.3]",
+            "parent": "V7.1"
+          },
+          {
+            "bom-ref": "V7.1.4",
+            "identifier": "V7.1.4",
+            "text": "[MODIFIED] Verify that each log entry includes necessary metadata that would allow for a detailed investigation of the timeline when an event happens.",
+            "parent": "V7.1"
+          },
+          {
+            "bom-ref": "V7.1.5",
+            "identifier": "V7.1.5",
+            "text": "[MOVED FROM 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.",
+            "parent": "V7.1"
+          },
+          {
+            "bom-ref": "V7.1.6",
+            "identifier": "V7.1.6",
+            "text": "[ADDED] Verify that the application only stores or broadcasts logs to the files and services that are documented in the log inventory.",
+            "parent": "V7.1"
+          },
+          {
+            "bom-ref": "V7.1.7",
+            "identifier": "V7.1.7",
+            "text": "[MODIFIED, MOVED FROM 1.7.1] Verify that logs can be read and correlated by the log processor which is in use, preferably by using a common logging format.",
+            "parent": "V7.1"
+          },
+          {
+            "bom-ref": "V7.2",
+            "identifier": "V7.2",
+            "title": "Security Events",
+            "parent": "V7"
+          },
+          {
+            "bom-ref": "V7.2.1",
+            "identifier": "V7.2.1",
+            "text": "[MODIFIED] Verify that all authentication operations are logged including both successful and unsuccessful attempts. Additional metadata such as type of authentication or factors used should also be collected.",
+            "parent": "V7.2"
+          },
+          {
+            "bom-ref": "V7.2.2",
+            "identifier": "V7.2.2",
+            "text": "[MODIFIED] Verify that all access control decisions are logged including failed attempts.",
+            "parent": "V7.2"
+          },
+          {
+            "bom-ref": "V7.2.3",
+            "identifier": "V7.2.3",
+            "text": "[MODIFIED, MOVED FROM 7.1.3] Verify that the application logs attempts to bypass the security controls defined in the design documentation such as input validation.",
+            "parent": "V7.2"
+          },
+          {
+            "bom-ref": "V7.2.4",
+            "identifier": "V7.2.4",
+            "text": "[MODIFIED, MOVED FROM 11.1.7] Verify that the application monitors for unusual events or activity from a business logic perspective.",
+            "parent": "V7.2"
+          },
+          {
+            "bom-ref": "V7.2.5",
+            "identifier": "V7.2.5",
+            "text": "[MODIFIED, MOVED FROM 11.1.8] Verify that the application has configurable alerting when unusual or malicious activity is detected.",
+            "parent": "V7.2"
+          },
+          {
+            "bom-ref": "V7.2.6",
+            "identifier": "V7.2.6",
+            "text": "[MODIFIED, MOVED FROM 9.2.5] Verify that the application logs security control failures such as backend TLS failures.",
+            "parent": "V7.2"
+          },
+          {
+            "bom-ref": "V7.2.7",
+            "identifier": "V7.2.7",
+            "text": "[MODIFIED, MOVED FROM 8.3.5] Verify that accessing sensitive data is logged (without logging the sensitive data itself) if this is required by relevant data protection requirements.",
+            "parent": "V7.2"
+          },
+          {
+            "bom-ref": "V7.3",
+            "identifier": "V7.3",
+            "title": "Log Protection",
+            "parent": "V7"
+          },
+          {
+            "bom-ref": "V7.3.1",
+            "identifier": "V7.3.1",
+            "text": "Verify that all logging components appropriately encode data to prevent log injection.",
+            "parent": "V7.3"
+          },
+          {
+            "bom-ref": "V7.3.2",
+            "identifier": "V7.3.2",
+            "text": "[DELETED, DUPLICATE OF 7.3.1]",
+            "parent": "V7.3"
+          },
+          {
+            "bom-ref": "V7.3.3",
+            "identifier": "V7.3.3",
+            "text": "[MODIFIED] Verify that logs are protected from unauthorized access and cannot be modified.",
+            "parent": "V7.3"
+          },
+          {
+            "bom-ref": "V7.3.4",
+            "identifier": "V7.3.4",
+            "text": "[MOVED TO 7.1.5]",
+            "parent": "V7.3"
+          },
+          {
+            "bom-ref": "V7.3.5",
+            "identifier": "V7.3.5",
+            "text": "[MOVED FROM 1.7.2] Verify that logs are securely transmitted to a preferably remote system for analysis, detection, alerting, and escalation.",
+            "parent": "V7.3"
+          },
+          {
+            "bom-ref": "V7.4",
+            "identifier": "V7.4",
+            "title": "Error Handling",
+            "parent": "V7"
+          },
+          {
+            "bom-ref": "V7.4.1",
+            "identifier": "V7.4.1",
+            "text": "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.",
+            "parent": "V7.4"
+          },
+          {
+            "bom-ref": "V7.4.2",
+            "identifier": "V7.4.2",
+            "text": "[MODIFIED] Verify that a consistent and standardized exception handling mechanism (or a functional equivalent) is used across the codebase.",
+            "parent": "V7.4"
+          },
+          {
+            "bom-ref": "V7.4.3",
+            "identifier": "V7.4.3",
+            "text": "Verify that a \"last resort\" error handler is defined which will catch all unhandled exceptions.",
+            "parent": "V7.4"
+          },
+          {
+            "bom-ref": "V7.4.4",
+            "identifier": "V7.4.4",
+            "text": "[ADDED] Verify that the application is designed in a way that a failure to access external resources does not result in the entire application failing, for example using the circuit breaker pattern.",
+            "parent": "V7.4"
+          },
+          {
+            "bom-ref": "V7.4.5",
+            "identifier": "V7.4.5",
+            "text": "[MODIFIED, MOVED FROM 4.1.5, LEVEL L1 > L2] Verify that the application fails gracefully and securely, including when an exception occurs, preventing fail open conditions such as processing a transaction despite errors resulting from validation logic.",
+            "parent": "V7.4"
+          },
+          {
+            "bom-ref": "V8",
+            "identifier": "V8",
+            "title": "Data Protection"
+          },
+          {
+            "bom-ref": "V1.8",
+            "identifier": "V1.8",
+            "title": "Data Protection and Privacy Documentation",
+            "parent": "V8"
+          },
+          {
+            "bom-ref": "V1.8.1",
+            "identifier": "V1.8.1",
+            "text": "[MODIFIED, MERGED FROM 8.3.4, 6.1.1, 6.1.2] Verify that all sensitive data created and processed by the application has been identified and classified into protection levels, and ensure that a policy is in place on how to deal with sensitive data. Note that this includes sensitive data that is being encoded in a recoverable form such as Base64 and JWT. Protection levels need to take into account any data protection and privacy regulations and standards which the application is required to comply with.",
+            "parent": "V1.8"
+          },
+          {
+            "bom-ref": "V1.8.2",
+            "identifier": "V1.8.2",
+            "text": "[MODIFIED, SPLIT TO 8.1.9] Verify that all protection levels have a documented set of protection requirements. This should include (but not be limited to) requirements related to general encryption, integrity verification, retention, how the data should be logged, access controls around sensitive data in logs, database-level encryption, privacy and privacy-enhancing technologies to be used, and other confidentiality requirements.",
+            "parent": "V1.8"
+          },
+          {
+            "bom-ref": "V8.1",
+            "identifier": "V8.1",
+            "title": "General Data Protection",
+            "parent": "V8"
+          },
+          {
+            "bom-ref": "V8.1.1",
+            "identifier": "V8.1.1",
+            "text": "[MODIFIED, MERGED FROM 8.1.2] Verify that the application prevents sensitive data from being cached in server components such as load balancers and application caches or ensures that the data is securely purged after use.",
+            "parent": "V8.1"
+          },
+          {
+            "bom-ref": "V8.1.2",
+            "identifier": "V8.1.2",
+            "text": "[DELETED, MERGED TO 8.1.1]",
+            "parent": "V8.1"
+          },
+          {
+            "bom-ref": "V8.1.3",
+            "identifier": "V8.1.3",
+            "text": "[DELETED, INSUFFICIENT IMPACT]",
+            "parent": "V8.1"
+          },
+          {
+            "bom-ref": "V8.1.4",
+            "identifier": "V8.1.4",
+            "text": "[GRAMMAR] Verify that 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.",
+            "parent": "V8.1"
+          },
+          {
+            "bom-ref": "V8.1.5",
+            "identifier": "V8.1.5",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V8.1"
+          },
+          {
+            "bom-ref": "V8.1.6",
+            "identifier": "V8.1.6",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V8.1"
+          },
+          {
+            "bom-ref": "V8.1.7",
+            "identifier": "V8.1.7",
+            "text": "[ADDED] Verify that caching mechanisms are configured to only cache responses which have the correct content type and do not contain sensitive, dynamic content. The web server should return a 404 or 302 response when an non-existent file is accessed rather than returning a different, valid file. This should prevent Web Cache Deception attacks.",
+            "parent": "V8.1"
+          },
+          {
+            "bom-ref": "V8.1.8",
+            "identifier": "V8.1.8",
+            "text": "[ADDED] Verify that defined sensitive data is not sent to untrusted parties (e.g. user trackers) to prevent unwanted collection of data outside of the application's control.",
+            "parent": "V8.1"
+          },
+          {
+            "bom-ref": "V8.1.9",
+            "identifier": "V8.1.9",
+            "text": "[ADDED, SPLIT FROM 1.8.2] Verify that controls around sensitive data are implemented as defined in the documentation for the specific data's protection level.",
+            "parent": "V8.1"
+          },
+          {
+            "bom-ref": "V8.1.10",
+            "identifier": "V8.1.10",
+            "text": "[ADDED] Verify that the application only returns the minimum required sensitive data for the application's functionality. For example, only returning some of the digits of a credit card number and not the full number. If the full data is absolutely required, it should be masked in the user interface unless the user specifically views it.",
+            "parent": "V8.1"
+          },
+          {
+            "bom-ref": "V8.2",
+            "identifier": "V8.2",
+            "title": "Client-side Data Protection",
+            "parent": "V8"
+          },
+          {
+            "bom-ref": "V8.2.1",
+            "identifier": "V8.2.1",
+            "text": "[MODIFIED] Verify that the application sets sufficient anti-caching HTTP response header fields (i.e. Cache-Control: no-store) so that sensitive data is not cached in browsers.",
+            "parent": "V8.2"
+          },
+          {
+            "bom-ref": "V8.2.2",
+            "identifier": "V8.2.2",
+            "text": "[MODIFIED, MERGED FROM 3.2.3] Verify that data stored in browser storage (such as localStorage, sessionStorage, IndexedDB, or cookies) does not contain sensitive data, with the exception of session identifiers.",
+            "parent": "V8.2"
+          },
+          {
+            "bom-ref": "V8.2.3",
+            "identifier": "V8.2.3",
+            "text": "[MODIFIED] Verify that authenticated data is cleared from client storage, such as the browser DOM, after the client or session is terminated. The \"Clear-Site-Data header\" may be able to help with this but the client-side should also be able to clear up if the server connection is lost.",
+            "parent": "V8.2"
+          },
+          {
+            "bom-ref": "V8.3",
+            "identifier": "V8.3",
+            "title": "Sensitive Private Data",
+            "parent": "V8"
+          },
+          {
+            "bom-ref": "V8.3.1",
+            "identifier": "V8.3.1",
+            "text": "[MODIFIED, MERGED FROM 3.1.1, 13.1.3] Verify that sensitive data is only sent to the server in the HTTP message body or header fields and that the URL and query string do not contain sensitive information, such as an API key or session token.",
+            "parent": "V8.3"
+          },
+          {
+            "bom-ref": "V8.3.2",
+            "identifier": "V8.3.2",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V8.3"
+          },
+          {
+            "bom-ref": "V8.3.3",
+            "identifier": "V8.3.3",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V8.3"
+          },
+          {
+            "bom-ref": "V8.3.4",
+            "identifier": "V8.3.4",
+            "text": "[DELETED, MERGED TO 1.8.1]",
+            "parent": "V8.3"
+          },
+          {
+            "bom-ref": "V8.3.5",
+            "identifier": "V8.3.5",
+            "text": "[MOVED TO 7.2.7]",
+            "parent": "V8.3"
+          },
+          {
+            "bom-ref": "V8.3.6",
+            "identifier": "V8.3.6",
+            "text": "[DELETED, NOT PRACTICAL]",
+            "parent": "V8.3"
+          },
+          {
+            "bom-ref": "V8.3.7",
+            "identifier": "V8.3.7",
+            "text": "[DELETED, DUPLICATE OF 1.8.2]",
+            "parent": "V8.3"
+          },
+          {
+            "bom-ref": "V8.3.8",
+            "identifier": "V8.3.8",
+            "text": "[LEVEL L2 > L3] 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.",
+            "parent": "V8.3"
+          },
+          {
+            "bom-ref": "V8.3.9",
+            "identifier": "V8.3.9",
+            "text": "[ADDED] Verify that sensitive information is removed from the metadata of user-submitted files unless storage is consented to by the user.",
+            "parent": "V8.3"
+          },
+          {
+            "bom-ref": "V9",
+            "identifier": "V9",
+            "title": "Secure Communication"
+          },
+          {
+            "bom-ref": "V1.9",
+            "identifier": "V1.9",
+            "title": "Communications Documentation",
+            "parent": "V9"
+          },
+          {
+            "bom-ref": "V1.9.1",
+            "identifier": "V1.9.1",
+            "text": "[DELETED, DUPLICATE OF 9.1.1, 9.2.2, 9.3.1]",
+            "parent": "V1.9"
+          },
+          {
+            "bom-ref": "V1.9.2",
+            "identifier": "V1.9.2",
+            "text": "[DELETED, DUPLICATE OF 9.2.3, 9.3.2]",
+            "parent": "V1.9"
+          },
+          {
+            "bom-ref": "V9.1",
+            "identifier": "V9.1",
+            "title": "HTTPS Communication with External Facing Services",
+            "parent": "V9"
+          },
+          {
+            "bom-ref": "V9.1.1",
+            "identifier": "V9.1.1",
+            "text": "[MODIFIED] Verify that TLS is used for all connectivity between a client and external facing, HTTP-based services, and does not fall back to insecure or unencrypted communications.",
+            "parent": "V9.1"
+          },
+          {
+            "bom-ref": "V9.1.2",
+            "identifier": "V9.1.2",
+            "text": "[MOVED TO 9.4.1]",
+            "parent": "V9.1"
+          },
+          {
+            "bom-ref": "V9.1.3",
+            "identifier": "V9.1.3",
+            "text": "[MOVED TO 9.4.2]",
+            "parent": "V9.1"
+          },
+          {
+            "bom-ref": "V9.1.4",
+            "identifier": "V9.1.4",
+            "text": "[ADDED] Verify that external facing services use publicly trusted TLS certificates.",
+            "parent": "V9.1"
+          },
+          {
+            "bom-ref": "V9.2",
+            "identifier": "V9.2",
+            "title": "General Service to Service Communication Security",
+            "parent": "V9"
+          },
+          {
+            "bom-ref": "V9.2.1",
+            "identifier": "V9.2.1",
+            "text": "[MOVED TO 9.3.2]",
+            "parent": "V9.2"
+          },
+          {
+            "bom-ref": "V9.2.2",
+            "identifier": "V9.2.2",
+            "text": "[MODIFIED] Verify that an encrypted protocol such as TLS is used for all inbound and outbound connections to and from the application, including monitoring systems, management tools, remote access and SSH, middleware, databases, mainframes, partner systems, or external APIs. The server must not fall back to insecure or unencrypted protocols.",
+            "parent": "V9.2"
+          },
+          {
+            "bom-ref": "V9.2.3",
+            "identifier": "V9.2.3",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V9.2"
+          },
+          {
+            "bom-ref": "V9.2.4",
+            "identifier": "V9.2.4",
+            "text": "[MOVED TO 9.4.3]",
+            "parent": "V9.2"
+          },
+          {
+            "bom-ref": "V9.2.5",
+            "identifier": "V9.2.5",
+            "text": "[MOVED TO 7.2.6]",
+            "parent": "V9.2"
+          },
+          {
+            "bom-ref": "V9.2.6",
+            "identifier": "V9.2.6",
+            "text": "[ADDED] Verify that TLS clients validate certificates received before communicating with a TLS server.",
+            "parent": "V9.2"
+          },
+          {
+            "bom-ref": "V9.3",
+            "identifier": "V9.3",
+            "title": "HTTPS Communication between Internal Services",
+            "parent": "V9"
+          },
+          {
+            "bom-ref": "V9.3.1",
+            "identifier": "V9.3.1",
+            "text": "[ADDED] Verify that TLS or another appropriate transport encryption mechanism used for all connectivity between internal, HTTP-based services within the application, and does not fall back to insecure or unencrypted communications.",
+            "parent": "V9.3"
+          },
+          {
+            "bom-ref": "V9.3.2",
+            "identifier": "V9.3.2",
+            "text": "[MODIFIED, MOVED FROM 9.2.1] Verify that TLS connections between internal services use trusted certificates. Where internally generated or self-signed certificates are used, the consuming service must be configured to only trust specific internal CAs and specific self-signed certificates. All others should be rejected.",
+            "parent": "V9.3"
+          },
+          {
+            "bom-ref": "V9.3.3",
+            "identifier": "V9.3.3",
+            "text": "[MODIFIED, MOVED FROM 2.2.5] Verify that services communicating internally within a system (intra-service communications) use strong authentication to ensure that each endpoint is verified. Strong authentication methods, such as mTLS, should be employed to ensure identity, using public-key infrastructure and mechanisms that are resistant to replay attacks. For microservice architectures, consider using a service mesh to simplify certificate management and enhance security.",
+            "parent": "V9.3"
+          },
+          {
+            "bom-ref": "V9.4",
+            "identifier": "V9.4",
+            "title": "General TLS Security Guidance",
+            "parent": "V9"
+          },
+          {
+            "bom-ref": "V9.4.1",
+            "identifier": "V9.4.1",
+            "text": "[MODIFIED, MOVED FROM 9.1.2] Verify that only the latest recommended cipher suites are enabled, with the strongest cipher suites set as preferred. L3 applications must only support cipher suites which provide forward secrecy.",
+            "parent": "V9.4"
+          },
+          {
+            "bom-ref": "V9.4.2",
+            "identifier": "V9.4.2",
+            "text": "[MOVED FROM 9.1.3] Verify that only the latest recommended versions of the TLS protocol are enabled, such as TLS 1.2 and TLS 1.3. The latest version of the TLS protocol should be the preferred option.",
+            "parent": "V9.4"
+          },
+          {
+            "bom-ref": "V9.4.3",
+            "identifier": "V9.4.3",
+            "text": "[MOVED FROM 9.2.4] Verify that proper certification revocation, such as Online Certificate Status Protocol (OCSP) Stapling, is enabled and configured.",
+            "parent": "V9.4"
+          },
+          {
+            "bom-ref": "V9.4.4",
+            "identifier": "V9.4.4",
+            "text": "[ADDED] Verify that Encrypted Client Hello (ECH) is supported and properly configured within the application’s TLS settings to prevent exposure of sensitive metadata, such as the Server Name Indication (SNI), during TLS handshake processes.",
+            "parent": "V9.4"
+          },
+          {
+            "bom-ref": "V9.4.5",
+            "identifier": "V9.4.5",
+            "text": "[ADDED] Verify that the application validates that mTLS client certificates are trusted before using the certificate identity for authentication or authorization.",
+            "parent": "V9.4"
+          },
+          {
+            "bom-ref": "V10",
+            "identifier": "V10",
+            "title": "Secure Coding Architecture and Implementation"
+          },
+          {
+            "bom-ref": "V1.10",
+            "identifier": "V1.10",
+            "title": "Secure Coding Documentation",
+            "parent": "V10"
+          },
+          {
+            "bom-ref": "V1.10.1",
+            "identifier": "V1.10.1",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V1.10"
+          },
+          {
+            "bom-ref": "V1.10.2",
+            "identifier": "V1.10.2",
+            "text": "[MODIFIED, MOVED FROM 14.2.5, MERGED FROM 14.2.4] Verify that an inventory catalog, such as software bill of materials (SBOM), is maintained of all third-party libraries in use, including verifying that components come from pre-defined, trusted, and continually maintained repositories.",
+            "parent": "V1.10"
+          },
+          {
+            "bom-ref": "V1.10.3",
+            "identifier": "V1.10.3",
+            "text": "[ADDED, SPLIT FROM 14.2.6] Verify that application documentation highlights \"risky\" third party libraries which should include: libraries which perform operations which are dangerous from a security perspective, libraries which are poorly maintained, unsupported, or end of life, libraries which have historically had several significant vulnerabilities, etc.",
+            "parent": "V1.10"
+          },
+          {
+            "bom-ref": "V1.10.4",
+            "identifier": "V1.10.4",
+            "text": "[ADDED, SPLIT FROM 1.14.5] Verify that application documentation highlights parts of the application where \"risky\" operations are being performed. \"Risky\" in this context means those with a high likelihood of being dangerously exploited such as: deserialization of untrusted data, raw file parsing, direct memory manipulation, etc.",
+            "parent": "V1.10"
+          },
+          {
+            "bom-ref": "V10.1",
+            "identifier": "V10.1",
+            "title": "Code Integrity",
+            "parent": "V10"
+          },
+          {
+            "bom-ref": "V10.1.1",
+            "identifier": "V10.1.1",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V10.1"
+          },
+          {
+            "bom-ref": "V10.2",
+            "identifier": "V10.2",
+            "title": "Malicious Code Search",
+            "parent": "V10"
+          },
+          {
+            "bom-ref": "V10.2.1",
+            "identifier": "V10.2.1",
+            "text": "[DELETED, NOT PRACTICAL]",
+            "parent": "V10.2"
+          },
+          {
+            "bom-ref": "V10.2.2",
+            "identifier": "V10.2.2",
+            "text": "[DELETED, NOT PRACTICAL]",
+            "parent": "V10.2"
+          },
+          {
+            "bom-ref": "V10.2.3",
+            "identifier": "V10.2.3",
+            "text": "[DELETED, NOT PRACTICAL]",
+            "parent": "V10.2"
+          },
+          {
+            "bom-ref": "V10.2.4",
+            "identifier": "V10.2.4",
+            "text": "[DELETED, NOT PRACTICAL]",
+            "parent": "V10.2"
+          },
+          {
+            "bom-ref": "V10.2.5",
+            "identifier": "V10.2.5",
+            "text": "[DELETED, NOT PRACTICAL]",
+            "parent": "V10.2"
+          },
+          {
+            "bom-ref": "V10.2.6",
+            "identifier": "V10.2.6",
+            "text": "[DELETED, NOT PRACTICAL]",
+            "parent": "V10.2"
+          },
+          {
+            "bom-ref": "V10.3",
+            "identifier": "V10.3",
+            "title": "Application Integrity",
+            "parent": "V10"
+          },
+          {
+            "bom-ref": "V10.3.1",
+            "identifier": "V10.3.1",
+            "text": "[MODIFIED, LEVEL L1 > L3] Verify that, if the application has an auto-update feature, updates should be digitally signed, with the digital signature being validated before installing or executing the update.",
+            "parent": "V10.3"
+          },
+          {
+            "bom-ref": "V10.3.2",
+            "identifier": "V10.3.2",
+            "text": "[MOVED TO 10.6.2]",
+            "parent": "V10.3"
+          },
+          {
+            "bom-ref": "V10.3.3",
+            "identifier": "V10.3.3",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V10.3"
+          },
+          {
+            "bom-ref": "V10.4",
+            "identifier": "V10.4",
+            "title": "Defensive Coding",
+            "parent": "V10"
+          },
+          {
+            "bom-ref": "V10.4.1",
+            "identifier": "V10.4.1",
+            "text": "[ADDED] Verify that the application explicitly ensures that variables are of the correct type and performs strict equality and comparator operations to avoid type juggling or type confusion vulnerabilities caused by the application code making an assumption about a variable type.",
+            "parent": "V10.4"
+          },
+          {
+            "bom-ref": "V10.4.2",
+            "identifier": "V10.4.2",
+            "text": "[ADDED] Verify that the application avoids DOM clobbering when using client-side JavaScript by employing explicit variable declarations, performing strict type checking, avoiding storing global variables on the document object, and implementing namespace isolation.",
+            "parent": "V10.4"
+          },
+          {
+            "bom-ref": "V10.4.3",
+            "identifier": "V10.4.3",
+            "text": "[ADDED] Verify that JavaScript code is written in a way that prevents prototype pollution, for example, by using Set() or Map() instead of object literals.",
+            "parent": "V10.4"
+          },
+          {
+            "bom-ref": "V10.4.4",
+            "identifier": "V10.4.4",
+            "text": "[MODIFIED, MOVED FROM 5.1.2] Verify that the application has countermeasures to protect against mass assignment attacks by limiting allowed fields per controller and action, e.g. it is not possible to insert or update a field value when it was not intended to be part of that action.",
+            "parent": "V10.4"
+          },
+          {
+            "bom-ref": "V10.4.5",
+            "identifier": "V10.4.5",
+            "text": "[ADDED] Verify that the application only returns data which the user has permission to access. For example, the API response does not return a full object with attributes that contain values the user has no permission to access, despite having permission to access the data object itself.",
+            "parent": "V10.4"
+          },
+          {
+            "bom-ref": "V10.4.6",
+            "identifier": "V10.4.6",
+            "text": "[ADDED] Verify that the application is able to discern and utilizes the user's true IP address to provide for sensitive functions, including rate limiting and logging.",
+            "parent": "V10.4"
+          },
+          {
+            "bom-ref": "V10.5.1",
+            "identifier": "V10.5.1",
+            "text": "[ADDED, SPLIT FROM 1.14.5, 14.2.6] Verify that the application implements additional protections around parts of the application which are documented as performing \"risky\" operations or using \"risky\" third-party libraries. This could include techniques such as sandboxing, encapsulation, containerization or network level isolation to delay and deter attackers who compromise one part of an application from pivoting elsewhere in the application.",
+            "parent": "V10.4"
+          },
+          {
+            "bom-ref": "V10.6.1",
+            "identifier": "V10.6.1",
+            "text": "[MODIFIED, MOVED FROM 14.2.1] Verify that all components are up to date.",
+            "parent": "V10.4"
+          },
+          {
+            "bom-ref": "V10.6.2",
+            "identifier": "V10.6.2",
+            "text": "[MODIFIED, MOVED FROM 10.3.2] Verify that third-party components and all of their transitive dependencies are included from the expected repository, whether internally owned or an external source, and that there is no risk of a dependency confusion attack.",
+            "parent": "V10.4"
+          },
+          {
+            "bom-ref": "V10.7",
+            "identifier": "V10.7",
+            "title": "Concurrency",
+            "parent": "V10"
+          },
+          {
+            "bom-ref": "V10.7.1",
+            "identifier": "V10.7.1",
+            "text": "[MODIFIED, MOVED FROM 1.11.3] Verify that only thread-safe types are used in multi-threaded contexts, or that non-thread-safe types are properly synchronized to prevent race conditions.",
+            "parent": "V10.7"
+          },
+          {
+            "bom-ref": "V10.7.2",
+            "identifier": "V10.7.2",
+            "text": "[MODIFIED, MOVED FROM 1.11.2, LEVEL L2 > L3] Verify that concurrent access to shared resources is controlled using synchronization primitives (e.g., locks, mutexes, semaphores) to prevent race conditions and ensure atomic operations on these resources.",
+            "parent": "V10.7"
+          },
+          {
+            "bom-ref": "V10.7.3",
+            "identifier": "V10.7.3",
+            "text": "[MODIFIED, MOVED FROM 11.1.6] Verify that all access to shared resources is consistently checked and accessed in a single atomic operation to prevent Time-of-Check to Time-of-Use (TOC/TOU) race conditions, ensuring resource state consistency between check and use.",
+            "parent": "V10.7"
+          },
+          {
+            "bom-ref": "V10.7.4",
+            "identifier": "V10.7.4",
+            "text": "[ADDED] Verify that resource acquisition uses a consistent locking strategy to avoid circular dependencies and ensure forward progress, preventing both deadlocks and livelock scenarios.",
+            "parent": "V10.7"
+          },
+          {
+            "bom-ref": "V10.7.5",
+            "identifier": "V10.7.5",
+            "text": "[ADDED] Verify that resource allocation policies prevent thread starvation by ensuring fair access to resources, such as by leveraging thread pools, allowing lower-priority threads to proceed within a reasonable timeframe.",
+            "parent": "V10.7"
+          },
+          {
+            "bom-ref": "V10.7.6",
+            "identifier": "V10.7.6",
+            "text": "[ADDED] Verify that locking primitives are only accessible to the owning class or module and are not publicly modifiable, ensuring that locks cannot be inadvertently or maliciously modified by external classes or code.",
+            "parent": "V10.7"
+          },
+          {
+            "bom-ref": "V11",
+            "identifier": "V11",
+            "title": "Business Logic"
+          },
+          {
+            "bom-ref": "V1.11",
+            "identifier": "V1.11",
+            "title": "Business Logic Documentation",
+            "parent": "V11"
+          },
+          {
+            "bom-ref": "V1.11.1",
+            "identifier": "V1.11.1",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V1.11"
+          },
+          {
+            "bom-ref": "V1.11.2",
+            "identifier": "V1.11.2",
+            "text": "[MOVED TO 10.7.2]",
+            "parent": "V1.11"
+          },
+          {
+            "bom-ref": "V1.11.3",
+            "identifier": "V1.11.3",
+            "text": "[MOVED TO 10.7.1]",
+            "parent": "V1.11"
+          },
+          {
+            "bom-ref": "V1.11.4",
+            "identifier": "V1.11.4",
+            "text": "[ADDED] Verify that expectations for business logic limits and validations are clearly documented including both per-user and also globally across the application.",
+            "parent": "V1.11"
+          },
+          {
+            "bom-ref": "V11.1",
+            "identifier": "V11.1",
+            "title": "Business Logic Security",
+            "parent": "V11"
+          },
+          {
+            "bom-ref": "V11.1.1",
+            "identifier": "V11.1.1",
+            "text": "Verify that the application will only process business logic flows for the same user in sequential step order and without skipping steps.",
+            "parent": "V11.1"
+          },
+          {
+            "bom-ref": "V11.1.2",
+            "identifier": "V11.1.2",
+            "text": "[MOVED TO 11.2.1]",
+            "parent": "V11.1"
+          },
+          {
+            "bom-ref": "V11.1.3",
+            "identifier": "V11.1.3",
+            "text": "[MODIFIED, MERGED FROM 11.1.5] Verify that business logic limits and validations are implemented as per the application's documentation, to avoid business logic flaws being exploited such as buying items for a negative amount.",
+            "parent": "V11.1"
+          },
+          {
+            "bom-ref": "V11.1.4",
+            "identifier": "V11.1.4",
+            "text": "[MOVED TO 11.2.2]",
+            "parent": "V11.1"
+          },
+          {
+            "bom-ref": "V11.1.5",
+            "identifier": "V11.1.5",
+            "text": "[DELETED, MERGED TO 11.1.3]",
+            "parent": "V11.1"
+          },
+          {
+            "bom-ref": "V11.1.6",
+            "identifier": "V11.1.6",
+            "text": "[MOVED TO 10.7.3]",
+            "parent": "V11.1"
+          },
+          {
+            "bom-ref": "V11.1.7",
+            "identifier": "V11.1.7",
+            "text": "[MOVED TO 7.2.4]",
+            "parent": "V11.1"
+          },
+          {
+            "bom-ref": "V11.1.8",
+            "identifier": "V11.1.8",
+            "text": "[MOVED TO 7.2.5]",
+            "parent": "V11.1"
+          },
+          {
+            "bom-ref": "V11.1.9",
+            "identifier": "V11.1.9",
+            "text": "[ADDED] Verify that \"atomic transactions\" are being used at the business logic level such that either a business logic operation succeeds in its entirety, or it is rolled back to the previous correct state.",
+            "parent": "V11.1"
+          },
+          {
+            "bom-ref": "V11.1.10",
+            "identifier": "V11.1.10",
+            "text": "[ADDED] Verify that very high-value business logic flows are restricted with multi-user approval to prevent unauthorized or accidental actions. This could include but is not limited to large monetary transfers, contract approvals, access to critical nuclear facility operations, healthcare record modifications, access to classified information, or safety overrides in manufacturing.",
+            "parent": "V11.1"
+          },
+          {
+            "bom-ref": "V11.2",
+            "identifier": "V11.2",
+            "title": "Anti-automation",
+            "parent": "V11"
+          },
+          {
+            "bom-ref": "V11.2.1",
+            "identifier": "V11.2.1",
+            "text": "[MODIFIED, MOVED FROM 11.1.2, LEVEL L1 > L3] Verify that business logic processes require realistic human timing, preventing excessively rapid transaction submissions.",
+            "parent": "V11.2"
+          },
+          {
+            "bom-ref": "V11.2.2",
+            "identifier": "V11.2.2",
+            "text": "[MODIFIED, MOVED FROM 11.1.4, LEVEL L1 > L2] Verify that anti-automation controls are in place to protect against excessive calls to application functions that could lead to data exfiltration, garbage data creation, quota exhaustion, rate limit breaches, denial of service, or overuse of costly resources.",
+            "parent": "V11.2"
+          },
+          {
+            "bom-ref": "V12",
+            "identifier": "V12",
+            "title": "File and Resources"
+          },
+          {
+            "bom-ref": "V1.12",
+            "identifier": "V1.12",
+            "title": "Secure File Upload Documentation",
+            "parent": "V12"
+          },
+          {
+            "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": "[DELETED, MERGED TO 50.6.1]",
+            "parent": "V1.12"
+          },
+          {
+            "bom-ref": "V1.12.3",
+            "identifier": "V1.12.3",
+            "text": "[ADDED] Verify that, if the application allows uploading files, the documentation defines the permitted file types, expected file extensions, and maximum size (including unpacked size) for each upload feature. Additionally, ensure that the documentation specifies how files are made safe for end-users to download and process.",
+            "parent": "V1.12"
+          },
+          {
+            "bom-ref": "V12.1",
+            "identifier": "V12.1",
+            "title": "File Upload",
+            "parent": "V12"
+          },
+          {
+            "bom-ref": "V12.1.1",
+            "identifier": "V12.1.1",
+            "text": "[MODIFIED] Verify that the application will only accept files of a size which it can process without causing a loss of performance or denial of service attack.",
+            "parent": "V12.1"
+          },
+          {
+            "bom-ref": "V12.1.2",
+            "identifier": "V12.1.2",
+            "text": "Verify that the application checks compressed files (e.g. zip, gz, docx, odt) against maximum allowed uncompressed size and against maximum number of files before uncompressing the file.",
+            "parent": "V12.1"
+          },
+          {
+            "bom-ref": "V12.1.3",
+            "identifier": "V12.1.3",
+            "text": "Verify that a file size quota and maximum number of files per user is enforced to ensure that a single user cannot fill up the storage with too many files, or excessively large files.",
+            "parent": "V12.1"
+          },
+          {
+            "bom-ref": "V12.1.4",
+            "identifier": "V12.1.4",
+            "text": "[ADDED] Verify that the application does not allow uploading compressed files containing symlinks unless this is specifically required (in which case it will be necessary to enforce an allowlist of the files that can be symlinked to).",
+            "parent": "V12.1"
+          },
+          {
+            "bom-ref": "V12.2",
+            "identifier": "V12.2",
+            "title": "File Integrity and Content",
+            "parent": "V12"
+          },
+          {
+            "bom-ref": "V12.2.1",
+            "identifier": "V12.2.1",
+            "text": "[MODIFIED] Verify that when the application accepts a file, either on its own or within an archive such as a zip file, it checks if the file extension matches an expected file extension and validates that the contents correspond to the type represented by the extension. This includes, but is not limited to, checking the initial 'magic bytes', performing image re-writing, and using specialized libraries for file content validation.",
+            "parent": "V12.2"
+          },
+          {
+            "bom-ref": "V12.2.2",
+            "identifier": "V12.2.2",
+            "text": "[ADDED] Verify that the application blocks uploaded images with a pixel size larger than the maximum allowed, to prevent pixel flood attacks.",
+            "parent": "V12.2"
+          },
+          {
+            "bom-ref": "V12.3",
+            "identifier": "V12.3",
+            "title": "File Execution",
+            "parent": "V12"
+          },
+          {
+            "bom-ref": "V12.3.1",
+            "identifier": "V12.3.1",
+            "text": "[MODIFIED, MERGED FROM 12.3.2, 12.3.3, 5.3.9] Verify that file operations avoid using user-submitted filenames or file metadata when creating file paths to protect against path traversal, local or remote file inclusion (LFI, RFI), and server-side request forgery (SSRF) attacks. Instead, use internal, trusted data for file I/O. If user-submitted filenames or file metadata must be used, strict validation and sanitization must be applied.",
+            "parent": "V12.3"
+          },
+          {
+            "bom-ref": "V12.3.2",
+            "identifier": "V12.3.2",
+            "text": "[DELETED, MERGED TO 12.3.1]",
+            "parent": "V12.3"
+          },
+          {
+            "bom-ref": "V12.3.3",
+            "identifier": "V12.3.3",
+            "text": "[DELETED, MERGED TO 12.3.1]",
+            "parent": "V12.3"
+          },
+          {
+            "bom-ref": "V12.3.4",
+            "identifier": "V12.3.4",
+            "text": "[MOVED TO 12.5.3]",
+            "parent": "V12.3"
+          },
+          {
+            "bom-ref": "V12.3.5",
+            "identifier": "V12.3.5",
+            "text": "[DELETED, DUPLICATE OF 5.3.8]",
+            "parent": "V12.3"
+          },
+          {
+            "bom-ref": "V12.3.6",
+            "identifier": "V12.3.6",
+            "text": "[DELETED, DUPLICATE OF 14.2.4]",
+            "parent": "V12.3"
+          },
+          {
+            "bom-ref": "V12.3.7",
+            "identifier": "V12.3.7",
+            "text": "[ADDED] Verify that server-side file processing such as file decompression ignores user-provided path information to prevent vulnerabilities such as zip slip.",
+            "parent": "V12.3"
+          },
+          {
+            "bom-ref": "V12.4",
+            "identifier": "V12.4",
+            "title": "File Storage",
+            "parent": "V12"
+          },
+          {
+            "bom-ref": "V12.4.1",
+            "identifier": "V12.4.1",
+            "text": "[MODIFIED] Verify that files uploaded or generated by untrusted input which are stored in a public folder are not executable as server-side program code when accessed directly by an end user.",
+            "parent": "V12.4"
+          },
+          {
+            "bom-ref": "V12.4.2",
+            "identifier": "V12.4.2",
+            "text": "Verify that files obtained from untrusted sources are scanned by antivirus scanners to prevent upload and serving of known malicious content.",
+            "parent": "V12.4"
+          },
+          {
+            "bom-ref": "V12.5",
+            "identifier": "V12.5",
+            "title": "File Download",
+            "parent": "V12"
+          },
+          {
+            "bom-ref": "V12.5.1",
+            "identifier": "V12.5.1",
+            "text": "[MOVED TO 14.3.6]",
+            "parent": "V12.5"
+          },
+          {
+            "bom-ref": "V12.5.2",
+            "identifier": "V12.5.2",
+            "text": "[MOVED TO 50.6.1]",
+            "parent": "V12.5"
+          },
+          {
+            "bom-ref": "V12.5.3",
+            "identifier": "V12.5.3",
+            "text": "[MODIFIED, MOVED FROM 12.3.4] Verify that the application validates or ignores user-submitted filenames, including in a JSON, JSONP, or URL parameter and specifies a filename in the Content-Disposition header field in the response.",
+            "parent": "V12.5"
+          },
+          {
+            "bom-ref": "V12.5.4",
+            "identifier": "V12.5.4",
+            "text": "[ADDED] Verify that file names served (e.g., in HTTP response header fields or email attachments) are encoded or sanitized (e.g., following RFC 6266) to preserve document structure and prevent injection attacks.",
+            "parent": "V12.5"
+          },
+          {
+            "bom-ref": "V12.6",
+            "identifier": "V12.6",
+            "title": "SSRF Protection",
+            "parent": "V12"
+          },
+          {
+            "bom-ref": "V12.6.1",
+            "identifier": "V12.6.1",
+            "text": "[MOVED TO 14.6.1]",
+            "parent": "V12.6"
+          },
+          {
+            "bom-ref": "V12.7",
+            "identifier": "V12.7",
+            "title": "Application Resources",
+            "parent": "V12"
+          },
+          {
+            "bom-ref": "V12.7.1",
+            "identifier": "V12.7.1",
+            "text": "[ADDED] Verify that the application proactively releases system resources, such as database connections, open files, threads, etc, when it finishes using them to prevent resource exhaustion.",
+            "parent": "V12.7"
+          },
+          {
+            "bom-ref": "V13",
+            "identifier": "V13",
+            "title": "API and Web Service"
+          },
+          {
+            "bom-ref": "V1.13",
+            "identifier": "V1.13",
+            "title": "API and Web Service Documentation",
+            "parent": "V13"
+          },
+          {
+            "bom-ref": "V13.1",
+            "identifier": "V13.1",
+            "title": "Generic Web Service Security",
+            "parent": "V13"
+          },
+          {
+            "bom-ref": "V13.1.1",
+            "identifier": "V13.1.1",
+            "text": "[MOVED TO 5.5.5]",
+            "parent": "V13.1"
+          },
+          {
+            "bom-ref": "V13.1.2",
+            "identifier": "V13.1.2",
+            "text": "[DELETED, DUPLICATE OF 4.3.1]",
+            "parent": "V13.1"
+          },
+          {
+            "bom-ref": "V13.1.3",
+            "identifier": "V13.1.3",
+            "text": "[DELETED, MERGED TO 8.3.1]",
+            "parent": "V13.1"
+          },
+          {
+            "bom-ref": "V13.1.4",
+            "identifier": "V13.1.4",
+            "text": "[DELETED, DUPLICATE OF 4.2.1]",
+            "parent": "V13.1"
+          },
+          {
+            "bom-ref": "V13.1.5",
+            "identifier": "V13.1.5",
+            "text": "[DELETED, INSUFFICIENT IMPACT]",
+            "parent": "V13.1"
+          },
+          {
+            "bom-ref": "V13.1.6",
+            "identifier": "V13.1.6",
+            "text": "[MODIFIED, MOVED FROM 13.2.6, LEVEL L2 > L3] Verify that per-message digital signatures are used to provide additional assurance on top of transport protections for requests or transactions which are highly sensitive or which traverse a number of systems.",
+            "parent": "V13.1"
+          },
+          {
+            "bom-ref": "V13.1.7",
+            "identifier": "V13.1.7",
+            "text": "[MODIFIED, MOVED FROM 14.4.1] Verify that every HTTP response with a message body contains a Content-Type header field that matches the actual content of the response, including the charset parameter to specify safe character encoding (e.g., UTF-8, ISO-8859-1) according to IANA Media Types, such as \"text/\", \"/+xml\" and \"/xml\".",
+            "parent": "V13.1"
+          },
+          {
+            "bom-ref": "V13.1.8",
+            "identifier": "V13.1.8",
+            "text": "[ADDED] Verify that HTTPS-based endpoints either return an error or do not respond to unencrypted HTTP requests which contain sensitive data in the headers or body. If a client is erroneously sending unencrypted HTTP requests but the requests are being automatically redirected to HTTPS, this leakage of sensitive data may go undiscovered.",
+            "parent": "V13.1"
+          },
+          {
+            "bom-ref": "V13.2",
+            "identifier": "V13.2",
+            "title": "Web Services",
+            "parent": "V13"
+          },
+          {
+            "bom-ref": "V13.2.1",
+            "identifier": "V13.2.1",
+            "text": "[MOVED TO 13.6.2]",
+            "parent": "V13.2"
+          },
+          {
+            "bom-ref": "V13.2.2",
+            "identifier": "V13.2.2",
+            "text": "[MODIFIED, MERGED FROM 13.3.1, LEVEL L1 > L3] Verify that structured data objects are validated to ensure they are properly formed, followed by validation of each input field before any processing of that data takes place. This could involve implementing schema validation for formats like JSON and XML.",
+            "parent": "V13.2"
+          },
+          {
+            "bom-ref": "V13.2.3",
+            "identifier": "V13.2.3",
+            "text": "[DELETED, MERGED TO 50.4.1]",
+            "parent": "V13.2"
+          },
+          {
+            "bom-ref": "V13.2.4",
+            "identifier": "V13.2.4",
+            "text": "[DELETED, DUPLICATE OF 11.1.4]",
+            "parent": "V13.2"
+          },
+          {
+            "bom-ref": "V13.2.5",
+            "identifier": "V13.2.5",
+            "text": "Verify that REST services explicitly check the incoming Content-Type to be the expected one, such as application/xml or application/json.",
+            "parent": "V13.2"
+          },
+          {
+            "bom-ref": "V13.2.6",
+            "identifier": "V13.2.6",
+            "text": "[MOVED TO 13.1.6]",
+            "parent": "V13.2"
+          },
+          {
+            "bom-ref": "V13.3",
+            "identifier": "V13.3",
+            "title": "SOAP Web Service",
+            "parent": "V13"
+          },
+          {
+            "bom-ref": "V13.3.1",
+            "identifier": "V13.3.1",
+            "text": "[DELETED, MERGED TO 13.2.2]",
+            "parent": "V13.3"
+          },
+          {
+            "bom-ref": "V13.3.2",
+            "identifier": "V13.3.2",
+            "text": "[DELETED, DUPLICATE OF 13.2.6]",
+            "parent": "V13.3"
+          },
+          {
+            "bom-ref": "V13.4",
+            "identifier": "V13.4",
+            "title": "GraphQL",
+            "parent": "V13"
+          },
+          {
+            "bom-ref": "V13.4.1",
+            "identifier": "V13.4.1",
+            "text": "[GRAMMAR] Verify that a query allowlist or a combination of depth limiting and amount limiting is 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.",
+            "parent": "V13.4"
+          },
+          {
+            "bom-ref": "V13.4.2",
+            "identifier": "V13.4.2",
+            "text": "[MODIFIED] Verify that authorization logic is implemented at the business logic layer instead of the GraphQL or resolver layer.",
+            "parent": "V13.4"
+          },
+          {
+            "bom-ref": "V13.4.3",
+            "identifier": "V13.4.3",
+            "text": "[ADDED] Verify that GraphQL introspection queries are disabled in the production environment unless the GraphQL API is meant to be used by other parties.",
+            "parent": "V13.4"
+          },
+          {
+            "bom-ref": "V13.5",
+            "identifier": "V13.5",
+            "title": "WebSocket",
+            "parent": "V13"
+          },
+          {
+            "bom-ref": "V13.5.1",
+            "identifier": "V13.5.1",
+            "text": "[ADDED] Verify that WebSocket over TLS (WSS) is used for all WebSocket connections.",
+            "parent": "V13.5"
+          },
+          {
+            "bom-ref": "V13.5.2",
+            "identifier": "V13.5.2",
+            "text": "[ADDED] Verify that, during the initial HTTP WebSocket handshake, the Origin header field is checked against a list of origins allowed for the application.",
+            "parent": "V13.5"
+          },
+          {
+            "bom-ref": "V13.5.3",
+            "identifier": "V13.5.3",
+            "text": "[ADDED] Verify that, if the application's standard session management cannot be used, dedicated tokens are being used for this which comply with the relevant Session Management security requirements.",
+            "parent": "V13.5"
+          },
+          {
+            "bom-ref": "V13.5.4",
+            "identifier": "V13.5.4",
+            "text": "[ADDED] Verify that dedicated WebSocket session management tokens are initially obtained or validated through the previously authenticated HTTPS session when transitioning an existing HTTPS session to a WebSocket channel.",
+            "parent": "V13.5"
+          },
+          {
+            "bom-ref": "V13.6",
+            "identifier": "V13.6",
+            "title": "HTTP Request Header Validation",
+            "parent": "V13"
+          },
+          {
+            "bom-ref": "V13.6.1",
+            "identifier": "V13.6.1",
+            "text": "[MODIFIED, MOVED FROM 14.5.1] Verify that the application only responds to HTTP methods in use by the application or by the API (including OPTIONS during preflight requests) and unused methods (e.g. TRACE) are blocked.",
+            "parent": "V13.6"
+          },
+          {
+            "bom-ref": "V13.6.2",
+            "identifier": "V13.6.2",
+            "text": "[MODIFIED, MOVED FROM 13.2.1] Verify that HTTP requests using the HEAD, OPTIONS, TRACE or GET verb do not modify any backend data structure or perform any state-changing actions. These requests are safe methods and should therefore not have any side effects.",
+            "parent": "V13.6"
+          },
+          {
+            "bom-ref": "V13.6.3",
+            "identifier": "V13.6.3",
+            "text": "[ADDED] Verify that all application components, including load balancers, firewalls, and application servers, comply with RFC 2616 by ignoring the Content-Length header field when a Transfer-Encoding header field is present, to prevent HTTP Request Smuggling.",
+            "parent": "V13.6"
+          },
+          {
+            "bom-ref": "V13.6.4",
+            "identifier": "V13.6.4",
+            "text": "[ADDED] Verify that any HTTP header field used by the application and defined by intermediary devices like load balancers or proxies, such as X-Real-IP and X-Forwarded-*, cannot be overridden by the end-user.",
+            "parent": "V13.6"
+          },
+          {
+            "bom-ref": "V13.7",
+            "identifier": "V13.7",
+            "title": "HTTP/2",
+            "parent": "V13"
+          },
+          {
+            "bom-ref": "V13.7.1",
+            "identifier": "V13.7.1",
+            "text": "[ADDED] Verify that the value in the Content-Length request header field matches the calculated length using the built-in mechanism.",
+            "parent": "V13.7"
+          },
+          {
+            "bom-ref": "V13.7.2",
+            "identifier": "V13.7.2",
+            "text": "[ADDED] Verify that all Transfer-Encoding header fields are stripped from the message or that the request is blocked entirely.",
+            "parent": "V13.7"
+          },
+          {
+            "bom-ref": "V13.7.3",
+            "identifier": "V13.7.3",
+            "text": "[ADDED] Verify that a full CRLF (\\r\\n) sequence is neutralized inside a HTTP/2 header.",
+            "parent": "V13.7"
+          },
+          {
+            "bom-ref": "V14",
+            "identifier": "V14",
+            "title": "Configuration"
+          },
+          {
+            "bom-ref": "V1.14",
+            "identifier": "V1.14",
+            "title": "Configuration Documentation",
+            "parent": "V14"
+          },
+          {
+            "bom-ref": "V1.14.1",
+            "identifier": "V1.14.1",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V1.14"
+          },
+          {
+            "bom-ref": "V1.14.2",
+            "identifier": "V1.14.2",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V1.14"
+          },
+          {
+            "bom-ref": "V1.14.3",
+            "identifier": "V1.14.3",
+            "text": "[DELETED, DUPLICATE OF 14.2.1]",
+            "parent": "V1.14"
+          },
+          {
+            "bom-ref": "V1.14.4",
+            "identifier": "V1.14.4",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V1.14"
+          },
+          {
+            "bom-ref": "V1.14.5",
+            "identifier": "V1.14.5",
+            "text": "[SPLIT TO 1.10.4, 10.5.1]",
+            "parent": "V1.14"
+          },
+          {
+            "bom-ref": "V1.14.6",
+            "identifier": "V1.14.6",
+            "text": "[MOVED TO 50.8.2]",
+            "parent": "V1.14"
+          },
+          {
+            "bom-ref": "V1.14.7",
+            "identifier": "V1.14.7",
+            "text": "[MODIFIED, MOVED FROM 1.1.5] Verify that all communication needs for the application are documented. This should include external services which the application relies upon and cases where an end user might be able to provide an external location to which the application will then connect.",
+            "parent": "V1.14"
+          },
+          {
+            "bom-ref": "V14.1",
+            "identifier": "V14.1",
+            "title": "Build and Deploy",
+            "parent": "V14"
+          },
+          {
+            "bom-ref": "V14.1.1",
+            "identifier": "V14.1.1",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V14.1"
+          },
+          {
+            "bom-ref": "V14.1.2",
+            "identifier": "V14.1.2",
+            "text": "[LEVEL L2 > L3] 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.",
+            "parent": "V14.1"
+          },
+          {
+            "bom-ref": "V14.1.3",
+            "identifier": "V14.1.3",
+            "text": "[MODIFIED] Verify that configuration hardening is performed on all third-party products, libraries, frameworks and services as per their individual recommendations.",
+            "parent": "V14.1"
+          },
+          {
+            "bom-ref": "V14.1.4",
+            "identifier": "V14.1.4",
+            "text": "[DELETED, NOT IN SCOPE]",
+            "parent": "V14.1"
+          },
+          {
+            "bom-ref": "V14.1.5",
+            "identifier": "V14.1.5",
+            "text": "[MODIFIED] Verify that deployed environments are short lived and frequently redeployed to a \"known good\" but updated state. Alternatively, long lived environments should use some form of \"drift prevention\" to ensure that deployed configurations are not changed to an insecure state.",
+            "parent": "V14.1"
+          },
+          {
+            "bom-ref": "V14.1.6",
+            "identifier": "V14.1.6",
+            "text": "[MOVED FROM 14.2.2] Verify that all unneeded features, documentation, sample applications and configurations are removed.",
+            "parent": "V14.1"
+          },
+          {
+            "bom-ref": "V14.1.7",
+            "identifier": "V14.1.7",
+            "text": "[ADDED] Verify that production environment does not include test code.",
+            "parent": "V14.1"
+          },
+          {
+            "bom-ref": "V14.1.8",
+            "identifier": "V14.1.8",
+            "text": "[ADDED] Verify that data, state information, and server instances related to the build and deployment process do not persist after the process has ended. (Ephemerality).",
+            "parent": "V14.1"
+          },
+          {
+            "bom-ref": "V14.1.9",
+            "identifier": "V14.1.9",
+            "text": "[ADDED] Verify that application code or functionality can only be changed via the standard update or build process and not directly in production through application functionality or some other direct modification mechanism.",
+            "parent": "V14.1"
+          },
+          {
+            "bom-ref": "V14.1.10",
+            "identifier": "V14.1.10",
+            "text": "[MODIFIED, MOVED FROM 2.5.4] Verify that default user accounts (e.g. \"root\", \"admin\", or \"sa\") are not present in the application or are disabled.",
+            "parent": "V14.1"
+          },
+          {
+            "bom-ref": "V14.2",
+            "identifier": "V14.2",
+            "title": "Dependency",
+            "parent": "V14"
+          },
+          {
+            "bom-ref": "V14.2.1",
+            "identifier": "V14.2.1",
+            "text": "[MOVED TO 10.6.1]",
+            "parent": "V14.2"
+          },
+          {
+            "bom-ref": "V14.2.2",
+            "identifier": "V14.2.2",
+            "text": "[MOVED TO 14.1.6]",
+            "parent": "V14.2"
+          },
+          {
+            "bom-ref": "V14.2.3",
+            "identifier": "V14.2.3",
+            "text": "[MOVED TO 50.7.1]",
+            "parent": "V14.2"
+          },
+          {
+            "bom-ref": "V14.2.4",
+            "identifier": "V14.2.4",
+            "text": "[DELETED, MERGED TO 1.10.2]",
+            "parent": "V14.2"
+          },
+          {
+            "bom-ref": "V14.2.5",
+            "identifier": "V14.2.5",
+            "text": "[MOVED TO 1.10.2]",
+            "parent": "V14.2"
+          },
+          {
+            "bom-ref": "V14.2.6",
+            "identifier": "V14.2.6",
+            "text": "[SPLIT TO 1.10.3, 10.5.1]",
+            "parent": "V14.2"
+          },
+          {
+            "bom-ref": "V14.3",
+            "identifier": "V14.3",
+            "title": "Unintended Information Leakage",
+            "parent": "V14"
+          },
+          {
+            "bom-ref": "V14.3.1",
+            "identifier": "V14.3.1",
+            "text": "[DELETED, DUPLICATE OF 7.4.1]",
+            "parent": "V14.3"
+          },
+          {
+            "bom-ref": "V14.3.2",
+            "identifier": "V14.3.2",
+            "text": "[MODIFIED] Verify that debug modes are disabled in production environments for every component to prevent exposure of debug features and unintended information leakage.",
+            "parent": "V14.3"
+          },
+          {
+            "bom-ref": "V14.3.3",
+            "identifier": "V14.3.3",
+            "text": "[MODIFIED] Verify that the application does not expose detailed version information of server-side components.",
+            "parent": "V14.3"
+          },
+          {
+            "bom-ref": "V14.3.4",
+            "identifier": "V14.3.4",
+            "text": "[ADDED, SPLIT FROM 4.3.2] Verify that directory browsing is disabled unless deliberately desired.",
+            "parent": "V14.3"
+          },
+          {
+            "bom-ref": "V14.3.5",
+            "identifier": "V14.3.5",
+            "text": "[ADDED, SPLIT FROM 4.3.2] Verify that the application does not allow discovery or disclosure of file or directory metadata, such as Thumbs.db, .DS_Store, .git or .svn folders.",
+            "parent": "V14.3"
+          },
+          {
+            "bom-ref": "V14.3.6",
+            "identifier": "V14.3.6",
+            "text": "[GRAMMAR, MOVED FROM 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.",
+            "parent": "V14.3"
+          },
+          {
+            "bom-ref": "V14.4",
+            "identifier": "V14.4",
+            "title": "HTTP Security Headers",
+            "parent": "V14"
+          },
+          {
+            "bom-ref": "V14.4.1",
+            "identifier": "V14.4.1",
+            "text": "[MOVED TO 13.1.7]",
+            "parent": "V14.4"
+          },
+          {
+            "bom-ref": "V14.4.2",
+            "identifier": "V14.4.2",
+            "text": "[DELETED, MERGED TO 50.6.1]",
+            "parent": "V14.4"
+          },
+          {
+            "bom-ref": "V14.4.3",
+            "identifier": "V14.4.3",
+            "text": "[MOVED TO 50.3.1]",
+            "parent": "V14.4"
+          },
+          {
+            "bom-ref": "V14.4.4",
+            "identifier": "V14.4.4",
+            "text": "[MOVED TO 50.3.2]",
+            "parent": "V14.4"
+          },
+          {
+            "bom-ref": "V14.4.5",
+            "identifier": "V14.4.5",
+            "text": "[MOVED TO 50.3.3]",
+            "parent": "V14.4"
+          },
+          {
+            "bom-ref": "V14.4.6",
+            "identifier": "V14.4.6",
+            "text": "[MOVED TO 50.3.4]",
+            "parent": "V14.4"
+          },
+          {
+            "bom-ref": "V14.4.7",
+            "identifier": "V14.4.7",
+            "text": "[MOVED TO 50.3.5]",
+            "parent": "V14.4"
+          },
+          {
+            "bom-ref": "V14.5",
+            "identifier": "V14.5",
+            "title": "HTTP Request Header Validation",
+            "parent": "V14"
+          },
+          {
+            "bom-ref": "V14.5.1",
+            "identifier": "V14.5.1",
+            "text": "[MOVED TO 13.6.1]",
+            "parent": "V14.5"
+          },
+          {
+            "bom-ref": "V14.5.2",
+            "identifier": "V14.5.2",
+            "text": "[DELETED, DUPLICATE OF 4.1.1]",
+            "parent": "V14.5"
+          },
+          {
+            "bom-ref": "V14.5.3",
+            "identifier": "V14.5.3",
+            "text": "[SPLIT TO 50.3.6, 50.4.3]",
+            "parent": "V14.5"
+          },
+          {
+            "bom-ref": "V14.5.4",
+            "identifier": "V14.5.4",
+            "text": "[DELETED, INCORRECT]",
+            "parent": "V14.5"
+          },
+          {
+            "bom-ref": "V14.6",
+            "identifier": "V14.6",
+            "title": "Web or Application Server Configuration",
+            "parent": "V14"
+          },
+          {
+            "bom-ref": "V14.6.1",
+            "identifier": "V14.6.1",
+            "text": "[GRAMMAR, MOVED FROM 12.6.1] Verify that the web or application server is configured with an allowlist of resources or systems to which the server can send requests or load data or files from.",
+            "parent": "V14.6"
+          },
+          {
+            "bom-ref": "V14.6.2",
+            "identifier": "V14.6.2",
+            "text": "[MODIFIED, MOVED FROM 1.2.1] Verify that communications between back-end application components, including local or operating system services, APIs, middleware and data layers, are performed with accounts assigned the least necessary privileges.",
+            "parent": "V14.6"
+          },
+          {
+            "bom-ref": "V14.7",
+            "identifier": "V14.7",
+            "title": "External Service Configuration",
+            "parent": "V14"
+          },
+          {
+            "bom-ref": "V14.7.1",
+            "identifier": "V14.7.1",
+            "text": "[MODIFIED, MOVED FROM 2.10.1, MERGED FROM 1.2.2] Verify that communications between back-end application components which don't support the application's standard user session mechanism, including APIs, middleware and data layers, are authenticated. Authentication should use individual service accounts, short-term tokens or certificate based authentication and not unchanging credentials such as passwords, API keys or shared accounts with privileged access.",
+            "parent": "V14.7"
+          },
+          {
+            "bom-ref": "V14.7.2",
+            "identifier": "V14.7.2",
+            "text": "[GRAMMAR, MOVED FROM 2.10.2] Verify that if a credential has to be used for service authentication, the credential being used by the consumer is not a default credential (e.g. root/root or admin/admin are default in some services during installation).",
+            "parent": "V14.7"
+          },
+          {
+            "bom-ref": "V14.7.3",
+            "identifier": "V14.7.3",
+            "text": "[MODIFIED, MOVED FROM 4.3.3] Verify that, if the application allows changing configurations around passwords or connection parameters for integrations with external databases and services, they are protected by extra controls such as re-authentication or multi-user approval.",
+            "parent": "V14.7"
+          },
+          {
+            "bom-ref": "V14.8",
+            "identifier": "V14.8",
+            "title": "Secret Management",
+            "parent": "V14"
+          },
+          {
+            "bom-ref": "V14.8.1",
+            "identifier": "V14.8.1",
+            "text": "[MODIFIED, MOVED FROM 6.4.1, MERGED FROM 1.6.2, 2.10.4] Verify that a secrets management solution such as a key vault is used to securely create, store, control access to, and destroy back-end secrets. These could include passwords, key material, integrations with databases and third-party systems, seeds and internal secrets, and API keys. Secrets must not be included in application source code or included in build artifacts. For a L3 application, this should involve a hardware-backed solution such as an HSM.",
+            "parent": "V14.8"
+          },
+          {
+            "bom-ref": "V14.8.2",
+            "identifier": "V14.8.2",
+            "text": "[MODIFIED, MOVED FROM 6.4.2] Verify that key material is not exposed to the application (neither the front-end nor the back-end) but instead uses an isolated security module like a vault for cryptographic operations.",
+            "parent": "V14.8"
+          },
+          {
+            "bom-ref": "V14.8.3",
+            "identifier": "V14.8.3",
+            "text": "[ADDED] Verify that key secrets have defined expiration dates and are rotated on a schedule based on the organization’s threat model and business requirements.",
+            "parent": "V14.8"
+          },
+          {
+            "bom-ref": "V14.8.4",
+            "identifier": "V14.8.4",
+            "text": "[ADDED] Verify that access to secret assets adheres to the principle of least privilege.",
+            "parent": "V14.8"
+          },
+          {
+            "bom-ref": "V50",
+            "identifier": "V50",
+            "title": "Web Frontend Security"
+          },
+          {
+            "bom-ref": "V1.50",
+            "identifier": "V1.50",
+            "title": "Web Frontend Security Documentation",
+            "parent": "V50"
+          },
+          {
+            "bom-ref": "V1.50.1",
+            "identifier": "V1.50.1",
+            "text": "[ADDED] Verify that application documentation states the expected security features that browsers using the application should support (such as HTTPS, HSTS, Content Security Policy (CSP), and other relevant HTTP security mechanisms). It should also define how the application must behave when some of these features are not available (such as warning the user or blocking access).",
+            "parent": "V1.50"
+          },
+          {
+            "bom-ref": "V50.1",
+            "identifier": "V50.1",
+            "title": "Site Isolation Architecture",
+            "parent": "V50"
+          },
+          {
+            "bom-ref": "V50.1.1",
+            "identifier": "V50.1.1",
+            "text": "[ADDED, DEPRECATES 3.4.5] Verify that separate applications are hosted on different hostnames to leverage the restrictions provided by same-origin policy, including how documents or scripts loaded by one origin can interact with resources from another origin and hostname-based restrictions on cookies.",
+            "parent": "V50.1"
+          },
+          {
+            "bom-ref": "V50.2",
+            "identifier": "V50.2",
+            "title": "Cookie Setup",
+            "parent": "V50"
+          },
+          {
+            "bom-ref": "V50.2.1",
+            "identifier": "V50.2.1",
+            "text": "[MODIFIED, MOVED FROM 3.4.1] Verify that cookies have the 'Secure' attribute set, and if the '\\__Host-' prefix is not used for the cookie name, the '__Secure-' prefix must be used for the cookie name.",
+            "parent": "V50.2"
+          },
+          {
+            "bom-ref": "V50.2.2",
+            "identifier": "V50.2.2",
+            "text": "[MODIFIED, MOVED FROM 3.4.2, LEVEL L1 > L2] Verify that if the value of a cookie is not meant to be accessible to client-side scripts (such as a session token), the cookie must have the 'HttpOnly' attribute set and the same value (e. g. session token) must only be transferred to the client via the 'Set-Cookie' header field.",
+            "parent": "V50.2"
+          },
+          {
+            "bom-ref": "V50.2.3",
+            "identifier": "V50.2.3",
+            "text": "[MODIFIED, MOVED FROM 3.4.3, LEVEL L1 > L2] Verify that each cookie's 'SameSite' attribute value is set according to the purpose of the cookie, to limit exposure to cross-site request forgery and user interface redress attacks.",
+            "parent": "V50.2"
+          },
+          {
+            "bom-ref": "V50.2.4",
+            "identifier": "V50.2.4",
+            "text": "[MODIFIED, MOVED FROM 3.4.4, LEVEL L1 > L2] Verify that cookies have the '__Host-' prefix for the cookie name unless they are explicitly designed to be shared with other hosts.",
+            "parent": "V50.2"
+          },
+          {
+            "bom-ref": "V50.2.5",
+            "identifier": "V50.2.5",
+            "text": "[ADDED] Verify that when the application writes a cookie the cookie name and value length combined are not over 4096 bytes. Overly large cookies will not be stored by the browser and therefore not sent with requests, preventing the user from using application functionality which relies on that cookie.",
+            "parent": "V50.2"
+          },
+          {
+            "bom-ref": "V50.3",
+            "identifier": "V50.3",
+            "title": "Browser Security Mechanism Headers",
+            "parent": "V50"
+          },
+          {
+            "bom-ref": "V50.3.1",
+            "identifier": "V50.3.1",
+            "text": "[MODIFIED, MOVED FROM 14.4.3, LEVEL L1 > L2] Verify that every HTTP response includes a Content-Security-Policy header to reduce the risk of malicious JavaScript. The directives object-src 'none' and base-uri 'none' must be defined. For an L3 application, a per-response policy with nonces or hashes must be defined.",
+            "parent": "V50.3"
+          },
+          {
+            "bom-ref": "V50.3.2",
+            "identifier": "V50.3.2",
+            "text": "[GRAMMAR, MOVED FROM 14.4.4] Verify that all responses contain a X-Content-Type-Options: nosniff header field.",
+            "parent": "V50.3"
+          },
+          {
+            "bom-ref": "V50.3.3",
+            "identifier": "V50.3.3",
+            "text": "[MODIFIED, MOVED FROM 14.4.5] Verify that a Strict-Transport-Security header field is included on all responses and for all subdomains, such as Strict-Transport-Security: max-age=31536000; includeSubdomains.",
+            "parent": "V50.3"
+          },
+          {
+            "bom-ref": "V50.3.4",
+            "identifier": "V50.3.4",
+            "text": "[MODIFIED, MOVED FROM 14.4.6] Verify that an suitable Referrer-Policy header is included to prevent sensitive information in the URL from being exposed to untrusted parties via the Referer header.",
+            "parent": "V50.3"
+          },
+          {
+            "bom-ref": "V50.3.5",
+            "identifier": "V50.3.5",
+            "text": "[MODIFIED, MOVED FROM 14.4.7] Verify that the content of the web application cannot be embedded in a third-party site by default, and that embedding of specific resources is allowed only when necessary, using the Content-Security-Policy frame-ancestors directive. Note that X-Frame-Options is now obsolete.",
+            "parent": "V50.3"
+          },
+          {
+            "bom-ref": "V50.3.6",
+            "identifier": "V50.3.6",
+            "text": "[ADDED, SPLIT FROM 14.5.3] Verify that the Cross-Origin Resource Sharing (CORS) Access-Control-Allow-Origin header field is validated against an allowlist of trusted origins. When \"Access-Control-Allow-Origin: *\" needs to be used, verify that the responses do not include any sensitive information.",
+            "parent": "V50.3"
+          },
+          {
+            "bom-ref": "V50.3.7",
+            "identifier": "V50.3.7",
+            "text": "[ADDED] Verify that the Content-Security-Policy header field specifies a location to report violations.",
+            "parent": "V50.3"
+          },
+          {
+            "bom-ref": "V50.4",
+            "identifier": "V50.4",
+            "title": "Browser Origin Separation",
+            "parent": "V50"
+          },
+          {
+            "bom-ref": "V50.4.1",
+            "identifier": "V50.4.1",
+            "text": "[MODIFIED, MOVED FROM 4.2.2, MERGED FROM 13.2.3] Verify that the application defends against Cross-Site Request Forgery (CSRF) attacks to protect authenticated or sensitive public functionality, using the development framework's built-in anti-CSRF functionality or CSRF tokens, along with additional defense-in-depth measures.",
+            "parent": "V50.4"
+          },
+          {
+            "bom-ref": "V50.4.2",
+            "identifier": "V50.4.2",
+            "text": "[ADDED] Verify that messages received by the postMessage interface are discarded if the origin of the message is not trusted, or if the syntax of the message is invalid.",
+            "parent": "V50.4"
+          },
+          {
+            "bom-ref": "V50.4.3",
+            "identifier": "V50.4.3",
+            "text": "[ADDED, SPLIT FROM 14.5.3] Verify that the Origin header field is validated against a defined list of allowed origins to match the desired Cross-Origin Resource Sharing (CORS) policy.",
+            "parent": "V50.4"
+          },
+          {
+            "bom-ref": "V50.5",
+            "identifier": "V50.5",
+            "title": "Cross-Site Script Inclusion",
+            "parent": "V50"
+          },
+          {
+            "bom-ref": "V50.5.1",
+            "identifier": "V50.5.1",
+            "text": "[ADDED] Verify that JSONP functionality is not enabled anywhere across the application to avoid Cross-Site Script Inclusion (XSSI) attacks.",
+            "parent": "V50.5"
+          },
+          {
+            "bom-ref": "V50.5.2",
+            "identifier": "V50.5.2",
+            "text": "[ADDED] Verify that data requiring authorization is not included in script resource responses, like JavaScript files, to prevent Cross-Site Script Inclusion (XSSI) attacks.",
+            "parent": "V50.5"
+          },
+          {
+            "bom-ref": "V50.6",
+            "identifier": "V50.6",
+            "title": "Unintended Content Interpretation",
+            "parent": "V50"
+          },
+          {
+            "bom-ref": "V50.6.1",
+            "identifier": "V50.6.1",
+            "text": "[MODIFIED, MOVED FROM 12.5.2, MERGED FROM 1.12.2, 14.4.2] Verify that security controls are in place to prevent browsers from rendering content or functionality in HTTP responses in an incorrect context (e.g., when an API, a user-uploaded file or other resource is requested directly). Possible controls could include: not serving the content unless HTTP request header fields, such as Sec-Fetch-\\*, indicate it is the correct context, Content-Security-Policy: sandbox, Content-Disposition: attachment, etc.",
+            "parent": "V50.6"
+          },
+          {
+            "bom-ref": "V50.6.2",
+            "identifier": "V50.6.2",
+            "text": "[ADDED, SPLIT FROM 5.3.3] Verify that functions (such as createTextNode, textContent) which safely render content as text, are used to apply untrusted content to an HTML page or the DOM. Properties or functions (such as innerHTML, document.write) that render content as HTML must not be used.",
+            "parent": "V50.6"
+          },
+          {
+            "bom-ref": "V50.7",
+            "identifier": "V50.7",
+            "title": "External Resource Integrity",
+            "parent": "V50"
+          },
+          {
+            "bom-ref": "V50.7.1",
+            "identifier": "V50.7.1",
+            "text": "[MODIFIED, MOVED FROM 14.2.3] Verify that if client-side assets, such as JavaScript libraries, CSS 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.",
+            "parent": "V50.7"
+          },
+          {
+            "bom-ref": "V50.8",
+            "identifier": "V50.8",
+            "title": "Other Browser Security Considerations",
+            "parent": "V50"
+          },
+          {
+            "bom-ref": "V50.8.1",
+            "identifier": "V50.8.1",
+            "text": "[ADDED, SPLIT FROM 5.1.5] Verify that the application shows a notification when the user is being redirected to a URL outside of the application's control, with an option to cancel the navigation.",
+            "parent": "V50.8"
+          },
+          {
+            "bom-ref": "V50.8.2",
+            "identifier": "V50.8.2",
+            "text": "[MODIFIED, MOVED FROM 1.14.6] Verify that the application only uses client-side technologies which are still supported and considered secure. Examples of technologies which do not meet this requirement include NSAPI plugins, Flash, Shockwave, ActiveX, Silverlight, NACL, or client-side Java applets.",
+            "parent": "V50.8"
+          },
+          {
+            "bom-ref": "V50.8.3",
+            "identifier": "V50.8.3",
+            "text": "[ADDED] Verify that the application behaves as documented (such as warning the user or blocking access) if the browser used to access the application does not support the expected security features.",
+            "parent": "V50.8"
+          },
+          {
+            "bom-ref": "V50.8.4",
+            "identifier": "V50.8.4",
+            "text": "[ADDED] Verify that the application's top-level domain (e.g., site.tld) is added to the public HSTS preload list so that the use of TLS for the application is built directly into the main browsers, rather than relying only on the relevant HTTP response header field.",
+            "parent": "V50.8"
+          },
+          {
+            "bom-ref": "V51",
+            "identifier": "V51",
+            "title": "OAuth and OIDC"
+          },
+          {
+            "bom-ref": "V51.1",
+            "identifier": "V51.1",
+            "title": "Generic OAuth and OIDC security",
+            "parent": "V51"
+          },
+          {
+            "bom-ref": "V51.1.1",
+            "identifier": "V51.1.1",
+            "text": "[ADDED] Verify that tokens are only sent to components that strictly need them. For example, avoid having access or refresh tokens accessible for the frontend when they are only needed by the backend.",
+            "parent": "V51.1"
+          },
+          {
+            "bom-ref": "V51.1.2",
+            "identifier": "V51.1.2",
+            "text": "[ADDED] Verify that the client only accepts values from the authorization server (such as the authorization code or ID token) if these values result from an authorization flow that was initiated by the same user agent session and transaction. This requires that client-generated secrets, such as the proof key for code exchange (PKCE) 'code_verifier', 'state' or OIDC 'nonce' are not guessable, are specific to the transaction, and are securely bound to both the client and the user agent session in which the transaction was started.",
+            "parent": "V51.1"
+          },
+          {
+            "bom-ref": "V51.2",
+            "identifier": "V51.2",
+            "title": "OAuth Client",
+            "parent": "V51"
+          },
+          {
+            "bom-ref": "V51.2.1",
+            "identifier": "V51.2.1",
+            "text": "[ADDED] Verify that, if the OAuth Client can interact with more than one authorization server, it has a defense against mix-up attacks. For example, it could require that the authorization server returns the 'iss' parameter value and validate it in the authorization response and the token response.",
+            "parent": "V51.2"
+          },
+          {
+            "bom-ref": "V51.2.2",
+            "identifier": "V51.2.2",
+            "text": "[ADDED] Verify that, if the code flow is used, the OAuth Client has protection against cross-site request forgery (CSRF) attacks which trigger token requests, either by using proof key for code exchange (PKCE) functionality or checking the 'state' parameter that was sent in the authorization request.",
+            "parent": "V51.2"
+          },
+          {
+            "bom-ref": "V51.2.3",
+            "identifier": "V51.2.3",
+            "text": "[ADDED] Verify that the OAuth Client only requests the required scopes (or other authorization parameters) in requests to the authorization server.",
+            "parent": "V51.2"
+          },
+          {
+            "bom-ref": "V51.3",
+            "identifier": "V51.3",
+            "title": "OAuth Resource Server",
+            "parent": "V51"
+          },
+          {
+            "bom-ref": "V51.3.1",
+            "identifier": "V51.3.1",
+            "text": "[ADDED] Verify that the resource server prevents the use of stolen access tokens or replay of access tokens (from unauthorized parties) by requiring sender-constrained access tokens, either Mutual TLS for OAuth 2 or OAuth 2 Demonstration of Proof of Possession (DPoP).",
+            "parent": "V51.3"
+          },
+          {
+            "bom-ref": "V51.3.2",
+            "identifier": "V51.3.2",
+            "text": "[ADDED] Verify that the resource server only accepts access tokens that are intended for use with that service (audience). The audience may be included in a structured access token (such as the 'aud' claim in JWT) or it can be checked using the token introspection endpoint.",
+            "parent": "V51.3"
+          },
+          {
+            "bom-ref": "V51.3.3",
+            "identifier": "V51.3.3",
+            "text": "[ADDED] Verify that the resource server enforces authorization decisions based on claims from the access token that define delegated authorization. If claims such as 'sub', 'scope', and 'authorization_details' are present, they should be part of the decision.",
+            "parent": "V51.3"
+          },
+          {
+            "bom-ref": "V51.3.4",
+            "identifier": "V51.3.4",
+            "text": "[ADDED] Verify that if an access control decision requires identifying a unique user from an access token (JWT or related token introspection response), the resource server identifies the user from claims that can not be reassigned to other users. Typically it means using a combination of 'iss' and 'sub' claims.",
+            "parent": "V51.3"
+          },
+          {
+            "bom-ref": "V51.4",
+            "identifier": "V51.4",
+            "title": "OAuth Authorization Server",
+            "parent": "V51"
+          },
+          {
+            "bom-ref": "V51.4.1",
+            "identifier": "V51.4.1",
+            "text": "[ADDED] Verify that, if the authorization server returns the authorization code, it can be used only once for a token request.",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.4.2",
+            "identifier": "V51.4.2",
+            "text": "[ADDED] Verify that the authorization code is short-lived. The maximum lifetime can be 10 minutes for L1 and L2 applications and 1 minute for L3 applications.",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.4.3",
+            "identifier": "V51.4.3",
+            "text": "[ADDED] Verify that, if the code grant is used, the authorization server mitigates authorization code interception attacks by requiring proof key for code exchange (PKCE). For authorization requests, the authorization server must require a valid 'code_challenge' value and must not accept 'code_challenge_method' value 'plain'. For a token request, it must require validation of the 'code_verifier' parameter.",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.4.4",
+            "identifier": "V51.4.4",
+            "text": "[ADDED] Verify that the authorization server mitigates refresh token replay attacks for public clients, preferably using sender-constrained refresh tokens (i.e. Demonstrating Proof of Possession (DPoP) or Certificate-Bound Access Tokens (mTLS)). For L1 applications only, refresh token rotation may be used instead. If refresh token rotation is used, verify that the authorization server invalidates the refresh token after usage and revokes all refresh tokens for that authorization if an already used and invalidated refresh token is provided.",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.4.5",
+            "identifier": "V51.4.5",
+            "text": "[ADDED] Verify that for a given client, the authorization server only allows the usage of grants that this client needs to use. Note that the grants 'token' (Implicit flow) and 'password' (Resource Owner Password Credentials flow) must no longer be used.",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.4.6",
+            "identifier": "V51.4.6",
+            "text": "[ADDED] Verify that the authorization server validates redirect URIs based on a client-specific allowlist of pre-registered URIs using exact string comparison.",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.4.7",
+            "identifier": "V51.4.7",
+            "text": "[ADDED] Verify that confidential client is authenticated for client-to-authorized server backchannel requests such as token requests, pushed authorization requests (PAR), token revocation requests, and token introspection requests.",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.4.8",
+            "identifier": "V51.4.8",
+            "text": "[ADDED] Verify that the authorization server configuration only assigns the required scopes to the OAuth Client.",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.4.9",
+            "identifier": "V51.4.9",
+            "text": "[ADDED] Verify that grant type 'code' is always used together with pushed authorization requests (PAR).",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.4.10",
+            "identifier": "V51.4.10",
+            "text": "[ADDED] Verify that the client is confidential and the authorization server requires the use of strong client authentication methods (based on public-key cryptography and resistant to replay attacks), i.e. 'mTLS' or 'private-key-jwt'.",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.4.11",
+            "identifier": "V51.4.11",
+            "text": "[ADDED] Verify that the authorization server issues only sender-constrained (Proof-of-Possession) access tokens, either using mTLS certificate binding or Demonstration of Proof of Possession (DPoP).",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.4.12",
+            "identifier": "V51.4.12",
+            "text": "[ADDED] Verify that for a given client, the authorization server only allows the 'response_mode' value that this client needs to use. For example by having the authorization server validate this value against the expected values or by using pushed authorization request (PAR) or JWT-secured authorization request (JAR).",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.4.13",
+            "identifier": "V51.4.13",
+            "text": "[ADDED] Verify that refresh tokens have an absolute expiration, including if sliding refresh token expiration is applied.",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.4.14",
+            "identifier": "V51.4.14",
+            "text": "[MODIFIED, MOVED FROM 3.5.1] Verify that refresh tokens and reference access tokens can be revoked by an authorized user. It can be achieved by using the authorization server user interface, or by a client that is using authorization server APIs for revocation.",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.4.15",
+            "identifier": "V51.4.15",
+            "text": "[ADDED] Verify that, for a server-side client (which is not executed on the end-user device), the authorization server ensures that the 'authorization_details' parameter value is from the client backend and that the user has not tampered with it. For example by requiring the usage of pushed authorization request (PAR) or JWT-secured authorization request (JAR).",
+            "parent": "V51.4"
+          },
+          {
+            "bom-ref": "V51.5",
+            "identifier": "V51.5",
+            "title": "OIDC Client",
+            "parent": "V51"
+          },
+          {
+            "bom-ref": "V51.5.1",
+            "identifier": "V51.5.1",
+            "text": "[ADDED] Verify that the Client (as the relying party) mitigates ID token replay attacks. For example, by ensuring that the 'nonce' claim in the ID token matches the 'nonce' value sent in the authentication request to the OpenID provider (in OAuth2 refereed to as the authorization request sent to the authorization server).",
+            "parent": "V51.5"
+          },
+          {
+            "bom-ref": "V51.5.2",
+            "identifier": "V51.5.2",
+            "text": "[ADDED] Verify that the Client uniquely identifies the user from ID token claims, usually the 'sub' claim, which cannot be reassigned to other users (for the scope of an identity provider).",
+            "parent": "V51.5"
+          },
+          {
+            "bom-ref": "V51.5.3",
+            "identifier": "V51.5.3",
+            "text": "[ADDED] Verify that the client rejects attempts by a malicious authorization server to impersonate another authorization server through authorization server metadata. The client must reject authorization server metadata if the issuer URL in the authorization server metadata does not exactly match the pre-configured issuer URL expected by client.",
+            "parent": "V51.5"
+          },
+          {
+            "bom-ref": "V51.5.4",
+            "identifier": "V51.5.4",
+            "text": "[ADDED] Verify that the client validates that the ID token is intended to be used for that client (audience) by checking that the 'aud' claim from the token is equal to the 'client_id' value for the client.",
+            "parent": "V51.5"
+          },
+          {
+            "bom-ref": "V51.6",
+            "identifier": "V51.6",
+            "title": "OpenID Provider",
+            "parent": "V51"
+          },
+          {
+            "bom-ref": "V51.6.1",
+            "identifier": "V51.6.1",
+            "text": "[ADDED] Verify that the OpenID Provider only allows values 'code', 'ciba', 'id-token', or 'id-token code' for response mode. Note that 'code' is preferred over 'id-token code' (the OIDC Hybrid flow), and 'token' (any Implicit flow) must not be used.",
+            "parent": "V51.6"
+          },
+          {
+            "bom-ref": "V51.7",
+            "identifier": "V51.7",
+            "title": "Consent Management",
+            "parent": "V51"
+          },
+          {
+            "bom-ref": "V51.7.1",
+            "identifier": "V51.7.1",
+            "text": "[ADDED] Verify that the authorization server ensures that the user consents to each authorization request. If the identity of the client cannot be assured, the authorization server must always explicitly prompt the user for consent.",
+            "parent": "V51.7"
+          },
+          {
+            "bom-ref": "V51.7.2",
+            "identifier": "V51.7.2",
+            "text": "[ADDED] Verify that when the authorization server prompts for user consent, it presents sufficient and clear information about what is being consented to. When applicable this should include the nature of the requested authorizations (typically based on scope, resource server, rich authorization requests (RAR) authorization details), the identity of the authorized application and the lifetime of these authorizations.",
+            "parent": "V51.7"
+          },
+          {
+            "bom-ref": "V51.7.3",
+            "identifier": "V51.7.3",
+            "text": "[ADDED] Verify that the user can review, modify and revoke consents which the user has granted through the authorization server.",
+            "parent": "V51.7"
+          },
+          {
+            "bom-ref": "V52",
+            "identifier": "V52",
+            "title": "Self-contained Tokens"
+          },
+          {
+            "bom-ref": "V52.1",
+            "identifier": "V52.1",
+            "title": "Token source and integrity",
+            "parent": "V52"
+          },
+          {
+            "bom-ref": "V52.1.1",
+            "identifier": "V52.1.1",
+            "text": "[MODIFIED, MOVED FROM 3.5.3, LEVEL L2 > L1] Verify that self-contained tokens are validated using their digital signature or MAC to protect against tampering before accepting the token's contents.",
+            "parent": "V52.1"
+          },
+          {
+            "bom-ref": "V52.1.2",
+            "identifier": "V52.1.2",
+            "text": "[ADDED] Verify that only algorithms on an allowlist can be used to create and verify self-contained tokens, for a given context. The allowlist should include the permitted algorithms, ideally only either symmetric or asymmetric algorithms, and should not include the 'None' algorithm. If both symmetric and asymmetric are needed, additional controls should prevent key confusion.",
+            "parent": "V52.1"
+          },
+          {
+            "bom-ref": "V52.1.3",
+            "identifier": "V52.1.3",
+            "text": "[ADDED] Verify that key material that is used to validate self-contained tokens is from trusted pre-configured sources for the token issuer, preventing attackers from specifying untrusted sources and keys. For JWTs and other JWS structures, headers such as 'jku', 'x5u', and 'jwk' must be validated against an allowlist of trusted sources.",
+            "parent": "V52.1"
+          },
+          {
+            "bom-ref": "V52.2",
+            "identifier": "V52.2",
+            "title": "Using token content",
+            "parent": "V52"
+          },
+          {
+            "bom-ref": "V52.2.1",
+            "identifier": "V52.2.1",
+            "text": "[ADDED] Verify that, if a validity time span is present in the token data, the token and its content are accepted only if the verification time is within this validity time span. For example, for JWTs the claims 'nbf' and 'exp' must be verified.",
+            "parent": "V52.2"
+          },
+          {
+            "bom-ref": "V52.2.2",
+            "identifier": "V52.2.2",
+            "text": "[ADDED] Verify that the service receiving a token validates the token to be the correct type and is meant for the intended purpose before accepting the token's contents. For example, only access tokens can be accepted for authorization decisions and only ID tokens can be used for proving user authentication.",
+            "parent": "V52.2"
+          },
+          {
+            "bom-ref": "V52.2.3",
+            "identifier": "V52.2.3",
+            "text": "[ADDED] Verify that the service only accepts tokens which are intended for use with that service (audience). For JWTs, this can be achieved by validating the 'aud' claim against an allowlist defined in the service.",
+            "parent": "V52.2"
+          },
+          {
+            "bom-ref": "V53",
+            "identifier": "V53",
+            "title": "WebRTC"
+          },
+          {
+            "bom-ref": "V53.1",
+            "identifier": "V53.1",
+            "title": "TURN Server",
+            "parent": "V53"
+          },
+          {
+            "bom-ref": "V53.1.1",
+            "identifier": "V53.1.1",
+            "text": "[ADDED] Verify that the Traversal Using Relays around NAT (TURN) service only allows access to IP addresses that are not reserved for special purposes (e.g., internal networks, broadcast, loopback). Note that this applies to both IPv4 and IPv6 addresses.",
+            "parent": "V53.1"
+          },
+          {
+            "bom-ref": "V53.1.2",
+            "identifier": "V53.1.2",
+            "text": "[ADDED] Verify that the Traversal Using Relays around NAT (TURN) service is not susceptible to resource exhaustion when legitimate users attempt to open a large number of ports on the TURN server.",
+            "parent": "V53.1"
+          },
+          {
+            "bom-ref": "V53.2",
+            "identifier": "V53.2",
+            "title": "Media",
+            "parent": "V53"
+          },
+          {
+            "bom-ref": "V53.2.1",
+            "identifier": "V53.2.1",
+            "text": "[ADDED] Verify that the key for the Datagram Transport Layer Security (DTLS) certificate is private by ensuring it is not reused in existing products or open-source projects and confirming it is not distributed or leaked.",
+            "parent": "V53.2"
+          },
+          {
+            "bom-ref": "V53.2.2",
+            "identifier": "V53.2.2",
+            "text": "[ADDED] Verify that the media server is configured to use and support strong cipher suites for the Datagram Transport Layer Security (DTLS) exchange, ensuring that the selected cipher suites are considered strong and secure.",
+            "parent": "V53.2"
+          },
+          {
+            "bom-ref": "V53.2.3",
+            "identifier": "V53.2.3",
+            "text": "[ADDED] Verify that the media server is not susceptible to the \"WebRTC DTLS ClientHello Race Condition\" vulnerability by checking if the media server is publicly known to be vulnerable or by performing the race condition test.",
+            "parent": "V53.2"
+          },
+          {
+            "bom-ref": "V53.2.4",
+            "identifier": "V53.2.4",
+            "text": "[ADDED] Verify that Secure Real-time Transport Protocol (SRTP) authentication is checked at the media server to prevent Real-time Transport Protocol (RTP) injection attacks from leading to either a Denial of Service condition or audio or video media insertion into media streams.",
+            "parent": "V53.2"
+          },
+          {
+            "bom-ref": "V53.2.5",
+            "identifier": "V53.2.5",
+            "text": "[ADDED] Verify that the media server is able to continue processing incoming media traffic during a flood of Secure Real-time Transport Protocol (SRTP) packets from legitimate users.",
+            "parent": "V53.2"
+          },
+          {
+            "bom-ref": "V53.2.6",
+            "identifier": "V53.2.6",
+            "text": "[ADDED] Verify that any audio or video recording mechanisms associated with the media server are able to continue processing incoming media traffic during a flood of Secure Real-time Transport Protocol (SRTP) packets from legitimate users.",
+            "parent": "V53.2"
+          },
+          {
+            "bom-ref": "V53.2.7",
+            "identifier": "V53.2.7",
+            "text": "[ADDED] Verify that the media server is able to continue processing incoming media traffic when encountering malformed SRTP packets.",
+            "parent": "V53.2"
+          },
+          {
+            "bom-ref": "V53.2.8",
+            "identifier": "V53.2.8",
+            "text": "[ADDED] Verify that the DTLS certificate is checked against the SDP fingerprint attribute, terminating the media stream if the check fails, to ensure the authenticity of the media stream.",
+            "parent": "V53.2"
+          },
+          {
+            "bom-ref": "V53.3",
+            "identifier": "V53.3",
+            "title": "Signalling",
+            "parent": "V53"
+          },
+          {
+            "bom-ref": "V53.3.1",
+            "identifier": "V53.3.1",
+            "text": "[ADDED] Verify that the signalling server is able to continue processing incoming signalling messages during a flood attack. This should be achieved by implementing rate limiting at the signalling level.",
+            "parent": "V53.3"
+          },
+          {
+            "bom-ref": "V53.3.2",
+            "identifier": "V53.3.2",
+            "text": "[ADDED] Verify that the signalling server is able to is able to continue processing signalling messages when encountering malformed signalling messages.",
+            "parent": "V53.3"
+          }
+        ],
+        "levels": [
+          {
+            "bom-ref": "level-1",
+            "identifier": "Level 1",
+            "description": "ASVS Level 1 is for low assurance levels, and is completely penetration testable.",
+            "requirements": [
+              "V1.2.6",
+              "V2.1.1",
+              "V2.1.2",
+              "V2.1.3",
+              "V2.1.5",
+              "V2.1.6",
+              "V2.1.7",
+              "V2.1.9",
+              "V2.1.11",
+              "V2.1.12",
+              "V2.2.1",
+              "V2.2.2",
+              "V2.2.3",
+              "V2.3.1",
+              "V2.3.4",
+              "V2.5.2",
+              "V2.5.6",
+              "V2.5.7",
+              "V2.7.1",
+              "V2.7.2",
+              "V2.7.3",
+              "V2.7.4",
+              "V2.8.1",
+              "V1.3.1",
+              "V1.3.2",
+              "V1.3.3",
+              "V3.1.2",
+              "V3.1.3",
+              "V3.1.4",
+              "V3.1.5",
+              "V3.3.2",
+              "V3.3.5",
+              "V3.7.1",
+              "V3.8.1",
+              "V3.8.2",
+              "V3.8.4",
+              "V3.8.5",
+              "V1.4.7",
+              "V4.1.3",
+              "V4.1.6",
+              "V4.2.3",
+              "V4.3.4",
+              "V1.5.1",
+              "V1.5.5",
+              "V5.1.1",
+              "V5.1.3",
+              "V5.1.4",
+              "V5.1.5",
+              "V5.1.7",
+              "V5.2.1",
+              "V5.2.2",
+              "V5.2.3",
+              "V5.2.4",
+              "V5.2.5",
+              "V5.2.6",
+              "V5.2.7",
+              "V5.2.8",
+              "V5.2.9",
+              "V5.2.10",
+              "V5.2.11",
+              "V5.3.1",
+              "V5.3.3",
+              "V5.3.4",
+              "V5.3.7",
+              "V5.3.8",
+              "V5.3.10",
+              "V5.3.11",
+              "V5.3.13",
+              "V5.5.2",
+              "V5.5.3",
+              "V5.6.1",
+              "V5.6.2",
+              "V6.2.1",
+              "V6.2.9",
+              "V6.3.1",
+              "V6.3.3",
+              "V6.5.2",
+              "V6.6.3",
+              "V6.6.4",
+              "V7.1.1",
+              "V7.4.1",
+              "V8.2.1",
+              "V8.2.2",
+              "V8.2.3",
+              "V8.3.1",
+              "V9.1.1",
+              "V9.1.4",
+              "V9.2.6",
+              "V9.4.1",
+              "V9.4.2",
+              "V10.4.1",
+              "V10.4.4",
+              "V10.4.5",
+              "V10.6.1",
+              "V10.6.2",
+              "V11.1.1",
+              "V11.1.3",
+              "V1.12.3",
+              "V12.1.1",
+              "V12.2.2",
+              "V12.3.1",
+              "V12.3.7",
+              "V12.4.1",
+              "V12.4.2",
+              "V12.5.3",
+              "V12.5.4",
+              "V13.1.7",
+              "V13.5.1",
+              "V13.5.2",
+              "V13.5.3",
+              "V13.5.4",
+              "V13.6.1",
+              "V13.6.2",
+              "V13.7.1",
+              "V13.7.2",
+              "V13.7.3",
+              "V14.1.6",
+              "V14.1.10",
+              "V14.3.2",
+              "V14.3.3",
+              "V14.3.4",
+              "V14.3.5",
+              "V14.3.6",
+              "V14.6.1",
+              "V50.1.1",
+              "V50.2.1",
+              "V50.3.2",
+              "V50.3.3",
+              "V50.3.4",
+              "V50.3.5",
+              "V50.3.6",
+              "V50.4.1",
+              "V50.4.3",
+              "V50.5.1",
+              "V50.5.2",
+              "V50.6.1",
+              "V50.6.2",
+              "V50.7.1",
+              "V51.1.1",
+              "V51.1.2",
+              "V51.2.1",
+              "V51.2.2",
+              "V51.2.3",
+              "V51.3.2",
+              "V51.3.3",
+              "V51.3.4",
+              "V51.4.1",
+              "V51.4.2",
+              "V51.4.3",
+              "V51.4.4",
+              "V51.4.6",
+              "V51.4.7",
+              "V51.4.8",
+              "V51.4.12",
+              "V51.4.13",
+              "V51.5.1",
+              "V51.5.2",
+              "V51.5.3",
+              "V51.5.4",
+              "V52.1.1",
+              "V52.1.2",
+              "V52.1.3",
+              "V52.2.1",
+              "V52.2.2",
+              "V52.2.3",
+              "V53.1.1",
+              "V53.2.1",
+              "V53.2.2",
+              "V53.2.4",
+              "V53.2.8"
+            ]
+          },
+          {
+            "bom-ref": "level-2",
+            "identifier": "Level 2",
+            "description": "ASVS Level 2 is for applications that contain sensitive data, which requires protection and is the recommended level for most apps.",
+            "requirements": [
+              "V1.2.4",
+              "V1.2.5",
+              "V1.2.6",
+              "V2.1.1",
+              "V2.1.2",
+              "V2.1.3",
+              "V2.1.5",
+              "V2.1.6",
+              "V2.1.7",
+              "V2.1.9",
+              "V2.1.10",
+              "V2.1.11",
+              "V2.1.12",
+              "V2.1.14",
+              "V2.2.1",
+              "V2.2.2",
+              "V2.2.3",
+              "V2.2.9",
+              "V2.2.10",
+              "V2.2.11",
+              "V2.3.1",
+              "V2.3.3",
+              "V2.3.4",
+              "V2.5.2",
+              "V2.5.6",
+              "V2.5.7",
+              "V2.6.1",
+              "V2.6.2",
+              "V2.6.3",
+              "V2.6.4",
+              "V2.7.1",
+              "V2.7.2",
+              "V2.7.3",
+              "V2.7.4",
+              "V2.7.6",
+              "V2.7.7",
+              "V2.8.1",
+              "V2.8.2",
+              "V2.8.3",
+              "V2.8.4",
+              "V2.11.1",
+              "V2.11.2",
+              "V2.11.3",
+              "V1.3.1",
+              "V1.3.2",
+              "V1.3.3",
+              "V3.1.2",
+              "V3.1.3",
+              "V3.1.4",
+              "V3.1.5",
+              "V3.3.2",
+              "V3.3.5",
+              "V3.6.3",
+              "V3.7.1",
+              "V3.7.2",
+              "V3.8.1",
+              "V3.8.2",
+              "V3.8.3",
+              "V3.8.4",
+              "V3.8.5",
+              "V1.4.7",
+              "V4.1.3",
+              "V4.1.6",
+              "V4.1.7",
+              "V4.1.8",
+              "V4.2.3",
+              "V4.2.4",
+              "V4.3.4",
+              "V1.5.1",
+              "V1.5.5",
+              "V5.1.1",
+              "V5.1.3",
+              "V5.1.4",
+              "V5.1.5",
+              "V5.1.6",
+              "V5.1.7",
+              "V5.2.1",
+              "V5.2.2",
+              "V5.2.3",
+              "V5.2.4",
+              "V5.2.5",
+              "V5.2.6",
+              "V5.2.7",
+              "V5.2.8",
+              "V5.2.9",
+              "V5.2.10",
+              "V5.2.11",
+              "V5.2.12",
+              "V5.2.13",
+              "V5.3.1",
+              "V5.3.3",
+              "V5.3.4",
+              "V5.3.7",
+              "V5.3.8",
+              "V5.3.10",
+              "V5.3.11",
+              "V5.3.12",
+              "V5.3.13",
+              "V5.4.1",
+              "V5.4.3",
+              "V5.4.4",
+              "V5.5.2",
+              "V5.5.3",
+              "V5.5.5",
+              "V5.6.1",
+              "V5.6.2",
+              "V5.6.3",
+              "V1.6.1",
+              "V1.6.4",
+              "V6.2.1",
+              "V6.2.2",
+              "V6.2.4",
+              "V6.2.9",
+              "V6.3.1",
+              "V6.3.3",
+              "V6.5.1",
+              "V6.5.2",
+              "V6.6.1",
+              "V6.6.2",
+              "V6.6.3",
+              "V6.6.4",
+              "V6.7.1",
+              "V6.8.2",
+              "V6.9.1",
+              "V6.9.2",
+              "V1.7.3",
+              "V7.1.1",
+              "V7.1.4",
+              "V7.1.5",
+              "V7.1.6",
+              "V7.1.7",
+              "V7.2.1",
+              "V7.2.2",
+              "V7.2.3",
+              "V7.2.4",
+              "V7.2.5",
+              "V7.2.7",
+              "V7.3.1",
+              "V7.3.3",
+              "V7.3.5",
+              "V7.4.1",
+              "V7.4.2",
+              "V7.4.3",
+              "V7.4.4",
+              "V7.4.5",
+              "V1.8.1",
+              "V1.8.2",
+              "V8.1.1",
+              "V8.1.4",
+              "V8.1.7",
+              "V8.1.8",
+              "V8.1.9",
+              "V8.2.1",
+              "V8.2.2",
+              "V8.2.3",
+              "V8.3.1",
+              "V8.3.9",
+              "V9.1.1",
+              "V9.1.4",
+              "V9.2.2",
+              "V9.2.6",
+              "V9.3.1",
+              "V9.3.2",
+              "V9.4.1",
+              "V9.4.2",
+              "V9.4.3",
+              "V1.10.2",
+              "V10.4.1",
+              "V10.4.2",
+              "V10.4.3",
+              "V10.4.4",
+              "V10.4.5",
+              "V10.4.6",
+              "V10.6.1",
+              "V10.6.2",
+              "V10.7.3",
+              "V1.11.4",
+              "V11.1.1",
+              "V11.1.3",
+              "V11.1.9",
+              "V11.2.2",
+              "V1.12.3",
+              "V12.1.1",
+              "V12.1.2",
+              "V12.1.3",
+              "V12.1.4",
+              "V12.2.1",
+              "V12.2.2",
+              "V12.3.1",
+              "V12.3.7",
+              "V12.4.1",
+              "V12.4.2",
+              "V12.5.3",
+              "V12.5.4",
+              "V12.7.1",
+              "V13.1.7",
+              "V13.1.8",
+              "V13.2.5",
+              "V13.4.1",
+              "V13.4.2",
+              "V13.4.3",
+              "V13.5.1",
+              "V13.5.2",
+              "V13.5.3",
+              "V13.5.4",
+              "V13.6.1",
+              "V13.6.2",
+              "V13.6.3",
+              "V13.6.4",
+              "V13.7.1",
+              "V13.7.2",
+              "V13.7.3",
+              "V1.14.7",
+              "V14.1.3",
+              "V14.1.6",
+              "V14.1.7",
+              "V14.1.9",
+              "V14.1.10",
+              "V14.3.2",
+              "V14.3.3",
+              "V14.3.4",
+              "V14.3.5",
+              "V14.3.6",
+              "V14.6.1",
+              "V14.6.2",
+              "V14.7.1",
+              "V14.7.2",
+              "V14.7.3",
+              "V14.8.1",
+              "V14.8.2",
+              "V14.8.3",
+              "V14.8.4",
+              "V50.1.1",
+              "V50.2.1",
+              "V50.2.2",
+              "V50.2.3",
+              "V50.2.4",
+              "V50.2.5",
+              "V50.3.1",
+              "V50.3.2",
+              "V50.3.3",
+              "V50.3.4",
+              "V50.3.5",
+              "V50.3.6",
+              "V50.4.1",
+              "V50.4.2",
+              "V50.4.3",
+              "V50.5.1",
+              "V50.5.2",
+              "V50.6.1",
+              "V50.6.2",
+              "V50.7.1",
+              "V50.8.2",
+              "V51.1.1",
+              "V51.1.2",
+              "V51.2.1",
+              "V51.2.2",
+              "V51.2.3",
+              "V51.3.2",
+              "V51.3.3",
+              "V51.3.4",
+              "V51.4.1",
+              "V51.4.2",
+              "V51.4.3",
+              "V51.4.4",
+              "V51.4.5",
+              "V51.4.6",
+              "V51.4.7",
+              "V51.4.8",
+              "V51.4.12",
+              "V51.4.13",
+              "V51.4.14",
+              "V51.5.1",
+              "V51.5.2",
+              "V51.5.3",
+              "V51.5.4",
+              "V51.6.1",
+              "V51.7.1",
+              "V51.7.2",
+              "V51.7.3",
+              "V52.1.1",
+              "V52.1.2",
+              "V52.1.3",
+              "V52.2.1",
+              "V52.2.2",
+              "V52.2.3",
+              "V53.1.1",
+              "V53.1.2",
+              "V53.2.1",
+              "V53.2.2",
+              "V53.2.3",
+              "V53.2.4",
+              "V53.2.5",
+              "V53.2.6",
+              "V53.2.7",
+              "V53.2.8",
+              "V53.3.1",
+              "V53.3.2"
+            ]
+          },
+          {
+            "bom-ref": "level-3",
+            "identifier": "Level 3",
+            "description": "ASVS Level 3 is for the most critical applications - applications that perform high value transactions, contain sensitive medical data, or any application that requires the highest level of trust.",
+            "requirements": [
+              "V1.2.4",
+              "V1.2.5",
+              "V1.2.6",
+              "V2.1.1",
+              "V2.1.2",
+              "V2.1.3",
+              "V2.1.5",
+              "V2.1.6",
+              "V2.1.7",
+              "V2.1.9",
+              "V2.1.10",
+              "V2.1.11",
+              "V2.1.12",
+              "V2.1.13",
+              "V2.1.14",
+              "V2.2.1",
+              "V2.2.2",
+              "V2.2.3",
+              "V2.2.4",
+              "V2.2.8",
+              "V2.2.9",
+              "V2.2.10",
+              "V2.2.11",
+              "V2.3.1",
+              "V2.3.3",
+              "V2.3.4",
+              "V2.5.2",
+              "V2.5.6",
+              "V2.5.7",
+              "V2.6.1",
+              "V2.6.2",
+              "V2.6.3",
+              "V2.6.4",
+              "V2.7.1",
+              "V2.7.2",
+              "V2.7.3",
+              "V2.7.4",
+              "V2.7.6",
+              "V2.7.7",
+              "V2.7.8",
+              "V2.8.1",
+              "V2.8.2",
+              "V2.8.3",
+              "V2.8.4",
+              "V2.8.6",
+              "V2.8.7",
+              "V2.8.8",
+              "V2.9.1",
+              "V2.9.2",
+              "V2.9.3",
+              "V2.11.1",
+              "V2.11.2",
+              "V2.11.3",
+              "V1.3.1",
+              "V1.3.2",
+              "V1.3.3",
+              "V3.1.2",
+              "V3.1.3",
+              "V3.1.4",
+              "V3.1.5",
+              "V3.3.2",
+              "V3.3.5",
+              "V3.6.1",
+              "V3.6.3",
+              "V3.7.1",
+              "V3.7.2",
+              "V3.8.1",
+              "V3.8.2",
+              "V3.8.3",
+              "V3.8.4",
+              "V3.8.5",
+              "V1.4.6",
+              "V1.4.7",
+              "V4.1.3",
+              "V4.1.6",
+              "V4.1.7",
+              "V4.1.8",
+              "V4.2.3",
+              "V4.2.4",
+              "V4.2.5",
+              "V4.3.1",
+              "V4.3.4",
+              "V1.5.1",
+              "V1.5.5",
+              "V5.1.1",
+              "V5.1.3",
+              "V5.1.4",
+              "V5.1.5",
+              "V5.1.6",
+              "V5.1.7",
+              "V5.2.1",
+              "V5.2.2",
+              "V5.2.3",
+              "V5.2.4",
+              "V5.2.5",
+              "V5.2.6",
+              "V5.2.7",
+              "V5.2.8",
+              "V5.2.9",
+              "V5.2.10",
+              "V5.2.11",
+              "V5.2.12",
+              "V5.2.13",
+              "V5.3.1",
+              "V5.3.3",
+              "V5.3.4",
+              "V5.3.7",
+              "V5.3.8",
+              "V5.3.10",
+              "V5.3.11",
+              "V5.3.12",
+              "V5.3.13",
+              "V5.4.1",
+              "V5.4.3",
+              "V5.4.4",
+              "V5.5.2",
+              "V5.5.3",
+              "V5.5.5",
+              "V5.6.1",
+              "V5.6.2",
+              "V5.6.3",
+              "V1.6.1",
+              "V1.6.4",
+              "V1.6.5",
+              "V6.2.1",
+              "V6.2.2",
+              "V6.2.4",
+              "V6.2.8",
+              "V6.2.9",
+              "V6.3.1",
+              "V6.3.3",
+              "V6.5.1",
+              "V6.5.2",
+              "V6.5.3",
+              "V6.5.4",
+              "V6.5.5",
+              "V6.6.1",
+              "V6.6.2",
+              "V6.6.3",
+              "V6.6.4",
+              "V6.7.1",
+              "V6.8.1",
+              "V6.8.2",
+              "V6.9.1",
+              "V6.9.2",
+              "V1.7.3",
+              "V7.1.1",
+              "V7.1.4",
+              "V7.1.5",
+              "V7.1.6",
+              "V7.1.7",
+              "V7.2.1",
+              "V7.2.2",
+              "V7.2.3",
+              "V7.2.4",
+              "V7.2.5",
+              "V7.2.6",
+              "V7.2.7",
+              "V7.3.1",
+              "V7.3.3",
+              "V7.3.5",
+              "V7.4.1",
+              "V7.4.2",
+              "V7.4.3",
+              "V7.4.4",
+              "V7.4.5",
+              "V1.8.1",
+              "V1.8.2",
+              "V8.1.1",
+              "V8.1.4",
+              "V8.1.7",
+              "V8.1.8",
+              "V8.1.9",
+              "V8.1.10",
+              "V8.2.1",
+              "V8.2.2",
+              "V8.2.3",
+              "V8.3.1",
+              "V8.3.8",
+              "V8.3.9",
+              "V9.1.1",
+              "V9.1.4",
+              "V9.2.2",
+              "V9.2.6",
+              "V9.3.1",
+              "V9.3.2",
+              "V9.3.3",
+              "V9.4.1",
+              "V9.4.2",
+              "V9.4.3",
+              "V9.4.4",
+              "V9.4.5",
+              "V1.10.2",
+              "V1.10.3",
+              "V1.10.4",
+              "V10.3.1",
+              "V10.4.1",
+              "V10.4.2",
+              "V10.4.3",
+              "V10.4.4",
+              "V10.4.5",
+              "V10.4.6",
+              "V10.5.1",
+              "V10.6.1",
+              "V10.6.2",
+              "V10.7.1",
+              "V10.7.2",
+              "V10.7.3",
+              "V10.7.4",
+              "V10.7.5",
+              "V10.7.6",
+              "V1.11.4",
+              "V11.1.1",
+              "V11.1.3",
+              "V11.1.9",
+              "V11.1.10",
+              "V11.2.1",
+              "V11.2.2",
+              "V1.12.3",
+              "V12.1.1",
+              "V12.1.2",
+              "V12.1.3",
+              "V12.1.4",
+              "V12.2.1",
+              "V12.2.2",
+              "V12.3.1",
+              "V12.3.7",
+              "V12.4.1",
+              "V12.4.2",
+              "V12.5.3",
+              "V12.5.4",
+              "V12.7.1",
+              "V13.1.6",
+              "V13.1.7",
+              "V13.1.8",
+              "V13.2.2",
+              "V13.2.5",
+              "V13.4.1",
+              "V13.4.2",
+              "V13.4.3",
+              "V13.5.1",
+              "V13.5.2",
+              "V13.5.3",
+              "V13.5.4",
+              "V13.6.1",
+              "V13.6.2",
+              "V13.6.3",
+              "V13.6.4",
+              "V13.7.1",
+              "V13.7.2",
+              "V13.7.3",
+              "V1.14.7",
+              "V14.1.2",
+              "V14.1.3",
+              "V14.1.5",
+              "V14.1.6",
+              "V14.1.7",
+              "V14.1.8",
+              "V14.1.9",
+              "V14.1.10",
+              "V14.3.2",
+              "V14.3.3",
+              "V14.3.4",
+              "V14.3.5",
+              "V14.3.6",
+              "V14.6.1",
+              "V14.6.2",
+              "V14.7.1",
+              "V14.7.2",
+              "V14.7.3",
+              "V14.8.1",
+              "V14.8.2",
+              "V14.8.3",
+              "V14.8.4",
+              "V1.50.1",
+              "V50.1.1",
+              "V50.2.1",
+              "V50.2.2",
+              "V50.2.3",
+              "V50.2.4",
+              "V50.2.5",
+              "V50.3.1",
+              "V50.3.2",
+              "V50.3.3",
+              "V50.3.4",
+              "V50.3.5",
+              "V50.3.6",
+              "V50.3.7",
+              "V50.4.1",
+              "V50.4.2",
+              "V50.4.3",
+              "V50.5.1",
+              "V50.5.2",
+              "V50.6.1",
+              "V50.6.2",
+              "V50.7.1",
+              "V50.8.1",
+              "V50.8.2",
+              "V50.8.3",
+              "V50.8.4",
+              "V51.1.1",
+              "V51.1.2",
+              "V51.2.1",
+              "V51.2.2",
+              "V51.2.3",
+              "V51.3.1",
+              "V51.3.2",
+              "V51.3.3",
+              "V51.3.4",
+              "V51.4.1",
+              "V51.4.2",
+              "V51.4.3",
+              "V51.4.4",
+              "V51.4.5",
+              "V51.4.6",
+              "V51.4.7",
+              "V51.4.8",
+              "V51.4.9",
+              "V51.4.10",
+              "V51.4.11",
+              "V51.4.12",
+              "V51.4.13",
+              "V51.4.14",
+              "V51.4.15",
+              "V51.5.1",
+              "V51.5.2",
+              "V51.5.3",
+              "V51.5.4",
+              "V51.6.1",
+              "V51.7.1",
+              "V51.7.2",
+              "V51.7.3",
+              "V52.1.1",
+              "V52.1.2",
+              "V52.1.3",
+              "V52.2.1",
+              "V52.2.2",
+              "V52.2.3",
+              "V53.1.1",
+              "V53.1.2",
+              "V53.2.1",
+              "V53.2.2",
+              "V53.2.3",
+              "V53.2.4",
+              "V53.2.5",
+              "V53.2.6",
+              "V53.2.7",
+              "V53.2.8",
+              "V53.3.1",
+              "V53.3.2"
+            ]
+          }
+        ],
+        "externalReferences": [
+          {
+            "type": "website",
+            "url": "https://owasp.org/asvs"
+          },
+          {
+            "type": "vcs",
+            "url": "https://github.com/OWASP/ASVS"
+          },
+          {
+            "type": "issue-tracker",
+            "url": "https://github.com/OWASP/ASVS/issues"
+          },
+          {
+            "type": "social",
+            "url": "https://twitter.com/OWASP_ASVS"
+          }
+        ]
+      }
+    ]
+  }
+}
diff --git a/docs/CLI.md b/docs/CLI.md
index f786b5126..7ea954335 100644
--- a/docs/CLI.md
+++ b/docs/CLI.md
@@ -117,8 +117,8 @@ Options:
       --standard               The list of standards which may consist of regulations, industry or organizational-specif
                                ic standards, maturity models, best practices, or any other requirements which can be eva
                                luated against or attested to.
-  [array] [choices: "asvs-4.0.3", "bsimm-v13", "masvs-2.0.0", "nist_ssdf-1.1", "pcissc-secure-slc-1.1", "scvs-1.0.0", "s
-                                                                                                     saf-DRAFT-2023-11"]
+  [array] [choices: "asvs-5.0", "asvs-4.0.3", "bsimm-v13", "masvs-2.0.0", "nist_ssdf-1.1", "pcissc-secure-slc-1.1", "scv
+                                                                                         s-1.0.0", "ssaf-DRAFT-2023-11"]
       --min-confidence         Minimum confidence needed for the identity of a component from 0 - 1, where 1 is 100% con
                                fidence.                                                            [number] [default: 0]
       --technique              Analysis technique to use