# Rotate an exposed credential even after the text is removed

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Rotate an exposed credential even after the text is removed

ID: MHC-D-RESEARCH-0665 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/rotate-an-exposed-credential-even-after-the-text-is-removed

Deletion changes visibility; rotation changes validity.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A real secret appeared in a commit, agent log or external tool call and has now been deleted.

### Avoid when

- Credential-response sequence varies by provider; follow the relevant security procedure instead of improvising rotation order.

### Explanation

Treat a genuinely exposed credential as potentially compromised. Follow the provider's incident procedure: rotate or replace it, revoke the old value as appropriate, inspect relevant use and remove it from history or logs where required. Do not assume rewriting the commit makes the credential safe again.

### Example

A token committed for two minutes is rotated even after the commit is amended because the old value may already have been copied.

### Check

The leaked value no longer authorizes access and the leakage path has a corrective action.

### Limits

- Credential-response sequence varies by provider; follow the relevant security procedure instead of improvising rotation order.

### Evidence and sources

- supports: GitHub secret-security guidance recommends revoking or rotating real credentials that were exposed rather than merely removing the text from a commit. — RS-6A6591C8A0A9FDD9. Exact rotation order and incident response depend on the credential provider and exposure scope. (Secret leakage response)
- RS-6A6591C8A0A9FDD9: Secret leakage risks — https://docs.github.com/en/code-security/concepts/secret-security/secret-leakage-risks

No review details supplied.
