Question 230
During an operational security assessment at a public-sector technology agency, the team documents this issue: A team assumes deleting a tag eliminates every historical copy of a committed password. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Which TWO responses form a sound implementation-and-verification pair for this issue? (Select TWO.)
Explanation
Correct Answers
Correct corrective action. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. The action targets the recorded failure (A team assumes deleting a tag eliminates every historical copy of a committed password), and is intended to reduce the corresponding risk: Deleting a leaked credential in a new commit does not remove the secret from previous history or revoke its validity.
Correct verification. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value. The measurement or controlled test provides evidence for the issue (A team assumes deleting a tag eliminates every historical copy of a committed password) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants. It is not the complementary risk control for credential removal from git history.
Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The credential removal from git history implementation and safeguard are still missing.
Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures. The two-part credential removal from git history control remains unsatisfied.