Question 480
A server operations team encounters the following situation: A login script uses a hardcoded password to mount a network share, exposing credentials to every user who can view the deployment package. Which sustained operational control best reduces the likelihood of this same issue recurring?
Explanation
Correct Answer
This control targets the underlying recurrence risk: Plaintext automation credentials create avoidable access and rotation risks. It builds validation into the affected workflow and supports the expected recovery result: The share mounts for authorized accounts with no reusable secret in the script.
Incorrect Answers
This control addresses a different scenario: A Python-style inventory description is pasted into a Bash variable assignment and the script fails because string values contain unquoted spaces. That event's root mechanism was script languages differ in data-type declarations and tokenization. The described incident instead arises from: Plaintext automation credentials create avoidable access and rotation risks.
This control addresses a different scenario: A PowerShell maintenance script targets every server because its inventory filter contains a wildcard where a tested staging group was intended. That event's root mechanism was broad parameter matching expands the change beyond its intended scope. The described incident instead arises from: Plaintext automation credentials create avoidable access and rotation risks.
This control addresses a different scenario: An unattended install script logs full API tokens while debugging a failed bootstrap step, and central logs are accessible to broad staff. That event's root mechanism was verbose automation output can become a secondary secret exposure channel. The described incident instead arises from: Plaintext automation credentials create avoidable access and rotation risks.