© Copyright by Eccam s.r.o. All rights reserved.
", "attachments": [ "INF-2_1_reqview_icon.png" ] }, { "id": "21", "guid": "d44a3fde-e852-4cd2-bfd7-aaacd6567915", "heading": "History", "children": [ { "id": "22", "guid": "a5a4569b-51e3-477c-a8f2-dad3f75467d3", "text": "| Name | Date | Reason for Change |
|---|---|---|
| Libor Bus | 2015-08-31 | Initial draft |
| Libor Bus | 2016-01-14 | Added document TESTS |
| Libor Bus | 2016-05-27 | Added document NEEDS |
| Libor Bus | 2016-06-17 | Added document RISKS |
| Libor Bus | 2017-02-23 | Reordered documents and other minor updates |
| Libor Bus | 2018-04-10 | Added template columns to documents NEEDS, SRS and RISKS |
| Libor Bus | 2018-08-19 | Added document INF with overall description |
| Libor Bus | 2018-11-16 | Added column Upstream Traceability to document SRS |
| Libor Bus | 2019-05-19 | Aligned documents SRS with the ISO/IEC/IEEE 29148 template |
| Libor Bus | 2019-09-12 | Added document ARCH |
| Libor Bus | 2019-10-23 | Simplified traceability columns to contain only formatting recognized by MS Word in the exported output |
| Tom Novacek | 2020-06-24 | Updated Introduction section in all documents |
| Libor Bus | 2022-04-24 | Added type attribute to documents TESTS and ARCH. Added usage traceability links in document ARCH |
| Libor Bus | 2023-05-17 | Organized documents in groups Defined table views |
| Libor Bus | 2024-03-08 | Added document ASVS Added security requirements document SRS |
This is a ReqView Demo Project illustrating how you can specify and manage requirements for a SW development project in ReqView.
Note: This is an example project, which is not complete.
" }, { "id": "12", "guid": "0d034daa-b479-49a3-b9c8-94726c550721", "text": "This project describes user needs, security requirements, risks, SW requirements, verification tests and solution architecture for a simplified functionality of ReqView application version v1.0.
" } ] }, { "id": "11", "guid": "2e31f9b5-d2f7-4d42-900a-0dc9e60629fd", "heading": "Intended Audience", "children": [ { "id": "14", "guid": "f9b4cec7-e383-4bed-8496-3c6793f4056f", "text": "The target audience are new ReqView users evaluating ReqView and users learning how to gather and manage requirements in ReqView.
" } ] }, { "id": "25", "guid": "4aff0011-6393-46fc-a362-dcbf8f30db04", "heading": "Project Structure", "children": [ { "id": "9", "guid": "c34f63fa-d24d-48dc-992e-51581da51043", "attachments": [ "INF-9_1_Project Traceability Diagram.png" ] } ] } ] }, { "id": "3", "guid": "37c768e3-641f-4989-bb46-1260e4edc7a8", "heading": "Documents", "children": [ { "id": "27", "guid": "5385af5b-7eca-4e57-9245-e1e52ce90a24", "heading": "Level 1", "children": [ { "id": "5", "guid": "100123cb-1d16-419f-a305-90bf4524ee86", "heading": "NEEDS: ReqView User Needs", "text": "NEEDS document describes the highest level user stories and constraints.
", "links": { "reference": [ "NEEDS-3", "NEEDS-4" ] } }, { "id": "30", "guid": "54fd60eb-7867-45f4-94e9-6ff5b21a1e58", "heading": "ASVS: OWASP Application Security Verification Standard", "text": "ASVS document describes application security requirements.
", "links": { "reference": [ "ASVS-61", "ASVS-118", "ASVS-186", "ASVS-214", "ASVS-228", "ASVS-264", "ASVS-285", "ASVS-303", "ASVS-324", "ASVS-335", "ASVS-349", "ASVS-359", "ASVS-381", "ASVS-401" ] } }, { "id": "8", "guid": "c87fe938-b654-4b0c-85da-e1b949d13dcb", "heading": "RISKS: Failure Mode and Effects Analysis", "text": "RISKS document describes project risks using failure mode and effects analysis (FMEA) method.
", "links": { "reference": [ "RISKS-2" ] } } ] }, { "id": "28", "guid": "bd22db9e-ccd4-48dc-972a-6f69c23287d4", "heading": "Level 2", "children": [ { "id": "6", "guid": "56158b1c-4c64-4a44-b048-c7b402c96df3", "heading": "SRS: ReqView Software Requirements Specification", "text": "SRS document describes SW requirements derived from user stories or mitigating project risks.
", "links": { "reference": [ "SRS-20" ] } }, { "id": "7", "guid": "2bfcd9e6-3de4-4495-b27d-9f851f088edf", "heading": "TESTS: ReqView Verification Tests", "text": "TESTS document describes test cases verifying functionality described by the SW requirements.
", "links": { "reference": [ "TESTS-2" ] } } ] }, { "id": "29", "guid": "e81e2fc9-587c-4631-80e5-527808a75ccd", "heading": "Level 3", "children": [ { "id": "23", "guid": "cb66b166-cfe7-4352-90f7-1bbc3a492973", "heading": "ARCH: ReqView Architecture", "text": "ARCH document describes the architecture of the application described by the SW requirements.
", "links": { "reference": [ "ARCH-2" ] } } ] } ] }, { "id": "4", "guid": "dc3049f9-b025-4e6d-ac12-85e9e90b4e77", "heading": "Traceability", "children": [ { "id": "16", "guid": "69884407-27d6-40ea-9a43-362c075a2441", "heading": "Satisfaction Links", "text": "Satisfaction links lead from downstream SW requirements to the related highest level user needs and security requirements (M:N).
" }, { "id": "20", "guid": "51ea8c7d-5985-4151-b559-91de5c8434df", "heading": "Mitigation Links", "text": "Mitigation links lead from downstream SW requirements to the related project risk corrective actions (M:N).
" }, { "id": "17", "guid": "ee02f69d-0255-43e2-9cb6-4ecfe30566f3", "heading": "Verification Links", "text": "Verification links lead from a test case to the related SW requirements (M:N).
" }, { "id": "24", "guid": "e7a4cd8b-0294-4632-a3b2-ceeb0c0da55f", "heading": "Implementation Links", "text": "Implementation links lead from a component in the architecture to the relates SW requirements (M:N).
" } ] } ], "attributes": { }, "templateColumns": { }, "views": { "Primary": { "columns": [ { "columnId": "id", "width": 119 }, { "columnId": "description", "width": 711 }, { "columnId": "links", "width": 386 } ], "default": true } } }, { "id": "NEEDS", "guid": "cf024593-2de0-45cf-ae98-0941b85cc094", "name": "ReqView User Needs", "lastId": 76, "createdOn": "2016-05-24T09:16:13.126Z", "createdBy": { "name": "Libor Bus", "email": "libor.bus@eccam.com", "company": "Eccam s.r.o." }, "lastChangedOn": "2024-03-08T12:50:25.311Z", "lastChangedBy": { "name": "Libor Bus", "email": "libor.bus@eccam.com", "company": "Eccam" }, "data": [ { "id": "45", "guid": "57916083-61b1-4406-b5ec-a341a2c10de7", "text": "© Copyright by Eccam s.r.o. All rights reserved.
", "type": "INF" }, { "id": "2", "guid": "c41769d3-cac5-4c45-9dfa-a33f52ac93d6", "heading": "Introduction", "instructions": "This document describes needs of product stakeholders as agile user stories. User stories are simple statements formulated according to the following template:
“As a <type of user>, I want <some goal>, so that <some reason>.”
For more information see User Stories Applied by Mike Cohn or his User Stories web page.
", "type": "SEC", "children": [ { "id": "64", "guid": "9b0d3723-912b-4728-aa0e-5c3bdfe04ea0", "heading": "Purpose", "instructions": "Identify the product specified in this document.
", "type": "SEC", "children": [ { "id": "67", "guid": "05fa03f6-9896-41cf-abc5-05c567b3cbbd", "text": "The main purpose of this document is to provide new ReqView users a working example of a document describing high-level user needs by means of user stories.
Note: This is an example document, which is not complete.
", "type": "INF" } ] }, { "id": "65", "guid": "8f30721e-0740-4277-b997-427a6b7e6db7", "heading": "Scope", "instructions": "Briefly describe the scope of the product.
", "type": "SEC", "children": [ { "id": "75", "guid": "1b5b7ed0-1303-41e7-a58b-87e40e495784", "text": "This document specifies requirements for a simple application for requirements management of software and system products.
", "type": "INF" }, { "id": "66", "guid": "7b6ac21f-da50-47b3-bf72-b31a5fee2331", "text": "Users should be able to:
Note: The application functionality corresponds to ReqView v1.0 released in 2015. Check all advanced requirements management features it offers now.
", "type": "INF" } ] }, { "id": "1", "guid": "03658799-6c3b-44fe-a0e6-a23613fce43f", "heading": "User Roles", "instructions": "Identify user roles for the product and for each role describe characteristics of a typical user.
You may consider creating personas with a real name. Each persona should be described sufficiently that everyone on the team feels like they know the persona.
", "type": "SEC", "children": [ { "id": "5", "guid": "2f415d73-2069-4cc2-b2e9-c5b5c359efd2", "heading": "Requirements Architect", "text": "Requirements Architect defines requirements model and configure the requirements project for other users.
Requirements Architect is typically a QA manager or project manager.
", "asAn": "Architect", "iWant": "Editor defines project requirements and creates requirements and tests documents.
Editor is typically a requirements engineer, business analyst, project manager, QA engineer or a tester.
", "asAn": "Editor", "iWant": "Reviewer reads project documents, performs review and provides feedback for improving the content of the document.
Reviewer is typically an internal QA expert reviewing requirements and tests, customer or supplier commenting requirements and setting the requirement acceptance state.
", "asAn": "Reviewer", "iWant": "Specify user stories describing functionality of the product grouped into epics for easier navigation in the document.
Set the following attributes for each story:
Tool supports:
save document in a file
", "soThat": "users can open the document for further editing or review
", "status": "Verified", "type": "STORY" }, { "id": "14", "guid": "d1fa5338-44e6-40e2-a971-b8a656238a16", "heading": "Document Templates", "acceptanceCriteria": "Tool supports:
save a document as a template file
", "soThat": "I can reuse the document structure and configuration of custom attributes for new documents
", "status": "Verified", "type": "STORY" }, { "id": "33", "guid": "6c0a35fc-d7f9-4175-84dc-4e5aad145238", "heading": "Autosave", "acceptanceCriteria": "Tool:
automatically persist my changes
", "soThat": "I do not lose my changes if the tool is unexpectedly terminated before saving into a file
", "status": "Verified", "type": "STORY" } ] }, { "id": "8", "guid": "4883987f-6c3a-4a66-a44f-8cd7000b70f0", "heading": "Define Requirements", "type": "EPIC", "children": [ { "id": "68", "guid": "47e4b317-17f5-45c4-a16c-a5fbda44a5c5", "heading": "Requirement Description", "acceptanceCriteria": "Tool supports:
specify requirements by a textual description
", "soThat": "the requirements can be reviewed by other users.
", "status": "Verified", "type": "STORY" }, { "id": "32", "guid": "8366a026-3158-443b-a759-fe299e589534", "heading": "Unique IDs", "acceptanceCriteria": "Tool supports:
identify requirements by their unique ID
", "soThat": "I can reference requirements from other documents or communication
", "status": "Verified", "type": "STORY" }, { "id": "12", "guid": "767f4667-4b3e-497f-b061-6024977a62db", "heading": "Document Structure", "acceptanceCriteria": "Tool supports:
organize requirements in a tree document hierarchy with numbered sections
", "soThat": "I can easily navigate in the document structure
", "status": "Verified", "type": "STORY" }, { "id": "73", "guid": "b2f883b8-769e-4aeb-b419-41490e5b2ce7", "heading": "Table View", "acceptanceCriteria": "Tool supports:
display a table of requirements
", "soThat": "I can review all requirements information in a single view
", "status": "Verified", "type": "STORY" }, { "id": "74", "guid": "138a88a8-b347-4835-8f85-661236e4c2bd", "heading": "Detailed View", "acceptanceCriteria": "Tool supports:
display all information about the selected requirement
", "soThat": "I can display details about any requirement which are not visible in the requirements table
", "status": "Verified", "type": "STORY" }, { "id": "17", "guid": "40f3c5d5-6c6f-45c6-869a-535b8eadc13a", "heading": "Attachments", "acceptanceCriteria": "Tool supports:
attach images and other documents to requirements
", "soThat": "I can enhance textual requirements with visual content such as mockups, diagrams, etc.
", "status": "Verified", "type": "STORY" }, { "id": "35", "guid": "7c634ae1-0e07-46c4-bc0c-3340513f6956", "heading": "Sort", "acceptanceCriteria": "Tool supports sorting requirements by:
order requirements by a chosen custom attribute
", "soThat": "I can display requirements sorted by priority, risk, effort, etc.
", "status": "Verified", "type": "STORY" } ] }, { "id": "70", "guid": "ce912e6b-e263-4c69-8d4c-d7d7050ee86b", "heading": "Manage Requirements", "type": "EPIC", "children": [ { "id": "19", "guid": "561c6863-ba20-41ef-8f9a-932b8e352af9", "heading": "Custom Attributes Configuration", "acceptanceCriteria": "Tool supports:
define additional requirements attributes
", "soThat": "the document can flexibly store additional requirement properties, such as requirement source, priority, status, etc.
", "status": "Verified", "type": "STORY" }, { "id": "69", "guid": "8547cf35-70e0-47e9-8683-44702395341a", "heading": "Custom Attributes", "acceptanceCriteria": "Tool supports:
set a value of a chosen custom attribute for one or more selected requirements
", "soThat": "I can define additional requirements properties, such as requirements source, prioritize requirements, manage requirement status, define acceptance criteria, etc.
", "status": "Verified", "type": "STORY" }, { "id": "16", "guid": "b9d27d67-aa41-4d85-8cc1-a90a715f9d37", "heading": "Traceability Configuration", "acceptanceCriteria": "Tool supports:
define types of relationships between requirements
", "soThat": "users can perform traceability analysis for a chosen group of links
", "status": "Verified", "type": "STORY" }, { "id": "21", "guid": "d080f428-cf1e-4919-89db-a8169d735e51", "heading": "Traceability Links", "acceptanceCriteria": "Tool supports:
link related requirements
", "soThat": "I can analyze requirements coverage, gap in requirements and impact of requirement changes.
", "status": "Verified", "type": "STORY" }, { "id": "34", "guid": "00ab0f5f-5bca-4635-9854-0de89db36a60", "heading": "Filter", "acceptanceCriteria": "Tool supports filtering requirements:
filter requirements
", "soThat": "I can identify and manipulate requirements matching a condition
", "status": "Verified", "type": "STORY" }, { "id": "36", "guid": "f83fb577-55a7-476b-8ea4-83fecdf77f9b", "heading": "Search", "acceptanceCriteria": "Tool supports searching requirements containing a given keyword.
", "asAn": "Editor", "iWant": "find keywords
", "soThat": "I can identify and manipulate requirements containing the searched keyword(s)
", "status": "Verified", "type": "STORY" } ] }, { "id": "22", "guid": "fb861b9d-011e-4046-8f17-cdc453bc3ed3", "heading": "Review Requirements", "type": "EPIC", "children": [ { "id": "24", "guid": "48d5aa49-31b8-4ff9-a52c-be80258fa9fa", "heading": "Discussion", "acceptanceCriteria": "Tool supports:
comment requirements
", "soThat": "I can provide feedback during requirements review
", "status": "Verified", "type": "STORY" }, { "id": "30", "guid": "78da2553-a8ba-47ed-8382-e8c207c1bf4f", "heading": "Traceability Browser", "acceptanceCriteria": "Tool supports:
trace related requirements
", "soThat": "I can perform coverage, gap and change impact analysis
", "status": "Verified", "type": "STORY" }, { "id": "29", "guid": "eea2a384-27ee-44c6-bbd2-6c80a1642768", "heading": "Print", "acceptanceCriteria": "Tool supports:
print a document view
", "soThat": "I can review requirements without the need to run the tool
", "status": "Verified", "type": "STORY" } ] }, { "id": "31", "guid": "e995cf73-40dd-41da-a96c-141d850cbd85", "heading": "Audit Trail", "type": "EPIC", "children": [ { "id": "26", "guid": "92f9a2c4-44fb-49ee-bc72-a5a7110bcd84", "heading": "History of Changes", "acceptanceCriteria": "Tool supports:
list all requirement changes
", "soThat": "I can understand how the requirement evolved in time
", "status": "Verified", "type": "STORY" }, { "id": "23", "guid": "dd4efc4c-c48c-4723-8866-16999d813d7f", "heading": "Traceability Report", "acceptanceCriteria": "Tool supports:
generate a traceability report
", "soThat": "I can analyze coverage, gaps and impact of requirements changes
", "status": "Verified", "type": "STORY" } ] }, { "id": "11", "guid": "fd49a637-753e-4114-8caa-587db1bea80b", "heading": "Integrations", "type": "EPIC", "children": [ { "id": "27", "guid": "f267ba72-6383-44b1-8b6a-37422d3841a4", "heading": "Import from Word", "acceptanceCriteria": "Tool supports:
import a requirements specification from a MS Word document
", "soThat": "I can reuse existing requirements specifications or other structured documents
", "status": "Verified", "type": "STORY" }, { "id": "71", "guid": "c511a76d-8c3c-4643-a24c-5124ba36df3a", "heading": "Import from Excel", "acceptanceCriteria": "Tool supports:
import requirements from a MS Excel spreadsheet
", "soThat": "I can import or update list of requirements
", "status": "Verified", "type": "STORY" }, { "id": "28", "guid": "a71a2a78-a185-43e7-891b-34b3247e93bc", "heading": "Export to Word", "acceptanceCriteria": "Tool supports:
to export structured requirements specification to MS Word
", "soThat": "I can share requirements specifications with users without the tool
", "status": "Verified", "type": "STORY" }, { "id": "72", "guid": "6ac4abc9-e72b-4e19-9412-80fe38121ec5", "heading": "Export to CSV", "acceptanceCriteria": "Tool supports:
export filtered list of requirements to MS Excel
", "soThat": "I can reuse or update requirements in another application
", "status": "Verified", "type": "STORY" } ] } ] }, { "id": "4", "guid": "fc5a0688-ffa0-4d49-8f88-f6cb7ebe15c1", "heading": "Constraints", "type": "SEC", "children": [ { "id": "39", "guid": "03711176-9aac-4767-a58f-a9238495d0c4", "heading": "Startup Time", "acceptanceCriteria": "Tool starts in less than 10s even for large projects.
", "asAn": "Editor", "iWant": "quickly start the tool
", "soThat": "I do not need to wait long time for editing a project
", "status": "Verified", "type": "CON" }, { "id": "41", "guid": "4cb8d2ca-d47c-4666-8551-e8fb663c1667", "heading": "Edit Response Time", "acceptanceCriteria": "Tool updates view after any edit operation in a document with 10000 requirements in less than 1s.
", "asAn": "Editor", "iWant": "edit effectively requirements in large documents
", "soThat": "I can work without waiting for tool responses
", "status": "Verified", "type": "CON" }, { "id": "44", "guid": "c6d0adc9-ba8d-4f81-bb50-7199c07707fb", "heading": "Document Size", "acceptanceCriteria": "Tool can store documents with 10000 requirements and 100 attachments of total size 100 MB.
", "asAn": "Editor", "iWant": "create large requirements specifications
", "soThat": "I can capture all requirements in a single document even for complex system development projects
", "status": "Verified", "type": "CON" }, { "id": "42", "guid": "0264ef81-e5e4-405f-8dde-4dd74e8721a2", "heading": "Security", "acceptanceCriteria": "Tool does not send any project information to the internet without user consent.
", "asAn": "Editor", "iWant": "store confidential information in the tool
", "soThat": "I can be sure that no confidential information is compromised
", "status": "Verified", "type": "CON" }, { "id": "51", "guid": "12b51945-516b-46fe-991c-5980dc57d099", "heading": "Compatibility", "acceptanceCriteria": "Tool is installed and run on Windows, Linux and a Mac.
", "asAn": "Editor", "iWant": "install and run the tool on Windows, Linux or Mac operating system
", "soThat": "I can use the tool on any desktop PC or notebook.
", "status": "Verified", "type": "CON" } ] } ], "attributes": { "acceptanceCriteria": { "name": "Acceptance Criteria", "type": "xhtml" }, "asAn": { "name": "As a(n)", "type": "enum", "values": [ { "key": "Architect" }, { "key": "Editor" }, { "key": "Reviewer" } ] }, "estimation": { "name": "Estimation", "type": "int" }, "iWant": { "name": "I want to", "type": "xhtml" }, "instructions": { "help": true, "type": "xhtml" }, "priority": { "name": "Priority", "type": "enum", "values": [ { "key": "High" }, { "key": "Medium" }, { "key": "Low" } ] }, "risk": { "name": "Risk", "type": "enum", "values": [ { "key": "High" }, { "key": "Medium" }, { "key": "Low" } ] }, "soThat": { "name": "So that", "type": "xhtml" }, "status": { "name": "Status", "type": "enum", "values": [ { "key": "New" }, { "key": "Planned" }, { "key": "Implemented" }, { "key": "Verified" } ] }, "type": { "name": "Type", "type": "enum", "values": [ { "key": "SEC", "label": "Section" }, { "key": "INF", "label": "Information" }, { "key": "EPIC", "label": "Epic" }, { "key": "STORY", "label": "User Story" }, { "key": "CON", "label": "Constraint" } ] } }, "templateColumns": { "0d1271c7-6d97-4500-b709-d8847086d848": { "label": "Downstream Traceability", "template": "{{#if (eval type \"==\" \"STORY\")}}\n{{#if (hasInlinks \"satisfaction\")}}\n{{#eachInlinkWith type=\"satisfaction\"}}\n◂ {{#hyperlink}}{{docObjId}}{{/hyperlink}}: {{shortDescription maxLength=80}}\n{{#if (hasInlinks \"verification\")}}\n{{#eachInlinkWith type=\"verification\"}}\n
◂ {{#hyperlink}}{{docObjId}}{{/hyperlink}}: {{shortDescription maxLength=80}}\n{{/eachInlinkWith}}\n{{else}}\n
◂ Missing verification links!\n{{/if}}\n
◂ Missing satisfaction links!
\n{{/if}}\n{{/if}}" }, "dd7d52bc-d0a2-4bfe-99b2-c7daa90ea5a9": { "label": "Story", "template": "{{#if (eval (eval type \"==\" \"STORY\") \"||\" (eval type \"==\" \"CON\"))}}\n\nAs a(n) {{asAn}} I want to {{formatString iWant}} so that {{formatString soThat}}.\n
\n{{/if}}" } }, "views": { "Capture": { "columns": [ { "columnId": "id", "width": 102 }, { "columnId": "type", "width": 93 }, { "columnId": "description", "width": 314 }, { "columnId": "asAn", "width": 81 }, { "columnId": "iWant", "width": 186 }, { "columnId": "soThat", "width": 189 }, { "columnId": "acceptanceCriteria", "width": 226 } ] }, "Export": { "columns": [ { "columnId": "id", "width": 106 }, { "columnId": "description", "width": 382 }, { "templateColumnId": "dd7d52bc-d0a2-4bfe-99b2-c7daa90ea5a9", "width": 338 }, { "columnId": "acceptanceCriteria", "width": 407 } ] }, "Primary": { "columns": [ { "columnId": "id", "width": 99 }, { "columnId": "type", "width": 103 }, { "columnId": "description", "width": 386 }, { "templateColumnId": "dd7d52bc-d0a2-4bfe-99b2-c7daa90ea5a9", "width": 262 }, { "columnId": "acceptanceCriteria", "width": 248 }, { "columnId": "status", "width": 89 } ], "default": true }, "Review": { "columns": [ { "columnId": "id", "width": 92 }, { "columnId": "description", "width": 314 }, { "templateColumnId": "dd7d52bc-d0a2-4bfe-99b2-c7daa90ea5a9", "width": 252 }, { "columnId": "acceptanceCriteria", "width": 253 }, { "columnId": "discussion", "width": 332 } ] }, "Traceability": { "columns": [ { "columnId": "id", "width": 101 }, { "columnId": "type", "width": 101 }, { "columnId": "description", "width": 271 }, { "templateColumnId": "dd7d52bc-d0a2-4bfe-99b2-c7daa90ea5a9", "width": 290 }, { "templateColumnId": "0d1271c7-6d97-4500-b709-d8847086d848", "width": 515 } ] } } }, { "id": "ASVS", "guid": "f0775375-0043-46e7-9ae0-76fffc054ae6", "name": "OWASP Application Security Verification Standard 4.0.3", "lastId": 456, "createdOn": "2024-03-04T15:54:40.978Z", "createdBy": { "name": "Libor Bus", "email": "libor.bus@eccam.com", "company": "Eccam" }, "lastChangedOn": "2024-03-12T13:43:29.891Z", "lastChangedBy": { "name": "Libor Bus", "email": "libor.bus@eccam.com", "company": "Eccam" }, "data": [ { "id": "9", "guid": "10d07e58-362d-4435-bc9b-9cb3a4ceefd4", "text": "Version 4.0.3, October 2021
Copyright © 2008-2021 The OWASP Foundation. This document is released under the Creative Commons Attribution ShareAlike 3.0 license. For any reuse or distribution, you must make clear to others the license terms of this work.
", "type": "INFO", "attachments": [ "ASVS-9_1_license.png" ] }, { "id": "456", "guid": "02b12abe-6998-4dc6-b8ac-300474193778", "heading": "Introduction", "type": "INFO", "children": [ { "id": "6", "guid": "259e6030-ba4e-4f1c-aeaa-401b2a7c0312", "heading": "About the Standard", "type": "INFO", "children": [ { "id": "7", "guid": "46979230-473b-47ab-a543-9568142007c9", "text": "The Application Security Verification Standard is a list of application security requirements or tests that can be used by architects, developers, testers, security professionals, tool vendors, and consumers to define, build, test and verify secure applications.
", "type": "INFO" } ] }, { "id": "16", "guid": "7df0ecfe-e8a9-40d1-9aa3-70a2d722b918", "heading": "Preface", "type": "INFO", "children": [ { "id": "17", "guid": "95af2670-0b4a-466d-85eb-b09fbb26fbac", "text": "Welcome to the Application Security Verification Standard (ASVS) version 4.0. The ASVS is a community-driven effort to establish a framework of security requirements and controls that focus on defining the functional and non-functional security controls required when designing, developing and testing modern web applications and web services.
Version 4.0.3 is the third minor patch to v4.0 intended to fix spelling errors and make requirements clearer without making breaking changes such as materially changing requirements, strengthening requirements or adding requirements. However, some requirements may have been slightly weakened where we felt appropriate and some entirely redundant requirements have been removed (but without renumbering).
ASVS v4.0 is the culmination of community effort and industry feedback over the last decade. We have attempted to make it easier to adopt the ASVS for a variety of different use cases throughout any secure software development lifecycle.
We expect that there will most likely never be 100% agreement on the contents of any web application standard, including the ASVS. Risk analysis is always subjective to some extent, which creates a challenge when attempting to generalize in a one-size-fits-all standard. However, we hope that the latest updates made in this version are a step in the right direction, and enhance the concepts introduced in this critical industry standard.
", "type": "INFO" } ] } ] }, { "id": "20", "guid": "f1a5f5d4-982a-4d0d-b42f-996393015fa4", "heading": "Using the ASVS", "type": "INFO", "children": [ { "id": "21", "guid": "0a5805c2-6007-4cd6-bbab-c8ea8e55e3fb", "text": "ASVS has two main goals:
The Application Security Verification Standard defines three security verification levels, with each level increasing in depth.
Each ASVS level contains a list of security requirements. Each of these requirements can also be mapped to security-specific features and capabilities that must be built into software by developers.
Figure 1 - OWASP Application Security Verification Standard 4.0 Levels
Level 1 is the only level that is completely penetration testable using humans. All others require access to documentation, source code, configuration, and the people involved in the development process. However, even if L1 allows \"black box\" (no documentation and no source) testing to occur, it is not an effective assurance activity and should be actively discouraged. Malicious attackers have a great deal of time, most penetration tests are over within a couple of weeks. Defenders need to build in security controls, protect, find and resolve all weaknesses, and detect and respond to malicious actors in a reasonable time. Malicious actors have essentially infinite time and only require a single porous defense, a single weakness, or missing detection to succeed. Black box testing, often performed at the end of development, quickly, or not at all, is completely unable to cope with that asymmetry.
Over the last 30+ years, black box testing has proven over and over again to miss critical security issues that led directly to ever more massive breaches. We strongly encourage the use of a wide range of security assurance and verification, including replacing penetration tests with source code led (hybrid) penetration tests at Level 1, with full access to developers and documentation throughout the development process. Financial regulators do not tolerate external financial audits with no access to the books, sample transactions, or the people performing the controls. Industry and governments must demand the same standard of transparency in the software engineering field.
We strongly encourage the use of security tools within the development process itself. DAST and SAST tools can be used continuously by the build pipeline to find easy to find security issues that should never be present.
Automated tools and online scans are unable to complete more than half of the ASVS without human assistance. If comprehensive test automation for each build is required, then a combination of custom unit and integration tests, along with build initiated online scans are used. Business logic flaws and access control testing is only possible using human assistance. These should be turned into unit and integration tests.
", "type": "INFO", "attachments": [ "ASVS-23_1_asvs_40_levels.png" ] } ] }, { "id": "24", "guid": "d8541b30-94a6-443e-a42b-059c43347280", "heading": "How to use this standard", "type": "INFO", "children": [ { "id": "25", "guid": "98ffced0-7f97-4390-9fe0-aa2f1adec8b2", "text": "One of the best ways to use the Application Security Verification Standard is to use it as a blueprint to create a Secure Coding Checklist specific to your application, platform or organization. Tailoring the ASVS to your use cases will increase the focus on the security requirements that are most important to your projects and environments.
", "type": "INFO" }, { "id": "26", "guid": "e4e35c6f-a4a1-440f-8d8c-3a06981931c5", "heading": "Level 1 - First steps, automated, or whole of portfolio view", "type": "INFO", "children": [ { "id": "27", "guid": "03210941-221f-4715-9e84-4c1bfc545570", "text": "An application achieves ASVS Level 1 if it adequately defends against application security vulnerabilities that are easy to discover, and included in the OWASP Top 10 and other similar checklists.
Level 1 is the bare minimum that all applications should strive for. It is also useful as a first step in a multi-phase effort or when applications do not store or handle sensitive data and therefore do not need the more rigorous controls of Level 2 or 3. Level 1 controls can be checked either automatically by tools or simply manually without access to source code. We consider Level 1 the minimum required for all applications.
Threats to the application will most likely be from attackers who are using simple and low effort techniques to identify easy-to-find and easy-to-exploit vulnerabilities. This is in contrast to a determined attacker who will spend focused energy to specifically target the application. If data processed by your application has high value, you would rarely want to stop at a Level 1 review.
", "type": "INFO" } ] }, { "id": "28", "guid": "226bf1fa-bdfd-4455-9e5d-1f40b5f3a7ce", "heading": "Level 2 - Most applications", "type": "INFO", "children": [ { "id": "29", "guid": "49d3b42b-9874-42a9-900e-9daaa84ddcd7", "text": "An application achieves ASVS Level 2 (or Standard) if it adequately defends against most of the risks associated with software today.
Level 2 ensures that security controls are in place, effective, and used within the application. Level 2 is typically appropriate for applications that handle significant business-to-business transactions, including those that process healthcare information, implement business-critical or sensitive functions, or process other sensitive assets, or industries where integrity is a critical facet to protect their business, such as the game industry to thwart cheaters and game hacks.
Threats to Level 2 applications will typically be skilled and motivated attackers focusing on specific targets using tools and techniques that are highly practiced and effective at discovering and exploiting weaknesses within applications.
", "type": "INFO" } ] }, { "id": "30", "guid": "c8b1cd99-9644-4305-951c-57d74d7f2274", "heading": "Level 3 - High value, high assurance, or high safety", "type": "INFO", "children": [ { "id": "31", "guid": "7b0bd01e-3f25-4ff5-96c7-ae008bb651b0", "text": "ASVS Level 3 is the highest level of verification within the ASVS. This level is typically reserved for applications that require significant levels of security verification, such as those that may be found within areas of military, health and safety, critical infrastructure, etc.
Organizations may require ASVS Level 3 for applications that perform critical functions, where failure could significantly impact the organization's operations, and even its survivability. Example guidance on the application of ASVS Level 3 is provided below. An application achieves ASVS Level 3 (or Advanced) if it adequately defends against advanced application security vulnerabilities and also demonstrates principles of good security design.
An application at ASVS Level 3 requires more in depth analysis of architecture, coding, and testing than all the other levels. A secure application is modularized in a meaningful way (to facilitate resiliency, scalability, and most of all, layers of security), and each module (separated by network connection and/or physical instance) takes care of its own security responsibilities (defense in depth), that need to be properly documented. Responsibilities include controls for ensuring confidentiality (e.g. encryption), integrity (e.g. transactions, input validation), availability (e.g. handling load gracefully), authentication (including between systems), authorization, and auditing (logging).
", "type": "INFO" } ] } ] } ] }, { "id": "61", "guid": "2936b55c-08c2-4adf-ae1d-043415cec4e0", "heading": "Architecture, Design and Threat Modeling", "asvsId": "1", "help": "Control Objective
Security architecture has almost become a lost art in many organizations. The days of the enterprise architect have passed in the age of DevSecOps. The application security field must catch up and adopt agile security principles while re-introducing leading security architecture principles to software practitioners. Architecture is not an implementation, but a way of thinking about a problem that has potentially many different answers, and no one single \"correct\" answer. All too often, security is seen as inflexible and demanding that developers fix code in a particular way, when the developers may know a much better way to solve the problem. There is no single, simple solution for architecture, and to pretend otherwise is a disservice to the software engineering field.
A specific implementation of a web application is likely to be revised continuously throughout its lifetime, but the overall architecture will likely rarely change but evolve slowly. Security architecture is identical - we need authentication today, we will require authentication tomorrow, and we will need it five years from now. If we make sound decisions today, we can save a lot of effort, time, and money if we select and re-use architecturally compliant solutions. For example, a decade ago, multi-factor authentication was rarely implemented.
If developers had invested in a single, secure identity provider model, such as SAML federated identity, the identity provider could be updated to incorporate new requirements such as NIST 800-63 compliance, while not changing the interfaces of the original application. If many applications shared the same security architecture and thus that same component, they all benefit from this upgrade at once. However, SAML will not always remain as the best or most suitable authentication solution - it might need to be swapped out for other solutions as requirements change. Changes like this are either complicated, so costly as to necessitate a complete re-write, or outright impossible without security architecture.
In this chapter, the ASVS covers off the primary aspects of any sound security architecture: availability, confidentiality, processing integrity, non-repudiation, and privacy. Each of these security principles must be built in and be innate to all applications. It is critical to \"shift left\", starting with developer enablement with secure coding checklists, mentoring and training, coding and testing, building, deployment, configuration, and operations, and finishing with follow up independent testing to assure that all of the security controls are present and functional. The last step used to be everything we did as an industry, but that is no longer sufficient when developers push code into production tens or hundreds of times a day. Application security professionals must keep up with agile techniques, which means adopting developer tools, learning to code, and working with developers rather than criticizing the project months after everyone else has moved on.
References
For more information, see also:
Verify the use of a secure software development lifecycle that addresses security in all stages of development. (C1)
", "applicable": false, "asvsId": "1.1.1", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "64", "guid": "93dfbe32-b707-4719-ac12-5b1d26b4bd17", "text": "Verify the use of threat modeling for every design change or sprint planning to identify threats, plan for countermeasures, facilitate appropriate risk responses, and guide security testing.
", "applicable": false, "asvsId": "1.1.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "65", "guid": "cf26ec62-49db-48d0-acb6-d38489020010", "text": "Verify that all user stories and features contain functional security constraints, such as \"As a user, I should be able to view and edit my profile. I should not be able to view or edit anyone else's profile\"
", "applicable": false, "asvsId": "1.1.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "66", "guid": "824b5455-5aff-47e8-9ebe-e9d2f642a641", "text": "Verify documentation and justification of all the application's trust boundaries, components, and significant data flows.
", "applicable": false, "asvsId": "1.1.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "67", "guid": "f0d0cbeb-a704-4dfe-9031-f8dd237b95b1", "text": "Verify definition and security analysis of the application's high-level architecture and all connected remote services. (C1)
", "applicable": false, "asvsId": "1.1.5", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" }, { "id": "68", "guid": "9748fb27-3c99-4e08-bd10-2831d84379d5", "text": "Verify implementation of centralized, simple (economy of design), vetted, secure, and reusable security controls to avoid duplicate, missing, ineffective, or insecure controls. (C10)
", "applicable": false, "asvsId": "1.1.6", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 6, "type": "REQ" }, { "id": "69", "guid": "99f7f328-f217-4d04-b308-b955f714f62a", "text": "Verify availability of a secure coding checklist, security requirements, guideline, or policy to all developers and testers.
", "applicable": false, "asvsId": "1.1.7", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 7, "type": "REQ" } ] }, { "id": "70", "guid": "a1d6bf2f-0692-4d06-bf94-0836b11931e9", "heading": "Authentication Architecture", "asvsId": "1.2", "help": "When designing authentication, it doesn't matter if you have strong hardware enabled multi-factor authentication if an attacker can reset an account by calling a call center and answering commonly known questions. When proving identity, all authentication pathways must have the same strength.
", "ord": 2, "type": "SEC", "children": [ { "id": "71", "guid": "e019dcba-d51c-4787-b905-438079592dbb", "text": "Verify the use of unique or special low-privilege operating system accounts for all application components, services, and servers. (C3)
", "applicable": false, "asvsId": "1.2.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "72", "guid": "df1174cb-36c0-476b-9a26-c48d21cf0b76", "text": "Verify that communications between application components, including APIs, middleware and data layers, are authenticated. Components should have the least necessary privileges needed. (C3)
", "applicable": false, "asvsId": "1.2.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "73", "guid": "e8707b8f-f887-4705-b4eb-f0507e2cbf6a", "text": "Verify that the application uses a single vetted authentication mechanism that is known to be secure, can be extended to include strong authentication, and has sufficient logging and monitoring to detect account abuse or breaches.
", "applicable": false, "asvsId": "1.2.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "74", "guid": "8b3136fc-6fb3-4d21-9387-9c54b9b64e29", "text": "Verify that all authentication pathways and identity management APIs implement consistent authentication security control strength, such that there are no weaker alternatives per the risk of the application.
", "applicable": false, "asvsId": "1.2.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" } ] }, { "id": "75", "guid": "8a18f238-cc32-4b77-89c3-148b74154846", "heading": "Session Management Architecture", "asvsId": "1.3", "help": "This is a placeholder for future architectural requirements.
", "ord": 3, "type": "SEC" }, { "id": "76", "guid": "7076dcf5-a2d4-4ee2-8edf-6a90965bcbb9", "heading": "Access Control Architecture", "asvsId": "1.4", "ord": 4, "type": "SEC", "children": [ { "id": "77", "guid": "8fbde0e1-d213-42b1-9321-759a06dd05a8", "text": "Verify that trusted enforcement points, such as access control gateways, servers, and serverless functions, enforce access controls. Never enforce access controls on the client.
", "applicable": false, "asvsId": "1.4.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "80", "guid": "1aacc551-a6f5-4619-b70d-3ad4b0c2b995", "text": "Verify the application uses a single and well-vetted access control mechanism for accessing protected data and resources. All requests must pass through this single mechanism to avoid copy and paste or insecure alternative paths. (C7)
", "applicable": false, "asvsId": "1.4.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "81", "guid": "44a03263-4534-40d5-b778-b9ca753aac25", "text": "Verify that attribute or feature-based access control is used whereby the code checks the user's authorization for a feature/data item rather than just their role. Permissions should still be allocated using roles. (C7)
", "applicable": false, "asvsId": "1.4.5", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" } ] }, { "id": "82", "guid": "013fc36f-ea62-443f-a98c-cc044bac281d", "heading": "Input and Output Architecture", "asvsId": "1.5", "help": "In 4.0, we have moved away from the term \"server-side\" as a loaded trust boundary term. The trust boundary is still concerning - making decisions on untrusted browsers or client devices is bypassable. However, in mainstream architectural deployments today, the trust enforcement point has dramatically changed. Therefore, where the term \"trusted service layer\" is used in the ASVS, we mean any trusted enforcement point, regardless of location, such as a microservice, serverless API, server-side, a trusted API on a client device that has secure boot, partner or external APIs, and so on.
The \"untrusted client\" term here refers to client-side technologies that render the presentation layer, commonly refered to as 'front-end' technologies. The term \"serialization\" here not only refers to sending data over the wire like an array of values or taking and reading a JSON structure, but also passing complex objects which can contain logic.
", "ord": 5, "type": "SEC", "children": [ { "id": "83", "guid": "7e9b5ea6-4ff9-441c-99d4-ff97910fef43", "text": "Verify that input and output requirements clearly define how to handle and process data based on type, content, and applicable laws, regulations, and other policy compliance.
", "applicable": false, "asvsId": "1.5.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "84", "guid": "cc28c0b2-189d-487d-9745-d724bbd7aa84", "text": "Verify that serialization is not used when communicating with untrusted clients. If this is not possible, ensure that adequate integrity controls (and possibly encryption if sensitive data is sent) are enforced to prevent deserialization attacks including object injection.
", "applicable": false, "asvsId": "1.5.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "85", "guid": "277077b4-52f4-4f19-b9fd-4d513849fcd4", "text": "Verify that input validation is enforced on a trusted service layer. (C5)
", "applicable": false, "asvsId": "1.5.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "86", "guid": "a07fde55-b953-4c5d-804f-6bc82d4b1203", "text": "Verify that output encoding occurs close to or by the interpreter for which it is intended. (C4)
", "applicable": false, "asvsId": "1.5.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" } ] }, { "id": "87", "guid": "4fec1f46-d96c-4af2-833e-58d6b6c8667f", "heading": "Cryptographic Architecture", "asvsId": "1.6", "help": "Applications need to be designed with strong cryptographic architecture to protect data assets as per their classification. Encrypting everything is wasteful, not encrypting anything is legally negligent. A balance must be struck, usually during architectural or high level design, design sprints or architectural spikes. Designing cryptography as you go or retrofitting it will inevitably cost much more to implement securely than simply building it in from the start.
Architectural requirements are intrinsic to the entire code base, and thus difficult to unit or integrate test. Architectural requirements require consideration in coding standards, throughout the coding phase, and should be reviewed during security architecture, peer or code reviews, or retrospectives.
", "ord": 6, "type": "SEC", "children": [ { "id": "88", "guid": "a92bcd7d-8b13-46c4-8ab6-c8bce48bf48a", "text": "Verify that there is an explicit policy for management of cryptographic keys and that a cryptographic key lifecycle follows a key management standard such as NIST SP 800-57.
", "applicable": false, "asvsId": "1.6.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "89", "guid": "c8c3a3d2-eea7-46af-8f8d-1ad5592170d6", "text": "Verify that consumers of cryptographic services protect key material and other secrets by using key vaults or API based alternatives.
", "applicable": false, "asvsId": "1.6.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "90", "guid": "ab6a8356-fe70-4cff-a599-265b438cbb85", "text": "Verify that all keys and passwords are replaceable and are part of a well-defined process to re-encrypt sensitive data.
", "applicable": false, "asvsId": "1.6.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "91", "guid": "3a59c643-35bc-4cdd-9f09-4971dcd4b7c2", "text": "Verify that the architecture treats client-side secrets--such as symmetric keys, passwords, or API tokens--as insecure and never uses them to protect or access sensitive data.
", "applicable": false, "asvsId": "1.6.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" } ] }, { "id": "92", "guid": "9e19927c-8f68-45f6-86a0-55e9c0ac007f", "heading": "Errors, Logging and Auditing Architecture", "asvsId": "1.7", "ord": 7, "type": "SEC", "children": [ { "id": "93", "guid": "81e19f56-d14e-4c40-b98e-3f6b1b2357a6", "text": "Verify that a common logging format and approach is used across the system. (C9)
", "applicable": false, "asvsId": "1.7.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "94", "guid": "462c99ee-649f-49fa-8d44-d4736f40bab1", "text": "Verify that logs are securely transmitted to a preferably remote system for analysis, detection, alerting, and escalation. (C9)
", "applicable": false, "asvsId": "1.7.2", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" } ] }, { "id": "95", "guid": "5d660bed-242b-45ce-b672-485832b1a70f", "heading": "Data Protection and Privacy Architecture", "asvsId": "1.8", "ord": 8, "type": "SEC", "children": [ { "id": "96", "guid": "ae9fb880-2fe2-4797-86af-35d4cccd64a5", "text": "Verify that all sensitive data is identified and classified into protection levels.
", "applicable": false, "asvsId": "1.8.1", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "97", "guid": "d409089b-d7ea-4555-be05-ff31dfc1e28b", "text": "Verify that all protection levels have an associated set of protection requirements, such as encryption requirements, integrity requirements, retention, privacy and other confidentiality requirements, and that these are applied in the architecture.
", "applicable": false, "asvsId": "1.8.2", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" } ] }, { "id": "98", "guid": "27dff729-fd50-41dd-93e5-c21e36f25dd8", "heading": "Communications Architecture", "asvsId": "1.9", "ord": 9, "type": "SEC", "children": [ { "id": "99", "guid": "d7dacfaa-6741-40c1-ae4c-811c34a59b47", "text": "Verify the application encrypts communications between components, particularly when these components are in different containers, systems, sites, or cloud providers. (C3)
", "applicable": false, "asvsId": "1.9.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "100", "guid": "9785e690-7392-48ed-a964-96689e8269ca", "text": "Verify that application components verify the authenticity of each side in a communication link to prevent person-in-the-middle attacks. For example, application components should validate TLS certificates and chains.
", "applicable": false, "asvsId": "1.9.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" } ] }, { "id": "101", "guid": "ac423cf4-529d-4097-a583-cd9022c7b296", "heading": "Malicious Software Architecture", "asvsId": "1.10", "ord": 10, "type": "SEC", "children": [ { "id": "102", "guid": "07df6682-13d3-4c9e-801e-e01ca8575a56", "text": "Verify that a source code control system is in use, with procedures to ensure that check-ins are accompanied by issues or change tickets. The source code control system should have access control and identifiable users to allow traceability of any changes.
", "applicable": false, "asvsId": "1.10.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" } ] }, { "id": "103", "guid": "25969fe9-df1c-466f-b3bb-5a3f8e440917", "heading": "Business Logic Architecture", "asvsId": "1.11", "ord": 11, "type": "SEC", "children": [ { "id": "104", "guid": "d80e3344-a1da-4503-8c78-2941ade05b14", "text": "Verify the definition and documentation of all application components in terms of the business or security functions they provide.
", "applicable": false, "asvsId": "1.11.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "105", "guid": "c5a579b6-a9c1-4676-84d3-f66267fd18a0", "text": "Verify that all high-value business logic flows, including authentication, session management and access control, do not share unsynchronized state.
", "applicable": false, "asvsId": "1.11.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "106", "guid": "ca3eb4a7-e204-4476-a704-41e5f7277868", "text": "Verify that all high-value business logic flows, including authentication, session management and access control are thread safe and resistant to time-of-check and time-of-use race conditions.
", "applicable": false, "asvsId": "1.11.3", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" } ] }, { "id": "107", "guid": "c95fd369-263b-4b92-bf8a-f69b983f47c5", "heading": "Secure File Upload Architecture", "asvsId": "1.12", "ord": 12, "type": "SEC", "children": [ { "id": "109", "guid": "0d4265f1-6dd2-4910-9cca-7ecf0c9a0fd9", "text": "Verify that user-uploaded files - if required to be displayed or downloaded from the application - are served by either octet stream downloads, or from an unrelated domain, such as a cloud file storage bucket. Implement a suitable Content Security Policy (CSP) to reduce the risk from XSS vectors or other attacks from the uploaded file.
", "applicable": false, "asvsId": "1.12.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" } ] }, { "id": "110", "guid": "a8782342-d646-4df0-b344-72cb0de3fcbc", "heading": "API Architecture", "asvsId": "1.13", "help": "This is a placeholder for future architectural requirements.
", "ord": 13, "type": "SEC" }, { "id": "111", "guid": "061a0874-49bf-496d-9b15-fef74655b139", "heading": "Configuration Architecture", "asvsId": "1.14", "ord": 14, "type": "SEC", "children": [ { "id": "112", "guid": "246f0e5c-ecd5-4193-bb76-d791a16363d3", "text": "Verify the segregation of components of differing trust levels through well-defined security controls, firewall rules, API gateways, reverse proxies, cloud-based security groups, or similar mechanisms.
", "applicable": false, "asvsId": "1.14.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "113", "guid": "68ae8976-b479-4a7f-9a28-b624d3e26232", "text": "Verify that binary signatures, trusted connections, and verified endpoints are used to deploy binaries to remote devices.
", "applicable": false, "asvsId": "1.14.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "114", "guid": "cb8397f0-8eba-4a85-9f0b-a9e535af99fb", "text": "Verify that the build pipeline warns of out-of-date or insecure components and takes appropriate actions.
", "applicable": false, "asvsId": "1.14.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "115", "guid": "80745a5e-ac26-45f3-b535-c4774d1a78a2", "text": "Verify that the build pipeline contains a build step to automatically build and verify the secure deployment of the application, particularly if the application infrastructure is software defined, such as cloud environment build scripts.
", "applicable": false, "asvsId": "1.14.4", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "116", "guid": "da3f9738-44c5-4438-9b95-cd8d74ca1d8f", "text": "Verify that application deployments adequately sandbox, containerize and/or isolate at the network level to delay and deter attackers from attacking other applications, especially when they are performing sensitive or dangerous actions such as deserialization. (C5)
", "applicable": false, "asvsId": "1.14.5", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" }, { "id": "117", "guid": "7a0119bf-5ba4-471d-a13a-94d3282ed6da", "text": "Verify the application does not use unsupported, insecure, or deprecated client-side technologies such as NSAPI plugins, Flash, Shockwave, ActiveX, Silverlight, NACL, or client-side Java applets.
", "applicable": false, "asvsId": "1.14.6", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 6, "type": "REQ" } ] } ] }, { "id": "118", "guid": "b51b74d2-53d0-4a21-961c-bdb880ea60d9", "heading": "Authentication", "asvsId": "2", "help": "Control Objective
Authentication is the act of establishing, or confirming, someone (or something) as authentic and that claims made by a person or about a device are correct, resistant to impersonation, and prevent recovery or interception of passwords.
When the ASVS was first released, username + password was the most common form of authentication outside of high security systems. Multi-factor Authentication (MFA) was commonly accepted in security circles but rarely required elsewhere. As the number of password breaches increased, the idea that usernames are somehow confidential and passwords unknown, rendered many security controls untenable. For example, NIST 800-63 considers usernames and Knowledge Based Authentication (KBA) as public information, SMS and email notifications as \"restricted\" authenticator types , and passwords as pre-breached. This reality renders knowledge based authenticators, SMS and email recovery, password history, complexity, and rotation controls useless. These controls always have been less than helpful, often forcing users to come up with weak passwords every few months, but with the release of over 5 billion username and password breaches, it's time to move on.
Of all the chapters in the ASVS, the authentication and session management chapters have changed the most. Adoption of effective, evidence-based leading practice will be challenging for many, and that's perfectly okay. We have to start the transition to a post-password future now.
NIST 800-63 - Modern, evidence-based authentication standard
NIST 800-63b is a modern, evidence-based standard, and represents the best advice available, regardless of applicability. The standard is helpful for all organizations all over the world but is particularly relevant to US agencies and those dealing with US agencies.
NIST 800-63 terminology can be a little confusing at first, especially if you're only used to username + password authentication. Advancements in modern authentication are necessary, so we have to introduce terminology that will become commonplace in the future, but we do understand the difficulty in understanding until the industry settles on these new terms. We have provided a glossary at the end of this chapter to assist. We have rephrased many requirements to satisfy the intent of the requirement, rather than the letter of the requirement. For example, the ASVS uses the term \"password\" when NIST uses \"memorized secret\" throughout this standard.
ASVS V2 Authentication, V3 Session Management, and to a lesser extent, V4 Access Controls have been adapted to be a compliant subset of selected NIST 800-63b controls, focused around common threats and commonly exploited authentication weaknesses. Where full NIST 800-63 compliance is required, please consult NIST 800-63.
Selecting an appropriate NIST AAL Level
The Application Security Verification Standard has tried to map ASVS L1 to NIST AAL1 requirements, L2 to AAL2, and L3 to AAL3. However, the approach of ASVS Level 1 as \"essential\" controls may not necessarily be the correct AAL level to verify an application or API. For example, if the application is a Level 3 application or has regulatory requirements to be AAL3, Level 3 should be chosen in chapters V2 and V3 Session Management. The choice of NIST compliant Authentication Assertion Level (AAL) should be performed as per NIST 800-63b guidelines as set out in Selecting AAL in NIST 800-63b Section 6.2.
Legend
Applications can always exceed the current level's requirements, especially if modern authentication is on an application's roadmap. Previously, the ASVS has required mandatory MFA. NIST does not require mandatory MFA. Therefore, we have used an optional designation in this chapter to indicate where the ASVS encourages but does not require a control. The following keys are used throughout this standard:
| Mark | Description |
|---|---|
| Not required | |
| o | Recommended, but not required |
| ✓ | Required |
Additional US Agency Requirements
US Agencies have mandatory requirements concerning NIST 800-63. The Application Security Verification Standard has always been about the 80% of controls that apply to nearly 100% of apps, and not the last 20% of advanced controls or those that have limited applicability. As such, the ASVS is a strict subset of NIST 800-63, especially for IAL1/2 and AAL1/2 classifications, but is not sufficiently comprehensive, particularly concerning IAL3/AAL3 classifications.
We strongly urge US government agencies to review and implement NIST 800-63 in its entirety.
Glossary of terms
| Term | Meaning |
|---|---|
| CSP | Credential Service Provider also called an Identity Provider |
| Authenticator | Code that authenticates a password, token, MFA, federated assertion, and so on. |
| Verifier | \"An entity that verifies the claimant's identity by verifying the claimant's possession and control of one or two authenticators using an authentication protocol. To do this, the verifier may also need to validate credentials that link the authenticator(s) to the subscriber's identifier and check their status\" |
| OTP | One-time password |
| SFA | Single-factor authenticators, such as something you know (memorized secrets, passwords, passphrases, PINs), something you are (biometrics, fingerprint, face scans), or something you have (OTP tokens, a cryptographic device such as a smart card), |
| MFA | Multi-factor authentication, which includes two or more single factors |
References
For more information, see also:
Passwords, called \"Memorized Secrets\" by NIST 800-63, include passwords, PINs, unlock patterns, pick the correct kitten or another image element, and passphrases. They are generally considered \"something you know\", and often used as single-factor authenticators. There are significant challenges to the continued use of single-factor authentication, including billions of valid usernames and passwords disclosed on the Internet, default or weak passwords, rainbow tables and ordered dictionaries of the most common passwords.
Applications should strongly encourage users to enroll in multi-factor authentication, and should allow users to re-use tokens they already possess, such as FIDO or U2F tokens, or link to a credential service provider that provides multi-factor authentication.
Credential Service Providers (CSPs) provide federated identity for users. Users will often have more than one identity with multiple CSPs, such as an enterprise identity using Azure AD, Okta, Ping Identity or Google, or consumer identity using Facebook, Twitter, Google, or WeChat, to name a just few common alternatives. This list is not an endorsement of these companies or services, but simply an encouragement for developers to consider the reality that many users have many established identities. Organizations should consider integrating with existing user identities, as per the risk profile of the CSP's strength of identity proofing. For example, it is unlikely a government organization would accept a social media identity as a login for sensitive systems, as it is easy to create fake or throw away identities, whereas a mobile game company may well need to integrate with major social media platforms to grow their active player base.
Note: The goal of allowing the user to view their password or see the last character temporarily is to improve the usability of credential entry, particularly around the use of longer passwords, passphrases, and password managers. Another reason for including the requirement is to deter or prevent test reports unnecessarily requiring organizations to override built-in platform password field behavior to remove this modern user-friendly security experience.
", "ord": 1, "type": "SEC", "children": [ { "id": "120", "guid": "0302f071-ebdf-4208-bc68-60477df67f70", "text": "Verify that user set passwords are at least 12 characters in length (after multiple spaces are combined). (C6)
", "applicable": false, "asvsId": "2.1.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 1, "type": "REQ" }, { "id": "121", "guid": "4930f113-73bf-47d9-b16c-8d92fb8c1a35", "text": "Verify that passwords of at least 64 characters are permitted, and that passwords of more than 128 characters are denied. (C6)
", "applicable": false, "asvsId": "2.1.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 2, "type": "REQ" }, { "id": "122", "guid": "dfbc7ac8-8504-49be-bbbf-c5cb95c0863e", "text": "Verify that password truncation is not performed. However, consecutive multiple spaces may be replaced by a single space. (C6)
", "applicable": false, "asvsId": "2.1.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 3, "type": "REQ" }, { "id": "123", "guid": "2cb034e3-60aa-4aed-878b-eb8a39f73efa", "text": "Verify that any printable Unicode character, including language neutral characters such as spaces and Emojis are permitted in passwords.
", "applicable": false, "asvsId": "2.1.4", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 4, "type": "REQ" }, { "id": "124", "guid": "efb00807-edad-4f0b-bc1c-1712610954a9", "text": "Verify users can change their password.
", "applicable": false, "asvsId": "2.1.5", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 5, "type": "REQ" }, { "id": "125", "guid": "2ecf242c-9d91-4c4a-b94e-8f3aeb2c2205", "text": "Verify that password change functionality requires the user's current and new password.
", "applicable": false, "asvsId": "2.1.6", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 6, "type": "REQ" }, { "id": "126", "guid": "ea31d3ca-f769-4034-b76b-1145290e1564", "text": "Verify that passwords submitted during account registration, login, and password change are checked against a set of breached passwords either locally (such as the top 1,000 or 10,000 most common passwords which match the system's password policy) or using an external API. If using an API a zero knowledge proof or other mechanism should be used to ensure that the plain text password is not sent or used in verifying the breach status of the password. If the password is breached, the application must require the user to set a new non-breached password. (C6)
", "applicable": false, "asvsId": "2.1.7", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 7, "type": "REQ" }, { "id": "127", "guid": "915d48e8-7ba9-4131-8bbd-f03f0cb91488", "text": "Verify that a password strength meter is provided to help users set a stronger password.
", "applicable": false, "asvsId": "2.1.8", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 8, "type": "REQ" }, { "id": "128", "guid": "5443f31d-1ec5-4c1a-85c2-9a25c70e665b", "text": "Verify that there are no password composition rules limiting the type of characters permitted. There should be no requirement for upper or lower case or numbers or special characters. (C6)
", "applicable": false, "asvsId": "2.1.9", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 9, "type": "REQ" }, { "id": "129", "guid": "f95a5f02-9c07-4997-8a51-b670bbf95a3a", "text": "Verify that there are no periodic credential rotation or password history requirements.
", "applicable": false, "asvsId": "2.1.10", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 10, "type": "REQ" }, { "id": "130", "guid": "054af149-89a6-4d37-a2f9-de8fae9810ef", "text": "Verify that \"paste\" functionality, browser password helpers, and external password managers are permitted.
", "applicable": false, "asvsId": "2.1.11", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 11, "type": "REQ" }, { "id": "131", "guid": "df77388f-0dbd-46e7-95de-9e624cc5dc23", "text": "Verify that the user can choose to either temporarily view the entire masked password, or temporarily view the last typed character of the password on platforms that do not have this as built-in functionality.
", "applicable": false, "asvsId": "2.1.12", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 12, "type": "REQ" } ] }, { "id": "132", "guid": "301b35d9-a54b-4728-9f08-31a13a030e14", "heading": "General Authenticator Security", "asvsId": "2.2", "help": "Authenticator agility is essential to future-proof applications. Refactor application verifiers to allow additional authenticators as per user preferences, as well as allowing retiring deprecated or unsafe authenticators in an orderly fashion.
NIST considers email and SMS as \"restricted\" authenticator types, and they are likely to be removed from NIST 800-63 and thus the ASVS at some point the future. Applications should plan a roadmap that does not require the use of email or SMS.
", "ord": 2, "type": "SEC", "children": [ { "id": "133", "guid": "79f53d08-e3b0-4c6d-ab5b-acf3b7f39845", "text": "Verify that anti-automation controls are effective at mitigating breached credential testing, brute force, and account lockout attacks. Such controls include blocking the most common breached passwords, soft lockouts, rate limiting, CAPTCHA, ever increasing delays between attempts, IP address restrictions, or risk-based restrictions such as location, first login on a device, recent attempts to unlock the account, or similar. Verify that no more than 100 failed attempts per hour is possible on a single account.
", "applicable": false, "asvsId": "2.2.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "5.2.2 / 5.1.1.2 / 5.1.4.2 / 5.1.5.2
", "ord": 1, "type": "REQ" }, { "id": "134", "guid": "d132c3de-8983-495f-9a37-720c494bdcf6", "text": "Verify that the use of weak authenticators (such as SMS and email) is limited to secondary verification and transaction approval and not as a replacement for more secure authentication methods. Verify that stronger methods are offered before weak methods, users are aware of the risks, or that proper measures are in place to limit the risks of account compromise.
", "applicable": false, "asvsId": "2.2.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 2, "type": "REQ" }, { "id": "135", "guid": "26ac8503-cc45-4cb3-b712-d78c71a47707", "text": "Verify that secure notifications are sent to users after updates to authentication details, such as credential resets, email or address changes, logging in from unknown or risky locations. The use of push notifications - rather than SMS or email - is preferred, but in the absence of push notifications, SMS or email is acceptable as long as no sensitive information is disclosed in the notification.
", "applicable": false, "asvsId": "2.2.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "136", "guid": "b5beaed0-5880-43fb-9860-a547849e41fe", "text": "Verify impersonation resistance against phishing, such as the use of multi-factor authentication, cryptographic devices with intent (such as connected keys with a push to authenticate), or at higher AAL levels, client-side certificates.
", "applicable": false, "asvsId": "2.2.4", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 4, "type": "REQ" }, { "id": "137", "guid": "dd5ee0d6-480c-480c-8b38-27fce625b203", "text": "Verify that where a Credential Service Provider (CSP) and the application verifying authentication are separated, mutually authenticated TLS is in place between the two endpoints.
", "applicable": false, "asvsId": "2.2.5", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 5, "type": "REQ" }, { "id": "138", "guid": "845026bd-f8ba-45c2-9133-d197b60eb40e", "text": "Verify replay resistance through the mandated use of One-time Passwords (OTP) devices, cryptographic authenticators, or lookup codes.
", "applicable": false, "asvsId": "2.2.6", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 6, "type": "REQ" }, { "id": "139", "guid": "d08eaaf1-4a09-495a-9fa7-1444c81ef67a", "text": "Verify intent to authenticate by requiring the entry of an OTP token or user-initiated action such as a button press on a FIDO hardware key.
", "applicable": false, "asvsId": "2.2.7", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 7, "type": "REQ" } ] }, { "id": "140", "guid": "35b11aa4-59d6-44f3-9e3a-b6380820dacf", "heading": "Authenticator Lifecycle", "asvsId": "2.3", "help": "Authenticators are passwords, soft tokens, hardware tokens, and biometric devices. The lifecycle of authenticators is critical to the security of an application - if anyone can self-register an account with no evidence of identity, there can be little trust in the identity assertion. For social media sites like Reddit, that's perfectly okay. For banking systems, a greater focus on the registration and issuance of credentials and devices is critical to the security of the application.
Note: Passwords are not to have a maximum lifetime or be subject to password rotation. Passwords should be checked for being breached, not regularly replaced.
", "ord": 3, "type": "SEC", "children": [ { "id": "141", "guid": "99ee36ba-ae1d-41a2-9229-fa91dd9cab5d", "text": "Verify system generated initial passwords or activation codes SHOULD be securely randomly generated, SHOULD be at least 6 characters long, and MAY contain letters and numbers, and expire after a short period of time. These initial secrets must not be permitted to become the long term password.
", "applicable": false, "asvsId": "2.3.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 1, "type": "REQ" }, { "id": "142", "guid": "e8fb2c38-5aed-4ec8-b7c7-822b751a7dd9", "text": "Verify that enrollment and use of user-provided authentication devices are supported, such as a U2F or FIDO tokens.
", "applicable": false, "asvsId": "2.3.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 2, "type": "REQ" }, { "id": "143", "guid": "7c0d9c4c-4bce-45b3-869d-937cb6844a94", "text": "Verify that renewal instructions are sent with sufficient time to renew time bound authenticators.
", "applicable": false, "asvsId": "2.3.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 3, "type": "REQ" } ] }, { "id": "144", "guid": "915296a1-39f1-4ea8-887a-7b0da02698f5", "heading": "Credential Storage", "asvsId": "2.4", "help": "Architects and developers should adhere to this section when building or refactoring code. This section can only be fully verified using source code review or through secure unit or integration tests. Penetration testing cannot identify any of these issues.
The list of approved one-way key derivation functions is detailed in NIST 800-63 B section 5.1.1.2, and in BSI Kryptographische Verfahren: Empfehlungen und Schlussellängen (2018). The latest national or regional algorithm and key length standards can be chosen in place of these choices.
This section cannot be penetration tested, so controls are not marked as L1. However, this section is of vital importance to the security of credentials if they are stolen, so if forking the ASVS for an architecture or coding guideline or source code review checklist, please place these controls back to L1 in your private version.
Where US standards are mentioned, a regional or local standard can be used in place of or in addition to the US standard as required.
", "ord": 4, "type": "SEC", "children": [ { "id": "145", "guid": "67bf0f4b-11f6-4bb7-92e4-0bd565f580d1", "text": "Verify that passwords are stored in a form that is resistant to offline attacks. Passwords SHALL be salted and hashed using an approved one-way key derivation or password hashing function. Key derivation and password hashing functions take a password, a salt, and a cost factor as inputs when generating a password hash. (C6)
", "applicable": false, "asvsId": "2.4.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 1, "type": "REQ" }, { "id": "146", "guid": "cd19fbe3-3461-43a8-9738-004746abab4c", "text": "Verify that the salt is at least 32 bits in length and be chosen arbitrarily to minimize salt value collisions among stored hashes. For each credential, a unique salt value and the resulting hash SHALL be stored. (C6)
", "applicable": false, "asvsId": "2.4.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 2, "type": "REQ" }, { "id": "147", "guid": "2e65f69c-8784-4294-add2-b93f15294621", "text": "Verify that if PBKDF2 is used, the iteration count SHOULD be as large as verification server performance will allow, typically at least 100,000 iterations. (C6)
", "applicable": false, "asvsId": "2.4.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 3, "type": "REQ" }, { "id": "148", "guid": "a96fddcb-861f-4329-9b19-964fcbfd5380", "text": "Verify that if bcrypt is used, the work factor SHOULD be as large as verification server performance will allow, with a minimum of 10. (C6)
", "applicable": false, "asvsId": "2.4.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 4, "type": "REQ" }, { "id": "149", "guid": "c479ec2d-6d98-4a9a-a310-a7c67c087662", "text": "Verify that an additional iteration of a key derivation function is performed, using a salt value that is secret and known only to the verifier. Generate the salt value using an approved random bit generator [SP 800-90Ar1] and provide at least the minimum security strength specified in the latest revision of SP 800-131A. The secret salt value SHALL be stored separately from the hashed passwords (e.g., in a specialized device like a hardware security module).
", "applicable": false, "asvsId": "2.4.5", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 5, "type": "REQ" } ] }, { "id": "150", "guid": "283403b0-3873-4c4e-89e7-923af7bff888", "heading": "Credential Recovery", "asvsId": "2.5", "ord": 5, "type": "SEC", "children": [ { "id": "151", "guid": "753a21e6-61bc-471a-a30f-5f2da87e5463", "text": "Verify that a system generated initial activation or recovery secret is not sent in clear text to the user. (C6)
", "applicable": false, "asvsId": "2.5.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 1, "type": "REQ" }, { "id": "152", "guid": "497d0ceb-ef08-4ef0-a256-cd4a55ca4490", "text": "Verify password hints or knowledge-based authentication (so-called \"secret questions\") are not present.
", "applicable": false, "asvsId": "2.5.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 2, "type": "REQ" }, { "id": "153", "guid": "92aa3593-fa50-487e-9fd4-1fdd030d0121", "text": "Verify password credential recovery does not reveal the current password in any way. (C6)
", "applicable": false, "asvsId": "2.5.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 3, "type": "REQ" }, { "id": "154", "guid": "b75ef1a7-43e2-4ba7-af23-b2d8b2913ba6", "text": "Verify shared or default accounts are not present (e.g. \"root\", \"admin\", or \"sa\").
", "applicable": false, "asvsId": "2.5.4", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 4, "type": "REQ" }, { "id": "155", "guid": "54542b54-255e-42e0-81ab-253467617467", "text": "Verify that if an authentication factor is changed or replaced, that the user is notified of this event.
", "applicable": false, "asvsId": "2.5.5", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 5, "type": "REQ" }, { "id": "156", "guid": "1edf8bdc-b576-4ce0-a47c-6e2ef98e94b3", "text": "Verify forgotten password, and other recovery paths use a secure recovery mechanism, such as time-based OTP (TOTP) or other soft token, mobile push, or another offline recovery mechanism. (C6)
", "applicable": false, "asvsId": "2.5.6", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 6, "type": "REQ" }, { "id": "157", "guid": "94467ed7-a4e0-4336-9f7c-8ed17bcbcb5a", "text": "Verify that if OTP or multi-factor authentication factors are lost, that evidence of identity proofing is performed at the same level as during enrollment.
", "applicable": false, "asvsId": "2.5.7", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 7, "type": "REQ" } ] }, { "id": "158", "guid": "a66ee7d8-0d0e-4784-bf3b-3afc54d6af52", "heading": "Look-up Secret Verifier", "asvsId": "2.6", "help": "Look up secrets are pre-generated lists of secret codes, similar to Transaction Authorization Numbers (TAN), social media recovery codes, or a grid containing a set of random values. These are distributed securely to users. These lookup codes are used once, and once all used, the lookup secret list is discarded. This type of authenticator is considered \"something you have\".
", "ord": 6, "type": "SEC", "children": [ { "id": "159", "guid": "b9b8c2f3-c2ad-4340-8f0c-de9b118eeed2", "text": "Verify that lookup secrets can be used only once.
", "applicable": false, "asvsId": "2.6.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 1, "type": "REQ" }, { "id": "160", "guid": "104e5b41-b3f8-4cc9-a5cd-7b1a6936cee6", "text": "Verify that lookup secrets have sufficient randomness (112 bits of entropy), or if less than 112 bits of entropy, salted with a unique and random 32-bit salt and hashed with an approved one-way hash.
", "applicable": false, "asvsId": "2.6.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 2, "type": "REQ" }, { "id": "161", "guid": "299d7e68-c3cd-456c-afb2-3a1335d95ae5", "text": "Verify that lookup secrets are resistant to offline attacks, such as predictable values.
", "applicable": false, "asvsId": "2.6.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 3, "type": "REQ" } ] }, { "id": "162", "guid": "50f6b3de-fc1a-4b45-b204-63a26114aed6", "heading": "Out of Band Verifier", "asvsId": "2.7", "help": "In the past, a common out of band verifier would have been an email or SMS containing a password reset link. Attackers use this weak mechanism to reset accounts they don't yet control, such as taking over a person's email account and re-using any discovered reset links. There are better ways to handle out of band verification.
Secure out of band authenticators are physical devices that can communicate with the verifier over a secure secondary channel. Examples include push notifications to mobile devices. This type of authenticator is considered \"something you have\". When a user wishes to authenticate, the verifying application sends a message to the out of band authenticator via a connection to the authenticator directly or indirectly through a third party service. The message contains an authentication code (typically a random six digit number or a modal approval dialog). The verifying application waits to receive the authentication code through the primary channel and compares the hash of the received value to the hash of the original authentication code. If they match, the out of band verifier can assume that the user has authenticated.
The ASVS assumes that only a few developers will be developing new out of band authenticators, such as push notifications, and thus the following ASVS controls apply to verifiers, such as authentication API, applications, and single sign-on implementations. If developing a new out of band authenticator, please refer to NIST 800-63B § 5.1.3.1.
Unsafe out of band authenticators such as e-mail and VOIP are not permitted. PSTN and SMS authentication are currently \"restricted\" by NIST and should be deprecated in favor of push notifications or similar. If you need to use telephone or SMS out of band authentication, please see § 5.1.3.3.
", "ord": 7, "type": "SEC", "children": [ { "id": "163", "guid": "6c649f42-10a0-4c9c-ae25-870913ab2e1c", "text": "Verify that clear text out of band (NIST \"restricted\") authenticators, such as SMS or PSTN, are not offered by default, and stronger alternatives such as push notifications are offered first.
", "applicable": false, "asvsId": "2.7.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 1, "type": "REQ" }, { "id": "164", "guid": "70608e2d-c0b1-46d1-9c41-ce12eba4edb5", "text": "Verify that the out of band verifier expires out of band authentication requests, codes, or tokens after 10 minutes.
", "applicable": false, "asvsId": "2.7.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 2, "type": "REQ" }, { "id": "165", "guid": "03ba23a5-fcf1-48ee-9588-0760f6a55b75", "text": "Verify that the out of band verifier authentication requests, codes, or tokens are only usable once, and only for the original authentication request.
", "applicable": false, "asvsId": "2.7.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 3, "type": "REQ" }, { "id": "166", "guid": "036aee14-ba6e-4a3c-9da4-b5465938b156", "text": "Verify that the out of band authenticator and verifier communicates over a secure independent channel.
", "applicable": false, "asvsId": "2.7.4", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 4, "type": "REQ" }, { "id": "167", "guid": "72841142-9de2-43e4-b462-03fc9c268e56", "text": "Verify that the out of band verifier retains only a hashed version of the authentication code.
", "applicable": false, "asvsId": "2.7.5", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 5, "type": "REQ" }, { "id": "168", "guid": "cdf671cc-f6a9-4a61-80b8-2bad95668687", "text": "Verify that the initial authentication code is generated by a secure random number generator, containing at least 20 bits of entropy (typically a six digital random number is sufficient).
", "applicable": false, "asvsId": "2.7.6", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 6, "type": "REQ" } ] }, { "id": "169", "guid": "ccdf09cc-93c9-4082-8f3d-b7a9e27ebb5a", "heading": "One Time Verifier", "asvsId": "2.8", "help": "Single-factor One-time Passwords (OTPs) are physical or soft tokens that display a continually changing pseudo-random one-time challenge. These devices make phishing (impersonation) difficult, but not impossible. This type of authenticator is considered \"something you have\". Multi-factor tokens are similar to single-factor OTPs, but require a valid PIN code, biometric unlocking, USB insertion or NFC pairing or some additional value (such as transaction signing calculators) to be entered to create the final OTP.
", "ord": 8, "type": "SEC", "children": [ { "id": "170", "guid": "ee692804-5428-4c74-a388-4c01b1354ead", "text": "Verify that time-based OTPs have a defined lifetime before expiring.
", "applicable": false, "asvsId": "2.8.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 1, "type": "REQ" }, { "id": "171", "guid": "04ed4d2e-f2c2-4efa-a734-75e0bb9eb847", "text": "Verify that symmetric keys used to verify submitted OTPs are highly protected, such as by using a hardware security module or secure operating system based key storage.
", "applicable": false, "asvsId": "2.8.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 2, "type": "REQ" }, { "id": "172", "guid": "68f78613-79c4-4168-ae13-108c760c5ddf", "text": "Verify that approved cryptographic algorithms are used in the generation, seeding, and verification of OTPs.
", "applicable": false, "asvsId": "2.8.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 3, "type": "REQ" }, { "id": "173", "guid": "54a1e3f9-4764-4005-9e24-31f3a4c31224", "text": "Verify that time-based OTP can be used only once within the validity period.
", "applicable": false, "asvsId": "2.8.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 4, "type": "REQ" }, { "id": "174", "guid": "397b214a-70ca-4156-966d-eb9771daf1f8", "text": "Verify that if a time-based multi-factor OTP token is re-used during the validity period, it is logged and rejected with secure notifications being sent to the holder of the device.
", "applicable": false, "asvsId": "2.8.5", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 5, "type": "REQ" }, { "id": "175", "guid": "b1c10db6-e4bc-4b3c-a416-b098a2741bf5", "text": "Verify physical single-factor OTP generator can be revoked in case of theft or other loss. Ensure that revocation is immediately effective across logged in sessions, regardless of location.
", "applicable": false, "asvsId": "2.8.6", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 6, "type": "REQ" }, { "id": "176", "guid": "2bc3eafb-8dc1-4dc9-b563-c1887136c779", "text": "Verify that biometric authenticators are limited to use only as secondary factors in conjunction with either something you have and something you know.
", "applicable": false, "asvsId": "2.8.7", "cwe": "", "l1": "NREQ", "l2": "OPT", "l2text": "o", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 7, "type": "REQ" } ] }, { "id": "177", "guid": "c0e16f11-f41f-4392-8347-b1622b937165", "heading": "Cryptographic Verifier", "asvsId": "2.9", "help": "Cryptographic security keys are smart cards or FIDO keys, where the user has to plug in or pair the cryptographic device to the computer to complete authentication. Verifiers send a challenge nonce to the cryptographic devices or software, and the device or software calculates a response based upon a securely stored cryptographic key.
The requirements for single-factor cryptographic devices and software, and multi-factor cryptographic devices and software are the same, as verification of the cryptographic authenticator proves possession of the authentication factor.
", "ord": 9, "type": "SEC", "children": [ { "id": "178", "guid": "0eaa9900-9584-4c2e-8573-8aace35d9a73", "text": "Verify that cryptographic keys used in verification are stored securely and protected against disclosure, such as using a Trusted Platform Module (TPM) or Hardware Security Module (HSM), or an OS service that can use this secure storage.
", "applicable": false, "asvsId": "2.9.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 1, "type": "REQ" }, { "id": "179", "guid": "ba777802-cf6b-4d99-89d0-e2fe2cc07c71", "text": "Verify that the challenge nonce is at least 64 bits in length, and statistically unique or unique over the lifetime of the cryptographic device.
", "applicable": false, "asvsId": "2.9.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 2, "type": "REQ" }, { "id": "180", "guid": "ac4b1559-1eca-4027-a48a-590c9d18cd65", "text": "Verify that approved cryptographic algorithms are used in the generation, seeding, and verification.
", "applicable": false, "asvsId": "2.9.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 3, "type": "REQ" } ] }, { "id": "181", "guid": "80d61c29-ee10-443b-8896-0a7605f45b4e", "heading": "Service Authentication", "asvsId": "2.10", "help": "This section is not penetration testable, so does not have any L1 requirements. However, if used in an architecture, coding or secure code review, please assume that software (just as Java Key Store) is the minimum requirement at L1. Clear text storage of secrets is not acceptable under any circumstances.
", "ord": 10, "type": "SEC", "children": [ { "id": "182", "guid": "03b0bc39-9c0d-43b9-a355-2511c89821cc", "text": "Verify that intra-service secrets do not rely on unchanging credentials such as passwords, API keys or shared accounts with privileged access.
", "applicable": false, "asvsId": "2.10.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "OS assisted", "l3": "REQ", "l3text": "HSM", "nist": "", "ord": 1, "type": "REQ" }, { "id": "183", "guid": "a66056b3-adfb-468b-8aed-bcddb40ccc0c", "text": "Verify that if passwords are required for service authentication, the service account used is not a default credential. (e.g. root/root or admin/admin are default in some services during installation).
", "applicable": false, "asvsId": "2.10.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "OS assisted", "l3": "REQ", "l3text": "HSM", "nist": "", "ord": 2, "type": "REQ" }, { "id": "184", "guid": "30e2bec9-90c9-470d-856d-214615845540", "text": "Verify that passwords are stored with sufficient protection to prevent offline recovery attacks, including local system access.
", "applicable": false, "asvsId": "2.10.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "OS assisted", "l3": "REQ", "l3text": "HSM", "nist": "", "ord": 3, "type": "REQ" }, { "id": "185", "guid": "2bf54d90-01f9-4a50-8a94-7fa562f5e444", "text": "Verify passwords, integrations with databases and third-party systems, seeds and internal secrets, and API keys are managed securely and not included in the source code or stored within source code repositories. Such storage SHOULD resist offline attacks. The use of a secure software key store (L1), hardware TPM, or an HSM (L3) is recommended for password storage.
", "applicable": false, "asvsId": "2.10.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "OS assisted", "l3": "REQ", "l3text": "HSM", "ord": 4, "type": "REQ" } ] } ] }, { "id": "186", "guid": "4a0846c4-7055-4538-a927-04087f7e4f0f", "heading": "Session Management", "asvsId": "3", "help": "Control Objective
One of the core components of any web-based application or stateful API is the mechanism by which it controls and maintains the state for a user or device interacting with it. Session management changes a stateless protocol to stateful, which is critical for differentiating different users or devices.
Ensure that a verified application satisfies the following high-level session management requirements:
As previously noted, these requirements have been adapted to be a compliant subset of selected NIST 800-63b controls, focused around common threats and commonly exploited authentication weaknesses. Previous verification requirements have been retired, de-duped, or in most cases adapted to be strongly aligned with the intent of mandatory NIST 800-63b requirements.
Security Verification Requirements
Description of the half-open Attack
In early 2018, several financial institutions were compromised using what the attackers called \"half-open attacks\". This term has stuck in the industry. The attackers struck multiple institutions with different proprietary code bases, and indeed it seems different code bases within the same institutions. The half-open attack is exploiting a design pattern flaw commonly found in many existing authentication, session management and access control systems.
Attackers start a half-open attack by attempting to lock, reset, or recover a credential. A popular session management design pattern re-uses user profile session objects/models between unauthenticated, half-authenticated (password resets, forgot username), and fully authenticated code. This design pattern populates a valid session object or token containing the victim's profile, including password hashes and roles. If access control checks in controllers or routers does not correctly verify that the user is fully logged in, the attacker will be able to act as the user. Attacks could include changing the user's password to a known value, update the email address to perform a valid password reset, disable multi-factor authentication or enroll a new MFA device, reveal or change API keys, and so on.
References
For more information, see also:
Verify the application never reveals session tokens in URL parameters.
", "applicable": false, "asvsId": "3.1.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" } ] }, { "id": "189", "guid": "e8f14a15-fafa-4d00-bcb1-aeab447eac89", "heading": "Session Binding", "asvsId": "3.2", "help": "TLS or another secure transport channel is mandatory for session management. This is covered off in the Communications Security chapter.
", "ord": 2, "type": "SEC", "children": [ { "id": "190", "guid": "934738e8-7cb0-405f-81de-99b6b2d13f30", "text": "Verify the application generates a new session token on user authentication. (C6)
", "applicable": false, "asvsId": "3.2.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 1, "type": "REQ" }, { "id": "191", "guid": "5c34fda8-9415-4052-9b20-26d4aa9be953", "text": "Verify that session tokens possess at least 64 bits of entropy. (C6)
", "applicable": false, "asvsId": "3.2.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 2, "type": "REQ" }, { "id": "192", "guid": "819b0347-4fe4-4d33-9f0f-66a41793f41c", "text": "Verify the application only stores session tokens in the browser using secure methods such as appropriately secured cookies (see section 3.4) or HTML 5 session storage.
", "applicable": false, "asvsId": "3.2.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 3, "type": "REQ" }, { "id": "193", "guid": "f6d5da43-288c-4d4b-8bb7-80ceb836e1d9", "text": "Verify that session tokens are generated using approved cryptographic algorithms. (C6)
", "applicable": false, "asvsId": "3.2.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 4, "type": "REQ" } ] }, { "id": "194", "guid": "1425ce9d-2af2-4051-9f10-2cc335cfbc08", "heading": "Session Termination", "asvsId": "3.3", "help": "Session timeouts have been aligned with NIST 800-63, which permits much longer session timeouts than traditionally permitted by security standards. Organizations should review the table below, and if a longer time out is desirable based around the application's risk, the NIST value should be the upper bounds of session idle timeouts.
L1 in this context is IAL1/AAL1, L2 is IAL2/AAL3, L3 is IAL3/AAL3. For IAL2/AAL2 and IAL3/AAL3, the shorter idle timeout is, the lower bound of idle times for being logged out or re-authenticated to resume the session.
", "ord": 3, "type": "SEC", "children": [ { "id": "195", "guid": "559e8ce0-d266-4281-8a6f-4cc4a7153296", "text": "Verify that logout and expiration invalidate the session token, such that the back button or a downstream relying party does not resume an authenticated session, including across relying parties. (C6)
", "applicable": false, "asvsId": "3.3.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 1, "type": "REQ" }, { "id": "196", "guid": "3475a5c8-96c3-4795-bbdf-abc34c74c870", "text": "If authenticators permit users to remain logged in, verify that re-authentication occurs periodically both when actively used or after an idle period. (C6)
", "applicable": false, "asvsId": "3.3.2", "cwe": "", "l1": "REQ", "l1text": "30 days", "l2": "REQ", "l2text": "12 hours or 30 minutes of inactivity, 2FA optional", "l3": "REQ", "l3text": "12 hours or 15 minutes of inactivity, with 2FA", "nist": "", "ord": 2, "type": "REQ" }, { "id": "197", "guid": "fb8fc94e-cbc2-445b-906a-415da6089e55", "text": "Verify that the application gives the option to terminate all other active sessions after a successful password change (including change via password reset/recovery), and that this is effective across the application, federated login (if present), and any relying parties.
", "applicable": false, "asvsId": "3.3.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "198", "guid": "deba9c67-009b-49b2-8f4a-cb9292bba4e9", "text": "Verify that users are able to view and (having re-entered login credentials) log out of any or all currently active sessions and devices.
", "applicable": false, "asvsId": "3.3.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 4, "type": "REQ" } ] }, { "id": "199", "guid": "2fed8674-e730-4216-b668-4579fdac8111", "heading": "Cookie-based Session Management", "asvsId": "3.4", "ord": 4, "type": "SEC", "children": [ { "id": "200", "guid": "00e96ee8-7a32-44c4-ad82-831a95fb0914", "text": "Verify that cookie-based session tokens have the 'Secure' attribute set. (C6)
", "applicable": false, "asvsId": "3.4.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 1, "type": "REQ" }, { "id": "201", "guid": "23844c1f-3530-4411-8614-b32d1b6162b2", "text": "Verify that cookie-based session tokens have the 'HttpOnly' attribute set. (C6)
", "applicable": false, "asvsId": "3.4.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 2, "type": "REQ" }, { "id": "202", "guid": "646da52d-9ac6-42d2-bcd2-52e1d2d3e1da", "text": "Verify that cookie-based session tokens utilize the 'SameSite' attribute to limit exposure to cross-site request forgery attacks. (C6)
", "applicable": false, "asvsId": "3.4.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 3, "type": "REQ" }, { "id": "203", "guid": "d3beab51-d68e-49e0-abb9-bc04e782b797", "text": "Verify that cookie-based session tokens use the \"__Host-\" prefix so cookies are only sent to the host that initially set the cookie.
", "applicable": false, "asvsId": "3.4.4", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 4, "type": "REQ" }, { "id": "204", "guid": "ea9f7166-5a81-4a5c-a5f4-c728196e3178", "text": "Verify that if the application is published under a domain name with other applications that set or use session cookies that might disclose the session cookies, set the path attribute in cookie-based session tokens using the most precise path possible. (C6)
", "applicable": false, "asvsId": "3.4.5", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 5, "type": "REQ" } ] }, { "id": "205", "guid": "595fd4fd-f017-4f7d-8b9f-3205cde7bc9e", "heading": "Token-based Session Management", "asvsId": "3.5", "help": "Token-based session management includes JWT, OAuth, SAML, and API keys. Of these, API keys are known to be weak and should not be used in new code.
", "ord": 5, "type": "SEC", "children": [ { "id": "206", "guid": "bb64b3c5-11b1-48d2-ac95-0ce1c8686457", "text": "Verify the application allows users to revoke OAuth tokens that form trust relationships with linked applications.
", "applicable": false, "asvsId": "3.5.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 1, "type": "REQ" }, { "id": "207", "guid": "3274a7af-cca5-4b1e-a7f1-992264734c8e", "text": "Verify the application uses session tokens rather than static API secrets and keys, except with legacy implementations.
", "applicable": false, "asvsId": "3.5.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "208", "guid": "0ad99929-8ed5-4160-a0f7-6799776d2342", "text": "Verify that stateless session tokens use digital signatures, encryption, and other countermeasures to protect against tampering, enveloping, replay, null cipher, and key substitution attacks.
", "applicable": false, "asvsId": "3.5.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" } ] }, { "id": "209", "guid": "966f0110-7b50-4d6c-b535-4cc7d81fd647", "heading": "Federated Re-authentication", "asvsId": "3.6", "help": "This section relates to those writing Relying Party (RP) or Credential Service Provider (CSP) code. If relying on code implementing these features, ensure that these issues are handled correctly.
", "ord": 6, "type": "SEC", "children": [ { "id": "210", "guid": "0f0e9088-212e-43de-a701-7ec50792741f", "text": "Verify that Relying Parties (RPs) specify the maximum authentication time to Credential Service Providers (CSPs) and that CSPs re-authenticate the user if they haven't used a session within that period.
", "applicable": false, "asvsId": "3.6.1", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 1, "type": "REQ" }, { "id": "211", "guid": "df9db035-72f4-4213-8d41-fca0a84f0a67", "text": "Verify that Credential Service Providers (CSPs) inform Relying Parties (RPs) of the last authentication event, to allow RPs to determine if they need to re-authenticate the user.
", "applicable": false, "asvsId": "3.6.2", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "nist": "", "ord": 2, "type": "REQ" } ] }, { "id": "212", "guid": "afed3c10-89c1-44b2-8976-0ce78021df95", "heading": "Defenses Against Session Management Exploits", "asvsId": "3.7", "help": "There are a small number of session management attacks, some related to the user experience (UX) of sessions. Previously, based on ISO 27002 requirements, the ASVS has required blocking multiple simultaneous sessions. Blocking simultaneous sessions is no longer appropriate, not only as modern users have many devices or the app is an API without a browser session, but in most of these implementations, the last authenticator wins, which is often the attacker. This section provides leading guidance on deterring, delaying and detecting session management attacks using code.
", "ord": 7, "type": "SEC", "children": [ { "id": "213", "guid": "14ec4e78-3788-4af1-80f8-7689a7653fab", "text": "Verify the application ensures a full, valid login session or requires re-authentication or secondary verification before allowing any sensitive transactions or account modifications.
", "applicable": false, "asvsId": "3.7.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" } ] } ] }, { "id": "214", "guid": "153b73a9-c209-46e3-8a9c-ee0f05bc1cef", "heading": "Access Control", "asvsId": "4", "help": "Control Objective
Authorization is the concept of allowing access to resources only to those permitted to use them. Ensure that a verified application satisfies the following high level requirements:
Security Verification Requirements
References
For more information, see also:
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.
", "applicable": false, "asvsId": "4.1.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "217", "guid": "47bc14f9-6bcc-4e43-935a-64f002e3fa32", "text": "Verify that all user and data attributes and policy information used by access controls cannot be manipulated by end users unless specifically authorized.
", "applicable": false, "asvsId": "4.1.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "218", "guid": "676a92f6-5aa0-42e9-b8c0-7e23ee4e2ebd", "text": "Verify that the principle of least privilege exists - users should only be able to access functions, data files, URLs, controllers, services, and other resources, for which they possess specific authorization. This implies protection against spoofing and elevation of privilege. (C7)
", "applicable": false, "asvsId": "4.1.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "220", "guid": "1987c405-faee-4b82-91b3-d36e4ef5bc4b", "text": "Verify that access controls fail securely including when an exception occurs. (C10)
", "applicable": false, "asvsId": "4.1.5", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" } ] }, { "id": "221", "guid": "1a8336a8-35b0-4ff8-a01a-0e600494f29a", "heading": "Operation Level Access Control", "asvsId": "4.2", "ord": 2, "type": "SEC", "children": [ { "id": "222", "guid": "ca1d8a1f-5209-492c-854a-8e31e6390aee", "text": "Verify that sensitive data and APIs are protected against Insecure Direct Object Reference (IDOR) attacks targeting creation, reading, updating and deletion of records, such as creating or updating someone else's record, viewing everyone's records, or deleting all records.
", "applicable": false, "asvsId": "4.2.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "223", "guid": "ab2e8489-28cc-4573-aac8-20ef932464d6", "text": "Verify that the application or framework enforces a strong anti-CSRF mechanism to protect authenticated functionality, and effective anti-automation or anti-CSRF protects unauthenticated functionality.
", "applicable": false, "asvsId": "4.2.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" } ] }, { "id": "224", "guid": "fe07d1c6-b592-454a-a96b-bc59c341b6f1", "heading": "Other Access Control Considerations", "asvsId": "4.3", "ord": 3, "type": "SEC", "children": [ { "id": "225", "guid": "016af5a8-de9c-4836-bdca-c6e181773817", "text": "Verify administrative interfaces use appropriate multi-factor authentication to prevent unauthorized use.
", "applicable": false, "asvsId": "4.3.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "226", "guid": "93b0a7bc-67e5-4518-a7d7-8030899fabed", "text": "Verify that directory browsing is disabled unless deliberately desired. Additionally, applications should not allow discovery or disclosure of file or directory metadata, such as Thumbs.db, .DS_Store, .git or .svn folders.
", "applicable": false, "asvsId": "4.3.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "227", "guid": "c23f573c-7061-4069-9204-031cd0b3129d", "text": "Verify the application has additional authorization (such as step up or adaptive authentication) for lower value systems, and / or segregation of duties for high value applications to enforce anti-fraud controls as per the risk of application and past fraud.
", "applicable": false, "asvsId": "4.3.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" } ] } ] }, { "id": "228", "guid": "fec6a2fe-82f3-4ba2-ad63-cacb9b381224", "heading": "Validation, Sanitization and Encoding", "asvsId": "5", "help": "Control Objective
The most common web application security weakness is the failure to properly validate input coming from the client or the environment before directly using it without any output encoding. This weakness leads to almost all of the significant vulnerabilities in web applications, such as Cross-Site Scripting (XSS), SQL injection, interpreter injection, locale/Unicode attacks, file system attacks, and buffer overflows.
Ensure that a verified application satisfies the following high-level requirements:
With modern web application architecture, output encoding is more important than ever. It is difficult to provide robust input validation in certain scenarios, so the use of safer API such as parameterized queries, auto-escaping templating frameworks, or carefully chosen output encoding is critical to the security of the application.
References
For more information, see also:
For more information on auto-escaping, please see:
For more information on deserialization, please see:
", "ord": 5, "type": "CHAP", "children": [ { "id": "229", "guid": "955b4125-6048-4b31-a71b-75e07ab2f7ec", "heading": "Input Validation", "asvsId": "5.1", "help": "Properly implemented input validation controls, using positive allow lists and strong data typing, can eliminate more than 90% of all injection attacks. Length and range checks can reduce this further. Building in secure input validation is required during application architecture, design sprints, coding, and unit and integration testing. Although many of these items cannot be found in penetration tests, the results of not implementing them are usually found in V5.3 - Output encoding and Injection Prevention Requirements. Developers and secure code reviewers are recommended to treat this section as if L1 is required for all items to prevent injections.
", "ord": 1, "type": "SEC", "children": [ { "id": "230", "guid": "a768665f-dc00-45dd-bed8-c5fd63547211", "text": "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).
", "applicable": false, "asvsId": "5.1.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "231", "guid": "673653e4-2a49-4b0b-92be-ace6699bb358", "text": "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)
", "applicable": false, "asvsId": "5.1.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "232", "guid": "5ffdea11-f5e7-43b2-8187-b762f552ccab", "text": "Verify that all input (HTML form fields, REST requests, URL parameters, HTTP headers, cookies, batch files, RSS feeds, etc) is validated using positive validation (allow lists). (C5)
", "applicable": true, "asvsId": "5.1.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "233", "guid": "5755c562-7ff8-4b89-9b58-bca5daf93dc1", "text": "Verify that structured data is strongly typed and validated against a defined schema including allowed characters, length and pattern (e.g. credit card numbers, e-mail addresses, telephone numbers, or validating that two related fields are reasonable, such as checking that suburb and zip/postcode match). (C5)
", "applicable": true, "asvsId": "5.1.4", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "234", "guid": "eaeebd11-8ead-4a17-aeb4-8f316d317690", "text": "Verify that URL redirects and forwards only allow destinations which appear on an allow list, or show a warning when redirecting to potentially untrusted content.
", "applicable": true, "asvsId": "5.1.5", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" } ] }, { "id": "235", "guid": "b86a05fd-1e50-4962-b64d-b5243dc373d9", "heading": "Sanitization and Sandboxing", "asvsId": "5.2", "ord": 2, "type": "SEC", "children": [ { "id": "236", "guid": "c52afb9e-970e-4d0c-b910-68aee6c17651", "text": "Verify that all untrusted HTML input from WYSIWYG editors or similar is properly sanitized with an HTML sanitizer library or framework feature. (C5)
", "applicable": true, "asvsId": "5.2.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "237", "guid": "7c84b4c1-abcb-4e45-9598-c0af744c22d0", "text": "Verify that unstructured data is sanitized to enforce safety measures such as allowed characters and length.
", "applicable": true, "asvsId": "5.2.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "238", "guid": "f4a4a105-7383-406f-b8ac-9976cb5c357f", "text": "Verify that the application sanitizes user input before passing to mail systems to protect against SMTP or IMAP injection.
", "applicable": false, "asvsId": "5.2.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "239", "guid": "1f11af99-6467-4954-9766-e6e19b42dbfb", "text": "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.
", "applicable": true, "asvsId": "5.2.4", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "240", "guid": "1f97098a-c365-4093-b849-4ee5cd359191", "text": "Verify that the application protects against template injection attacks by ensuring that any user input being included is sanitized or sandboxed.
", "applicable": true, "asvsId": "5.2.5", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" }, { "id": "241", "guid": "a8aaac20-f720-4ccd-9d99-7223d88d1d02", "text": "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, and uses allow lists of protocols, domains, paths and ports.
", "applicable": false, "asvsId": "5.2.6", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 6, "type": "REQ" }, { "id": "242", "guid": "73ef599b-d071-4871-86b1-4309e3478489", "text": "Verify that the application sanitizes, disables, or sandboxes user-supplied Scalable Vector Graphics (SVG) scriptable content, especially as they relate to XSS resulting from inline scripts, and foreignObject.
", "applicable": true, "asvsId": "5.2.7", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 7, "type": "REQ" }, { "id": "243", "guid": "1c46978e-7974-4f3a-b689-154f2fe53aed", "text": "Verify that the application sanitizes, disables, or sandboxes user-supplied scriptable or expression template language content, such as Markdown, CSS or XSL stylesheets, BBCode, or similar.
", "applicable": false, "asvsId": "5.2.8", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 8, "type": "REQ" } ] }, { "id": "244", "guid": "5ed8ef8d-34f8-497a-871d-0014ff16d511", "heading": "Output Encoding and Injection Prevention", "asvsId": "5.3", "help": "Output encoding close or adjacent to the interpreter in use is critical to the security of any application. Typically, output encoding is not persisted, but used to render the output safe in the appropriate output context for immediate use. Failing to output encode will result in an insecure, injectable, and unsafe application.
Note: Using parameterized queries or escaping SQL is not always sufficient; table and column names, ORDER BY and so on, cannot be escaped. The inclusion of escaped user-supplied data in these fields results in failed queries or SQL injection.
Note: The SVG format explicitly allows ECMA script in almost all contexts, so it may not be possible to block all SVG XSS vectors completely. If SVG upload is required, we strongly recommend either serving these uploaded files as text/plain or using a separate user supplied content domain to prevent successful XSS from taking over the application.
", "ord": 3, "type": "SEC", "children": [ { "id": "245", "guid": "e4dc8677-4d38-4b40-920d-a7fe550beb14", "text": "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)
", "applicable": true, "asvsId": "5.3.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "246", "guid": "f738be91-ad57-4953-bd9a-19fd79348993", "text": "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)
", "applicable": true, "asvsId": "5.3.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "247", "guid": "6c46119a-7a62-4504-a733-fb2d78309e15", "text": "Verify that context-aware, preferably automated - or at worst, manual - output escaping protects against reflected, stored, and DOM based XSS. (C4)
", "applicable": true, "asvsId": "5.3.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "248", "guid": "f1fec940-32c3-4fcc-99e7-d26138d477b1", "text": "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)
", "applicable": false, "asvsId": "5.3.4", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "249", "guid": "167c30db-ca1d-488f-b98b-9a89799ec53a", "text": "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)
", "applicable": false, "asvsId": "5.3.5", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" }, { "id": "250", "guid": "272c74a7-7aba-41a0-adae-1b3199ab1d5d", "text": "Verify that the application protects against JSON injection attacks, JSON eval attacks, and JavaScript expression evaluation. (C4)
", "applicable": true, "asvsId": "5.3.6", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 6, "type": "REQ" }, { "id": "251", "guid": "12b24d65-f6ab-46c3-abd6-669391858399", "text": "Verify that the application protects against LDAP injection vulnerabilities, or that specific security controls to prevent LDAP injection have been implemented. (C4)
", "applicable": false, "asvsId": "5.3.7", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 7, "type": "REQ" }, { "id": "252", "guid": "cac124ef-78ec-494a-a2d3-7f342cc61a68", "text": "Verify that the application protects against OS command injection and that operating system calls use parameterized OS queries or use contextual command line output encoding. (C4)
", "applicable": false, "asvsId": "5.3.8", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 8, "type": "REQ" }, { "id": "253", "guid": "0ec0595b-827f-40f2-ba2e-65d47f0b85e6", "text": "Verify that the application protects against Local File Inclusion (LFI) or Remote File Inclusion (RFI) attacks.
", "applicable": false, "asvsId": "5.3.9", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 9, "type": "REQ" }, { "id": "254", "guid": "d91dbddf-79fd-4b85-a588-b848108f3245", "text": "Verify that the application protects against XPath injection or XML injection attacks. (C4)
", "applicable": false, "asvsId": "5.3.10", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 10, "type": "REQ" } ] }, { "id": "255", "guid": "2bb1829b-db7b-4833-abe6-71bde60ea0fd", "heading": "Memory, String, and Unmanaged Code", "asvsId": "5.4", "help": "The following requirements will only apply when the application uses a systems language or unmanaged code.
", "ord": 4, "type": "SEC", "children": [ { "id": "256", "guid": "23c3b3d2-2c22-4e39-a81d-575f9fc9fca9", "text": "Verify that the application uses memory-safe string, safer memory copy and pointer arithmetic to detect or prevent stack, buffer, or heap overflows.
", "applicable": false, "asvsId": "5.4.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "257", "guid": "a61863a5-1f51-4b83-b0e2-bc5ed03fea35", "text": "Verify that format strings do not take potentially hostile input, and are constant.
", "applicable": false, "asvsId": "5.4.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "258", "guid": "1414de61-d22c-4b3d-9608-615735385371", "text": "Verify that sign, range, and input validation techniques are used to prevent integer overflows.
", "applicable": false, "asvsId": "5.4.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" } ] }, { "id": "259", "guid": "52bab10f-07ff-47fa-a8a2-7e8144224d59", "heading": "Deserialization Prevention", "asvsId": "5.5", "ord": 5, "type": "SEC", "children": [ { "id": "260", "guid": "12ff7051-21c0-4f18-9695-fc82a7f83bce", "text": "Verify that serialized objects use integrity checks or are encrypted to prevent hostile object creation or data tampering. (C5)
", "applicable": false, "asvsId": "5.5.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "261", "guid": "8e41978b-a3ed-4994-8959-1f9b6bdf42b9", "text": "Verify that the application correctly restricts XML parsers to only use the most restrictive configuration possible and to ensure that unsafe features such as resolving external entities are disabled to prevent XML eXternal Entity (XXE) attacks.
", "applicable": false, "asvsId": "5.5.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "262", "guid": "6183b892-ec54-475d-8ac8-7eaa19bd117a", "text": "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).
", "applicable": false, "asvsId": "5.5.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "263", "guid": "10abed8a-539b-47ba-a1e5-81e07956af66", "text": "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.
", "applicable": true, "asvsId": "5.5.4", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" } ] } ] }, { "id": "264", "guid": "c3a72964-70af-46ba-ad91-c728aa99ab47", "heading": "Stored Cryptography", "asvsId": "6", "help": "Control Objective
Ensure that a verified application satisfies the following high level requirements:
References
For more information, see also:
The most important asset is the data processed, stored or transmitted by an application. Always perform a privacy impact assessment to classify the data protection needs of any stored data correctly.
", "ord": 1, "type": "SEC", "children": [ { "id": "266", "guid": "d50fbc68-3a65-4d8b-9bc3-574ea7322991", "text": "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.
", "applicable": false, "asvsId": "6.1.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "267", "guid": "0e4cc9d8-930f-4483-86a3-e5d8c124123a", "text": "Verify that regulated health data is stored encrypted while at rest, such as medical records, medical device details, or de-anonymized research records.
", "applicable": false, "asvsId": "6.1.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "268", "guid": "d6b66e89-985a-40ff-b18a-722eabd51f04", "text": "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.
", "applicable": false, "asvsId": "6.1.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" } ] }, { "id": "269", "guid": "0e4b01ad-7b4f-4014-9fff-6e36a19dcef3", "heading": "Algorithms", "asvsId": "6.2", "help": "Recent advances in cryptography mean that previously safe algorithms and key lengths are no longer safe or sufficient to protect data. Therefore, it should be possible to change algorithms.
Although this section is not easily penetration tested, developers should consider this entire section as mandatory even though L1 is missing from most of the items.
", "ord": 2, "type": "SEC", "children": [ { "id": "270", "guid": "addc7a93-e016-4710-8e77-29640a3e7c71", "text": "Verify that all cryptographic modules fail securely, and errors are handled in a way that does not enable Padding Oracle attacks.
", "applicable": false, "asvsId": "6.2.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "271", "guid": "1c01cf9b-3d97-4175-9608-d0a5552a11fb", "text": "Verify that industry proven or government approved cryptographic algorithms, modes, and libraries are used, instead of custom coded cryptography. (C8)
", "applicable": false, "asvsId": "6.2.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "272", "guid": "59fb8ef3-eafe-4c7d-98a3-dd42f9c6d643", "text": "Verify that encryption initialization vector, cipher configuration, and block modes are configured securely using the latest advice.
", "applicable": false, "asvsId": "6.2.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "273", "guid": "512532a8-824a-4baa-8f30-3f05acde25f9", "text": "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)
", "applicable": false, "asvsId": "6.2.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "274", "guid": "5ce28dd2-4250-4d0a-a2bc-b0a943f0d882", "text": "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.
", "applicable": false, "asvsId": "6.2.5", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" }, { "id": "275", "guid": "97e53ee7-368e-4c7e-953d-5413d0878685", "text": "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.
", "applicable": false, "asvsId": "6.2.6", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 6, "type": "REQ" }, { "id": "276", "guid": "4a5a7cb3-c9d6-4652-a45f-b81336246b5a", "text": "Verify that encrypted data is authenticated via signatures, authenticated cipher modes, or HMAC to ensure that ciphertext is not altered by an unauthorized party.
", "applicable": false, "asvsId": "6.2.7", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "ord": 7, "type": "REQ" }, { "id": "277", "guid": "e29e5d38-6a84-4357-b697-d2f4f88fdb5f", "text": "Verify that all cryptographic operations are constant-time, with no 'short-circuit' operations in comparisons, calculations, or returns, to avoid leaking information.
", "applicable": false, "asvsId": "6.2.8", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "ord": 8, "type": "REQ" } ] }, { "id": "278", "guid": "bfdc57cb-246d-4b06-859d-7c0f550f1aa3", "heading": "Random Values", "asvsId": "6.3", "help": "True Pseudo-random Number Generation (PRNG) is incredibly difficult to get right. Generally, good sources of entropy within a system will be quickly depleted if over-used, but sources with less randomness can lead to predictable keys and secrets.
", "ord": 3, "type": "SEC", "children": [ { "id": "279", "guid": "0377ac27-a297-4c1d-9e64-45155becea25", "text": "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.
", "applicable": false, "asvsId": "6.3.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "280", "guid": "7059d788-c8ff-4249-81d6-91a031db2071", "text": "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.
", "applicable": false, "asvsId": "6.3.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "281", "guid": "cc259237-5a35-4deb-9586-c7b785827e1e", "text": "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.
", "applicable": false, "asvsId": "6.3.3", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" } ] }, { "id": "282", "guid": "97455b62-c41d-4a9e-834f-d27d57a68dcf", "heading": "Secret Management", "asvsId": "6.4", "help": "Although this section is not easily penetration tested, developers should consider this entire section as mandatory even though L1 is missing from most of the items.
", "ord": 4, "type": "SEC", "children": [ { "id": "283", "guid": "5af9211f-e790-46a4-b4dc-ecc1610af755", "text": "Verify that a secrets management solution such as a key vault is used to securely create, store, control access to and destroy secrets. (C8)
", "applicable": false, "asvsId": "6.4.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "284", "guid": "c1027cf5-f404-45da-b054-1137e10dc61d", "text": "Verify that key material is not exposed to the application but instead uses an isolated security module like a vault for cryptographic operations. (C8)
", "applicable": false, "asvsId": "6.4.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" } ] } ] }, { "id": "285", "guid": "474c6609-0b94-4311-9929-57b522333e35", "heading": "Error Handling and Logging", "asvsId": "7", "help": "Control Objective
The primary objective of error handling and logging is to provide useful information for the user, administrators, and incident response teams. The objective is not to create massive amounts of logs, but high quality logs, with more signal than discarded noise.
High quality logs will often contain sensitive data, and must be protected as per local data privacy laws or directives. This should include:
If logs contain private or sensitive data, the definition of which varies from country to country, the logs become some of the most sensitive information held by the application and thus very attractive to attackers in their own right.
It is also important to ensure that the application fails securely and that errors do not disclose unnecessary information.
References
For more information, see also:
Logging sensitive information is dangerous - the logs become classified themselves, which means they need to be encrypted, become subject to retention policies, and must be disclosed in security audits. Ensure only necessary information is kept in logs, and certainly no payment, credentials (including session tokens), sensitive or personally identifiable information.
V7.1 covers OWASP Top 10 2017:A10. As 2017:A10 and this section are not penetration testable, it's important for:
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)
", "applicable": true, "asvsId": "7.1.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "288", "guid": "9d5da756-b6a5-402f-95ef-1ed262cb374c", "text": "Verify that the application does not log other sensitive data as defined under local privacy laws or relevant security policy. (C9)
", "applicable": true, "asvsId": "7.1.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "289", "guid": "654ad6ac-66b1-4653-9604-01f4387d0b3b", "text": "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)
", "applicable": false, "asvsId": "7.1.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "290", "guid": "01c3cc4f-1348-407d-9450-b91885a95da7", "text": "Verify that each log event includes necessary information that would allow for a detailed investigation of the timeline when an event happens. (C9)
", "applicable": false, "asvsId": "7.1.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" } ] }, { "id": "291", "guid": "b390cde5-c88f-43a6-8248-bf02f49276de", "heading": "Log Processing", "asvsId": "7.2", "help": "Timely logging is critical for audit events, triage, and escalation. Ensure that the application's logs are clear and can be easily monitored and analyzed either locally or log shipped to a remote monitoring system.
V7.2 covers OWASP Top 10 2017:A10. As 2017:A10 and this section are not penetration testable, it's important for:
Verify that all authentication decisions are logged, without storing sensitive session tokens or passwords. This should include requests with relevant metadata needed for security investigations.
", "applicable": false, "asvsId": "7.2.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "293", "guid": "5793217f-7fcd-4ca4-998c-52f6e60a6721", "text": "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.
", "applicable": false, "asvsId": "7.2.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" } ] }, { "id": "294", "guid": "e8daa4a3-6d4e-4db5-9c79-36986e7d409a", "heading": "Log Protection", "asvsId": "7.3", "help": "Logs that can be trivially modified or deleted are useless for investigations and prosecutions. Disclosure of logs can expose inner details about the application or the data it contains. Care must be taken when protecting logs from unauthorized disclosure, modification or deletion.
Note: Log encoding (7.3.1) is difficult to test and review using automated dynamic tools and penetration tests, but architects, developers, and source code reviewers should consider it an L1 requirement.
", "ord": 3, "type": "SEC", "children": [ { "id": "295", "guid": "016a7595-2e23-4af5-9fa8-506f211b690a", "text": "Verify that all logging components appropriately encode data to prevent log injection. (C9)
", "applicable": false, "asvsId": "7.3.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "297", "guid": "d666d0b6-5194-4f7c-835a-4eabf56013ac", "text": "Verify that security logs are protected from unauthorized access and modification. (C9)
", "applicable": false, "asvsId": "7.3.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "298", "guid": "72712abe-6576-4c20-b47b-8644dc945c0a", "text": "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)
", "applicable": false, "asvsId": "7.3.4", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" } ] }, { "id": "299", "guid": "ba83a093-4744-43bd-ae19-9bb9067d5c87", "heading": "Error Handling", "asvsId": "7.4", "help": "The purpose of error handling is to allow the application to provide security relevant events for monitoring, triage and escalation. The purpose is not to create logs. When logging security related events, ensure that there is a purpose to the log, and that it can be distinguished by SIEM or analysis software.
Note: Certain languages, such as Swift and Go - and through common design practice - many functional languages, do not support exceptions or last resort event handlers. In this case, architects and developers should use a pattern, language, or framework friendly way to ensure that applications can securely handle exceptional, unexpected, or security-related events.
", "ord": 4, "type": "SEC", "children": [ { "id": "300", "guid": "8e4567f9-3859-4fe2-86dc-6858c2befddb", "text": "Verify that a generic message is shown when an unexpected or security sensitive error occurs, potentially with a unique ID which support personnel can use to investigate. (C10)
", "applicable": false, "asvsId": "7.4.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "301", "guid": "d1d1b36a-9572-42fa-87d8-f4d4cd061648", "text": "Verify that exception handling (or a functional equivalent) is used across the codebase to account for expected and unexpected error conditions. (C10)
", "applicable": false, "asvsId": "7.4.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "302", "guid": "49913038-0c61-49f6-9cb3-ed001b13d17b", "text": "Verify that a \"last resort\" error handler is defined which will catch all unhandled exceptions. (C10)
", "applicable": false, "asvsId": "7.4.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" } ] } ] }, { "id": "303", "guid": "bb209d26-fb3d-44a3-baa1-b45870859c43", "heading": "Data Protection", "asvsId": "8", "help": "Control Objective
There are three key elements to sound data protection: Confidentiality, Integrity and Availability (CIA). This standard assumes that data protection is enforced on a trusted system, such as a server, which has been hardened and has sufficient protections.
Applications have to assume that all user devices are compromised in some way. Where an application transmits or stores sensitive information on insecure devices, such as shared computers, phones and tablets, the application is responsible for ensuring data stored on these devices is encrypted and cannot be easily illicitly obtained, altered or disclosed.
Ensure that a verified application satisfies the following high level data protection requirements:
References
For more information, see also:
Verify the application protects sensitive data from being cached in server components such as load balancers and application caches.
", "applicable": false, "asvsId": "8.1.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "306", "guid": "e0ae3a9e-813e-4555-ac3a-4eddd796d9e4", "text": "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.
", "applicable": false, "asvsId": "8.1.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "307", "guid": "b79a5c62-966d-494d-bab9-3e929ad9b412", "text": "Verify the application minimizes the number of parameters in a request, such as hidden fields, Ajax variables, cookies and header values.
", "applicable": false, "asvsId": "8.1.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "308", "guid": "a2a846d1-5912-4fee-81ce-411f1f80bde1", "text": "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.
", "applicable": false, "asvsId": "8.1.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "309", "guid": "7f470941-37e8-45bc-ac4c-1bcbfa7ca20a", "text": "Verify that regular backups of important data are performed and that test restoration of data is performed.
", "applicable": false, "asvsId": "8.1.5", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" }, { "id": "310", "guid": "12f3c448-db42-482f-9418-ff4d1293faeb", "text": "Verify that backups are stored securely to prevent data from being stolen or corrupted.
", "applicable": false, "asvsId": "8.1.6", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "ord": 6, "type": "REQ" } ] }, { "id": "311", "guid": "f0375b06-cba9-4ace-ab86-83beb57926ab", "heading": "Client-side Data Protection", "asvsId": "8.2", "ord": 2, "type": "SEC", "children": [ { "id": "312", "guid": "1040ec1d-e8c0-48c2-8a7a-e4fa23305e2a", "text": "Verify the application sets sufficient anti-caching headers so that sensitive data is not cached in modern browsers.
", "applicable": false, "asvsId": "8.2.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "313", "guid": "ba299b0d-b36d-4ffd-a97b-71654ce3933e", "text": "Verify that data stored in browser storage (such as localStorage, sessionStorage, IndexedDB, or cookies) does not contain sensitive data.
", "applicable": false, "asvsId": "8.2.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "314", "guid": "6e112bec-29f5-4946-b4d8-e3d027711005", "text": "Verify that authenticated data is cleared from client storage, such as the browser DOM, after the client or session is terminated.
", "applicable": false, "asvsId": "8.2.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" } ] }, { "id": "315", "guid": "b3b9300c-d337-4fe3-8aaa-84ca6aaa891c", "heading": "Sensitive Private Data", "asvsId": "8.3", "help": "This section helps protect sensitive data from being created, read, updated, or deleted without authorization, particularly in bulk quantities.
Compliance with this section implies compliance with V4 Access Control, and in particular V4.2. For example, to protect against unauthorized updates or disclosure of sensitive personal information requires adherence to V4.2.1. Please comply with this section and V4 for full coverage.
Note: Privacy regulations and laws, such as the Australian Privacy Principles APP-11 or GDPR, directly affect how applications must approach the implementation of storage, use, and transmission of sensitive personal information. This ranges from severe penalties to simple advice. Please consult your local laws and regulations, and consult a qualified privacy specialist or lawyer as required.
When considering data protection, a primary consideration should be around bulk extraction or modification or excessive usage. For example, many social media systems only allow users to add 100 new friends per day, but which system these requests came from is not important. A banking platform might wish to block more than 5 transactions per hour transferring more than 1000 euro of funds to external institutions. Each system's requirements are likely to be very different, so deciding on \"abnormal\" must consider the threat model and business risk. Important criteria are the ability to detect, deter, or preferably block such abnormal bulk actions.
", "ord": 3, "type": "SEC", "children": [ { "id": "316", "guid": "dce6b0b8-d60d-4f4f-9192-90feec056947", "text": "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.
", "applicable": false, "asvsId": "8.3.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "317", "guid": "ff6ee539-ee77-4289-a921-0b646677595e", "text": "Verify that users have a method to remove or export their data on demand.
", "applicable": false, "asvsId": "8.3.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "318", "guid": "c46fe1d8-cc37-4160-9fea-11e87729c434", "text": "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.
", "applicable": true, "asvsId": "8.3.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "319", "guid": "9c59b612-d31a-444f-88d0-073945984454", "text": "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)
", "applicable": true, "asvsId": "8.3.4", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "320", "guid": "7ef7cfd2-1ee0-4189-a0a8-592beb8641d4", "text": "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.
", "applicable": false, "asvsId": "8.3.5", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" }, { "id": "321", "guid": "0fc11b77-bff2-47c3-8994-4cb1d3e88a1b", "text": "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.
", "applicable": false, "asvsId": "8.3.6", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 6, "type": "REQ" }, { "id": "322", "guid": "67912c19-4edd-40a5-b2cb-90258d6664c7", "text": "Verify that sensitive or private information that is required to be encrypted, is encrypted using approved algorithms that provide both confidentiality and integrity. (C8)
", "applicable": false, "asvsId": "8.3.7", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 7, "type": "REQ" }, { "id": "323", "guid": "788482de-755a-4023-a93e-cbc8d5a65381", "text": "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.
", "applicable": false, "asvsId": "8.3.8", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 8, "type": "REQ" } ] } ] }, { "id": "324", "guid": "cf75b6a1-83a4-4961-9d2c-4cae8f67f408", "heading": "Communication", "asvsId": "9", "help": "Control Objective
Ensure that a verified application meets the following high level requirements:
Within these requirements:
References
For more information, see also:
Ensure all client messages are sent over encrypted networks, using TLS 1.2 or later.Use up to date tools to review the client configuration on a regular basis.
", "ord": 1, "type": "SEC", "children": [ { "id": "326", "guid": "06304bd0-8efd-4dc4-ad5e-c162a2f865f7", "text": "Verify that TLS is used for all client connectivity, and does not fall back to insecure or unencrypted communications. (C8)
", "applicable": false, "asvsId": "9.1.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "327", "guid": "cbb091e3-7c4a-4df6-a0d2-f5252ffd1344", "text": "Verify using up to date TLS testing tools that only strong cipher suites are enabled, with the strongest cipher suites set as preferred.
", "applicable": false, "asvsId": "9.1.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "328", "guid": "aee597b6-3610-46e9-9f43-d6efae3b19d1", "text": "Verify that only the latest recommended versions of the TLS protocol are enabled, such as TLS 1.2 and TLS 1.3. The latest version of the TLS protocol should be the preferred option.
", "applicable": false, "asvsId": "9.1.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" } ] }, { "id": "329", "guid": "73d51e87-9179-4f9e-888e-4c7d5920c3ce", "heading": "Server Communication Security", "asvsId": "9.2", "help": "Server communications are more than just HTTP. Secure connections to and from other systems, such as monitoring systems, management tools, remote access and ssh, middleware, database, mainframes, partner or external source systems — must be in place. All of these must be encrypted to prevent \"hard on the outside, trivially easy to intercept on the inside\".
", "ord": 2, "type": "SEC", "children": [ { "id": "330", "guid": "a7429ae7-dc34-4047-9391-2649c0ca096e", "text": "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.
", "applicable": false, "asvsId": "9.2.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "331", "guid": "310925be-6b51-4465-99aa-c596b7c5b028", "text": "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.
", "applicable": false, "asvsId": "9.2.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "332", "guid": "05f7db3c-b524-474f-b30a-b649ff7e1779", "text": "Verify that all encrypted connections to external systems that involve sensitive information or functions are authenticated.
", "applicable": false, "asvsId": "9.2.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "333", "guid": "0cc174b6-55a5-4065-a025-7f43ef661651", "text": "Verify that proper certification revocation, such as Online Certificate Status Protocol (OCSP) Stapling, is enabled and configured.
", "applicable": false, "asvsId": "9.2.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "334", "guid": "d4603878-faad-49d4-8a63-d5295e06b1d2", "text": "Verify that backend TLS connection failures are logged.
", "applicable": false, "asvsId": "9.2.5", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" } ] } ] }, { "id": "335", "guid": "b6820ba0-b306-4b2b-92ad-e96212c141c0", "heading": "Malicious Code", "asvsId": "10", "help": "Control Objective
Ensure that code satisfies the following high level requirements:
Finding malicious code is proof of the negative, which is impossible to completely validate. Best efforts should be undertaken to ensure that the code has no inherent malicious code or unwanted functionality.
References
", "ord": 10, "type": "CHAP", "children": [ { "id": "336", "guid": "65ce9e91-9d6c-4a1f-9db5-6020505c0b17", "heading": "Code Integrity", "asvsId": "10.1", "help": "The best defense against malicious code is \"trust, but verify\". Introducing unauthorized or malicious code into code is often a criminal offence in many jurisdictions. Policies and procedures should make sanctions regarding malicious code clear.
Lead developers should regularly review code check-ins, particularly those that might access time, I/O, or network functions.
", "ord": 1, "type": "SEC", "children": [ { "id": "337", "guid": "b5bc9e6d-2ef3-40ed-b84a-36dc27cd25a5", "text": "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.
", "applicable": false, "asvsId": "10.1.1", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" } ] }, { "id": "338", "guid": "a8e7dcad-3e37-4497-bd77-b7e5e3427503", "heading": "Malicious Code Search", "asvsId": "10.2", "help": "Malicious code is extremely rare and is difficult to detect. Manual line by line code review can assist looking for logic bombs, but even the most experienced code reviewer will struggle to find malicious code even if they know it exists.
Complying with this section is not possible without complete access to source code, including third-party libraries.
", "ord": 2, "type": "SEC", "children": [ { "id": "339", "guid": "27a0c7f2-a278-48a0-a74b-80e6692c8573", "text": "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.
", "applicable": false, "asvsId": "10.2.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "340", "guid": "5d69ad3b-7e3f-4ff7-8c42-c6aad374ea34", "text": "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.
", "applicable": false, "asvsId": "10.2.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "341", "guid": "d163d076-c707-45a1-9f6b-346706648ac5", "text": "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.
", "applicable": false, "asvsId": "10.2.3", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "342", "guid": "a2dfd473-dff4-43c6-8930-ffd070e8c42e", "text": "Verify that the application source code and third party libraries do not contain time bombs by searching for date and time related functions.
", "applicable": false, "asvsId": "10.2.4", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "343", "guid": "414c039e-5364-4c70-9f04-d9dea4154e7c", "text": "Verify that the application source code and third party libraries do not contain malicious code, such as salami attacks, logic bypasses, or logic bombs.
", "applicable": false, "asvsId": "10.2.5", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" }, { "id": "344", "guid": "8d5fb865-a402-494b-b973-25b3f32d7001", "text": "Verify that the application source code and third party libraries do not contain Easter eggs or any other potentially unwanted functionality.
", "applicable": false, "asvsId": "10.2.6", "cwe": "", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "ord": 6, "type": "REQ" } ] }, { "id": "345", "guid": "8223d773-ccd8-4014-8ce8-5761cb3c6c10", "heading": "Application Integrity", "asvsId": "10.3", "help": "Once an application is deployed, malicious code can still be inserted. Applications need to protect themselves against common attacks, such as executing unsigned code from untrusted sources and subdomain takeovers.
Complying with this section is likely to be operational and continuous.
", "ord": 3, "type": "SEC", "children": [ { "id": "346", "guid": "74ea534b-0d3a-445d-9b9a-6c1b1f09f2d6", "text": "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.
", "applicable": false, "asvsId": "10.3.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "347", "guid": "dd4f9822-83b5-4b35-a648-3e245d4befbe", "text": "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.
", "applicable": true, "asvsId": "10.3.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "348", "guid": "3fbf2405-3950-4aa6-a208-5dd2ad2750a2", "text": "Verify that the application has protection from subdomain takeovers if the application relies upon DNS entries or DNS subdomains, 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.
", "applicable": false, "asvsId": "10.3.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" } ] } ] }, { "id": "349", "guid": "9b78a23d-0f85-4818-a652-a336efd89f56", "heading": "Business Logic", "asvsId": "11", "help": "Control Objective
Ensure that a verified application satisfies the following high level requirements:
References
For more information, see also:
Business logic security is so individual to every application that no one checklist will ever apply. Business logic security must be designed in to protect against likely external threats - it cannot be added using web application firewalls or secure communications. We recommend the use of threat modeling during design sprints, for example using the OWASP Cornucopia or similar tools.
", "ord": 1, "type": "SEC", "children": [ { "id": "351", "guid": "3f2a5822-441b-42bc-acc7-4a48b897c728", "text": "Verify that the application will only process business logic flows for the same user in sequential step order and without skipping steps.
", "applicable": false, "asvsId": "11.1.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "352", "guid": "728cd959-23db-4fe3-a9ac-a98f2dadd9fb", "text": "Verify that 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.
", "applicable": false, "asvsId": "11.1.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "353", "guid": "21946c65-72f4-48a7-b478-cad885fb23bc", "text": "Verify the application has appropriate limits for specific business actions or transactions which are correctly enforced on a per user basis.
", "applicable": false, "asvsId": "11.1.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "354", "guid": "a28596b5-82a2-4148-b2a1-7c24e5de571e", "text": "Verify that the application has anti-automation controls to protect against excessive calls such as mass data exfiltration, business logic requests, file uploads or denial of service attacks.
", "applicable": false, "asvsId": "11.1.4", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "355", "guid": "595bd296-f1ae-45f1-8b6a-f7022e33d564", "text": "Verify the application has business logic limits or validation to protect against likely business risks or threats, identified using threat modeling or similar methodologies.
", "applicable": false, "asvsId": "11.1.5", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" }, { "id": "356", "guid": "d255708f-07eb-4d6f-9adf-b66d5a86522f", "text": "Verify that the application does not suffer from \"Time Of Check to Time Of Use\" (TOCTOU) issues or other race conditions for sensitive operations.
", "applicable": false, "asvsId": "11.1.6", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 6, "type": "REQ" }, { "id": "357", "guid": "7184c27b-6b28-4861-a709-918ef2bcb596", "text": "Verify that 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)
", "applicable": false, "asvsId": "11.1.7", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 7, "type": "REQ" }, { "id": "358", "guid": "25f7298b-6211-47ac-9375-eaae53721a2b", "text": "Verify that the application has configurable alerting when automated attacks or unusual activity is detected.
", "applicable": false, "asvsId": "11.1.8", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 8, "type": "REQ" } ] } ] }, { "id": "359", "guid": "5bb13152-98c9-43b4-b117-6a5e2457a178", "heading": "Files and Resources", "asvsId": "12", "help": "Control Objective
Ensure that a verified application satisfies the following high level requirements:
References
For more information, see also:
Although zip bombs are eminently testable using penetration testing techniques, they are considered L2 and above to encourage design and development consideration with careful manual testing, and to avoid automated or unskilled manual penetration testing of a denial of service condition.
", "ord": 1, "type": "SEC", "children": [ { "id": "361", "guid": "7c502d03-f3bb-43c1-b26b-937ba69a13e9", "text": "Verify that the application will not accept large files that could fill up storage or cause a denial of service.
", "applicable": false, "asvsId": "12.1.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "362", "guid": "c8962bf6-f07b-43e7-9b23-08dcbd538ee4", "text": "Verify that the application checks compressed files (e.g. zip, gz, docx, odt) against maximum allowed uncompressed size and against maximum number of files before uncompressing the file.
", "applicable": false, "asvsId": "12.1.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "363", "guid": "96e16df3-0e67-4e90-af7f-d2bb4c9f208d", "text": "Verify that a file size quota and maximum number of files per user is enforced to ensure that a single user cannot fill up the storage with too many files, or excessively large files.
", "applicable": false, "asvsId": "12.1.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" } ] }, { "id": "364", "guid": "6adbb083-30f9-4296-bc42-cf6b39f73461", "heading": "File Integrity", "asvsId": "12.2", "ord": 2, "type": "SEC", "children": [ { "id": "365", "guid": "331e5813-6641-4ac1-944a-56981e453bd6", "text": "Verify that files obtained from untrusted sources are validated to be of expected type based on the file's content.
", "applicable": false, "asvsId": "12.2.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" } ] }, { "id": "366", "guid": "e0bc513e-4cfd-474e-9803-279cc3d1b333", "heading": "File Execution", "asvsId": "12.3", "ord": 3, "type": "SEC", "children": [ { "id": "367", "guid": "92f42fe6-e42f-4d27-a2aa-7090da13265a", "text": "Verify that user-submitted filename metadata is not used directly by system or framework filesystems and that a URL API is used to protect against path traversal.
", "applicable": false, "asvsId": "12.3.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "368", "guid": "0913a24e-14aa-441e-9727-bcbbaf9f9272", "text": "Verify that user-submitted filename metadata is validated or ignored to prevent the disclosure, creation, updating or removal of local files (LFI).
", "applicable": false, "asvsId": "12.3.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "369", "guid": "ec45723f-d342-4a24-bb45-a7863caadabc", "text": "Verify that user-submitted filename metadata is validated or ignored to prevent the disclosure or execution of remote files via Remote File Inclusion (RFI) or Server-side Request Forgery (SSRF) attacks.
", "applicable": false, "asvsId": "12.3.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "370", "guid": "e3511dc8-9616-463f-81a2-f0b65bc9cd24", "text": "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.
", "applicable": false, "asvsId": "12.3.4", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "371", "guid": "8ecf4655-3df2-496e-8268-921ab8f01928", "text": "Verify that untrusted file metadata is not used directly with system API or libraries, to protect against OS command injection.
", "applicable": false, "asvsId": "12.3.5", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" }, { "id": "372", "guid": "3d8a5f2c-ccf9-40e2-bebe-179149532cd6", "text": "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.
", "applicable": false, "asvsId": "12.3.6", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 6, "type": "REQ" } ] }, { "id": "373", "guid": "d8d4182b-2754-40e9-aaed-45772835210a", "heading": "File Storage", "asvsId": "12.4", "ord": 4, "type": "SEC", "children": [ { "id": "374", "guid": "0bf373fb-9f7a-48a1-8498-51783b1c16c7", "text": "Verify that files obtained from untrusted sources are stored outside the web root, with limited permissions.
", "applicable": false, "asvsId": "12.4.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "375", "guid": "d276355b-4815-4d93-9796-41840bcca612", "text": "Verify that files obtained from untrusted sources are scanned by antivirus scanners to prevent upload and serving of known malicious content.
", "applicable": false, "asvsId": "12.4.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" } ] }, { "id": "376", "guid": "0264a997-44dd-4427-94f8-7ada226a97ec", "heading": "File Download", "asvsId": "12.5", "ord": 5, "type": "SEC", "children": [ { "id": "377", "guid": "eee26241-8911-4768-894c-3b2d75a933ff", "text": "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.
", "applicable": false, "asvsId": "12.5.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "378", "guid": "04156a50-4314-4d8d-b5d5-f7079d12b4c5", "text": "Verify that direct requests to uploaded files will never be executed as HTML/JavaScript content.
", "applicable": false, "asvsId": "12.5.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" } ] }, { "id": "379", "guid": "dec63aad-1445-4de2-ba1b-e9d26d2d5386", "heading": "SSRF Protection", "asvsId": "12.6", "ord": 6, "type": "SEC", "children": [ { "id": "380", "guid": "42a70cf5-1ed8-4b7c-9c66-6da71fb98954", "text": "Verify that the web or application server is configured with an allow list of resources or systems to which the server can send requests or load data/files from.
", "applicable": false, "asvsId": "12.6.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" } ] } ] }, { "id": "381", "guid": "c38f3112-e0c6-4f36-b80f-2ed88aedc12b", "heading": "API and Web Service", "asvsId": "13", "help": "Control Objective
Ensure that a verified application that uses trusted service layer APIs (commonly using JSON or XML or GraphQL) has:
Please read this chapter in combination with all other chapters at this same level; we no longer duplicate authentication or API session management concerns.
References
For more information, see also:
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.
", "applicable": false, "asvsId": "13.1.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "385", "guid": "c54b7ca8-89cf-40b3-8714-5178e2aff13a", "text": "Verify API URLs do not expose sensitive information, such as the API key, session tokens etc.
", "applicable": false, "asvsId": "13.1.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "386", "guid": "7cfd28fc-0eeb-4c41-a75c-ac8e9dbb3501", "text": "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.
", "applicable": false, "asvsId": "13.1.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "387", "guid": "7da56631-63cd-4c82-b8cd-774fe12c37bc", "text": "Verify that requests containing unexpected or missing content types are rejected with appropriate headers (HTTP response status 406 Unacceptable or 415 Unsupported Media Type).
", "applicable": false, "asvsId": "13.1.5", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" } ] }, { "id": "388", "guid": "d42ecc99-b892-4379-8b5f-5b66e628516c", "heading": "RESTful Web Service", "asvsId": "13.2", "help": "JSON schema validation is in a draft stage of standardization (see references). When considering using JSON schema validation, which is best practice for RESTful web services, consider using these additional data validation strategies in combination with JSON schema validation:
Once the JSON schema validation standard is formalized, ASVS will update its advice in this area. Carefully monitor any JSON schema validation libraries in use, as they will need to be updated regularly until the standard is formalized and bugs are ironed out of reference implementations.
", "ord": 2, "type": "SEC", "children": [ { "id": "389", "guid": "511335a3-a6be-469c-a6e8-e92c6ea8b587", "text": "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.
", "applicable": false, "asvsId": "13.2.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "390", "guid": "8d6dbd6d-843c-49a8-a0c6-c7d5ad00052a", "text": "Verify that JSON schema validation is in place and verified before accepting input.
", "applicable": false, "asvsId": "13.2.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "391", "guid": "bc637551-e04c-4ee2-9021-5b1b7e87a246", "text": "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: double submit cookie pattern, CSRF nonces, or Origin request header checks.
", "applicable": false, "asvsId": "13.2.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "393", "guid": "e9a66937-75ef-4b38-8eac-9b2875ccc82a", "text": "Verify that REST services explicitly check the incoming Content-Type to be the expected one, such as application/xml or application/json.
", "applicable": false, "asvsId": "13.2.5", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" }, { "id": "394", "guid": "e61ba1f1-6ee2-40ec-9653-c89625b6f769", "text": "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.
", "applicable": false, "asvsId": "13.2.6", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 6, "type": "REQ" } ] }, { "id": "395", "guid": "5c5fbd51-ccf3-45de-bb5c-6ff12a18fb3a", "heading": "SOAP Web Service", "asvsId": "13.3", "help": "Note: Due to issues with XXE attacks against DTDs, DTD validation should not be used, and framework DTD evaluation disabled as per the requirements set out in V14 Configuration.
", "ord": 3, "type": "SEC", "children": [ { "id": "396", "guid": "8ad1b10e-5618-441f-bc7d-f48f069dec13", "text": "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.
", "applicable": false, "asvsId": "13.3.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "397", "guid": "1dbdc812-7777-4bbd-815b-570f45ccb390", "text": "Verify that the message payload is signed using WS-Security to ensure reliable transport between client and service.
", "applicable": false, "asvsId": "13.3.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" } ] }, { "id": "398", "guid": "4caa90b9-8981-48ec-8814-5731a58fb40f", "heading": "GraphQL", "asvsId": "13.4", "ord": 4, "type": "SEC", "children": [ { "id": "399", "guid": "cdb3fad9-3a1c-46cb-9f31-82c232afe090", "text": "Verify that a query allow list or a combination of depth limiting and amount limiting is used to prevent GraphQL or data layer expression Denial of Service (DoS) as a result of expensive, nested queries. For more advanced scenarios, query cost analysis should be used.
", "applicable": false, "asvsId": "13.4.1", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "400", "guid": "f6524229-870f-4a7d-813e-1c74fd905b77", "text": "Verify that GraphQL or other data layer authorization logic should be implemented at the business logic layer instead of the GraphQL layer.
", "applicable": false, "asvsId": "13.4.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" } ] } ] }, { "id": "401", "guid": "36f18f98-7e12-43d0-ad77-539eaee9e499", "heading": "Configuration", "asvsId": "14", "help": "Control Objective
Ensure that a verified application has:
Configuration of the application out of the box should be safe to be on the Internet, which means a safe out of the box configuration.
References
For more information, see also:
Build pipelines are the basis for repeatable security - every time something insecure is discovered, it can be resolved in the source code, build or deployment scripts, and tested automatically. We are strongly encouraging the use of build pipelines with automatic security and dependency checks that warn or break the build to prevent known security issues being deployed into production. Manual steps performed irregularly directly leads to avoidable security mistakes.
As the industry moves to a DevSecOps model, it is important to ensure the continued availability and integrity of deployment and configuration to achieve a \"known good\" state. In the past, if a system was hacked, it would take days to months to prove that no further intrusions had taken place. Today, with the advent of software defined infrastructure, rapid A/B deployments with zero downtime, and automated containerized builds, it is possible to automatically and continuously build, harden, and deploy a \"known good\" replacement for any compromised system.
If traditional models are still in place, then manual steps must be taken to harden and back up that configuration to allow the compromised systems to be quickly replaced with high integrity, uncompromised systems in a timely fashion.
Compliance with this section requires an automated build system, and access to build and deployment scripts.
", "ord": 1, "type": "SEC", "children": [ { "id": "403", "guid": "35474882-8b1f-4b68-81da-eccb7b608a9e", "text": "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.
", "applicable": true, "asvsId": "14.1.1", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "404", "guid": "4df4dc73-958c-46a6-a900-b380551c630c", "text": "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.
", "applicable": false, "asvsId": "14.1.2", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "405", "guid": "a90dd359-d902-4739-96b6-9b4b637d83c0", "text": "Verify that server configuration is hardened as per the recommendations of the application server and frameworks in use.
", "applicable": false, "asvsId": "14.1.3", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "406", "guid": "653ba639-c0df-4a19-bd42-505e5604186c", "text": "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.
", "applicable": true, "asvsId": "14.1.4", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "407", "guid": "20689ef7-130b-4f63-b756-a5c8358629b1", "text": "Verify that authorized administrators can verify the integrity of all security-relevant configurations to detect tampering.
", "applicable": true, "asvsId": "14.1.5", "l1": "NREQ", "l2": "NREQ", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" } ] }, { "id": "408", "guid": "d634bd12-1158-4dab-9b3d-e95758e870d0", "heading": "Dependency", "asvsId": "14.2", "help": "Dependency management is critical to the safe operation of any application of any type. Failure to keep up to date with outdated or insecure dependencies is the root cause of the largest and most expensive attacks to date.
Note: At Level 1, 14.2.1 compliance relates to observations or detections of client-side and other libraries and components, rather than the more accurate build-time static code analysis or dependency analysis. These more accurate techniques could be discoverable by interview as required.
", "ord": 2, "type": "SEC", "children": [ { "id": "409", "guid": "3f2a4198-b05a-4910-9f3e-4ad8cd7ae5ae", "text": "Verify that all components are up to date, preferably using a dependency checker during build or compile time. (C2)
", "applicable": true, "asvsId": "14.2.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "410", "guid": "dee4f119-fa3f-4a4a-a46e-c261e3ff72da", "text": "Verify that all unneeded features, documentation, sample applications and configurations are removed.
", "applicable": true, "asvsId": "14.2.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "411", "guid": "c3eed1d9-2644-4410-91a3-920140cdafb1", "text": "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.
", "applicable": false, "asvsId": "14.2.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "412", "guid": "68389d84-73c0-4a0c-8447-476ae07cb716", "text": "Verify that third party components come from pre-defined, trusted and continually maintained repositories. (C2)
", "applicable": false, "asvsId": "14.2.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "413", "guid": "450fd1df-6bbc-47ff-a262-db3145fca5ed", "text": "Verify that a Software Bill of Materials (SBOM) is maintained of all third party libraries in use. (C2)
", "applicable": false, "asvsId": "14.2.5", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" }, { "id": "414", "guid": "e053202c-1178-41c9-bdf8-43daa2d07e42", "text": "Verify that the attack surface is reduced by sandboxing or encapsulating third party libraries to expose only the required behaviour into the application. (C2)
", "applicable": false, "asvsId": "14.2.6", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 6, "type": "REQ" } ] }, { "id": "415", "guid": "15f2d992-370b-464b-ae38-3cee3af93e38", "heading": "Unintended Security Disclosure", "asvsId": "14.3", "help": "Configurations for production should be hardened to protect against common attacks, such as debug consoles, raise the bar for Cross-site Scripting (XSS) and Remote File Inclusion (RFI) attacks, and to eliminate trivial information discovery \"vulnerabilities\" that are the unwelcome hallmark of many penetration testing reports. Many of these issues are rarely rated as a significant risk, but they are chained together with other vulnerabilities. If these issues are not present by default, it raises the bar before most attacks can succeed.
", "ord": 3, "type": "SEC", "children": [ { "id": "417", "guid": "c6dbf15c-fbd8-41ec-a64a-53a368679dfb", "text": "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.
", "applicable": false, "asvsId": "14.3.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "418", "guid": "57ebc4f4-a7c6-485b-844d-c46d0fbf61b1", "text": "Verify that the HTTP headers or any part of the HTTP response do not expose detailed version information of system components.
", "applicable": false, "asvsId": "14.3.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" } ] }, { "id": "419", "guid": "b84e3e80-9853-44fd-a4f9-3a8fb7a46329", "heading": "HTTP Security Headers", "asvsId": "14.4", "ord": 4, "type": "SEC", "children": [ { "id": "420", "guid": "6a8aec93-bd3e-41e5-a25f-a0a79bd7b88f", "text": "Verify that every HTTP response contains a Content-Type header. Also specify a safe character set (e.g., UTF-8, ISO-8859-1) if the content types are text/*, /+xml and application/xml. Content must match with the provided Content-Type header.
", "applicable": false, "asvsId": "14.4.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "421", "guid": "e0042258-6f9f-4d6f-8a1b-77f2d59b3c77", "text": "Verify that all API responses contain a Content-Disposition: attachment; filename=\"api.json\" header (or other appropriate filename for the content type).
", "applicable": false, "asvsId": "14.4.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "422", "guid": "1fe27395-5278-42cb-a426-ca4c8848dec3", "text": "Verify that a Content Security Policy (CSP) response header is in place that helps mitigate impact for XSS attacks like HTML, DOM, JSON, and JavaScript injection vulnerabilities.
", "applicable": false, "asvsId": "14.4.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "423", "guid": "7e7bcac3-f93f-490e-aa95-fe388f7c6971", "text": "Verify that all responses contain a X-Content-Type-Options: nosniff header.
", "applicable": false, "asvsId": "14.4.4", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" }, { "id": "424", "guid": "fa341134-ba89-4598-8d19-e02a212adca3", "text": "Verify that a Strict-Transport-Security header is included on all responses and for all subdomains, such as Strict-Transport-Security: max-age=15724800; includeSubdomains.
", "applicable": false, "asvsId": "14.4.5", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 5, "type": "REQ" }, { "id": "425", "guid": "0585d70b-d9d2-44c5-ba9a-39f32009eba6", "text": "Verify that a suitable Referrer-Policy header is included to avoid exposing sensitive information in the URL through the Referer header to untrusted parties.
", "applicable": false, "asvsId": "14.4.6", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 6, "type": "REQ" }, { "id": "426", "guid": "468e4876-2259-4641-b8e8-c14b486ba6ae", "text": "Verify that the content of a web application cannot be embedded in a third-party site by default and that embedding of the exact resources is only allowed where necessary by using suitable Content-Security-Policy: frame-ancestors and X-Frame-Options response headers.
", "applicable": false, "asvsId": "14.4.7", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 7, "type": "REQ" } ] }, { "id": "427", "guid": "eb8d9f10-d5c5-4d54-969a-710fa5a25509", "heading": "HTTP Request Header Validation", "asvsId": "14.5", "ord": 5, "type": "SEC", "children": [ { "id": "428", "guid": "2e67a091-1a7c-4595-8bc3-9ee2a6777ba4", "text": "Verify that the application server only accepts the HTTP methods in use by the application/API, including pre-flight OPTIONS, and logs/alerts on any requests that are not valid for the application context.
", "applicable": false, "asvsId": "14.5.1", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 1, "type": "REQ" }, { "id": "429", "guid": "d65c9a2d-c73e-4aed-851c-1dc338fcc832", "text": "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.
", "applicable": false, "asvsId": "14.5.2", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 2, "type": "REQ" }, { "id": "430", "guid": "cf263396-2170-48b5-bcc0-645d5304f2c2", "text": "Verify that the Cross-Origin Resource Sharing (CORS) Access-Control-Allow-Origin header uses a strict allow list of trusted domains and subdomains to match against and does not support the \"null\" origin.
", "applicable": false, "asvsId": "14.5.3", "cwe": "", "l1": "REQ", "l1text": "✓", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 3, "type": "REQ" }, { "id": "431", "guid": "4b58d9b9-86f1-49b8-ac05-cb977236d116", "text": "Verify that HTTP headers added by a trusted proxy or SSO devices, such as a bearer token, are authenticated by the application.
", "applicable": false, "asvsId": "14.5.4", "cwe": "", "l1": "NREQ", "l2": "REQ", "l2text": "✓", "l3": "REQ", "l3text": "✓", "ord": 4, "type": "REQ" } ] } ] }, { "id": "432", "guid": "82d97a40-8acd-4d93-af02-31ab90d6a270", "heading": "Appendix A: Glossary", "type": "INFO", "children": [ { "id": "433", "guid": "cef423bc-707e-4cf4-84ad-2deaf7099ae2", "text": "The following OWASP projects are most likely to be useful to users/adopters of this standard:
", "type": "INFO" }, { "id": "436", "guid": "23a75b31-104b-4c22-a3f5-70e171bfff7b", "heading": "OWASP Core Projects", "type": "INFO", "children": [ { "id": "437", "guid": "58739236-f514-4a37-8864-60251db8731c", "text": "This project has a number of cheat sheets which will be relevant for different topics in the ASVS.
There is a mapping to the ASVS which can be found here: https://cheatsheetseries.owasp.org/cheatsheets/IndexASVS.html
", "type": "INFO" } ] }, { "id": "440", "guid": "6f8eed6f-a802-4ff1-b57e-edc408389331", "heading": "Mobile Security Related Projects", "type": "INFO", "children": [ { "id": "441", "guid": "1abbf978-3a67-48d4-92c2-afa5da01ff9c", "text": "Similarly, the following web sites are most likely to be useful to users/adopters of this standard
This chapter was originally in the main branch, but with the work that the OWASP IoT team has done, it doesn't make sense to maintain two different threads on the subject. For the 4.0 release, we are moving this to the Appendix, and urge all who require this, to rather use the main OWASP IoT project
", "type": "INFO" }, { "id": "450", "guid": "fd34e859-0a1a-4c11-acd0-de7ee4773b9d", "heading": "Control Objective", "type": "INFO", "children": [ { "id": "451", "guid": "38bfa37f-c2ce-4083-8a74-29990385049b", "text": "Embedded/IoT devices should:
| # | Description | L1 | L2 | L3 | Since |
|---|---|---|---|---|---|
| C.1 | Verify that application layer debugging interfaces such USB, UART, and other serial variants are disabled or protected by a complex password. | ✓ | ✓ | ✓ | 4.0 |
| C.2 | Verify that cryptographic keys and certificates are unique to each individual device. | ✓ | ✓ | ✓ | 4.0 |
| C.3 | Verify that memory protection controls such as ASLR and DEP are enabled by the embedded/IoT operating system, if applicable. | ✓ | ✓ | ✓ | 4.0 |
| C.4 | Verify that on-chip debugging interfaces such as JTAG or SWD are disabled or that available protection mechanism is enabled and configured appropriately. | ✓ | ✓ | ✓ | 4.0 |
| C.5 | Verify that trusted execution is implemented and enabled, if available on the device SoC or CPU. | ✓ | ✓ | ✓ | 4.0 |
| C.6 | Verify that sensitive data, private keys and certificates are stored securely in a Secure Element, TPM, TEE (Trusted Execution Environment), or protected using strong cryptography. | ✓ | ✓ | ✓ | 4.0 |
| C.7 | Verify that the firmware apps protect data-in-transit using transport layer security. | ✓ | ✓ | ✓ | 4.0 |
| C.8 | Verify that the firmware apps validate the digital signature of server connections. | ✓ | ✓ | ✓ | 4.0 |
| C.9 | Verify that wireless communications are mutually authenticated. | ✓ | ✓ | ✓ | 4.0 |
| C.10 | Verify that wireless communications are sent over an encrypted channel. | ✓ | ✓ | ✓ | 4.0 |
| C.11 | Verify that any use of banned C functions are replaced with the appropriate safe equivalent functions. | ✓ | ✓ | ✓ | 4.0 |
| C.12 | Verify that each firmware maintains a software bill of materials cataloging third-party components, versioning, and published vulnerabilities. | ✓ | ✓ | ✓ | 4.0 |
| C.13 | Verify all code including third-party binaries, libraries, frameworks are reviewed for hardcoded credentials (backdoors). | ✓ | ✓ | ✓ | 4.0 |
| C.14 | Verify that the application and firmware components are not susceptible to OS Command Injection by invoking shell command wrappers, scripts, or that security controls prevent OS Command Injection. | ✓ | ✓ | ✓ | 4.0 |
| C.15 | Verify that the firmware apps pin the digital signature to a trusted server(s). | ✓ | ✓ | 4.0 | |
| C.16 | Verify the presence of tamper resistance and/or tamper detection features. | ✓ | ✓ | 4.0 | |
| C.17 | Verify that any available Intellectual Property protection technologies provided by the chip manufacturer are enabled. | ✓ | ✓ | 4.0 | |
| C.18 | Verify security controls are in place to hinder firmware reverse engineering (e.g., removal of verbose debugging symbols). | ✓ | ✓ | 4.0 | |
| C.19 | Verify the device validates the boot image signature before loading. | ✓ | ✓ | 4.0 | |
| C.20 | Verify that the firmware update process is not vulnerable to time-of-check vs time-of-use attacks. | ✓ | ✓ | 4.0 | |
| C.21 | Verify the device uses code signing and validates firmware upgrade files before installing. | ✓ | ✓ | 4.0 | |
| C.22 | Verify that the device cannot be downgraded to old versions (anti-rollback) of valid firmware. | ✓ | ✓ | 4.0 | |
| C.23 | Verify usage of cryptographically secure pseudo-random number generator on embedded device (e.g., using chip-provided random number generators). | ✓ | ✓ | 4.0 | |
| C.24 | Verify that firmware can perform automatic firmware updates upon a predefined schedule. | ✓ | ✓ | 4.0 | |
| C.25 | Verify that the device wipes firmware and sensitive data upon detection of tampering or receipt of invalid message. | ✓ | 4.0 | ||
| C.26 | Verify that only micro controllers that support disabling debugging interfaces (e.g. JTAG, SWD) are used. | ✓ | 4.0 | ||
| C.27 | Verify that only micro controllers that provide substantial protection from de-capping and side channel attacks are used. | ✓ | 4.0 | ||
| C.28 | Verify that sensitive traces are not exposed to outer layers of the printed circuit board. | ✓ | 4.0 | ||
| C.29 | Verify that inter-chip communication is encrypted (e.g. Main board to daughter board communication). | ✓ | 4.0 | ||
| C.30 | Verify the device uses code signing and validates code before execution. | ✓ | 4.0 | ||
| C.31 | Verify that sensitive information maintained in memory is overwritten with zeros as soon as it is no longer required. | ✓ | 4.0 | ||
| C.32 | Verify that the firmware apps utilize kernel containers for isolation between apps. | ✓ | 4.0 | ||
| C.33 | Verify that secure compiler flags such as -fPIE, -fstack-protector-all, -Wl,-z,noexecstack, -Wl,-z,noexecheap are configured for firmware builds. | ✓ | 4.0 | ||
| C.34 | Verify that micro controllers are configured with code protection (if applicable). | ✓ | 4.0 |
For more information, see also:
© Copyright by Eccam s.r.o. All rights reserved.
", "type": "INF" }, { "id": "1", "guid": "132dcab5-8b8b-46c0-ab37-e3752aab1331", "heading": "Introduction", "instructions": "This document describes product or process failures using Failure Mode and Effects Analysis (FMEA) method.
You can identify potential failure modes, their causes, and effects on the system or stakeholders.
For each identified cause and effect you can assess its risk and determine corrective actions.
For more information see Effective FMEAs by Carl Carlson.
", "type": "SEC", "children": [ { "id": "5", "guid": "a85e7603-54d0-41ab-aa96-fd4f20dc2720", "heading": "Purpose", "instructions": "Identify the product specified in this document.
", "type": "SEC", "children": [ { "id": "36", "guid": "0f545e62-d6b0-4c2c-b6f6-1b4a3905327c", "text": "The main purpose of this document is to provide new ReqView users a working example of a document describing project risks by means of Failure Mode and Effects Analysis (FMEA) method.
", "type": "INF" } ] }, { "id": "27", "guid": "6dda73cb-48b7-4ea8-9ff0-585187c2f4df", "heading": "Scope", "instructions": "Briefly describe the scope of the product risk analysis.
", "type": "SEC", "children": [ { "id": "28", "guid": "fb943a0f-aaa4-4cda-a2de-b7643af054aa", "text": "This document describes risks related to ReqView functionality specified in [DEMO-NEEDS] document.
", "type": "INF" }, { "id": "46", "guid": "8eae3e1a-7e4d-4f27-be81-85e2cd387fa3", "text": "Note: The application functionality corresponds to ReqView v1.0 released in 2015. Check all advanced requirements management features it offers now.
", "type": "INF" } ] }, { "id": "30", "guid": "45b82e0f-8430-41ab-9630-7ab0d692acf1", "heading": "Definitions", "type": "SEC", "children": [ { "id": "35", "guid": "400a777f-4ba0-44d8-bc2d-b25513feea0f", "text": "This section provides example definitions of probability, severability and detectability taken from Wikipedia.
", "type": "INF" }, { "id": "32", "guid": "42dcfdef-e805-4e70-bb81-2221b59ba4de", "text": "Severity:
| Rating | Meaning |
|---|---|
| 1-2 | No relevant effect on reliability or safety |
| 3-4 | Very minor, no damage, no injuries, only results in a maintenance action (only noticed by discriminating customers) |
| 5-6 | Minor, low damage, light injuries (affects very little of the system, noticed by average customer) |
| 7-8 | Critical (causes a loss of primary function; Loss of all safety Margins, 1 failure away from a catastrophe, severe damage, severe injuries, max 1 possible death ) |
| 9-10 | Catastrophic (product becomes inoperative; the failure may result in complete unsafe operation and possible multiple deaths) |
Define rank for severity from 1 (no effect) up to 10 (catastrophic) used further in the document, see example.
", "type": "INF" }, { "id": "31", "guid": "1e1544d3-9614-4138-886b-b42392300336", "text": "Probability:
| Rating | Meaning |
|---|---|
| 1-2 | Extremely Unlikely (Virtually impossible or No known occurrences on similar products or processes, with many running hours) |
| 3-4 | Remote (relatively few failures) |
| 5-6 | Occasional (occasional failures) |
| 7-8 | Reasonably Possible (repeated failures) |
| 9-10 | Frequent (failure is almost inevitable) |
Define rank for probability from 1 (extremely unlikely) to 10 (inevitable) used further in the document, see example.
", "type": "INF" }, { "id": "33", "guid": "3cbd0c5e-e1ff-4e92-8ed6-90d22c2d3bc7", "text": "Detectability:
| Rating | Meaning |
|---|---|
| 1 | Certain – fault will be caught on test - e.g. Poka-Yoke |
| 2-3 | Almost certain |
| 4-5 | High |
| 6-7 | Moderate |
| 8-9 | Low |
| 10 | Fault is undetected by Operators or Maintainers |
Define rank for detection from 1 (almost certain) up to 10 (absolute uncertainly) used further in the document, see example.
", "type": "INF" } ] } ] }, { "id": "2", "guid": "226aa626-520e-47a1-b4ed-3981c7d2617c", "heading": "Risks", "instructions": "Identify potential failure modes, their causes, and effects on the system or stakeholders. For each identified cause and effect assess its risk and determine corrective actions. For more information see Effective FMEAs by Carl Carlson.
Organize failures by items or process step into sections with the following hierarchy: Function → Failure Mode → Potential Cause → Corrective Action.
Function
Failure Modes
Potential Cause
Corrective Actions
Application is reliable
", "type": "FUNC", "children": [ { "id": "22", "guid": "c6127b53-d3c3-43db-b17b-a7305ed990c1", "text": "Loss of data entered by users
", "effects": "Users stop using the application
", "severity": 6, "type": "FAIL", "children": [ { "id": "40", "guid": "fd9820d7-ae42-411a-8662-542b1328fbbb", "text": "The application crashes due to a bug
", "detectability": 8, "detection": "Stability test of the application with corner case data.
", "probability": 3, "severity": 6, "type": "CAUSE", "children": [ { "id": "26", "guid": "0a3c9583-0ed9-444c-ba41-ec92411357a5", "text": "Implement Autosave functionality storing immediately all changes into a persistent application storage so that only the last unsaved change is lost.
", "detectability": 8, "probability": 3, "responsibility": "Libor Bus", "severity": 2, "targetDate": "2015-12-31", "type": "ACT" } ] }, { "id": "44", "guid": "1df2d01c-25bd-42e0-8b67-ae56c3345ddd", "text": "Functional bug in user data handling
", "detectability": 4, "detection": "Unit tests of user data handling with 90% coverage.
", "probability": 3, "severity": 6, "type": "CAUSE", "children": [ { "id": "45", "guid": "ca3122fe-35fd-4b92-bb92-e05cdd01e4d7", "text": "Unit tests with 99% coverage
", "detectability": 1, "probability": 3, "responsibility": "Libor Bus", "severity": 6, "targetDate": "2018-09-30", "type": "ACT" } ] } ] } ] } ] } ] }, { "id": "37", "guid": "1d2eccc0-4739-4c29-9e66-03dd9e28d9e4", "heading": "References", "type": "SEC", "children": [ { "id": "38", "guid": "cf880862-c782-47de-a092-07d3f5933ddc", "text": "[DEMO-NEEDS]: ReqView User Needs
", "type": "INF" } ] } ], "attributes": { "detectability": { "name": "DET", "type": "int" }, "detection": { "name": "Detection Mode", "type": "xhtml" }, "effects": { "name": "Potential Effects", "type": "xhtml" }, "instructions": { "help": true, "type": "xhtml" }, "probability": { "name": "PROB", "type": "int" }, "responsibility": { "name": "Responsibility", "type": "string" }, "severity": { "name": "SEV", "type": "int" }, "targetDate": { "name": "Target Date", "type": "date" }, "type": { "name": "Type", "type": "enum", "values": [ { "key": "FUNC", "label": "Function" }, { "key": "FAIL", "label": "Failure Mode" }, { "key": "CAUSE", "label": "Potential Cause" }, { "key": "ACT", "label": "Corrective Action" }, { "key": "SEC", "label": "Section" }, { "key": "INF", "label": "Information" } ] } }, "templateColumns": { "283578a7-4cef-47a9-b7ef-68d9f81038a7": { "label": "Downstream Traceability", "template": "{{#if (eval type \"==\" \"ACT\")}}\n{{#if (hasInlinks \"mitigation\")}}\n{{#eachInlinkWith type=\"mitigation\"}}\n◂ {{#hyperlink}}{{docObjId}}{{/hyperlink}}: {{shortDescription maxLength=80}}
\n{{#if (hasInlinks \"verification\")}}\n{{#eachInlinkWith type=\"verification\"}}\n◂ {{#hyperlink}}{{docObjId}}{{/hyperlink}}: {{shortDescription maxLength=80}}
\n{{/eachInlinkWith}}\n{{else}}\nMissing verification links!\n{{/if}}\n{{/eachInlinkWith}}\n{{else}}\n
Missing mitigation links!\n{{/if}}\n{{/if}}" }, "74b9b882-3a3e-4f19-891e-c993faa3a574": { "label": "RPN", "template": "{{#if (eval (eval type \"==\" \"CAUSE\") \"||\" (eval type \"==\" \"ACT\"))}}\n{{var \"rpn\" (eval (eval detectability \"*\" probability) \"*\" severity)}}\n
© Copyright by Eccam s.r.o. All rights reserved.
", "type": "INF" }, { "id": "1", "guid": "abbd78ca-b069-4ea0-9457-104d2e72cff4", "heading": "Introduction", "helpRef": "8.5", "type": "SEC", "children": [ { "id": "2", "guid": "3acc2187-2a22-4525-ba60-b41e8c461f2d", "heading": "Purpose", "helpRef": "9.6.2", "type": "SEC", "children": [ { "id": "180", "guid": "7ee38bfd-067c-4155-8e44-224f480e6da4", "text": "The main purpose of this document is to provide a working example of a Software Requirements Specification (SRS) based on ISO/IEC/IEEE 29148:2018 standard.
Note: This is an example document, which is not complete.
", "type": "INF" } ] }, { "id": "3", "guid": "5dc86839-ef47-4911-914e-147d21253fdb", "heading": "Scope", "helpRef": "9.6.3", "type": "SEC", "children": [ { "id": "32", "guid": "f077d25c-cb26-46d2-89be-67b2627516ac", "text": "This document specifies SW requirements for user needs described in [DEMO-NEEDS] document.
", "type": "INF" }, { "id": "36", "guid": "21ae8c24-0721-466b-a0dc-f85208271261", "text": "The application allows users to:
The application stores documents as human readable files with open file format.
", "type": "INF" }, { "id": "38", "guid": "2e47b12e-0d7e-40e3-a348-865dec03d572", "text": "The application runs offline without connection to any server.
", "type": "INF" }, { "id": "203", "guid": "f93b7df1-ac89-421b-99e8-40c70b247cda", "text": "Note: The application functionality corresponds to ReqView v1.0 released in 2015. Check all advanced requirements management features it offers now.
", "type": "INF" } ] }, { "id": "4", "guid": "3348dd4f-3dff-465c-afa7-11bf80f39724", "heading": "Product perspective", "helpRef": "9.6.4", "type": "SEC", "children": [ { "id": "5", "guid": "35606406-f8ea-4f5f-ab01-adbfc831ebf4", "heading": "System interfaces", "helpRef": "9.6.4.1", "type": "SEC", "children": [ { "id": "47", "guid": "61412017-7f8d-447b-85c9-0f813b62a8ed", "text": "The application runs on Windows, Linux and Mac.
", "type": "INF" } ] }, { "id": "6", "guid": "b818ebd3-41f9-4a7c-87af-8f281d39c0d9", "heading": "User interfaces", "helpRef": "9.6.4.2", "type": "SEC", "children": [ { "id": "45", "guid": "63a890bc-51c0-42cd-af9e-0039969a3fb2", "text": "The application GUI provides menus, toolbars, buttons, panes, containers, grids allowing for easy control by a keyboard and a mouse.
", "type": "INF" } ] }, { "id": "7", "guid": "b546714f-b696-4816-bf65-760713be73f6", "heading": "Hardware interfaces", "helpRef": "9.6.4.3", "type": "SEC" }, { "id": "8", "guid": "dce8317a-1c9f-4af4-b3fe-292de89c5bbd", "heading": "Software interfaces", "helpRef": "9.6.4.4", "type": "SEC", "children": [ { "id": "166", "guid": "06964a20-0a59-4221-88aa-a7fb3233f542", "text": "The application allows import a structured MS Word document via HTML data format.
", "type": "INF" }, { "id": "168", "guid": "0db3883f-26ce-4f0b-9dca-f391d9a70b83", "text": "The application allows populating a MS Word document with project data via HTML data format.
", "type": "INF" }, { "id": "167", "guid": "9aeebf52-a5a3-4d10-8722-a071a7b6fa23", "text": "The application allows import / export a list of requirements from / to MS Excel sheet via CSV data format.
", "type": "INF" }, { "id": "169", "guid": "f11974f8-47fb-4de0-9502-f03cc4b7f780", "text": "The application stores project data in JSON format to enable easy integration with 3rd party applications.
", "type": "INF" } ] }, { "id": "9", "guid": "e4ef2496-c912-4b40-babb-230cfbee7748", "heading": "Communications interfaces", "helpRef": "9.6.4.5", "type": "SEC" }, { "id": "10", "guid": "7fc1577d-1b59-44a4-bc06-7488c0b96903", "heading": "Memory constraints", "helpRef": "9.6.4.6", "type": "SEC" }, { "id": "11", "guid": "f3f810f8-afe6-43ab-a33e-7405ccee08e2", "heading": "Operations", "helpRef": "9.6.4.7", "type": "SEC" }, { "id": "12", "guid": "d2ba3d71-a50c-49df-afcf-697834a787fb", "heading": "Site adaptation requirements", "helpRef": "9.6.4.8", "type": "SEC" }, { "id": "13", "guid": "fa917181-7a58-4d48-8c40-db5112aa4e20", "heading": "Interfaces with services", "helpRef": "9.6.4.9", "type": "SEC" } ] }, { "id": "14", "guid": "bee467ac-cf99-47e3-80aa-a7759995b6c0", "heading": "Product functions", "helpRef": "9.6.5", "type": "SEC", "children": [ { "id": "49", "guid": "a968173a-47ac-480d-a371-fc7c04986a6e", "text": "Product functions are summarized in Section 2. User Stories of NEEDS document.
", "type": "INF", "links": { "reference": [ "NEEDS-3" ] } } ] }, { "id": "15", "guid": "cbac12e5-3a65-4e89-aaab-36f82febfbc8", "heading": "User characteristics", "helpRef": "9.6.6", "type": "SEC" }, { "id": "16", "guid": "c75e1437-b9eb-480e-a709-245d2dcd3cb6", "heading": "Limitations", "helpRef": "9.6.7", "type": "SEC" }, { "id": "17", "guid": "382740d0-a1c6-4866-8ea0-58bc12027b4a", "heading": "Assumptions and dependencies", "helpRef": "9.6.8", "type": "SEC" }, { "id": "18", "guid": "f1d0c012-8aff-4690-832a-03b1109692f7", "heading": "Definitions", "helpRef": "9.2.3", "type": "SEC", "children": [ { "id": "186", "guid": "b0526dfb-6732-416a-bbe0-afee03646984", "text": "Custom Attribute: Additional requirement property capturing additional requirements properties such as requirements source, status, priority, verification method, fit criterion, ...,
", "type": "INF" }, { "id": "188", "guid": "4b966abd-8314-40e9-86f2-486dc1a92665", "text": "Document: A structured requirements specification capturing textual requirements for a given product or service.
", "type": "INF" }, { "id": "187", "guid": "880faed9-3c9a-416e-aff2-6d79f12f0613", "text": "Link: A directed association between related requirements allowing to analyze requirements coverage, gaps and impact of changes.
", "type": "INF" }, { "id": "189", "guid": "4d8f7490-865f-4985-9e58-4ec6f131f252", "text": "Link Type: Property of traceability links allowing to analyze links with different semantic independently, e.g., satisfaction and verification links.
", "type": "INF" } ] }, { "id": "19", "guid": "bf7a35e9-6508-4c09-9f6a-d7ccf5691b99", "heading": "Acronyms and abbreviations", "helpRef": "9.2.5", "type": "SEC", "children": [ { "id": "184", "guid": "d91ed3eb-7746-429d-975d-4c63fdc2e43e", "text": "CSV: Comma Separated Values
", "type": "INF" }, { "id": "185", "guid": "55af80b1-8272-47b8-895e-354e31a6e88d", "text": "DNF: Disjunctive Normal Form
", "type": "INF" }, { "id": "181", "guid": "e35ecca6-a045-4fa4-9596-7f42bc6f873b", "text": "ID: Identifier
", "type": "INF" }, { "id": "200", "guid": "6f3c5afc-b1aa-48c9-a600-e83a88b1782e", "text": "GUI: Graphical User Interface
", "type": "INF" }, { "id": "183", "guid": "d71deb69-ea46-425b-8995-b35015418a8e", "text": "HTML: Hypertext Markup Language
", "type": "INF" }, { "id": "182", "guid": "0114d4f4-afd4-434c-a8ff-7040f7fdc5ee", "text": "SRS: Software Requirements Specification
", "type": "INF" } ] } ] }, { "id": "20", "guid": "a0c09c59-756b-43fb-8e50-5a3ff44f924d", "heading": "Requirements", "helpRef": "9.6.10", "type": "SEC", "children": [ { "id": "21", "guid": "6b56a23e-c05f-4097-9295-4446f4df2936", "heading": "External interfaces", "helpRef": "9.6.11", "type": "SEC" }, { "id": "22", "guid": "e033dea5-33b4-4e95-92d9-d003723f03b1", "heading": "Functions", "helpRef": "9.6.12", "type": "SEC", "children": [ { "id": "51", "guid": "3ff4eb01-f371-4798-abee-5212a2cf4a48", "heading": "File Operations", "type": "SEC", "children": [ { "id": "52", "guid": "9e2bf801-7398-46fe-874e-30b3c6fa870c", "heading": "Create Document", "type": "SEC", "children": [ { "id": "53", "guid": "9180992d-50de-4549-8a0e-e3009f5e1c6b", "text": "The application shall allow users to create a new empty document.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-58" ] } }, { "id": "54", "guid": "1a275816-1187-4b31-a012-4b292cf1169b", "text": "If the current document contains unsaved changes then the application shall allow users to save the changes before closing the document.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-58" ] } } ] }, { "id": "55", "guid": "6ebd5eb8-578c-4588-a014-9aa1923e34d1", "heading": "Open File", "type": "SEC", "children": [ { "id": "56", "guid": "eb0685b8-b40a-4582-9ed3-9515cc2a88fb", "text": "The application shall allow users to open a document from a chosen file.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-58" ] } } ] }, { "id": "58", "guid": "61d8f1df-04b1-4e68-9a79-1dc25e0937ad", "heading": "Save Local File", "type": "SEC", "children": [ { "id": "59", "guid": "5eecdff8-60e2-463f-88af-63ffa4cdcbeb", "text": "The application shall allow users to save the opened document into a file.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-58" ] } } ] }, { "id": "60", "guid": "43919c4d-cb1e-46d9-9008-cd0f5b4ce26f", "heading": "Document Template", "type": "SEC", "children": [ { "id": "61", "guid": "ee706ece-aa2f-4b2e-b728-9ac72e90f5f0", "text": "The application shall allow users to create a document template file from the opened document.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-14" ] } }, { "id": "62", "guid": "68d46573-6217-4a2d-8a79-681e3285339b", "text": "Document templates shall store structure of document sections and definition and values of requirement attributes.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-14" ] } }, { "id": "63", "guid": "24edae06-69eb-4cb9-86c3-b2379867fa3f", "text": "The application shall allow users to create a new document from a chosen document template file preserving the structure of document sections and the definition and values of requirement attributes.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-14" ] } } ] }, { "id": "71", "guid": "a5331502-f024-4a93-b206-cc5c8662ed0d", "heading": "Import", "type": "SEC", "children": [ { "id": "72", "guid": "2b8e2c8d-aafc-4118-88bd-2b93a98535d7", "text": "The application shall allow users to import a MS Word document preserving structure of document sections and paragraphs, rich text description of requirements and images.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-27" ] } }, { "id": "73", "guid": "d4ea7a8c-10ba-4abb-9756-505f4fb73a78", "text": "The application shall allow users to import a MS Excel table of requirements preserving section headings, levels, unformatted text description of requirements and values of custom attributes.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-71" ] } } ] }, { "id": "74", "guid": "3b0330d7-0c46-4145-9e20-d9df0122bd9c", "heading": "Export", "type": "SEC", "children": [ { "id": "76", "guid": "421512a1-4ac7-42c9-bad1-c5cc4edaa128", "text": "The application shall allow users to export the displayed document view to HTML.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-28", "NEEDS-23" ] } }, { "id": "77", "guid": "8f6f5469-dea3-4f33-9879-cf436f11cedc", "text": "The application shall allow users to export requirements to CSV.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-72", "NEEDS-23" ] } } ] } ] }, { "id": "78", "guid": "1f87c808-3f88-494a-a2a8-f06e94070f35", "heading": "Document View", "type": "SEC", "children": [ { "id": "79", "guid": "6ea8ce06-3eea-46b1-bf99-2d4a88053056", "heading": "Table of Contents", "type": "SEC", "children": [ { "id": "80", "guid": "eb4ed29a-bf91-4fa4-bf01-030880a7a7a7", "text": "The application shall display the table of contents containing section headings organized according to their document tree hierarchy.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-12" ] } }, { "id": "81", "guid": "1f498912-1755-4efe-8926-a0f1baf570bd", "text": "When user clicks on a document section in the table of contents then the application shall focus the section in the requirements table.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-12" ] } } ] }, { "id": "82", "guid": "cb320d6c-134d-4e3b-bb94-5deee1d539a4", "heading": "Requirements Table", "type": "SEC", "children": [ { "id": "83", "guid": "6575d585-782a-4db3-b352-46a5dd959500", "text": "The application shall display the document in a requirements table containing the following columns: ID, Description, Discussion, Links and a column for each custom requirement attribute.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-12", "NEEDS-17", "NEEDS-32", "NEEDS-68", "NEEDS-73" ] } }, { "id": "84", "guid": "c6a58070-2169-4115-92be-cc565054f025", "text": "The ID column of the requirements table shall display unique requirement identifiers.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-32", "NEEDS-73" ] } }, { "id": "85", "guid": "1ff1ec7c-105b-4dcf-bbb4-a297d7a6ef6c", "text": "The Description column of the requirements table shall display the section numbers, headings, requirement text descriptions and attachments.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-68", "NEEDS-17", "NEEDS-73" ] } }, { "id": "86", "guid": "81b12796-89c9-4271-a79c-23bec2d203f1", "text": "The Discussion column of the requirements table shall display requirement comments with information about comment author, date and text ordered by date and time.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-24", "NEEDS-73" ] } }, { "id": "87", "guid": "99f71e0b-7643-414f-938a-c65c4515cd2e", "text": "The Links column of the requirements table shall display requirement traceability links grouped by link types.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-21", "NEEDS-73", "NEEDS-30" ] } }, { "id": "88", "guid": "6c194076-a44c-4ffe-9e88-8a77a3308745", "text": "The application shall allow users to change width of each requirements table column.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-73" ] } }, { "id": "190", "guid": "3b4916da-cd7e-48ec-b9ca-a7c58f62c7fd", "text": "The application shall allow users to reorder requirements table columns.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-73" ] } }, { "id": "89", "guid": "41952f31-23e9-42e2-a79b-668cf98f36a6", "text": "The application shall allow users to show and hide requirements table columns except the ID column.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-73" ] } }, { "id": "90", "guid": "bed27937-e5b4-499f-b014-0e7332494b59", "text": "The application shall allow users to sort all requirements table columns except the Discussion and Links columns by ascending or descending order.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-35" ] } } ] }, { "id": "91", "guid": "e7d8e737-8841-47a3-9aaf-267a883561a0", "heading": "Detailed Information", "type": "SEC", "children": [ { "id": "92", "guid": "58061c74-c8be-4979-b98c-c1a0fe7bbc26", "text": "The application shall allow users to show and hide a pane displaying detailed information about custom attributes, discussion, traceability links or history of changes of the selected requirement.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-74", "NEEDS-30" ] } }, { "id": "93", "guid": "3e97c81e-bf63-41d6-9d4f-c4e5be1900ec", "text": "While the custom attributes pane is shown, the application shall display values of all assigned custom attributes for the selected requirement.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-74" ] } }, { "id": "94", "guid": "c6eb00d1-af9a-454e-b807-7b5b7d875d4e", "text": "While the discussion pane is shown, the application shall display all comments for the selected requirement ordered by date and time.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-74" ] } }, { "id": "96", "guid": "7bfb8d08-a141-46a6-b007-8237594294dc", "text": "While the discussion pane is shown, the application shall allow users to expand or collapse a selected comment or all displayed comments.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-74" ] } }, { "id": "97", "guid": "d7b906b3-a011-4022-b818-5e070641e763", "text": "While a displayed discussion comment is expanded, then the application shall display the date, time, author and description of the comment.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-74" ] } }, { "id": "98", "guid": "a6d6c40c-c589-4f8e-845a-eedec4ee57b5", "text": "While a displayed discussion comment is collapsed, then the application shall display the date, time and author of the comment.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-74" ] } }, { "id": "99", "guid": "956fd99d-288e-4418-8a3b-2119040ea3fc", "text": "While the links pane is shown, the application shall display all traceability links starting in or leading to the selected requirement grouped by link types and ordered by ID of the linked object.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-74", "NEEDS-30" ] } }, { "id": "142", "guid": "092ad7a0-81fa-4c64-91dc-5b3061f50e76", "text": "When user clicks on a traceability link then the application shall focus the linked requirement.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-74", "NEEDS-21", "NEEDS-30" ] } } ] } ] }, { "id": "104", "guid": "962ee448-b164-4de0-bb25-b3fc3a4bc90e", "heading": "Edit Document", "type": "SEC", "children": [ { "id": "105", "guid": "154f1c8d-a366-414e-8286-d35c0237fd8c", "heading": "Document Structure", "type": "SEC", "children": [ { "id": "106", "guid": "c84a100d-ff1d-417c-bff7-598ccbd52631", "text": "The application shall allow users to create a new requirement and place it in any document section.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-12", "NEEDS-68" ] } }, { "id": "107", "guid": "d4138097-3de7-4cc2-9205-a812d30df038", "text": "When users creates a new requirement the application shall assign it a unique ID which cannot be changed.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-32" ] } }, { "id": "108", "guid": "41abf100-7a3c-4e83-873b-48ae78bd91e9", "text": "The application shall allow users to copy selected requirements or document sections within the document.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-12" ] } }, { "id": "109", "guid": "52bc10ff-d33f-4d2a-8544-30a79ab743e8", "text": "The application shall allow users to move selected requirements or document sections within the document.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-12" ] } }, { "id": "110", "guid": "4deae666-057e-4186-84b6-0705bb601e1c", "text": "The application shall allow users to mark selected requirements or document sections as deleted.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-12" ] } }, { "id": "111", "guid": "5cbf9064-8e16-448e-8b0f-3e9fef67dc1b", "text": "The application shall allow users to undelete selected deleted requirements or document sections.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-12" ] } }, { "id": "112", "guid": "5930a2a2-19d9-49fd-a9c6-dd4b719b6e13", "text": "The application shall allow users to permanently remove selected deleted requirements or document sections from the document.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-12" ] } } ] }, { "id": "113", "guid": "217df052-498b-4d9b-acef-e839fbf96cb4", "heading": "Requirement Attributes", "type": "SEC", "children": [ { "id": "114", "guid": "22d84e0c-667a-4311-a507-07b11df15df5", "text": "The application shall allow users to edit the heading of the selected section.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-12" ] } }, { "id": "115", "guid": "60786aee-a78c-4fa3-993a-8c6a812a0105", "text": "The application shall allow users to edit the text description of the selected requirement.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-68" ] } }, { "id": "116", "guid": "bd08ea3a-368c-4098-8d38-290a20aac23f", "text": "The application shall allow users to paste an HTML content copied from MS Word, Excel or other application into the text description of the selected requirement.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-68" ] } } ] }, { "id": "118", "guid": "2d4ae7e5-3275-4b79-bf4c-356fb101b23b", "heading": "Custom Attributes", "type": "SEC", "children": [ { "id": "119", "guid": "d5391be4-b88b-4f87-a39a-c47c023eacee", "text": "The application shall allow users to define custom requirement attributes and assign them a unique ID which cannot be changed.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-19" ] } }, { "id": "121", "guid": "fffade5b-57ad-461c-b93a-eebb262488b2", "text": "The application shall allow users to set a type of each custom attribute as follows: boolean, integer number, real number, string, date, enum or XHTML.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-19" ] } }, { "id": "191", "guid": "72d7887e-24af-46ee-a5e5-175c1aafa625", "text": "The application shall allow users to set one or more values for custom attributes of enumeration type.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-19" ] } }, { "id": "122", "guid": "67baeb2b-36a3-4c13-b091-622f35f05729", "text": "When a user changes the type of a custom attribute then the application shall automatically convert all values of the attribute to the new type.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-19" ] } }, { "id": "157", "guid": "aec61759-5ec6-4eae-935b-bfe7781ce37e", "text": "If the automatic conversion fails for any attribute value, then the application shall prevent the change of custom attribute type.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-19" ] } }, { "id": "120", "guid": "65862962-dfd2-4da8-978c-2c55f91c5c2d", "text": "The application shall allow users to set an optional name of each custom attribute.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-19" ] } }, { "id": "192", "guid": "d3e7b3ae-11f9-42e2-a31e-be40b675e907", "text": "The application shall allow users to remove custom attributes.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-19" ] } }, { "id": "193", "guid": "cbef0ab4-56db-4f58-8577-aa2c9c21fc61", "text": "When a user removes a custom attribute then the application shall unset values of the attribute in all requirements.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-19" ] } }, { "id": "165", "guid": "53ece1ea-1b5f-445e-89c1-75131ed1fc27", "text": "The application shall allow users to edit custom attributes of the selected requirement.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-69" ] } } ] }, { "id": "123", "guid": "d05a605f-d86f-4a41-831f-4468ac2f4fd2", "heading": "Attachments", "type": "SEC", "children": [ { "id": "124", "guid": "fd7e1bf0-8f0b-4038-a838-0ebd8d2a07bd", "text": "The application shall allow users to attach one or more images or documents (PDF, Word, Excel, Powerpoint, Visio, …) to the selected requirement.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-17" ] } }, { "id": "126", "guid": "a599627e-7a60-4ced-9ddc-b91d93e6efaa", "text": "When a new attachment is added to the document then the application shall generate its unique attachment ID as a combination of the requirement ID and the original attachment file name.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-17" ] } }, { "id": "210", "guid": "bcc3de4e-1d0e-4d94-b978-a2a79ac939fe", "text": "The application shall display preview of image attachments in the document.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-17" ] } }, { "id": "127", "guid": "b2750a62-cad1-4597-9866-df83c68c2d87", "text": "The application shall allow users to save attachment files to the local file system.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-17" ] } }, { "id": "128", "guid": "07828501-823c-4740-833b-869b35674fd1", "text": "The application shall allow users to update content of requirement attachments from a selected file.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-17" ] } }, { "id": "129", "guid": "27709a48-48ff-44d6-943a-e095a44b1c13", "text": "The application shall allow users to permanently remove attachments from the document.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-17" ] } }, { "id": "130", "guid": "0312a27a-9e48-4619-a6de-73fa5d76b8ac", "text": "Example:
This is an example attachment.
", "type": "INF", "attachments": [ "SRS-130_1_ReqView File Data Format v11.pdf" ] } ] }, { "id": "131", "guid": "3d81ee95-2133-4700-b62f-dba603165bab", "heading": "Comments", "type": "SEC", "children": [ { "id": "132", "guid": "e8c164f7-ab10-4f10-8420-12f59a23b51b", "text": "The application shall allow users to comment the selected requirement.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-24" ] } }, { "id": "133", "guid": "ccb73f29-0562-4110-92a7-162374b024d2", "text": "When a user creates a new comment then the application shall record the current date and time and the author of the comment.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-24" ] } } ] }, { "id": "134", "guid": "a3679e97-5bba-4973-94e9-b960eb09d83d", "heading": "Traceability Links Configuration", "type": "SEC", "children": [ { "id": "135", "guid": "77aa7b20-0395-4a61-95df-d6fd539a7411", "text": "The application shall allow users to define link types and assign them a unique ID which cannot be changed.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-16" ] }, "discussion": [ { "comment": "Examples: \"satisfaction\", \"verification\", \"reference\", …
", "date": "2019-05-07T09:46:30.543Z", "author": { "name": "Libor Bus", "email": "libor.bus@eccam.com", "company": "Eccam s.r.o." } } ] }, { "id": "156", "guid": "dda5d870-a305-4417-a51b-5074288d90b6", "text": "The application shall allow users to set for each link type its name and role name of the source and target requirements.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-16" ] } }, { "id": "138", "guid": "8db3e13d-f24a-4334-afa2-b5520e6c7e11", "text": "The application shall allow users to remove link types.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-16" ] } }, { "id": "161", "guid": "e8a15ee0-6308-4cb9-a830-3d496a9f064c", "text": "When a user removes a link type then the application shall remove all traceability links of the link type from the document.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-16" ] } } ] }, { "id": "136", "guid": "d940caa3-28c6-4686-aa2e-057921cfd487", "heading": "Traceability Links", "type": "SEC", "children": [ { "id": "137", "guid": "cd1225bb-d433-461a-9813-878d12c2d18f", "text": "The application shall allow users to create directed traceability links of a chosen link type between selections of requirements or document sections.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-21" ] } }, { "id": "139", "guid": "86de1779-640a-4844-9129-61de60ec8ccc", "text": "The application shall allow users to change the link type of a selected link traceability.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-21" ] } }, { "id": "140", "guid": "c50ba614-f14c-4cd6-a893-33917e854ffb", "text": "The application shall allow users to revert direction of a selected traceability link.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-21" ] } }, { "id": "141", "guid": "306f0cd7-2a6c-402b-9591-a4d79827917a", "text": "The application shall allow users to permanently remove a selected traceability link from the document.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-21" ] } } ] }, { "id": "143", "guid": "04047547-6151-449f-8e32-800be1dbaa5f", "heading": "Auto Save", "type": "SEC", "children": [ { "id": "144", "guid": "2ae949f7-1c7c-4d82-b4f7-86c5d867cc66", "text": "The application shall automatically persist all document changes and restore them when it is restarted.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "mitigation": [ "RISKS-26" ], "satisfaction": [ "NEEDS-33" ] } }, { "id": "160", "guid": "494b27f0-5cf8-476b-a580-cb91924f6579", "text": "When user closes the document the application shall clear all persisted document data.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "mitigation": [ "RISKS-26" ], "satisfaction": [ "NEEDS-33" ] } } ] } ] }, { "id": "145", "guid": "c76206fe-b633-40c3-be8c-5046cb64469c", "heading": "Filtering", "type": "SEC", "children": [ { "id": "146", "guid": "b54671b4-52f1-47cf-849d-53fc4127b08e", "heading": "Requirements Filter", "type": "SEC", "children": [ { "id": "147", "guid": "74ddcacb-d7ba-496c-bcc9-2b0322b61d87", "text": "The application shall allow users to filter requirements according to a condition in disjunctive normal form (DNF).
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-34" ] } }, { "id": "148", "guid": "9bb5b6b9-80eb-44f6-9095-616b124e8979", "text": "The application shall allow users to enter a filtering condition matching document sections by their number or heading.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-34" ] } }, { "id": "149", "guid": "dee5e63d-59ad-4e1f-bca9-48e96f01c9fe", "text": "The application shall allow users to enter a filtering condition matching requirements by their text description or a custom attribute.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-34" ] } }, { "id": "150", "guid": "30648e00-a255-4036-a2cd-44e506629fb1", "text": "The application shall allow users to filter requirements with missing traceability links of a given type.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-34" ] } } ] }, { "id": "151", "guid": "d4464ee6-479b-4836-8c68-0441354a226d", "heading": "Full Text Search", "type": "SEC", "children": [ { "id": "152", "guid": "8e3921eb-c456-4fd8-a769-029ca3c0a7b5", "text": "The application shall allow users to search requirements matching one or more given keywords in an string or xhtml attribute.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-36" ] } }, { "id": "153", "guid": "7cf012d5-d5bc-47cb-b69b-65f62e1b739f", "text": "While the search mode is active the application shall highlight the matched requirements and allow user to select the next or previous matched requirement in the document.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-36" ] } } ] } ] }, { "id": "154", "guid": "f2d68c2e-ff33-4f8e-b5b3-cca7145806c4", "heading": "History of Changes", "type": "SEC", "children": [ { "id": "159", "guid": "28cad8df-b9a7-4601-9928-44f76f91c334", "text": "When a user changes a requirement the application shall record the current date and time and the author of the change.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-26" ] } }, { "id": "101", "guid": "b86eccf4-cd65-47d3-877a-c33ccea79288", "text": "The application shall display all changes of the selected requirement ordered by date and time.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-26" ] } }, { "id": "102", "guid": "5d0b9978-fdef-4ee8-856b-4fcbb6a170c7", "text": "Each displayed requirement change shall contain author, date & time and description of the change.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-26" ] } }, { "id": "103", "guid": "b243ba1b-e5cf-4246-a329-46a5b4fe2dbd", "text": "The application shall allow users to expand and collapse all changes in the History pane.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-26" ] } } ] }, { "id": "162", "guid": "0813038a-4b24-4823-a052-114d3a3d82b1", "heading": "Reporting", "type": "SEC", "children": [ { "id": "163", "guid": "73ba7588-a005-4a29-8d60-44a8437be41e", "text": "The application shall allow users to print the displayed requirements table.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-29", "NEEDS-23" ] } }, { "id": "164", "guid": "c80547d9-8852-47f8-830a-c0fca99f5f2f", "text": "The application shall allow users to create a PDF containing the displayed requirements table.
", "status": "Released", "type": "FR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-29", "NEEDS-23" ] } } ] } ] }, { "id": "23", "guid": "5647049c-8405-4e29-858f-fc29f4d7db07", "heading": "Usability requirements", "helpRef": "9.6.13", "type": "SEC" }, { "id": "24", "guid": "e0735be9-4a0d-4588-b568-3358fb2aac44", "heading": "Performance requirements", "helpRef": "9.6.14", "type": "SEC", "children": [ { "id": "174", "guid": "2e97d79e-0243-4a39-9238-50056381bf1c", "heading": "Startup Time", "text": "The application should display the opened document within 10s after it is started.
", "type": "NFR", "links": { "satisfaction": [ "NEEDS-39" ] } }, { "id": "171", "guid": "3ec2b06c-1ce1-4b40-bf68-2510f093e5b1", "heading": "Edit Response Time", "text": "The application should display updated values within 1s after user triggers the edit operation.
", "type": "NFR", "links": { "satisfaction": [ "NEEDS-41" ] } }, { "id": "173", "guid": "ffadcffa-e893-4048-860c-53f04fe28de2", "heading": "Smooth Scrolling", "text": "While a user scrolls the requirements table, the application should not display scrolling jerks longer than 200ms.
", "type": "NFR", "links": { "satisfaction": [ "NEEDS-44" ] } }, { "id": "170", "guid": "1aaac032-7b5a-4976-9234-c6b4ee74f1c0", "heading": "Document Size", "text": "The application shall allow users to open documents up to 10000 objects and 100 file attachments with total size up to 100MB.
", "type": "NFR", "links": { "satisfaction": [ "NEEDS-44" ] } } ] }, { "id": "25", "guid": "7c7140c6-2d81-44f2-9e8b-3ea1f48d54b3", "heading": "Logical database requirements", "helpRef": "9.6.15", "type": "SEC" }, { "id": "26", "guid": "d91d4a07-e4cb-416c-9486-f490148b3f7a", "heading": "Design constraints", "helpRef": "9.6.16", "type": "SEC" }, { "id": "27", "guid": "09b8bff5-7c20-4b38-bb17-51433ec9d06b", "heading": "Standards compliance", "helpRef": "9.6.17", "type": "SEC", "children": [ { "id": "204", "guid": "f56ffc5b-abc3-4741-b750-2e2166a790d3", "text": "The application shall comply with OWASP Application Security Verification Standard (ASVS) - Level 1, see document [DEMO-ASVS].
", "type": "NFR", "links": { "satisfaction": [ "ASVS-456" ] } } ] }, { "id": "28", "guid": "0a1c553a-de61-4add-bf58-befe0b7e3516", "heading": "Software system attributes", "helpRef": "9.6.18", "type": "SEC", "children": [ { "id": "212", "guid": "1a65d996-4e65-443c-aaba-d5bf4fa9042b", "heading": "Security", "type": "SEC", "children": [ { "id": "224", "guid": "8b75512d-4bd1-47eb-a3e2-68f4f1e8ce67", "heading": "Secure Input", "type": "SEC", "children": [ { "id": "205", "guid": "aa31e427-272e-4be0-af73-c43f15b91355", "text": "The application shall validate all inputs entered by users.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-232", "ASVS-233" ] } }, { "id": "206", "guid": "f46aef10-edc4-4d33-9f98-f453eaf29b15", "text": "The application shall sanitize all inputs entered by users in a rich text editor.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-236" ] } }, { "id": "199", "guid": "bf0a7684-3ea1-4f99-b057-a84f3edb8c81", "text": "The application shall sanitize all inputs imported by users.
", "type": "NFR", "links": { "satisfaction": [ "NEEDS-42", "ASVS-236" ] } }, { "id": "207", "guid": "e4003534-9720-4c6d-be6b-d5a679d874f6", "text": "The application shall prevent user to attach an executable file to project data.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-237" ] } }, { "id": "211", "guid": "574b93ae-5cef-4353-9713-8a169052320d", "text": "The application shall not display preview of insecure SVG image attachments.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-242" ] } }, { "id": "208", "guid": "4debb5f7-fef2-4f7e-9e44-99a6b7503a83", "text": "The application shall prevent user to attach a file larger than 10 MBs.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-237" ] } }, { "id": "209", "guid": "43d97384-3ef8-4218-b14f-b244107102d4", "text": "The application shall not execute any code provided by users, which is not sanitized or running in a sandbox.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-239", "ASVS-240" ] } }, { "id": "218", "guid": "f01d5209-c4d3-4940-b18d-0db09d0a18bf", "text": "The application shall be protected against JSON injection attacks, JSON eval attacks, and JavaScript expression evaluation.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-250", "ASVS-263" ] } } ] }, { "id": "225", "guid": "5ab824be-17d8-47d5-8dde-976ceb698c4c", "heading": "Secure Output", "type": "SEC", "children": [ { "id": "217", "guid": "28ac2d9b-9aa3-445e-be47-c05a5ee1c2ab", "text": "The application shall escape all HTML exports.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-245", "ASVS-246", "ASVS-247" ] } } ] }, { "id": "226", "guid": "4c6c5648-edfa-4554-bb51-54e2fc7ddd48", "heading": "Sensitive Data Handling", "type": "SEC", "children": [ { "id": "219", "guid": "fc5808cf-7a53-405c-b1ed-886b5566571d", "text": "The application shall not store sensitive data in application logs.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-287", "ASVS-288" ] } }, { "id": "220", "guid": "efc33d81-2088-4f8c-97af-ddc1e9f3cdb9", "text": "The application privacy policy shall clearly explain how personal and project data are processed.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-318", "ASVS-319" ] } } ] }, { "id": "223", "guid": "27e4700f-0510-4546-8163-be885b4d5360", "heading": "Secure Build", "type": "SEC", "children": [ { "id": "228", "guid": "24b3dcfc-c18c-4616-a14b-c67a406e7b4c", "text": "The application source and configuration files shall be managed under a version control system.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-407" ] } }, { "id": "222", "guid": "5ed8818a-6761-4a65-b397-4456f296af4a", "text": "The application shall be build in a secure image separated from the host environment.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-403", "ASVS-406" ] } }, { "id": "227", "guid": "93875563-fbc0-4056-9fa9-01e56fae028b", "text": "The application build shall be reproducible.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-406" ] } }, { "id": "229", "guid": "a3c69164-5b01-4a86-9e4e-98ad4e467a0c", "text": "The application 3rd party dependencies shall be updated before building binaries.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-409" ] } }, { "id": "230", "guid": "767c499a-58a7-423a-bda2-61dfcdba1a82", "text": "Unused application features, configurations, and 3rd party dependencies shall be removed before building binaries.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-410" ] } }, { "id": "221", "guid": "a61b88ab-8cba-4954-81ba-d8fee2c7fc5b", "text": "The application executable binaries shall be digitally signed.
", "type": "NFR", "links": { "satisfaction": [ "ASVS-347" ] } } ] } ] }, { "id": "215", "guid": "7c29e9ef-bbbb-47e5-89bd-c78ff10c4d12", "heading": "Portability", "type": "SEC", "children": [ { "id": "195", "guid": "4fedf9f7-567f-46be-b752-583c4575a862", "text": "The application shall run on Windows, Linux or Mac operating systems.
", "status": "Released", "type": "NFR", "verMethod": "T", "links": { "satisfaction": [ "NEEDS-51" ] } } ] } ] } ] }, { "id": "29", "guid": "1a22c42b-07bf-4a97-8492-6177bc2f7dc4", "heading": "Verification", "helpRef": "9.6.19", "type": "SEC", "children": [ { "id": "198", "guid": "f720f8e1-1d6f-45a9-84d2-c12bbaee0c1e", "text": "Verification tests are specified in [DEMO-TESTS] document.
", "type": "INF" } ] }, { "id": "30", "guid": "b1945def-c739-4466-8564-51a3e644a6c0", "heading": "Supporting information", "helpRef": "9.6.20", "type": "SEC" }, { "id": "31", "guid": "7a48c760-5a6b-4236-95f8-6f03d0942b67", "heading": "References", "helpRef": "9.2.4", "type": "SEC", "children": [ { "id": "177", "guid": "19719e5d-810a-431f-bc95-29c159a1fd76", "text": "[DEMO-NEEDS]: ReqView User Needs
", "type": "INF" }, { "id": "216", "guid": "8b459b5b-b960-4915-934d-1d8735c5fc08", "text": "[DEMO-ASVS]: OWASP Application Security Verification Standard
" }, { "id": "197", "guid": "c5b27ce0-08cf-420c-9247-df3d0fb497aa", "text": "[DEMO-TESTS]: ReqView Verification Tests
", "type": "INF" } ] } ], "attributes": { "compliance": { "name": "Compliance", "type": "enum", "values": [ { "key": "Compliant" }, { "key": "Partial" }, { "key": "Non-compliant" } ] }, "difficulty": { "name": "Difficulty", "type": "enum", "values": [ { "key": "E", "label": "Easy" }, { "key": "N", "label": "Nominal" }, { "key": "D", "label": "Difficult" } ] }, "owner": { "name": "Owner", "type": "string" }, "priority": { "name": "Priority", "type": "enum", "values": [ { "key": "L", "label": "Low" }, { "key": "M", "label": "Medium" }, { "key": "H", "label": "High" } ] }, "rationale": { "name": "Rationale", "type": "xhtml" }, "source": { "name": "Source", "type": "string" }, "status": { "name": "Status", "type": "enum", "values": [ { "key": "Draft" }, { "key": "Ready" }, { "key": "Reviewed" }, { "key": "Approved" }, { "key": "Released" } ] }, "type": { "name": "Type", "type": "enum", "values": [ { "key": "FR", "label": "Functional Requirement" }, { "key": "INT", "label": "Interface Requirement" }, { "key": "NFR", "label": "Non-func. Requirement" }, { "key": "SEC", "label": "Section" }, { "key": "INF", "label": "Information" } ] }, "verMethod": { "name": "Ver. Method", "type": "enum", "values": [ { "key": "T", "label": "Test" }, { "key": "D", "label": "Demonstration" }, { "key": "I", "label": "Inspection" }, { "key": "A", "label": "Analysis" } ] } }, "templateColumns": { "20066760-0dbf-4c90-97a7-531f0d447d89": { "label": "Is Verified By", "template": "{{#eachInlinkWith type=\"verification\"}}\n◂ {{#hyperlink}}{{docObjId}}{{/hyperlink}}: {{shortDescription maxLength=80}}
\n{{/eachInlinkWith}}" }, "2236e0bc-8fae-4450-b448-2fdb822d2747": { "label": "Satisfies", "template": "{{#eachOutlinkWith type=\"satisfaction\"}}\n▸ {{#hyperlink}}{{docObjId}}{{/hyperlink}}: {{shortDescription maxLength=80}}
\n{{/eachOutlinkWith}}\n" }, "45e65d74-d2a6-4782-9e74-38d950773df3": { "label": "Implemented By", "template": "{{#eachInlinkWith type=\"implementation\"}}\n◂ {{#hyperlink}}{{docObjId}}{{/hyperlink}}: {{shortDescription maxLength=80}}
\n{{/eachInlinkWith}}" } }, "views": { "Capture": { "columns": [ { "columnId": "id", "width": 107 }, { "columnId": "type", "width": 125 }, { "columnId": "description", "width": 633 }, { "columnId": "rationale", "width": 189 }, { "columnId": "source", "width": 189 } ] }, "Export": { "columns": [ { "columnId": "id", "width": 88 }, { "columnId": "description", "width": 1106 } ] }, "Primary": { "columns": [ { "columnId": "id", "width": 86 }, { "columnId": "type", "width": 104 }, { "columnId": "description", "width": 565 }, { "columnId": "rationale", "width": 162 }, { "columnId": "status", "width": 93 } ], "default": true }, "Review": { "columns": [ { "columnId": "id", "width": 96 }, { "columnId": "description", "width": 583 }, { "columnId": "rationale", "width": 251 }, { "columnId": "discussion", "width": 315 } ] }, "Traceability": { "columns": [ { "columnId": "id", "width": 80 }, { "columnId": "type", "width": 100 }, { "templateColumnId": "2236e0bc-8fae-4450-b448-2fdb822d2747", "width": 213 }, { "columnId": "description", "width": 444 }, { "templateColumnId": "20066760-0dbf-4c90-97a7-531f0d447d89", "width": 205 }, { "templateColumnId": "45e65d74-d2a6-4782-9e74-38d950773df3" } ] } } }, { "id": "TESTS", "guid": "c29aae4e-f6f1-491c-a638-50000a2d2b58", "name": "ReqView Verification Tests", "lastId": 30, "createdOn": "2016-01-14T03:04:15.797Z", "createdBy": { "name": "Libor Bus", "email": "libor.bus@eccam.com", "company": "Eccam s.r.o." }, "lastChangedOn": "2023-10-09T15:05:30.700Z", "lastChangedBy": { "name": "Libor Bus", "email": "libor.bus@eccam.com", "company": "Eccam" }, "data": [ { "id": "25", "guid": "b0224dda-b913-4cea-97a0-922103ba8927", "text": "© Copyright by Eccam s.r.o. All rights reserved.
", "type": "INF" }, { "id": "1", "guid": "26f82d1d-0700-42f0-a50e-eb7857e5e4d8", "heading": "Introduction", "type": "SEC", "children": [ { "id": "23", "guid": "180b45cf-4834-4b0c-861b-cbd70eddb753", "text": "This document describes test cases for ReqView application version 1.0, which implements functionality specified in [DEMO-SRS] document.
Note: This is an example document, which is not complete.
", "type": "INF" } ] }, { "id": "2", "guid": "845a4ec8-108d-4933-b0fa-32d2f6c9759f", "heading": "Test Cases", "type": "SEC", "children": [ { "id": "3", "guid": "4fe93d6b-9f34-4397-8892-9518042b0200", "heading": "File Operations", "type": "SEC", "children": [ { "id": "4", "guid": "c4d73203-9d44-47b2-a5a8-46b9b3a2abad", "heading": "Open Local File", "status": "Passed", "type": "SUITE", "links": { "verification": [ "SRS-56" ] }, "children": [ { "id": "9", "guid": "fe004173-e687-4bb3-9393-6195d89c3c92", "heading": "File Open Success", "status": "Passed", "type": "CASE", "children": [ { "id": "19", "guid": "be15d570-9cde-4057-9441-bfae1325f8d3", "text": "Edit the first object by deleting its description.
", "precondition": "Clean demo document is opened.
", "type": "STEP" }, { "id": "11", "guid": "b1882969-a905-49e9-9da3-5eae0eb9334e", "text": "Select File / Open (CTRL+O) from menu.
", "expected": "Dialog \"Save changes?\" is shown.
", "type": "STEP" }, { "id": "20", "guid": "a058adba-1970-4862-ac49-7317d9e98ea6", "text": "Choose \"Do not save\" in \"Save changes?\" dialog.
", "expected": "System file selection Open dialog is shown.
", "type": "STEP" }, { "id": "12", "guid": "87a6fa0b-2a51-4fc0-b8b4-fc21b9a0decb", "text": "In the Open dialog choose a ReqView project file (*.reqw) and click Open button.
", "data": "data/reqview_demo.reqw
", "expected": "The project from the file is successfully opened.
The current document is the last active document from the project.
", "type": "STEP" } ] }, { "id": "10", "guid": "fbde7b1d-e615-4a62-bc85-d0647dccfbbe", "heading": "File Open Failure", "status": "Passed", "type": "CASE", "children": [ { "id": "15", "guid": "483a593a-192d-48ff-9372-115fa8f69194", "text": "Select File / Open (CTRL+O) from menu.
", "expected": "Open dialog is shown.
", "type": "STEP" }, { "id": "16", "guid": "6ea04965-6037-4266-989f-89d2f55612f4", "text": "In the Open dialog choose a file which is not a valid ReqView project file and click Open button.
", "data": "data/reqview_export.csv
", "expected": "Error message \"Error during opening file!\" is displayed.
", "type": "STEP" } ] } ] }, { "id": "5", "guid": "c32dd641-1398-4152-922f-43d615229291", "heading": "Save Local File", "status": "Draft", "type": "SUITE", "links": { "verification": [ "SRS-59" ] } } ] }, { "id": "6", "guid": "79d6d576-1d2e-42d2-893e-dcc7b23d6e0c", "heading": "Edit Requirements", "type": "SEC", "children": [ { "id": "21", "guid": "61fe5e2f-1878-4f39-b7c6-aded1425ac62", "heading": "Create Requirements", "status": "Draft", "type": "SUITE", "links": { "verification": [ "SRS-53", "SRS-106", "SRS-107", "SRS-114", "SRS-115", "SRS-116" ] } }, { "id": "22", "guid": "a116d8de-b85b-4099-9575-8d24645b421a", "heading": "Restructure Requirement", "status": "Draft", "type": "SUITE", "links": { "verification": [ "SRS-108", "SRS-109", "SRS-110", "SRS-111", "SRS-112" ] } }, { "id": "29", "guid": "616a50a3-2bc9-4dcf-8f9d-a981217a38a1", "heading": "Custom Attributes", "status": "Draft", "type": "SUITE", "links": { "verification": [ "SRS-119", "SRS-120", "SRS-121", "SRS-122", "SRS-157", "SRS-165", "SRS-191", "SRS-192", "SRS-193" ] } }, { "id": "30", "guid": "13df16d7-cf5a-469d-a290-bc561a79bd66", "heading": "Discussion", "status": "Draft", "type": "SUITE", "links": { "verification": [ "SRS-132", "SRS-133", "SRS-96", "SRS-97", "SRS-98", "SRS-90" ] } } ] }, { "id": "14", "guid": "60eaaa06-6fd9-4ea4-81c5-59f772d44491", "heading": "..." } ] }, { "id": "26", "guid": "69f8216f-8a25-4858-b4af-3305c6cb5fc5", "heading": "References", "children": [ { "id": "28", "guid": "e74d9117-3ab5-46fa-a854-50cb058f7046", "text": "[DEMO-SRS]: ReqView Software Requirements Specification
" } ] } ], "attributes": { "data": { "name": "Test Data", "type": "xhtml" }, "expected": { "name": "Expected Result", "type": "xhtml" }, "postcondition": { "name": "Postcondition", "type": "xhtml" }, "precondition": { "name": "Precondition", "type": "xhtml" }, "status": { "name": "Status", "type": "enum", "values": [ { "key": "Draft" }, { "key": "Approved" }, { "key": "Passed" }, { "key": "Failed" } ] }, "type": { "name": "Type", "type": "enum", "values": [ { "key": "SUITE", "label": "Test Suite" }, { "key": "CASE", "label": "Test Case" }, { "key": "STEP", "label": "Test Step" }, { "key": "SEC", "label": "Section" }, { "key": "INF", "label": "Information" } ] } }, "templateColumns": { "96c43f1b-cfc6-4e8f-b05f-2ed932a5c620": { "label": "Verifies", "template": "{{#eachOutlinkWith type=\"verification\"}}\n▸ {{#hyperlink}}{{docObjId}}{{/hyperlink}}: {{shortDescription maxLength=80}}
\n{{/eachOutlinkWith}}\n" } }, "views": { "Primary": { "columns": [ { "columnId": "id", "width": 90 }, { "columnId": "type", "width": 104 }, { "columnId": "description", "width": 342 }, { "columnId": "status", "width": 90 }, { "columnId": "precondition", "width": 156 }, { "columnId": "data", "width": 176 }, { "columnId": "expected", "width": 261 }, { "columnId": "postcondition", "width": 225 } ], "default": true }, "Traceability": { "columns": [ { "columnId": "id", "width": 124 }, { "columnId": "type", "width": 118 }, { "columnId": "description", "width": 417 }, { "templateColumnId": "96c43f1b-cfc6-4e8f-b05f-2ed932a5c620", "width": 266 }, { "columnId": "status", "width": 100 } ] } } }, { "id": "ARCH", "guid": "c907e0e8-1982-429c-879b-d0d03d96b553", "name": "ReqView Architecture", "lastId": 18, "createdOn": "2019-09-10T14:01:32.469Z", "createdBy": { "name": "Libor Bus", "email": "libor.bus@eccam.com", "company": "Eccam" }, "lastChangedOn": "2024-03-06T13:58:46.219Z", "lastChangedBy": { "name": "Libor Bus", "email": "libor.bus@eccam.com", "company": "Eccam" }, "data": [ { "id": "3", "guid": "d7543a42-f1cd-4386-9feb-ef2bef0063da", "text": "© Copyright by Eccam s.r.o. All rights reserved.
", "type": "INF" }, { "id": "1", "guid": "cf876f6b-1239-45b1-9431-4e30408f6721", "heading": "Introduction", "type": "SEC", "children": [ { "id": "4", "guid": "3ca3e96f-ff0e-41ca-9ad6-24e8ead0f457", "text": "This document describes architecture of ReqView application version 1.0, which implements functionality specified in [DEMO-SRS] document.
Note: This is an example document, which is not complete.
", "type": "INF" } ] }, { "id": "2", "guid": "e3603963-b957-479e-9105-55156e43863c", "heading": "Architecture", "type": "SEC", "children": [ { "id": "18", "guid": "4a73a18f-bfa4-4523-b763-513742303d35", "heading": "Application", "type": "SYS", "links": { "implementation": [ "SRS-174", "SRS-195" ] }, "children": [ { "id": "7", "guid": "1f13f99f-645a-4551-9724-02e27c4b940d", "type": "INF", "attachments": [ "ARCH-7_1_reqview_architecture.png" ] }, { "id": "8", "guid": "218cb8fe-e4ea-4981-86a7-01fc95775ab6", "heading": "Widgets", "text": "Widgets displayed in the UI triggering events based on an user input
", "type": "MOD", "links": { "implementation": [ "SRS-80", "SRS-83", "SRS-84", "SRS-85", "SRS-86", "SRS-87", "SRS-88", "SRS-89", "SRS-190", "SRS-90", "SRS-81", "SRS-92", "SRS-93", "SRS-94", "SRS-96", "SRS-97", "SRS-98", "SRS-99", "SRS-142", "SRS-114", "SRS-115", "SRS-116", "SRS-165", "SRS-147", "SRS-148", "SRS-149", "SRS-150", "SRS-152", "SRS-153", "SRS-101", "SRS-102", "SRS-103", "SRS-173", "SRS-171", "SRS-199" ], "usage": [ "ARCH-9" ] } }, { "id": "9", "guid": "fe6526b5-22b5-4792-a059-839751503d2d", "heading": "Actions", "text": "UI actions called from UI widgets based on UI events
", "type": "MOD", "links": { "implementation": [ "SRS-53", "SRS-54", "SRS-56", "SRS-59", "SRS-61", "SRS-63", "SRS-72", "SRS-73", "SRS-76", "SRS-77", "SRS-106", "SRS-108", "SRS-109", "SRS-110", "SRS-111", "SRS-112", "SRS-160", "SRS-137", "SRS-139", "SRS-140", "SRS-141", "SRS-135", "SRS-138", "SRS-156", "SRS-161", "SRS-132", "SRS-124", "SRS-127", "SRS-128", "SRS-129", "SRS-119", "SRS-122", "SRS-192", "SRS-163", "SRS-164" ], "usage": [ "ARCH-10", "ARCH-12", "ARCH-13", "ARCH-14", "ARCH-16" ] } }, { "id": "10", "guid": "86c3da79-58a6-4278-acbe-3a57b94f40f2", "heading": "Dialogs", "text": "UI dialogs opened from UI actions
", "type": "MOD", "links": { "implementation": [ "SRS-199" ] } }, { "id": "11", "guid": "9a54b3e8-8993-41df-93f1-28ddcd18b765", "heading": "Commands", "text": "Commands called from the CLI
", "type": "MOD", "links": { "usage": [ "ARCH-12", "ARCH-14" ] } }, { "id": "14", "guid": "173807e0-890f-4ab4-ad8d-59e366718ee4", "heading": "Export", "text": "Exporters of project data to supported external file formats
", "type": "MOD", "links": { "implementation": [ "SRS-76", "SRS-77" ], "usage": [ "ARCH-17" ] } }, { "id": "13", "guid": "ab642e2f-63e9-4f7a-90f6-5c7d2d236191", "heading": "Import", "text": "Importers of project data from supported external file formats
", "type": "MOD", "links": { "implementation": [ "SRS-72", "SRS-73", "SRS-199" ], "usage": [ "ARCH-17" ] } }, { "id": "16", "guid": "bfba17c7-4bc0-4ffb-bdda-b962d0f216f1", "heading": "File", "text": "ReqView Project File / Folder readers and writers
", "type": "MOD", "links": { "implementation": [ "SRS-59", "SRS-56", "SRS-62", "SRS-199" ] } }, { "id": "17", "guid": "c0c4d1f3-c55d-43e1-b671-e4c96d61529f", "heading": "Tools", "text": "Various tools for data conversion and formatting
", "type": "MOD" }, { "id": "12", "guid": "e253a749-94e7-40e6-a296-aa9e37e333e4", "heading": "Models", "text": "Data models storing project data and user preferences
", "type": "MOD", "links": { "implementation": [ "SRS-106", "SRS-108", "SRS-109", "SRS-110", "SRS-111", "SRS-112", "SRS-107", "SRS-114", "SRS-115", "SRS-144", "SRS-137", "SRS-139", "SRS-140", "SRS-141", "SRS-135", "SRS-138", "SRS-156", "SRS-161", "SRS-132", "SRS-133", "SRS-126", "SRS-124", "SRS-127", "SRS-128", "SRS-129", "SRS-119", "SRS-120", "SRS-121", "SRS-122", "SRS-157", "SRS-165", "SRS-191", "SRS-192", "SRS-193", "SRS-159", "SRS-170", "SRS-173", "SRS-171" ], "usage": [ "ARCH-15" ] } }, { "id": "15", "guid": "c00f77e7-75ae-4639-861a-03bd3b77061a", "heading": "Persistency", "text": "Application persistency readers and writers
", "type": "MOD", "links": { "implementation": [ "SRS-144", "SRS-160", "SRS-170" ] } } ] } ] }, { "id": "5", "guid": "d3d020d6-fe73-467e-bf59-2a37e6dce53a", "heading": "References", "type": "SEC", "children": [ { "id": "6", "guid": "32c8bf14-139c-4527-bb47-27edaff2eb92", "text": "[DEMO-SRS]: ReqView Software Requirements Specification
", "type": "INF" } ] } ], "attributes": { "type": { "name": "Type", "type": "enum", "values": [ { "key": "SYS", "label": "System" }, { "key": "MOD", "label": "SW Module" }, { "key": "SEC", "label": "Section" }, { "key": "INF", "label": "Information" } ] } }, "templateColumns": { "41b42ac7-a273-48a1-906a-c52e65df763d": { "label": "Implements", "template": "\n{{#if (hasOutlinks \"implementation\")}}\n