Vulnerability Management, Alerting & Monitoring

Security+ SY0-701 · Security Operations

By Abu Anns · Last updated 20 November 2026Exam version: SY0-701

The vulnerability management lifecycle

Vulnerability management is a continuous cycle, not a one-time project: identify vulnerabilities, analyze and prioritize them, remediate them, validate the fix, and report on the results. The exam tests each stage and the tools used at each stage. The cycle never ends, because new vulnerabilities are discovered every day and every change to the environment can introduce new ones.

Identification starts with vulnerability scanning: automated tools that probe systems for known weaknesses and compare what they find against databases such as the National Vulnerability Database (NVD) and the Common Vulnerabilities and Exposures (CVE) list. Scans can be credentialed (the scanner logs in with credentials and inspects the system from inside, producing more accurate results) or non-credentialed (the scanner probes from outside, seeing only what an external attacker would see). Penetration testing goes further: a human tester actively tries to exploit vulnerabilities, simulating a real attack. Other identification sources include threat intelligence feeds, application security testing (static analysis of source code, dynamic testing of running applications), and configuration audits against benchmarks such as the CIS benchmarks.

Analysis: CVSS, false positives, and prioritization

Not every finding deserves the same urgency. CVSS (Common Vulnerability Scoring System) assigns each vulnerability a score from 0.0 to 10.0 based on its characteristics: how it can be exploited, how complex the attack is, whether authentication is needed, and what the impact is. Scores are grouped into ratings: None (0.0), Low (0.1–3.9), Medium (4.0–6.9), High (7.0–8.9), and Critical (9.0–10.0). The exam tests the bands: a score of 9.8 is Critical, a score of 5.3 is Medium. But CVSS is only a starting point — prioritization must also consider whether the vulnerability is actually exploitable in your environment, whether the affected system is exposed to the internet, and how important the system is.

Scanners are not perfect. A false positive is a finding that reports a vulnerability that does not actually exist; a false negative is a real vulnerability the scanner missed. False positives waste time; false negatives create a false sense of security. Remediation is the fix: patching is the most common, but sometimes the right answer is a compensating control (isolating the system), reconfiguring the service, or accepting the risk when the fix is impossible and the impact is low. Validation confirms the fix worked, usually by rescanning. Reporting communicates the results to management, including the risk that remains.

Alerting and monitoring: SIEM, IDS/IPS, and logs

Monitoring is how an organization sees what is happening on its network. The central tool is the SIEM (security information and event management) system, which collects logs from across the environment — firewalls, servers, endpoints, applications — correlates them, and generates alerts when it detects suspicious patterns. A SIEM's value is correlation: a single failed login is noise, but a hundred failed logins followed by a successful login from an unusual country is an alert.

An IDS (intrusion detection system) monitors traffic and raises alerts when it sees suspicious activity, but does not block anything. An IPS (intrusion prevention system) does the same detection and also blocks the malicious traffic. Both can be network-based (NIDS/NIPS, watching traffic) or host-based (HIDS/HIPS, watching a single system). Detection methods include signature-based (matching known attack patterns), anomaly-based (flagging behavior that deviates from a learned baseline), and heuristic-based (using rules about suspicious behavior). Signature-based detection is precise but misses new attacks; anomaly-based detection catches new attacks but generates more false positives.

Other monitoring tools the exam names: NetFlow (collecting network traffic metadata to spot unusual patterns), DLP (monitoring for sensitive data leaving the organization), antivirus/antimalware (detecting known malicious software on endpoints), vulnerability scanners (as above), and SCAP (Security Content Automation Protocol, a standard for automated vulnerability management and configuration checking). Log management matters too: logs must be collected centrally, protected from tampering, retained for the required period, and reviewed — logs nobody reads are useless. Alert tuning is the ongoing work of adjusting alert thresholds so the team sees real incidents without drowning in false positives; too many alerts leads to alert fatigue, where real warnings get ignored.

Threat intelligence and information sharing

Vulnerability management and monitoring both improve when the organization knows what its adversaries are doing. Threat intelligence is information about current threats: which actors are active, which vulnerabilities are being exploited in the wild, and which indicators of compromise (malicious IP addresses, domains, file hashes) to watch for. Threat feeds deliver this information automatically, and a SIEM can consume feeds to alert on traffic to known-bad addresses. Information sharing organizations such as ISACs (Information Sharing and Analysis Centers) let companies in the same industry warn each other about attacks they have seen. The exam tests the practical use of threat intelligence: if a feed reports that a vulnerability you have is being actively exploited, that vulnerability jumps to the top of the patching queue regardless of its CVSS score, because the threat is no longer theoretical.

Two more monitoring concepts to know. Quarantine is the isolation of a suspicious file, email, or system so it cannot cause harm while it is investigated — a quarantined email is held rather than delivered, and a quarantined endpoint is cut off from the network. Security orchestration connects monitoring tools to response actions: when the SIEM raises a critical alert, orchestration can automatically isolate the affected endpoint, block the malicious IP at the firewall, and open an incident ticket. This is the link between monitoring (seeing the attack) and incident response (stopping it), and it is why the exam treats alerting, monitoring, and automation as one connected workflow rather than separate topics.

Log management deserves a final word, because it underpins everything in this guide. Logs must be collected centrally (so an attacker who compromises one system cannot delete the evidence of their activity), protected from tampering (ideally written to append-only storage), time-synchronized (so events across systems can be correlated accurately — NTP is essential), and retained for the period the organization's policy and regulations require. Logs that are collected but never reviewed are a compliance checkbox, not a security control: the value of a log is realized only when someone — or a SIEM — actually reads it.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.A vulnerability scan reports a finding with a CVSS score of 9.8. How should this vulnerability be classified?

Report an error

Q2.A security team wants its vulnerability scans to inspect installed software versions and configuration settings on each server, not just probe open ports from the network. Which type of scan should it run?

Report an error

Q3.A vulnerability scanner reports that a server is missing a critical patch. The administrator checks the server and confirms the patch was installed months ago. What is this scanner result called?

Report an error

Q4.A company wants a system that not only detects a known attack signature in network traffic but automatically blocks the malicious packets before they reach the target server. Which solution should it deploy?

Report an error

Q5.A security operations center wants a single system that collects logs from firewalls, servers, and endpoints, correlates events across them, and raises alerts on suspicious patterns. Which tool provides this?

Report an error

Q6.After patching a critical vulnerability on a server, the security team runs a follow-up scan to confirm the vulnerability is gone. Which stage of the vulnerability management lifecycle is this?

Report an error

Q7.A company's security team receives thousands of alerts per day, and analysts have started ignoring them. Many alerts turn out to be harmless. What should the team do to fix this problem?

Report an error

Q8.A company hires a security firm to simulate a real attacker: the testers actively try to exploit vulnerabilities in the company's systems and report which attacks succeeded. What is this activity called?

Report an error