Secret Leak Response

Objective

Practice the correct response when a secret is accidentally committed.

Scenario

An example API token appears in a committed .env file. Do not use a real token.

Deliverables

• Written response checklist.
• Fixed .gitignore.
• Commit removing the sample secret from current files.
• Short explanation of why rotation is still required for real secrets.

Success Criteria

• The project states that real exposed credentials must be revoked or rotated.
• The repository includes prevention steps for the future.