Integrations
Each integration is a governed, read-only channel with declared scope. It contributes source evidence for reconciliation into the Explainable Intelligent CMDB. It is not certification, real-time sync, automatic merge, approval, or write-back.
Collect users, groups, computers, OUs, and group-membership evidence over LDAPS as governed source observations for reconciliation and change evidence.
Bring in asset, ownership, contract, warranty, and CMDB records as a reviewed migration and reconciliation source. Promotion into the official registry stays human-reviewed.
Read ticket, approval/status, configuration-item, relationship, and software records as governed evidence for reconciliation and change-authorization context.
Read Action Request change and CMDB instance records as governed change-authorization evidence. ORAVUNO does not make approvals from connector data.
Collect network node and configuration inventory with change evidence as governed source observations, with source and scope preserved.
Collect firewall device, rule, object, and revision evidence with provenance for network change intelligence. Requested-versus-delivered access stays review evidence, not approval.
Collect virtualization inventory such as hosts and virtual machines with change evidence as governed source observations.
Collect host and vulnerability findings as governed security-context evidence, with the reporting source and scope preserved.
Collect device, installed-software, vulnerability, and security-posture evidence as governed source observations.
Collect device, subnet, CVE, and model-breach evidence as governed security context. This is evidence only. ORAVUNO does not act on it automatically.
Collect discovery evidence such as assets, services, software, and certificates as governed observations for careful reconciliation.
Collect host, access/security-event, and software evidence through governed read-only queries. Used as corroborating evidence, not as an authoritative record.
For a source not listed, ORAVUNO can work with customer-approved structured imports or a purpose-built adapter while keeping source, scope, collection status, and provenance explicit.
Discuss an integration