AInforce

Integrations and data sources

Start with the data you need.

A file review, a live connector, and an inline control require different access. Before an evaluation, agree which source you will use, what it provides, and what remains outside the review.

Discovery files

The DNS analyzer and identity audit tools accept customer-supplied exports. Review the required format and remove unnecessary personal data before uploading. An export-based review is not a live directory connection.

Review the DNS analyzer

Identity and permissions

Identify the directory, scopes, organization attribution, and refresh behavior you need. Confirm a supported connector and its permissions before granting access; do not assume every identity provider has a native integration.

Review the identity export audit

Cost and usage records

Subscription imports and API usage telemetry answer different questions. Confirm provider support, data freshness, currency, and attribution before relying on token-level or department-level reporting.

Review cost reporting scope

Runtime and event workflows

Inspection requires a supported traffic path. SIEM delivery, ticket creation, and custom workflows need a confirmed connection method and agreed configuration; listing a vendor is not proof of a ready-to-use connector.

Review security scope

Confirm your connection before purchase

Bring your provider, required workflow, and security requirements to the discussion. The team can confirm availability and configuration for your intended deployment. This page does not promise a native connector or an entitlement for every vendor or plan.