CI Security Compliance

Enforces GitHub Actions security and compliance for this monorepo. Use when adding third-party actions, handling secrets, defining permissions, and reviewing CI security trade-offs.

camunda 2646e3c 2 files · 1.7 KB Updated

File contents

CI Security and Compliance Skill

Consult docs/monorepo-docs/ci.md before decisions.

Third-Party Action Review Flow

  1. Verify necessity and alternatives.
  2. Check allowlist in docs/monorepo-docs/ci.md (CI Security section).
  3. Present both options:
    • Option A: approved actions only
    • Option B: unapproved candidate with security assessment
  4. If unapproved action is accepted:
    • Add to allowlist in alphabetical order
    • Pin commit SHA in workflow
    • Request DRI review if trustworthiness is unclear

Never silently drop unapproved but relevant options.

Permissions Rules

Start with:

permissions: {}

Add only required scopes.

Secret Management

Vault is mandatory. GitHub Secrets are only for Vault bootstrap values:

  • VAULT_ADDR
  • VAULT_ROLE_ID
  • VAULT_SECRET_ID

Boundaries

  • Always: least privilege, SHA pinning, Vault usage, explicit trade-offs
  • Ask first: OIDC trust boundaries, new deployment targets
  • Never: embedded credentials, broad permissions, untrusted curl | bash

Reference

  • Allowed action guidance: references/approved-actions.md

camunda/camunda/tree/main/.claude/skills/ci-security-compliance commit 2646e3c95b

Frequently asked questions

npx skillmds@latest add camunda/ci-security-compliance