Lab
Isovalent Network Policy Governance
Share policy ownership between platform and application teams without breaking required traffic.
Separate platform guardrails from application access. Test before enforcement, use Admin and Normal tiers with Pass, narrow access, apply an explicit deny, and roll back safely.
🏛️ Classify risk and ownership
Define which traffic must remain and which team owns each policy decision.
🔍 Assess and observe open access
Identify which open flows are required and which should be blocked.
🧪 Stage, test, and enforce a policy
Protect a required request before you enable ingress default-deny.
🛡️ Add the platform boundary and hand off application access
Keep the required request working while introducing Admin, Normal, and ingressPass.
🎯 Tighten the application allow
Narrow the active application policy to the required workload identity and port.
🚫 Explicitly deny external egress
Block public-internet access for one workload while leaving its internal egress available.
↩️ Roll back a failed revision
Use Timescape to find a policy regression and restore the last known-good application policy.
🏆 Exam: Deliver two policy rollouts
Stage one CNP safely, then complete application and platform policies for a second workload.