Question 860
During an operational security assessment at a public-sector technology agency, the team documents this issue: A release stage references an insecure plain variable for a sensitive token despite an available Key Vault link. 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. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. The action targets the recorded failure (A release stage references an insecure plain variable for a sensitive token despite an available Key Vault link), and is intended to reduce the corresponding risk: Treating arbitrary certificates as linked secrets or exposing secure files broadly can leak deployment material and cause pipeline failures.
Correct verification. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. The measurement or controlled test provides evidence for the issue (A release stage references an insecure plain variable for a sensitive token despite an available Key Vault link) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. The azure pipelines secure files and key vault variable groups implementation and safeguard are still missing.
A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value. It is not the complementary risk control for azure pipelines secure files and key vault variable groups.
Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. The two-part azure pipelines secure files and key vault variable groups control remains unsatisfied.