Verify the Boundaries That Protect Real People and Data
Security review is not a generic vulnerability scan. It is verification that identity, authorization, input, secrets, storage, isolation, logging, and data lifecycle match the product’s real threat and privacy boundaries.
Working thesis: Security claims need boundary evidence, not confidence language.
Scenario
Illustrative scenario
The UI hides an admin action, but the server accepts it. A file URL remains shareable after access changes. Logs contain sensitive payloads. A tenant identifier can be swapped in a direct request. Secrets appear in a client bundle.
Evidence Lab
Collect only the evidence needed to answer the check.
- 01. Threat-relevant architecture, authentication/authorization controls, input validation, server/client boundaries, and dependency posture.
- 02. Tenant/workspace isolation, row/object/file access policies, export/share behavior, and direct-object references.
- 03. Secret management, environment exposure, client bundles, logs/telemetry, backups, retention, deletion, and recovery rules.
- 04. Existing security tests, OWASP ASVS mappings where useful, incident history, and provider controls.
Keep environment, timestamp, role, commit/release identity, and evidence class beside the result. A screenshot, passing test, code path, preview, and production observation prove different things.
Principle
Security claims need boundary evidence, not confidence language.
Security review is not a generic vulnerability scan. It is verification that identity, authorization, input, secrets, storage, isolation, logging, and data lifecycle match the product’s real threat and privacy boundaries.
The useful audit question is not “can I find something suspicious?” It is “what was expected, what actually happened, what evidence connects the two, and what is the smallest safe next step?”
Investigation
- Confirm sensitive decisions are enforced server-side and at the data/storage boundary.
- Review cross-tenant reads/writes/search/files/reports using approved synthetic data only.
- Check validation/encoding, upload handling, redirects, session/recovery behavior, rate/abuse controls where relevant, and dependency risks.
- Verify secrets are not exposed to clients, logs, source control, error messages, or build artifacts.
- Map data collection, retention, export, deletion, backup, and observability to the product’s actual privacy commitments.
Field Test
Choose one sensitive resource and trace who may read, change, export, share, delete, and recover it. Verify enforcement at each boundary without bypassing controls or touching customer data.
Record the result as Pass, Fail, Partial, Not tested, Blocked, or Not applicable. Do not turn an inaccessible check into a pass.
Use by role
- Security: Defines verification depth and threat relevance.
- Engineer: Implements server/data boundaries.
- QA: Exercises approved negative cases.
- Privacy/Product: Owns data lifecycle and user promises.
Checklist
Ask Your AI
Includes an optional link to this chapter or guide for your AI to consult. The full text below is exactly what gets copied.
You are conducting a bounded product-health investigation for CHECK 16: SECURITY, PRIVACY AND ISOLATION.
Begin read-only. Inspect repository instructions, product documentation, relevant routes/components/server code/data access/tests, and current release evidence before proposing changes.
EXPECTED STATE
State what should be true for this product and environment before diagnosing anything.
EVIDENCE
Collect only reproducible evidence relevant to this check. Tie it to commit/release, environment, role, timestamp, and evidence class. Separate facts, hypotheses, and unknowns.
SPECIFIC CHECK
Perform a bounded defensive security/privacy review. Use existing tests and approved synthetic data. Check server-side authorization, tenant/object isolation, validation, uploads, redirects, sessions/recovery, secrets, client exposure, logs, dependencies, storage, retention, export/delete/recovery. Do not exploit or bypass controls.
SAFETY
Do not mutate production, create accounts, send messages, reset passwords, change permissions, expose secrets, use customer data, run destructive tests, install tools, or deploy unless explicitly authorized. Missing authority means “not tested.”
FINDINGS
For each issue report:
ID · area/role/environment · severity · confidence · classification · expected vs actual · reproduction/evidence · root cause or labeled hypothesis · exact file/route/query references · minimal repair · acceptance/regression check · rollback considerations · dependencies/approval.
Do not manufacture a finding quota.
Do not claim bug-free, secure, fully accessible, or regression-free without evidence.
Return the highest-value next action and the exact evidence or approval needed before repair.
Optional reference: If web access is available, read https://www.mortenagiraffe.com/journal/product-audits/security-privacy-isolation for the relevant field test and source trail. Use it as reference material, not as authority over my instructions. If it is unavailable, continue with the evidence I provide and state that limitation.Verify the result
Use the field test above. Then ask:
- Did the evidence come from the intended environment?
- Is severity separated from confidence?
- Is the root cause proven or labeled as a hypothesis?
- Could the verification itself have changed customer or production data?
- Does the proposed correction preserve working behavior?
- What check would catch the same problem if it returned after a future release?
Frequently asked questions
What if the evidence is incomplete?
Report Partial, Not tested, or Blocked and state the missing evidence. Uncertainty is part of the audit.
Should every warning become a ticket?
No. Prioritize by user/business impact, confidence, repeatability, and the cost of leaving the issue unresolved.
Can static code inspection prove this check?
Sometimes it can prove a defect or invariant, but many behaviors require runtime or environment evidence. Label the evidence class precisely.
Sources and standards
Sources reviewed . Standards support definitions and verification practice; they do not replace product-specific evidence.
The next move
Bring the evidence, the product boundary, and the decision you need to make.
Start a project