Software has CVEs—known vulnerabilities with scores (CVSS). Process: discover, prioritize, patch, verify.
Sources
Dependency scanners (npm audit, pip-audit, Dependabot), container scans, quarterly pen tests.
Prioritize
Exploitability + exposure (internet-facing) + asset criticality—not all CVEs need immediate weekend work.
Important interview questions and answers
- Q: Zero-day?
A: Unknown vulnerability with no patch yet—compensating controls matter. - Q: SLA?
A: Critical internet-facing patch in days; internal tools may differ.
Self-check
- What is a CVE?
- How prioritize vulns?
Tip: Enable Dependabot/Renovate—do not ignore lockfile PRs forever.
Interview prep
- CVE?
Public identifier for a known vulnerability.