Security Planning and Engineering
Domain 4 focuses on security planning and engineering: translating strategy, mission needs, and risk decisions into executable plans. The exam tests security plans, CONOPS, implementation schedules, resource estimates, migration and transition planning, and alignment with enterprise architecture.
Core rules
- Anchor the security plan in mission and business objectives, scope, assumptions, constraints, and risk tolerance.
- Define roles, responsibilities, authorities, and coordination points across engineering, operations, and procurement.
- Break work into phases with dependencies, milestones, entry and exit criteria, resources, and measurable success criteria.
- Plan migration and transition, including coexistence, rollback, data movement, and user transition.
- Integrate security into the systems engineering plan and project schedule; do not create a parallel plan.
- Establish change control and update the plan when architecture, threats, or requirements change.
Worked example
An enterprise plans a zero-trust segmentation program. The security plan defines scope (two data centers, 40 applications), success metrics (lateral movement blocked in tests, 95 percent of flows authorized by policy), and phases: inventory, policy design, pilot, wave migration, decommission legacy trust zones. Dependencies include identity integration and application owner sign-off. Rollback restores the prior firewall rules for 72 hours. The plan assigns risk acceptance to the CISO and schedules post-transition monitoring.
Traps
Planning without budget or schedule; no success criteria; skipping rollback and coexistence; treating the plan as static; and failing to align with enterprise architecture or mission owners.