Executing Continuous Compliance for Servers for ServiceNow use cases

When you implement the BMC Continuous Compliance for Servers for ServiceNow solution, you can execute several key child use cases that enable you to automate and maintain continuous compliance in your data center.

Use caseDescription

Operator-initiated change

This use case enables you to facilitate the tracking of infrastructure change actions initiated by a BMC Server Automation operator, by integrating the execution of BMC Server Automation jobs with ServiceNow. 

When operations changes are implemented, operators need to document these changes in their change management system. To automate this change tracking process, a change request is automatically created in ServiceNow when a BMC Server Automation operator submits a job that requires ServiceNow tracking and approval. After the change is approved in ServiceNow, the job is scheduled for execution in BMC Server Automation. 

For a user scenario of the operations-initiated change use case, see Documenting operator-initiated changes for servers for ServiceNow.

Closed-loop compliance for servers for ServiceNow

This use case involves automatically creating incidents and change requests if noncompliant servers are detected, or if deviations from a master server configuration are detected.

Continuous Compliance for Server Automation integrates the remediation of discrepancies and compliance violations in BMC Server Automation to the change management processes facilitated by the ServiceNow IT management system.

Was this page helpful? Yes No Submitting... Thank you