Red Hat OpenShift Container Platform

Record profiles from workloads

The Security Profiles Operator can record system calls with ProfileRecording objects to create baseline profiles for applications.

When using the log enricher for recording seccomp profiles, verify the log enricher feature is enabled. See Additional resources for more information.

A container with privileged: true security context restraints prevents log-based recording. Privileged containers are not subject to seccomp policies, and log-based recording makes use of a special seccomp profile to record events.

Procedure

Create a project by running the following command:
```
$ oc new-project my-namespace
```
Label the namespace with enable-recording=true by running the following command:
```
$ oc label ns my-namespace spo.x-k8s.io/enable-recording=true
```

Create a ProfileRecording object containing a recorder: logs variable:

apiVersion: security-profiles-operator.x-k8s.io/v1alpha1
kind: ProfileRecording
metadata:
  namespace: my-namespace
  name: test-recording
spec:
  kind: SeccompProfile
  recorder: logs
  podSelector:
    matchLabels:
      app: my-app

Create a workload to record:

apiVersion: v1
kind: Pod
metadata:
  namespace: my-namespace
  name: my-pod
  labels:
    app: my-app
spec:
  securityContext:
    runAsNonRoot: true
    seccompProfile:
      type: RuntimeDefault
  containers:
    - name: nginx
      image: quay.io/security-profiles-operator/test-nginx-unprivileged:1.21
      ports:
        - containerPort: 8080
      securityContext:
        allowPrivilegeEscalation: false
        capabilities:
          drop: [ALL]
    - name: redis
      image: quay.io/security-profiles-operator/redis:6.2.1
      securityContext:
        allowPrivilegeEscalation: false
        capabilities:
          drop: [ALL]

Confirm the pod is in a Running state by entering the following command:

$ oc -n my-namespace get pods

Example output

NAME     READY   STATUS    RESTARTS   AGE
my-pod   2/2     Running   0          18s

Confirm the enricher indicates that it receives audit logs for those containers:

$ oc -n openshift-security-profiles logs --since=1m --selector name=spod -c log-enricher

Example output

I0523 14:19:08.747313  430694 enricher.go:445] log-enricher "msg"="audit" "container"="redis" "executable"="/usr/local/bin/redis-server" "namespace"="my-namespace" "node"="xiyuan-23-5g2q9-worker-eastus2-6rpgf" "pid"=656802 "pod"="my-pod" "syscallID"=0 "syscallName"="read" "timestamp"="1684851548.745:207179" "type"="seccomp"

Verification

Remove the pod:
```
$ oc -n my-namespace delete pod my-pod
```

Confirm the Security Profiles Operator reconciles the two seccomp profiles:

$ oc get seccompprofiles -lspo.x-k8s.io/recording-id=test-recording

Example output for seccomp profile

NAME                   STATUS      AGE
test-recording-nginx   Installed   2m48s
test-recording-redis   Installed   2m48s

Merge per-container profile instances

To reuse one recorded profile when deploying applications with a ReplicaSet or Deployment, configure the Security Profiles Operator to merge per-container profile instances into a single profile instead of keeping a separate profile for each container.

Procedure

Edit a ProfileRecording object to include a mergeStrategy: containers variable:

apiVersion: security-profiles-operator.x-k8s.io/v1alpha1
kind: ProfileRecording
metadata:
  # The name of the Recording is the same as the resulting SeccompProfile CRD
  # after reconciliation.
  name: test-recording
  namespace: my-namespace
spec:
  kind: SeccompProfile
  recorder: logs
  mergeStrategy: containers
  podSelector:
    matchLabels:
      app: sp-record

Label the namespace by running the following command:

$ oc label ns my-namespace security.openshift.io/scc.podSecurityLabelSync=false pod-security.kubernetes.io/enforce=privileged pod-security.kubernetes.io/audit=privileged pod-security.kubernetes.io/warn=privileged --overwrite=true

Create the workload with the following YAML:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deploy
  namespace: my-namespace
spec:
  replicas: 3
  selector:
    matchLabels:
      app: sp-record
  template:
    metadata:
      labels:
        app: sp-record
    spec:
      serviceAccountName: spo-record-sa
      containers:
      - name: nginx-record
        image: quay.io/security-profiles-operator/test-nginx-unprivileged:1.21
        ports:
        - containerPort: 8080

To record the individual profiles, delete the deployment by running the following command:
```
$ oc delete deployment nginx-deploy -n my-namespace
```
To merge the profiles, delete the profile recording by running the following command:
```
$ oc delete profilerecording test-recording -n my-namespace
```

To start the merge operation and generate the results profile, run the following command:

$ oc get seccompprofiles -lspo.x-k8s.io/recording-id=test-recording -n my-namespace

Example output for seccomp profile

NAME                          STATUS       AGE
test-recording-nginx-record   Installed    55s

To view the permissions used by any of the containers, run the following command:
```
$ oc get seccompprofiles test-recording-nginx-record -o yaml
```