User scenario for closed-loop compliance for network configuration policies

This topic describes a scenario where a compliance violation is detected by BMC Network Automation, and it automatically opens a network incident in BMC Remedy Incident Management, and relates a network change request within BMC Remedy Change Management to begin the remediation and tracking process.

The closed-loop compliance for network configuration policies use case is part of the larger Continuous Compliance for Networks use case.

Overview

The following scenario presents a walkthrough of the steps involved in tracking changes initiated by the discovery of a compliance violation by BMC Network Automation. It begins when a BMC Network Automation policy detects a configuration change that is non-compliant with audited rules on a device.

Scenario

• The policy notifies BMC Atrium Orchestrator by way of an SNMP trap to open a BMC Remedy Incident. The Policy Condition is configured to open Incidents on devices supporting the Business Service.Email Services.
  
  
• The Remedy Incident is shown below. The system relates the network CI to the Incident. To begin remediation process, a Change ticket is created and associated with the Incident. The Notes in the Remedy Incident and Change tickets identifies the non-compliant rule.
  
  
  Shown below is the Change ticket created and related to the Incident.
  
  
• A Network Task is automatically created for the Change.
  
  
• The Task is related to the CI that has a compliance violation.
  
  
• When the Remedy user progresses the Change ticket through approvals, the Change ticket is displayed in the BMC Network Automation Remedy Inbox (CRQ000000000127) for servicing.
  
  
• The network engineer clicks on the Change request. A Job window is opened. The Change ID and Task ID are automatically assigned to the job for change tracking. The user adds a Deploy to Active span action to remediate the compliance violation.
  
  
• The network engineer clicks the Report icon to view the Compliance Summary report. The report indicates which rule(s) are in violation.
  
  
• The user clicks on the Failed link to view the violation details in the Different Details Report page.
  
  
• Based on the violation, the user previews the SmartMerge remediation script before submitting the job for execution.
  
  

• The user submits the job. When the job completes, the Remedy Change Task is updated with the completion Status.
• The BMC Remedy user can also verify the remediation by selecting the Launch button (above) on the Task window.
  
  
• The BMC Remedy user selects the Job Details report to get a summary of all devices changed.
  
  
• The BMC Remedy user selects the Job ID, Change ID, or Task ID to view the Job Summary report.
  
  
• The BMC Remedy user sees the Running configuration was modified on the network CI. The Change Details Report is displayed to view the exact change.
  
  The user can see the compliance violation has been resolved. At any time, the BMC Remedy user can launch the Compliance Summary Report from the CMDB CI Relationship Viewer to view current compliance status.