anchor.diff:  
   [WARNING]
   ====
  -This SCC allows host access to namespaces, file systems, and PIDS. It should only be used by trusted pods. Grant with caution.
  +This SCC allows host access to namespaces, file systems, and PIDs. It should only be used by trusted pods. Grant with caution.
   ====
   
   |`hostmount-anyuid`
  
positive.code: 
  [NOTE]
  ====
  Setting `privileged: true` in the pod specification does not select the `privileged` SCC. Setting `privileged: true` in the pod specification matches on the `allowPrivilegedContainer` field of an SCC.
  ====
  endif::[]
  
  |`restricted`
  |Denies access to all host features and requires pods to be run with a UID, and SELinux context that are allocated to the namespace.  This is the most restrictive SCC and it is used by default for authenticated users.
  
  The `restricted` SCC:
  
  
negative.code: 
  [NOTE]
  ====
  You can drop all capabilites from containers by setting the `requiredDropCapabilities` parameter to `ALL`.
  ====
  
  [id="authorization-SCC-strategies_{context}"]
  