Developers want to push an emergency schema change straight into the production court-records database overnight. What secure-SDLC expectation should govern that change?
Select an answer to reveal the explanation.
Short Explanation
Even “gotta fix it tonight” schema edits need a ticket, eyes on the risk, and a trail. Trusted vibes are not change control—especially on court records.
Full Explanation
Change management within the SDLC requires controlled, reviewed, and recorded changes to production systems, including emergency fixes with expedited but still accountable paths. Untracked or unreviewed schema changes on municipal court data create integrity, availability, and audit failures. Security review scales with risk but is not optional for structural production changes. Logging and approval preserve accountability after the incident window closes.