Security Testing Portfolio
SAST, DAST, dependency and secret scanning, fuzzing, penetration tests and review each see a different slice; no scanner understands every authorization rule.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
One tool is treated as coverage, findings lack ownership, or tests stop at syntax and miss business authorization.
The important question is not “what is Security Testing Portfolio?” but “which assumption let untrusted data or an over-scoped identity cross designed control → evidence it works under hostile input?” Trace the decision at the boundary, then constrain what can happen after the first control fails.
Design the control in layers
Start with the control closest to the interpretation or privilege boundary: Combine complementary methods based on threat model Then add a control that reduces blast radius and telemetry that proves the decision was enforced.
The resulting design is not labelled secure. Record the identified controls, the known failure paths, the remaining exposure, and the evidence you would need during an incident.
| Prevent | Detect | Recover |
|---|---|---|
| Combine complementary methods based on threat model · Put invariant tests in CI · Verify findings and fixes manually where context matters | Coverage by asset/boundary and regression escape rate | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: Security invariants across code, dependencies, configuration and running behavior.
- Boundary: Designed control → evidence it works under hostile input
- Primary control: Combine complementary methods based on threat model
- Detection signal: Coverage by asset/boundary and regression escape rate
- Always ask what limits damage when the primary control fails.
Boundary control exercise
This lesson uses the shared boundary-control exercise.
Follow the attack
Safe conceptual simulation: capability → missing control → crossed boundary → asset impact.
- 1Attacker starts with: The defects and regressions that reach production unnoticed.
- 2One tool is treated as coverage, findings lack ownership, or tests stop at syntax and miss business authorization.
- 3The weak or missing boundary control is crossed: Designed control → evidence it works under hostile input
- 4Impact: Known classes of failure recur or remain invisible until production.
- Known classes of failure recur or remain invisible until production.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Combine complementary methods based on threat model
- • Put invariant tests in CI
- • Verify findings and fixes manually where context matters
- • Coverage by asset/boundary and regression escape rate
- • Contain the affected identity or component.
- • Scope access from audit evidence.
- • Fix the boundary and add a regression test.
- • Misconfiguration and new access paths can bypass the intended control.
- • A privileged insider or compromised control plane may still reach the asset.