Question 830
During an operational security assessment at a public-sector technology agency, the team documents this issue: A token grants permission across an entire subscription although the workflow deploys one app. 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. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. The action targets the recorded failure (A token grants permission across an entire subscription although the workflow deploys one app), and is intended to reduce the corresponding risk: Long-lived secrets in repository settings can be stolen, while excessively permissive federation can authorize untrusted branches.
Correct verification. An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity. The measurement or controlled test provides evidence for the issue (A token grants permission across an entire subscription although the workflow deploys one app) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. It is not the complementary risk control for oidc workload identity federation for GitHub actions.
Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts. This does not supply the required oidc workload identity federation for GitHub actions action-and-control pair.
Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. The paired controls concern oidc workload identity federation for GitHub actions, not that measure.