The Security Lifecycle: Plan-Do-Check-Act
What you'll learn: How the PDCA cycle creates a continuous security improvement process that never stops evolving.
The Core Idea
Remember from the previous lesson that security is continuous improvement, not a final state? The PDCA cycle (Plan-Do-Check-Act) is the engine that drives that improvement. It's a repeating four-phase process borrowed from quality management that perfectly fits security work.
Think of PDCA like maintaining a garden. You don't plant once and walk away—you plan what to grow, do the planting, check how things develop, and act on what you learned by adjusting your approach. Then you repeat the cycle again next season.
The Four Phases
Plan: Identify security risks and design controls to address them. This is where you apply principles like Defense in Depth and determine what security controls you need based on frameworks like NIST or ISO 27001.
Do: Implement your security controls. Install firewalls, configure access controls using RBAC or MAC, establish Trust Boundaries, and deploy your defenses.
Check: Monitor and measure effectiveness. Are your controls working? Continuous monitoring reveals if your Weakest Links are being exploited or if your Attack Surface has grown unexpectedly.
Act: Respond to findings and improve. Adjust controls, add Compensating Controls where needed, refine your Defense-in-Depth layers, and update your security posture based on real-world results.
Then the cycle begins again—security threats evolve, so your Plan phase must incorporate lessons from the previous Act phase.
Why PDCA Matters
Without PDCA, security becomes static and brittle. The cycle ensures you're constantly adapting to new threats, learning from incidents, and closing gaps that continuous monitoring reveals.
Key Takeaway: The PDCA cycle transforms security from a one-time project into an ongoing process—plan your defenses, implement them, monitor their effectiveness, and continuously improve based on what you learn.