Question 340
A server operations team encounters the following situation: An application service uses a shared account with no identity attribution in its event logs, obscuring which scheduled integration changed a record. Which sustained operational control best reduces the likelihood of this same issue recurring?
Explanation
Correct Answer
This control targets the underlying recurrence risk: Shared credentials eliminate reliable accountability for service operations. It builds validation into the affected workflow and supports the expected recovery result: Test changes identify the correct service principal and timestamp.
Incorrect Answers
This control addresses a different scenario: A server's monitoring agent polls every five minutes and misses short CPU saturation bursts that time out API requests. That event's root mechanism was coarse averages hide short resource bottlenecks. The described incident instead arises from: Shared credentials eliminate reliable accountability for service operations.
This control addresses a different scenario: A file-share migration includes symlinks that resolve outside the approved storage root, unexpectedly exposing sensitive folders to destination users. That event's root mechanism was filesystem link resolution differs from intended share access scope. The described incident instead arises from: Shared credentials eliminate reliable accountability for service operations.
This control addresses a different scenario: A Linux application server needs to transfer reports securely but administrators send them across the network using an unencrypted FTP channel. That event's root mechanism was plaintext transfer exposes sensitive content and credentials in transit. The described incident instead arises from: Shared credentials eliminate reliable accountability for service operations.