Low privileged users able to use unconfined seccomp profile via restricted-v2 SCC

Solution Verified - Updated -


  • While creating a pod/deployment with seccompProfile: Unconfined, why the pod's security context is matched against the restricted-v2 SCC given that restricted-v2 prohibits unconfined seccomp profiles?
  • It's evident that the only Seccomp profile allowed is runtime/default
$ oc describe scc restricted-v2 | grep Seccomp
  Allowed Seccomp Profiles:         runtime/default


  • Red Hat OpenShift Container Platform
    • 4.11,4.12

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content