Executing continuous compliance for networks use cases

When you implement the BMC Continuous Compliance for Network Automation solution, you can execute several key use cases. These use cases demonstrate how you can automate the way network changes (such as updating configuration attributes across one or more devices) are tracked and approved, whether the changes are initiated by a BMC Network Automation network engineer (that is, Operations) or by a staff member at the BMC Remedy Service Desk. For a complete discussion of these use cases, see 8903 Continuous compliance for networks use cases.

Use case

Description and references

Operator-initiated changes

This use case enables you to facilitate the tracking of network configuration actions initiated by a BMC Network Automation network engineer, by integrating the execution of BMC Network Automation jobs with BMC Remedy ITSM.

When network configuration changes are implemented, network engineers are required to document these changes in BMC Remedy Change Management. To automate the change tracking and documentation process, a network change request is automatically created in BMC Remedy Change Management when a network user submits a job that requires BMC Remedy approval. After the change request is approved in BMC Remedy, the change is scheduled for execution in BMC Network Automation.

For a user scenario of the operator-initiated change use case, see User scenario for operator-initiated changes for continuous compliance for networks.

BMC Remedy Service Desk-initiated changes

In the IT environment of most large enterprises, general change requests like provisioning a new server are often initiated by the BMC Remedy Service Desk. The network group is required to make a network change to provision the server onto the network. When the Service Desk user submits a network change request through BMC Remedy, it appears in the BMC Network Automation BMC Remedy inbox where the network engineer can create a job to service the request. The job will contain the actions required to support the change request – for example, provisioning the switch port for the server.

For a scenario of the BMC Remedy Service Desk-initiated change use case, see User scenario for BMC Remedy Service Desk initiated changes.

Closed-loop compliance for network configuration policies

BMC Network Automation performs network compliance audits based on security, operational, and regulatory configuration standards. When a compliance violation is detected, BMC Network Automation can automatically open a network incident in BMC Remedy Incident Management and optionally relate a network change request within BMC Remedy Change Management to begin the remediation and tracking process.

For a user scenario of the closed-loop compliance use case, see User scenario for closed-loop compliance for network configuration policies.

Compliance to changes made without prior approval (latent changes)

Network engineers occasionally make one-time changes without requiring any prior approvals. Reconciling jobs is a capability that ensures all changes on the network that occur without prior approval can be tracked in the Change Management system.

Additional use cases

If you have completed an integration with the BMC Atrium CMDB, you can also perform other operational tasks within the context of the business service, such as:

  • Performing network change and configuration tasks with business service context
  • Launching network reports from BMC Atrium Explorer
  • Launching into the BMC Atrium Explorer from device info popup windows

For a complete discussion of these use cases, see BMC Atrium CMDB integration.

For known issues and workarounds, see Known issues and workarounds in continuous compliance for networks.

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