An asset inventory is not a device list

Most asset "inventories" are really device lists: hostname, IP address, serial number, maybe a purchase date. For a stock count, that is enough. For evidence under ISO 27001 or NIS2, it is not. An auditor rarely asks whether a device exists. They ask who is responsible for it, where it stands, what software runs on it, and who accesses it from outside.

An inventory is a web of relationships, not a list

None of those questions is answered by adding one more column. They describe relationships: system to location, system to software, system to person, system to service provider. And those relationships are the first thing that drifts in a hand-maintained table. A machine is moved, an employee changes departments, software is installed after the fact, and the list is the last to know, if it ever finds out.

The most reliable source usually belongs to IT operations

Yet this web already exists in most organizations, just not in the compliance tool. It lives in the client management system that IT operations works with every day. Whoever distributes software, rolls out patches and counts licenses inevitably maintains which system stands at which location and who uses it. That data is current because daily work keeps it current, not because an audit is approaching.

How isidaten taps that source

The ACMP connector pulls exactly this web out of the Aagon Client Management Platform into isidaten: IT systems, software, locations, people and service providers, along with the links between them. Not as a one-off import, but as an ongoing sync through the isidaten agent. Your compliance evidence inherits the data maintenance operations already does, instead of rebuilding it a second time by hand. Two tools from the German-speaking market, Aagon from Soest and isidaten, one data chain without a detour.

How the sync works in detail is shown on the ACMP connector page. What else you can connect is listed in the integrations overview.