nerdexam
Isaca

CRISC · Question #336

An organization allows programmers to change production systems in emergency situations. Which of the following is the BEST control?

The correct answer is A. Implementing an emergency change authorization process. The best control for an organization that allows programmers to change production systems in emergency situations is to implement an emergency change authorization process.

Submitted by luis.pe· Apr 18, 2026Risk Response and Reporting

Question

An organization allows programmers to change production systems in emergency situations. Which of the following is the BEST control?

Options

  • AImplementing an emergency change authorization process
  • BPeriodically reviewing operator logs
  • CLimiting the number of super users
  • DReviewing the programmers' emergency change reports

How the community answered

(29 responses)
  • A
    76% (22)
  • B
    14% (4)
  • C
    3% (1)
  • D
    7% (2)

Why each option

The best control for an organization that allows programmers to change production systems in emergency situations is to implement an emergency change authorization process.

AImplementing an emergency change authorization processCorrect

An emergency change authorization process ensures that even urgent changes follow a documented procedure, requiring explicit approval from appropriate personnel, potentially post-facto, while still documenting the rationale and scope. This control balances the need for rapid resolution with critical oversight, accountability, and proper documentation, minimizing the risk of unauthorized or detrimental changes to production systems.

BPeriodically reviewing operator logs

Periodically reviewing operator logs is a detective control that identifies issues after they have occurred, not a proactive control to ensure proper authorization and control over emergency changes.

CLimiting the number of super users

Limiting the number of super users is a good general security practice for least privilege, but it does not specify the control mechanism for *how* those permitted super users make emergency changes.

DReviewing the programmers' emergency change reports

Reviewing programmers' emergency change reports is a detective control, similar to log review, providing oversight after the fact rather than upfront control and authorization for emergency changes.

Concept tested: Emergency change management control

Source: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r5.pdf

Topics

#Emergency Change Management#Change Control#Authorization Process#Preventive Controls

Community Discussion

No community discussion yet for this question.

Full CRISC Practice