Building robust ServiceNow CMDB through data ownership
The second challenge is putting a governance and ownership structure. Think about this. The CMDB is the central repository for all of the data about core data about your organization. The individuals or the team that owns your endpoints is almost always different than the team that owns your networking, that owns— which is different from the team that owns your third-party resources, which is different from the team that owns AWS or Azure or all of those. And you need to assign ownership of that information in the CMDB. No one—no single individual or even team of individuals— can be the authoritative source owner or data owner for all these different kinds of data. It has to be what we call a federated data ownership model. Yes, that means that other parts of the organization are going to have to get involved, and, obviously, everybody really oversubscribed, but in order to make it work, you establish that. Once you establish that, it absolutely becomes the source of authority for the organization as a whole—if you want to find out how many of whatever it is that you have, where it is, what it's doing, how old it is, what's its security posture, what it's costing you, what its risks are. If you have a true executive sponsorship and federated data ownership model, you'll be able to maintain that.
https://www.youtube.com/watch?v=FQ8y6p-bbco