Integrations

Native where it counts. Webhooks where it does not.

PolicyCortex reads configuration and events from the cloud providers most defense and regulated organizations already run: Azure, AWS, and GCP, with Azure Government, AWS GovCloud (US) and GCC High supported, through their own APIs, and writes approved remediation through their own primitives. Findings, tickets, notifications, and evidence exports move through the security, GRC, notification, and SIEM tools listed below.

Cloud providers

Native integration means consuming events directly and applying remediation through the provider's own primitives, not screen-scraping consoles.

Cloud providers3 providers
ProviderWhat is readWhat is written
AWS, with AWS GovCloud (US) supportedResource configuration and events, through the provider APIs, read only.Approved remediation through the provider's own primitives, with a rollback identifier where a restore exists and rollback is enabled for the action.
Azure, with Azure Government and GCC High supportedResource configuration and events, through the provider APIs, read only.Approved remediation through the provider's own primitives, with a rollback identifier where a restore exists and rollback is enabled for the action.
GCP, including Assured WorkloadsResource configuration and events, through the provider APIs, read only.Approved remediation through the provider's own primitives, with a rollback identifier where a restore exists and rollback is enabled for the action.

AWS and Azure boundaries are supported for ATO packaging; GCP support covers governance, remediation, and control-linked evidence, not an ATO workflow.

Security posture

Posture platforms already in the environment feed the evidence record; no write-back is on record.

Security posture5 providers
ProviderWhat is readWhat is written
Microsoft Defender for CloudFindings.None on record
AWS Security HubFindings.None on record
GCP Security Command CenterFindings.None on record
WizFindings.None on record
PrismaFindings.None on record

Ticketing and GRC

Work items go to the ticketing system your teams already watch; evidence can be imported into an existing GRC tool.

Ticketing and GRC6 providers
ProviderWhat is readWhat is written
ServiceNow ITSM and GRCNone on recordTickets.
JiraNone on recordTickets.
LinearNone on recordNo ticketing integration today.
Azure DevOpsNone on recordNo ticketing integration today.
DrataNone on recordEvidence, imported into the GRC tool.
VantaNone on recordEvidence, imported into the GRC tool.

Notifications

Outbound only.

Notifications5 providers
ProviderWhat is readWhat is written
SlackNone on recordNotifications.
Microsoft TeamsNone on recordNotifications.
PagerDutyNone on recordNotifications.
EmailNone on recordNotifications.
WebhookNone on recordNotifications, as events.

AI and ML platforms

The AI estate inventory enumerates every model and agent in scope with identities, channels, egress paths, and binding envelope, as of a timestamp the customer chooses.

AI and ML platforms7 providers
ProviderWhat is readWhat is written
Azure OpenAIModels and agents in scope, for the AI estate inventory.None on record
AWS BedrockModels and agents in scope, for the AI estate inventory.None on record
GCP Vertex AIModels and agents in scope, for the AI estate inventory.None on record
OpenAI APIModels and agents in scope, for the AI estate inventory.None on record
AnthropicModels and agents in scope, for the AI estate inventory.None on record
Hugging FaceModels and agents in scope, for the AI estate inventory.None on record
MLflowModels and agents in scope, for the AI estate inventory.None on record

Audit and evidence

Packages export as OSCAL 1.1.2 with SSP, SAR, POA&M, the eMASS POA&M worksheet, POA&M XML, and evidence indexes generated from one implementation record.

Audit and evidence6 providers
ProviderWhat is readWhat is written
OSCAL 1.1.2None on recordSSP, SAR, POA&M, and evidence indexes.
eMASSNone on recordThe eMASS POA&M worksheet. POA&M XML uses the PolicyCortex schema; its import into eMASS has not been verified.
SplunkNone on recordChained records, as events.
Microsoft SentinelNone on recordChained records, as events.
DatadogNone on recordChained records, as events.
Custom SIEM via webhookNone on recordChained records, as events.
Intelligence headquarters perimeter canopy at duskYOUR BOUNDARY · CUSTOMER-OPERATED INSTALLATION
Available in your own Azure subscription or Kubernetes cluster, delivered with our engineers
Cryptographic cipher rotor assemblySHA3-256 EVIDENCE STREAM · OFFLINE VERIFIER
Every exported package carries a hash-chained stream your assessor verifies offline

Missing one? Tell us what you run.