SONAR-22543 Introduce STIG & CASA reports

8 files changed, 2448 insertions, 126 deletions

diff --git a/server/sonar-web/src/main/js/apps/issues/sidebar/StandardFacet.tsx b/server/sonar-web/src/main/js/apps/issues/sidebar/StandardFacet.tsx
index fe35647d881..67a7c48c2ed 100644
--- a/server/sonar-web/src/main/js/apps/issues/sidebar/StandardFacet.tsx
+++ b/server/sonar-web/src/main/js/apps/issues/sidebar/StandardFacet.tsx
@@ -92,6 +92,8 @@ export class StandardFacet extends React.PureComponent<Props, State> {
       sonarsourceSecurity: {},
       'pciDss-3.2': {},
       'pciDss-4.0': {},
+      'stig-ASD_V5R3': {},
+      casa: {},
       'owaspAsvs-4.0': {},
     },
   };
@@ -124,24 +126,28 @@ export class StandardFacet extends React.PureComponent<Props, State> {
   loadStandards = () => {
     getStandards().then(
       ({
-        'owaspTop10-2021': owaspTop102021,
-        owaspTop10,
-        cwe,
-        sonarsourceSecurity,
-        'pciDss-3.2': pciDss32,
-        'pciDss-4.0': pciDss40,
-        'owaspAsvs-4.0': owaspAsvs40,
+        [SecurityStandard.OWASP_TOP10_2021]: owaspTop102021,
+        [SecurityStandard.OWASP_TOP10]: owaspTop10,
+        [SecurityStandard.CWE]: cwe,
+        [SecurityStandard.SONARSOURCE]: sonarsourceSecurity,
+        [SecurityStandard.PCI_DSS_3_2]: pciDss32,
+        [SecurityStandard.PCI_DSS_4_0]: pciDss40,
+        [SecurityStandard.OWASP_ASVS_4_0]: owaspAsvs40,
+        [SecurityStandard.STIG_ASD_V5R3]: stigV5,
+        [SecurityStandard.CASA]: casa,
       }: Standards) => {
         if (this.mounted) {
           this.setState({
             standards: {
-              'owaspTop10-2021': owaspTop102021,
-              owaspTop10,
-              cwe,
-              sonarsourceSecurity,
-              'pciDss-3.2': pciDss32,
-              'pciDss-4.0': pciDss40,
-              'owaspAsvs-4.0': owaspAsvs40,
+              [SecurityStandard.OWASP_TOP10_2021]: owaspTop102021,
+              [SecurityStandard.OWASP_TOP10]: owaspTop10,
+              [SecurityStandard.CWE]: cwe,
+              [SecurityStandard.SONARSOURCE]: sonarsourceSecurity,
+              [SecurityStandard.PCI_DSS_3_2]: pciDss32,
+              [SecurityStandard.PCI_DSS_4_0]: pciDss40,
+              [SecurityStandard.OWASP_ASVS_4_0]: owaspAsvs40,
+              [SecurityStandard.STIG_ASD_V5R3]: stigV5,
+              [SecurityStandard.CASA]: casa,
             },
           });
         }
diff --git a/server/sonar-web/src/main/js/apps/security-hotspots/SecurityHotspotsApp.tsx b/server/sonar-web/src/main/js/apps/security-hotspots/SecurityHotspotsApp.tsx
index ad7e8adf121..d00d9e9154c 100644
--- a/server/sonar-web/src/main/js/apps/security-hotspots/SecurityHotspotsApp.tsx
+++ b/server/sonar-web/src/main/js/apps/security-hotspots/SecurityHotspotsApp.tsx
@@ -107,6 +107,8 @@ export class SecurityHotspotsApp extends React.PureComponent<Props, State> {
         [SecurityStandard.PCI_DSS_3_2]: {},
         [SecurityStandard.PCI_DSS_4_0]: {},
         [SecurityStandard.SONARSOURCE]: {},
+        [SecurityStandard.CASA]: {},
+        [SecurityStandard.STIG_ASD_V5R3]: {},
       },
     };
   }
diff --git a/server/sonar-web/src/main/js/apps/security-hotspots/utils.ts b/server/sonar-web/src/main/js/apps/security-hotspots/utils.ts
index c46e679d2c6..aeb4952dc22 100644
--- a/server/sonar-web/src/main/js/apps/security-hotspots/utils.ts
+++ b/server/sonar-web/src/main/js/apps/security-hotspots/utils.ts
@@ -20,6 +20,7 @@
 import { HotspotRatingEnum } from 'design-system';
 import { flatten, groupBy, sortBy } from 'lodash';
 import {
+  renderCASACategory,
   renderCWECategory,
   renderOwaspAsvs40Category,
   renderOwaspTop102021Category,
@@ -27,6 +28,7 @@ import {
   renderPciDss32Category,
   renderPciDss40Category,
   renderSonarSourceSecurityCategory,
+  renderStigCategory,
 } from '../../helpers/security-standard';
 import { SecurityStandard } from '../../types/security';
 import {
@@ -61,6 +63,8 @@ export const SECURITY_STANDARDS = [
   SecurityStandard.PCI_DSS_3_2,
   SecurityStandard.PCI_DSS_4_0,
   SecurityStandard.OWASP_ASVS_4_0,
+  SecurityStandard.CASA,
+  SecurityStandard.STIG_ASD_V5R3,
 ];
 
 export const SECURITY_STANDARD_RENDERER = {
@@ -71,6 +75,8 @@ export const SECURITY_STANDARD_RENDERER = {
   [SecurityStandard.PCI_DSS_3_2]: renderPciDss32Category,
   [SecurityStandard.PCI_DSS_4_0]: renderPciDss40Category,
   [SecurityStandard.OWASP_ASVS_4_0]: renderOwaspAsvs40Category,
+  [SecurityStandard.CASA]: renderCASACategory,
+  [SecurityStandard.STIG_ASD_V5R3]: renderStigCategory,
 };
 
 export function mapRules(rules: Array<{ key: string; name: string }>): Dict<string> {
diff --git a/server/sonar-web/src/main/js/helpers/__tests__/security-standard-test.ts b/server/sonar-web/src/main/js/helpers/__tests__/security-standard-test.ts
index 855827264b8..b5cc582e35c 100644
--- a/server/sonar-web/src/main/js/helpers/__tests__/security-standard-test.ts
+++ b/server/sonar-web/src/main/js/helpers/__tests__/security-standard-test.ts
@@ -19,16 +19,17 @@
  */
 import { Standards } from '../../types/security';
 import {
+  renderCASACategory,
   renderCWECategory,
   renderOwaspAsvs40Category,
-  renderOwaspTop102021Category,
   renderOwaspTop10Category,
   renderPciDss32Category,
   renderPciDss40Category,
   renderSonarSourceSecurityCategory,
+  renderStigCategory,
 } from '../security-standard';
 
-describe('renderCWECategory', () => {
+describe('standards renderers', () => {
   const standards: Standards = {
     cwe: {
       '1004': {
@@ -38,118 +39,34 @@ describe('renderCWECategory', () => {
         title: 'No CWE associated',
       },
     },
-    owaspTop10: {},
-    'owaspTop10-2021': {},
-    sonarsourceSecurity: {},
-    'pciDss-3.2': {},
-    'pciDss-4.0': {},
-    'owaspAsvs-4.0': {},
-  };
-  it('should render cwe categories correctly', () => {
-    expect(renderCWECategory(standards, '1004')).toEqual(
-      "CWE-1004 - Sensitive Cookie Without 'HttpOnly' Flag",
-    );
-    expect(renderCWECategory(standards, '124')).toEqual('CWE-124');
-    expect(renderCWECategory(standards, 'unknown')).toEqual('No CWE associated');
-  });
-});
-
-describe('renderOwaspTop10Category', () => {
-  const standards: Standards = {
-    cwe: {},
     owaspTop10: {
       a1: {
         title: 'Injection',
       },
     },
-    'owaspTop10-2021': {},
-    sonarsourceSecurity: {},
-    'pciDss-3.2': {},
-    'pciDss-4.0': {},
-    'owaspAsvs-4.0': {},
-  };
-  it('should render owasp categories correctly', () => {
-    expect(renderOwaspTop10Category(standards, 'a1')).toEqual('A1 - Injection');
-    expect(renderOwaspTop10Category(standards, 'a1', true)).toEqual('OWASP A1 - Injection');
-    expect(renderOwaspTop10Category(standards, 'a2')).toEqual('A2');
-    expect(renderOwaspTop10Category(standards, 'a2', true)).toEqual('OWASP A2');
-  });
-});
-
-describe('renderOwaspTop102021Category', () => {
-  const standards: Standards = {
-    cwe: {},
-    owaspTop10: {},
     'owaspTop10-2021': {
       a1: {
         title: 'Injection',
       },
     },
-    sonarsourceSecurity: {},
-    'pciDss-3.2': {},
-    'pciDss-4.0': {},
-    'owaspAsvs-4.0': {},
-  };
-  it('should render owasp categories correctly', () => {
-    expect(renderOwaspTop102021Category(standards, 'a1')).toEqual('A1 - Injection');
-    expect(renderOwaspTop102021Category(standards, 'a1', true)).toEqual('OWASP A1 - Injection');
-    expect(renderOwaspTop102021Category(standards, 'a2')).toEqual('A2');
-    expect(renderOwaspTop102021Category(standards, 'a2', true)).toEqual('OWASP A2');
-  });
-});
-
-describe('renderPciDss32Category', () => {
-  const standards: Standards = {
-    cwe: {},
-    owaspTop10: {},
-    'owaspTop10-2021': {},
-    sonarsourceSecurity: {},
+    sonarsourceSecurity: {
+      xss: {
+        title: 'Cross-Site Scripting (XSS)',
+      },
+      others: {
+        title: 'Others',
+      },
+    },
     'pciDss-3.2': {
       '1': {
         title: 'Install and maintain a firewall configuration to protect cardholder data',
       },
     },
-    'pciDss-4.0': {},
-    'owaspAsvs-4.0': {},
-  };
-  it('should render Pci Dss 3.2 correctly', () => {
-    expect(renderPciDss32Category(standards, '1')).toEqual(
-      '1 - Install and maintain a firewall configuration to protect cardholder data',
-    );
-    expect(renderPciDss32Category(standards, '1.1')).toEqual('1.1');
-  });
-});
-
-describe('renderPciDss40Category', () => {
-  const standards: Standards = {
-    cwe: {},
-    owaspTop10: {},
-    'owaspTop10-2021': {},
-    sonarsourceSecurity: {},
-    'pciDss-3.2': {},
     'pciDss-4.0': {
       '1': {
         title: 'Install and maintain a firewall configuration to protect cardholder data',
       },
     },
-    'owaspAsvs-4.0': {},
-  };
-  it('should render Pci Dss 4.0 correctly', () => {
-    expect(renderPciDss40Category(standards, '1')).toEqual(
-      '1 - Install and maintain a firewall configuration to protect cardholder data',
-    );
-    expect(renderPciDss40Category(standards, '1.1')).toEqual('1.1');
-  });
-});
-
-describe('renderOwaspAsvs40Category', () => {
-  const standards: Standards = {
-    cwe: {},
-    owaspTop10: {},
-    'owaspTop10-2021': {},
-    sonarsourceSecurity: {},
-    'pciDss-3.2': {},
-    'pciDss-4.0': {},
     'owaspAsvs-4.0': {
       '1': {
         title: 'Main category',
@@ -159,30 +76,52 @@ describe('renderOwaspAsvs40Category', () => {
         level: '2',
       },
     },
+    casa: {
+      '1': {
+        title: 'Main category',
+      },
+    },
+    'stig-ASD_V5R3': {
+      'v-123': {
+        title: 'Stig requirement',
+      },
+    },
   };
+
+  it('should render cwe categories correctly', () => {
+    expect(renderCWECategory(standards, '1004')).toEqual(
+      "CWE-1004 - Sensitive Cookie Without 'HttpOnly' Flag",
+    );
+    expect(renderCWECategory(standards, '124')).toEqual('CWE-124');
+    expect(renderCWECategory(standards, 'unknown')).toEqual('No CWE associated');
+  });
+
+  it('should render owasp categories correctly', () => {
+    expect(renderOwaspTop10Category(standards, 'a1')).toEqual('A1 - Injection');
+    expect(renderOwaspTop10Category(standards, 'a1', true)).toEqual('OWASP A1 - Injection');
+    expect(renderOwaspTop10Category(standards, 'a2')).toEqual('A2');
+    expect(renderOwaspTop10Category(standards, 'a2', true)).toEqual('OWASP A2');
+  });
+
   it('should render OwaspAsvs 4.0 correctly', () => {
     expect(renderOwaspAsvs40Category(standards, '1')).toEqual('1 - Main category');
     expect(renderOwaspAsvs40Category(standards, '1.1')).toEqual('1.1 - Sub category (Level 2)');
   });
-});
 
-describe('renderSonarSourceSecurityCategory', () => {
-  const standards: Standards = {
-    cwe: {},
-    owaspTop10: {},
-    'owaspTop10-2021': {},
-    sonarsourceSecurity: {
-      xss: {
-        title: 'Cross-Site Scripting (XSS)',
-      },
-      others: {
-        title: 'Others',
-      },
-    },
-    'pciDss-3.2': {},
-    'pciDss-4.0': {},
-    'owaspAsvs-4.0': {},
-  };
+  it('should render Pci Dss 3.2 correctly', () => {
+    expect(renderPciDss32Category(standards, '1')).toEqual(
+      '1 - Install and maintain a firewall configuration to protect cardholder data',
+    );
+    expect(renderPciDss32Category(standards, '1.1')).toEqual('1.1');
+  });
+
+  it('should render Pci Dss 4.0 correctly', () => {
+    expect(renderPciDss40Category(standards, '1')).toEqual(
+      '1 - Install and maintain a firewall configuration to protect cardholder data',
+    );
+    expect(renderPciDss40Category(standards, '1.1')).toEqual('1.1');
+  });
+
   it('should render sonarsource categories correctly', () => {
     expect(renderSonarSourceSecurityCategory(standards, 'xss')).toEqual(
       'Cross-Site Scripting (XSS)',
@@ -193,4 +132,14 @@ describe('renderSonarSourceSecurityCategory', () => {
     expect(renderSonarSourceSecurityCategory(standards, 'others')).toEqual('Others');
     expect(renderSonarSourceSecurityCategory(standards, 'others', true)).toEqual('Others');
   });
+
+  it('should render casa categories correctly', () => {
+    expect(renderCASACategory(standards, '1')).toEqual('1 - Main category');
+    expect(renderCASACategory(standards, '2')).toEqual('2');
+  });
+
+  it('should render stig requirements correctly', () => {
+    expect(renderStigCategory(standards, 'v-123')).toEqual('v-123 - Stig requirement');
+    expect(renderStigCategory(standards, 'none')).toEqual('none');
+  });
 });
diff --git a/server/sonar-web/src/main/js/helpers/mocks/security-hotspots.ts b/server/sonar-web/src/main/js/helpers/mocks/security-hotspots.ts
index ccb2f630b0e..85e1a8cfb98 100644
--- a/server/sonar-web/src/main/js/helpers/mocks/security-hotspots.ts
+++ b/server/sonar-web/src/main/js/helpers/mocks/security-hotspots.ts
@@ -188,5 +188,15 @@ export function mockStandards(): Standards {
         title: 'New OWASP ASVS cat 1',
       },
     },
+    'stig-ASD_V5R3': {
+      'V-123': {
+        title: 'STIG requirement 123',
+      },
+    },
+    casa: {
+      '1': {
+        title: 'New CASA cat 1',
+      },
+    },
   };
 }
diff --git a/server/sonar-web/src/main/js/helpers/security-standard.ts b/server/sonar-web/src/main/js/helpers/security-standard.ts
index 012dcbf5086..83a2f46391c 100644
--- a/server/sonar-web/src/main/js/helpers/security-standard.ts
+++ b/server/sonar-web/src/main/js/helpers/security-standard.ts
@@ -104,3 +104,16 @@ export function renderOwaspAsvs40Category(standards: Standards, category: string
 function addPrefix(title: string, prefix: string, withPrefix: boolean) {
   return withPrefix ? `${prefix} ${title}` : title;
 }
+
+export function renderCASACategory(standards: Standards, category: string): string {
+  const record = standards['casa'][category];
+  if (!record) {
+    return category;
+  }
+  return `${category} - ${record.title}`;
+}
+
+export function renderStigCategory(standards: Standards, category: string) {
+  const record = standards['stig-ASD_V5R3'][category];
+  return record ? `${category} - ${record.title}` : category;
+}
diff --git a/server/sonar-web/src/main/js/helpers/standards.json b/server/sonar-web/src/main/js/helpers/standards.json
index fbcfcd5f5a0..22fa3d377bb 100644
--- a/server/sonar-web/src/main/js/helpers/standards.json
+++ b/server/sonar-web/src/main/js/helpers/standards.json
@@ -5260,5 +5260,2339 @@
       "title": "Verify that HTTP headers added by a trusted proxy or SSO devices, such as a bearer token, are authenticated by the application.",
       "level": "2"
     }
+  },
+  "stig-ASD_V5R3": {
+    "V-222400": {
+        "title": "Validity periods must be verified on all application messages using WS-Security or SAML assertions.",
+        "description": "When using WS-Security in SOAP messages, the application should check the validity of the time stamps with creation and expiration times. Time stamps that are not validated may lead to a replay..."
+    },
+    "V-222404": {
+        "title": "The application must use both the NotBefore and NotOnOrAfter elements or OneTimeUse element when using the Conditions element in a SAML assertion.",
+        "description": "SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens containing assertions to pass information about a principal (usually an..."
+    },
+    "V-222612": {
+        "title": "The application must not be vulnerable to overflow attacks.",
+        "description": "A buffer overflow occurs when a program exceeds the amount of data allocated to a buffer. The buffer is a sequential section of memory and when the data is written outside the memory bounds, the..."
+    },
+    "V-222578": {
+        "title": "The application must destroy the session ID value and/or cookie on logoff or browser close.",
+        "description": "Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever possible it is recommended to utilize the provided session management..."
+    },
+    "V-222430": {
+        "title": "The application must execute without excessive account permissions.",
+        "description": "Applications are often designed to utilize a user account. The account represents a means to control application permissions and access to OS resources, application resources or both. When the..."
+    },
+    "V-222432": {
+        "title": "The application must enforce the limit of three consecutive invalid logon attempts by a user during a 15 minute time period.",
+        "description": "By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the..."
+    },
+    "V-222577": {
+        "title": "The application must not expose session IDs.",
+        "description": "Authenticity protection provides protection against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions. Application communication sessions are..."
+    },
+    "V-222609": {
+        "title": "The application must not be subject to input handling vulnerabilities.",
+        "description": "A common application vulnerability is unpredictable behavior due to improper input validation. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where..."
+    },
+    "V-222608": {
+        "title": "The application must not be vulnerable to XML-oriented attacks.",
+        "description": "Extensible Markup Language (XML) is widely employed in web technology and applications like web services (SOAP, REST, and WSDL) and is also used for configuration files. XML vulnerability examples..."
+    },
+    "V-222602": {
+        "title": "The application must protect from Cross-Site Scripting (XSS) vulnerabilities.",
+        "description": "XSS attacks are essentially code injection attacks against the various language interpreters contained within the browser. XSS can be executed via HTML, JavaScript, VBScript, ActiveX; essentially..."
+    },
+    "V-222601": {
+        "title": "The application must not store sensitive information in hidden fields.",
+        "description": "Hidden fields allow developers to process application data without having to display it on the screen. Using hidden fields to pass data in forms is a common practice among web applications and by..."
+    },
+    "V-222607": {
+        "title": "The application must not be vulnerable to SQL Injection.",
+        "description": "SQL Injection is a code injection attack against database applications. Malicious SQL statements are inserted into an application data entry field where they are submitted to the database and..."
+    },
+    "V-222604": {
+        "title": "The application must protect from command injection.",
+        "description": "A command injection attack is an attack on a vulnerable application where improperly validated input is passed to a command shell setup in the application. The result is the ability of an attacker..."
+    },
+    "V-222403": {
+        "title": "The application must use the NotOnOrAfter condition when using the SubjectConfirmation element in a SAML assertion.",
+        "description": "SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens containing assertions to pass information about a principal (usually an..."
+    },
+    "V-222585": {
+        "title": "The application must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.",
+        "description": "Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized access to system resources. Applications or systems that fail suddenly and..."
+    },
+    "V-222550": {
+        "title": "The application, when utilizing PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.",
+        "description": "Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. A trust anchor is an authoritative..."
+    },
+    "V-222522": {
+        "title": "The application must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).",
+        "description": "To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational..."
+    },
+    "V-222554": {
+        "title": "The application must not display passwords/PINs as clear text.",
+        "description": "To prevent the compromise of authentication information such as passwords during the authentication process, the feedback from the information system must not provide any information that would..."
+    },
+    "V-222596": {
+        "title": "The application must protect the confidentiality and integrity of transmitted information.",
+        "description": "Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This..."
+    },
+    "V-222399": {
+        "title": "Messages protected with WS_Security must use time stamps with creation and expiration times.",
+        "description": "The lack of time stamps could lead to the eventual replay of the message, leaving the application susceptible to replay events which may result in an immediate loss of confidentiality."
+    },
+    "V-222658": {
+        "title": "All products must be supported by the vendor or the development team.",
+        "description": "Unsupported commercial and government developed software products should not be used because fixes to newly identified bugs will not be implemented by the vendor or development team. The lack of..."
+    },
+    "V-222659": {
+        "title": "The application must be decommissioned when maintenance or support is no longer available.",
+        "description": "Unsupported software products should not be used because fixes to newly identified bugs will not be implemented by the vendor or development team. The lack of security updates can result in..."
+    },
+    "V-222551": {
+        "title": "The application, when using PKI-based authentication, must enforce authorized access to the corresponding private key.",
+        "description": "If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. The cornerstone of the PKI is the private key..."
+    },
+    "V-222620": {
+        "title": "Application web servers must be on a separate network segment from the application and database servers if it is a tiered application operating in the DoD DMZ.",
+        "description": "A tiered application usually consists of 3 tiers, the web layer (presentation tier), the application layer (application logic tier), and the database layer (data storage tier). Using one system..."
+    },
+    "V-222536": {
+        "title": "The application must enforce a minimum 15-character password length.",
+        "description": "The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. Use of passwords for application authentication is intended only..."
+    },
+    "V-222643": {
+        "title": "The application must have the capability to mark sensitive/classified output when required.",
+        "description": "Failure to properly mark output could result in a disclosure of sensitive or classified data which is an immediate loss in confidentiality."
+    },
+    "V-222542": {
+        "title": "The application must only store cryptographic representations of passwords.",
+        "description": "Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations..."
+    },
+    "V-222543": {
+        "title": "The application must transmit only cryptographically-protected passwords.",
+        "description": "Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations..."
+    },
+    "V-222425": {
+        "title": "The application must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.",
+        "description": "To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., networks, web servers, and web..."
+    },
+    "V-222642": {
+        "title": "The application must not contain embedded authentication data.",
+        "description": "Authentication data stored in code could potentially be read and used by anonymous users to gain access to a backend database or application servers. This could lead to compromise of application data."
+    },
+    "V-222662": {
+        "title": "Default passwords must be changed.",
+        "description": "Default passwords can easily be compromised by attackers allowing immediate access to the applications."
+    },
+    "V-222555": {
+        "title": "The application must use mechanisms meeting the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module.",
+        "description": "A cryptographic module is a hardware or software device or component that performs cryptographic operations securely within a physical or logical boundary, using a hardware, software or hybrid..."
+    },
+    "V-222541": {
+        "title": "The application must require the change of at least 8 of the total number of characters when passwords are changed.",
+        "description": "Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations..."
+    },
+    "V-222395": {
+        "title": "The application must associate organization-defined types of security attributes having organization-defined security attribute values with information in transmission.",
+        "description": "Without the association of security attributes to information, there is no basis for the application to make security related access-control decisions. Security attributes are abstractions..."
+    },
+    "V-222491": {
+        "title": "The application must provide an audit reduction capability that supports after-the-fact investigations of security incidents.",
+        "description": "If the audit reduction capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack, or identify..."
+    },
+    "V-222409": {
+        "title": "The application must automatically remove or disable temporary user accounts 72 hours after account creation.",
+        "description": "If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of..."
+    },
+    "V-222408": {
+        "title": "Shared/group account credentials must be terminated when members leave the group.",
+        "description": "If shared/group account credentials are not terminated when individuals leave the group, the user that left the group can still gain access even though they are no longer authorized. A..."
+    },
+    "V-222560": {
+        "title": "The application must conform to FICAM-issued profiles.",
+        "description": "FICAM establishes a federated identity framework for the Federal Government. FICAM provides Government-wide services for common Identity, Credential, and Access Management (ICAM) requirements. ..."
+    },
+    "V-222561": {
+        "title": "Applications used for non-local maintenance sessions must audit non-local maintenance and diagnostic sessions for organization-defined auditable events.",
+        "description": "Non-local maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal..."
+    },
+    "V-222566": {
+        "title": "The application must terminate all sessions and network connections when non-local maintenance is completed.",
+        "description": "If a maintenance session or connection remains open after maintenance is completed, it may be hijacked by an attacker and used to compromise or damage the system. Non-local maintenance and..."
+    },
+    "V-222567": {
+        "title": "The application must not be vulnerable to race conditions.",
+        "description": "A race condition is a timing event within an application that can become a security vulnerability. A race condition can occur when a pair of programming calls operating simultaneously do not work..."
+    },
+    "V-222564": {
+        "title": "Applications used for non-local maintenance sessions must verify remote disconnection at the termination of non-local maintenance and diagnostic sessions.",
+        "description": "Non-local maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal..."
+    },
+    "V-222565": {
+        "title": "The application must employ strong authenticators in the establishment of non-local maintenance and diagnostic sessions.",
+        "description": "If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the system. The act of managing systems and applications includes the ability..."
+    },
+    "V-222401": {
+        "title": "The application must ensure each unique asserting party provides unique assertion ID references for each SAML assertion.",
+        "description": "SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens containing assertions to pass information about a principal (usually an..."
+    },
+    "V-222568": {
+        "title": "The application must terminate all network connections associated with a communications session at the end of the session.",
+        "description": "Networked applications routinely open connections to and from other systems as part of their design and function. When connections are opened by the application, system resources are consumed. ..."
+    },
+    "V-222402": {
+        "title": "The application must ensure encrypted assertions, or equivalent confidentiality protections are used when assertion data is passed through an intermediary, and confidentiality of the assertion data is required when passing through the intermediary.",
+        "description": "SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens containing assertions to pass information about a principal (usually an..."
+    },
+    "V-222405": {
+        "title": "The application must ensure if a OneTimeUse element is used in an assertion, there is only one of the same used in the Conditions element portion of an assertion.",
+        "description": "Multiple <OneTimeUse> elements used in a SAML assertion can lead to elevation of privileges, if the application does not process SAML assertions correctly."
+    },
+    "V-222407": {
+        "title": "The application must provide automated mechanisms for supporting account management functions.",
+        "description": "Enterprise environments make application account management challenging and complex. A manual process for account management functions adds the risk of a potential oversight or other..."
+    },
+    "V-222406": {
+        "title": "The application must ensure messages are encrypted when the SessionIndex is tied to privacy data.",
+        "description": "When the SessionIndex is tied to privacy data (e.g., attributes containing privacy data) the message should be encrypted. If the message is not encrypted there is the possibility of compromise of..."
+    },
+    "V-222618": {
+        "title": "Unsigned Category 1A mobile code must not be used in the application in accordance with DoD policy.",
+        "description": "Use of un-trusted Level 1A mobile code technologies can introduce security vulnerabilities and malicious code into the client system. 1A code is defined as: - ActiveX controls - Mobile code..."
+    },
+    "V-222619": {
+        "title": "The ISSO must ensure an account management process is implemented, verifying only authorized users can gain access to the application, and individual accounts designated as inactive, suspended, or terminated are promptly removed.",
+        "description": "A comprehensive account management process will ensure that only authorized users can gain access to applications and that individual accounts designated as inactive, suspended, or terminated are..."
+    },
+    "V-222413": {
+        "title": "The application must automatically audit account creation.",
+        "description": "Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to..."
+    },
+    "V-222610": {
+        "title": "The application must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.",
+        "description": "Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify application components...."
+    },
+    "V-222579": {
+        "title": "Applications must use system-generated session identifiers that protect against session fixation.",
+        "description": "Session fixation allows an attacker to hijack a valid user’s application session. The attack focuses on the manner in which a web application manages the user’s session ID. Applications become..."
+    },
+    "V-222613": {
+        "title": "The application must remove organization-defined software components after updated versions have been installed.",
+        "description": "Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products..."
+    },
+    "V-222614": {
+        "title": "Security-relevant software updates and patches must be kept up to date.",
+        "description": "Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations..."
+    },
+    "V-222615": {
+        "title": "The application performing organization-defined security functions must verify correct operation of security functions.",
+        "description": "Without verification, security functions may not operate correctly and this failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information..."
+    },
+    "V-222616": {
+        "title": "The application must perform verification of the correct operation of security functions: upon system startup and/or restart; upon command by a user with privileged access; and/or every 30 days.",
+        "description": "Without verification, security functions may not operate correctly and this failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information..."
+    },
+    "V-222481": {
+        "title": "The application must off-load audit records onto a different system or media than the system being audited.",
+        "description": "Information stored in one location is vulnerable to accidental or incidental deletion or alteration. In addition, attackers often manipulate logs to hide or obfuscate their activity. The goal is..."
+    },
+    "V-222480": {
+        "title": "The application must provide centralized management and configuration of the content to be captured in audit records generated by all application components.",
+        "description": "Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a..."
+    },
+    "V-222483": {
+        "title": "The application must provide an immediate warning to the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of repository maximum audit record storage capacity.",
+        "description": "If security personnel are not notified immediately upon storage volume utilization reaching 75%, they are unable to plan for storage capacity expansion. Due to variances in application usage and..."
+    },
+    "V-222482": {
+        "title": "The application must be configured to write application logs to a centralized log repository.",
+        "description": "Information stored in one location is vulnerable to accidental or incidental deletion or alteration. In addition, attackers often manipulate logs to hide or obfuscate their activity. Off-loading..."
+    },
+    "V-222485": {
+        "title": "The application must alert the ISSO and SA (at a minimum) in the event of an audit processing failure.",
+        "description": "It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an..."
+    },
+    "V-222484": {
+        "title": "Applications categorized as having a moderate or high impact must provide an immediate real-time alert to the SA and ISSO (at a minimum) for all audit failure events.",
+        "description": "Applications that are categorized as having a high or moderate impact on the organization must provide immediate alerts when encountering failures with the application audit system. It is..."
+    },
+    "V-222487": {
+        "title": "The application must provide the capability to centrally review and analyze audit records from multiple components within the system.",
+        "description": "Successful incident response and auditing relies on timely, accurate system information and analysis in order to allow the organization to identify and respond to potential incidents in a..."
+    },
+    "V-222486": {
+        "title": "The application must shut down by default upon audit failure (unless availability is an overriding concern).",
+        "description": "It is critical that when the application is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include: software/hardware..."
+    },
+    "V-222489": {
+        "title": "The application must provide an audit reduction capability that supports on-demand reporting requirements.",
+        "description": "The ability to generate on-demand reports, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports as..."
+    },
+    "V-222488": {
+        "title": "The application must provide the capability to filter audit records for events of interest based upon organization-defined criteria.",
+        "description": "The ability to specify the event criteria that are of interest provides the persons reviewing the logs with the ability to quickly isolate and identify these events without having to review..."
+    },
+    "V-222431": {
+        "title": "The application must audit the execution of privileged functions.",
+        "description": "Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious..."
+    },
+    "V-222624": {
+        "title": "The ISSO must ensure active vulnerability testing is performed.",
+        "description": "Use of automated scanning tools accompanied with manual testing/validation which confirms or expands on the automated test results is an accepted best practice when performing application security..."
+    },
+    "V-222575": {
+        "title": "The application must set the HTTPOnly flag on session cookies.",
+        "description": "HTTPOnly is a flag included in a Set-Cookie HTTP response header. If the HTTPOnly flag is included in the HTTP response header, the cookie cannot be accessed through client side scripts like..."
+    },
+    "V-222574": {
+        "title": "The application user interface must be either physically or logically separated from data storage and management interfaces.",
+        "description": "Application management functionality includes functions necessary for administration and requires privileged user access. Allowing non-privileged users to access application management..."
+    },
+    "V-222576": {
+        "title": "The application must set the secure flag on session cookies.",
+        "description": "Many web development frameworks such as PHP, .NET, ASP as well as application servers include their own mechanisms for session management. Whenever possible it is recommended to utilize the..."
+    },
+    "V-222478": {
+        "title": "The application must generate audit records containing the full-text recording of privileged commands or the individual identities of group account users.",
+        "description": "Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. Organizations consider limiting the additional audit information to only..."
+    },
+    "V-222570": {
+        "title": "The application must utilize FIPS-validated cryptographic modules when signing application components.",
+        "description": "Applications that distribute components of the application must sign the components to provide an identity assurance to consumers of the application component. Components can include application..."
+    },
+    "V-222573": {
+        "title": "Applications making SAML assertions must use FIPS-approved random numbers in the generation of SessionIndex in the SAML element AuthnStatement.",
+        "description": "A predictable SessionIndex could lead to an attacker computing a future SessionIndex, thereby, possibly compromising the application. Use of weak or untested encryption algorithms undermines the..."
+    },
+    "V-222572": {
+        "title": "The application must utilize FIPS-validated cryptographic modules when protecting unclassified information that requires cryptographic protection.",
+        "description": "Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards..."
+    },
+    "V-222474": {
+        "title": "The application must produce audit records containing enough information to establish which component, feature or function of the application triggered the audit event.",
+        "description": "It is impossible to establish, correlate, and investigate the events relating to an incident if the details regarding the source of the event it not available. In order to compile an accurate..."
+    },
+    "V-222475": {
+        "title": "When using centralized logging; the application must include a unique identifier in order to distinguish itself from other application logs.",
+        "description": "Without establishing the source, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In the case of centralized logging, or other instances..."
+    },
+    "V-222476": {
+        "title": "The application must produce audit records that contain information to establish the outcome of the events.",
+        "description": "Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the..."
+    },
+    "V-222477": {
+        "title": "The application must generate audit records containing information that establishes the identity of any individual or process associated with the event.",
+        "description": "Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, security personnel cannot determine..."
+    },
+    "V-222470": {
+        "title": "The application must log destination IP addresses.",
+        "description": "The IP addresses of the systems that the application connects to are an important aspect of identifying application network related activity. Recording the IP addresses of the system the..."
+    },
+    "V-222471": {
+        "title": "The application must log user actions involving access to data.",
+        "description": "When users access application data, there is risk of data compromise or seepage if the account used to access is compromised or access is granted improperly. To be able to investigate which..."
+    },
+    "V-222472": {
+        "title": "The application must log user actions involving changes to data.",
+        "description": "When users change/modify application data, there is risk of data compromise if the account used to access is compromised or access is granted improperly. To be able to investigate which account..."
+    },
+    "V-222473": {
+        "title": "The application must produce audit records containing information to establish when (date and time) the events occurred.",
+        "description": "Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment, and..."
+    },
+    "V-222562": {
+        "title": "Applications used for non-local maintenance sessions must implement cryptographic mechanisms to protect the integrity of non-local maintenance and diagnostic communications.",
+        "description": "Privileged access contains control and configuration information which is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms to..."
+    },
+    "V-222563": {
+        "title": "Applications used for non-local maintenance sessions must implement cryptographic mechanisms to protect the confidentiality of non-local maintenance and diagnostic communications.",
+        "description": "Privileged access contains control and configuration information which is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms to..."
+    },
+    "V-222603": {
+        "title": "The application must protect from Cross-Site Request Forgery (CSRF) vulnerabilities.",
+        "description": "Cross-Site Request Forgery (CSRF) is an attack where a website user is forced to execute an unwanted action on a website that he or she is currently authenticated to. An attacker, through social..."
+    },
+    "V-222600": {
+        "title": "The application must not disclose unnecessary information to users.",
+        "description": "Applications should not disclose information not required for the transaction. (e.g., a web application should not divulge the fact there is a SQL server database and/or its version). These..."
+    },
+    "V-222606": {
+        "title": "The application must validate all input.",
+        "description": "Checking the valid syntax and semantics of information system inputs (e.g., character set, length, numerical range, and acceptable values) verifies that inputs match specified definitions for..."
+    },
+    "V-222605": {
+        "title": "The application must protect from canonical representation vulnerabilities.",
+        "description": "Canonical representation vulnerabilities can occur when a data conversion process does not convert the data to its simplest form resulting in the possible misrepresentation of the data. The..."
+    },
+    "V-222391": {
+        "title": "Applications requiring user access authentication must provide a logoff capability for user initiated communication session.",
+        "description": "If a user cannot explicitly end an application session, the session may remain open and be exploited by an attacker. Applications providing user access must provide the ability for users to..."
+    },
+    "V-222497": {
+        "title": "The applications must use internal system clocks to generate time stamps for audit records.",
+        "description": "Without an internal clock used as the reference for the time stored on each event to provide a trusted common reference for the time, forensic analysis would be impeded. Determining the correct..."
+    },
+    "V-222655": {
+        "title": "Threat models must be documented and reviewed for each application release and updated as required by design and functionality changes or when new threats are discovered.",
+        "description": "Threat modeling is an approach for analyzing the security of an application. It is a structured approach that enables you to identify, quantify, and address the security risks associated with an..."
+    },
+    "V-222557": {
+        "title": "The application must accept Personal Identity Verification (PIV) credentials from other federal agencies.",
+        "description": "Access may be denied to authorized users if federal agency PIV credentials are not accepted. Personal Identity Verification (PIV) credentials are those credentials issued by federal agencies that..."
+    },
+    "V-222469": {
+        "title": "The application must log application shutdown events.",
+        "description": "Forensics is a large part of security incident response. Applications must provide a record of their actions so application events can be investigated post-event. Attackers may attempt to shut..."
+    },
+    "V-222468": {
+        "title": "The application must initiate session auditing upon startup.",
+        "description": "If the application does not begin logging upon startup, important log events could be missed."
+    },
+    "V-222467": {
+        "title": "The application must generate audit records for all account creations, modifications, disabling, and termination events.",
+        "description": "When application user accounts are created, modified, disabled or terminated the event must be logged. Centralized management of user accounts allows for rapid response to user related security..."
+    },
+    "V-222466": {
+        "title": "The application must generate audit records for all direct access to the information system.",
+        "description": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an..."
+    },
+    "V-222465": {
+        "title": "The application must generate audit records when successful/unsuccessful accesses to objects occur.",
+        "description": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an..."
+    },
+    "V-222464": {
+        "title": "The application must generate audit records showing starting and ending time for user access to the system.",
+        "description": "Knowing when a user’s application session began and when it ended is critical information that aids in forensic analysis."
+    },
+    "V-222463": {
+        "title": "The application must generate audit records for privileged activities or other system-level access.",
+        "description": "Privileged activities include the tasks or actions taken by users in an administrative role (admin, backup operator, manager, etc.) which are used to manage or reconfigure application function...."
+    },
+    "V-222461": {
+        "title": "The application must generate audit records when successful/unsuccessful attempts to delete categories of information (e.g., classification levels) occur.",
+        "description": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an..."
+    },
+    "V-222460": {
+        "title": "The application must generate audit records when successful/unsuccessful attempts to delete application database security objects occur.",
+        "description": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an..."
+    },
+    "V-222500": {
+        "title": "The application must protect audit information from any type of unauthorized read access.",
+        "description": "If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult if not impossible to achieve. In..."
+    },
+    "V-222501": {
+        "title": "The application must protect audit information from unauthorized modification.",
+        "description": "If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of..."
+    },
+    "V-222502": {
+        "title": "The application must protect audit information from unauthorized deletion.",
+        "description": "If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of..."
+    },
+    "V-222503": {
+        "title": "The application must protect audit tools from unauthorized access.",
+        "description": "Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on..."
+    },
+    "V-222504": {
+        "title": "The application must protect audit tools from unauthorized modification.",
+        "description": "Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on..."
+    },
+    "V-222505": {
+        "title": "The application must protect audit tools from unauthorized deletion.",
+        "description": "Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on..."
+    },
+    "V-222506": {
+        "title": "The application must back up audit records at least every seven days onto a different system or system component than the system or component being audited.",
+        "description": "Protection of log data includes assuring log data is not accidentally lost or deleted. Backing up audit records to a different system or onto separate media than the system being audited on an..."
+    },
+    "V-222507": {
+        "title": "The application must use cryptographic mechanisms to protect the integrity of audit information.",
+        "description": "Audit records may be tampered with; if the integrity of audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is..."
+    },
+    "V-222636": {
+        "title": "A disaster recovery/continuity plan must exist in accordance with DoD policy based on the applications availability requirements.",
+        "description": "All applications must document disaster recovery/continuity procedures to include business recovery plans, system contingency plans, facility disaster recovery plans, and plan acceptance."
+    },
+    "V-222509": {
+        "title": "The integrity of the audit tools must be validated by checking the files for changes in the cryptographic hash value.",
+        "description": "Protecting the integrity of the tools used for auditing purposes is a critical step to ensuring the integrity of audit data. Audit data includes all information (e.g., audit records, audit..."
+    },
+    "V-222634": {
+        "title": "The application services and interfaces must be compatible with and ready for IPv6 networks.",
+        "description": "If the application has not been upgraded to execute on an IPv6-only network, there is a possibility the application will not execute properly, and as a result, a denial of service could occur. In..."
+    },
+    "V-222635": {
+        "title": "The application must not be hosted on a general purpose machine if the application is designated as critical or high availability by the ISSO.",
+        "description": "Critical applications should not be hosted on a multi-purpose server with other applications. Applications that share resources are susceptible to the other shared application security defects...."
+    },
+    "V-222632": {
+        "title": "A Software Configuration Management (SCM) plan describing the configuration control and change management process of application objects developed by the organization and the roles and responsibilities of the organization must be created and maintained.",
+        "description": "Software Configuration Management (SCM) is very important in tracking code releases, baselines, and managing access to the configuration management repository. The SCM plan identifies what should..."
+    },
+    "V-222633": {
+        "title": "A Configuration Control Board (CCB) that meets at least every release cycle, for managing the Configuration Management (CM) process must be established.",
+        "description": "Software Configuration Management (SCM) is very important in tracking code releases, baselines, and managing access to the configuration management repository. An SCM plan or charter identifies..."
+    },
+    "V-222630": {
+        "title": "The Configuration Management (CM) repository must be properly patched and STIG compliant.",
+        "description": "A Configuration Management (CM) repository is used to manage application code versions and to securely store application code. Failure to properly apply security patches and secure the software..."
+    },
+    "V-222631": {
+        "title": "Access privileges to the Configuration Management (CM) repository must be reviewed every three months.",
+        "description": "A Configuration Management (CM) repository is used to manage application code versions and to securely store application code. Incorrect access privileges to the CM repository can lead to..."
+    },
+    "V-222588": {
+        "title": "The application must implement approved cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest on organization-defined information system components.",
+        "description": "Applications handling data requiring \"data at rest\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. Selection of a..."
+    },
+    "V-222589": {
+        "title": "The application must use appropriate cryptography in order to protect stored DoD information when required by the information owner or DoD policy.",
+        "description": "Applications handling data requiring \"data at rest\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. Selection of a..."
+    },
+    "V-222556": {
+        "title": "The application must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).",
+        "description": "Lack of authentication and identification enables non-organizational users to gain access to the application or possibly other information systems and provides an opportunity for intruders to..."
+    },
+    "V-222580": {
+        "title": "Applications must validate session identifiers.",
+        "description": "Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever possible it is recommended to utilize the provided session management framework."
+    },
+    "V-222581": {
+        "title": "Applications must not use URL embedded session IDs.",
+        "description": "Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever possible it is recommended to utilize the provided session management..."
+    },
+    "V-222582": {
+        "title": "The application must not re-use or recycle session IDs.",
+        "description": "Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever possible it is recommended to utilize the provided session management..."
+    },
+    "V-222583": {
+        "title": "The application must use the Federal Information Processing Standard (FIPS) 140-2-validated cryptographic modules and random number generator if the application implements encryption, key exchange, digital signature, and hash functionality.",
+        "description": "Sequentially generated session IDs can be easily guessed by an attacker. Employing the concept of randomness in the generation of unique session identifiers helps to protect against brute-force..."
+    },
+    "V-222584": {
+        "title": "The application must only allow the use of DoD-approved certificate authorities for verification of the establishment of protected sessions.",
+        "description": "Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DoD systems or by organizations with insufficient..."
+    },
+    "V-222586": {
+        "title": "In the event of a system failure, applications must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.",
+        "description": "Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality,..."
+    },
+    "V-222587": {
+        "title": "The application must protect the confidentiality and integrity of stored information when required by DoD policy or the information owner.",
+        "description": "Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive) within an organizational information system. Mobile..."
+    },
+    "V-222526": {
+        "title": "The application must use multifactor (e.g., CAC, Alt. Token) authentication for network access to non-privileged accounts.",
+        "description": "To assure accountability and prevent unauthenticated access, non-privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system. Multifactor..."
+    },
+    "V-222390": {
+        "title": "The application must automatically terminate the admin user session and log off admin users after a 10 minute idle time period is exceeded.",
+        "description": "Leaving an admin user's application session established for an indefinite period of time increases the risk of session hijacking. Session termination terminates an individual user's logical..."
+    },
+    "V-222524": {
+        "title": "The application must accept Personal Identity Verification (PIV) credentials.",
+        "description": "The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DoD has mandated the use of the CAC to support identity management and personal authentication..."
+    },
+    "V-222452": {
+        "title": "The application must generate audit records when successful/unsuccessful attempts to access security levels occur.",
+        "description": "A security level denotes a permissions or authorization capability within the application. This is most often associated with a user role. Attempts to access a security level can occur when a user..."
+    },
+    "V-222453": {
+        "title": "The application must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur.",
+        "description": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an..."
+    },
+    "V-222450": {
+        "title": "The application must generate audit records when successful/unsuccessful attempts to grant privileges occur.",
+        "description": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an..."
+    },
+    "V-222657": {
+        "title": "The application development team must provide an application incident response plan.",
+        "description": "An application incident response process is managed by the development team and should include a method for individuals to submit potential security vulnerabilities to the development or..."
+    },
+    "V-222456": {
+        "title": "The application must generate audit records when successful/unsuccessful attempts to modify security levels occur.",
+        "description": "A security level denotes a permissions or authorization capability within the application. This is most often associated with a user role. Attempts to modify a security level can be construed as..."
+    },
+    "V-222457": {
+        "title": "The application must generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur.",
+        "description": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an..."
+    },
+    "V-222454": {
+        "title": "The application must generate audit records when successful/unsuccessful attempts to modify privileges occur.",
+        "description": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an..."
+    },
+    "V-222455": {
+        "title": "The application must generate audit records when successful/unsuccessful attempts to modify security objects occur.",
+        "description": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an..."
+    },
+    "V-222458": {
+        "title": "The application must generate audit records when successful/unsuccessful attempts to delete privileges occur.",
+        "description": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an..."
+    },
+    "V-222459": {
+        "title": "The application must generate audit records when successful/unsuccessful attempts to delete security levels occur.",
+        "description": "A security level denotes a permissions or authorization capability within the application. This is most often associated with a user role. Attempts to delete a security level can be construed as..."
+    },
+    "V-222393": {
+        "title": "The application must associate organization-defined types of security attributes having organization-defined security attribute values with information in storage.",
+        "description": "Without the association of security attributes to information, there is no basis for the application to make security related access-control decisions. Security attributes are abstractions..."
+    },
+    "V-222651": {
+        "title": "The changes to the application must be assessed for IA and accreditation impact prior to implementation.",
+        "description": "When changes are made to an application, either in the code or in the configuration of underlying components such as the OS or the web or application server, there is the potential for security..."
+    },
+    "V-222513": {
+        "title": "The application must have the capability to prevent the installation of patches, service packs, or application components without verification the software component has been digitally signed using a certificate that is recognized and approved by the organization.",
+        "description": "Changes to any software components can have significant effects on the overall security of the application. Verifying software components have been digitally signed using a certificate that is..."
+    },
+    "V-222512": {
+        "title": "The application must audit who makes configuration changes to the application.",
+        "description": "Without auditing the enforcement of access restrictions against changes to the application configuration, it will be difficult to identify attempted attacks and an audit trail will not be..."
+    },
+    "V-222511": {
+        "title": "The application must enforce access restrictions associated with changes to application configuration.",
+        "description": "Failure to provide logical access restrictions associated with changes to application configuration may have significant effects on the overall security of the system. When dealing with access..."
+    },
+    "V-222510": {
+        "title": "The application must prohibit user installation of software without explicit privileged status.",
+        "description": "Allowing regular users to install software, without explicit privileges, creates the risk that untested or potentially malicious software will be installed on the system. Explicit privileges..."
+    },
+    "V-222517": {
+        "title": "The application must employ a deny-all, permit-by-exception (whitelist) policy to allow the execution of authorized software programs.",
+        "description": "Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of..."
+    },
+    "V-222516": {
+        "title": "The application must prevent program execution in accordance with organization-defined policies regarding software program usage and restrictions, and/or rules authorizing the terms and conditions of software program usage.",
+        "description": "Control of application execution is a mechanism used to prevent execution of unauthorized applications in order to follow the rules of least privilege. Some applications may provide a capability..."
+    },
+    "V-222388": {
+        "title": "The application must clear temporary storage and cookies when the session is terminated.",
+        "description": "Persistent cookies are a primary means by which a web application will store application state and user information. Since HTTP is a stateless protocol, this persistence allows the web..."
+    },
+    "V-222389": {
+        "title": "The application must automatically terminate the non-privileged user session and log off non-privileged users after a 15 minute idle time period has elapsed.",
+        "description": "Leaving a user’s application session established for an indefinite period of time increases the risk of session hijacking. Session termination terminates an individual user's logical application..."
+    },
+    "V-222629": {
+        "title": "The application must be registered with the DoD Ports and Protocols Database.",
+        "description": "Failure to register the applications usage of ports, protocols, and services with the DoD PPS Database may result in a Denial of Service (DoS) because of enclave boundary protections at other end..."
+    },
+    "V-222387": {
+        "title": "The application must provide a capability to limit the number of logon sessions per user.",
+        "description": "Application management includes the ability to control the number of users and user sessions that utilize an application. Limiting the number of allowed users and sessions per user is helpful in..."
+    },
+    "V-222519": {
+        "title": "The application must be configured to use only functions, ports, and protocols permitted to it in the PPSM CAL.",
+        "description": "In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must..."
+    },
+    "V-222518": {
+        "title": "The application must be configured to disable non-essential capabilities.",
+        "description": "It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked..."
+    },
+    "V-222599": {
+        "title": "The application must maintain the confidentiality and integrity of information during reception.",
+        "description": "Data is subject to manipulation and other integrity related attacks whenever that data is transferred across a network. To protect data integrity during transmission, the application must..."
+    },
+    "V-222451": {
+        "title": "The application must generate audit records when successful/unsuccessful attempts to access security objects occur.",
+        "description": "Security objects represent application objects that provide or require security protections or have a security role within the application. Examples include but are not limited to, files,..."
+    },
+    "V-222611": {
+        "title": "The application must reveal error messages only to the ISSO, ISSM, or SA.",
+        "description": "Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify application components...."
+    },
+    "V-222593": {
+        "title": "XML-based applications must mitigate DoS attacks by using XML filters, parser options, or gateways.",
+        "description": "DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. XML-based..."
+    },
+    "V-222592": {
+        "title": "Applications must prevent unauthorized and unintended information transfer via shared system resources.",
+        "description": "Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of..."
+    },
+    "V-222591": {
+        "title": "The application must maintain a separate execution domain for each executing process.",
+        "description": "Applications can maintain separate execution domains for each executing process by assigning each process a separate address space. Each process has a distinct address space so that communication..."
+    },
+    "V-222590": {
+        "title": "The application must isolate security functions from non-security functions.",
+        "description": "An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions. Security functions are the hardware, software,..."
+    },
+    "V-222597": {
+        "title": "The application must implement cryptographic mechanisms to prevent unauthorized disclosure of information and/or detect changes to information during transmission unless otherwise protected by alternative physical safeguards, such as, at a minimum, a Protected Distribution System (PDS).",
+        "description": "Data is subject to manipulation and other integrity related attacks whenever that data is transferred across a network. To protect data integrity during transmission, the application must..."
+    },
+    "V-222595": {
+        "title": "The web service design must include redundancy mechanisms when used with high-availability systems.",
+        "description": "DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. In the case..."
+    },
+    "V-222594": {
+        "title": "The application must restrict the ability to launch Denial of Service (DoS) attacks against itself or other information systems.",
+        "description": "Denial of Service (DoS) is a condition where a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded..."
+    },
+    "V-222515": {
+        "title": "An application vulnerability assessment must be conducted.",
+        "description": "An application vulnerability assessment is a test conducted in order to identify weaknesses and security vulnerabilities that may exist within an application. The testing must cover all aspects..."
+    },
+    "V-222621": {
+        "title": "The ISSO must ensure application audit trails are retained for at least 1 year for applications without SAMI data, and 5 years for applications including SAMI data.",
+        "description": "Log files are a requirement to trace intruder activity or to audit user activity."
+    },
+    "V-222445": {
+        "title": "The application must provide audit record generation capability for session timeouts.",
+        "description": "When a user's session times out, it is important to be able to identify these events in the application logs. Without the capability to generate audit records, it would be difficult to establish,..."
+    },
+    "V-222444": {
+        "title": "The application must not write sensitive data into the application logs.",
+        "description": "It is important to identify and exclude certain types of data that is written into the logs. If the logs are compromised and sensitive data is included in the logs, this could assist an attacker..."
+    },
+    "V-222447": {
+        "title": "The application must provide audit record generation capability for HTTP headers including User-Agent, Referer, GET, and POST.",
+        "description": "HTTP header information is a critical component of data that is used when evaluating forensic activity. Without the capability to generate audit records, it would be difficult to establish,..."
+    },
+    "V-222446": {
+        "title": "The application must record a time stamp indicating when the event occurred.",
+        "description": "It is important to include the time stamps for when an event occurred. Failure to include time stamps in the event logs is detrimental to forensic analysis."
+    },
+    "V-222441": {
+        "title": "The application must provide audit record generation capability for the creation of session IDs.",
+        "description": "Applications create session IDs at the onset of a user session in order to manage user access to the application and differentiate between different user sessions. It is important to log the..."
+    },
+    "V-222394": {
+        "title": "The application must associate organization-defined types of security attributes having organization-defined security attribute values with information in process.",
+        "description": "Without the association of security attributes to information, there is no basis for the application to make security related access-control decisions. Security attributes are abstractions..."
+    },
+    "V-222443": {
+        "title": "The application must provide audit record generation capability for the renewal of session IDs.",
+        "description": "Application design sometimes requires the renewal of session IDs in order to continue approved user access to the application. Session renewal is done on a case by case basis under circumstances..."
+    },
+    "V-222442": {
+        "title": "The application must provide audit record generation capability for the destruction of session IDs.",
+        "description": "Applications should destroy session IDs at the end of a user session in order to terminate user access to the application session and to reduce the possibility of an unauthorized attacker high..."
+    },
+    "V-222449": {
+        "title": "The application must record the username or user ID of the user associated with the event.",
+        "description": "When users conduct activity within an application, that user’s identity must be recorded in the audit log. Failing to record the identity of the user responsible for the activity within the..."
+    },
+    "V-222448": {
+        "title": "The application must provide audit record generation capability for connecting system IP addresses.",
+        "description": "Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit..."
+    },
+    "V-222527": {
+        "title": "The application must use multifactor (Alt. Token) authentication for local access to privileged accounts.",
+        "description": "Multifactor authentication requires using two or more factors to achieve authentication and access. Factors include: (i) something a user knows (e.g., password/PIN); (ii) something a user has..."
+    },
+    "V-222656": {
+        "title": "The application must not be subject to error handling vulnerabilities.",
+        "description": "Error handling is the failure to check the return values of functions or catch top level exceptions within a program. Improper error handling in an application can lead to an application failure..."
+    },
+    "V-222525": {
+        "title": "The application must electronically verify Personal Identity Verification (PIV) credentials.",
+        "description": "The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DoD has mandated the use of the CAC to support identity management and personal authentication..."
+    },
+    "V-222650": {
+        "title": "Flaws found during a code review must be tracked in a defect tracking system.",
+        "description": "This requirement is meant to apply to developers or organizations that are doing application development work. If flaws are not tracked they may possibly be forgotten to be included in a release...."
+    },
+    "V-222523": {
+        "title": "The application must use multifactor (Alt. Token) authentication for network access to privileged accounts.",
+        "description": "Multifactor authentication requires using two or more factors to achieve authentication and access. Factors include: (i) something a user knows (e.g., password/PIN); (ii) something a user has..."
+    },
+    "V-222652": {
+        "title": "Security flaws must be fixed or addressed in the project plan.",
+        "description": "This requirement is meant to apply to developers or organizations that are doing application development work. Application development efforts include the creation of a project plan to track and..."
+    },
+    "V-222521": {
+        "title": "The application must require devices to reauthenticate when organization-defined circumstances or situations requiring reauthentication.",
+        "description": "Without reauthenticating devices, unidentified or unknown devices may be introduced; thereby facilitating malicious activity. In addition to the reauthentication requirements associated with..."
+    },
+    "V-222398": {
+        "title": "Applications with SOAP messages requiring integrity must include the following message elements:-Message ID-Service Request-Timestamp-SAML Assertion (optionally included in messages) and all elements of the message must be digitally signed.",
+        "description": "Digitally signed SOAP messages provide message integrity and authenticity of the signer of the message independent of the transport layer. Service requests may be intercepted and changed in..."
+    },
+    "V-222552": {
+        "title": "The application must map the authenticated identity to the individual user or group account for PKI-based authentication.",
+        "description": "Without mapping the certificate used to authenticate to a corresponding user account, the ability to determine the identity of the individual user or group will not be available for forensic..."
+    },
+    "V-222528": {
+        "title": "The application must use multifactor (e.g., CAC, Alt. Token) authentication for local access to non-privileged accounts.",
+        "description": "To assure accountability, prevent unauthenticated access, and prevent misuse of the system, privileged users must utilize multifactor authentication for local access. Multifactor authentication..."
+    },
+    "V-222529": {
+        "title": "The application must ensure users are authenticated with an individual authenticator prior to using a group authenticator.",
+        "description": "To assure individual accountability and prevent unauthorized access, application users must be individually identified and authenticated. Individual accountability mandates that each user is..."
+    },
+    "V-222397": {
+        "title": "The application must implement cryptographic mechanisms to protect the integrity of remote access sessions.",
+        "description": "Without integrity protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. Remote access is access to DoD nonpublic information..."
+    },
+    "V-222433": {
+        "title": "The application administrator must follow an approved process to unlock locked user accounts.",
+        "description": "Once a user account has been locked, it must be unlocked by an administrator. An ISSM and ISSO approved process must be created and followed to ensure the user requesting access is properly..."
+    },
+    "V-222623": {
+        "title": "The ISSO must report all suspected violations of IA policies in accordance with DoD information system IA procedures.",
+        "description": "Violations of IA policies must be reviewed and reported. If there are no policies regarding the reporting of IA violations, IA violations may not be tracked or addressed in a proper manner."
+    },
+    "V-222539": {
+        "title": "The application must enforce password complexity by requiring that at least one numeric character be used.",
+        "description": "Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations..."
+    },
+    "V-222396": {
+        "title": "The application must implement DoD-approved encryption to protect the confidentiality of remote access sessions.",
+        "description": "Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. Remote access is access to DoD nonpublic information..."
+    },
+    "V-222622": {
+        "title": "The ISSO must review audit trails periodically based on system documentation recommendations or immediately upon system security events.",
+        "description": "Without access control the data is not secure. It can be compromised, misused, or changed by unauthorized access at any time."
+    },
+    "V-222531": {
+        "title": "The application must implement replay-resistant authentication mechanisms for network access to non-privileged accounts.",
+        "description": "A replay attack is a man-in-the-middle style attack which allows an attacker to repeat or alter a valid data transmission that may enable unauthorized access to the application. Authentication..."
+    },
+    "V-222625": {
+        "title": "Execution flow diagrams and design documents must be created to show how deadlock and recursion issues in web services are being mitigated.",
+        "description": "In order to understand data flows within web services, the process flow of data must be developed and documented. There are several different ways that web service deadlock occurs, many times it..."
+    },
+    "V-222533": {
+        "title": "The application must authenticate all network connected endpoint devices before establishing any connection.",
+        "description": "Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. For distributed architectures (e.g., service-oriented architectures),..."
+    },
+    "V-222532": {
+        "title": "The application must utilize mutual authentication when endpoint device non-repudiation protections are required by DoD policy or by the data owner.",
+        "description": "Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. With one way SSL authentication which is the typical form of SSL..."
+    },
+    "V-222535": {
+        "title": "The application must disable device identifiers after 35 days of inactivity unless a cryptographic certificate is used for authentication.",
+        "description": "Device identifiers are used to identify hardware devices that interact with the application much like a user account is used to identify an application user. Examples of hardware devices include..."
+    },
+    "V-222534": {
+        "title": "Service-Oriented Applications handling non-releasable data must authenticate endpoint devices via mutual SSL/TLS.",
+        "description": "Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. One way SSL/TLS authentication is the typical form of authentication done..."
+    },
+    "V-222537": {
+        "title": "The application must enforce password complexity by requiring that at least one upper-case character be used.",
+        "description": "Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations..."
+    },
+    "V-222646": {
+        "title": "At least one tester must be designated to test for security flaws in addition to functional testing.",
+        "description": "If there is no person designated to test for security flaws, vulnerabilities can potentially be missed during testing. This requirement is meant to apply to developers or organizations that are..."
+    },
+    "V-222645": {
+        "title": "Application files must be cryptographically hashed prior to deploying to DoD operational networks.",
+        "description": "When application code and binaries are transferred from one environment to another, there is the potential for malware to be introduced into either the application code or even the application..."
+    },
+    "V-222641": {
+        "title": "The application must use encryption to implement key exchange and authenticate endpoints prior to establishing a communication channel for key exchange.",
+        "description": "If the application does not use encryption and authenticate endpoints prior to establishing a communication channel and prior to transmitting encryption keys, these keys may be intercepted, and..."
+    },
+    "V-222438": {
+        "title": "The application must protect against an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by non-repudiation.",
+        "description": "Without non-repudiation, it is impossible to positively attribute an action to an individual (or process acting on behalf of an individual). Non-repudiation services can be used to determine if..."
+    },
+    "V-222439": {
+        "title": "For applications providing audit record aggregation, the application must compile audit records from organization-defined information system components into a system-wide audit trail that is time-correlated with an organization-defined level of tolerance for the relationship between time stamps of individual records in the audit trail.",
+        "description": "Without the ability to collate records based on the time when the events occurred, the ability to perform forensic analysis and investigations across multiple components is significantly..."
+    },
+    "V-222514": {
+        "title": "The applications must limit privileges to change the software resident within software libraries.",
+        "description": "If the application were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a..."
+    },
+    "V-222553": {
+        "title": "The application, for PKI-based authentication, must implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network.",
+        "description": "A local cache of revocation data is also known as a CRL list. This list contains a list of revoked certificates and can be periodically downloaded to ensure certificates can still be checked for..."
+    },
+    "V-222648": {
+        "title": "An application code review must be performed on the application.",
+        "description": "A code review is a systematic evaluation of computer source code conducted for the purposes of identifying and remediating the security flaws in the software. This requirement is meant to apply..."
+    },
+    "V-222628": {
+        "title": "New IP addresses, data services, and associated ports used by the application must be submitted to the appropriate approving authority for the organization, which in turn will be submitted through the DoD Ports, Protocols, and Services Management (DoD PPSM)",
+        "description": "Failure to comply with DoD Ports, Protocols, and Services (PPS) Vulnerability Analysis and associated PPS mitigations may result in compromise of enclave boundary protections and/or functionality..."
+    },
+    "V-222640": {
+        "title": "Procedures must be in place to assure the appropriate physical and technical protection of the backup and restoration of the application.",
+        "description": "Protection of backup and restoration assets is essential for the successful restore of operations after a catastrophic failure or damage to the system or data files. Failure to follow proper..."
+    },
+    "V-222626": {
+        "title": "The designer must ensure the application does not store configuration and control files in the same directory as user data.",
+        "description": "Application configuration settings and user data are required to be stored in separate locations in order to prevent application users from possibly being able to access application configuration..."
+    },
+    "V-222520": {
+        "title": "The application must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.",
+        "description": "Without reauthentication, users may access resources or perform tasks for which they do not have authorization. When applications provide the capability to change security roles or escalate the..."
+    },
+    "V-222530": {
+        "title": "The application must implement replay-resistant authentication mechanisms for network access to privileged accounts.",
+        "description": "A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be..."
+    },
+    "V-222627": {
+        "title": "The ISSO must ensure if a DoD STIG or NSA guide is not available, a third-party product will be configured by following available guidance.",
+        "description": "Not all COTS products are covered by a STIG. Those products not covered by a STIG, should follow commercially accepted best practices, independent testing results and vendors lock down guides and..."
+    },
+    "V-222548": {
+        "title": "The application password must not be changeable by users other than the administrator or the user with which the password is associated.",
+        "description": "If the application allows user A to change user B's password, user B can be locked out of the application, and user A is provided the ability to grant themselves access to the application as user..."
+    },
+    "V-222549": {
+        "title": "The application must terminate existing user sessions upon account deletion.",
+        "description": "The application must ensure that a user does not retain any rights that may have been granted or retain access to the application after the user's authorization or role within the application has..."
+    },
+    "V-222545": {
+        "title": "The application must enforce a 60-day maximum password lifetime restriction.",
+        "description": "Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations..."
+    },
+    "V-222544": {
+        "title": "The application must enforce 24 hours/1 day as the minimum password lifetime.",
+        "description": "Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations..."
+    },
+    "V-222673": {
+        "title": "The Program Manager must verify all levels of program management, designers, developers, and testers receive annual security training pertaining to their job function.",
+        "description": "Many application team members may not be aware of the security implications regarding the code that they design, write and test. To address this concern, the Program Manager will ensure all..."
+    },
+    "V-222671": {
+        "title": "Connections between the DoD enclave and the Internet or other public or commercial wide area networks must require a DMZ.",
+        "description": "In order to protect DoD data and systems, all remote access to DoD information systems must be mediated through a managed access control point, such as a remote access server in a DMZ."
+    },
+    "V-222540": {
+        "title": "The application must enforce password complexity by requiring that at least one special character be used.",
+        "description": "Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations..."
+    },
+    "V-222546": {
+        "title": "The application must prohibit password reuse for a minimum of five generations.",
+        "description": "Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations..."
+    },
+    "V-222423": {
+        "title": "Application data protection requirements must be identified and documented.",
+        "description": "Failure to protect organizational information from data mining may result in a compromise of information. In order to assign the appropriate data protections, application data must be identified..."
+    },
+    "V-222421": {
+        "title": "The application must automatically audit account enabling actions.",
+        "description": "When application accounts are enabled, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves...."
+    },
+    "V-222547": {
+        "title": "The application must allow the use of a temporary password for system logons with an immediate change to a permanent password.",
+        "description": "Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations..."
+    },
+    "V-222427": {
+        "title": "The application must enforce approved authorizations for controlling the flow of information within the system based on organization-defined information flow control policies.",
+        "description": "A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If information flow is not enforced based on approved authorizations,..."
+    },
+    "V-222426": {
+        "title": "The application must enforce organization-defined discretionary access control policies over defined subjects and objects.",
+        "description": "Discretionary Access Control allows users to determine who is allowed to access their data. To mitigate the risk of unauthorized access to sensitive information by entities that have been issued..."
+    },
+    "V-222424": {
+        "title": "The application must utilize organization-defined data mining detection techniques for organization-defined data storage objects to adequately detect data mining attempts.",
+        "description": "Failure to protect organizational information from data mining may result in a compromise of information. Data mining occurs when the application is programmatically probed and data is..."
+    },
+    "V-222429": {
+        "title": "The application must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.",
+        "description": "Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or..."
+    },
+    "V-222428": {
+        "title": "The application must enforce approved authorizations for controlling the flow of information between interconnected systems based on organization-defined information flow control policies.",
+        "description": "A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If information flow is not enforced based on approved authorizations,..."
+    },
+    "V-222462": {
+        "title": "The application must generate audit records when successful/unsuccessful logon attempts occur.",
+        "description": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an..."
+    },
+    "V-222598": {
+        "title": "The application must maintain the confidentiality and integrity of information during preparation for transmission.",
+        "description": "Data is subject to manipulation and other integrity related attacks whenever that data is transferred across a network. To protect data integrity during transmission, the application must..."
+    },
+    "V-254803": {
+        "title": "The application must implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.",
+        "description": "Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect classified data. The application must implement cryptographic modules adhering to the..."
+    },
+    "V-222499": {
+        "title": "The application must record time stamps for audit records that meet a granularity of one second for a minimum degree of precision.",
+        "description": "Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. Time stamps generated by the application include date and time...."
+    },
+    "V-222668": {
+        "title": "The system must alert an administrator when low resource conditions are encountered.",
+        "description": "In order to prevent DoS type attacks, applications should be monitored when resource conditions reach a predefined threshold. This could indicate the onset of a DoS attack or could be the..."
+    },
+    "V-222559": {
+        "title": "The application must accept FICAM-approved third-party credentials.",
+        "description": "FICAM establishes a federated identity framework for the Federal Government. FICAM provides Government-wide services for common Identity, Credential and Access Management (ICAM) requirements. The..."
+    },
+    "V-222558": {
+        "title": "The application must electronically verify Personal Identity Verification (PIV) credentials from other federal agencies.",
+        "description": "Inappropriate access may be granted to unauthorized users if federal agency PIV credentials are not electronically verified. Personal Identity Verification (PIV) credentials are those credentials..."
+    },
+    "V-222665": {
+        "title": "The designer must ensure uncategorized or emerging mobile code is not used in applications.",
+        "description": "By definition, mobile code is software obtained from remote systems outside the enclave boundary, transferred across a network, and then downloaded and executed on a local system without explicit..."
+    },
+    "V-222664": {
+        "title": "If the application contains classified data, a Security Classification Guide must exist containing data elements and their classification.",
+        "description": "Without a classification guide the marking, storage, and output media of classified material can be inadvertently mixed with unclassified material, leading to its possible loss or compromise."
+    },
+    "V-222667": {
+        "title": "Protections against DoS attacks must be implemented.",
+        "description": "Known DoS threats documented in the threat model should be mitigated, to prevent DoS type attacks."
+    },
+    "V-222666": {
+        "title": "Production database exports must have database administration credentials and sensitive data removed before releasing the export.",
+        "description": "Production database exports are often used to populate development databases. Test and development environments do not typically have the same rigid security protections that production..."
+    },
+    "V-222661": {
+        "title": "Unnecessary built-in application accounts must be disabled.",
+        "description": "Default passwords and properties of built-in accounts are often publicly available. Anyone with necessary knowledge, internal or external, can compromise an application using built-in..."
+    },
+    "V-222663": {
+        "title": "An Application Configuration Guide must be created and included with the application.",
+        "description": "The Application Configuration Guide is any document or collection of documents used to configure the application. These documents may be part of a user guide, secure configuration guide, or any..."
+    },
+    "V-222416": {
+        "title": "The application must automatically audit account removal actions.",
+        "description": "When application accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves...."
+    },
+    "V-222414": {
+        "title": "The application must automatically audit account modification.",
+        "description": "One way for an attacker to establish persistent access is for the attacker to modify or copy an existing account. Auditing of account modification is one method for mitigating this risk. A..."
+    },
+    "V-222415": {
+        "title": "The application must automatically audit account disabling actions.",
+        "description": "When application accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves...."
+    },
+    "V-222412": {
+        "title": "Unnecessary application accounts must be disabled, or deleted.",
+        "description": "Test or demonstration accounts are sometimes created during the application installation process. This creates a security risk as these accounts often remain after the initial installation process..."
+    },
+    "V-222638": {
+        "title": "Data backup must be performed at required intervals in accordance with DoD policy.",
+        "description": "Without proper backups, the application is not protected from the loss of data or the operating environment in the event of hardware or software failure."
+    },
+    "V-222538": {
+        "title": "The application must enforce password complexity by requiring that at least one lower-case character be used.",
+        "description": "Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations..."
+    },
+    "V-222639": {
+        "title": "Back-up copies of the application software or source code must be stored in a fire-rated container or stored separately (offsite).",
+        "description": "Application developers and application administrators must take steps to ensure continuity of development effort and operations should a disaster strike. Steps include protecting back-up copies..."
+    },
+    "V-222508": {
+        "title": "Application audit tools must be cryptographically hashed.",
+        "description": "Protecting the integrity of the tools used for auditing purposes is a critical step to ensuring the integrity of audit data. Audit data includes all information (e.g., audit records, audit..."
+    },
+    "V-222498": {
+        "title": "The application must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).",
+        "description": "If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the application include date and time...."
+    },
+    "V-222637": {
+        "title": "Recovery procedures and technical system features must exist so recovery is performed in a secure and verifiable manner. The ISSO will document circumstances inhibiting a trusted recovery.",
+        "description": "Without a disaster recovery plan, the application is susceptible to interruption in service due to damage within the processing site. If the application is part of the site’s disaster recovery..."
+    },
+    "V-222496": {
+        "title": "The application must provide a report generation capability that does not alter original content or time ordering of audit records.",
+        "description": "If the audit report generation capability alters the original content or time ordering of audit records, the integrity of the audit records is compromised, and the records are no longer usable for..."
+    },
+    "V-222571": {
+        "title": "The application must utilize FIPS-validated cryptographic modules when generating cryptographic hashes.",
+        "description": "Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards..."
+    },
+    "V-222494": {
+        "title": "The application must provide a report generation capability that supports after-the-fact investigations of security incidents.",
+        "description": "If the report generation capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack, or..."
+    },
+    "V-222495": {
+        "title": "The application must provide an audit reduction capability that does not alter original content or time ordering of audit records.",
+        "description": "If the audit reduction capability alters the content or time ordering of audit records, the integrity of the audit records is compromised, and the records are no longer usable for forensic..."
+    },
+    "V-222492": {
+        "title": "The application must provide a report generation capability that supports on-demand audit review and analysis.",
+        "description": "The report generation capability must support on-demand review and analysis in order to facilitate the organization's ability to generate incident reports as needed to better handle larger-scale..."
+    },
+    "V-222493": {
+        "title": "The application must provide a report generation capability that supports on-demand reporting requirements.",
+        "description": "The report generation capability must support on-demand reporting in order to facilitate the organization's ability to generate incident reports as needed to better handle larger-scale or more..."
+    },
+    "V-222490": {
+        "title": "The application must provide an audit reduction capability that supports on-demand audit review and analysis.",
+        "description": "The ability to perform on-demand audit review and analysis, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate..."
+    },
+    "V-222479": {
+        "title": "The application must implement transaction recovery logs when transaction based.",
+        "description": "Without required logging and access control, security issues related to data changes will not be identified. This could lead to security compromises such as data misuse, unauthorized changes, or..."
+    },
+    "V-222434": {
+        "title": "The application must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the application.",
+        "description": "Display of the DoD-approved use notification before granting access to the application ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive..."
+    },
+    "V-222436": {
+        "title": "The publicly accessible application must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the application.",
+        "description": "Display of a standardized and approved use notification before granting access to the publicly accessible application ensures privacy and security notification verbiage used is consistent with..."
+    },
+    "V-222411": {
+        "title": "The application must automatically disable accounts after a 35 day period of account inactivity.",
+        "description": "Attackers that are able to exploit an inactive account can potentially obtain and maintain undetected access to an application. Owners of inactive accounts will not notice if unauthorized access..."
+    },
+    "V-222617": {
+        "title": "The application must notify the ISSO and ISSM of failed security verification tests.",
+        "description": "If personnel are not notified of failed security verification tests, they will not be able to take corrective action and the unsecure condition(s) will remain. Security function is defined as the..."
+    },
+    "V-222654": {
+        "title": "The designer must create and update the Design Document for each release of the application.",
+        "description": "This requirement is meant to apply to developers or organizations that are doing application development work. The application design document or configuration guide includes configuration..."
+    },
+    "V-222653": {
+        "title": "The application development team must follow a set of coding standards.",
+        "description": "Coding standards are guidelines established by the development team or individual developers that recommend programming style, practices and methods. The coding standards employed will vary based..."
+    },
+    "V-222647": {
+        "title": "Test procedures must be created and at least annually executed to ensure system initialization, shutdown, and aborts are configured to verify the system remains in a secure state.",
+        "description": "Secure state assurance cannot be accomplished without testing the system state at least annually to ensure the system remains in a secure state upon initialization, shutdown, and aborts."
+    },
+    "V-222644": {
+        "title": "Prior to each release of the application, updates to system, or applying patches; tests plans and procedures must be created and executed.",
+        "description": "Without test plans and procedures for application releases or updates, unexpected results may occur which could lead to a denial of service to the application or components. This requirement is..."
+    },
+    "V-222435": {
+        "title": "The application must retain the Standard Mandatory DoD Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access.",
+        "description": "The banner must be acknowledged by the user prior to allowing the user access to the application. This provides assurance that the user has seen the message and accepted the conditions for access...."
+    },
+    "V-222437": {
+        "title": "The application must display the time and date of the users last successful logon.",
+        "description": "Providing a last successful logon date and time stamp notification to the user when they authenticate and access the application allows the user to determine if their application account has been..."
+    },
+    "V-222649": {
+        "title": "Code coverage statistics must be maintained for each release of the application.",
+        "description": "This requirement is meant to apply to developers or organizations that are doing application development work. Code coverage statistics describes the overall functionality provided by the..."
+    },
+    "V-222392": {
+        "title": "The application must display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions.",
+        "description": "If a user is not explicitly notified that their application session has been terminated, they cannot be certain that their session did not remain open. Applications with a user access interface..."
+    },
+    "V-222670": {
+        "title": "The application must provide notifications or alerts when product update and security related patches are available.",
+        "description": "An application vulnerability management and update process must be in place to notify and provide users and administrators with a means of obtaining security patches and updates for the..."
+    },
+    "V-222422": {
+        "title": "The application must notify System Administrators and Information System Security Officers of account enabling actions.",
+        "description": "Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply..."
+    },
+    "V-222672": {
+        "title": "The application must generate audit records when concurrent logons from different workstations occur.",
+        "description": "When an application provides users with the ability to concurrently logon, an event must be recorded that indicates the user has logged on from different workstations. It is important to ensure..."
+    },
+    "V-222420": {
+        "title": "The application must notify System Administrators and Information System Security Officers of account removal actions.",
+        "description": "Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply..."
+    },
+    "V-222669": {
+        "title": "At least one application administrator must be registered to receive update notifications, or security alerts, when automated alerts are available.",
+        "description": "Administrators should register for updates to all COTS and custom-developed software, so when security flaws are identified, they can be tracked for testing and updates of the application can be..."
+    },
+    "V-222660": {
+        "title": "Procedures must be in place to notify users when an application is decommissioned.",
+        "description": "When maintenance no longer exists for an application, there are no individuals responsible for making security updates. The application support staff should maintain procedures for..."
+    },
+    "V-222417": {
+        "title": "The application must notify System Administrators and Information System Security Officers when accounts are created.",
+        "description": "Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply..."
+    },
+    "V-222410": {
+        "title": "The application must have a process, feature or function that prevents removal or disabling of emergency accounts.",
+        "description": "Emergency accounts are administrator accounts which are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account..."
+    },
+    "V-222418": {
+        "title": "The application must notify System Administrators and Information System Security Officers when accounts are modified.",
+        "description": "Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply..."
+    },
+    "V-222419": {
+        "title": "The application must notify System Administrators and Information System Security Officers of account disabling actions.",
+        "description": "Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply..."
+    }
+  },
+  "casa": {
+    "1": {
+      "title": "Architecture, Design And Threat Modelling"
+    },
+    "2": {
+      "title": "Authentication"
+    },
+    "3": {
+      "title": "Session Management"
+    },
+    "4": {
+      "title": "Access Control"
+    },
+    "5": {
+      "title": "Malicious Input Handling"
+    },
+    "6": {
+      "title": "Cryptography At Rest"
+    },
+    "7": {
+      "title": "Error Handling And Logging"
+    },
+    "8": {
+      "title": "Data Protection"
+    },
+    "9": {
+      "title": "Communications Security"
+    },
+    "10": {
+      "title": "Malicious Controls"
+    },
+    "11": {
+      "title": "Business Logic"
+    },
+    "12": {
+      "title": "Files And Resources"
+    },
+    "13": {
+      "title": "Web Services"
+    },
+    "14": {
+      "title": "Configuration"
+    },
+    "1.1.1": {
+      "title": "Verify the use of a secure software development lifecycle that addresses security in all stages of development.",
+      "level": "2"
+    },
+    "1.1.2": {
+      "title": "Verify the use of threat modeling for every design change or sprint planning to identify threats, plan for countermeasures, facilitate appropriate risk responses, and guide security testing.",
+      "level": "2"
+    },
+    "1.1.3": {
+      "title": "Verify that all user stories and features contain functional security constraints, such as \"As a user,I should be able to view and edit my profile.I should not be able to view or edit anyone else 's profile\"",
+      "level": "2"
+    },
+    "1.1.4": {
+      "title": "Verify documentation and justification of all the application's trust boundaries, components, and significant data flows.",
+      "level": "2"
+    },
+    "1.1.5": {
+      "title": "Verify definition and security analysis of the application's high-level architecture and all connected remote services.",
+      "level": "2"
+    },
+    "1.1.6": {
+      "title": "Verify implementation of centralized, simple (economy of design), vetted, secure, and reusable security controls to avoid duplicate, missing, ineffective, or insecure controls.",
+      "level": "2"
+    },
+    "1.1.7": {
+      "title": "Verify availability of a secure coding checklist, security requirements, guideline, or policy to all developers and testers.",
+      "level": "2"
+    },
+    "1.10.1": {
+      "title": "Verify that a source code control system is in use, with procedures to ensure that check-ins are accompanied by issues or change tickets. The source code control system should have access control and identifiable users to allow traceability of any changes.",
+      "level": "2"
+    },
+    "1.11.1": {
+      "title": "Verify the definition and documentation of all application components in terms of the business or security functions they provide.",
+      "level": "2"
+    },
+    "1.11.2": {
+      "title": "Verify that all high-value business logic flows, including authentication, session management and access control, do not share unsynchronized state.",
+      "level": "2"
+    },
+    "1.11.3": {
+      "title": "Verify that all high-value business logic flows, including authentication, session management and access control are thread safe and resistant to time-of-check and time-of-use race conditions.",
+      "level": "3"
+    },
+    "1.12.1": {
+      "title": "Verify that user-uploaded files are stored outside of the web root.",
+      "level": "2"
+    },
+    "1.12.2": {
+      "title": "Verify that user-uploaded files - if required to be displayed or downloaded from the application - are served by either octet stream downloads, or from an unrelated domain, such as a cloud file storage bucket. Implement a suitable content security policy to reduce the risk from XSS vectors or other attacks from the uploaded file.",
+      "level": "2"
+    },
+    "1.14.1": {
+      "title": "Verify the segregation of components of differing trust levels through well-defined security controls, firewall rules, API gateways, reverse proxies, cloud-based security groups, or similar mechanisms.",
+      "level": "2"
+    },
+    "1.14.2": {
+      "title": "Verify that if deploying binaries to untrusted devices makes use of binary signatures, trusted connections, and verified endpoints.",
+      "level": "2"
+    },
+    "1.14.3": {
+      "title": "Verify that the build pipeline warns of out-of-date or insecure components and takes appropriate actions.",
+      "level": "2"
+    },
+    "1.14.4": {
+      "title": "Verify that the build pipeline contains a build step to automatically build and verify the secure deployment of the application, particularly if the application infrastructure is software defined, such as cloud environment build scripts.",
+      "level": "2"
+    },
+    "1.14.5": {
+      "title": "Verify that application deployments adequately sandbox, containerize and/or isolate at the network level to delay and deter attackers from attacking other applications, especially when they are performing sensitive or dangerous actions such as deserialization.",
+      "level": "2"
+    },
+    "1.14.6": {
+      "title": "Verify the application does not use unsupported, insecure, or deprecated client-side technologies such as NSAPI plugins, Flash, Shockwave, ActiveX, Silverlight, NACL, or client-side Java applets.",
+      "level": "2"
+    },
+    "1.2.1": {
+      "title": "Verify the use of unique or special low-privilege operating system accounts for all application components, services, and servers.",
+      "level": "2"
+    },
+    "1.2.2": {
+      "title": "Verify that communications between application components, including APIs, middleware and data layers, are authenticated. Components should have the least necessary privileges needed.",
+      "level": "2"
+    },
+    "1.2.3": {
+      "title": "Verify that the application uses a single vetted authentication mechanism that is known to be secure, can be extended to include strong authentication, and has sufficient logging and monitoring to detect account abuse or breaches.",
+      "level": "2"
+    },
+    "1.2.4": {
+      "title": "Verify that all authentication pathways and identity management APIs implement consistent authentication security control strength, such that there are no weaker alternatives per the risk of the application.",
+      "level": "2"
+    },
+    "1.4.1": {
+      "title": "Verify that trusted enforcement points such as at access control gateways, servers, and serverless functions enforce access controls. Never enforce access controls on the client.",
+      "level": "2"
+    },
+    "1.4.2": {
+      "title": "Verify that the chosen access control solution is flexible enough to meet the application's needs.",
+      "level": "2"
+    },
+    "1.4.3": {
+      "title": "Verify enforcement of the principle of least privilege in functions, data files, URLs, controllers, services, and other resources. This implies protection against spoofing and elevation of privilege.",
+      "level": "2"
+    },
+    "1.4.4": {
+      "title": "Verify the application uses a single and well-vetted access control mechanism for accessing protected data and resources. All requests must pass through this single mechanism to avoid copy and paste or insecure alternative paths.",
+      "level": "2"
+    },
+    "1.4.5": {
+      "title": "Verify that attribute or feature-based access control is used whereby the code checks the user's authorization for a feature/data item rather than just their role. Permissions should still be allocated using roles.",
+      "level": "2"
+    },
+    "1.5.1": {
+      "title": "Verify that input and output requirements clearly define how to handle and process data based on type, content, and applicable laws, regulations, and other policy compliance.",
+      "level": "2"
+    },
+    "1.5.2": {
+      "title": "Verify that serialization is not used when communicating with untrusted clients. If this is not possible, ensure that adequate integrity controls (and possibly encryption if sensitive data is sent) are enforced to prevent deserialization attacks including object injection.",
+      "level": "2"
+    },
+    "1.5.3": {
+      "title": "Verify that input validation is enforced on a trusted service layer.",
+      "level": "2"
+    },
+    "1.5.4": {
+      "title": "Verify that output encoding occurs close to or by the interpreter for which it is intended.",
+      "level": "2"
+    },
+    "1.6.1": {
+      "title": "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.",
+      "level": "2"
+    },
+    "1.6.2": {
+      "title": "Verify that consumers of cryptographic services protect key material and other secrets by using key vaults or API based alternatives.",
+      "level": "2"
+    },
+    "1.6.3": {
+      "title": "Verify that all keys and passwords are replaceable and are part of a well-defined process to re-encrypt sensitive data.",
+      "level": "2"
+    },
+    "1.6.4": {
+      "title": "Verify that symmetric keys, passwords, or API secrets generated by or shared with clients are used only in protecting low risk secrets, such as encrypting local storage, or temporary ephemeral uses such as parameter obfuscation. Sharing secrets with clients is clear-text equivalent and architecturally should be treated as such.",
+      "level": "2"
+    },
+    "1.7.1": {
+      "title": "Verify that a common logging format and approach is used across the system. ",
+      "level": "2"
+    },
+    "1.7.2": {
+      "title": "Verify that logs are securely transmitted to a preferably remote system for analysis, detection, alerting, and escalation.",
+      "level": "2"
+    },
+    "1.8.1": {
+      "title": "Verify that all sensitive data is identified and classified into protection levels.",
+      "level": "2"
+    },
+    "1.8.2": {
+      "title": "Verify that all protection levels have an associated set of protection requirements, such as encryption requirements, integrity requirements, retention, privacy and other confidentiality requirements, and that these are applied in the architecture.",
+      "level": "2"
+    },
+    "1.9.1": {
+      "title": "Verify the application encrypts communications between components, particularly when these components are in different containers, systems, sites, or cloud providers.",
+      "level": "2"
+    },
+    "1.9.2": {
+      "title": "Verify that application components verify the authenticity of each side in a communication link to prevent person-in-the-middle attacks. For example, application components should validate TLS certificates and chains.",
+      "level": "2"
+    },
+    "2.1.1": {
+      "title": "Verify that user set passwords are at least 12 characters in length.",
+      "level": "1"
+    },
+    "2.1.10": {
+      "title": "Verify that there are no periodic credential rotation or password history requirements.",
+      "level": "1"
+    },
+    "2.1.11": {
+      "title": "Verify that \"paste\" functionality, browser password helpers, and external password managers are permitted.",
+      "level": "1"
+    },
+    "2.1.12": {
+      "title": "Verify that the user can choose to either temporarily view the entire masked password, or temporarily view the last typed character of the password on platforms that do not have this as native functionality.",
+      "level": "1"
+    },
+    "2.1.2": {
+      "title": "Verify that passwords 64 characters or longer are permitted.",
+      "level": "1"
+    },
+    "2.1.3": {
+      "title": "Verify that passwords can contain spaces and truncation is not performed. Consecutive multiple spaces MAY optionally be coalesced.",
+      "level": "1"
+    },
+    "2.1.4": {
+      "title": "Verify that Unicode characters are permitted in passwords. A single Unicode code point is considered a character, so 12 emoji or 64 kanji characters should be valid and permitted.",
+      "level": "1"
+    },
+    "2.1.5": {
+      "title": "Verify users can change their password.",
+      "level": "1"
+    },
+    "2.1.6": {
+      "title": "Verify that password change functionality requires the user's current and new password.",
+      "level": "1"
+    },
+    "2.1.7": {
+      "title": "Verify that passwords submitted during account registration, login, and password change are checked against a set of breached passwords either locally (such as the top 1,000 or 10,000 most common passwords which match the system's password policy) or using an external API. If using an API a zero knowledge proof or other mechanism should be used to ensure that the plain text password is not sent or used in verifying the breach status of the password. If the password is breached, the application must require the user to set a new non-breached password.",
+      "level": "1"
+    },
+    "2.1.8": {
+      "title": "Verify that a password strength meter is provided to help users set a stronger password.",
+      "level": "1"
+    },
+    "2.1.9": {
+      "title": "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.",
+      "level": "1"
+    },
+    "2.10.1": {
+      "title": "Verify that integration secrets do not rely on unchanging passwords, such as API keys or shared privileged accounts.",
+      "level": "1"
+    },
+    "2.10.2": {
+      "title": "Verify that if passwords are required, the credentials are not a default account.",
+      "level": "1"
+    },
+    "2.10.3": {
+      "title": "Verify that passwords are stored with sufficient protection to prevent offline recovery attacks, including local system access.",
+      "level": "1"
+    },
+    "2.10.4": {
+      "title": "Verify passwords, integrations with databases and third-party systems, seeds and internal secrets, and API keys are managed securely and not included in the source code or stored within source code repositories. Such storage SHOULD resist offline attacks. The use of a secure software key store (L1), hardware trusted platform module (TPM), or a hardware security module (L3) is recommended for password storage.",
+      "level": "1"
+    },
+    "2.2.1": {
+      "title": "Verify that anti-automation controls are effective at mitigating breached credential testing, brute force, and account lockout attacks. Such controls include blocking the most common breached passwords, soft lockouts, rate limiting, CAPTCHA, ever increasing delays between attempts, IP address restrictions, or risk-based restrictions such as location, first login on a device, recent attempts to unlock the account, or similar. Verify that no more than 100 failed attempts per hour is possible on a single account.",
+      "level": "1"
+    },
+    "2.2.2": {
+      "title": "Verify that the use of weak authenticators (such as SMS and email) is limited to secondary verification and transaction approval and not as a replacement for more secure authentication methods. Verify that stronger methods are offered before weak methods, users are aware of the risks, or that proper measures are in place to limit the risks of account compromise.",
+      "level": "1"
+    },
+    "2.2.3": {
+      "title": "Verify that secure notifications are sent to users after updates to authentication details, such as credential resets, email or address changes, logging in from unknown or risky locations. The use of push notifications - rather than SMS or email - is preferred, but in the absence of push notifications, SMS or email is acceptable as long as no sensitive information is disclosed in the notification.",
+      "level": "1"
+    },
+    "2.2.4": {
+      "title": "Verify impersonation resistance against phishing, such as the use of multi-factor authentication, cryptographic devices with intent (such as connected keys with a push to authenticate), or at higher AAL levels, client-side certificates.",
+      "level": "3"
+    },
+    "2.2.5": {
+      "title": "Verify that where a credential service provider (CSP) and the application verifying authentication are separated, mutually authenticated TLS is in place between the two endpoints.",
+      "level": "3"
+    },
+    "2.2.6": {
+      "title": "Verify replay resistance through the mandated use of OTP devices, cryptographic authenticators, or lookup codes.",
+      "level": "3"
+    },
+    "2.2.7": {
+      "title": "Verify intent to authenticate by requiring the entry of an OTP token or user-initiated action such as a button press on a FIDO hardware key.",
+      "level": "3"
+    },
+    "2.3.1": {
+      "title": "Verify system generated initial passwords or activation codes SHOULD be securely randomly generated, SHOULD be at least 6 characters long, and MAY contain letters and numbers, and expire after a short period of time. These initial secrets must not be permitted to become the long term password.",
+      "level": "1"
+    },
+    "2.3.2": {
+      "title": "Verify that enrollment and use of subscriber-provided authentication devices are supported, such as a U2F or FIDO tokens.",
+      "level": "2"
+    },
+    "2.3.3": {
+      "title": "Verify that renewal instructions are sent with sufficient time to renew time bound authenticators.",
+      "level": "2"
+    },
+    "2.4.1": {
+      "title": "Verify that passwords are stored in a form that is resistant to offline attacks. Passwords SHALL be salted and hashed using an approved one-way key derivation or password hashing function. Key derivation and password hashing functions take a password, a salt, and a cost factor as inputs when generating a password hash.",
+      "level": "2"
+    },
+    "2.4.2": {
+      "title": "Verify that the salt is at least 32 bits in length and be chosen arbitrarily to minimize salt value collisions among stored hashes. For each credential, a unique salt value and the resulting hash SHALL be stored.",
+      "level": "2"
+    },
+    "2.4.3": {
+      "title": "Verify that if PBKDF2 is used, the iteration count SHOULD be as large as verification server performance will allow, typically at least 100,000 iterations.",
+      "level": "2"
+    },
+    "2.4.4": {
+      "title": "Verify that if bcrypt is used, the work factor SHOULD be as large as verification server performance will allow, typically at least 13.",
+      "level": "2"
+    },
+    "2.4.5": {
+      "title": "Verify that an additional iteration of a key derivation function is performed, using a salt value that is secret and known only to the verifier. Generate the salt value using an approved random bit generator [SP 800-90Ar1] and provide at least the minimum security strength specified in the latest revision of SP 800-131A. The secret salt value SHALL be stored separately from the hashed passwords (e.g., in a specialized device like a hardware security module).",
+      "level": "2"
+    },
+    "2.5.1": {
+      "title": "Verify that a system generated initial activation or recovery secret is not sent in clear text to the user.",
+      "level": "1"
+    },
+    "2.5.2": {
+      "title": "Verify password hints or knowledge-based authentication (so-called \"secret questions\") are not present.",
+      "level": "1"
+    },
+    "2.5.3": {
+      "title": "Verify password credential recovery does not reveal the current password in any way.",
+      "level": "1"
+    },
+    "2.5.4": {
+      "title": "Verify shared or default accounts are not present (e.g. \"root\", \"admin\", or \"sa\").",
+      "level": "1"
+    },
+    "2.5.5": {
+      "title": "Verify that if an authentication factor is changed or replaced, that the user is notified of this event.",
+      "level": "1"
+    },
+    "2.5.6": {
+      "title": "Verify forgotten password, and other recovery paths use a secure recovery mechanism, such as TOTP or other soft token, mobile push, or another offline recovery mechanism.",
+      "level": "1"
+    },
+    "2.5.7": {
+      "title": "Verify that if OTP or multi-factor authentication factors are lost, that evidence of identity proofing is performed at the same level as during enrollment.",
+      "level": "2"
+    },
+    "2.6.1": {
+      "title": "Verify that lookup secrets can be used only once.",
+      "level": "2"
+    },
+    "2.6.2": {
+      "title": "Verify that lookup secrets have sufficient randomness (112 bits of entropy), or if less than 112 bits of entropy, salted with a unique and random 32-bit salt and hashed with an approved one-way hash.",
+      "level": "2"
+    },
+    "2.6.3": {
+      "title": "Verify that lookup secrets are resistant to offline attacks, such as predictable values.",
+      "level": "2"
+    },
+    "2.7.1": {
+      "title": "Verify that clear text out of band (NIST \"restricted\") authenticators, such as SMS or PSTN, are not offered by default, and stronger alternatives such as push notifications are offered first.",
+      "level": "1"
+    },
+    "2.7.2": {
+      "title": "Verify that the out of band verifier expires out of band authentication requests, codes, or tokens after 10 minutes.",
+      "level": "1"
+    },
+    "2.7.3": {
+      "title": "Verify that the out of band verifier authentication requests, codes, or tokens are only usable once, and only for the original authentication request.",
+      "level": "1"
+    },
+    "2.7.4": {
+      "title": "Verify that the out of band authenticator and verifier communicates over a secure independent channel.",
+      "level": "1"
+    },
+    "2.7.5": {
+      "title": "Verify that the out of band verifier retains only a hashed version of the authentication code.",
+      "level": "2"
+    },
+    "2.7.6": {
+      "title": "Verify that the initial authentication code is generated by a secure random number generator, containing at least 20 bits of entropy (typically a six digital random number is sufficient).",
+      "level": "2"
+    },
+    "2.8.1": {
+      "title": "Verify that time-based OTPs have a defined lifetime before expiring.",
+      "level": "1"
+    },
+    "2.8.2": {
+      "title": "Verify that symmetric keys used to verify submitted OTPs are highly protected, such as by using a hardware security module or secure operating system based key storage.",
+      "level": "2"
+    },
+    "2.8.3": {
+      "title": "Verify that approved cryptographic algorithms are used in the generation, seeding, and verification.",
+      "level": "2"
+    },
+    "2.8.4": {
+      "title": "Verify that time-based OTP can be used only once within the validity period.",
+      "level": "2"
+    },
+    "2.8.5": {
+      "title": "Verify that if a time-based multi factor OTP token is re-used during the validity period, it is logged and rejected with secure notifications being sent to the holder of the device.",
+      "level": "2"
+    },
+    "2.8.6": {
+      "title": "Verify physical single factor OTP generator can be revoked in case of theft or other loss. Ensure that revocation is immediately effective across logged in sessions, regardless of location.",
+      "level": "2"
+    },
+    "2.8.7": {
+      "title": "Verify that biometric authenticators are limited to use only as secondary factors in conjunction with either something you have and something you know.",
+      "level": "3"
+    },
+    "2.9.1": {
+      "title": "Verify that cryptographic keys used in verification are stored securely and protected against disclosure, such as using a TPM or HSM, or an OS service that can use this secure storage.",
+      "level": "2"
+    },
+    "2.9.2": {
+      "title": "Verify that the challenge nonce is at least 64 bits in length, and statistically unique or unique over the lifetime of the cryptographic device.",
+      "level": "2"
+    },
+    "2.9.3": {
+      "title": "Verify that approved cryptographic algorithms are used in the generation, seeding, and verification.",
+      "level": "2"
+    },
+    "3.1.1": {
+      "title": "Verify the application never reveals session tokens in URL parameters or error messages.",
+      "level": "1"
+    },
+    "3.2.1": {
+      "title": "Verify the application generates a new session token on user authentication.",
+      "level": "1"
+    },
+    "3.2.2": {
+      "title": "Verify that session tokens possess at least 64 bits of entropy.",
+      "level": "1"
+    },
+    "3.2.3": {
+      "title": "Verify the application only stores session tokens in the browser using secure methods such as appropriately secured cookies (see section 3.4) or HTML 5 session storage.",
+      "level": "1"
+    },
+    "3.2.4": {
+      "title": "Verify that session token are generated using approved cryptographic algorithms.",
+      "level": "2"
+    },
+    "3.3.1": {
+      "title": "Verify that logout and expiration invalidate the session token, such that the back button or a downstream relying party does not resume an authenticated session, including across relying parties.",
+      "level": "1"
+    },
+    "3.3.2": {
+      "title": "If authenticators permit users to remain logged in, verify that re-authentication occurs periodically both when actively used or after an idle period.",
+      "level": "1"
+    },
+    "3.3.3": {
+      "title": "Verify that the application terminates all other active sessions after a successful password change, and that this is effective across the application, federated login (if present), and any relying parties.",
+      "level": "2"
+    },
+    "3.3.4": {
+      "title": "Verify that users are able to view and log out of any or all currently active sessions and devices.",
+      "level": "2"
+    },
+    "3.4.1": {
+      "title": "Verify that cookie-based session tokens have the 'Secure' attribute set.",
+      "level": "1"
+    },
+    "3.4.2": {
+      "title": "Verify that cookie-based session tokens have the 'HttpOnly' attribute set.",
+      "level": "1"
+    },
+    "3.4.3": {
+      "title": "Verify that cookie-based session tokens utilize the 'SameSite' attribute to limit exposure to cross-site request forgery attacks.",
+      "level": "1"
+    },
+    "3.4.4": {
+      "title": "Verify that cookie-based session tokens use \"__Host-\" prefix (see references) to provide session cookie confidentiality.",
+      "level": "1"
+    },
+    "3.4.5": {
+      "title": "Verify that if the application is published under a domain name with other applications that set or use session cookies that might override or disclose the session cookies, set the path attribute in cookie-based session tokens using the most precise path possible.",
+      "level": "1"
+    },
+    "3.5.1": {
+      "title": "Verify the application does not treat OAuth and refresh tokens &mdash; on their own &mdash; as the presence of the subscriber and allows users to terminate trust relationships with linked applications.",
+      "level": "2"
+    },
+    "3.5.2": {
+      "title": "Verify the application uses session tokens rather than static API secrets and keys, except with legacy implementations.",
+      "level": "2"
+    },
+    "3.5.3": {
+      "title": "Verify that stateless session tokens use digital signatures, encryption, and other countermeasures to protect against tampering, enveloping, replay, null cipher, and key substitution attacks.",
+      "level": "2"
+    },
+    "3.6.1": {
+      "title": "Verify that relying parties specify the maximum authentication time to CSPs and that CSPs re-authenticate the subscriber if they haven't used a session within that period.",
+      "level": "3"
+    },
+    "3.6.2": {
+      "title": "Verify that CSPs inform relying parties of the last authentication event, to allow RPs to determine if they need to re-authenticate the user.",
+      "level": "3"
+    },
+    "3.7.1": {
+      "title": "Verify the application ensures a valid login session or requires re-authentication or secondary verification before allowing any sensitive transactions or account modifications.",
+      "level": "1"
+    },
+    "4.1.1": {
+      "title": "Verify that the application enforces access control rules on a trusted service layer, especially if client-side access control is present and could be bypassed.",
+      "level": "1"
+    },
+    "4.1.2": {
+      "title": "Verify that all user and data attributes and policy information used by access controls cannot be manipulated by end users unless specifically authorized.",
+      "level": "1"
+    },
+    "4.1.3": {
+      "title": "Verify that the principle of least privilege exists - users should only be able to access functions, data files, URLs, controllers, services, and other resources, for which they possess specific authorization. This implies protection against spoofing and elevation of privilege.",
+      "level": "1"
+    },
+    "4.1.4": {
+      "title": "Verify that the principle of deny by default exists whereby new users/roles start with minimal or no permissions and users/roles do not receive access to new features until access is explicitly assigned. ",
+      "level": "1"
+    },
+    "4.1.5": {
+      "title": "Verify that access controls fail securely including when an exception occurs.",
+      "level": "1"
+    },
+    "4.2.1": {
+      "title": "Verify that sensitive data and APIs are protected against direct object attacks targeting creation, reading, updating and deletion of records, such as creating or updating someone else's record, viewing everyone's records, or deleting all records.",
+      "level": "1"
+    },
+    "4.2.2": {
+      "title": "Verify that the application or framework enforces a strong anti-CSRF mechanism to protect authenticated functionality, and effective anti-automation or anti-CSRF protects unauthenticated functionality.",
+      "level": "1"
+    },
+    "4.3.1": {
+      "title": "Verify administrative interfaces use appropriate multi-factor authentication to prevent unauthorized use.",
+      "level": "1"
+    },
+    "4.3.2": {
+      "title": "Verify that directory browsing is disabled unless deliberately desired. Additionally, applications should not allow discovery or disclosure of file or directory metadata, such as Thumbs.db, .DS_Store, .git or .svn folders.",
+      "level": "1"
+    },
+    "4.3.3": {
+      "title": "Verify the application has additional authorization (such as step up or adaptive authentication) for lower value systems, and / or segregation of duties for high value applications to enforce anti-fraud controls as per the risk of application and past fraud.",
+      "level": "2"
+    },
+    "5.1.1": {
+      "title": "Verify that the application has defenses against HTTP parameter pollution attacks, particularly if the application framework makes no distinction about the source of request parameters (GET, POST, cookies, headers, or environment variables).",
+      "level": "1"
+    },
+    "5.1.2": {
+      "title": "Verify that frameworks protect against mass parameter assignment attacks, or that the application has countermeasures to protect against unsafe parameter assignment, such as marking fields private or similar.",
+      "level": "1"
+    },
+    "5.1.3": {
+      "title": "Verify that all input (HTML form fields, REST requests, URL parameters, HTTP headers, cookies, batch files, RSS feeds, etc) is validated using positive validation (whitelisting).",
+      "level": "1"
+    },
+    "5.1.4": {
+      "title": "Verify that structured data is strongly typed and validated against a defined schema including allowed characters, length and pattern (e.g. credit card numbers or telephone, or validating that two related fields are reasonable, such as checking that suburb and zip/postcode match).",
+      "level": "1"
+    },
+    "5.1.5": {
+      "title": "Verify that URL redirects and forwards only allow whitelisted destinations, or show a warning when redirecting to potentially untrusted content.",
+      "level": "1"
+    },
+    "5.2.1": {
+      "title": "Verify that all untrusted HTML input from WYSIWYG editors or similar is properly sanitized with an HTML sanitizer library or framework feature.",
+      "level": "1"
+    },
+    "5.2.2": {
+      "title": "Verify that unstructured data is sanitized to enforce safety measures such as allowed characters and length.",
+      "level": "1"
+    },
+    "5.2.3": {
+      "title": "Verify that the application sanitizes user input before passing to mail systems to protect against SMTP or IMAP injection.",
+      "level": "1"
+    },
+    "5.2.4": {
+      "title": "Verify that the application avoids the use of eval() or other dynamic code execution features. Where there is no alternative, any user input being included must be sanitized or sandboxed before being executed.",
+      "level": "1"
+    },
+    "5.2.5": {
+      "title": "Verify that the application protects against template injection attacks by ensuring that any user input being included is sanitized or sandboxed.",
+      "level": "1"
+    },
+    "5.2.6": {
+      "title": "Verify that the application protects against SSRF attacks, by validating or sanitizing untrusted data or HTTP file metadata, such as filenames and URL input fields, use whitelisting of protocols, domains, paths and ports.",
+      "level": "1"
+    },
+    "5.2.7": {
+      "title": "Verify that the application sanitizes, disables, or sandboxes user-supplied SVG scriptable content, especially as they relate to XSS resulting from inline scripts, and foreignObject.",
+      "level": "1"
+    },
+    "5.2.8": {
+      "title": "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.",
+      "level": "1"
+    },
+    "5.3.1": {
+      "title": "Verify that output encoding is relevant for the interpreter and context required. For example, use encoders specifically for HTML values, HTML attributes, JavaScript, URL Parameters, HTTP headers, SMTP, and others as the context requires, especially from untrusted inputs (e.g. names with Unicode or apostrophes, such as ねこ or O'Hara).",
+      "level": "1"
+    },
+    "5.3.10": {
+      "title": "Verify that the application protects against XPath injection or XML injection attacks.",
+      "level": "1"
+    },
+    "5.3.2": {
+      "title": "Verify that output encoding preserves the user's chosen character set and locale, such that any Unicode character point is valid and safely handled.",
+      "level": "1"
+    },
+    "5.3.3": {
+      "title": "Verify that context-aware, preferably automated - or at worst, manual - output escaping protects against reflected, stored, and DOM based XSS.",
+      "level": "1"
+    },
+    "5.3.4": {
+      "title": "Verify that data selection or database queries (e.g. SQL, HQL, ORM, NoSQL) use parameterized queries, ORMs, entity frameworks, or are otherwise protected from database injection attacks.",
+      "level": "1"
+    },
+    "5.3.5": {
+      "title": "Verify that where parameterized or safer mechanisms are not present, context-specific output encoding is used to protect against injection attacks, such as the use of SQL escaping to protect against SQL injection.",
+      "level": "1"
+    },
+    "5.3.6": {
+      "title": "Verify that the application projects against JavaScript or JSON injection attacks, including for eval attacks, remote JavaScript includes, CSP bypasses, DOM XSS, and JavaScript expression evaluation.",
+      "level": "1"
+    },
+    "5.3.7": {
+      "title": "Verify that the application protects against LDAP Injection vulnerabilities, or that specific security controls to prevent LDAP Injection have been implemented.",
+      "level": "1"
+    },
+    "5.3.8": {
+      "title": "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.",
+      "level": "1"
+    },
+    "5.3.9": {
+      "title": "Verify that the application protects against Local File Inclusion (LFI) or Remote File Inclusion (RFI) attacks.",
+      "level": "1"
+    },
+    "5.4.1": {
+      "title": "Verify that the application uses memory-safe string, safer memory copy and pointer arithmetic to detect or prevent stack, buffer, or heap overflows.",
+      "level": "2"
+    },
+    "5.4.2": {
+      "title": "Verify that format strings do not take potentially hostile input, and are constant.",
+      "level": "2"
+    },
+    "5.4.3": {
+      "title": "Verify that sign, range, and input validation techniques are used to prevent integer overflows.",
+      "level": "2"
+    },
+    "5.5.1": {
+      "title": "Verify that serialized objects use integrity checks or are encrypted to prevent hostile object creation or data tampering.",
+      "level": "1"
+    },
+    "5.5.2": {
+      "title": "Verify that the application correctly restricts XML parsers to only use the most restrictive configuration possible and to ensure that unsafe features such as resolving external entities are disabled to prevent XXE.",
+      "level": "1"
+    },
+    "5.5.3": {
+      "title": "Verify that deserialization of untrusted data is avoided or is protected in both custom code and third-party libraries (such as JSON, XML and YAML parsers).",
+      "level": "1"
+    },
+    "5.5.4": {
+      "title": "Verify that when parsing JSON in browsers or JavaScript-based backends, JSON.parse is used to parse the JSON document. Do not use eval() to parse JSON.",
+      "level": "1"
+    },
+    "6.1.1": {
+      "title": "Verify that regulated private data is stored encrypted while at rest, such as personally identifiable information (PII), sensitive personal information, or data assessed likely to be subject to EU's GDPR.",
+      "level": "2"
+    },
+    "6.1.2": {
+      "title": "Verify that regulated health data is stored encrypted while at rest, such as medical records, medical device details, or de-anonymized research records.",
+      "level": "2"
+    },
+    "6.1.3": {
+      "title": "Verify that regulated financial data is stored encrypted while at rest, such as financial accounts, defaults or credit history, tax records, pay history, beneficiaries, or de-anonymized market or research records.",
+      "level": "2"
+    },
+    "6.2.1": {
+      "title": "Verify that all cryptographic modules fail securely, and errors are handled in a way that does not enable Padding Oracle attacks.",
+      "level": "1"
+    },
+    "6.2.2": {
+      "title": "Verify that industry proven or government approved cryptographic algorithms, modes, and libraries are used, instead of custom coded cryptography.",
+      "level": "2"
+    },
+    "6.2.3": {
+      "title": "Verify that encryption initialization vector, cipher configuration, and block modes are configured securely using the latest advice.",
+      "level": "2"
+    },
+    "6.2.4": {
+      "title": "Verify that random number, encryption or hashing algorithms, key lengths, rounds, ciphers or modes, can be reconfigured, upgraded, or swapped at any time, to protect against cryptographic breaks.",
+      "level": "2"
+    },
+    "6.2.5": {
+      "title": "Verify that known insecure block modes (i.e. ECB, etc.), padding modes (i.e. PKCS#1 v1.5, etc.), ciphers with small block sizes (i.e. Triple-DES, Blowfish, etc.), and weak hashing algorithms (i.e. MD5, SHA1, etc.) are not used unless required for backwards compatibility.",
+      "level": "2"
+    },
+    "6.2.6": {
+      "title": "Verify that nonces, initialization vectors, and other single use numbers must not be used more than once with a given encryption key. The method of generation must be appropriate for the algorithm being used.",
+      "level": "2"
+    },
+    "6.2.7": {
+      "title": "Verify that encrypted data is authenticated via signatures, authenticated cipher modes, or HMAC to ensure that ciphertext is not altered by an unauthorized party.",
+      "level": "3"
+    },
+    "6.2.8": {
+      "title": "Verify that all cryptographic operations are constant-time, with no 'short-circuit' operations in comparisons, calculations, or returns, to avoid leaking information.",
+      "level": "3"
+    },
+    "6.3.1": {
+      "title": "Verify that all random numbers, random file names, random GUIDs, and random strings are generated using the cryptographic module's approved cryptographically secure random number generator when these random values are intended to be not guessable by an attacker.",
+      "level": "2"
+    },
+    "6.3.2": {
+      "title": "Verify that random GUIDs are created using the GUID v4 algorithm, and a cryptographically-secure pseudo-random number generator (CSPRNG). GUIDs created using other pseudo-random number generators may be predictable.",
+      "level": "2"
+    },
+    "6.3.3": {
+      "title": "Verify that random numbers are created with proper entropy even when the application is under heavy load, or that the application degrades gracefully in such circumstances.",
+      "level": "3"
+    },
+    "6.4.1": {
+      "title": "Verify that a secrets management solution such as a key vault is used to securely create, store, control access to and destroy secrets.",
+      "level": "2"
+    },
+    "6.4.2": {
+      "title": "Verify that key material is not exposed to the application but instead uses an isolated security module like a vault for cryptographic operations.",
+      "level": "2"
+    },
+    "7.1.1": {
+      "title": "Verify that the application does not log credentials or payment details. Session tokens should only be stored in logs in an irreversible, hashed form.",
+      "level": "1"
+    },
+    "7.1.2": {
+      "title": "Verify that the application does not log other sensitive data as defined under local privacy laws or relevant security policy.",
+      "level": "1"
+    },
+    "7.1.3": {
+      "title": "Verify that the application logs security relevant events including successful and failed authentication events, access control failures, deserialization failures and input validation failures.",
+      "level": "2"
+    },
+    "7.1.4": {
+      "title": "Verify that each log event includes necessary information that would allow for a detailed investigation of the timeline when an event happens.",
+      "level": "2"
+    },
+    "7.2.1": {
+      "title": "Verify that all authentication decisions are logged, without storing sensitive session identifiers or passwords. This should include requests with relevant metadata needed for security investigations.",
+      "level": "2"
+    },
+    "7.2.2": {
+      "title": "Verify that all access control decisions can be logged and all failed decisions are logged. This should include requests with relevant metadata needed for security investigations.",
+      "level": "2"
+    },
+    "7.3.1": {
+      "title": "Verify that the application appropriately encodes user-supplied data to prevent log injection.",
+      "level": "2"
+    },
+    "7.3.2": {
+      "title": "Verify that all events are protected from injection when viewed in log viewing software.",
+      "level": "2"
+    },
+    "7.3.3": {
+      "title": "Verify that security logs are protected from unauthorized access and modification.",
+      "level": "2"
+    },
+    "7.3.4": {
+      "title": "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.",
+      "level": "2"
+    },
+    "7.4.1": {
+      "title": "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.",
+      "level": "1"
+    },
+    "7.4.2": {
+      "title": "Verify that exception handling (or a functional equivalent) is used across the codebase to account for expected and unexpected error conditions.",
+      "level": "2"
+    },
+    "7.4.3": {
+      "title": "Verify that a \"last resort\" error handler is defined which will catch all unhandled exceptions.",
+      "level": "2"
+    },
+    "8.1.1": {
+      "title": "Verify the application protects sensitive data from being cached in server components such as load balancers and application caches.",
+      "level": "2"
+    },
+    "8.1.2": {
+      "title": "Verify that all cached or temporary copies of sensitive data stored on the server are protected from unauthorized access or purged/invalidated after the authorized user accesses the sensitive data.",
+      "level": "2"
+    },
+    "8.1.3": {
+      "title": "Verify the application minimizes the number of parameters in a request, such as hidden fields, Ajax variables, cookies and header values.",
+      "level": "2"
+    },
+    "8.1.4": {
+      "title": "Verify the application can detect and alert on abnormal numbers of requests, such as by IP, user, total per hour or day, or whatever makes sense for the application.",
+      "level": "2"
+    },
+    "8.1.5": {
+      "title": "Verify that regular backups of important data are performed and that test restoration of data is performed.",
+      "level": "3"
+    },
+    "8.1.6": {
+      "title": "Verify that backups are stored securely to prevent data from being stolen or corrupted.",
+      "level": "3"
+    },
+    "8.2.1": {
+      "title": "Verify the application sets sufficient anti-caching headers so that sensitive data is not cached in modern browsers.",
+      "level": "1"
+    },
+    "8.2.2": {
+      "title": "Verify that data stored in client side storage (such as HTML5 local storage, session storage, IndexedDB, regular cookies or Flash cookies) does not contain sensitive data or PII.",
+      "level": "1"
+    },
+    "8.2.3": {
+      "title": "Verify that authenticated data is cleared from client storage, such as the browser DOM, after the client or session is terminated.",
+      "level": "1"
+    },
+    "8.3.1": {
+      "title": "Verify that sensitive data is sent to the server in the HTTP message body or headers, and that query string parameters from any HTTP verb do not contain sensitive data.",
+      "level": "1"
+    },
+    "8.3.2": {
+      "title": "Verify that users have a method to remove or export their data on demand.",
+      "level": "1"
+    },
+    "8.3.3": {
+      "title": "Verify that users are provided clear language regarding collection and use of supplied personal information and that users have provided opt-in consent for the use of that data before it is used in any way.",
+      "level": "1"
+    },
+    "8.3.4": {
+      "title": "Verify that all sensitive data created and processed by the application has been identified, and ensure that a policy is in place on how to deal with sensitive data.",
+      "level": "1"
+    },
+    "8.3.5": {
+      "title": "Verify accessing sensitive data is audited (without logging the sensitive data itself), if the data is collected under relevant data protection directives or where logging of access is required.",
+      "level": "2"
+    },
+    "8.3.6": {
+      "title": "Verify that sensitive information contained in memory is overwritten as soon as it is no longer required to mitigate memory dumping attacks, using zeroes or random data.",
+      "level": "2"
+    },
+    "8.3.7": {
+      "title": "Verify that sensitive or private information that is required to be encrypted, is encrypted using approved algorithms that provide both confidentiality and integrity.",
+      "level": "2"
+    },
+    "8.3.8": {
+      "title": "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.",
+      "level": "2"
+    },
+    "9.1.1": {
+      "title": "Verify that secured TLS is used for all client connectivity, and does not fall back to insecure or unencrypted protocols.",
+      "level": "1"
+    },
+    "9.1.2": {
+      "title": "Verify using online or up to date TLS testing tools that only strong algorithms, ciphers, and protocols are enabled, with the strongest algorithms and ciphers set as preferred.",
+      "level": "1"
+    },
+    "9.1.3": {
+      "title": "Verify that old versions of SSL and TLS protocols, algorithms, ciphers, and configuration are disabled, such as SSLv2, SSLv3, or TLS 1.0 and TLS 1.1. The latest version of TLS should be the preferred cipher suite.",
+      "level": "1"
+    },
+    "9.2.1": {
+      "title": "Verify that connections to and from the server use trusted TLS certificates. Where internally generated or self-signed certificates are used, the server must be configured to only trust specific internal CAs and specific self-signed certificates. All others should be rejected.",
+      "level": "2"
+    },
+    "9.2.2": {
+      "title": "Verify that encrypted communications such as TLS is used for all inbound and outbound connections, including for management ports, monitoring, authentication, API, or web service calls, database, cloud, serverless, mainframe, external, and partner connections. The server must not fall back to insecure or unencrypted protocols.",
+      "level": "2"
+    },
+    "9.2.3": {
+      "title": "Verify that all encrypted connections to external systems that involve sensitive information or functions are authenticated.",
+      "level": "2"
+    },
+    "9.2.4": {
+      "title": "Verify that proper certification revocation, such as Online Certificate Status Protocol (OCSP) Stapling, is enabled and configured.",
+      "level": "2"
+    },
+    "9.2.5": {
+      "title": "Verify that backend TLS connection failures are logged.",
+      "level": "3"
+    },
+    "10.1.1": {
+      "title": "Verify that a code analysis tool is in use that can detect potentially malicious code, such as time functions, unsafe file operations and network connections.",
+      "level": "3"
+    },
+    "10.2.1": {
+      "title": "Verify that the application source code and third party libraries do not contain unauthorized phone home or data collection capabilities. Where such functionality exists, obtain the user's permission for it to operate  before collecting any data.",
+      "level": "2"
+    },
+    "10.2.2": {
+      "title": "Verify that the application does not ask for unnecessary or excessive permissions to privacy related features or sensors, such as contacts, cameras, microphones, or location.",
+      "level": "2"
+    },
+    "10.2.3": {
+      "title": "Verify that the application source code and third party libraries do not contain back doors, such as hard-coded or additional undocumented accounts or keys, code obfuscation, undocumented binary blobs, rootkits, or anti-debugging, insecure debugging features, or otherwise out of date, insecure, or hidden functionality that could be used maliciously if discovered.",
+      "level": "3"
+    },
+    "10.2.4": {
+      "title": "Verify that the application source code and third party libraries does not contain time bombs by searching for date and time related functions.",
+      "level": "3"
+    },
+    "10.2.5": {
+      "title": "Verify that the application source code and third party libraries does not contain malicious code, such as salami attacks, logic bypasses, or logic bombs.",
+      "level": "3"
+    },
+    "10.2.6": {
+      "title": "Verify that the application source code and third party libraries do not contain Easter eggs or any other potentially unwanted functionality.",
+      "level": "3"
+    },
+    "10.3.1": {
+      "title": "Verify that if the application has a client or server auto-update feature, updates should be obtained over secure channels and digitally signed. The update code must validate the digital signature of the update before installing or executing the update.",
+      "level": "1"
+    },
+    "10.3.2": {
+      "title": "Verify that the application employs integrity protections, such as code signing or sub-resource integrity. The application must not load or execute code from untrusted sources, such as loading includes, modules, plugins, code, or libraries from untrusted sources or the Internet.",
+      "level": "1"
+    },
+    "10.3.3": {
+      "title": "Verify that the application has protection from sub-domain takeovers if the application relies upon DNS entries or DNS sub-domains, such as expired domain names, out of date DNS pointers or CNAMEs, expired projects at public source code repos, or transient cloud APIs, serverless functions, or storage buckets (autogen-bucket-id.cloud.example.com) or similar. Protections can include ensuring that DNS names used by applications are regularly checked for expiry or change.",
+      "level": "1"
+    },
+    "11.1.1": {
+      "title": "Verify the application will only process business logic flows for the same user in sequential step order and without skipping steps.",
+      "level": "1"
+    },
+    "11.1.2": {
+      "title": "Verify the application will only process business logic flows with all steps being processed in realistic human time, i.e. transactions are not submitted too quickly.",
+      "level": "1"
+    },
+    "11.1.3": {
+      "title": "Verify the application has appropriate limits for specific business actions or transactions which are correctly enforced on a per user basis.",
+      "level": "1"
+    },
+    "11.1.4": {
+      "title": "Verify the application has sufficient anti-automation controls to detect and protect against data exfiltration, excessive business logic requests, excessive file uploads or denial of service attacks.",
+      "level": "1"
+    },
+    "11.1.5": {
+      "title": "Verify the application has business logic limits or validation to protect against likely business risks or threats, identified using threat modelling or similar methodologies.",
+      "level": "1"
+    },
+    "11.1.6": {
+      "title": "Verify the application does not suffer from \"time of check to time of use\" (TOCTOU) issues or other race conditions for sensitive operations.",
+      "level": "2"
+    },
+    "11.1.7": {
+      "title": "Verify the application monitors for unusual events or activity from a business logic perspective. For example, attempts to perform actions out of order or actions which a normal user would never attempt.",
+      "level": "2"
+    },
+    "11.1.8": {
+      "title": "Verify the application has configurable alerting when automated attacks or unusual activity is detected.",
+      "level": "2"
+    },
+    "12.1.1": {
+      "title": "Verify that the application will not accept large files that could fill up storage or cause a denial of service attack.",
+      "level": "1"
+    },
+    "12.1.2": {
+      "title": "Verify that compressed files are checked for \"zip bombs\" - small input files that will decompress into huge files thus exhausting file storage limits.",
+      "level": "2"
+    },
+    "12.1.3": {
+      "title": "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.",
+      "level": "2"
+    },
+    "12.2.1": {
+      "title": "Verify that files obtained from untrusted sources are validated to be of expected type based on the file's content.",
+      "level": "2"
+    },
+    "12.3.1": {
+      "title": "Verify that user-submitted filename metadata is not used directly with system or framework file and URL API to protect against path traversal.",
+      "level": "1"
+    },
+    "12.3.2": {
+      "title": "Verify that user-submitted filename metadata is validated or ignored to prevent the disclosure, creation, updating or removal of local files (LFI).",
+      "level": "1"
+    },
+    "12.3.3": {
+      "title": "Verify that user-submitted filename metadata is validated or ignored to prevent the disclosure or execution of remote files (RFI), which may also lead to SSRF.",
+      "level": "1"
+    },
+    "12.3.4": {
+      "title": "Verify that the application protects against reflective file download (RFD) by validating or ignoring user-submitted filenames in a JSON, JSONP, or URL parameter, the response Content-Type header should be set to text/plain, and the Content-Disposition header should have a fixed filename.",
+      "level": "1"
+    },
+    "12.3.5": {
+      "title": "Verify that untrusted file metadata is not used directly with system API or libraries, to protect against OS command injection.",
+      "level": "1"
+    },
+    "12.3.6": {
+      "title": "Verify that the application does not include and execute functionality from untrusted sources, such as unverified content distribution networks, JavaScript libraries, node npm libraries, or server-side DLLs.",
+      "level": "2"
+    },
+    "12.4.1": {
+      "title": "Verify that files obtained from untrusted sources are stored outside the web root, with limited permissions, preferably with strong validation.",
+      "level": "1"
+    },
+    "12.4.2": {
+      "title": "Verify that files obtained from untrusted sources are scanned by antivirus scanners to prevent upload of known malicious content.",
+      "level": "1"
+    },
+    "12.5.1": {
+      "title": "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.",
+      "level": "1"
+    },
+    "12.5.2": {
+      "title": "Verify that direct requests to uploaded files will never be executed as HTML/JavaScript content.",
+      "level": "1"
+    },
+    "12.6.1": {
+      "title": "Verify that the web or application server is configured with a whitelist of resources or systems to which the server can send requests or load data/files from.",
+      "level": "1"
+    },
+    "13.1.1": {
+      "title": "Verify that all application components use the same encodings and parsers to avoid parsing attacks that exploit different URI or file parsing behavior that could be used in SSRF and RFI attacks.",
+      "level": "1"
+    },
+    "13.1.2": {
+      "title": "Verify that access to administration and management functions is limited to authorized administrators.",
+      "level": "1"
+    },
+    "13.1.3": {
+      "title": "Verify API URLs do not expose sensitive information, such as the API key, session tokens etc.",
+      "level": "1"
+    },
+    "13.1.4": {
+      "title": "Verify that authorization decisions are made at both the URI, enforced by programmatic or declarative security at the controller or router, and at the resource level, enforced by model-based permissions.",
+      "level": "2"
+    },
+    "13.1.5": {
+      "title": "Verify that requests containing unexpected or missing content types are rejected with appropriate headers (HTTP response status 406 Unacceptable or 415 Unsupported Media Type).",
+      "level": "2"
+    },
+    "13.2.1": {
+      "title": "Verify that enabled RESTful HTTP methods are a valid choice for the user or action, such as preventing normal users using DELETE or PUT on protected API or resources.",
+      "level": "1"
+    },
+    "13.2.2": {
+      "title": "Verify that JSON schema validation is in place and verified before accepting input.",
+      "level": "1"
+    },
+    "13.2.3": {
+      "title": "Verify that RESTful web services that utilize cookies are protected from Cross-Site Request Forgery via the use of at least one or more of the following: triple or double submit cookie pattern",
+      "level": "1"
+    },
+    "13.2.4": {
+      "title": "Verify that REST services have anti-automation controls to protect against excessive calls, especially if the API is unauthenticated.",
+      "level": "2"
+    },
+    "13.2.5": {
+      "title": "Verify that REST services explicitly check the incoming Content-Type to be the expected one, such as application/xml or application/JSON.",
+      "level": "2"
+    },
+    "13.2.6": {
+      "title": "Verify that the message headers and payload are trustworthy and not modified in transit. Requiring strong encryption for transport (TLS only) may be sufficient in many cases as it provides both confidentiality and integrity protection. Per-message digital signatures can provide additional assurance on top of the transport protections for high-security applications but bring with them additional complexity and risks to weigh against the benefits.",
+      "level": "2"
+    },
+    "13.3.1": {
+      "title": "Verify that XSD schema validation takes place to ensure a properly formed XML document, followed by validation of each input field before any processing of that data takes place.",
+      "level": "1"
+    },
+    "13.3.2": {
+      "title": "Verify that the message payload is signed using WS-Security to ensure reliable transport between client and service.",
+      "level": "2"
+    },
+    "13.4.1": {
+      "title": "Verify that query whitelisting or a combination of depth limiting and amount limiting should be used to prevent GraphQL or data layer expression denial of service (DoS) as a result of expensive, nested queries. For more advanced scenarios, query cost analysis should be used.",
+      "level": "2"
+    },
+    "13.4.2": {
+      "title": "Verify that GraphQL or other data layer authorization logic should be implemented at the business logic layer instead of the GraphQL layer.",
+      "level": "2"
+    },
+    "14.1.1": {
+      "title": "Verify that the application build and deployment processes are performed in a secure and repeatable way, such as CI / CD automation, automated configuration management, and automated deployment scripts.",
+      "level": "2"
+    },
+    "14.1.2": {
+      "title": "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.",
+      "level": "2"
+    },
+    "14.1.3": {
+      "title": "Verify that server configuration is hardened as per the recommendations of the application server and frameworks in use.",
+      "level": "2"
+    },
+    "14.1.4": {
+      "title": "Verify that the application, configuration, and all dependencies can be re-deployed using automated deployment scripts, built from a documented and tested runbook in a reasonable time, or restored from backups in a timely fashion.",
+      "level": "2"
+    },
+    "14.1.5": {
+      "title": "Verify that authorized administrators can verify the integrity of all security-relevant configurations to detect tampering.",
+      "level": "3"
+    },
+    "14.2.1": {
+      "title": "Verify that all components are up to date, preferably using a dependency checker during build or compile time.",
+      "level": "1"
+    },
+    "14.2.2": {
+      "title": "Verify that all unneeded features, documentation, samples, configurations are removed, such as sample applications, platform documentation, and default or example users.",
+      "level": "1"
+    },
+    "14.2.3": {
+      "title": "Verify that if application assets, such as JavaScript libraries, CSS stylesheets or web fonts, are hosted externally on a content delivery network (CDN) or external provider, Subresource Integrity (SRI) is used to validate the integrity of the asset.",
+      "level": "1"
+    },
+    "14.2.4": {
+      "title": "Verify that third party components come from pre-defined, trusted and continually maintained repositories.",
+      "level": "2"
+    },
+    "14.2.5": {
+      "title": "Verify that an inventory catalog is maintained of all third party libraries in use.",
+      "level": "2"
+    },
+    "14.2.6": {
+      "title": "Verify that the attack surface is reduced by sandboxing or encapsulating third party libraries to expose only the required behaviour into the application.",
+      "level": "2"
+    },
+    "14.3.1": {
+      "title": "Verify that web or application server and framework error messages are configured to deliver user actionable, customized responses to eliminate any unintended security disclosures.",
+      "level": "1"
+    },
+    "14.3.2": {
+      "title": "Verify that web or application server and application framework debug modes are disabled in production to eliminate debug features, developer consoles, and unintended security disclosures.",
+      "level": "1"
+    },
+    "14.3.3": {
+      "title": "Verify that the HTTP headers or any part of the HTTP response do not expose detailed version information of system components.",
+      "level": "1"
+    },
+    "14.4.1": {
+      "title": "Verify that every HTTP response contains a content type header specifying a safe character set (e.g., UTF-8, ISO 8859-1).",
+      "level": "1"
+    },
+    "14.4.2": {
+      "title": "Verify that all API responses contain Content-Disposition: attachment; filename=\"api.json\" (or other appropriate filename for the content type).",
+      "level": "1"
+    },
+    "14.4.3": {
+      "title": "Verify that a content security policy (CSPv2) is in place that helps mitigate impact for XSS attacks like HTML, DOM, JSON, and JavaScript injection vulnerabilities.",
+      "level": "1"
+    },
+    "14.4.4": {
+      "title": "Verify that all responses contain X-Content-Type-Options: nosniff.",
+      "level": "1"
+    },
+    "14.4.5": {
+      "title": "Verify that HTTP Strict Transport Security headers are included on all responses and for all subdomains, such as Strict-Transport-Security: max-age=15724800; includeSubdomains.",
+      "level": "1"
+    },
+    "14.4.6": {
+      "title": "Verify that a suitable \"Referrer-Policy\" header is included, such as \"no-referrer\" or \"same-origin\".",
+      "level": "1"
+    },
+    "14.4.7": {
+      "title": "Verify that a suitable X-Frame-Options or Content-Security-Policy: frame-ancestors header is in use for sites where content should not be embedded in a third-party site.",
+      "level": "1"
+    },
+    "14.5.1": {
+      "title": "Verify that the application server only accepts the HTTP methods in use by the application or API, including pre-flight OPTIONS.",
+      "level": "1"
+    },
+    "14.5.2": {
+      "title": "Verify that the supplied Origin header is not used for authentication or access control decisions, as the Origin header can easily be changed by an attacker.",
+      "level": "1"
+    },
+    "14.5.3": {
+      "title": "Verify that the cross-domain resource sharing (CORS) Access-Control-Allow-Origin header uses a strict white-list of trusted domains to match against and does not support the \"null\" origin.",
+      "level": "1"
+    },
+    "14.5.4": {
+      "title": "Verify that HTTP headers added by a trusted proxy or SSO devices, such as a bearer token, are authenticated by the application.",
+      "level": "2"
+    }
   }
 }
diff --git a/server/sonar-web/src/main/js/types/security.ts b/server/sonar-web/src/main/js/types/security.ts
index 2c4aff9923a..63ec41c3b42 100644
--- a/server/sonar-web/src/main/js/types/security.ts
+++ b/server/sonar-web/src/main/js/types/security.ts
@@ -27,6 +27,8 @@ export enum SecurityStandard {
   PCI_DSS_3_2 = 'pciDss-3.2',
   PCI_DSS_4_0 = 'pciDss-4.0',
   OWASP_ASVS_4_0 = 'owaspAsvs-4.0',
+  STIG_ASD_V5R3 = 'stig-ASD_V5R3',
+  CASA = 'casa',
 }
 
 export type StandardType = SecurityStandard;