Integrations

Integrations — connect your security stack

14 native connectors pull configuration, identity, endpoint, and vulnerability data from the systems your controls already run on — and attach each artifact to the control it proves. No more quarterly screenshot drills.

Start free Book a demo

Native connectors

Grouped by what they cover. Each connector maps its data to the controls it satisfies.

Cloud configuration

AWS ConfigResource configuration state and conformance-pack findings across your AWS accounts.
Google Cloud (SCC)Security Command Center findings and asset inventory from Google Cloud.
Microsoft AzureResource configuration and Microsoft Defender for Cloud posture findings.

Identity & access

OktaUsers, groups, MFA enrollment, and access logs for access-review controls.
Google WorkspaceUser and group membership and 2-step verification status.

Endpoint & EDR

CrowdStrike FalconEndpoint agent health, coverage, and detection posture.
Microsoft DefenderEndpoint protection status and alert posture.
Jamf ProApple fleet inventory and device-compliance posture.

Vulnerability scanning

QualysVulnerability scan results and host findings.
Rapid7InsightVM scan results and remediation state.
TenableNessus / Tenable.io vulnerability findings.
TrustwaveManaged scanning and ASV scan results.

App & dependency

GitHub (Dependabot)Dependency alerts and code-scanning results from your repositories.
SnykOpen-source, container, and infrastructure-as-code vulnerabilities.

How evidence sync works

01Connect a system once with least-privilege, read-only credentials.

02SentinelPanda syncs on a schedule you set, or on demand, pulling the relevant evidence.

03Each artifact is timestamped and attached to the control(s) it supports.

04Cross-framework mapping credits the same evidence across every framework it satisfies.

Credentials encrypted with AES-256-GCM at rest. Decrypted only at sync time.

Integrations — frequently asked questions

How are integration credentials secured?

Integration credentials are encrypted with AES-256-GCM at rest and decrypted only inside the sync worker, at the moment a sync runs.

Can I sync on a schedule or on demand?

Both — connectors sync on a schedule you set and can also be triggered on demand, with each artifact timestamped and attached to the control it supports.

What if the tool I use isn’t listed?

You can attach evidence manually or via the API/webhooks, so a control is never blocked on a connector. The native connector list expands over time.

Which frameworks does the evidence count toward?

Because controls are cross-mapped, a single piece of evidence can satisfy the equivalent control across PCI DSS, ISO 27001, SOC 2, NIST CSF and more.