Plan a repeatable vulnerability management cycle
Vulnerability management is the ongoing work of discovering assets and weaknesses, validating findings, prioritizing fixes, and verifying remediation. A vulnerability scan automates some of that work. Maintain an asset inventory with system owners, exposure, data sensitivity, and business importance. Use it to choose which hosts, applications, and cloud resources to scan, and to spot assets that were missed.
Set scan frequency based on risk, change rate, and operational constraints. Internet-facing systems and systems holding sensitive data often warrant closer monitoring. Run targeted scans after significant changes or reports of a new threat. Coordinate scan windows and use appropriately safe checks for production or fragile systems.
Threat intelligence is information analyzed to understand threats, their targets, and their behavior. Relevant sources include internal incident records and restricted commercial feeds, sharing groups such as Information Sharing and Analysis Centers (ISACs), and open-source intelligence gathered lawfully from public material. Check source reliability, timeliness, and relevance. Scanner feeds and plug-ins provide detection content. Threat intelligence helps explain which findings matter now.
NIST · Guide to Cyber Threat Information Sharing · NIST · Security Testing and Assessment
Run scans from the right vantage point
- Port and service discovery
- Identifies reachable ports and services. An open port establishes exposure. Determine whether the service or configuration actually has a weakness.
- Infrastructure scanning
- Checks hosts, services, and configurations against known vulnerability and hardening checks.
- Application and package scanning
- Tests web application behavior or inventories dependencies and flags known issues. Package analysis can also surface vulnerable transitive dependencies.
- Cloud scanning
- Uses authorized interfaces to assess cloud workloads and settings, such as public storage access or overly broad identity permissions.
Update scanner feeds and plug-ins, then set scope, test sensitivity, scan rate, and excluded checks. A credentialed scan can inspect package versions, patches, or configuration from inside the authorized system. Check that authentication succeeded and the scanner account can read what it needs. A noncredentialed scan shows what is visible without login from that network location. The two views answer different questions.
Coordinate permissions and network paths with system owners. Document filtering or other barriers that affect coverage. When appropriate, use the scan to verify IDS or IPS detection and logging. If approved tuning is needed to manage alert volume, scope it to the scan source and window while retaining useful evidence.
NIST SP 800-115 · Technical Guide to Information Security Testing and Assessment
Validate findings and prioritize fixes
- Validate results and coverage. A false positive flags a weakness that is absent. Confirm the installed build and configuration against vendor guidance, since a fix may have been backported. A false negative misses a real weakness. Check for failed authentication, stale plug-ins, excluded checks, and unreachable assets. Compare scanner output with independent evidence where practical.
- Rank by local risk. Consider severity, evidence of exploitation, internet exposure, asset importance, available attack paths, and compensating controls. CVSS describes severity. EPSS estimates the probability of observed exploitation activity over the next 30 days. CISA’s Known Exploited Vulnerabilities (KEV) Catalog identifies vulnerabilities with evidence of exploitation in the wild. Verify that the finding applies to your asset.
- Report and assign work. Give managers a summary of exposure, trends, and overdue high-risk findings. Give technical owners affected assets, evidence, recommended fixes, and due dates.
- Remediate or document an exception. Patch, harden, remove a service, or restrict access. If a fix must wait, document the reason, risk owner, interim controls, and review date. Verify that segmentation actually blocks the relevant path.
- Verify closure. Rescan or test the affected configuration from the relevant vantage point. Check that credentials worked, the fix took effect, and any workaround still functions. Record the result and reopen the finding if necessary.
FIRST · CVSS · FIRST · EPSS FAQ · CISA · Known Exploited Vulnerabilities Catalog · NIST · Enterprise Patch Management
Choose an audit, assessment, or penetration test
An audit examines evidence against defined criteria and calls for appropriate independence from the activity being audited. Internal audit teams can provide that independence when they are separate from the operations under review. External auditors or assessors can bring independent assurance or specialized expertise. A security assessment evaluates how effectively controls are implemented and identifies gaps. The organization can use those findings to plan corrective work and verify it later.
A penetration test attempts to validate exploitability or show how weaknesses can combine into an attack path within an authorized scope. Internal testers may know the environment well. External testers can offer independence and a fresh perspective. Choose based on the objectives and skills required, and define targets, allowed actions, test windows, stop conditions, and contacts in the rules of engagement.
Active reconnaissance directly queries or probes target infrastructure. Passive reconnaissance gathers information without directly probing the target, such as reviewing public records or existing telemetry. Active probing may trigger monitoring. Passive research can still leave records with the services used to gather information.
NIST · Security Testing and Assessment · NIST · Security and Privacy Control Assessment Procedures
Practice case
Three scan results, one maintenance window. The scan flags a medium-severity vulnerability on an internet-facing gateway. The vulnerability appears in CISA’s KEV catalog. It also flags a critical vulnerability on a segmented internal test server, although the vendor says the installed package build may have a backported fix. A credentialed scan of the payroll server reports no findings but logs an authentication failure.
What would you check for each system? Which change would you prioritize, and how would you verify the results?
Review a possible answer
Confirm that the gateway runs an affected version and that the vulnerable service is reachable. Its exposure and known exploitation make it a priority once verified. If a patch cannot be deployed in the window, apply a supported workaround or restrict access and verify it from outside the network.
Compare the internal server’s exact package build with the vendor’s fixed-build advisory and verify the segmentation. Treat the payroll result as incomplete coverage. Restore authorized scanner access and rerun the check. After remediation, rescan the affected assets and record the evidence used to close or retain each finding.
Read and watch
- Compare scanning, examination, and penetration testing methods. NIST · Technical Guide to Information Security Testing and Assessment
- Review how exploitation probability is estimated and used. FIRST · EPSS Frequently Asked Questions
- Watch how a scanner is configured and how its report is read. Use only authorized lab targets for hands-on practice. Video · OPENVAS BASIC Setup and First Scan Tutorial