Radius360 by BlueRadius
Radius360by BlueRadius
Try it free

Getting started

Quick start

Thirty minutes. By the end, you'll have a populated risk register, a connected integration, an in-progress framework assessment, and a first draft of a board report.

Before you start

You'll need a Radius360 account, if you don't have one yet, start a free 7-day trial. No credit card required.

You'll also want admin credentials for at least one of the tools you want to connect. For the quick start we recommend Okta, Microsoft 365, or AWS. Any one of them gives you evidence across several frameworks immediately.

Your trial includes Program features

During your 7-day trial you have access to everything on the Program plan: deep integrations, the GRC Assistant, board reports, and multi-client support. Use the time to explore the full platform, not just the basics.

1. Onboard your first client

Open Client Management → Onboard Client. The onboarding wizard walks you through six short steps: client info (name, industry, size), frameworks, starter risks, starter policies, review, and who on your team works the client. When you finish, Radius360 seeds:

  • Starter risks matched to the frameworks you picked, spanning AI, compliance, data security, identity, and operations
  • Every framework you select (SOC 2, ISO 27001, NIST CSF, HIPAA, etc.), activated with its full control library
  • Eight starter policies, saved as drafts, covering information security, access control, incident response, and more
The wizard's starter content is a foundation, not a final deliverable. Every risk, policy, and control is editable. Think of it as a one-minute head start, not a one-size-fits-all template.

2. Connect a deep integration

Go to Integrations and pick one of the 23 deep integrations. These do more than collect evidence, they auto-generate mapped risks and keep your posture current as the underlying environment changes.

  1. 1
    Pick your integration. For a first one, we recommend Okta (identity), Microsoft 365 (productivity + identity), or AWS (cloud). Each one lights up evidence across SOC 2, ISO 27001, HIPAA, and NIST CSF simultaneously.
  2. 2
    Authenticate. Radius360 uses OAuth or service-account credentials depending on the integration. No firewall changes, no agent install.
  3. 3
    Wait for the first sync. Most integrations complete their first sync in 2–5 minutes. You'll see evidence appearing in the vault and new risks generated from detected misconfigurations (e.g., users without MFA, unencrypted S3 buckets, unreviewed admin access).

Detection stays with your tools

Radius360 doesn't replace your SIEM, XDR, or EDR. It reads their output and turns it into governance artifacts, a scored risk in your register, mapped to the controls it touches, with an owned mitigation task. Detection runs on your existing stack. Governance runs in Radius360.

3. Run a framework assessment

Go to Compliance (the Controls tab) and open any framework you selected during onboarding. You'll see every control, its current evidence status, and the gaps the system has detected so far.

For each unmet control, Radius360 shows you the specific piece of evidence missing and which integration (or manual upload) could satisfy it. Click a control to see its cross-framework mappings, in most cases the same evidence satisfies controls across SOC 2, ISO 27001, and NIST CSF simultaneously, so you're not doing the work three times.

4. Open your board report

Go to Reports and click Generate Board Report. Pick a period (weekly, monthly, or quarterly) and Radius360 drafts a board-ready report from your live data: posture score and trend, top risks, framework progress, integration health, what changed in the period, and prioritized actions for the next 30 days.

Review the draft. Radius360 writes for a non-technical reader, but the tone and emphasis should match your company. Regenerate if you want a different draft, copy it to the clipboard, or download it as a PDF when you are ready to send.

The report improves as you populate the tenant

A first-week report with one integration connected and a few risks looks thinner than a report a month later after you have connected three integrations, run a framework assessment, and closed a few risks. Come back to the report as the underlying data fills in.

5. Try the GRC Assistant

Open the GRC Assistant and ask questions in plain English:

  • "What's our MFA coverage across all clients?"
  • "Which risks are past their SLA?"
  • "Draft a data retention policy for a healthcare client."
  • "Summarize what changed in our security posture this week."

The assistant reads your live data, risks, policies, evidence, framework state, and answers from that. It cites specific controls when relevant, and it will tell you when it doesn't have enough data to answer rather than making something up.

When the assistant drafts policy-shaped output, save it to your Policy Library with one click. No copy-paste.

What next

After the quick start, useful next reads:

PreviousIntroductionNext Key concepts