🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →
Sequence 296 — Access-overgrant incident
Context: Cross-Chapter Integration & Capstones | Capstone / Integration
Source: CDMP Master Execution Manual
When / purpose
Reactivate Chapter 7 within the broader data environment.
What you should learn
- Least privilege is tested through actual permissions.
- Governance intent and technical enforcement are related but distinct.
What to read / study
| Priority | Resource | Use now | Stop point |
|---|---|---|---|
| MUST | Cross-Chapter Capstone & Incident Roadmap | Use only the capstone/checkpoint named by this card. | Do not pull future chapter controls into earlier checkpoints. |
| REFERENCE | Meridian Casebook | Use canonical systems/roles/incidents. | No new company facts without documenting them. |
Do this in order
- Overgrant a lab role in a controlled environment.
- Demonstrate the unwanted access.
- Correct it.
- Document the decision/evidence path.
Meridian application
Reuse the actual Meridian artifacts created in prior chapters; the capstone should integrate, not restart.
Create / save
Access incident packet.
Stop / boundary
Use only chapters already completed at this point. Do not solve the incident with knowledge from future chapters.
Completion gate
You can show and explain the difference between policy intent, grant configuration and test evidence.
NEXT → Sequence 297
Operationalized from the verified canonical 00C Master Execution Manual; not a verbatim transcription. Separate chapter mastery packages and applied labs are not created by this migration.