Integrations
Deep vs standard
Every integration in Radius360 is one of two types. Knowing which is which changes what you can expect from it.
The short version
Standard integrations collect evidence for audits. Deep integrations do that plus turn the signal from those systems into governance workflow inside Radius360: scored risks, control mappings, owned mitigation tasks, and incident records.
If an integration is deep, you can build a real risk program around its data. If it is standard, you have audit evidence but not an active feed into your program.
What standard integrations do
Standard integrations are one-way collectors. They:
- Pull configuration, state, or logs from the source system on a schedule (daily by default)
- Store what they find in the Evidence Vault, tagged with the framework controls it satisfies
- Surface it at audit time when an auditor asks "show me proof of X"
What they do not do: generate risks, create tasks, or trigger incidents.
The 18 standard integrations include: Jira, Linear, ServiceNow, KnowBe4, Proofpoint Security Awareness, Qualys VMDR, Rapid7 InsightVM, Elastic Security, Microsoft Entra ID, Microsoft Defender for Endpoint, Microsoft Defender for Cloud, AWS Security Hub, GCP Security Command Center, and Segment.
What deep integrations add
Deep integrations do everything standard integrations do, plus four things:
- Risk generation. Detected issues (unencrypted bucket, user without MFA, lateral movement alert) become scored risks in the register, with AI-suggested impact and likelihood, mapped to the framework controls they touch.
- Task creation. Every generated risk gets an owned mitigation task. Default owner is configurable per integration.
- Incident escalation. High-severity events (critical CVEs on production assets, confirmed ransomware activity, impossible travel on admin accounts) create incident records with timelines and assigned responders.
- Live posture scoring. Deep integrations continuously feed the Security Posture Score, so board reports and executive dashboards reflect today's state, not last month's.
The 23 deep integrations include: Okta, Microsoft 365, Google Workspace, AWS, Google Cloud, Wiz, CrowdStrike, SentinelOne, Splunk, Microsoft Sentinel, Sekoia XDR, Datadog, Tenable, GitHub, Supabase, Vercel, MongoDB Atlas, and the AI-governance trio: Azure OpenAI, OpenAI, and Anthropic.
Side-by-side comparison
| Capability | Standard | Deep |
|---|---|---|
| Evidence collection | Yes | Yes |
| Framework control mapping | Yes | Yes |
| Auto-generated risks | No | Yes |
| Mitigation task creation | No | Yes |
| Incident escalation | No | Yes |
| Live posture score input | No | Yes |
| Sync frequency | Daily by default (6 hr to weekly, configurable) | Daily by default (6 hr to weekly, configurable) |
When each is the right choice
Use a standard integration when you need evidence for an audit but do not need the platform to act on the data. Example: KnowBe4 training completion rates are great audit evidence, but you probably do not need Radius360 to open mitigation tasks when a user is late on their training. Standard is enough.
Use a deep integration when you want changes in the source system to flow into your program without manual intervention. Example: Okta is deep because a new admin account created outside your normal workflow should become a risk automatically, not wait for someone to review an export.
Your first three integrations should be deep
For most clients, the highest-leverage first three integrations are one identity (Okta or Microsoft 365), one cloud (AWS or GCP), and one detection tool (CrowdStrike or Microsoft Sentinel). Those three together cover the majority of real-world risk inputs and light up evidence across SOC 2, ISO 27001, HIPAA, and NIST CSF at once.Licensing and tier limits
Plans and pricing are quoted per engagement. Email support@radius360.co if you want to confirm which integrations your plan includes.
See the billing page for plan details, or the integrations overview for the full list of supported connectors.