Ticketing compliance policy violations and documenting automatic remediation
Overview
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. The server auditing and server compliance capabilities in BMC BladeLogic Server Automation involve:
- detecting discrepancies between specific servers or component configurations against a baseline server or configuration
- monitoring and detecting compliance violations between specific servers or component configurations against specific rules related to operations, security, and governance
Continuous Compliance for Server Automation integrates the remediation of discrepancies and compliance violations in BMC BladeLogic Server Automation to the change management processes facilitated by BMC Remedy ITSM management system.
Tracking the remediation of compliance violations
This workflow automates the processes associated with remediating compliance violations detected in the configuration of servers and targets managed by the BMC BladeLogic Server Automation system.
Task | Description and reference |
|---|---|
Step 1: Detect violations | Detecting and obtaining compliance violations with the configuration of target servers. To prevent unauthorized or unwanted changes in server configurations, the BMC BladeLogic Server Automation operator runs a Compliance job periodically that compares each server configuration against certain rules and policies (for example, operational or regulatory policies). The Compliance job produces a list of consistent and inconsistent servers. |
Step 2: Create tickets | Creating incidents and change tickets for those inconsistent servers. The BMC BladeLogic Server Automation operator configured the job to send an SNMP alert to notify BMC Atrium Orchestrator of these compliance violations. |
Step 3: Resolve the compliance violation | Once the change tickets are approved in BMC Remedy ITSM, BMC Atrium Orchestrator creates and executes a remediation job in BMC BladeLogic Server Automation. |
Step 4: Verify the change | Finally, BMC Atrium Orchestrator ensures that the discrepancy is resolved and properly tracked in BMC Remedy ITSM. |
For information on this use case, see "Tracking the remediation of compliance violations" in the BMC Continuous Compliance for Server Automation Solution Getting Started Guide.
Tracking remediation of audit discrepancies
This use case automates the processes associated with remediating audit discrepancies detected in the configuration of servers and targets managed by the BMC BladeLogic system.
Task | Description and references |
|---|---|
Step 1: Detect discrepancies | Detect and obtain audit discrepancies or inconsistencies with the configuration of target servers. To ensure that there are no unauthorized changes in server configuration, the BMC BladeLogic Server Automation operator runs an Audit job periodically that compares each server configuration with one or more baseline server configurations. Any detected differences in the configurations are treated as audit discrepancies in BMC BladeLogic Server Automation. |
Step 2: Create tickets | Create a single incident ticket for all the failed target servers in the Audit Job, and creating incidents and change tickets for the audit discrepancies per server. The BMC BladeLogic Server Automation operator configured the job to send an SNMP alert to notify BMC Atrium Orchestrator of these audit discrepancies. |
Step 3: Resolve the audit discrepancies | Once the change tickets are approved in BMC Remedy ITSM, BMC Atrium Orchestrator creates and executes a remediation job in BMC BladeLogic Server Automation. |
Step 4: Verify the change | Finally, BMC Atrium Orchestrator ensures that the discrepancy is resolved and properly tracked in BMC Remedy ITSM. |
For information on this use case, see "Tracking remediation of audit discrepancies" in the BMC Continuous Compliance for Server Automation Solution Getting Started Guide.