In this project, we simulate the implementation of a comprehensive vulnerability management program, from inception to completion.
Inception State: the organization has no existing policy or vulnerability management practices in place.
Completion State: a formal policy is enacted, stakeholder buy-in is secured, and a full cycle of organization-wide vulnerability remediation is successfully completed.
- Tenable (enterprise vulnerability management platform)
- Azure Virtual Machines (Nessus scan engine + scan targets)
- PowerShell & BASH (remediation scripts)
- Vulnerability Management Policy Draft Creation
- Mock Meeting: Policy Buy-In (Stakeholders)
- Policy Finalization and Senior Leadership Sign-Off
- Mock Meeting: Initial Scan Permission (Server Team)
- Initial Scan of Server Team Assets
- Vulnerability Assessment and Prioritization
- Distributing Remediations to Remediation Teams
- Mock Meeting: Post-Initial Discovery Scan (Server Team)
- Mock CAB Meeting: Implementing Remediations
- Remediation Round 1: Outdated Wireshark Removal
- Remediation Round 2: Insecure Protocols & Ciphers
- Remediation Round 3: Guest Account Group Membership
- Remediation Round 4: Windows OS Updates
- First Cycle Remediation Effort Summary
This phase focuses on drafting a Vulnerability Management Policy as a starting point for stakeholder engagement. The initial draft outlines scope, responsibilities, and remediation timelines, and may be adjusted based on feedback from relevant departments to ensure practical implementation before final approval by upper management.
Draft Policy
In this phase, a meeting with the server team introduces the draft Vulnerability Management Policy and assesses their capability to meet remediation timelines. Feedback leads to adjustments, like extending the critical remediation window from 48 hours to one week, ensuring collaborative implementation.
🟡🟡 Mock Meeting Discussion 🟡🟡 💬
Josh:
Hey, good morning Jimmy. How’s everything been lately? I know it’s been a busy few weeks.
Jimmy:
Good morning, John. Yeah, it’s been a bit hectic, but we’re hanging in there. Thanks for asking.
I had a chance to read through the policy draft, and overall it makes sense. However, with our current staffing, we can’t meet the aggressive remediation timelines—especially the 48-hour window for critical vulnerabilities.
Josh:
Yeah, I totally understand. It is a bit aggressive, especially at the start.
Maybe we can extend the critical remediation window to one week for now. That could be a good compromise, and we can reserve the 48-hour requirement for truly severe cases, like major zero-day vulnerabilities.
Jimmy:
That sounds reasonable. We really appreciate the flexibility.
Could we also get a bit of leeway at the beginning, as we work through getting used to the remediation and patching process—just for the first few months?
Josh:
Absolutely. After the policy is finalized, we’ll officially start the program. But we’re planning to give all departments about six months to adjust and get comfortable with the new process.
Does that sound fair?
Jimmy:
It does—thanks, John. We’ll do our best. I appreciate you including us in the decision-making process. It really helps us feel like we’re part of the solution.
Josh:
Yeah, of course. We’re all in this together. Thanks for working with us.
Jimmy:
No problem. And thanks for keeping the meeting short.
Josh:
Yeah, those are my favorite kind. Bye for now!
Jimmy:
See you later.
After gathering feedback from the server team, the policy is revised, addressing aggressive remediation timelines. With final approval from upper management, the policy now guides the program, ensuring compliance and reference for pushback resolution.
Finalized Policy
The team collaborates with the server team to initiate scheduled credential scans. A compromise is reached to scan a single server first, monitoring resource impact, and using just-in-time Active Directory credentials for secure, controlled access.
🟡🟡 Mock Meeting Discussion 🟡🟡 💬
Josh: Morning, Jimmy!
Jimmy: Good morning, Josh. I heard you were ready to conduct some scans?
Josh: Yep, now that our vulnerability management policy is in place, I wanted to get started on conducting some scheduled credential scans of your environment.
Jimmy: Sounds good to me. What's involved, and how can we help?
Josh: We're planning to schedule some weekly scans of the server infrastructure. Uh, we estimate it'll take about four to six hours to scan all 200 assets. We'll need you to provide us with some administrative credentials, which will allow the scan engine to remotely log into the targets to better assess them.
Jimmy: Whoa, whoa, hold on there. What does this scanning actually entail? I'm a bit worried about resource utilization. Also, you want admin credentials to all 200 machines? That doesn't sound safe.
Josh: Yeah, those are valid concerns. The scan engine basically sends different traffic to the servers that will check for the existence of certain vulnerabilities, which include like looking into the registry and seeing if certain out-of-date software is installed or if there are any insecure protocols or cipher suites, that kind of thing. So that's why credentials are required.
Jimmy: I see. Well, as long as it doesn't bring the servers offline, I guess we should be okay.
Josh: Absolutely. Let's just scan a single server for now and keep an eye on the resource utilization.
Jimmy: Not a bad idea.
Josh: Great. Also, for the credentials, can you set up something in Active Directory for us? Like some Active Directory credentials you can just leave disabled until we're ready to do the scan, and then enable them during the scan, and then when it's finished, we can deprovision or at least disable that account. Kind of like a just-in-time access situation.
Jimmy: That sounds good. I'll ask Jane to get started on the automation for the account provisioning.
Josh: Awesome. Okay, talk soon.
Jimmy: Yeah, that sounds good. I'll get back to you once the credentials are set up. See you later.
Josh: See you later.
In this phase, an insecure Windows Server is provisioned to simulate the server team's environment. After creating vulnerabilities, an authenticated scan is performed, and the results are exported for future remediation steps.
Scan 1 - Initial Scan
We assessed vulnerabilities and established a remediation prioritization strategy based on ease of remediation and impact. The following priorities were set:
- Third Party Software Removal (Wireshark)
- Windows OS Secure Configuration (Protocols & Ciphers)
- Windows OS Secure Configuration (Guest Account Group Membership)
- Windows OS Updates
The server team received remediation scripts and scan reports to address key vulnerabilities. This streamlined their efforts and prepared them for a follow-up review.
The server team reviewed vulnerability scan results, identifying outdated software, insecure accounts, and deprecated protocols. The remediation packages were prepared for submission to the Change Control Board (CAB).
🟡🟡 Mock Meeting Discussion 🟡🟡 💬
Josh: Morning, Jimmy, how are you doing?
Jimmy: Not bad for a Monday, and yourself?
Josh: I can't complain. But before we get into the vulnerabilities, how did the actual scan go on your end? Did you have any outages or overutilization or anything?
Jimmy: The scan went well. We were monitoring them, and aside from all the open connections, we would have never known a scan was taking place.
Josh: Yeah, that's good news. I kind of expected that much. We can keep monitoring going forward, but I don't expect we'll have any issues with resource utilization. Do you mind if I dive into the vulnerability findings?
Jimmy: Yeah, absolutely.
Josh: Cool. I'm going to share my screen really quick. So basically, the majority of these vulnerabilities come from Wireshark being installed. You can see all these Wiresharks because it's just super out of date, that's all. One interesting thing I did find is the local guest account on the servers actually belongs to a group, and I looked deeper, and it belongs to the local administrators group. I'm not sure why that is. Also, some of these might be automatically resolved by Windows updates, like this Microsoft Edge Chromium one, and then I'm not sure about this one as well, could be resolved by Windows updates, I'm not really sure. But these we don't have to worry about, the self-signed certificate one, because it's just, you know, the computer self-signed cert. But these medium strength cipher suites and TLS 1.1 and 1.0, these are like deprecated cipher suites and deprecated protocols. So I think we should take some time to remediate these. So basically just Wireshark, the protocols, cipher suites, and removing the guest account is what we're looking at.
Jimmy: Very interesting. The good news is I suspect most of our servers are going to have the same vulnerabilities. Hopefully that makes things easier during remediation.
Josh: Yeah, that's actually good news, like a uniform loadout. Do you foresee any issues with remediating any specifically, like the cipher suites and the insecure protocols?
Jimmy: I highly doubt there will be any issues. We'll run it through the next Change Control Board. Uninstalling Wireshark and fixing the guest account, those shouldn't be an issue. Those aren't supposed to be on the servers anyway. I'll have to talk to our CIS admins about that.
Josh: Yeah, that's good news. I'll go ahead and get started on building out some remediation packages for you to kind of make your life easier when it comes time to fix them.
Jimmy: Yeah, that sounds great.
Josh: Oh, I wanted to ask, do you have anything in place to actually fix the Windows update related vulnerabilities? Like, you have patch management already?
Jimmy: Oh yes, I'm not actually worried about that. Windows update should be handled automatically by next week. We have a patch management in place.
Josh: Okay, excellent. All right, I'll get started on researching the best way to remediate these findings, and I'll get back to you before the next Change Control Board.
Jimmy: Sounds good. Talk to you soon.
Josh: Cool, cool. Talk to you soon.
The Change Control Board (CAB) reviewed and approved the plan to remove insecure protocols and cipher suites. The plan included a rollback script and a tiered deployment approach.
🟡🟡 Mock Meeting Discussion 🟡🟡 💬
Johnny: Okay, next up on the list are a couple of vulnerability remediations for the server team: number one, removal of insecure protocols, and number two, removal of insecure cipher suites. It looks like Josh from the risk department is working in conjunction with Jimmy from infrastructure on this. Jimmy, do you want to walk us through the technical aspects of the change being implemented?
Jimmy: Normally, I would, but do you mind giving this one to Josh? He actually built the solution for us. We're still getting used to the process.
Josh: Yeah, I can explain these. So basically, insecure cipher suites and protocols—the existence of those on the system just means that the system is capable of negotiating and using some kind of algorithm or protocol that's been deprecated, right? If it connects to a server and the server only wants to use those protocols, it's possible that the computer will use them, and these are controlled by the Windows registry. It's a really simple fix. We just wrote a PowerShell script that goes through and disables all the insecure protocols and ciphers and then enables the ones that are standardized or that are like today's standard, that are secure. So, it's really straightforward.
Jack: Yeah, that sounds good, but what if something goes wrong? Do we have a rollback plan in place? Did you even think about that?
Josh: Yes, absolutely. So first of all, we're going to do a tiered deployment. So it means like a pilot group, which is a really small group of computers, pre-pilot, pre-production, and then finally production where it goes everywhere. On top of this, we have a fully built-in, test-made automated rollback script for each remediation. So the script will actually restore the original protocols and ciphers should there be any unknown issues that come up.
Jack: That sounds good. I guess I notice the fixes are simple registry updates. I'm not too concerned, I suppose.
Jimmy: Yep, yep, exactly, exactly. Any more questions from anybody?
Johnny: Great, that wraps things up for this week's CAB meeting. See you all next week.
Josh, Jimmy, and Jack: See you later.
Remediation Round 1: Outdated Wireshark Removal
The server team used a PowerShell script to remove outdated Wireshark. A follow-up scan confirmed successful remediation.
Wireshark Removal Script
Scan 2 - Third Party Software Removal
Remediation Round 2: Insecure Protocols & Ciphers
The server team used PowerShell scripts to remediate insecure protocols and cipher suites. A follow-up scan verified successful remediation, and the results were saved for reference.
PowerShell: Insecure Protocols Remediation
PowerShell: Insecure Ciphers Remediation
Scan 3 - Ciphersuites and Protocols
Remediation Round 3: Guest Account Group Membership
The server team removed the guest account from the administrator group. A new scan confirmed remediation, and the results were exported for comparison.
PowerShell: Guest Account Group Membership Remediation
Scan 4 - Guest Account Group Removal
Remediation Round 4: Windows OS Updates
Windows updates were re-enabled and applied until the system was fully up to date. A final scan verified the changes
Scan 5 - Post Windows Updates
The remediation process reduced total vulnerabilities by 80%, from 30 to 6. Critical vulnerabilities were resolved by the second scan (100%), and high vulnerabilities dropped by 90%. Mediums were reduced by 76%. In an actual production environment, asset criticality would further guide future remediation efforts.
Remediation Data
After completing the initial remediation cycle, the vulnerability management program transitions into Maintenance Mode. This phase ensures that vulnerabilities continue to be managed proactively, keeping systems secure over time. Regular scans, continuous monitoring, and timely remediation are crucial components of this phase. (See Finalized Policy for scanning and remediation cadence requirements.)
Key activities in Maintenance Mode include:
- Scheduled Vulnerability Scans: Perform regular scans (e.g., weekly or monthly) to detect new vulnerabilities as systems evolve.
- Patch Management: Continuously apply security patches and updates, ensuring no critical vulnerabilities remain unpatched.
- Remediation Follow-ups: Address newly identified vulnerabilities promptly, prioritizing based on risk and impact.
- Policy Review and Updates: Periodically review the Vulnerability Management Policy to ensure it aligns with the latest security best practices and organizational needs.
- Audit and Compliance: Conduct internal audits to ensure compliance with the vulnerability management policy and external regulations.
- Ongoing Communication with Stakeholders: Maintain open communication with teams responsible for remediation, ensuring efficient coordination.
By maintaining an active vulnerability management process, organizations can stay ahead of emerging threats and ensure long-term security resilience.