What's changed: Initial version
4.1Vulnerability management
Covers vulnerability management, the continuous cycle of finding and fixing weaknesses (identify -> manage -> mitigate); the difference between active reconnaissance (touching the target directly) and passive reconnaissance (using only public information and observation); and port scanning to list open ports plus automation for repetitive work—as the foundation for working out "where the holes are and how to close them."
The first step in protecting a system is knowing "where the weak spots are." Finding and closing the holes yourself before an attacker finds them first—this continuous effort is vulnerability management. This section covers the flow of finding weaknesses (identify), organizing and prioritizing them (manage), and closing them with patches or configuration changes (mitigate); the difference in how you investigate—active reconnaissance vs. passive reconnaissance; and the representative technique of port scanning plus the automation that streamlines repetitive work—learned not by rote but through the lens of "which hole to close, and how."
4.1.1The vulnerability management cycle
- Identify is the stage of discovering what weaknesses the assets have. Using vulnerability scanners, port scans, and cross-checks against an asset inventory, you learn "what" is running and "in which version." You cannot protect assets you cannot see, so visibility comes first.
- Manage is the stage of recording and classifying the found vulnerabilities and prioritizing them by severity and asset importance. Since you cannot fix everything at once, you plan to address the highest-impact ones first. Scores such as CVSS help guide prioritization.
- Mitigate is the stage of actually closing the holes—reducing weaknesses through patching, configuration changes, disabling unneeded services, and applying workarounds. After closing, you re-scan to confirm resolution. Crucially, vulnerability management is not a one-time task but a continuously repeating cycle.
4.1.2Active vs. passive reconnaissance, port scanning, and automation
- Active reconnaissance investigates by sending packets directly to the target and learning from the responses. Port scanning and querying services are typical; it is accurate but leaves traces in the target's logs and is more easily detected.
- Passive reconnaissance gathers information without touching the target, using only public information and observation of traffic—WHOIS, public web pages, search results, and the like. It leaves no traces, but the information obtained is limited.
- Port scanning is an active technique that lists which ports are open and what services run (nmap is the classic tool). Automation hands repetitive work—scanning and cross-checking—to tools and scripts so a wide scope can be inspected regularly and comprehensively. It sustains a scale that manual effort alone cannot keep up with.
Most-tested: vulnerability management is a continuous cycle of identify -> manage -> mitigate; active reconnaissance sends packets directly and is more detectable while passive reconnaissance observes public information and leaves no traces; port scanning (nmap) is an active technique; automation sustains regular, wide-scope inspection. Learn to tell whether an investigation method is active or passive.
Suppose you are told to find the weaknesses in a set of servers newly assigned to you. Rather than patching haphazardly, the right approach is to think along the vulnerability management cycle. In the first stage, identify, you run a port scan against the target servers (e.g., listing open ports with nmap) to learn what services run and in which versions. This "send packets directly and watch the responses" method is active reconnaissance—accurate, but because it shows up in the target's logs, in production it requires prior approval and scheduling. If you want to do groundwork before approval, limit yourself to passive reconnaissance using only public information (reading announcements or documentation of externally exposed services). In the next stage, manage, you do not merely list the vulnerabilities but prioritize them by severity score and by asset importance such as "is this server used for payments." Finally, in mitigate, you apply patches or configuration changes and re-scan to confirm the hole is truly closed. The key point: vulnerability management is not "scan once and done"—since new vulnerabilities are disclosed daily, the posture is to keep the identify -> manage -> mitigate cycle running continuously. Moreover, once the target grows to hundreds of machines, manual effort cannot keep up, so automating scans and cross-checks to enable regular, comprehensive inspection becomes the realistic defense.
| Aspect | Active reconnaissance | Passive reconnaissance |
|---|---|---|
| Contact with target | Sends packets directly | No contact, observation only |
| Typical means | Port scanning, querying services | WHOIS, public web, search results |
| Detectability | Leaves logs and is more detectable | Leaves no traces |
| Information gained | Accurate and concrete | Limited but safe |
Trap: "A port scan just looks at public information, so it is passive reconnaissance and the target never notices" is wrong—port scanning sends packets directly to the target and is active reconnaissance, leaving traces in the target's logs and being detectable. Also wrong: "once you scan and fix vulnerabilities, you are safe thereafter"—since new vulnerabilities are disclosed daily, vulnerability management is a continuous cycle of identify -> manage -> mitigate.
4.1.3Section summary
- Vulnerability management is a continuous cycle of identify -> manage -> mitigate; after closing a hole, re-scan to confirm
- Active reconnaissance sends packets directly and is detectable; passive reconnaissance observes public information and leaves no traces
- Port scanning (nmap) is an active technique; automation sustains regular, comprehensive inspection at scale
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You are about to list open ports on a production server with nmap and directly examine the running services and versions. How is this investigation method best classified?
Q2. Which is the most appropriate order for the vulnerability management flow?
Q3. For hundreds of servers, you want to keep inspecting open ports and known vulnerabilities regularly and comprehensively. What is the most realistic approach?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.

