How to sync CMDB/Asset structure with IRM Entity mapping structure?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I have a client requirement where the CMDB Asset structure (CIs, hierarchy, relationships) needs to stay in sync with the IRM Entity framework.
In simple terms, we want the Entities in IRM to automatically reflect whatever is present in the CMDB—including which items are in scope and how they are grouped—without manually creating or updating Entities.
I understand that IRM Entities usually reference CMDB records through Entity Types + Entity Filters, not modify them.
Also, I’ve seen suggestions to use CMDB Query Builder queries tagged for GRC scoping to dynamically pull CIs into Entity Types.
What I need help with:
- Best practices for mapping CMDB tables/relationships to IRM Entity Types
- Ensuring Entities auto‑update when CIs change (added/retired)
- Whether tools like Crowe IRM Entity Manager help in syncing CMDB → IRM dependencies automatically
- Any recommended approach to keep both models aligned without custom heavy scripting
If you’ve implemented CMDB‑to‑Entity synchronization or dynamic scoping, please share how you approached it.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
AFAIR this feature is on the roadmap so will be coming soon OOTB.
The key challenge is that the CMDB is more of a matrix than a downtream/upstream hierarchy like entities tend to be. In earlier discussion with SN product team I mentioned about uncles, and cousins rather than simple parent-children relationships.
Since you ask for a setup without scripting, I can mention that for one client we set up a flow where we used the CMDB dependencies for few classes to be the trigger for defining the related entity as downstream.
So if we setup:
1- CI Class A as entity type A and CI Class B as entity type B;
2- then "if CI XY from Class A "depends on" CI XZ from Class B",
3- then Entity XY is upstream to Entity XZ
It does mean that you have to first agree on which CI classes & relationships are considered upstream from others and understand the potential limitations of this model to fully replicate the CMDB across GRC.
