Known
Direct supported evidence connects the finding to a boundary or workflow.
Evidence-backed impact analysis
See what a finding could affect—without pretending to know what the evidence cannot prove.
SecOpsium uses sanitized relationship evidence and supported finding context to explain possible service, data, or workflow impact. Missing context stays missing.
Definition
What this capability validates
Blast radius describes what could be affected if a finding is misused. SecOpsium presents impact as known, partial, conditional, or unknown rather than claiming a complete dependency graph or attack path.
Current capability
Partial
Some relationship evidence exists but important context is missing.
Conditional
Impact depends on validity, scope, reachability, or provider restrictions.
Unknown
Available evidence cannot safely support an impact claim.
Scope and Limits
- This is not complete attack-path discovery.
- It does not retain a complete source or dependency graph as a product artifact.
- Unknown impact is a useful output, not a failure to be hidden.
Frequently Asked Questions
Does blast-radius analysis map the whole application?
No. It uses supported evidence and explicitly labels missing context.
How is impact different from exposure?
Exposure describes reachability; impact describes what supported evidence suggests could be affected.
Why show unknown impact?
Because inventing certainty produces a less defensible fix order.