CLOUD + IDENTITYWhat is running, and who can reach it
See infrastructure and identity next to the boundary, controls, and owners.
SOURCES & INTEGRATIONS
Connect the systems that already know part of the truth.
No source system tells the whole story. ComplAI shows what each one contributes — and what it does not.
Direct connector · partner adapter · API · secure file · custom path
Scope the source architecture SOURCE SYSTEMS
Use the systems you already have.
Cloud, identity, security, operations, repositories, SaaS, and data platforms are typical sources. A vendor mark means possible context — not a promised native connector.
CLOUD + IDENTITY
SECURITY + OPERATIONSWhat your tools already flagged
Put operational records next to the requirement they can support.
DATA SYSTEMSWhere the data actually sits
Connect where regulated data lives to the systems and people in scope.
INGESTION PATHS
Use the path your environment can govern.
The right connection depends on the source, the boundary, the host, and your controls. We confirm the path before data moves.
- 01
Direct ComplAI connectors where they are reviewed and enabled.
- 02
Axonius adapter context when that product is part of the architecture.
- 03
Secure API or file exchange with a named owner.
- 04
Custom adapters when you approve the interface and who runs it.
WHAT COMES OUT
Turn what the sources say into work people can review.
What ComplAI collects can inform evidence, control status, SSP and POA&M records, findings, and review queues. On its own it is not an authorization or assessment decision.
EVIDENCEKeep the source attached
Keep the source, time, scope, owner, and requirement with the record.
CHANGESee drift and impact
See which controls, records, and people a change may affect.
REVIEWGive someone the full picture
So they can accept, fix, escalate, or look closer.
NEXT DECISION
Start with the systems already in the boundary.
We’ll map owners, collection paths, and what each source can actually support.