Skip to content

Harden demo secrets: rotate credentials and ship secure demo env template #3

Description

@johnstel

Problem statement

Active credentials in .env (Entra client secret, GitHub token, session secret) are a critical demo blocker. Current setup needs immediate rotation and a safe handoff pattern for demo/customer environments.

Priority

P0 — critical security blocker before any customer demo.

Acceptance criteria

  • All currently active demo credentials are rotated.
  • .env handling is verified safe (.gitignore + no tracked secrets).
  • A checked-in .env.demo (or .env.template) is added with placeholder values only.
  • Runbook documents secure secret provisioning/rotation flow for demo operators.

Checklist

  • Rotate Entra secret.
  • Rotate GitHub token/PAT.
  • Rotate session secret.
  • Verify no secrets in git history for current branch changes.
  • Add secure demo config template and docs.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

priority:p0Blocking releasesquad:zoeAssigned to Zoe (Security & Governance)type:choreMaintenance, refactoring, cleanup

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions