Production .env & Connection URIs in GitHub Actions CI/CD Pipelines: Automated Remediation PRs & Maker-Checker Workflow
Transmitting .env.production through GitHub Actions runner logs and diagnostic artifacts exposes four plaintext credentials at once: the Slack bot token now held as __SE_SLAC_C631C0__, the OpenAI key as __SE_OPEN_158B56__, and the PostgreSQL and Redis passwords as __SE_DB_3D8BD0__ and __SE_DB_10C8E0__. PreflightSweeper and GenericScriptExtractor scan key-value lines and byte streams for fixed-prefix signatures (AKIA, sk-, xoxb-) and high-entropy values, masking only the password segment inside connection URIs so scheme, host, and port survive for debugging. Within a sub-15 ms local in-memory pass, ShadowCaster substitutes deterministic 6-character hex FNV-1a shadow tokens, letting engineers paste manifests into Claude or ChatGPT, or runners send snippets to Anthropic or OpenAI APIs, with zero plaintext egress.
1. Free CLI Workstation Setup
Install the client-side binary to tokenize clipboard inputs and git commits with 0 bytes plaintext credential egress.
2. CI/CD Automated PR Robot
.github/workflows/stackengine.ymlBlock raw secret leaks at the pipeline chokepoint and synthesize deterministic remediation PRs governed by Maker-Checker sign-off.
name: StackEngine Zero-Plaintext-Egress Gate
on: [pull_request]
jobs:
remediate:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Scan & Synthesize Maker-Checker Fix PR
run: |
npm i -g stackengine
stackengine scan .env.production || \
stackengine fix .env.production --ci-pr
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
STACKENGINE_LICENSE_KEY: ${{ secrets.STACKENGINE_LICENSE_KEY }}NODE_ENV=production DATABASE_URL=postgres://master_user:__SE_DB_10C8E0__@prod-db.c7x8y9z0a1b2.us-east-1.rds.amazonaws.com:5432/finance_db REDIS_URL=rediss://:[email protected]:6379 OPENAI_API_KEY=__SE_OPEN_158B56__ SLACK_BOT_TOKEN=__SE_SLAC_C631C0__
1. Token Extraction Audit Matrix (Real-Time In-Memory Map)
| Scalar Target Field | Detection Invariant / Engine | Shadow Token (__SE_*) | Original Value (Sanitized Preview) | Vault State |
|---|---|---|---|---|
| SLACK_BOT_TOKEN (Bot User OAuth) | Preflight Sweeper + Script Scanner | __SE_SLAC_C631C0__ | x******x | 10-min Ephemeral (FIFO) |
| OPENAI_API_KEY (LLM Gateway Key) | Preflight Sweeper + Script Scanner | __SE_OPEN_158B56__ | s******0 | 10-min Ephemeral (FIFO) |
| REDIS_AUTH_PASSWORD (ElastiCache Credential) | Preflight Sweeper + Script Scanner | __SE_DB_3D8BD0__ | R******! | 10-min Ephemeral (FIFO) |
| DB_MASTER_PASSWORD (Sensitive Credential) | Preflight Sweeper + Script Scanner | __SE_DB_10C8E0__ | C******! | 10-min Ephemeral (FIFO) |
2. Shared Repository Policy Spec (.stackengine.yaml)
Commit this file to the root of your repository to enforce zero-plaintext-egress policies across all developer workstations and GitHub Actions CI/CD Pipelines runners:
# Commit to repository root (.stackengine.yaml) — Requires Commercial Team Edition version: "2.0" enforcement: strict-zero-plaintext-egress target_grammars: ["dotenv", "env", "ini", "bash"] customIntentKeys: - "DATABASE_URL" - "REDIS_URL" - "OPENAI_API_KEY" - "SLACK_BOT_TOKEN" pipeline: provider: "github" chokepoint: "ci-runner-gate" fail_on_leak: true ci_remediation: mode: maker-checker-pr attestation: sha256-soc2-evidence branch_prefix: "stackengine/remediation-" auto_merge: false # Strictly enforced: machines draft, humans sign-off
3. Sample SOC 2 Zero-Plaintext-Egress PR Attestation
When executing at your CI/CD runner gate, stackengine fix --ci --provider github generates a verified Pull Request appending this immutable cryptographic seal to satisfy SOC 2 Type II (CC6.1 & CC6.6) audit criteria:
| Security Chokepoint | GitHub Actions CI/CD Pipelines (CI/CD Runner Pipeline Gate) |
| Target Payload | Production .env & Connection URIs (generic) |
| Sanitized Scalars | 4 sensitive credentials locally tokenized into __SE_*__ |
| Plaintext Egress to LLM | 0 bytes (100% Client-Side In-Memory Tokenization) |
| Cryptographic Seal | ed25519:sha256:56c60554580e4632... (Offline Asymmetric Attestation) |
| Governance Boundary | Maker-Checker Protocol (Human Tech Lead Review Required) |
Governance & Maker-Checker Implementation
Because stackengine fix .env.production --ci-pr executes inside the runner, it reads the repository's .stackengine.yaml keys (DATABASE_URL, REDIS_URL, OPENAI_API_KEY, SLACK_BOT_TOKEN) and produces a syntax-validated unified diff instead of editing values in place. InboundGrafter restores non-secret topology identifiers while refactoring the intercepted credentials into cloud secret-store references, then drafts a Maker-Checker PR requiring dual approval, backed by a SHA-256 pre-flight manifest. No plaintext credential leaves the runner boundary, and that dual-approval trail supplies audit evidence for SOC 2 CC6.1, CC6.7, and CC8.1 controls.