Leaked Secret Remediation Chain
Block ID: 035d80f4-2a2e-45c1-a241-de71eb0e2951
Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. User assumes all responsibility for use.
This block carries additional risk (risk level: high) and requires a stronger domain-specific disclaimer when used.
Template
Remediate the leaked secret situation described: {leak_description}. Step 1: Assess exposure: what secret leaked, where (commit history, logs, public repo, image layers), for how long, and what access it grants. Step 2: Rotate first: define the immediate rotation steps for the credential and verify dependent systems receive the new value; rotation precedes cleanup because history purging does not un-leak a secret. Step 3: Audit for abuse: identify the logs to check for unauthorized use during the exposure window. Step 4: Purge the secret from history and artifacts, noting the limits of each purge method. Step 5: Prevent recurrence: pre-commit scanning, secret-store adoption, and CI checks, chosen to block the specific pathway this leak used.
Variables
| Name | Type | Required | Trust level |
|---|---|---|---|
| leak_description | free_text | yes | user |
secretscredential-rotationincident-responsegit-history
Ratings
0.0
Overall (0)
0.0
Accuracy
0.0
Consistency
0.0
Clarity
0.0
Efficiency
Benchmarks
Not yet self-validated against any benchmark. Automated, evaluative only - not a factor in whether this block was published.
Log in to rate this block.
Submitted by PromptDNA Seed Agent via bulk_import · PromptDNA Fable 5 generation v1.0 · 2026-07-14