Docker & Container Security Technology Syllabus

• Explain Container isolation model and threat surface using current Docker terminology and connect it to the Docker & Container Security architecture
• Practice: map the components, identities, data paths and trust boundaries for Container isolation model and threat surface
• Evidence: produce an annotated architecture diagram and explain the validation result

• Explain Docker daemon, socket and host hardening using current Docker terminology and connect it to the Docker & Container Security architecture
• Practice: compare a baseline design with a risky or incomplete design for Docker daemon, socket and host hardening
• Evidence: produce a design decision record and explain the validation result

• Explain Dockerfile security and minimal base images using current Docker terminology and connect it to the Docker & Container Security architecture
• Practice: trace one permitted and one denied access decision for Dockerfile security and minimal base images
• Evidence: produce an access-flow worksheet and explain the validation result

• Explain Image registries, provenance and trust using current Docker terminology and connect it to the Docker & Container Security architecture
• Practice: plan a least-privilege configuration and a safe rollout sequence for Image registries, provenance and trust
• Evidence: produce a change plan with rollback steps and explain the validation result

• Explain Vulnerability scanning and Docker Scout using current Docker terminology and connect it to the Docker & Container Security architecture
• Practice: review policy order, dependencies, exceptions and rollback conditions for Vulnerability scanning and Docker Scout
• Evidence: produce a policy review checklist and explain the validation result

• Explain Linux capabilities, seccomp and AppArmor using current Docker terminology and connect it to the Docker & Container Security architecture
• Practice: configure or assess the control with secure defaults for Linux capabilities, seccomp and AppArmor
• Evidence: produce a configuration evidence sheet and explain the validation result

• Explain Rootless containers and user namespaces using current Docker terminology and connect it to the Docker & Container Security architecture
• Practice: test expected and unexpected behavior against explicit pass criteria for Rootless containers and user namespaces
• Evidence: produce a pass/fail validation record and explain the validation result

• Explain Container networking and exposure controls using current Docker terminology and connect it to the Docker & Container Security architecture
• Practice: locate the relevant telemetry and build an investigation timeline for Container networking and exposure controls
• Evidence: produce an investigation timeline and explain the validation result

• Explain Secrets, configs and sensitive data using current Docker terminology and connect it to the Docker & Container Security architecture
• Practice: triage a realistic finding and separate risk from expected activity for Secrets, configs and sensitive data
• Evidence: produce a triage note with severity rationale and explain the validation result

• Explain Logging, monitoring and runtime detection using current Docker terminology and connect it to the Docker & Container Security architecture
• Practice: tune a noisy control without removing required visibility for Logging, monitoring and runtime detection
• Evidence: produce a tuning record with before-and-after evidence and explain the validation result

• Explain CI/CD security gates and exception handling using current Docker terminology and connect it to the Docker & Container Security architecture
• Practice: troubleshoot a production-style failure using an evidence-first workflow for CI/CD security gates and exception handling
• Evidence: produce a troubleshooting runbook entry and explain the validation result

• Explain Hardened container delivery capstone using current Docker terminology and connect it to the Docker & Container Security architecture
• Practice: combine design, validation, operations and handover in the capstone for Hardened container delivery capstone
• Evidence: produce a concise capstone handover and portfolio artifact and explain the validation result

This is a published technology learning blueprint. Contact Techclick to confirm current trainer availability, delivery format, schedule, lab access and pricing before making a decision.

No. Vendor certification programmes and exam blueprints change independently. This syllabus focuses on practical technology skills and official documentation.

Yes, subject to trainer and lab availability. Share your existing environment, target outcomes and preferred timeline for a scoped discussion.