{"page":1,"standards":[{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x10-V1-Architecture.md#v11-secure-software-development-lifecycle","id":"ASVS:V1.1.1:Verify the use of a secure software development lifecycle that addresses security in all stages of development.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x10-V1-Architecture.md#v11-secure-software-development-lifecycle","links":[{"document":{"doctype":"CRE","id":"616-305","name":"Development processes for security","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"Verify the use of a secure software development lifecycle that addresses security in all stages of development.","sectionID":"V1.1.1","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x10-V1-Architecture.md#v11-secure-software-development-lifecycle","id":"ASVS:V1.1.5:Verify definition and security analysis of the application's high-level architecture and all connected remote services.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x10-V1-Architecture.md#v11-secure-software-development-lifecycle","links":[{"document":{"doctype":"CRE","id":"068-102","name":"Describe high-level system architecture and perform threat modeling on it every critical change and regularly","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"Verify definition and security analysis of the application's high-level architecture and all connected remote services.","sectionID":"V1.1.5","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x10-V1-Architecture.md#v11-secure-software-development-lifecycle","id":"ASVS:V1.10.1: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.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x10-V1-Architecture.md#v11-secure-software-development-lifecycle","links":[{"document":{"doctype":"CRE","id":"757-271","name":"Use source code control system with change traceability and access control","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"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.","sectionID":"V1.10.1","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x18-V10-Malicious.md#v103-application-integrity","id":"ASVS:V10.3.2:Verify that the application employs integrity protections, such as code signing or subresource 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.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x18-V10-Malicious.md#v103-application-integrity","links":[{"document":{"doctype":"CRE","id":"307-507","name":"Allow only trusted sources both build time and runtime; therefore perform integrity checks on all resources and code","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"Verify that the application employs integrity protections, such as code signing or subresource 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.","sectionID":"V10.3.2","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x22-V14-Config.md#v141-build-and-deploy","id":"ASVS:V14.1.5:Verify that authorized administrators can verify the integrity of all security-relevant configurations to detect tampering.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x22-V14-Config.md#v141-build-and-deploy","links":[{"document":{"doctype":"CRE","id":"347-352","name":"Set and confirm integrity of security deployment configuration","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"Verify that authorized administrators can verify the integrity of all security-relevant configurations to detect tampering.","sectionID":"V14.1.5","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x10-V1-Architecture.md#v11-secure-software-development-lifecycle","id":"ASVS:V1.14.4: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.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x10-V1-Architecture.md#v11-secure-software-development-lifecycle","links":[{"document":{"doctype":"CRE","id":"263-184","name":"Automate secure build and deployment, especially with SDI","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"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.","sectionID":"V1.14.4","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x10-V1-Architecture.md#v11-secure-software-development-lifecycle","id":"ASVS:V1.14.2:Verify that binary signatures, trusted connections, and verified endpoints are used to deploy binaries to remote devices.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x10-V1-Architecture.md#v11-secure-software-development-lifecycle","links":[{"document":{"doctype":"CRE","id":"171-222","name":"Check binary integrity before deployment","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"Verify that binary signatures, trusted connections, and verified endpoints are used to deploy binaries to remote devices.","sectionID":"V1.14.2","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x22-V14-Config.md#v141-build-and-deploy","id":"ASVS:V14.1.4: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.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x22-V14-Config.md#v141-build-and-deploy","links":[{"document":{"doctype":"CRE","id":"208-355","name":"Ensure repeatability of deployment","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"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.","sectionID":"V14.1.4","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x18-V10-Malicious.md#v103-application-integrity","id":"ASVS:V10.3.1: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.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x18-V10-Malicious.md#v103-application-integrity","links":[{"document":{"doctype":"CRE","id":"028-254","name":"Secure auto-updates over full stack","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"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.","sectionID":"V10.3.1","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x22-V14-Config.md#v141-build-and-deploy","id":"ASVS:V14.1.1: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.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x22-V14-Config.md#v141-build-and-deploy","links":[{"document":{"doctype":"CRE","id":"253-452","name":"Securely automate build and deployment in pipeline","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"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.","sectionID":"V14.1.1","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x22-V14-Config.md#v141-build-and-deploy","id":"ASVS:V14.1.2: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.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x22-V14-Config.md#v141-build-and-deploy","links":[{"document":{"doctype":"CRE","id":"314-131","name":"Use features in compile and build tools for executable security","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"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.","sectionID":"V14.1.2","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x10-V1-Architecture.md#v11-secure-software-development-lifecycle","id":"ASVS:V1.14.6: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.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x10-V1-Architecture.md#v11-secure-software-development-lifecycle","links":[{"document":{"doctype":"CRE","id":"673-475","name":"Disallow unsupported/deprecated client-side technologies","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"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.","sectionID":"V1.14.6","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x18-V10-Malicious.md#v102-malicious-code-search","id":"ASVS:V10.2.6:Verify that the application source code and third party libraries do not contain Easter eggs or any other potentially unwanted functionality.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x18-V10-Malicious.md#v102-malicious-code-search","links":[{"document":{"doctype":"CRE","id":"154-031","name":"Harden application by excluding unwanted functionality","tags":["Configuration"]},"ltype":"Linked To"}],"name":"ASVS","section":"Verify that the application source code and third party libraries do not contain Easter eggs or any other potentially unwanted functionality.","sectionID":"V10.2.6","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x22-V14-Config.md#v142-dependency","id":"ASVS:V14.2.2:Verify that all unneeded features, documentation, sample applications and configurations are removed.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x22-V14-Config.md#v142-dependency","links":[{"document":{"doctype":"CRE","id":"462-245","name":"Remove unnecessary elements from external components (e.g. features, documentation, configuration)","tags":["Configuration"]},"ltype":"Linked To"}],"name":"ASVS","section":"Verify that all unneeded features, documentation, sample applications and configurations are removed.","sectionID":"V14.2.2","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x18-V10-Malicious.md#v102-malicious-code-search","id":"ASVS:V10.2.1: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.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x18-V10-Malicious.md#v102-malicious-code-search","links":[{"document":{"doctype":"CRE","id":"834-645","name":"Avoid unauthorized client data collection","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"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.","sectionID":"V10.2.1","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x18-V10-Malicious.md#v102-malicious-code-search","id":"ASVS:V10.2.3: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.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x18-V10-Malicious.md#v102-malicious-code-search","links":[{"document":{"doctype":"CRE","id":"838-636","name":"Check source code and third party libraries to not contain backdoors","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"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.","sectionID":"V10.2.3","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x18-V10-Malicious.md#v102-malicious-code-search","id":"ASVS:V10.2.5:Verify that the application source code and third party libraries do not contain malicious code, such as salami attacks, logic bypasses, or logic bombs.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x18-V10-Malicious.md#v102-malicious-code-search","links":[{"document":{"doctype":"CRE","id":"265-800","name":"Check source code and third party libraries to not contain malicious code","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"Verify that the application source code and third party libraries do not contain malicious code, such as salami attacks, logic bypasses, or logic bombs.","sectionID":"V10.2.5","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x18-V10-Malicious.md#v102-malicious-code-search","id":"ASVS:V10.2.4:Verify that the application source code and third party libraries do not contain time bombs by searching for date and time related functions.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x18-V10-Malicious.md#v102-malicious-code-search","links":[{"document":{"doctype":"CRE","id":"418-525","name":"Check source code and third party libraries to not contain timebombs","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"Verify that the application source code and third party libraries do not contain time bombs by searching for date and time related functions.","sectionID":"V10.2.4","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x22-V14-Config.md#v142-dependency","id":"ASVS:V14.2.3:Verify that if application assets, such as JavaScript libraries, CSS or web fonts, are hosted externally on a Content Delivery Network (CDN) or external provider, Subresource Integrity (SRI) is used to validate the integrity of the asset.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x22-V14-Config.md#v142-dependency","links":[{"document":{"doctype":"CRE","id":"577-260","name":"Enforce integrity check for externally hosted assets (eg SRI)","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"Verify that if application assets, such as JavaScript libraries, CSS or web fonts, are hosted externally on a Content Delivery Network (CDN) or external provider, Subresource Integrity (SRI) is used to validate the integrity of the asset.","sectionID":"V14.2.3","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]},{"doctype":"Standard","hyperlink":"https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x22-V14-Config.md#v142-dependency","id":"ASVS:V14.2.4:Verify that third party components come from pre-defined, trusted and continually maintained repositories.:https://github.com/OWASP/ASVS/blob/v4.0.3/4.0/en/0x22-V14-Config.md#v142-dependency","links":[{"document":{"doctype":"CRE","id":"715-223","name":"Ensure trusted origin of third party resources","tags":["subtype:requirements_standard","source:opencre_master_sheet","audience:architect","family:standard","maturity:stable"]},"ltype":"Linked To"}],"name":"ASVS","section":"Verify that third party components come from pre-defined, trusted and continually maintained repositories.","sectionID":"V14.2.4","tags":["subtype:requirements_standard","source:owasp_asvs","family:standard","audience:developer","maturity:stable"]}],"total_pages":14}
