DO430 – Securing Kubernetes Clusters with Red Hat Advanced Cluster Security — Lesson 2: Image Scanning, Vulnerabilities, Registries, Policies, and Admission Control

Learning Objectives

• Configure the principal services, objects, workflows, and controls for image scanning, vulnerabilities, and registries.
• Apply security policies and admission control while preserving reviewable technical evidence.
• Recognize and correct the condition where a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect.

Detailed Topics

• image scanning: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• vulnerabilities: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• registries: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• security policies: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• admission control: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.

Instructor Demonstration

The instructor demonstrates image scanning, vulnerabilities, registries, policies, and admission control by tracing architecture, commands, configuration, system messages, and evidence. The walkthrough tests how a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect and explains how to isolate the cause without masking related issues.

Hands-On Exercise

Implement the core workflow for Image Scanning, Vulnerabilities, Registries, Policies, and Admission Control and add the verified result to the RHACS deployment baseline, security policy set, vulnerability evidence, runtime alerts, and response playbook.

1. Confirm scope, versions, access, dependencies, assumptions, and acceptance criteria.
2. Perform the workflow while recording commands, configuration, output, events, and decisions.
3. Test the normal path and one course-specific exception or boundary condition.
4. Retest the correction and document rollback, ownership, and follow-up actions.

Scenario Analysis

• Identify which dependency most strongly influences image scanning in the stated scenario.
• Compare two approaches for security policies and explain the security, reliability, performance, and support trade-offs.
• Decide what evidence must be retained in the RHACS deployment baseline, security policy set, vulnerability evidence, runtime alerts, and response playbook before operational acceptance.

Troubleshooting Guidance

Begin with the first observable difference from the expected result. Check configuration, permissions, sequence, connectivity, and functional behavior separately, then correlate logs, events, commands, metrics, and configuration history. Treat the assumption that a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect as a hypothesis until a reproducible retest confirms the cause.

Validation Checklist

• The required configuration, permissions, sequence, connectivity, and functional behavior were checked and recorded.
• The normal path and a course-specific exception were tested.
• The RHACS deployment baseline, security policy set, vulnerability evidence, runtime alerts, and response playbook links conclusions to commands, configuration, logs, metrics, or other objective evidence.
• Corrective actions, rollback, ownership, and handover notes are complete.

Lesson Outcome

Learners can apply Image Scanning, Vulnerabilities, Registries, Policies, and Admission Control, explain the observed platform behavior, and support the result with a reviewable RHACS deployment baseline, security policy set, vulnerability evidence, runtime alerts, and response playbook.