CYBERJA · PRACTICE GUIDE

Secure Application & API Review Hub

Use synthetic evidence. Enter your own observations, then compare them with the worked direction below.

Open the tool · Open this file in a browser or print it to PDF.

Practice scenario

A test account can request another tenant’s record.

Record the assessment

Open Connected Workspaces and select Application & API security. Use the assessment form to work through these prompts.

Application, API and trust boundaries — Describe users, entry points, APIs, sensitive data flows, external services and the boundaries where trust changes.

Threat scenarios and abuse cases — Identify plausible unauthorised access, tampering, injection, data exposure and service disruption for the selected design.

Authentication and authorisation requirements — Document session controls, object/function-level access checks, role boundaries and negative tests.

Input handling, secrets and dependencies — Review validation, output handling, secure secret storage and dependency updates. Record software/component evidence.

Specific security requirements — Map each selected threat to a measurable requirement and an ASVS reference where appropriate. Explain applicability.

Verification method and observed results — Record authorised test steps, expected results, actual evidence and unresolved issues. Planned tests must remain labelled as planned.

Release recommendation — Use a scoped recommendation; this tool does not approve a deployment or certify an application.

Residual risks and review conditions — Identify untested functions, accepted exceptions, approval authority and required follow-up.

Worked direction

Use two sandbox identities to reproduce the authorization gap. Record expected denial and the retest after a server-side fix.

Review your work

Map the design and trust boundaries.

Identify threats and measurable requirements.

Review or perform authorised verification.

Record a scoped release recommendation and exceptions.

Evidence and handoff

Capture a mock evidence reference and its limitations. Record the finding, accountable owner and next review. Where a material risk remains, record it in the shared risk register and schedule a follow-up.

Reference: OWASP ASVS and NIST Secure Software Development Framework — https://owasp.org/www-project-application-security-verification-standard/

Continue with the community

Compare your practice approach with other CyberJA Connect members.

Join CyberJA Connect ↗