NIST CSF 2.0
Create a common view of cybersecurity risk and turn gaps into an action plan.
Application Security Verification Standard
Give developers, testers and buyers a shared checklist for application security.
Application teams and buyers defining measurable technical security requirements for web applications and services.
A versioned requirements-to-test matrix with evidence and owned remediation.
Choose the target level and version explicitly. Tie each requirement to tests that cover your application rather than relying only on automated scanner output.
Monitor progress against the target, failed control tests and gaps that leave a critical service exposed.
Fill this in with your sponsor and send it to the people who own the work.
OWASP ASVS kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Set target level, version and boundary · Application security + product owners [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Select one service and test a high-impact control with its owner. Record what actually happened, what failed and the proposed target. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
A billing portal moves invoice downloads behind a new API. Testers attempt to fetch an invoice using another account’s identifier, record the negative test and open a defect when the service checks login but misses object ownership.
Check product-level legal duties where the application forms part of a covered product.
Preserve relevant development and remediation evidence for assurance work.
Checklist, instructions and 8 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Set target level, version and boundary | Application security + product owners | At design and major change | Set a start date | Scope memo; System inventory | Open |
| Write tests against selected requirements | Developers + security testers | Before the target release | Set a start date | Control matrix; Testing matrix | Open |
| Record observations and verify fixes | Security tester + engineering | During release testing | Set a start date | Test workpapers; Remediation tracker | Open |
| Keep requirements in the delivery process | Engineering lead + product security | On every relevant release | Set a start date | Change log; Evidence plan | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Record entry points, sensitive workflows, tech stack and target assurance level. Pin published requirement identifiers for the version in use.
Fictional details. Use the same fields with evidence from your work.
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.
Fictional details. Use the same fields with evidence from your work.
Each item has one accountable owner. The source and as-of date let a reviewer trace it back.
Share the reviewed inventory with the people building the control, privacy or testing scope.
Map each applicable requirement to design evidence, manual tests or automated checks. Document exclusions and include abuse cases and role boundaries.
Fictional details. Use the same fields with evidence from your work.
A different person can operate the control or test it using the matrix and its evidence links.
Give the baseline to control owners and the assessor before walkthroughs or sampling.
Fictional details. Use the same fields with evidence from your work.
Every essential claim and risk control has evidence or a documented justification for the gap.
Give the approved protocol to the testing team and the traceability matrix to the submission owner.
Keep sanitized inputs, environment and expected and actual results. Prioritize exploitable findings, fix them and run the same test again.
Fictional details. Use the same fields with evidence from your work.
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
Fictional details. Use the same fields with evidence from your work.
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.
Add secure acceptance checks and ownership to the development workflow. Update tests and the baseline when the ASVS edition or system architecture changes.
Fictional details. Use the same fields with evidence from your work.
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Use the log at case reviews and provide a restricted copy only where the engagement requires it.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.