A sudden configuration change in production broke the city's utility billing API. What software-security control would best support investigation and accountability?
Select an answer to reveal the explanation.
Short Explanation
When billing breaks at 2 a.m., "someone changed something" is not an answer citizens will love. Logged, auditable production changes tell you what moved, who moved it, and when. That trail is how you fix it and keep it from happening again.
Full Explanation
Auditing and logging of software and configuration changes in production supports integrity, non-repudiation of operational actions, and forensic investigation. Change records should capture who authorized and implemented modifications and what differed. Without auditable change history, municipal operators cannot reliably assess or remediate software-driven incidents.