Plain-language meaning
The seriousness of a detected issue based on risk or technical consequence.
Why it matters
Severity affects how a website is discovered, understood, used, maintained, or evaluated. In an Asuruas report, the term remains connected to evidence and context.
Use “Severity” precisely
In an audit, severity should name a specific condition, object, relationship, or decision—not serve as a vague synonym for website quality. Attach the term to the exact evidence and affected scope so a reviewer can understand what was observed and what remains uncertain.
Evidence to inspect for Severity
- Website inventory, ownership, environments, vendors, dependencies, maintenance history, incidents, findings, work, approvals, and verification.
- Clear accountability for the next action and the conditions that trigger escalation.
- Document how the term affects the outcome to keep website work visible, accountable, repeatable, and connected to business responsibility.
- Confirm the owner, evidence, decision, implementation record, retest, and follow-up date are all present.
Decision and verification record
Scope
Name the website, environment, URLs, entities, templates, or user journeys included in the severity decision.
Decision
Record the chosen action, owner, priority, dependencies, approval, and the evidence that justified it.
Verification
Confirm the owner, evidence, decision, implementation record, retest, and follow-up date are all present.
Turn severity into an accountable record.
A shared working definition of severity used consistently across reports and operational records.