Guide
Configure finding detection
Tune issue and anomaly detection while preserving enough coverage to notice meaningful changes.
Last reviewed September 12, 2026
Configure issue detection
Issue detection settings determine which supported conditions SiteWall evaluates and how they are classified. Record the existing configuration, change one preset or rule at a time, preserve the owner and reason, and compare subsequent findings against representative traffic before expanding the change.
Procedure
- 1.
Open the correct project and page
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.
Preserve the original signal
Record the finding link, current status and severity, affected entity, first and last observation, relevant session, and recent deployment context before changing disposition or detection settings.
- 3.
Presets
Compare the signal with the affected entity, linked session, timing, and expected behavior before setting its disposition.
- 4.
Reproduce and compare
Repeat a representative journey when safe, then compare the new session and source records with the original finding. Verify that the selected disposition describes the reviewed evidence.
- 5.
Record the decision trail
Preserve the original finding, supporting records, expected behavior, owner, disposition, rationale, and follow-up. A workflow-state change must not replace the evidence used to reach it.
Configure anomaly detection
Anomaly detection settings tune supported deviation and sensitivity rules. Establish a normal observation period first, change one setting at a time, document the reason, and review both missed activity and false positives across representative journeys.