← All insightsSecurity

Securing Red Hat OpenShift: least privilege and safe defaults

CodeWizard Engineering · 29 July 2025 · 3 min read · Advanced

Security with Red Hat OpenShift is mostly correct, boring defaults applied consistently. Here is the short list that removes most of the risk.

Safe defaults

  • Keep the restrictive default SCC; avoid privileged pods
  • Use built-in OAuth and per-project RBAC

Wire it into the pipeline

Build from source in-cluster with a BuildConfig.

yaml
apiVersion: build.openshift.io/v1
kind: BuildConfig
metadata: { name: web }
spec:
  source: { git: { uri: https://github.com/acme/web } }
  strategy: { type: Docker }
  output: { to: { kind: ImageStreamTag, name: 'web:latest' } }

Reinforcing habits

  • Work with SCCs - run non-root and drop capabilities
  • Use ImageStreams + DeploymentConfigs/Deployments for rollouts
  • Adopt OpenShift Pipelines (Tekton) for CI/CD

Want senior help putting Red Hat OpenShift to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult