Skip to content
FendixDocumentationDocs

.fendix.yaml · SEC-001 · SARIF

Current release v3.7.0
ConceptStable

Release decision history

Distinguish a later execution from a later authoritative decision for the same target.

On this page

Distinguish a later execution from a later authoritative decision for the same target.

Read a target’s timeline

Open Decision History from the target’s decision. The timeline belongs to one stored target in one workspace, not every scan with a similar URL or display name. It shows recorded decisions, in-progress executions, failed executions and completed scans without a decision, newest first.

Each recorded decision retains its own policy, threshold, coverage, timestamp and finding counts. Superseded means a later completed scan recorded a verdict; it does not mean the historical verdict was deleted or revised. Older records may lack some context.

Example: BLOCK still stands

Monday records BLOCK. Tuesday’s scan fails. Wednesday’s scan is still running. Monday remains the latest recorded decision. When Wednesday completes and records WARN, WARN becomes current and Monday remains in the timeline.

Read the decision age alongside the newest execution. A recent failed attempt is not fresh assurance. Use Compare with previous on a recorded decision, or select two loaded decisions in the comparison picker. Open the scan to inspect its original evidence.

What history does not establish

A change to a less restrictive verdict is not automatically a reduction in risk. A different threshold, policy, engine, scope or analyzer coverage can explain it. History reflects retained records; deletion or retention limits can leave gaps. It does not reconstruct missing scans or re-run their policies.

Continue the journey

  1. 01Security scan comparison
  2. 02Explore the demo
  3. 03Decision Intelligence product