Skip to main content

Change Management FAQ

This FAQ answers common questions about Cloudaware Change Management.

How Do I Know Who Made a Change?​

Use CMDB change history where enabled. On many CI detail pages, the CHANGE MANAGEMENT tab shows Changes History, including the timestamp and the user or automation that performed the update (when available).

For background, see History & Audit.

Do I Need to Create Change Tickets for Every Configuration Change?​

No. A common Cloudaware pattern is to:

  • Auto‑record every change for audit and troubleshooting.
  • Auto‑approve low‑risk changes (standard changes) using templates and tight scope.
  • Route only high‑risk changes to approvers/CAB based on policy and CMDB context.

See Approvals.

Can Cloudaware Integrate With ServiceNow Change Requests?​

Yes. Cloudaware can create or update ServiceNow incidents and change requests from Cloudaware events, findings, or workflows, and can keep state synchronized depending on your integration pattern.

See ITSM (ServiceNow) for common patters and the broader ServiceNow ITSM integration guide for setup steps.

How Do I Handle Emergency Changes?​

Use an expedited approval path plus a required retrospective review:

  • Minimize the approval chain (risk acceptance) to restore service quickly.
  • Require evidence after the fact (what changed, why, and validation/rollback).

How Long Is Change History Retained?​

Retention depends on your Cloudaware account configuration and any external systems you export to. For audit requirements, coordinate with your Cloudaware representative on retention and export options, and use scheduled reports or exports where needed.