Framework: The Center for Internet Security (CIS) Top 18 Controls

Episode 82 — Safeguard 18.2 – Internal and red team exercises

Safeguard 18.2 extends penetration testing to include internal assessments and red team exercises that emulate an attacker with initial access. Internal testing evaluates how far a threat could move laterally, escalate privileges, and access sensitive data once inside the network. Red team exercises simulate full-scale adversary campaigns, testing detection, containment, and response capabilities across technical and human layers. These exercises reveal not just vulnerabilities, but also gaps in processes and situational awareness. They measure whether monitoring tools trigger alerts, whether analysts interpret them correctly, and how quickly response teams can contain the intrusion. Internal and red team testing transforms theoretical preparedness into proven readiness, helping organizations close the final mile between defense design and real-world resilience. Implementing this safeguard involves careful planning and coordination between leadership, blue teams, and testing personnel. Internal tests should include domain privilege escalation, network traversal, and data exfiltration attempts, all performed under controlled conditions with predefined safety boundaries. Red team engagements require clearly documented objectives, such as testing detection of phishing payloads or lateral movement techniques. During these exercises, communication protocols and deconfliction measures prevent accidental business disruption. Post-engagement debriefs bring together both offensive and defensive participants to review findings collaboratively, focusing on lessons learned rather than blame. Metrics such as detection time, escalation efficiency, and remediation completion rates guide continuous improvement. When performed regularly, internal and red team exercises evolve cybersecurity from static prevention toward adaptive readiness—where the organization learns directly from simulated adversaries and strengthens every layer of its defense and response capability.  Produced by BareMetalCyber.com, where you’ll find more cyber audio courses, books, and information to strengthen your educational path. Also, if you want to stay up to date with the latest news, visit DailyCyber.News for a newsletter you can use, and a daily podcast you can commute with.

Episode 81 — Safeguard 18.1 – External testing programs

Safeguard 18.1 requires organizations to establish and maintain a formal penetration testing program that includes recurring external assessments. External tests simulate real-world attackers operating from outside the enterprise perimeter, probing exposed systems, web applications, and cloud environments for exploitable weaknesses. Unlike automated vulnerability scans, these engagements apply human expertise to chain vulnerabilities, test business logic, and evaluate how well network defenses withstand targeted attacks. The program must define scope, frequency, and reporting standards, ensuring that results are actionable and repeatable. External penetration testing provides the most realistic measurement of how resilient an organization’s public-facing assets truly are and whether the layered defenses described in previous controls—such as patching, configuration management, and monitoring—perform effectively under adversarial pressure. To operationalize this safeguard, enterprises should define a documented testing policy outlining which assets, IP ranges, and applications fall within scope. Engagements must be performed by qualified testers who follow strict rules of engagement to avoid service disruption while still providing comprehensive evaluation. Pre-test coordination with internal teams ensures monitoring and incident response systems are aware of expected activity, allowing evaluation of detection effectiveness. After testing, findings should be risk-ranked, correlated with asset criticality, and assigned to responsible owners for remediation. Reports must include technical evidence, proof-of-concept details, and mitigation recommendations. Testing frequency should be at least annual, or more often after significant infrastructure or application changes. Over time, an external testing program evolves from compliance validation into a continuous improvement process—one that strengthens trust by demonstrating that defenses are not only designed well but tested against real threats in authentic conditions.  Produced by BareMetalCyber.com, where you’ll find more cyber audio courses, books, and information to strengthen your educational path. Also, if you want to stay up to date with the latest news, visit DailyCyber.News for a newsletter you can use, and a daily podcast you can commute with.

Episode 80 — Overview – Why penetration testing validates defenses

Control 18—Penetration Testing—closes the CIS framework by validating how well all other controls perform under real-world conditions. While vulnerability scanning identifies potential weaknesses, penetration testing goes further by exploiting them to assess the enterprise’s true exposure. These controlled attacks, conducted by skilled professionals, reveal how vulnerabilities chain together, how far an attacker could advance, and whether detection and response mechanisms activate as intended. Penetration testing provides management with concrete evidence of risk, translating technical gaps into business impact. It verifies that security investments deliver measurable protection and highlights areas where layered defenses may overlap or fail. Ultimately, this control ensures that an organization’s cybersecurity posture is not theoretical but proven through realistic adversarial testing. Conducting effective penetration tests requires clear scope, defined rules of engagement, and strong collaboration between testers and stakeholders. Scenarios should reflect both external and internal attack perspectives, covering network, application, and physical entry points. Tests may also include social engineering components to gauge user resilience. All testing must balance realism with safety—avoiding disruption while capturing authentic results. Findings should be prioritized by exploitability and potential business impact, with remediation plans tracked through formal governance channels. Repeat testing validates that fixes are effective and that no regressions occur over time. For mature organizations, red team exercises simulate advanced, persistent threats to evaluate end-to-end detection and response capabilities. Control 18 thus serves as the final proof point of the CIS Controls: confirming that security architecture, processes, and people can withstand—and learn from—the tactics of real adversaries.  Produced by BareMetalCyber.com, where you’ll find more cyber audio courses, books, and information to strengthen your educational path. Also, if you want to stay up to date with the latest news, visit DailyCyber.News for a newsletter you can use, and a daily podcast you can commute with.

Episode 79 — Remaining safeguards summary (Control 17)

The remaining safeguards in Control 17 reinforce the full lifecycle of incident response—spanning preparation, communication, testing, and continuous improvement. These include assigning key response roles, defining secure communication mechanisms, conducting post-incident reviews, and establishing thresholds that differentiate normal events from true incidents. Together, these steps ensure that teams can act quickly, share accurate information, and recover efficiently without confusion. Designated roles provide clarity of authority; communication protocols—both primary and backup—keep coordination intact even if normal channels are compromised. Post-incident reviews transform each response into a learning opportunity, refining both technology and human processes. Defining thresholds prevents overreaction to minor anomalies while ensuring serious incidents receive immediate escalation. Implementing these safeguards requires integrating technical and organizational readiness. Communication tools—such as dedicated incident bridges, encrypted messaging, and offline contact lists—must be tested alongside technical playbooks. Regular cross-functional meetings evaluate whether response thresholds and classification criteria still match business risk and compliance obligations. Documentation from post-incident reviews should update training materials, configuration baselines, and preventive controls. Mature organizations track and trend incident metrics to identify recurring weaknesses and measure improvement over time. When practiced consistently, these safeguards build resilience not just in systems, but in people and processes. Control 17, as a whole, evolves cybersecurity from a set of defensive measures into a dynamic capability—one that anticipates disruption, coordinates under pressure, and emerges stronger from every challenge encountered.  Produced by BareMetalCyber.com, where you’ll find more cyber audio courses, books, and information to strengthen your educational path. Also, if you want to stay up to date with the latest news, visit DailyCyber.News for a newsletter you can use, and a daily podcast you can commute with.

Episode 78 — Safeguard 17.2 – Tabletop exercises

Safeguard 17.2 emphasizes the importance of testing the incident response plan through structured tabletop exercises. These simulations bring together key personnel—from technical teams to executives—to rehearse decision-making during hypothetical security events. Unlike full-scale technical drills, tabletop exercises focus on communication flow, role clarity, and coordination across departments. Scenarios may include ransomware outbreaks, cloud breaches, insider threats, or supply-chain compromises. The purpose is to identify gaps in preparedness—such as unclear escalation paths, communication delays, or conflicting responsibilities—before a real incident exposes them. Regular exercises, conducted at least annually, help maintain readiness and reinforce a culture of collaboration under pressure. To execute effective tabletop sessions, organizations should design scenarios that reflect realistic challenges based on current threat intelligence and business context. Each session should define clear objectives, such as evaluating response time, testing regulatory reporting procedures, or verifying decision-making authority. Facilitators document outcomes and capture improvement actions, assigning ownership for follow-up. Afterward, debrief sessions discuss what worked, what failed, and how the plan can evolve. Mature programs alternate between table-based and functional simulations, gradually introducing live elements such as system isolation or communication with external stakeholders. These rehearsals build confidence, ensure cross-functional awareness, and strengthen trust among participants. Safeguard 17.2 transforms policy into practice, turning static documentation into operational muscle memory that reduces uncertainty and sharpens the organization’s ability to respond effectively when real crises occur.  Produced by BareMetalCyber.com, where you’ll find more cyber audio courses, books, and information to strengthen your educational path. Also, if you want to stay up to date with the latest news, visit DailyCyber.News for a newsletter you can use, and a daily podcast you can commute with.