What do scanner terms like match, enrich and triage mean?
A plain glossary of vulnerability scanner terms: inventory, SBOM, purl, advisory, alias, match, enrichment, triage, reachability, VEX and baseline.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
A plain glossary of vulnerability scanner terms: inventory, SBOM, purl, advisory, alias, match, enrichment, triage, reachability, VEX and baseline.
Reviewers often check public signals first: email authentication, TLS, a security.txt file and a clear security page. Check them on your domain.
COOP and COEP together make a page cross-origin isolated. Learn what each header controls, which browser features need them, and how to roll them out.
CVE, GHSA, USN and DSA identify different things: a vulnerability, a GitHub advisory, an Ubuntu notice and a Debian advisory. Learn which to track and why.
EPSS uses about 2,850 daily features: exploit code, chatter, CVSS metrics, age and references. Plain definitions of each group and what it cannot see.
A security platform usually stores more than findings: metadata, code snippets, user data, logs. Here is how to ask a vendor for a complete data inventory.
Before a dependency scanning PoC, find out what leaves your network: package lists, source code, or metadata. Questions to ask and a way to verify it.
CVSS scores map to None, Low, Medium, High and Critical bands, with Critical starting at 9.0. The full table, what the bands mean and how to use them.
Triage history is the set of decisions, reasons, owners and dates attached to findings. Here is the field list to export before you leave a scanner.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.