How to use section method of Verify Package

Best Inspec_ruby code snippet using Verify.section

create_asvs_database.rb

Source:create_asvs_database.rb

...13	(SECTION TEXT PRIMARY KEY	NOT NULL,14	TITLE TEXT	NOT NULL,15	MILESTONE TEXT	NOT NULL );''')16boards = [17{section: '1.1',  title: 'Secure Software Development Lifecycle Requirements', milestone: 'Architecture, Design and Threat Modeling Verification Requirements'},18{section: '1.2',  title: 'Authentication Architectural Requirements', milestone: 'Architecture, Design and Threat Modeling Verification Requirements'},19{section: '1.3',  title: 'Session Management Architectural Requirements', milestone: 'Architecture, Design and Threat Modeling Verification Requirements'},20{section: '1.4',  title: 'Access Control Architectural Requirements', milestone: 'Architecture, Design and Threat Modeling Verification Requirements'},21{section: '1.5',  title: 'Input and Output Architectural Requirements', milestone: 'Architecture, Design and Threat Modeling Verification Requirements'},22{section: '1.6',  title: 'Cryptographic Architectural Requirements', milestone: 'Architecture, Design and Threat Modeling Verification Requirements'},23{section: '1.7',  title: 'Errors, Logging and Auditing Architectural Requirements', milestone: 'Architecture, Design and Threat Modeling Verification Requirements'},24{section: '1.8',  title: 'Data Protection and Privacy Architectural Requirements', milestone: 'Architecture, Design and Threat Modeling Verification Requirements'},25{section: '1.9',  title: 'Communications Architectural Requirements', milestone: 'Architecture, Design and Threat Modeling Verification Requirements'},26{section: '1.10', title: 'Malicious Software Architectural Requirements', milestone: 'Architecture, Design and Threat Modeling Verification Requirements'},27{section: '1.11', title: 'Business Logic Architectural Requirements', milestone: 'Architecture, Design and Threat Modeling Verification Requirements'},28{section: '1.12', title: 'Secure File Upload Architectural Requirements', milestone: 'Architecture, Design and Threat Modeling Verification Requirements'},29{section: '1.13', title: 'API Architectural Requirements', milestone: 'Architecture, Design and Threat Modeling Verification Requirements'},30{section: '1.14', title: 'Configuration Architectural Requirements', milestone: 'Architecture, Design and Threat Modeling Verification Requirements'},31{section: '2.1',  title: 'Password Security Requirements', milestone: 'Authentication Verification Requirements'},32{section: '2.2',  title: 'General Authenticator Requirements', milestone: 'Authentication Verification Requirements'},33{section: '2.3',  title: 'Authenticator Lifecycle Requirements', milestone: 'Authentication Verification Requirements'},34{section: '2.4',  title: 'Credential Storage Requirements', milestone: 'Authentication Verification Requirements'},35{section: '2.5',  title: 'Credential Recovery Requirements', milestone: 'Authentication Verification Requirements'},36{section: '2.6',  title: 'Look-up Secret Verifier Requirements', milestone: 'Authentication Verification Requirements'},37{section: '2.7',  title: 'Out of Band Verifier Requirements', milestone: 'Authentication Verification Requirements'},38{section: '2.8',  title: 'Single or Multi Factor One Time Verifier Requirements', milestone: 'Authentication Verification Requirements'},39{section: '2.9',  title: 'Cryptographic Software and Devices Verifier Requirements', milestone: 'Authentication Verification Requirements'},40{section: '2.10', title: 'Service Authentication Requirements', milestone: 'Authentication Verification Requirements'},41{section: '3.1',  title: 'Fundamental Session Management Requirements', milestone: 'Session Management Verification Requirements'},42{section: '3.2',  title: 'Session Binding Requirements', milestone: 'Session Management Verification Requirements'},43{section: '3.3',  title: 'Session Logout and Timeout Requirements', milestone: 'Session Management Verification Requirements'},44{section: '3.4',  title: 'Cookie-based Session Management', milestone: 'Session Management Verification Requirements'},45{section: '3.5',  title: 'Token-based Session Management', milestone: 'Session Management Verification Requirements'},46{section: '3.6',  title: 'Re-authentication from a Federation or Assertion', milestone: 'Session Management Verification Requirements'},47{section: '3.7',  title: 'Defenses Against Session Management Exploits', milestone: 'Session Management Verification Requirements'},48{section: '4.1',  title: 'General Access Control Design', milestone: 'Access Control Verification Requirements'},49{section: '4.2',  title: 'Operation Level Access Control', milestone: 'Access Control Verification Requirements'},50{section: '4.3',  title: 'Other Access Control Considerations', milestone: 'Access Control Verification Requirements'},51{section: '5.1',  title: 'Input Validation Requirements', milestone: 'Validation, Sanitization and Encoding Verification Requirements'},52{section: '5.2',  title: 'Sanitization and Sandboxing Requirements', milestone: 'Validation, Sanitization and Encoding Verification Requirements'},53{section: '5.3',  title: 'Output encoding and Injection Prevention Requirements', milestone: 'Validation, Sanitization and Encoding Verification Requirements'},54{section: '5.4',  title: 'Memory, String, and Unmanaged Code Requirements', milestone: 'Validation, Sanitization and Encoding Verification Requirements'},55{section: '5.5',  title: 'Deserialization Prevention Requirements', milestone: 'Validation, Sanitization and Encoding Verification Requirements'},56{section: '6.1',  title: 'Data Classification', milestone: 'Stored Cryptography Verification Requirements'},57{section: '6.2',  title: 'Algorithms', milestone: 'Stored Cryptography Verification Requirements'},58{section: '6.3',  title: 'Random Values', milestone: 'Stored Cryptography Verification Requirements'},59{section: '6.4',  title: 'Secret Management', milestone: 'Stored Cryptography Verification Requirements'},60{section: '7.1',  title: 'Log Content Requirements', milestone: 'Error Handling and Logging Verification Requirements'},61{section: '7.2',  title: 'Log Processing Requirements', milestone: 'Error Handling and Logging Verification Requirements'},62{section: '7.3',  title: 'Log Protection Requirements', milestone: 'Error Handling and Logging Verification Requirements'},63{section: '7.4',  title: 'Error Handling', milestone: 'Error Handling and Logging Verification Requirements'},64{section: '8.1',  title: 'General Data Protection', milestone: 'Data Protection Verification Requirements'},65{section: '8.2',  title: 'Client-side Data Protection', milestone: 'Data Protection Verification Requirements'},66{section: '8.3',  title: 'Sensitive Private Data', milestone: 'Data Protection Verification Requirements'},67{section: '9.1',  title: 'Communications Security Requirements', milestone: 'Communications Verification Requirements'},68{section: '9.2',  title: 'Server Communications Security Requirements', milestone: 'Communications Verification Requirements'},69{section: '10.1', title: 'Code Integrity Controls', milestone: 'Malicious Code Verification Requirements'},70{section: '10.2', title: 'Malicious Code Search', milestone: 'Malicious Code Verification Requirements'},71{section: '10.3', title: 'Deployed Application Integrity Controls', milestone: 'Malicious Code Verification Requirements'},72{section: '11.1', title: 'Business Logic Security Requirements', milestone: 'Business Logic Verification Requirements'},73{section: '12.1', title: 'File Upload Requirements', milestone: 'Files and Resources Verification Requirements'},74{section: '12.2', title: 'File Integrity Requirements', milestone: 'Files and Resources Verification Requirements'},75{section: '12.3', title: 'File execution Requirements', milestone: 'Files and Resources Verification Requirements'},76{section: '12.4', title: 'File Storage Requirements', milestone: 'Files and Resources Verification Requirements'},77{section: '12.5', title: 'File Download Requirements', milestone: 'Files and Resources Verification Requirements'},78{section: '12.6', title: 'SSRF Protection Requirements', milestone: 'Files and Resources Verification Requirements'},79{section: '13.1', title: 'Generic Web Service Security Verification Requirements', milestone: 'API and Web Service Verification Requirements'},80{section: '13.2', title: 'RESTful Web Service Verification Requirements', milestone: 'API and Web Service Verification Requirements'},81{section: '13.3', title: 'SOAP Web Service Verification Requirements', milestone: 'API and Web Service Verification Requirements'},82{section: '13.4', title: 'GraphQL and other Web Service Data Layer Security Requirements', milestone: 'API and Web Service Verification Requirements'},83{section: '14.1', title: 'Build', milestone: 'Configuration Verification Requirements'},84{section: '14.2', title: 'Dependency', milestone: 'Configuration Verification Requirements'},85{section: '14.3', title: 'Unintended Security Disclosure Requirements', milestone: 'Configuration Verification Requirements'},86{section: '14.4', title: 'HTTP Security Headers Requirements', milestone: 'Configuration Verification Requirements'},87{section: '14.5', title: 'Validate HTTP Request Header Requirements', milestone: 'Configuration Verification Requirements'},88]89boards.each do |board|90	db.execute("INSERT INTO BOARDS VALUES (?, ?, ?)", board[:section], board[:title], board[:milestone])91end92issues = [93{id: '1.1.1',   section: '1.1',  level: 2, weight: 50,  cwe: '-1', nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify the use of a secure software development lifecycle that addresses security in all stages of development. ([C1](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},94{id: '1.1.2',   section: '1.1',  level: 2, weight: 50,  cwe: 'id1053', nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},95{id: '1.1.3',   section: '1.1',  level: 2, weight: 50,  cwe: 'id1110', nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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"'},96{id: '1.1.4',   section: '1.1',  level: 2, weight: 50,  cwe: 'id1059', nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify documentation and justification of all the application\'s trust boundaries, components, and significant data flows.'},97{id: '1.1.6',   section: '1.1',  level: 2, weight: 50,  cwe: 'id637',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify implementation of centralized, simple (economy of design), vetted, secure, and reusable security controls to avoid duplicate, missing, ineffective, or insecure controls. ([C10](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},98{id: '1.1.7',   section: '1.1',  level: 2, weight: 50,  cwe: 'id637',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify availability of a secure coding checklist, security requirements, guideline, or policy to all developers and testers.'},99{id: '1.10.1',  section: '1.10', level: 2, weight: 50,  cwe: 'id284',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},100{id: '1.11.1',  section: '1.11', level: 2, weight: 50,  cwe: 'id1059', nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify the definition and documentation of all application components in terms of the business or security functions they provide.'},101{id: '1.11.2',  section: '1.11', level: 2, weight: 50,  cwe: 'id362',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify that all high-value business logic flows, including authentication, session management and access control, do not share unsynchronized state.'},102{id: '1.11.3',  section: '1.11', level: 3, weight: 100, cwe: 'id367',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},103{id: '1.12.1',  section: '1.12', level: 2, weight: 50,  cwe: 'id552',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify that user-uploaded files are stored outside of the web root.'},104{id: '1.12.2',  section: '1.12', level: 2, weight: 50,  cwe: 'id646',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},105{id: '1.14.1',  section: '1.14', level: 2, weight: 50,  cwe: 'id923',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},106{id: '1.14.2',  section: '1.14', level: 2, weight: 50,  cwe: 'id494',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify that if deploying binaries to untrusted devices makes use of binary signatures, trusted connections, and verified endpoints.'},107{id: '1.14.3',  section: '1.14', level: 2, weight: 50,  cwe: 'id1104', nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify that the build pipeline warns of out-of-date or insecure components and takes appropriate actions.'},108{id: '1.14.4',  section: '1.14', level: 2, weight: 50,  cwe: '-1', nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},109{id: '1.14.5',  section: '1.14', level: 2, weight: 50,  cwe: 'id265',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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. ([C5](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},110{id: '1.14.6',  section: '1.14', level: 2, weight: 50,  cwe: 'id477',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},111{id: '1.2.1',   section: '1.2',  level: 2, weight: 50,  cwe: 'id250',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify the use of unique or special low-privilege operating system accounts for all application components, services, and servers. ([C3](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},112{id: '1.2.2',   section: '1.2',  level: 2, weight: 50,  cwe: 'id306',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify that communications between application components, including APIs, middleware and data layers, are authenticated. Components should have the least necessary privileges needed. ([C3](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},113{id: '1.2.3',   section: '1.2',  level: 2, weight: 50,  cwe: 'id306',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},114{id: '1.2.4',   section: '1.2',  level: 2, weight: 50,  cwe: 'id306',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},115{id: '1.4.1',   section: '1.4',  level: 2, weight: 50,  cwe: 'id602',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},116{id: '1.4.2',   section: '1.4',  level: 2, weight: 50,  cwe: 'id284',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify that the chosen access control solution is flexible enough to meet the application\'s needs.'},117{id: '1.4.3',   section: '1.4',  level: 2, weight: 50,  cwe: 'id272',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},118{id: '1.4.4',   section: '1.4',  level: 2, weight: 50,  cwe: 'id284',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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. ([C7](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},119{id: '1.4.5',   section: '1.4',  level: 2, weight: 50,  cwe: 'id275',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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. ([C7](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},120{id: '1.5.1',   section: '1.5',  level: 2, weight: 50,  cwe: 'id1029', nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},121{id: '1.5.2',   section: '1.5',  level: 2, weight: 50,  cwe: 'id502',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},122{id: '1.5.3',   section: '1.5',  level: 2, weight: 50,  cwe: 'id602',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify that input validation is enforced on a trusted service layer. ([C5](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},123{id: '1.5.4',   section: '1.5',  level: 2, weight: 50,  cwe: 'id116',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify that output encoding occurs close to or by the interpreter for which it is intended. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},124{id: '1.6.1',   section: '1.6',  level: 2, weight: 50,  cwe: 'id320',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},125{id: '1.6.2',   section: '1.6',  level: 2, weight: 50,  cwe: 'id320',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify that consumers of cryptographic services protect key material and other secrets by using key vaults or API based alternatives.'},126{id: '1.6.3',   section: '1.6',  level: 2, weight: 50,  cwe: 'id320',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify that all keys and passwords are replaceable and are part of a well-defined process to re-encrypt sensitive data.'},127{id: '1.6.4',   section: '1.6',  level: 2, weight: 50,  cwe: 'id320',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},128{id: '1.7.1',   section: '1.7',  level: 2, weight: 50,  cwe: 'id1009', nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify that a common logging format and approach is used across the system.  ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},129{id: '1.7.2',   section: '1.7',  level: 2, weight: 50,  cwe: '-1', nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify that logs are securely transmitted to a preferably remote system for analysis, detection, alerting, and escalation. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},130{id: '1.8.1',   section: '1.8',  level: 2, weight: 50,  cwe: '-1', nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify that all sensitive data is identified and classified into protection levels.'},131{id: '1.8.2',   section: '1.8',  level: 2, weight: 50,  cwe: '-1', nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},132{id: '1.9.1',   section: '1.9',  level: 2, weight: 50,  cwe: 'id319',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', title: 'Verify the application encrypts communications between components, particularly when these components are in different containers, systems, sites, or cloud providers. ([C3](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},133{id: '1.9.2',   section: '1.9',  level: 2, weight: 50,  cwe: 'id295',  nist: nil, milestone: 'Architecture, Design and Threat Modeling Verification Requirements', 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.'},134{id: '2.1.1',   section: '2.1',  level: 1, weight: 25,  cwe: 'id521',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that user set passwords are at least 12 characters in length. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},135{id: '2.1.10',  section: '2.1',  level: 1, weight: 25,  cwe: 'id263',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that there are no periodic credential rotation or password history requirements.'},136{id: '2.1.11',  section: '2.1',  level: 1, weight: 25,  cwe: 'id521',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that "paste" functionality, browser password helpers, and external password managers are permitted.'},137{id: '2.1.12',  section: '2.1',  level: 1, weight: 25,  cwe: 'id521',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', 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.'},138{id: '2.1.2',   section: '2.1',  level: 1, weight: 25,  cwe: 'id521',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that passwords 64 characters or longer are permitted. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},139{id: '2.1.3',   section: '2.1',  level: 1, weight: 25,  cwe: 'id521',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that passwords can contain spaces and truncation is not performed. Consecutive multiple spaces MAY optionally be coalesced. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},140{id: '2.1.4',   section: '2.1',  level: 1, weight: 25,  cwe: 'id521',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', 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.'},141{id: '2.1.5',   section: '2.1',  level: 1, weight: 25,  cwe: 'id620',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', title: 'Verify users can change their password.'},142{id: '2.1.6',   section: '2.1',  level: 1, weight: 25,  cwe: 'id620',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that password change functionality requires the user\'s current and new password.'},143{id: '2.1.7',   section: '2.1',  level: 1, weight: 25,  cwe: 'id521',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', 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. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},144{id: '2.1.8',   section: '2.1',  level: 1, weight: 25,  cwe: 'id521',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that a password strength meter is provided to help users set a stronger password.'},145{id: '2.1.9',   section: '2.1',  level: 1, weight: 25,  cwe: 'id521',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', 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. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},146{id: '2.10.1',  section: '2.10', level: 2, weight: 50,  cwe: 'id287',  nist: ['5.1.1.1'], milestone: 'Authentication Verification Requirements', title: 'Verify that integration secrets do not rely on unchanging passwords, such as API keys or shared privileged accounts.'},147{id: '2.10.2',  section: '2.10', level: 2, weight: 50,  cwe: 'id255',  nist: ['5.1.1.1'], milestone: 'Authentication Verification Requirements', title: 'Verify that if passwords are required, the credentials are not a default account.'},148{id: '2.10.3',  section: '2.10', level: 2, weight: 50,  cwe: 'id522',  nist: ['5.1.1.1'], milestone: 'Authentication Verification Requirements', title: 'Verify that passwords are stored with sufficient protection to prevent offline recovery attacks, including local system access.'},149{id: '2.10.4',  section: '2.10', level: 2, weight: 50,  cwe: 'id798',  nist: nil, milestone: 'Authentication Verification Requirements', 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.'},150{id: '2.2.1',   section: '2.2',  level: 1, weight: 25,  cwe: 'id307',  nist: ['5.2.2', '5.1.1.2', '5.1.4.2', '5.1.5.2'], milestone: 'Authentication Verification Requirements', 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.'},151{id: '2.2.2',   section: '2.2',  level: 1, weight: 25,  cwe: 'id304',  nist: ['5.2.10'], milestone: 'Authentication Verification Requirements', 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.'},152{id: '2.2.3',   section: '2.2',  level: 1, weight: 25,  cwe: 'id620',  nist: nil, milestone: 'Authentication Verification Requirements', 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.'},153{id: '2.2.4',   section: '2.2',  level: 3, weight: 100, cwe: 'id308',  nist: ['5.2.5'], milestone: 'Authentication Verification Requirements', 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.'},154{id: '2.2.5',   section: '2.2',  level: 3, weight: 100, cwe: 'id319',  nist: ['5.2.6'], milestone: 'Authentication Verification Requirements', 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.'},155{id: '2.2.6',   section: '2.2',  level: 3, weight: 100, cwe: 'id308',  nist: ['5.2.8'], milestone: 'Authentication Verification Requirements', title: 'Verify replay resistance through the mandated use of OTP devices, cryptographic authenticators, or lookup codes.'},156{id: '2.2.7',   section: '2.2',  level: 3, weight: 100, cwe: 'id308',  nist: ['5.2.9'], milestone: 'Authentication Verification Requirements', 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.'},157{id: '2.3.1',   section: '2.3',  level: 1, weight: 25,  cwe: 'id330',  nist: ['5.1.1.2', 'A.3'], milestone: 'Authentication Verification Requirements', 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.'},158{id: '2.3.2',   section: '2.3',  level: 2, weight: 50,  cwe: 'id308',  nist: ['6.1.3'], milestone: 'Authentication Verification Requirements', title: 'Verify that enrollment and use of subscriber-provided authentication devices are supported, such as a U2F or FIDO tokens.'},159{id: '2.3.3',   section: '2.3',  level: 2, weight: 50,  cwe: 'id287',  nist: ['6.1.4'], milestone: 'Authentication Verification Requirements', title: 'Verify that renewal instructions are sent with sufficient time to renew time bound authenticators.'},160{id: '2.4.1',   section: '2.4',  level: 2, weight: 50,  cwe: 'id916',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', 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. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},161{id: '2.4.2',   section: '2.4',  level: 2, weight: 50,  cwe: 'id916',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', 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. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},162{id: '2.4.3',   section: '2.4',  level: 2, weight: 50,  cwe: 'id916',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', 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. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},163{id: '2.4.4',   section: '2.4',  level: 2, weight: 50,  cwe: 'id916',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that if bcrypt is used, the work factor SHOULD be as large as verification server performance will allow, typically at least 13. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},164{id: '2.4.5',   section: '2.4',  level: 2, weight: 50,  cwe: 'id916',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', 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).'},165{id: '2.5.1',   section: '2.5',  level: 1, weight: 25,  cwe: 'id640',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that a system generated initial activation or recovery secret is not sent in clear text to the user. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},166{id: '2.5.2',   section: '2.5',  level: 1, weight: 25,  cwe: 'id640',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', title: 'Verify password hints or knowledge-based authentication (so-called "secret questions") are not present.'},167{id: '2.5.3',   section: '2.5',  level: 1, weight: 25,  cwe: 'id640',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', title: 'Verify password credential recovery does not reveal the current password in any way. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},168{id: '2.5.4',   section: '2.5',  level: 1, weight: 25,  cwe: 'id16',   nist: ['5.1.1.2', 'A.3'], milestone: 'Authentication Verification Requirements', title: 'Verify shared or default accounts are not present (e.g. "root", "admin", or "sa").'},169{id: '2.5.5',   section: '2.5',  level: 1, weight: 25,  cwe: 'id304',  nist: ['6.1.2.3'], milestone: 'Authentication Verification Requirements', title: 'Verify that if an authentication factor is changed or replaced, that the user is notified of this event.'},170{id: '2.5.6',   section: '2.5',  level: 1, weight: 25,  cwe: 'id640',  nist: ['5.1.1.2'], milestone: 'Authentication Verification Requirements', 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. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},171{id: '2.5.7',   section: '2.5',  level: 2, weight: 50,  cwe: 'id308',  nist: ['6.1.2.3'], milestone: 'Authentication Verification Requirements', 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.'},172{id: '2.6.1',   section: '2.6',  level: 2, weight: 50,  cwe: 'id308',  nist: ['5.1.2.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that lookup secrets can be used only once.'},173{id: '2.6.2',   section: '2.6',  level: 2, weight: 50,  cwe: 'id330',  nist: ['5.1.2.2'], milestone: 'Authentication Verification Requirements', 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.'},174{id: '2.6.3',   section: '2.6',  level: 2, weight: 50,  cwe: 'id310',  nist: ['5.1.2.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that lookup secrets are resistant to offline attacks, such as predictable values.'},175{id: '2.7.1',   section: '2.7',  level: 1, weight: 25,  cwe: 'id287',  nist: ['5.1.3.2'], milestone: 'Authentication Verification Requirements', 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.'},176{id: '2.7.2',   section: '2.7',  level: 1, weight: 25,  cwe: 'id287',  nist: ['5.1.3.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that the out of band verifier expires out of band authentication requests, codes, or tokens after 10 minutes.'},177{id: '2.7.3',   section: '2.7',  level: 1, weight: 25,  cwe: 'id287',  nist: ['5.1.3.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that the out of band verifier authentication requests, codes, or tokens are only usable once, and only for the original authentication request.'},178{id: '2.7.4',   section: '2.7',  level: 1, weight: 25,  cwe: 'id523',  nist: ['5.1.3.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that the out of band authenticator and verifier communicates over a secure independent channel.'},179{id: '2.7.5',   section: '2.7',  level: 2, weight: 50,  cwe: 'id256',  nist: ['5.1.3.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that the out of band verifier retains only a hashed version of the authentication code.'},180{id: '2.7.6',   section: '2.7',  level: 2, weight: 50,  cwe: 'id310',  nist: ['5.1.3.2'], milestone: 'Authentication Verification Requirements', 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).'},181{id: '2.8.1',   section: '2.8',  level: 1, weight: 25,  cwe: 'id613',  nist: ['5.1.4.2', '5.1.5.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that time-based OTPs have a defined lifetime before expiring.'},182{id: '2.8.2',   section: '2.8',  level: 2, weight: 50,  cwe: 'id320',  nist: ['5.1.4.2', '5.1.5.2'], milestone: 'Authentication Verification Requirements', 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.'},183{id: '2.8.3',   section: '2.8',  level: 2, weight: 50,  cwe: 'id326',  nist: ['5.1.4.2', '5.1.5.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that approved cryptographic algorithms are used in the generation, seeding, and verification.'},184{id: '2.8.4',   section: '2.8',  level: 2, weight: 50,  cwe: 'id287',  nist: ['5.1.4.2', '5.1.5.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that time-based OTP can be used only once within the validity period.'},185{id: '2.8.5',   section: '2.8',  level: 2, weight: 50,  cwe: 'id287',  nist: ['5.1.5.2'], milestone: 'Authentication Verification Requirements', 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.'},186{id: '2.8.6',   section: '2.8',  level: 2, weight: 50,  cwe: 'id613',  nist: ['5.2.1'], milestone: 'Authentication Verification Requirements', 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.'},187{id: '2.8.7',   section: '2.8',  level: 3, weight: 100, cwe: 'id308',  nist: ['5.2.3'], milestone: 'Authentication Verification Requirements', title: 'Verify that biometric authenticators are limited to use only as secondary factors in conjunction with either something you have and something you know.'},188{id: '2.9.1',   section: '2.9',  level: 2, weight: 50,  cwe: 'id320',  nist: ['5.1.7.2'], milestone: 'Authentication Verification Requirements', 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.'},189{id: '2.9.2',   section: '2.9',  level: 2, weight: 50,  cwe: 'id330',  nist: ['5.1.7.2'], milestone: 'Authentication Verification Requirements', 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.'},190{id: '2.9.3',   section: '2.9',  level: 2, weight: 50,  cwe: 'id327',  nist: ['5.1.7.2'], milestone: 'Authentication Verification Requirements', title: 'Verify that approved cryptographic algorithms are used in the generation, seeding, and verification.'},191{id: '3.1.1',   section: '3.1',  level: 1, weight: 25,  cwe: 'id598',  nist: nil, milestone: 'Session Management Verification Requirements', title: 'Verify the application never reveals session tokens in URL parameters or error messages.'},192{id: '3.2.1',   section: '3.2',  level: 1, weight: 25,  cwe: 'id384',  nist: ['7.1'], milestone: 'Session Management Verification Requirements', title: 'Verify the application generates a new session token on user authentication. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},193{id: '3.2.2',   section: '3.2',  level: 1, weight: 25,  cwe: 'id331',  nist: ['7.1'], milestone: 'Session Management Verification Requirements', title: 'Verify that session tokens possess at least 64 bits of entropy. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},194{id: '3.2.3',   section: '3.2',  level: 1, weight: 25,  cwe: 'id539',  nist: ['7.1'], milestone: 'Session Management Verification Requirements', 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.'},195{id: '3.2.4',   section: '3.2',  level: 2, weight: 50,  cwe: 'id331',  nist: ['7.1'], milestone: 'Session Management Verification Requirements', title: 'Verify that session token are generated using approved cryptographic algorithms. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},196{id: '3.3.1',   section: '3.3',  level: 1, weight: 25,  cwe: 'id613',  nist: ['7.1'], milestone: 'Session Management Verification Requirements', 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. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},197{id: '3.3.2',   section: '3.3',  level: 1, weight: 25,  cwe: 'id613',  nist: ['7.2'], milestone: 'Session Management Verification Requirements', title: 'If authenticators permit users to remain logged in, verify that re-authentication occurs periodically both when actively used or after an idle period. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},198{id: '3.3.3',   section: '3.3',  level: 2, weight: 50,  cwe: 'id613',  nist: nil, milestone: 'Session Management Verification Requirements', 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.'},199{id: '3.3.4',   section: '3.3',  level: 2, weight: 50,  cwe: 'id613',  nist: ['7.1'], milestone: 'Session Management Verification Requirements', title: 'Verify that users are able to view and log out of any or all currently active sessions and devices.'},200{id: '3.4.1',   section: '3.4',  level: 1, weight: 25,  cwe: 'id614',  nist: ['7.1.1'], milestone: 'Session Management Verification Requirements', title: 'Verify that cookie-based session tokens have the \'Secure\' attribute set. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},201{id: '3.4.2',   section: '3.4',  level: 1, weight: 25,  cwe: 'id1004', nist: ['7.1.1'], milestone: 'Session Management Verification Requirements', title: 'Verify that cookie-based session tokens have the \'HttpOnly\' attribute set. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},202{id: '3.4.3',   section: '3.4',  level: 1, weight: 25,  cwe: 'id16',   nist: ['7.1.1'], milestone: 'Session Management Verification Requirements', title: 'Verify that cookie-based session tokens utilize the \'SameSite\' attribute to limit exposure to cross-site request forgery attacks. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},203{id: '3.4.4',   section: '3.4',  level: 1, weight: 25,  cwe: 'id16',   nist: ['7.1.1'], milestone: 'Session Management Verification Requirements', title: 'Verify that cookie-based session tokens use "__Host-" prefix (see references) to provide session cookie confidentiality.'},204{id: '3.4.5',   section: '3.4',  level: 1, weight: 25,  cwe: 'id16',   nist: ['7.1.1'], milestone: 'Session Management Verification Requirements', 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. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},205{id: '3.5.1',   section: '3.5',  level: 2, weight: 50,  cwe: 'id290',  nist: ['7.1.2'], milestone: 'Session Management Verification Requirements', 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.'},206{id: '3.5.2',   section: '3.5',  level: 2, weight: 50,  cwe: 'id798',  nist: nil, milestone: 'Session Management Verification Requirements', title: 'Verify the application uses session tokens rather than static API secrets and keys, except with legacy implementations.'},207{id: '3.5.3',   section: '3.5',  level: 2, weight: 50,  cwe: 'id345',  nist: nil, milestone: 'Session Management Verification Requirements', 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.'},208{id: '3.6.1',   section: '3.6',  level: 3, weight: 100, cwe: 'id613',  nist: ['7.2.1'], milestone: 'Session Management Verification Requirements', 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.'},209{id: '3.6.2',   section: '3.6',  level: 3, weight: 100, cwe: 'id613',  nist: ['7.2.1'], milestone: 'Session Management Verification Requirements', 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.'},210{id: '3.7.1',   section: '3.7',  level: 1, weight: 25,  cwe: 'id778',  nist: nil, milestone: 'Session Management Verification Requirements', title: 'Verify the application ensures a valid login session or requires re-authentication or secondary verification before allowing any sensitive transactions or account modifications.'},211{id: '4.1.1',   section: '4.1',  level: 1, weight: 25,  cwe: 'id602',  nist: nil, milestone: 'Access Control Verification Requirements', 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.'},212{id: '4.1.2',   section: '4.1',  level: 1, weight: 25,  cwe: 'id639',  nist: nil, milestone: 'Access Control Verification Requirements', title: 'Verify that all user and data attributes and policy information used by access controls cannot be manipulated by end users unless specifically authorized.'},213{id: '4.1.3',   section: '4.1',  level: 1, weight: 25,  cwe: 'id285',  nist: nil, milestone: 'Access Control Verification Requirements', 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. ([C7](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},214{id: '4.1.4',   section: '4.1',  level: 1, weight: 25,  cwe: 'id276',  nist: nil, milestone: 'Access Control Verification Requirements', 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.  ([C7](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},215{id: '4.1.5',   section: '4.1',  level: 1, weight: 25,  cwe: 'id285',  nist: nil, milestone: 'Access Control Verification Requirements', title: 'Verify that access controls fail securely including when an exception occurs. ([C10](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},216{id: '4.2.1',   section: '4.2',  level: 1, weight: 25,  cwe: 'id639',  nist: nil, milestone: 'Access Control Verification Requirements', 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.'},217{id: '4.2.2',   section: '4.2',  level: 1, weight: 25,  cwe: 'id352',  nist: nil, milestone: 'Access Control Verification Requirements', 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.'},218{id: '4.3.1',   section: '4.3',  level: 1, weight: 25,  cwe: 'id419',  nist: nil, milestone: 'Access Control Verification Requirements', title: 'Verify administrative interfaces use appropriate multi-factor authentication to prevent unauthorized use.'},219{id: '4.3.2',   section: '4.3',  level: 1, weight: 25,  cwe: 'id548',  nist: nil, milestone: 'Access Control Verification Requirements', 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.'},220{id: '4.3.3',   section: '4.3',  level: 2, weight: 50,  cwe: 'id732',  nist: nil, milestone: 'Access Control Verification Requirements', 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.'},221{id: '5.1.1',   section: '5.1',  level: 1, weight: 25,  cwe: 'id235',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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).'},222{id: '5.1.2',   section: '5.1',  level: 1, weight: 25,  cwe: 'id915',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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. ([C5](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},223{id: '5.1.3',   section: '5.1',  level: 1, weight: 25,  cwe: 'id20',   nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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). ([C5](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},224{id: '5.1.4',   section: '5.1',  level: 1, weight: 25,  cwe: 'id20',   nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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). ([C5](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},225{id: '5.1.5',   section: '5.1',  level: 1, weight: 25,  cwe: 'id601',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', title: 'Verify that URL redirects and forwards only allow whitelisted destinations, or show a warning when redirecting to potentially untrusted content.'},226{id: '5.2.1',   section: '5.2',  level: 1, weight: 25,  cwe: 'id116',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', title: 'Verify that all untrusted HTML input from WYSIWYG editors or similar is properly sanitized with an HTML sanitizer library or framework feature. ([C5](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},227{id: '5.2.2',   section: '5.2',  level: 1, weight: 25,  cwe: 'id138',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', title: 'Verify that unstructured data is sanitized to enforce safety measures such as allowed characters and length.'},228{id: '5.2.3',   section: '5.2',  level: 1, weight: 25,  cwe: 'id147',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', title: 'Verify that the application sanitizes user input before passing to mail systems to protect against SMTP or IMAP injection.'},229{id: '5.2.4',   section: '5.2',  level: 1, weight: 25,  cwe: 'id95',   nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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.'},230{id: '5.2.5',   section: '5.2',  level: 1, weight: 25,  cwe: 'id94',   nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', title: 'Verify that the application protects against template injection attacks by ensuring that any user input being included is sanitized or sandboxed.'},231{id: '5.2.6',   section: '5.2',  level: 1, weight: 25,  cwe: 'id918',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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.'},232{id: '5.2.7',   section: '5.2',  level: 1, weight: 25,  cwe: 'id159',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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.'},233{id: '5.2.8',   section: '5.2',  level: 1, weight: 25,  cwe: 'id94',   nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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.'},234{id: '5.3.1',   section: '5.3',  level: 1, weight: 25,  cwe: 'id116',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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). ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},235{id: '5.3.10',  section: '5.3',  level: 1, weight: 25,  cwe: 'id643',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', title: 'Verify that the application protects against XPath injection or XML injection attacks. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},236{id: '5.3.2',   section: '5.3',  level: 1, weight: 25,  cwe: 'id176',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},237{id: '5.3.3',   section: '5.3',  level: 1, weight: 25,  cwe: 'id79',   nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', title: 'Verify that context-aware, preferably automated - or at worst, manual - output escaping protects against reflected, stored, and DOM based XSS. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},238{id: '5.3.4',   section: '5.3',  level: 1, weight: 25,  cwe: 'id89',   nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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. ([C3](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},239{id: '5.3.5',   section: '5.3',  level: 1, weight: 25,  cwe: 'id89',   nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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. ([C3, C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},240{id: '5.3.6',   section: '5.3',  level: 1, weight: 25,  cwe: 'id830',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},241{id: '5.3.7',   section: '5.3',  level: 1, weight: 25,  cwe: 'id943',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', title: 'Verify that the application protects against LDAP Injection vulnerabilities, or that specific security controls to prevent LDAP Injection have been implemented. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},242{id: '5.3.8',   section: '5.3',  level: 1, weight: 25,  cwe: 'id78',   nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},243{id: '5.3.9',   section: '5.3',  level: 1, weight: 25,  cwe: 'id829',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', title: 'Verify that the application protects against Local File Inclusion (LFI) or Remote File Inclusion (RFI) attacks.'},244{id: '5.4.1',   section: '5.4',  level: 2, weight: 50,  cwe: 'id120',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', title: 'Verify that the application uses memory-safe string, safer memory copy and pointer arithmetic to detect or prevent stack, buffer, or heap overflows.'},245{id: '5.4.2',   section: '5.4',  level: 2, weight: 50,  cwe: 'id134',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', title: 'Verify that format strings do not take potentially hostile input, and are constant.'},246{id: '5.4.3',   section: '5.4',  level: 2, weight: 50,  cwe: 'id190',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', title: 'Verify that sign, range, and input validation techniques are used to prevent integer overflows.'},247{id: '5.5.1',   section: '5.5',  level: 1, weight: 25,  cwe: 'id502',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', title: 'Verify that serialized objects use integrity checks or are encrypted to prevent hostile object creation or data tampering. ([C5](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},248{id: '5.5.2',   section: '5.5',  level: 1, weight: 25,  cwe: 'id611',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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.'},249{id: '5.5.3',   section: '5.5',  level: 1, weight: 25,  cwe: 'id502',  nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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).'},250{id: '5.5.4',   section: '5.5',  level: 1, weight: 25,  cwe: 'id95',   nist: nil, milestone: 'Validation, Sanitization and Encoding Verification Requirements', 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.'},251{id: '6.1.1',   section: '6.1',  level: 2, weight: 50,  cwe: 'id311',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', 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.'},252{id: '6.1.2',   section: '6.1',  level: 2, weight: 50,  cwe: 'id311',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', title: 'Verify that regulated health data is stored encrypted while at rest, such as medical records, medical device details, or de-anonymized research records.'},253{id: '6.1.3',   section: '6.1',  level: 2, weight: 50,  cwe: 'id311',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', 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.'},254{id: '6.2.1',   section: '6.2',  level: 1, weight: 25,  cwe: 'id310',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', title: 'Verify that all cryptographic modules fail securely, and errors are handled in a way that does not enable Padding Oracle attacks.'},255{id: '6.2.2',   section: '6.2',  level: 2, weight: 50,  cwe: 'id327',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', title: 'Verify that industry proven or government approved cryptographic algorithms, modes, and libraries are used, instead of custom coded cryptography. ([C8](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},256{id: '6.2.3',   section: '6.2',  level: 2, weight: 50,  cwe: 'id326',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', title: 'Verify that encryption initialization vector, cipher configuration, and block modes are configured securely using the latest advice.'},257{id: '6.2.4',   section: '6.2',  level: 2, weight: 50,  cwe: 'id326',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', 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. ([C8](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},258{id: '6.2.5',   section: '6.2',  level: 2, weight: 50,  cwe: 'id326',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', 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.'},259{id: '6.2.6',   section: '6.2',  level: 2, weight: 50,  cwe: 'id326',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', 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.'},260{id: '6.2.7',   section: '6.2',  level: 3, weight: 100, cwe: 'id326',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', 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.'},261{id: '6.2.8',   section: '6.2',  level: 3, weight: 100, cwe: 'id385',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', title: 'Verify that all cryptographic operations are constant-time, with no \'short-circuit\' operations in comparisons, calculations, or returns, to avoid leaking information.'},262{id: '6.3.1',   section: '6.3',  level: 2, weight: 50,  cwe: 'id338',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', 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.'},263{id: '6.3.2',   section: '6.3',  level: 2, weight: 50,  cwe: 'id338',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', 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.'},264{id: '6.3.3',   section: '6.3',  level: 3, weight: 100, cwe: 'id338',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', 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.'},265{id: '6.4.1',   section: '6.4',  level: 2, weight: 50,  cwe: 'id798',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', title: 'Verify that a secrets management solution such as a key vault is used to securely create, store, control access to and destroy secrets. ([C8](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},266{id: '6.4.2',   section: '6.4',  level: 2, weight: 50,  cwe: 'id320',  nist: nil, milestone: 'Stored Cryptography Verification Requirements', title: 'Verify that key material is not exposed to the application but instead uses an isolated security module like a vault for cryptographic operations. ([C8](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},267{id: '7.1.1',   section: '7.1',  level: 1, weight: 25,  cwe: 'id532',  nist: nil, milestone: 'Error Handling and Logging Verification Requirements', 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. ([C9, C10](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},268{id: '7.1.2',   section: '7.1',  level: 1, weight: 25,  cwe: 'id532',  nist: nil, milestone: 'Error Handling and Logging Verification Requirements', title: 'Verify that the application does not log other sensitive data as defined under local privacy laws or relevant security policy. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},269{id: '7.1.3',   section: '7.1',  level: 2, weight: 50,  cwe: 'id778',  nist: nil, milestone: 'Error Handling and Logging Verification Requirements', title: 'Verify that the application logs security relevant events including successful and failed authentication events, access control failures, deserialization failures and input validation failures. ([C5, C7](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},270{id: '7.1.4',   section: '7.1',  level: 2, weight: 50,  cwe: 'id778',  nist: nil, milestone: 'Error Handling and Logging Verification Requirements', title: 'Verify that each log event includes necessary information that would allow for a detailed investigation of the timeline when an event happens. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},271{id: '7.2.1',   section: '7.2',  level: 2, weight: 50,  cwe: 'id778',  nist: nil, milestone: 'Error Handling and Logging Verification Requirements', 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.'},272{id: '7.2.2',   section: '7.2',  level: 2, weight: 50,  cwe: 'id285',  nist: nil, milestone: 'Error Handling and Logging Verification Requirements', 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.'},273{id: '7.3.1',   section: '7.3',  level: 2, weight: 50,  cwe: 'id117',  nist: nil, milestone: 'Error Handling and Logging Verification Requirements', title: 'Verify that the application appropriately encodes user-supplied data to prevent log injection. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},274{id: '7.3.2',   section: '7.3',  level: 2, weight: 50,  cwe: 'id117',  nist: nil, milestone: 'Error Handling and Logging Verification Requirements', title: 'Verify that all events are protected from injection when viewed in log viewing software. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},275{id: '7.3.3',   section: '7.3',  level: 2, weight: 50,  cwe: 'id200',  nist: nil, milestone: 'Error Handling and Logging Verification Requirements', title: 'Verify that security logs are protected from unauthorized access and modification. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},276{id: '7.3.4',   section: '7.3',  level: 2, weight: 50,  cwe: '-1', nist: nil, milestone: 'Error Handling and Logging Verification Requirements', 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. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},277{id: '7.4.1',   section: '7.4',  level: 1, weight: 25,  cwe: 'id210',  nist: nil, milestone: 'Error Handling and Logging Verification Requirements', 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.  ([C10](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},278{id: '7.4.2',   section: '7.4',  level: 2, weight: 50,  cwe: 'id544',  nist: nil, milestone: 'Error Handling and Logging Verification Requirements', title: 'Verify that exception handling (or a functional equivalent) is used across the codebase to account for expected and unexpected error conditions. ([C10](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},279{id: '7.4.3',   section: '7.4',  level: 2, weight: 50,  cwe: 'id460',  nist: nil, milestone: 'Error Handling and Logging Verification Requirements', title: 'Verify that a "last resort" error handler is defined which will catch all unhandled exceptions. ([C10](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},280{id: '8.1.1',   section: '8.1',  level: 2, weight: 50,  cwe: 'id524',  nist: nil, milestone: 'Data Protection Verification Requirements', title: 'Verify the application protects sensitive data from being cached in server components such as load balancers and application caches.'},281{id: '8.1.2',   section: '8.1',  level: 2, weight: 50,  cwe: 'id524',  nist: nil, milestone: 'Data Protection Verification Requirements', 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.'},282{id: '8.1.3',   section: '8.1',  level: 2, weight: 50,  cwe: 'id233',  nist: nil, milestone: 'Data Protection Verification Requirements', title: 'Verify the application minimizes the number of parameters in a request, such as hidden fields, Ajax variables, cookies and header values.'},283{id: '8.1.4',   section: '8.1',  level: 2, weight: 50,  cwe: 'id770',  nist: nil, milestone: 'Data Protection Verification Requirements', 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.'},284{id: '8.1.5',   section: '8.1',  level: 3, weight: 100, cwe: 'id19',   nist: nil, milestone: 'Data Protection Verification Requirements', title: 'Verify that regular backups of important data are performed and that test restoration of data is performed.'},285{id: '8.1.6',   section: '8.1',  level: 3, weight: 100, cwe: 'id19',   nist: nil, milestone: 'Data Protection Verification Requirements', title: 'Verify that backups are stored securely to prevent data from being stolen or corrupted.'},286{id: '8.2.1',   section: '8.2',  level: 1, weight: 25,  cwe: 'id525',  nist: nil, milestone: 'Data Protection Verification Requirements', title: 'Verify the application sets sufficient anti-caching headers so that sensitive data is not cached in modern browsers.'},287{id: '8.2.2',   section: '8.2',  level: 1, weight: 25,  cwe: 'id922',  nist: nil, milestone: 'Data Protection Verification Requirements', 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.'},288{id: '8.2.3',   section: '8.2',  level: 1, weight: 25,  cwe: 'id922',  nist: nil, milestone: 'Data Protection Verification Requirements', title: 'Verify that authenticated data is cleared from client storage, such as the browser DOM, after the client or session is terminated.'},289{id: '8.3.1',   section: '8.3',  level: 1, weight: 25,  cwe: 'id319',  nist: nil, milestone: 'Data Protection Verification Requirements', 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.'},290{id: '8.3.2',   section: '8.3',  level: 1, weight: 25,  cwe: 'id212',  nist: nil, milestone: 'Data Protection Verification Requirements', title: 'Verify that users have a method to remove or export their data on demand.'},291{id: '8.3.3',   section: '8.3',  level: 1, weight: 25,  cwe: 'id285',  nist: nil, milestone: 'Data Protection Verification Requirements', 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.'},292{id: '8.3.4',   section: '8.3',  level: 1, weight: 25,  cwe: 'id200',  nist: nil, milestone: 'Data Protection Verification Requirements', 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. ([C8](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},293{id: '8.3.5',   section: '8.3',  level: 2, weight: 50,  cwe: 'id532',  nist: nil, milestone: 'Data Protection Verification Requirements', 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.'},294{id: '8.3.6',   section: '8.3',  level: 2, weight: 50,  cwe: 'id226',  nist: nil, milestone: 'Data Protection Verification Requirements', 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.'},295{id: '8.3.7',   section: '8.3',  level: 2, weight: 50,  cwe: 'id327',  nist: nil, milestone: 'Data Protection Verification Requirements', title: 'Verify that sensitive or private information that is required to be encrypted, is encrypted using approved algorithms that provide both confidentiality and integrity. ([C8](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},296{id: '8.3.8',   section: '8.3',  level: 2, weight: 50,  cwe: 'id285',  nist: nil, milestone: 'Data Protection Verification Requirements', 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.'},297{id: '9.1.1',   section: '9.1',  level: 1, weight: 25,  cwe: 'id319',  nist: nil, milestone: 'Communications Verification Requirements', title: 'Verify that secured TLS is used for all client connectivity, and does not fall back to insecure or unencrypted protocols. ([C8](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},298{id: '9.1.2',   section: '9.1',  level: 1, weight: 25,  cwe: 'id326',  nist: nil, milestone: 'Communications Verification Requirements', 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.'},299{id: '9.1.3',   section: '9.1',  level: 1, weight: 25,  cwe: 'id326',  nist: nil, milestone: 'Communications Verification Requirements', 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.'},300{id: '9.2.1',   section: '9.2',  level: 2, weight: 50,  cwe: 'id295',  nist: nil, milestone: 'Communications Verification Requirements', 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.'},301{id: '9.2.2',   section: '9.2',  level: 2, weight: 50,  cwe: 'id319',  nist: nil, milestone: 'Communications Verification Requirements', 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.'},302{id: '9.2.3',   section: '9.2',  level: 2, weight: 50,  cwe: 'id287',  nist: nil, milestone: 'Communications Verification Requirements', title: 'Verify that all encrypted connections to external systems that involve sensitive information or functions are authenticated.'},303{id: '9.2.4',   section: '9.2',  level: 2, weight: 50,  cwe: 'id299',  nist: nil, milestone: 'Communications Verification Requirements', title: 'Verify that proper certification revocation, such as Online Certificate Status Protocol (OCSP) Stapling, is enabled and configured.'},304{id: '9.2.5',   section: '9.2',  level: 3, weight: 100, cwe: 'id544',  nist: nil, milestone: 'Communications Verification Requirements', title: 'Verify that backend TLS connection failures are logged.'},305{id: '10.1.1',  section: '10.1', level: 3, weight: 100, cwe: 'id749',  nist: nil, milestone: 'Malicious Code Verification Requirements', 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.'},306{id: '10.2.1',  section: '10.2', level: 2, weight: 50,  cwe: 'id359',  nist: nil, milestone: 'Malicious Code Verification Requirements', 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.'},307{id: '10.2.2',  section: '10.2', level: 2, weight: 50,  cwe: 'id272',  nist: nil, milestone: 'Malicious Code Verification Requirements', 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.'},308{id: '10.2.3',  section: '10.2', level: 3, weight: 100, cwe: 'id507',  nist: nil, milestone: 'Malicious Code Verification Requirements', 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.'},309{id: '10.2.4',  section: '10.2', level: 3, weight: 100, cwe: 'id511',  nist: nil, milestone: 'Malicious Code Verification Requirements', title: 'Verify that the application source code and third party libraries does not contain time bombs by searching for date and time related functions.'},310{id: '10.2.5',  section: '10.2', level: 3, weight: 100, cwe: 'id511',  nist: nil, milestone: 'Malicious Code Verification Requirements', 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.'},311{id: '10.2.6',  section: '10.2', level: 3, weight: 100, cwe: 'id507',  nist: nil, milestone: 'Malicious Code Verification Requirements', title: 'Verify that the application source code and third party libraries do not contain Easter eggs or any other potentially unwanted functionality.'},312{id: '10.3.1',  section: '10.3', level: 1, weight: 25,  cwe: 'id16',   nist: nil, milestone: 'Malicious Code Verification Requirements', 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.'},313{id: '10.3.2',  section: '10.3', level: 1, weight: 25,  cwe: 'id353',  nist: nil, milestone: 'Malicious Code Verification Requirements', 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.'},314{id: '10.3.3',  section: '10.3', level: 1, weight: 25,  cwe: 'id350',  nist: nil, milestone: 'Malicious Code Verification Requirements', 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.'},315{id: '11.1.1',  section: '11.1', level: 1, weight: 25,  cwe: 'id841',  nist: nil, milestone: 'Business Logic Verification Requirements', title: 'Verify the application will only process business logic flows for the same user in sequential step order and without skipping steps.'},316{id: '11.1.2',  section: '11.1', level: 1, weight: 25,  cwe: 'id779',  nist: nil, milestone: 'Business Logic Verification Requirements', 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.'},317{id: '11.1.3',  section: '11.1', level: 1, weight: 25,  cwe: 'id770',  nist: nil, milestone: 'Business Logic Verification Requirements', title: 'Verify the application has appropriate limits for specific business actions or transactions which are correctly enforced on a per user basis.'},318{id: '11.1.4',  section: '11.1', level: 1, weight: 25,  cwe: 'id770',  nist: nil, milestone: 'Business Logic Verification Requirements', 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.'},319{id: '11.1.5',  section: '11.1', level: 1, weight: 25,  cwe: 'id841',  nist: nil, milestone: 'Business Logic Verification Requirements', 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.'},320{id: '11.1.6',  section: '11.1', level: 2, weight: 50,  cwe: 'id367',  nist: nil, milestone: 'Business Logic Verification Requirements', title: 'Verify the application does not suffer from "time of check to time of use" (TOCTOU) issues or other race conditions for sensitive operations.'},321{id: '11.1.7',  section: '11.1', level: 2, weight: 50,  cwe: 'id754',  nist: nil, milestone: 'Business Logic Verification Requirements', 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. ([C9](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},322{id: '11.1.8',  section: '11.1', level: 2, weight: 50,  cwe: 'id390',  nist: nil, milestone: 'Business Logic Verification Requirements', title: 'Verify the application has configurable alerting when automated attacks or unusual activity is detected.'},323{id: '12.1.1',  section: '12.1', level: 1, weight: 25,  cwe: 'id400',  nist: nil, milestone: 'Files and Resources Verification Requirements', title: 'Verify that the application will not accept large files that could fill up storage or cause a denial of service attack.'},324{id: '12.1.2',  section: '12.1', level: 2, weight: 50,  cwe: 'id409',  nist: nil, milestone: 'Files and Resources Verification Requirements', title: 'Verify that compressed files are checked for "zip bombs" - small input files that will decompress into huge files thus exhausting file storage limits.'},325{id: '12.1.3',  section: '12.1', level: 2, weight: 50,  cwe: 'id770',  nist: nil, milestone: 'Files and Resources Verification Requirements', 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.'},326{id: '12.2.1',  section: '12.2', level: 2, weight: 50,  cwe: 'id434',  nist: nil, milestone: 'Files and Resources Verification Requirements', title: 'Verify that files obtained from untrusted sources are validated to be of expected type based on the file\'s content.'},327{id: '12.3.1',  section: '12.3', level: 1, weight: 25,  cwe: 'id22',   nist: nil, milestone: 'Files and Resources Verification Requirements', title: 'Verify that user-submitted filename metadata is not used directly with system or framework file and URL API to protect against path traversal.'},328{id: '12.3.2',  section: '12.3', level: 1, weight: 25,  cwe: 'id73',   nist: nil, milestone: 'Files and Resources Verification Requirements', title: 'Verify that user-submitted filename metadata is validated or ignored to prevent the disclosure, creation, updating or removal of local files (LFI).'},329{id: '12.3.3',  section: '12.3', level: 1, weight: 25,  cwe: 'id98',   nist: nil, milestone: 'Files and Resources Verification Requirements', 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.'},330{id: '12.3.4',  section: '12.3', level: 1, weight: 25,  cwe: 'id641',  nist: nil, milestone: 'Files and Resources Verification Requirements', 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.'},331{id: '12.3.5',  section: '12.3', level: 1, weight: 25,  cwe: 'id78',   nist: nil, milestone: 'Files and Resources Verification Requirements', title: 'Verify that untrusted file metadata is not used directly with system API or libraries, to protect against OS command injection.'},332{id: '12.3.6',  section: '12.3', level: 2, weight: 50,  cwe: 'id829',  nist: nil, milestone: 'Files and Resources Verification Requirements', 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.'},333{id: '12.4.1',  section: '12.4', level: 1, weight: 25,  cwe: 'id922',  nist: nil, milestone: 'Files and Resources Verification Requirements', title: 'Verify that files obtained from untrusted sources are stored outside the web root, with limited permissions, preferably with strong validation.'},334{id: '12.4.2',  section: '12.4', level: 1, weight: 25,  cwe: 'id509',  nist: nil, milestone: 'Files and Resources Verification Requirements', title: 'Verify that files obtained from untrusted sources are scanned by antivirus scanners to prevent upload of known malicious content.'},335{id: '12.5.1',  section: '12.5', level: 1, weight: 25,  cwe: 'id552',  nist: nil, milestone: 'Files and Resources Verification Requirements', 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.'},336{id: '12.5.2',  section: '12.5', level: 1, weight: 25,  cwe: 'id434',  nist: nil, milestone: 'Files and Resources Verification Requirements', title: 'Verify that direct requests to uploaded files will never be executed as HTML/JavaScript content.'},337{id: '12.6.1',  section: '12.6', level: 1, weight: 25,  cwe: 'id918',  nist: nil, milestone: 'Files and Resources Verification Requirements', 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.'},338{id: '13.1.1',  section: '13.1', level: 1, weight: 25,  cwe: 'id116',  nist: nil, milestone: 'API and Web Service Verification Requirements', 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.'},339{id: '13.1.2',  section: '13.1', level: 1, weight: 25,  cwe: 'id419',  nist: nil, milestone: 'API and Web Service Verification Requirements', title: 'Verify that access to administration and management functions is limited to authorized administrators.'},340{id: '13.1.3',  section: '13.1', level: 1, weight: 25,  cwe: 'id598',  nist: nil, milestone: 'API and Web Service Verification Requirements', title: 'Verify API URLs do not expose sensitive information, such as the API key, session tokens etc.'},341{id: '13.1.4',  section: '13.1', level: 2, weight: 50,  cwe: 'id285',  nist: nil, milestone: 'API and Web Service Verification Requirements', 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.'},342{id: '13.1.5',  section: '13.1', level: 2, weight: 50,  cwe: 'id434',  nist: nil, milestone: 'API and Web Service Verification Requirements', 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).'},343{id: '13.2.1',  section: '13.2', level: 1, weight: 25,  cwe: 'id650',  nist: nil, milestone: 'API and Web Service Verification Requirements', 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.'},344{id: '13.2.2',  section: '13.2', level: 1, weight: 25,  cwe: 'id20',   nist: nil, milestone: 'API and Web Service Verification Requirements', title: 'Verify that JSON schema validation is in place and verified before accepting input.'},345{id: '13.2.3',  section: '13.2', level: 1, weight: 25,  cwe: 'id352',  nist: nil, milestone: 'API and Web Service Verification Requirements', 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 (see [references](https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)_Prevention_Cheat_Sheet)), CSRF nonces, or ORIGIN request header checks.'},346{id: '13.2.4',  section: '13.2', level: 2, weight: 50,  cwe: 'id779',  nist: nil, milestone: 'API and Web Service Verification Requirements', title: 'Verify that REST services have anti-automation controls to protect against excessive calls, especially if the API is unauthenticated.'},347{id: '13.2.5',  section: '13.2', level: 2, weight: 50,  cwe: 'id436',  nist: nil, milestone: 'API and Web Service Verification Requirements', title: 'Verify that REST services explicitly check the incoming Content-Type to be the expected one, such as application/xml or application/JSON.'},348{id: '13.2.6',  section: '13.2', level: 2, weight: 50,  cwe: 'id345',  nist: nil, milestone: 'API and Web Service Verification Requirements', 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.'},349{id: '13.3.1',  section: '13.3', level: 1, weight: 25,  cwe: 'id20',   nist: nil, milestone: 'API and Web Service Verification Requirements', 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.'},350{id: '13.3.2',  section: '13.3', level: 2, weight: 50,  cwe: 'id345',  nist: nil, milestone: 'API and Web Service Verification Requirements', title: 'Verify that the message payload is signed using WS-Security to ensure reliable transport between client and service.'},351{id: '13.4.1',  section: '13.4', level: 2, weight: 50,  cwe: 'id770',  nist: nil, milestone: 'API and Web Service Verification Requirements', 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.'},352{id: '13.4.2',  section: '13.4', level: 2, weight: 50,  cwe: 'id285',  nist: nil, milestone: 'API and Web Service Verification Requirements', title: 'Verify that GraphQL or other data layer authorization logic should be implemented at the business logic layer instead of the GraphQL layer.'},353{id: '14.1.1',  section: '14.1', level: 2, weight: 50,  cwe: '-1', nist: nil, milestone: 'Configuration Verification Requirements', 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.'},354{id: '14.1.2',  section: '14.1', level: 2, weight: 50,  cwe: 'id120',  nist: nil, milestone: 'Configuration Verification Requirements', 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.'},355{id: '14.1.3',  section: '14.1', level: 2, weight: 50,  cwe: 'id16',   nist: nil, milestone: 'Configuration Verification Requirements', title: 'Verify that server configuration is hardened as per the recommendations of the application server and frameworks in use.'},356{id: '14.1.4',  section: '14.1', level: 2, weight: 50,  cwe: '-1', nist: nil, milestone: 'Configuration Verification Requirements', 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.'},357{id: '14.1.5',  section: '14.1', level: 3, weight: 100, cwe: '-1', nist: nil, milestone: 'Configuration Verification Requirements', title: 'Verify that authorized administrators can verify the integrity of all security-relevant configurations to detect tampering.'},358{id: '14.2.1',  section: '14.2', level: 1, weight: 25,  cwe: 'id1026', nist: nil, milestone: 'Configuration Verification Requirements', title: 'Verify that all components are up to date, preferably using a dependency checker during build or compile time. ([C2](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},359{id: '14.2.2',  section: '14.2', level: 1, weight: 25,  cwe: 'id1002', nist: nil, milestone: 'Configuration Verification Requirements', title: 'Verify that all unneeded features, documentation, samples, configurations are removed, such as sample applications, platform documentation, and default or example users.'},360{id: '14.2.3',  section: '14.2', level: 1, weight: 25,  cwe: 'id714',  nist: nil, milestone: 'Configuration Verification Requirements', 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.'},361{id: '14.2.4',  section: '14.2', level: 2, weight: 50,  cwe: 'id829',  nist: nil, milestone: 'Configuration Verification Requirements', title: 'Verify that third party components come from pre-defined, trusted and continually maintained repositories. ([C2](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},362{id: '14.2.5',  section: '14.2', level: 2, weight: 50,  cwe: '-1', nist: nil, milestone: 'Configuration Verification Requirements', title: 'Verify that an inventory catalog is maintained of all third party libraries in use. ([C2](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},363{id: '14.2.6',  section: '14.2', level: 2, weight: 50,  cwe: 'id265',  nist: nil, milestone: 'Configuration Verification Requirements', title: 'Verify that the attack surface is reduced by sandboxing or encapsulating third party libraries to expose only the required behaviour into the application. ([C2](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))'},364{id: '14.3.1',  section: '14.3', level: 1, weight: 25,  cwe: 'id209',  nist: nil, milestone: 'Configuration Verification Requirements', 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.'},365{id: '14.3.2',  section: '14.3', level: 1, weight: 25,  cwe: 'id497',  nist: nil, milestone: 'Configuration Verification Requirements', 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.'},366{id: '14.3.3',  section: '14.3', level: 1, weight: 25,  cwe: 'id200',  nist: nil, milestone: 'Configuration Verification Requirements', title: 'Verify that the HTTP headers or any part of the HTTP response do not expose detailed version information of system components.'},367{id: '14.4.1',  section: '14.4', level: 1, weight: 25,  cwe: 'id173',  nist: nil, milestone: 'Configuration Verification Requirements', title: 'Verify that every HTTP response contains a content type header specifying a safe character set (e.g., UTF-8, ISO 8859-1).'},368{id: '14.4.2',  section: '14.4', level: 1, weight: 25,  cwe: 'id116',  nist: nil, milestone: 'Configuration Verification Requirements', title: 'Verify that all API responses contain Content-Disposition: attachment; filename="api.json" (or other appropriate filename for the content type).'},369{id: '14.4.3',  section: '14.4', level: 1, weight: 25,  cwe: 'id1021', nist: nil, milestone: 'Configuration Verification Requirements', 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.'},370{id: '14.4.4',  section: '14.4', level: 1, weight: 25,  cwe: 'id116',  nist: nil, milestone: 'Configuration Verification Requirements', title: 'Verify that all responses contain X-Content-Type-Options: nosniff.'},371{id: '14.4.5',  section: '14.4', level: 1, weight: 25,  cwe: 'id523',  nist: nil, milestone: 'Configuration Verification Requirements', 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.'},372{id: '14.4.6',  section: '14.4', level: 1, weight: 25,  cwe: 'id116',  nist: nil, milestone: 'Configuration Verification Requirements', title: 'Verify that a suitable "Referrer-Policy" header is included, such as "no-referrer" or "same-origin".'},373{id: '14.4.7',  section: '14.4', level: 1, weight: 25,  cwe: 'id346',  nist: nil, milestone: 'Configuration Verification Requirements', 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.'},374{id: '14.5.1',  section: '14.5', level: 1, weight: 25,  cwe: 'id749',  nist: nil, milestone: 'Configuration Verification Requirements', title: 'Verify that the application server only accepts the HTTP methods in use by the application or API, including pre-flight OPTIONS.'},375{id: '14.5.2',  section: '14.5', level: 1, weight: 25,  cwe: 'id346',  nist: nil, milestone: 'Configuration Verification Requirements', 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.'},376{id: '14.5.3',  section: '14.5', level: 1, weight: 25,  cwe: 'id346',  nist: nil, milestone: 'Configuration Verification Requirements', 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.'},377{id: '14.5.4',  section: '14.5', level: 2, weight: 50,  cwe: 'id306',  nist: nil, milestone: 'Configuration Verification Requirements', title: 'Verify that HTTP headers added by a trusted proxy or SSO devices, such as a bearer token, are authenticated by the application.'}378]379issues.each do |issue|380  db.execute("INSERT INTO ISSUES VALUES (?, ?, ?, ?, ?, ?, ?)", issue[:id], issue[:section], issue[:level], issue[:weight], issue[:cwe], issue[:milestone], issue[:title])381end...

review_steps.rb

Source:review_steps.rb

...4end5def and_i_save_the_final_refund6  refund_review_page.save_and_continue.click7end8def and_i_verify_the_claimant_section_of_the_refund_review_page9  refund_review_page.about_the_claimant do |section|10    expect(section.full_name.text).to eql "#{test_user.title} #{test_user.first_name} #{test_user.last_name}"11    expect(section.date_of_birth.text).to eql Date.parse(test_user.date_of_birth).strftime('%d/%m/%Y')12  end13end14def and_i_verify_the_claimants_contact_details_of_the_refund_review_page15  refund_review_page.claimants_contact_details do |section|16    expect(section.building.text).to eql test_user.address.building.to_s17    expect(section.street.text).to eql test_user.address.street.to_s18    expect(section.locality.text).to eql test_user.address.locality.to_s19    expect(section.county.text).to eql test_user.address.county.to_s20    expect(section.post_code.text).to eql test_user.address.post_code.to_s21    expect(section.telephone_number.text).to eql test_user.telephone_number.to_s22    expect(section.email_address.text).to eql test_user.email_address.to_s23  end24end25def and_i_verify_the_claimants_name_and_address_in_the_original_case_details_of_the_refund_review_page26  refund_review_page.original_claimant_details do |section|27    expect(section.name.text).to eql "#{test_user.title} #{test_user.first_name} #{test_user.last_name}"28    expect(section.email_address.text).to eql test_user.email_address.to_s29    expect(section.building.text).to eql test_user.et_claim_to_refund.address.building.to_s30    expect(section.street.text).to eql test_user.et_claim_to_refund.address.street.to_s31    expect(section.locality.text).to eql test_user.et_claim_to_refund.address.locality.to_s32    expect(section.county.text).to eql test_user.et_claim_to_refund.address.county.to_s33    expect(section.post_code.text).to eql test_user.et_claim_to_refund.address.post_code.to_s34  end35end36def and_i_verify_the_case_details_in_the_case_details_of_the_refund_review_page37  refund_review_page.original_case_details do |section|38    expect(section.et_country_of_claim.text).to eql test_user.et_claim_to_refund.et_country_of_claim.to_s39    expect(section.et_case_number.text).to eql test_user.et_claim_to_refund.et_case_number.to_s40    expect(section.eat_case_number.text).to eql test_user.et_claim_to_refund.eat_case_number.to_s41    expect(section.et_tribunal_office.text).to eql test_user.et_claim_to_refund.et_tribunal_office.to_s42    expect(section.additional_information.text).to eql test_user.et_claim_to_refund.additional_information.to_s43  end44end45def and_i_verify_the_respondent_details_in_the_case_details_of_the_refund_review_page46  refund_review_page.original_respondent_details do |section|47    expect(section.name.text).to eql test_user.et_claim_to_refund.respondent.name.to_s48    expect(section.building.text).to eql test_user.et_claim_to_refund.respondent.address.building.to_s49    expect(section.street.text).to eql test_user.et_claim_to_refund.respondent.address.street.to_s50    expect(section.locality.text).to eql test_user.et_claim_to_refund.respondent.address.locality.to_s51    expect(section.county.text).to eql test_user.et_claim_to_refund.respondent.address.county.to_s52    expect(section.post_code.text).to eql test_user.et_claim_to_refund.respondent.address.post_code.to_s53  end54end55def and_i_verify_the_representative_details_in_the_case_details_of_the_refund_review_page56  refund_review_page.original_representative_details do |section|57    expect(section.name.text).to eql test_user.et_claim_to_refund.representative.name.to_s58    expect(section.building.text).to eql test_user.et_claim_to_refund.representative.address.building.to_s59    expect(section.street.text).to eql test_user.et_claim_to_refund.representative.address.street.to_s60    expect(section.locality.text).to eql test_user.et_claim_to_refund.representative.address.locality.to_s61    expect(section.county.text).to eql test_user.et_claim_to_refund.representative.address.county.to_s62    expect(section.post_code.text).to eql test_user.et_claim_to_refund.representative.address.post_code.to_s63  end64end65def and_i_verify_the_fees_in_the_case_details_of_the_refund_review_page66  aggregate_failures do67    fees = test_user.et_claim_to_refund.fees68    if fees.et_issue_fee.present?69      refund_review_page.original_claim_fees.et_issue do |section|70        expect(section.fee.text).to eql "Â£#{fees.et_issue_fee}"71        expect(section.payment_method.text).to eql fees.et_issue_payment_method.to_s72        expect(section.payment_date.text).to eql fee_date_for(fees.et_issue_payment_date, unknown: fees.et_issue_payment_date_unknown)73      end74    else75      expect(refund_review_page.original_claim_fees).to have_no_et_issue76    end77    if fees.et_hearing_fee.present?78      refund_review_page.original_claim_fees.et_hearing do |section|79        expect(section.fee.text).to eql "Â£#{fees.et_hearing_fee}"80        expect(section.payment_method.text).to eql fees.et_hearing_payment_method.to_s81        expect(section.payment_date.text).to eql fee_date_for(fees.et_hearing_payment_date, unknown: fees.et_hearing_payment_date_unknown)82      end83    else84      expect(refund_review_page.original_claim_fees).to have_no_et_hearing85    end86    if fees.et_reconsideration_fee.present?87      refund_review_page.original_claim_fees.et_reconsideration do |section|88        expect(section.fee.text).to eql "Â£#{fees.et_reconsideration_fee}"89        expect(section.payment_method.text).to eql fees.et_reconsideration_payment_method.to_s90        expect(section.payment_date.text).to eql fee_date_for(fees.et_reconsideration_payment_date, unknown: fees.et_reconsideration_payment_date_unknown)91      end92    else93      expect(refund_review_page.original_claim_fees).to have_no_et_reconsideration94    end95    if fees.eat_issue_fee.present?96      refund_review_page.original_claim_fees.eat_issue do |section|97        expect(section.fee.text).to eql "Â£#{fees.eat_issue_fee}"98        expect(section.payment_method.text).to eql fees.eat_issue_payment_method.to_s99        expect(section.payment_date.text).to eql fee_date_for(fees.eat_issue_payment_date, unknown: fees.eat_issue_payment_date_unknown)100      end101    else102      expect(refund_review_page.original_claim_fees).to have_no_eat_issue103    end104    if fees.eat_hearing_fee.present?105      refund_review_page.original_claim_fees.eat_hearing do |section|106        expect(section.fee.text).to eql "Â£#{fees.eat_hearing_fee}"107        expect(section.payment_method.text).to eql fees.eat_hearing_payment_method.to_s108        expect(section.payment_date.text).to eql fee_date_for(fees.eat_hearing_payment_date, unknown: fees.eat_hearing_payment_date_unknown)109      end110    else111      expect(refund_review_page.original_claim_fees).to have_no_eat_hearing112    end113    expected_total = [:et_issue, :et_hearing, :et_reconsideration, :eat_issue, :eat_hearing].reduce(0.0) do |t, fee|114      fee_value = fees.send("#{fee}_fee".to_sym)115      next t if fee_value.nil?116      t + fee_value.to_f117    end118    if expected_total > 0.0119      total_value = refund_review_page.original_claim_fees.total.fee.text.gsub(/Â£/, '').to_f120      expect(total_value).to eql expected_total121    else122      expect(refund_review_page.original_claim_fees).to have_empty_fees123    end124  end125end126def and_i_verify_the_representative_details_are_not_present_in_the_case_details_of_the_refund_review_page127  aggregate_failures do128    refund_review_page.original_representative_details do |section|129      expect(section).to have_no_name130      expect(section).to have_no_building131      expect(section).to have_no_street132      expect(section).to have_no_locality133      expect(section).to have_no_county134      expect(section).to have_no_post_code135    end136  end137end138def and_i_verify_the_bank_details_in_the_bank_details_of_the_refund_review_page139  refund_review_page.bank_details do |section|140    expect(section.account_name.text).to eql test_user.bank_account.account_name141    expect(section.bank_name.text).to eql test_user.bank_account.bank_name142    expect(section.account_number.text).to eql test_user.bank_account.account_number143    expect(section.sort_code.text).to eql test_user.bank_account.sort_code144  end145end146def and_i_verify_the_building_society_details_in_the_bank_details_of_the_refund_review_page147  refund_review_page.building_society_details do |section|148    expect(section.account_name.text).to eql test_user.building_society_account.account_name149    expect(section.building_society_name.text).to eql test_user.building_society_account.building_society_name150    expect(section.account_number.text).to eql test_user.building_society_account.account_number151    expect(section.sort_code.text).to eql test_user.building_society_account.sort_code152  end153end154def and_i_verify_the_bank_details_are_not_present_in_the_bank_details_of_the_review_page155  expect(refund_review_page).to have_no_bank_details156end157def and_i_verify_the_building_society_details_are_not_present_in_the_bank_details_of_the_refund_review_page158  expect(refund_review_page).to have_no_building_society_details159end160def and_i_verify_the_review_page_and_accept_the_declaration161  and_i_verify_the_claimant_section_of_the_refund_review_page162  and_i_verify_the_claimants_contact_details_of_the_refund_review_page163  and_i_verify_the_claimants_name_and_address_in_the_original_case_details_of_the_refund_review_page164  and_i_verify_the_case_details_in_the_case_details_of_the_refund_review_page165  and_i_verify_the_respondent_details_in_the_case_details_of_the_refund_review_page166  and_i_verify_the_representative_details_in_the_case_details_of_the_refund_review_page if test_user.et_claim_to_refund.has_representative == 'Yes'167  and_i_verify_the_representative_details_are_not_present_in_the_case_details_of_the_refund_review_page unless test_user.et_claim_to_refund.has_representative == 'Yes'168  and_i_verify_the_fees_in_the_case_details_of_the_refund_review_page169  and_i_verify_the_bank_details_in_the_bank_details_of_the_refund_review_page if test_user.bank_account.present?170  and_i_verify_the_bank_details_are_not_present_in_the_bank_details_of_the_review_page if test_user.bank_account.blank?171  and_i_verify_the_building_society_details_in_the_bank_details_of_the_refund_review_page if test_user.building_society_account.present?172  and_i_verify_the_building_society_details_are_not_present_in_the_bank_details_of_the_refund_review_page if test_user.building_society_account.blank?173  and_i_accept_the_refund_final_declaration174end175def then_the_continue_button_should_be_disabled_on_the_review_page...

patient_dashboard_page.rb

Source:patient_dashboard_page.rb

...13        find(".dashboard a", :text => name, :match => :prefer_exact).click14        wait_for_overlay_to_be_hidden15    end16    def verify_visit_vitals_info(vitals)17        vitals_section = find('.dashboard-section h2', :text => 'Vitals').parent18        expect(vitals_section).to have_content("BMI #{vitals[:bmi]}") if vitals.has_key? :bmi19        expect(vitals_section).to have_content("BMI STATUS #{vitals[:bmi_status]}") if vitals.has_key? :bmi_status20        expect(vitals_section).to have_content("HEIGHT #{vitals[:height]}") if vitals.has_key? :height21        expect(vitals_section).to have_content("WEIGHT #{vitals[:weight]}") if vitals.has_key? :weight22    end23    def start_consultation24        find(".grouped-buttons a", :text => 'Consultation', :match => :prefer_exact).click25    end26    def verify_existing_drugs(sections)27      sections.each do |section|28        table = page.find(TREATMENT_SECTION, :text => section['visit_date'])29        section['drugs'].each do |drug|30          expect(table).to have_content(drug)31        end32      end33    end34    def navigate_to_all_treatments_page35      find('h2', :text =>'Treatments').click36    end37    def navigate_to_visit_page(visit_date)38      find("a", :text=>visit_date, :match => :prefer_exact).click39    end40    def navigate_to_current_visit41      find("#Visits i[title='Current Visit']").click42      wait_for_overlay_to_be_hidden43    end44    def verify_new_drugs(*drugs)45      verify_drug_details(TREATMENT_SECTION, *drugs)46    end47    def verify_patient_profile_section(name)48      # todo: add more verification49      patient_section = find("#patient_information")50      expect(patient_section).to have_content(name)51    end52  def verify_radiology_section(radiology_image_concepts)53    expect(page).to have_selector('.dashboard-radiology-section .radiology-doc-item', :count=>radiology_image_concepts.length)54    radiology_image_concepts.each_with_index { |radiology_image_item, index|55      expect(find(".dashboard-radiology-section .radiology-doc-item:nth-of-type(#{index+1}) a", :visible => true).text).to eq(radiology_image_item[:concept_name])56      image_count = radiology_image_item[:image_count]57      if(image_count)58      expect(find(".dashboard-radiology-section .radiology-doc-item:nth-of-type(#{index+1}) span", :visible => true).text).to eq("(#{image_count})")59      end60    }61  end62  def verify_vitals(observations,id)63    observations_section = find('[id="'+id+'"]')64    expect(observations_section).to have_content("Pulse (72 - 72) #{observations[:pulse]} /min") if observations.has_key? :pulse65    expect(observations_section).to have_content("Diastolic (70 - 85) #{observations[:diastolic]} mm Hg") if observations.has_key? :diastolic66    expect(observations_section).to have_content("Systolic (110 - 140) #{observations[:systolic]} mm Hg") if observations.has_key? :systolic67    expect(observations_section).to have_content("Posture #{observations[:posture]}") if observations.has_key? :posture68    expect(observations_section).to have_content("Temperature (98.6 - 98.6) #{observations[:temperature]} F") if observations.has_key? :temperature69    expect(observations_section).to have_content("RR (16 - 20) #{observations[:rr]} /min") if observations.has_key? :rr70    expect(observations_section).to have_content("SPO2 (> 97) #{observations[:spo2]} %") if observations.has_key? :spo271  end72  def verify_second_vitals(observations,id)73    verify_vitals(observations, id)74  end75  def verify_nutritional_values(observations,id)76    observations_section = find('[id="'+id+'"]')77    expect(observations_section).to have_content("BMI #{observations[:bmi]}") if observations.has_key? :bmi78    expect(observations_section).to have_content("BMI STATUS #{observations[:bmi_status]}") if observations.has_key? :bmi_status79    expect(observations_section).to have_content("HEIGHT #{observations[:height]}") if observations.has_key? :height80    expect(observations_section).to have_content("WEIGHT #{observations[:weight]}") if observations.has_key? :weight81  end82  def verify_history_and_examination_values(observations,id)83    observations_section = find('[id="'+id+'"]')84    verify_chief_complaints(observations_section, observations[:chief_complaints]) if observations.has_key? :chief_complaints85    expect(observations_section).to have_content("History Notes #{observations[:history_notes]}") if observations.has_key? :history_notes86    expect(observations_section).to have_content("Examination Notes #{observations[:examination_notes]}") if observations.has_key? :examination_notes87    expect(observations_section).to have_content("Smoking History #{observations[:smoking_history]}") if observations.has_key? :smoking_history88  end89  def verify_gynaecology_values(observations,id)90    observations_section = find('[id="'+id+'"]')91    expect(observations_section).to have_content("P/S (Per Speculum) - Cervix #{observations[:ps_perSpeculum_cervix][0]}, #{observations[:ps_perSpeculum_cervix][1]}") if observations.has_key? :ps_perSpeculum_cervix92  end93  def verify_anc_values(observations, id)94    observations_section = find('[id="'+id+'"]')95    expect(observations_section).to have_content("#{observations[:Danger_sign]}")96    expect(observations_section).to have_content("#{observations[:ANC_Visit_Number]}")97  end98  def verify_obstetrics_values(observations,id)99    observations_section = find('[id="'+id+'"]')100    expect(observations_section).to have_content("Fundal Height (Weeks) #{observations[:fundal_height]}") if observations.has_key? :fundal_height101    expect(observations_section).to have_content("P/A Presenting Part #{observations[:pa_presenting_part]}") if observations.has_key? :pa_presenting_part102    expect(observations_section).to have_content("FHS #{observations[:fhs]}") if observations.has_key? :fhs103    #expect(observations_section).to have_content("LMP #{observations[:lmp]}") if observations.has_key? :lmp104    expect(observations_section).to have_content("Amount of Liquor #{observations[:amountOfLiquor]}") if observations.has_key? :amountOfLiquor105  end106  def verify_observations_on_all_details_page(observations, id)107    observation_section = "observationControlSection"108    find('[id="'+id+'"]').find("h2").click109    verify_nutritional_values(observations, observation_section) if observations.has_key? :bmi110    verify_history_and_examination_values(observations, observation_section)  if observations.has_key? :chief_complaints111    verify_gynaecology_values(observations, observation_section)  if observations.has_key? :ps_perSpeculum_cervix112    verify_second_vitals(observations, observation_section) if observations.has_key? :pulse113    verify_vitals(observations, observation_section) if observations.has_key? :pulse114    verify_obstetrics_values(observations, observation_section) if observations.has_key? :fundal_height115    find('.ngdialog-theme-default.ng-dialog-all-details-page .ngdialog-close').click116  end117  def verify_presence_of_start_consultation_link()118    expect(page).to have_link("Consultation")119  end120  def verify_absence_of_start_consultation_link()121    dashboard_header_right_section= page.find('div.dashboard-header-right-wrapper')122    expect(dashboard_header_right_section).to have_no_link("Consultation")123  end124  def verify_presence_of_current_visit()125    expect(page).to have_selector("i#currentVisitIcon")126  end127  def verify_absence_of_current_visit()128    expect(page).to have_no_selector("i#currentVisitIcon")129  end130  def verify_visit_type(visit_type)131    visits_section = page.find("#visitDisplayTable").first("tr#eachVisit")132    expect(visits_section.first("td#visitType")).to have_content(visit_type)133  end134  def verify_retrospective_date(location,retro_date)135    verify_retrospective_date_tab(location,retro_date)136    verify_retrospective_date_in_visit_section(retro_date)137  end138  def verify_retrospective_data(retro_date,vitals)139    verify_retrospective_date_in_visits_page(vitals)140    verify_retrospective_date_in_all_vitals_page(retro_date)141  end142  def verify_retrospective_date_tab(location,retro_date)143    expected=find("div.retro-date-widget-header").text144    expect(expected).to eq(location+","+retro_date)145  end146  def verify_retrospective_date_in_visit_section(retro_date)147    expected=find("#visitDisplayTable").text148    expect(expected).to match(retro_date+" - "+retro_date)149  end150  def verify_retrospective_date_in_drug_section(retro_date)151    expected=find("treatment-table thead").text152    expect(expected).to match(retro_date)153  end154  def verify_retrospective_date_in_visits_page(vitals)155    click_link_with_text "Vitals"156    visit_page.verify_observations(vitals)157  end158  def verify_retrospective_date_in_all_vitals_page(retro_date)159    expected=find("#Visits").text160    expect(expected).to be(retro_date+" - "+retro_date)161  end162  def verify_lab_results163    page.all(:css , '.dashboard-laborders-section span.value').each do |result|164      expect(result.text).to include("10")165    end166  end167end...

section

Using AI Code Generation

1puts Verify.section(str, 0, 4)2puts Verify.section(str, 4, 4)3puts Verify.section(str, 8, 4)4puts Verify.section(str, 12, 4)5puts Verify.section(str, 16, 4)6puts Verify.section(str, 20, 4)7puts Verify.section(str, 24, 4)8puts Verify.section(str, 28, 4)9puts Verify.section(str, 32, 4)10puts Verify.section(str, 36, 4)11puts Verify.section(str, 40, 4)12puts Verify.section(str, 44, 4)13puts Verify.section(str, 48, 4)14puts Verify.section(str, 52, 4)15puts Verify.section(str, 56, 4)16puts Verify.section(str, 60, 4)17puts Verify.section(str, 64, 4)18puts Verify.section(str, 0, 4)19puts Verify.section(str, 4, 4)20puts Verify.section(str, 8, 4)21puts Verify.section(str, 12, 4)22puts Verify.section(str, 16, 4)23puts Verify.section(str, 20, 4)24puts Verify.section(str, 24, 4)25puts Verify.section(str, 28, 4)26puts Verify.section(str, 32, 4)27puts Verify.section(str, 36, 4)28puts Verify.section(str, 40, 4)29puts Verify.section(str, 44, 4)30puts Verify.section(str, 48, 4

section

Using AI Code Generation

1  v.verify { ARGV[0].is_a? String }2  v.verify { ARGV[0].length > 0 }3  v.verify { ARGV[1].is_a? Integer }4  v.verify { ARGV[1] > 0 }5  v.verify { ARGV[2].is_a? String }6  v.verify { ARGV[2].length > 0 }7  v.verify { ARGV[3].is_a? Integer }8  v.verify { ARGV[3] > 0 }9  v.verify { ARGV[4].is_a? String }10  v.verify { ARGV[4].length > 0 }11  v.verify { ARGV[5].is_a? Integer }12  v.verify { ARGV[5] > 0 }13  v.verify { ARGV[6].is_a? String }14  v.verify { ARGV[6].length > 0 }15  v.verify { ARGV[7].is_a? Integer }16  v.verify { ARGV[7] > 0 }17  v.verify { ARGV[8].is_a? String }18  v.verify { ARGV[8].length > 0 }19  v.verify { ARGV[9].is_a? Integer }20  v.verify {

section

Using AI Code Generation

1verify(1) { section("1.1") { puts "test" } }2  def self.section(name)3verify(2) { section("1.1") { puts "test" } }4  def self.section(name)5verify(3) { section("1.1") { puts "test" } }6  def self.section(name)7verify(4) { section("1.1") { puts "test" } }8  def self.section(name)9verify(5) { section("1.1") { puts "test" } }10  def self.section(name)11verify(6) { section("1.1") { puts "test" } }

Automation Testing Tutorials

Learn to execute automation testing from scratch with LambdaTest Learning Hub. Right from setting up the prerequisites to run your first automation test, to following best practices and diving deeper into advanced test scenarios. LambdaTest Learning Hubs compile a list of step-by-step guides to help you be proficient with different test automation frameworks i.e. Selenium, Cypress, TestNG etc.