Reference
Finding fields and lifecycle
Reference issue and anomaly fields, timestamps, statuses, technical context, and workflow transitions.
Last reviewed September 12, 2026
Issue fields and lifecycle
Issue records identify a page or resource condition with severity, type, Open/Acknowledged/Closed state, first and last seen context, description, recommendation, technical details, linked sessions, and raw data where available. Acknowledged means reviewed; Closed means current handling is complete.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| Types | Read the workflow state with its timestamps, affected entity, and owner action. Acknowledging or closing a record changes review status; it does not remove the underlying observation or prove remediation. |
| Severities | Read the workflow state with its timestamps, affected entity, and owner action. Acknowledging or closing a record changes review status; it does not remove the underlying observation or prove remediation. |
| State semantics | Read the workflow state with its timestamps, affected entity, and owner action. Acknowledging or closing a record changes review status; it does not remove the underlying observation or prove remediation. |
| Timestamps | Compare the first, last, and event timestamps with the investigation or reporting window. These values describe SiteWall observations for the active project and do not establish activity outside the captured period. |
Apply the reference
- 1.
Open a representative source record
Use the project selector to choose the website you intend to review, then open Issues in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 2.
Read the field with its context
Interpret the value with its entity type, project, observation window, state, and source link. Do not compare values collected under materially different conditions as if they were equivalent.
- 3.
Carry the definition into the workflow
Use the field to navigate or prioritize, then make the operational decision in the provider, resource, session, finding, policy, or evidence workflow that owns it.
Anomaly fields and lifecycle
Anomaly records identify a behavioral or performance deviation with category, severity, Open/Acknowledged/Closed state, detected time, affected resource, behavioral and network context, sensitive access, linked session or policy context, detailed events, and raw data where available.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| Categories | Read the workflow state with its timestamps, affected entity, and owner action. Acknowledging or closing a record changes review status; it does not remove the underlying observation or prove remediation. |
| Severity | Use the value to prioritize review, then inspect the contributing findings and runtime evidence. A score or severity is a triage signal, not an approval decision or a confirmed incident. |
| State semantics | Read the workflow state with its timestamps, affected entity, and owner action. Acknowledging or closing a record changes review status; it does not remove the underlying observation or prove remediation. |
Apply the reference
- 1.
Open a representative source record
Use the project selector to choose the website you intend to review, then open Anomalies in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 2.
Read the field with its context
Interpret the value with its entity type, project, observation window, state, and source link. Do not compare values collected under materially different conditions as if they were equivalent.
- 3.
Carry the definition into the workflow
Use the field to navigate or prioritize, then make the operational decision in the provider, resource, session, finding, policy, or evidence workflow that owns it.