← All insightsSecurity

Securing Pulumi: least privilege and safe defaults

CodeWizard Engineering · 26 November 2025 · 3 min read · Advanced

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

Safe defaults

  • Encrypt secrets in state and config
  • Use least-privilege cloud credentials in CI

Wire it into the pipeline

Preview and deploy with the Pulumi GitHub Action.

yaml
- uses: pulumi/actions@v6
  with: { command: up, stack-name: acme/prod }
  env: { PULUMI_ACCESS_TOKEN: ${{ secrets.PULUMI_ACCESS_TOKEN }} }

Reinforcing habits

  • Keep programs declarative; push logic into tested helpers
  • Use pulumi config set --secret for encrypted config
  • Write unit tests with the language's normal test tools

Want senior help putting Pulumi 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