Using continuous compliance for servers

Operator-initiated change

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

When operations changes are implemented, operators need to document these changes in BMC Remedy ITSM Change Management. To automate this change tracking process, a change request is automatically created in BMC Remedy ITSM when a BMC BladeLogic operator submits a job that requires BMC Remedy ITSM tracking and approval. Once the change is approved in BMC Remedy ITSM, the job is scheduled for execution in BMC BladeLogic.

For a user scenario of the operations-initiated change use case, see User scenario - Operations-initiated changes.

Closed-loop compliance and audit

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 BladeLogic to the change management processes facilitated by the BMC Remedy ITSM management system.

Incident enrichment

This use case involves automating the addition of information from various relevant sources (such as BMC Atrium Configuration Management Database (CMDB) and BMC BladeLogic servers) to the incident ticket when a server-related incident is detected in BMC Remedy ITSM.