Skip to content
ZajLibrary
prod e051e98
Browse

1 · Pre-flight security hygiene (P0)

TL;DR

Section titled “TL;DR”

Objective — rotate every test-mode key and staging password that touched a chat or log, vault plaintext credentials, re-scope over-privileged service accounts, and record the audit, so no convenience credential from iteration becomes a liability the moment real traffic arrives.

Background

Section titled “Background”

Never skip this. Every production deploy starts here. Staging and production are different security contexts: credentials that were convenient during iteration become liabilities the moment real traffic arrives.

Steps

Section titled “Steps”

1. Rotate every test-mode payment key

Section titled “1. Rotate every test-mode payment key”

Roll each key that appeared in chat or log history, then revoke the old value at the source.

  1. Roll each test-mode key in the gateway dashboard, update the staging environment with the new value, and revoke the old key.

    • ✅ Every test-mode key is rotated and the old keys are revoked at the source.

2. Rotate all staging-side passwords

Section titled “2. Rotate all staging-side passwords”

SMTP, database, and hosting-panel credentials — and any password that lived in a plaintext file.

  1. Rotate the staging-side passwords — SMTP, database, hosting-panel, and anything that lived in a plaintext file.

    • ✅ All staging-side passwords are rotated.

3. Migrate plaintext credentials into a real secrets manager

Section titled “3. Migrate plaintext credentials into a real secrets manager”

Move every secret into the appropriate vault, then replace the plaintext store with pointers (or delete it and .gitignore it).

  1. Move every secret into the appropriate vault, then replace the plaintext store with pointers — or delete it and .gitignore it.

    • ✅ Plaintext credentials are replaced with vault pointers (or deleted + gitignored).

4. Re-scope over-privileged service accounts

Section titled “4. Re-scope over-privileged service accounts”

Narrow each API key and the deploy user to the minimum permissions they actually need.

  1. Narrow each API key and the deploy user — payments, analytics, error tracking — to the minimum permissions they actually need.

    • ✅ Every service-account scope is narrowed to the minimum.

5. Record the audit

Section titled “5. Record the audit”

Capture what changed so the rotation is auditable later. An agent can draft this record from your notes.

  1. Write the audit summary in your customizations log — what was rotated, what moved to the vault, what was re-scoped, and any accepted exceptions with the reason.

    • ✅ The audit summary is committed.

Checklist

Section titled “Checklist”

Do not mark this step done until every box below is checked.

  • 👤 Test-mode keys rotated — every test-mode payment key rolled; old keys revoked at the source.
  • 👤 Staging passwords rotated — SMTP, database, and hosting-panel credentials all changed.
  • 👤 Credentials vaulted — plaintext secrets replaced with vault pointers (or deleted + gitignored).
  • 👤 Scopes minimized — every API key and the deploy user narrowed to minimum permissions.
  • 🔀 Audit recorded — rotation/move/re-scope summary committed to the customizations log.

Release & deploy