Configuration management database

And then desired state management gets you there.

And if it sees a drift from, again, very common things you see in the CMDB and data center systems, like this drift management and bringing it back to the state, we've brought those kinds of governance controls.

So I'm talking about all the things that exist today that will help you govern AI or any kind of new onslaught of technology like what we're seeing.

But again, I got to leave some suspense for you to wait till Omnisa 1.

So what happens? People start connecting the information manually.

Someone opens the CMDB, someone else checks the CRM, finance checks the ERP, the service manager looks for the SLA.

Messages start moving between teams.

We have APIs everywhere, but we are still using people as an API.

So for a chief information security officer, dealing with a potentially serious security event that is not just inefficient, it is a risk.

So today I want to ask a, I would say, very provocative question.

Should your CMDB be known about customers' contract revenue and business risk? I think it should, but that does not mean turning the CMDB into another CRM or another ERP.

It means building what I call a business aware CMDB.

Yeah, yeah, that is important, absolutely.

But we also have seen that, uh, customers are using that as a CMDB.

Um, they are using-

Mm-hmm

So the DDI platform was used as a monitoring platform because they pushed, uh, information from, uh, from other stuff into it.

So, um, we were not even aware of that, that customers are using the platforms like they do.

Well, it makes sense because to s- to an extent that's not true for other, like, CMDB type systems.

What's in your systems has to be correct.

It was updated to version one dot zero dot three.

In this version, they added some new features, including automatic registration of dedicated CMDB discovery source for Rasen imports, added an in-application privacy policy page and navigation module, and added support for creating and updating CMDB records to the ServiceNow Identification and Reconciliation engine, helping reduce duplicate CIs and align imported data with CMDB rec- reconciliation rules.

There were some improvements around import set table selection for CI class mapping configuration and transform map field mapping handling to ensure that only mappings from the active transform map are used during CMDB import processing.

And that's what's new from the team at Arasan Inc.

Our second highlight of the episode is from ServiceNow.

And then I move to a governance model and I start with... insisting on somebody's accountable for that API or that AI agent.

By name, in the CMDB, we've got people that are absolutely accountable for what that agent does, what an agent doesn't do.

And when that agent makes a decision and it's not a good decision, for whatever reason, maybe it's a credit risk, you know, rejection that's biased.

When that happens, somebody has to be the accountable party to, not in a punishment kind of way, but just somebody's gotta, you know, feel responsible because the default position will be the CISO.