Radius360 by BlueRadius
Radius360by BlueRadius
Try it free

Integrations

Connecting Wiz

Wiz is the multi-cloud CSPM Radius360 inherits from. Once connected, open Wiz Issues land in your risk register, mapped to SOC 2, NIST CSF 2.0, CIS v8, ISO 27001, and CMMC controls — with a per-control evidence trail that survives audit.

What this integration does

Wiz finds problems across your cloud surface — misconfigurations, exposed vulnerabilities, over-permissioned identities, leaked secrets, network paths to sensitive data. Radius360's Wiz integration pulls those open Issues every hour and projects them onto the security program views your team already uses.

  • Risk register. Every open Wiz Issue at or above your severity floor becomes a scored risk in the Risk Register, deduped by Wiz issue ID across syncs.
  • Control linkage. Each risk is auto-linked to its mapped controls across SOC 2, NIST CSF, CIS, ISO 27001, and CMMC. The Controls tab on the risk page populates without manual mapping.
  • Per-control evidence. Each sync writes one append-only pass/fail row per control covered by the FINDING_MAP, so the Evidence Vault shows a continuous trail an auditor can sample.
  • Mitigation tasks. Open Wiz Issues without a corresponding tenant task get a task auto-created with severity-derived SLA.

What's not included in v1

The integration covers Issues only. The Wiz cloudResources graph (multi-cloud asset discovery into cmdb_assets) and webhook-based push for new Issues are roadmap follow-ups. Hourly polling currently catches everything within a comfortable detection window.

Prerequisites

  • A Wiz tenant with admin access to Settings → Service Accounts.
  • Your Wiz datacenter prefix from your tenant URL: app.<DC>.wiz.io — e.g. us1, us2, us17, eu1, eu2.

Connect Wiz

  1. 1
    Create a Wiz service account. In Wiz, go to Settings → Service Accounts → Create. Type: Custom Integration. Grant read scopes: at minimum read:issues; read:cloud_resources if you'll enable asset discovery later.
  2. 2
    Copy the credentials. Wiz shows the client_id and client_secret once. Store them somewhere safe; you'll paste them into Radius360 next.
  3. 3
    Identify your datacenter. Look at your Wiz tenant URL: app.us17.wiz.io means your datacenter is us17.
  4. 4
    Connect from Radius360. Go to Integrations in Radius360, find the Wiz card, click Connect. Paste the client ID, client secret, and datacenter prefix. Optionally set a severity floor (default HIGH) — see tuning below.
  5. 5
    Verify the first sync. Click Sync now. Within ~10 seconds the Wiz card flips to active with a count of issues pulled. The Risk Register and Vulnerability Management pages populate immediately after.

What gets created

The Wiz integration produces five artifact types per sync:

Wiz issue typeMaps to controls
Cloud misconfigurationSOC 2 CC6.6, CC7.1 · NIST CSF DE.CM-7, PR.PS-01 · CIS v8 12.x · ISO 27001 A.8.9, A.8.20 · CMMC SC.L2-3.13.1/6
Vulnerability findingSOC 2 CC7.1 · NIST CSF DE.CM-8, ID.RA-01 · CIS v8 7.x · ISO 27001 A.8.8 · CMMC RA.L2-3.11.2
IAM findingSOC 2 CC6.1, CC6.2, CC6.3 · NIST CSF PR.AA-01, PR.AA-05 · CIS v8 5.4, 6.x · ISO 27001 A.5.15, A.8.2
Network exposureSOC 2 CC6.6, CC6.7 · NIST CSF PR.IR-01, DE.CM-1 · CIS v8 12.2, 13.4 · ISO 27001 A.8.20, A.8.22
Secrets detectionSOC 2 CC6.1 · NIST CSF PR.DS-01, PR.AA-01 · CIS v8 3.3 · ISO 27001 A.8.24 · CMMC IA.L2-3.5.10

Severity floor and tuning

Wiz emits issues from INFORMATIONAL through CRITICAL. Pulling everything floods the risk register with low-signal items that drown out the work that matters. The default severity floor of HIGH imports only HIGH and CRITICAL — which for most tenants is the right starting point.

  • HIGH (default): imports HIGH + CRITICAL. The "what should we work on?" view.
  • CRITICAL: top-of-risk-register only. Useful for the very first sync if your Wiz tenant has thousands of open issues — keeps the inbox triageable.
  • MEDIUM: imports MEDIUM through CRITICAL. Use once your team has burned down the high-severity backlog and wants the next tier.
  • LOW: everything except INFORMATIONAL. Defensible only if your security team is at full capacity for cloud posture work.

Each sync hard-caps at 1,000 issues for runtime control. Any tenant approaching that ceiling should narrow the floor.

Troubleshooting

"Wiz integration not configured" — the connect step didn't save. Re-enter the credentials and click Save again before clicking Sync.

"Wiz auth failed (401)" — the client ID / secret pair is wrong, or the service account was deleted in Wiz. Recreate the service account, paste the new credentials.

"Wiz GraphQL error (403)" — the service account doesn't have read:issues. Update its scopes in Wiz and retry.

Issues count is zero but you know there are open issues in Wiz — check the severity floor. Default is HIGH. Lower it to MEDIUM if your highest open severities are MEDIUM.

Connection problems persist? See Integrations troubleshooting for the general decision tree.

PreviousConnecting Microsoft 365Next GRC Assistant