Unauthorized changes on CIs: who decides retain vs. rollback, and who clears the flag?

RohitJ432388693
Tera Contributor

Hi all,

We're designing our process for handling unauthorized changes detected on CIs, and I'd like the Community's view on how responsibilities should be split. I'm not asking how to clear the Unauthorized checkbox. I'm asking who should own each decision, and in what order.

(Also posted in the ITSM forum, since it spans CMDB and Change Management.)

Our setup

  • When an unauthorized change is detected on a CI, a change record is created with Unauthorized = true (Emergency type).
  • We populate the Support Group field on cmdb_ci. Our intention is for that CI's support group (mostly technical/operations staff) to investigate and decide whether the change should be retained or rolled back.
  • These staff don't normally hold the change_manager role.
  • I recently learned that a user with change_manager can convert an unauthorized change into an emergency change model.

Diagram 1 – Original flow

The Support Group received a task that followed our existing Emergency CHG approval workflow, then approved (keep) or rejected (roll back).

1_original_flow.pngDiagram 1 – Original flow

Diagram 2 – Current flow

We replaced the approval task with a direct "accept / retain or roll back" decision by the Support Group. Rollback tasks go to the person's own Support Group (if a person caused it) or to the Change Implementer's Support Group (if automation caused it), with a fallback Unauthorized Change Support Group. Retained changes close the CHG, and rolled-back changes cancel it.

2_current_flow.pngDiagram 2 – Current flow

Diagram 3 – Proposed revision

The main change is that accepting a change that has already been made and clearing its Unauthorized flag become two separate decisions. The yellow boxes are the points I'm unsure about.

Diagram 3 – Proposed revision (yellow = open questions)Diagram 3 – Proposed revision (yellow = open questions)

My questions

  1. Should the support group's decision be only a technical recommendation, with a separate Change Manager giving formal approval and handling any reclassification?
  2. When should an unauthorized change be converted to an emergency change? Is deciding to keep it enough reason to convert, or should it stay recorded as unauthorized even after it's accepted?
  3. Would you grant change_manager to technical support group members for this, or keep that role separate? What permission or governance issues would granting it create?
  4. If the roles stay separate, where should the handoff to Change Management happen? Who owns the change record, and who owns the investigation and rollback tasks?
  5. For rollback, should we use the original record or a linked remediation change? And what closure outcome should replace the automatic "Cancel CHG" in our flow?
  6. How do you keep unauthorized-change reporting accurate after a record is reclassified?

Example: the support group investigates and says, "This change is technically acceptable; keep it." What should happen next? Who approves it, who changes any flags or the model, and which state should the record move to?

I'd appreciate a recommended sequence of steps and owners for both the retain path and the rollback path, or a pointer to how you've handled this in your own instance.

Thanks,
Rohit

2 REPLIES 2

sanjaygupta
Tera Guru
 

I'd recommend separating the technical decision from the approval process. The CI support group should investigate and recommend whether to retain or roll back the change, while Change Management should own the final decision.

  • Assign the unauthorized change to the Change Management group.

  • Create a Change Task for the CI support group to investigate the change.

  • If the change is retained, document the justification and obtain the required approval.

  • If rollback is required, create a linked remediation change and assign it to the responsible team.

  • Keep the original unauthorized change as an audit record.

  • Document the final decision and validation results before closing the record.

One important point: retaining an unauthorized change does not automatically make it authorized. Keep the audit trail intact and follow your organization's change policy.

You can refer to the ServiceNow documentation on Unauthorized Change Requests for more details.

I'd avoid automating the retain or rollback decision without first defining clear ownership and approval rules.

 
Hope you find this helpful.

JamesB570251289
Tera Contributor

Rohit, you have asked the right question and I would answer the six of them with one rule. Retaining an unauthorized change is a decision about that change, not a reclassification of it. Once you hold to that, most of the diagram sorts itself out.

Take the plain case. A DBA adds memory to a production database at two in the morning to stop an outage. Discovery catches it, the record is raised as unauthorized, and the support group confirms it worked and wants to keep it. Two different things just happened. The support group established a technical fact. Somebody still has to accept the risk of keeping an unreviewed change in production, and that is the decision.  Keep them as two acts by two people, and let the record show who did which.

On conversion, do what your process needs to carry the approvals, but the unauthorized flag does not clear on retention. It is a fact about how the change entered the estate and it stays true after you decide to keep it. Sanjay has this right above and I would put it more strongly: clear the flag and you have rewritten history, and you have also broken your sixth question, because the report can no longer tell a retained unauthorized change from a planned one.

On the role, I would not hand out change manager to make the workflow fit. Give whoever makes retain calls a written, bounded authority instead, for these CI classes, up to this risk, for this period, granted by the change authority, and keep the grant where an auditor can find it, even if your platform only gives you a group and a policy document to hold it in. A retain made under a grant like that is legitimate and you can show why. A retain made because somebody had a role is just a login.

The handoff is the moment a recommendation exists, nothing earlier. Rollback goes through a linked remediation change, and the original closes with a close code that says rolled back, not cancelled, because cancelled says it never happened and it did. Reporting then takes care of itself. Count unauthorized changes by how they entered, and count dispositions seperately, retained, rolled back, open, each with the name of whoever decided.

The test I would put against all three diagrams, and especially the yellow boxes, is this. A year from now, for the database change above, can you say from the record alone who decided to keep it, on what basis, and under what authority. Every box where the answer is "we would have to ask around" is the box that needs a field.