The execution layer that turns risks into tracked work
Playbook Library
27 structured runbooks covering the remediations and program work that repeat. Apply a playbook to an open risk so its tasks inherit the risk SLA, or run it as scheduled program work on cadence.
Why it matters
Built for outcomes, not checkboxes
27 Structured Runbooks
MFA gap, access review, patch CVEs, cloud config hardening, SaaS baseline, JML lifecycle, IR activation, breach notification, and 19 more. Built from CISO practice, not marketing copy.
Risk-Triggered or Scheduled
Apply a playbook to an open risk so its tasks inherit the risk SLA and priority, or run it standalone on calendar cadence (quarterly access review, annual DR tabletop).
Tasks with Owners and SLAs
Each playbook step becomes a mitigation task with a due date, priority, and verification criteria. Integration hints flag steps that automate (Okta, AWS, Tenable).
MSSP Baseline Cascading
Configure your practice baseline once with default playbooks. Applying to a new client spins up 80% of the program in 60 seconds.
How it works
Everything in one place, nothing to bolt on
AI Triage on Fresh Risks
A consolidated AI triage dialog opens when a new risk is created and suggests the best playbook to apply plus the relevant framework controls to link. High-confidence picks pre-checked; you approve or skip.
- AI proposes one primary playbook + one alternative per risk
- High-confidence suggestions default-checked
- Control suggestions and playbook suggestion in one pass
- AI suggests, human decides; nothing auto-applied
Library Coverage
Library spans identity, access, data protection, network, endpoint, operations, incident response, BCP/DR, vendor risk, governance, and compliance evidence. Each runbook includes prerequisites, deliverables, and a 'use when' indicator so it's obvious whether it fits.
- Identity + access: MFA gap, quarterly access review, PAM rollout, JML lifecycle
- Vulnerability and endpoint: patch critical CVEs, EDR deployment, cloud config hardening
- Incident response: IR activation, phishing incident, ransomware readiness, breach notification
- Compliance and governance: SOC 2 evidence refresh, HIPAA SRA, cyber insurance renewal, AI use-case risk
Scheduled vs Reactive Classification
Every playbook carries a cadence label: risk-triggered playbooks apply to an open risk; scheduled playbooks run on calendar cadence as standalone program work. The Library filters both ways so practitioners pick the right path without thinking about it.
- Risk-triggered: apply to open risk, tasks inherit SLA + priority
- Scheduled: run on cadence, spawns standalone program tasks
- 9 scheduled runbooks (quarterly access review, annual SRA, DR tabletop, etc.)
- 18 reactive runbooks (patch CVE, IR activation, vendor onboarding, etc.)
Tasks With Verification Criteria
Applying a playbook spawns a mitigation task per step with owner assignment, due date from the risk SLA, and verification criteria. Integration hints (e.g., 'auto · okta', 'auto · aws') flag steps that can automate once the integration is connected.
- One task per playbook step, tracked to close
- Priority and due date inherited from the source risk
- Verification criteria on each step
- Automation hints per step when an integration matches
Get started today
Run your security program, not just your tools
Whether you're the security lead holding it together in-house without a CISO, or a vCISO, consultant, or MSSP running client programs, Radius360 turns your stack into decisions your board and auditors trust.
We use cookies
We use strictly necessary cookies to make Radius360 work. With your consent, we'd also like to use analytics cookies to understand how visitors use our site so we can improve it. You can change your choice anytime. See our Privacy Policy.