Severity
Preserve the technical seriousness of the supported finding.
SecOpsium combines supported technical signals without pretending that one severity label answers every business decision.
Definition
Severity describes technical seriousness. Exposure describes reachability. Impact describes supported consequences. Priority is the resulting practical order and can change when your team adds stronger context.
Preserve the technical seriousness of the supported finding.
Show whether evidence appears public, restricted, internal, or uncertain.
Describe supported affected boundaries and keep unknown context visible.
Produce a practical fix order while leaving room for human judgment.
No. Priority combines severity with exposure, supported impact, evidence confidence, and practical urgency.
No. The product presents a fix queue but does not currently claim an ownership-assignment workflow.
Teams should apply stronger business and architecture context when it exists.