START HERE

What you will learn

  • Understand how a verification standard differs from a risk-awareness list.
  • Select and document requirements within a clear application scope.
  • Describe security evidence without overstating what was assessed.

Before you start: Read the guide to security principles and frameworks first if the distinction between a risk and a requirement is new to you.

Reference edition: OWASP ASVS 5.0.0. Sources checked 2026-11-11.

A requirement needs an observable result

“We take access control seriously” is an intention. “This read-only identity is denied a write operation on every relevant route” is an expectation that can be investigated. ASVS helps provide a more systematic basis for requirements and verification than a list of broad risk categories alone.

Use the published standard for the actual requirement wording and identifiers. This guide explains a way to work with requirements; the example checks below are teaching examples, not invented ASVS requirement numbers or a substitute for the standard.

Define what the review actually includes

Record the application version, components, interfaces, user roles and selected verification depth. Decide how exclusions and requirements that do not apply will be justified. A scoped review should make its limits visible rather than quietly treating untested areas as passing.

Evidence may include a repeatable test result, a configuration review or inspected implementation behaviour. The appropriate form depends on the requirement. A written policy can support a process decision but may not establish that the running application enforces the intended technical rule.

Include the routes used by software as well as browser screens. An application programming interface (API) lets software request operations; its permission checks matter even when a person normally uses the browser interface.

Step-by-step process

  1. Choose the edition and assessment scope

    State ASVS 5.0.0 and the application or service version being reviewed. Identify relevant interfaces, identities and integrations.

  2. Select applicable requirements from the standard

    Use the official text and identifiers. Involve someone with the security knowledge needed to judge coverage; do not assume the examples in an article are exhaustive.

  3. Translate each selected requirement into a check

    Write the test conditions, expected result and evidence location. Use authorised test accounts and synthetic information where possible.

  4. Record pass, fail, not tested or justified non-applicability

    Keep these outcomes distinct. A missing test is not a passing result, and an exclusion needs a reason and accountable owner.

  5. Repair and retest

    Associate a defect with the failed requirement and application revision. Repeat the relevant checks after a correction and preserve unresolved limitations in the final report.

FOLLOW ONE EXAMPLE

Worked scenario

Reviewing an API used by a personal knowledge application

A fictional stakeholder is preparing a limited pilot. The application lets a person search documents and update saved notes. The review includes its API, not only its browser screens.

  1. The reviewer records the edition, pilot roles, API routes and document storage in scope. Relevant requirements are selected from the standard.
  2. For a write operation, a check specifies a read-only test identity, a synthetic note and the expected rejection. A separate permitted identity must still be able to complete its intended operation.
  3. A failed check becomes a tracked defect. After repair, the review repeats the checks against the corrected revision and records what was not assessed.

What this shows: The stakeholder receives traceable evidence for defined requirements and visible gaps. They do not receive a blanket assurance about every possible weakness.

The process at a glance

Keep the selected requirement, actual check and resulting evidence connected. Untested work must remain visible in the result.
ProcessDecisionHuman checkpoint
Read Mermaid diagram source
flowchart LR
 A[Choose edition and scope] --> B[Select applicable requirements]
 B --> C[Define observable checks]
 C --> D[Collect evidence]
 D --> E[Record results and gaps]
 E --> F[Repair and retest]

What you should have at the end

  • A requirements-to-evidence record with a named reference edition.
  • Clear distinctions between failures, untested work and justified exclusions.
  • A review report whose claims match its actual coverage.

Common mistakes and how to avoid them

Inventing identifiers from a summary article

Use identifiers and exact requirement wording from the selected official edition.

Calling an untested requirement “not applicable”

Explain why a requirement does not apply; absence of evidence is different.

Keeping the same result after changing the system

Revisit affected requirements when interfaces, identities or dependencies change.

APPLY THE IDEA

Try it yourself

Your task: Write one testable expectation for an operation in a system you own. Then locate an applicable area in the official ASVS edition.

What to produce: A draft verification record with scope, official reference, conditions, expected result, evidence and limitations.

Check your understanding: Could another reviewer repeat the check and distinguish a failure from work that was never tested?

Key terms in plain English

Verification requirement
A defined security expectation used as a basis for checking.
Scope
The components, versions and behaviour included in the review.
Evidence
Recorded information supporting a particular assessment result.
Non-applicability
A justified determination that a requirement does not fit the assessed scope.

Sources and further reading