security advisory
A public notice from a vendor, project or government agency describing a security flaw, which versions it affects, and how to fix or work around it.
In more detail
An advisory usually gives the flaw a public identifier, a severity, the version where it was introduced and the version that fixes it. Teams match advisories against their software inventory or software bill of materials to find what must be patched. Machine-readable advisory feeds let a script do that matching automatically.
Example
affected = ver(a["introduced"]) <= ver(c["version"]) < ver(a["fixed"])Related terms
- OSV — Open Source Vulnerabilities: a JSON format and public database describing which package versions each vulnerability affects.
- CVE — A public identifier, such as CVE-2024-21626, given to one known security vulnerability so everyone can refer to it.
- software composition analysis — Finding the open-source packages in your software and checking their exact versions against known vulnerability advisories.
- patch management — The routine of finding, testing and installing software updates that fix security flaws and bugs on every system an organisation runs.
- SBOM — A list of every software package and version inside an image, like an ingredients label.
- vulnerability — A weakness in software or configuration that an attacker could use to cause harm.
- Log4j — Apache Log4j, a very widely used Java library for writing log messages, whose 2021 flaw Log4Shell let attackers run their own code on servers remotely.
- version comparison — Deciding which of two version numbers is newer by the rules of the ecosystem, comparing each part as a number.
- pip-audit — A tool that checks a Python project's pinned dependencies against public advisory databases and reports known vulnerabilities with fixed versions.
Taught in
- Software Composition Analysis with Trivy — Cloud Security & DevSecOps Engineering
- Supply Chain Security: SBOMs & Cosign Signing — Cloud Security & DevSecOps Engineering
- Security Baselines, Policies & Hardening Standards — Cybersecurity Fundamentals, GRC & Cryptography
- Vendor & Third-Party Risk Management Programs — Cybersecurity Fundamentals, GRC & Cryptography
- Dependency Risk And Typosquatting — Application Security & Threat Modeling for Engineers
- Lockfiles And Reproducible Builds — Application Security & Threat Modeling for Engineers
- Software Bill Of Materials — Application Security & Threat Modeling for Engineers
- Image Scanning And Trivy — Application Security & Threat Modeling for Engineers