Unified Findings & Feature Flags
Every security engine reports into one unified findings model, browsed from a single Findings tab with a scanner filter, and switched on per tenant with feature flags.
Unified Findings & Feature Flags
Safeguard's security engines don't each carry their own siloed inbox. Every engine reports into one unified findings model, that model is browsed from one Findings tab per project, and each engine can be switched on or off with a feature flag.
One model, discriminated by finding_type
All engine findings share a single model discriminated by a finding_type field, so you can view, filter, and correlate across engines in one place:
finding_type | Scanner filter option | Source engine |
|---|---|---|
sast | SAST | Application Security Testing |
dast | DAST | Application Security Testing |
api | API Security | Application Security Testing |
container | Container | Application Security Testing |
iac | IaC | Application Security Testing |
redteam | Red Team | Red Team |
dspm | DSPM | DSPM |
aisec | AI Security | AI-SPM |
pkgfw | Package Firewall | Package Firewall |
Software composition findings have their own dedicated Vulnerabilities tab, so they are not repeated in the scanner filter. See SCA.
The short id in the
?scanner=<value>deep link doesn't always equal thefinding_type. AI Security is?scanner=ai-securitybutfinding_type: aisec, and Package Firewall is?scanner=package-firewallbutfinding_type: pkgfw. If you build a?scanner=link by hand, use the dropdown value. An unknown value falls back to All scanners.
Because findings share the model, they share correlation keys, so a confirmed, reachable finding is prioritized together with its related findings from other engines. See AutoTriage for how cross-engine duplicates collapse into one canonical finding, and Vulnerability Prioritization (Reachability Analysis) for how reachability is computed.
Every finding is scoped to its tenant and organization end to end.
The Findings tab and the scanner filter
Findings for a project live in a single Findings tab. Rather than a separate tab per scanner, the tab has a Scanner dropdown at the top:
- All scanners (the default) shows every
finding_typetogether. - Selecting an individual scanner scopes the table, the summary stats, and the underlying queries to that engine's
finding_type.
If a scanner has no findings for the project, the table shows No <Scanner> findings found for this project. That means no scan has posted findings of that type yet. Check that a scan ran, using the engine's own page.
Scanner Coverage deep links
The project Info page shows a Scanner Coverage section: one card per scanner, each with a live finding count. Clicking a card opens the Findings tab with that scanner preselected through a query parameter:
.../findings?scanner=<value>For example, the DSPM card links to .../findings?scanner=dspm.
Feature flags
Each engine is switched on per tenant by a feature flag named scanner:<key>, for example scanner:sast, scanner:dspm or scanner:pkgfw. Flags are independent, so you can enable SAST and DAST without Red Team, or DSPM without any other engine. Ask your Safeguard administrator to change them.
FAQ & Troubleshooting
I picked a scanner in the dropdown and the table is empty. Is something broken?
Not necessarily. No scan has posted findings for that finding_type on this project yet. Check that a scan ran.
Why isn't SCA in the Findings scanner dropdown? SCA has its own dedicated Vulnerabilities tab, so it is left out of the filter to avoid showing the same data twice.
A Scanner Coverage link sent me to "All scanners".
The scanner value in the URL doesn't match a known scanner id. The Findings tab falls back to the unfiltered view rather than erroring.
Related
PR Guard
AI-driven code review that runs against a pull request's diff and surfaces severity-ranked findings, inline in Safeguard and optionally posted back to the pull request itself.
Trusted Artifacts
Packages and images rebuilt from source, signed, and delivered with an SBOM, SLSA provenance and VEX through the Gold registry.