Skip to content
Asuruas
Methodology

Finding anatomy, severity, and priority

A useful finding explains the evidence, affected scope, technical meaning, business context, recommended action, and verification method.

Run a free website audit See a sample report
Audiencecustomers, administrators, reviewers, and procurement teams PurposeUnderstand scope, evidence, and interpretation Reading time2 min · 281 words Last reviewed
Start reading
Methodology

Finding anatomy, severity, and priority

State authorization, scope, method, evidence type, limitations, interpretation rules, and the verification required before closure.

Primary topicFinding anatomy, severity, and priority

A useful finding explains the evidence, affected scope, technical meaning, business context, recommended action, and verification method.

Operating outcomeAccountable improvement

Turn technical evidence into a defensible decision record for both stakeholders and implementers.

Review statusMaintained resource

Reviewed for accuracy, clarity, and operational use.

01

Finding record

  • Stable identifier
  • Title and category
  • Detection source and timestamp
  • Evidence
  • Affected assets
  • Severity
  • Confidence
  • Business context
  • Priority
  • Recommendation
  • Owner
  • Status
  • Verification
02

Severity is not priority

Severity describes the seriousness of the technical condition. Priority describes when the organization should act after considering business impact, reach, exploitability, dependency, effort, timing, and accepted risk.

03

Outcome states

  • Open
  • Triaged
  • Planned
  • In progress
  • Ready for verification
  • Resolved
  • Accepted risk
  • False positive
  • Not applicable
  • Reopened
04

Evidence standard

  • State the authorization, scope, exclusions, environment, timing, and methodology version for finding anatomy, severity, and priority.
  • An executive explanation and an implementation record generated from the same source data.
  • Distinguish direct observation, calculated result, heuristic, inference, and manual judgment.
  • Preserve failed, incomplete, blocked, and uncertain checks instead of silently dropping them.
05

Interpretation and decision record

A methodology should help reviewers reach the same bounded conclusion from the same evidence. It should not imply certainty beyond the assessed scope. Record the finding, limitation, owner, decision, remediation, and the verification required to turn technical evidence into a defensible decision record for both stakeholders and implementers.

06

Decision and verification record

01

Scope

Name the website, environment, URLs, entities, templates, or user journeys included in the finding anatomy, severity, and priority decision.

02

Decision

Record the chosen action, owner, priority, dependencies, approval, and the evidence that justified it.

03

Verification

Confirm the report matches the current source records, scope, approvals, and verification status before distribution.

Next useful action

Turn finding anatomy, severity, and priority into an accountable record.

A reproducible finding anatomy, severity, and priority assessment record with scope, evidence, limitations, and verification rules.

Run a free website audit See a sample report
Continue

Related resources

01

Website operations intelligence in one accountable system

Asuruas connects website inventory, technical audits, evidence, remediation, reporting, and operational history without reducing the website to a one-time project.

Open resource → 02

See how Asuruas communicates technical findings

Review the structure of an executive summary, category scores, prioritized findings, technical evidence, and recommended next steps.

Open resource → 03

Security controls for accounts, website authorization, and audit evidence

Asuruas combines verified site authority, bounded audit scope, tenant-aware access, MFA, revocable sessions, signed provider events, and auditable operations.

Open resource → 04

Run a free audit on a website you are authorized to assess

Create an Explorer account, verify the email and website, choose a bounded scope, and audit up to 250 pages each month without a payment card.

Open resource → 05

Asuruas audit and operations methodology

A transparent method for defining scope, collecting evidence, normalizing findings, setting severity and priority, planning remediation, and verifying outcomes.

Open resource → 06

Accessibility evaluation methodology

Asuruas organizes automated and manual accessibility work around the current WCAG 2 family without presenting an automated scan as proof of conformance.

Open resource →