When integrating BMC ProactiveNet with BMC Atrium CMDB

A configuration item (CI) contains four Access Control List (ACL) attributes: two from BMC Atrium CMDB, and two that can be defined locally in BMC ProactiveNet. When BMC ProactiveNet is integrated with BMC Atrium CMDB, it is assumed that BMC Atrium CMDB is used as the source of the CIs.

BMC recommends that you define access control user groups in BMC Atrium CMDB and associate them with the ACLs of the CIs. This makes BMC Atrium CMDB the central source of critical data and it is easy to manage these entities in a central repository. If access control is not designed and maintained properly, it can proliferate beyond control and an enterprise can almost lose track of the reason for creating the access control entities. A poorly designed access control system can also cause security loopholes and compromise access to data and critical parts of the system.

To activate user groups that are defined in BMC Atrium CMDB in BMC ProactiveNet, ensure that the user groups you create in BMC ProactiveNet contain identical names as the user groups in BMC Atrium CMDB.

BMC Atrium CMDB may contain many user groups that are required by other applications but may not be required by BMC ProactiveNet. BMC recommends that you first determine which of the user groups are used in BMC ProactiveNet, and then define them in BMC ProactiveNet accordingly.

When integrating with BMC Atrium CMDB, BMC recommends to use BMC Atrium CMDB as the source of the CIs. If CIs are imported into BMC ProactiveNet from external sources, BMC recommends that you synchronize all the external CIs with BMC Atrium CMDB during configuration, to ensure consistent access. Otherwise, you might have CIs residing in multiple locations which may in turn lead to complications in access management.