RiskSphere

RiskSphere: Risk management recorded from criteria to the risk owner's decision

RiskSphere replaces the spreadsheet risk register with a complete ISO/IEC 27005 process: versioned criteria, likelihood × impact scoring, treatment plans, residual-risk acceptance by the risk owner, and an SoA linked to each risk.

RiskSphere dashboard with sample data

32

Ready-to-use baseline risk scenarios

17 security, 10 privacy, 5 both, plus custom scenarios for your own workspace

93

ISO/IEC 27001:2022 Annex A controls in the Statement of Applicability

Plus 78 ISO/IEC 27701:2025 controls when privacy is in scope

5×5

Default likelihood × impact matrix

Switch to 3×3 or 4×4 before any risk has been assessed

A spreadsheet risk register can't answer an auditor's questions

Many companies keep their risk register in a spreadsheet that only gets updated before an audit. Assessment criteria change without a record, so last year's scores can no longer be compared with this year's.

Auditors ask specific questions: who accepted this residual risk, under which version of the criteria, when, and why was this Annex A control excluded from the SoA. The answers usually sit across emails, meeting notes, and separate files.

ISO/IEC 27001:2022 clause 6.1.2 calls for risk assessments that produce consistent, comparable results, and clause 6.1.3 requires risk owners to accept the residual risk. RiskSphere records each of those steps in one place, with who did it, when, and why.

How RiskSphere Works

A simple, structured process your team can run right away.

  1. 01

    Set the scope and risk criteria

    Define the ISMS or PIMS scope, the standards in use, matrix size, impact dimensions, level thresholds, risk appetite, and review cycles. Every change to the criteria is saved as a new version with its reason.

  2. 02

    Identify risks

    Start from the 32-scenario baseline library, import your existing register from Excel, or add risks by hand. Records in the risk-source registers (assets, pentest findings, incidents, audit findings, third parties, processing activities) can be turned into new risks and stay linked to them.

  3. 03

    Score likelihood × impact

    Score inherent, residual, and target risk. Impact takes the highest value across the active dimensions, and the criteria version is stored with each assessment. Risks scoring above appetite are flagged in the register, on the dashboard, and in the notification bell.

  4. 04

    Treat the risk and accept what remains

    Choose Mitigate, Accept, Avoid, or Transfer, link Annex A controls, then assign actions with an owner, due date, and cost. The designated risk owner accepts the residual risk, and that acceptance is tied to the residual score at the time.

  5. 05

    Review on schedule and report

    Review dates follow the risk level (by default: Critical every 3 months, High every 6, Medium and Low every 12), with reminders inside the app. The register, risk profile, treatment plan, and SoA download as PDF or Excel for management review and audits.

Features & Capabilities

Built for real operational needs, not a checklist of features that only looks good in a brochure.

01
Scenario-based risk register
Each risk records the threat, vulnerability, affected asset, C/I/A properties, category, and risk owner, with automatic codes such as R-001. Filter by level, owner, stage, review date, or heatmap cell. Risks are never deleted, only closed with a reason, and can be reopened.
02
Versioned criteria and risk heatmap
A 3×3, 4×4, or 5×5 matrix with impact dimensions you define, including your own rupiah thresholds. Inherent and residual heatmaps show where every risk sits, and levels always appear as a number and a label, never colour alone.
03
Cross-risk treatment plan
Treatment actions with owners, due dates, costs, and linked controls come together in one treatment plan. Filter to My tasks or overdue items, update many actions at once, and attach evidence to each action.
04
Acceptance by the risk owner
Only the designated risk owner can accept a residual risk, and a reason is required when the score is above appetite. Each acceptance stores the score, criteria version, time, and validity period, and lapses if the residual score changes.
05
SoA linked to your risks
93 ISO/IEC 27001:2022 Annex A controls and 78 ISO/IEC 27701:2025 controls, each with an applicable or excluded decision, implementation status, owner, and evidence. Justifications can come straight from linked risks, and controls without one are flagged.
06
Dashboard and audit-ready reports
The dashboard shows risks above appetite, overdue actions, control implementation progress, and the highest-scoring risks. Formal A4 PDF reports with a cover page cover the register, risk profile, treatment plan, and SoA, and Excel exports state the criteria version.

RiskSphere Modules in Detail

All 13 modules available in the RiskSphere dashboard today, grouped as they appear in the app menu.

Risk management

4 modules

Risk register
Record scenario-based risks with threat, vulnerability, affected asset, C/I/A, and owner, then score inherent, residual, and target risk. Each risk keeps its treatment, acceptance, linked controls, and history.
Treatment plan
Every treatment action from open risks in one list, with owner, due date, cost, and status. Filter to My tasks or overdue items, update many actions at once, and export to Excel.
Baseline library
32 information security and privacy risk scenarios with their related controls, plus custom scenarios for your own workspace. Add several at once and assign owners to speed up identification.
Risk criteria
Set the matrix size, likelihood and impact scales, impact dimensions, risk levels, risk appetite, and review cycles. Each change becomes a new version with a reason, so earlier assessments stay comparable.

Risk sources

6 modules

Assets & processes
A list of information, application, infrastructure, cloud, process, people, and physical assets with classification, C/I/A requirements, a personal-data flag, and owner. One asset can link to many risks.
Pentest findings
Record findings with severity, CVSS score, affected asset, recommendation, owner, and due date, then track their status through to a passed retest. Any finding can be turned into a new risk in the register.
Incidents
Record security incidents with category, severity, timeline, and lessons learned. For incidents involving personal data, the time left in the 3 × 24-hour notification window under the PDP Law is calculated and shown.
Audit findings
Record internal and external audit findings by type (major, minor, observation, improvement opportunity), clause, corrective action, owner, and due date, and link them to the relevant risks.
Third parties
A list of vendors and partners with service, criticality, data access, data processing agreement status, and next review date. Third parties past their review date appear in the notification bell.
Processing activities
A record of personal data processing activities (RoPA) with purpose, PDP Law legal basis, data categories, recipients, cross-border transfers, retention, and DPIA status. Shown when ISO/IEC 27701 is in scope.

Controls & compliance

1 module

Statement of Applicability
Mark each ISO/IEC 27001:2022 and ISO/IEC 27701:2025 Annex A control as applicable or excluded, with justification from linked risks, implementation status, owner, and evidence. Progress is calculated per standard.

Reports & data

2 modules

Reports
Download the risk register, risk profile, treatment plan, and SoA as formal A4 PDFs or Excel files, plus the risk-source registers in Excel. Each document lists the ISO clauses it supports.
Activity log
A timeline of risk changes across the workspace: who did what, and when. Owners and Admins also see administrative actions with their IP addresses.

Compliance & Supported Standards

RiskSphere is designed to help your organization meet the relevant control requirements and information-security standards.

ISO/IEC 27001:2022 · 6.1.2

Information security risk assessment

Versioned risk acceptance and assessment criteria, an owner for every risk, likelihood × impact analysis, and evaluation against risk appetite. Each assessment keeps its criteria version, so results stay comparable over time.

ISO/IEC 27001:2022 · 6.1.3

Information security risk treatment

Treatment options, controls selected from Annex A, an SoA with justifications and implementation status, a risk treatment plan, and residual-risk acceptance by the risk owner.

ISO/IEC 27001:2022 · 8.2, 8.3

Performing assessment and treatment

Periodic reviews are scheduled by risk level, overdue reviews show in the register and on the dashboard, and the status of every treatment action is recorded. Each risk's history serves as documented information on assessment and treatment results.

ISO/IEC 27701:2025 · 6.1.2, 6.1.3

Privacy risk and the privacy SoA

Privacy risks must be scored for their impact on data subjects, and the SoA includes the 78 ISO/IEC 27701:2025 controls that match your role as controller, processor, or both.

Service Level Agreement (SLA)

The following SLA applies equally to all six Sphere Suite products and forms part of the mutually signed Service Agreement. All Customers receive full access to every feature of the products they subscribe to.

Uptime

99.5%

Monthly service availability, excluding scheduled maintenance announced 24 hours in advance

Critical Incident Response

4 business hours

First response time for issues with a significant operational impact

Normal Issue Response

1 business day

First response time for support requests and general technical questions

Data Backup

Daily

Automatic daily data backup, retained for a minimum of 30 days

RTO (Recovery Time)

8 hours

Maximum time to restore service after a major incident affecting platform availability

RPO (Recovery Point)

24 hours

The most recent data point guaranteed to be recoverable in a system-failure scenario

Incident Notification

≤ 2 hours

Maximum time to notify Customers once an availability incident is identified

* All SLAs are measured monthly and apply from the subscription activation date.

Who Needs RiskSphere?

This platform is designed to address the real pain points of different roles across the organization.

01
ISMS / PIMS Manager
Has to keep the register, criteria, treatment plan, and SoA in sync before every audit without rebuilding them from several spreadsheets.
02
ISO/IEC 27001 and 27701 Consultant
Supports several clients at once and needs the same baseline for each, with every client's data kept separate and reachable from one account.
03
CISO / Head of IT
Needs to see which risks are still above appetite and which actions are overdue, then bring that to management review in a report people can read.

Frequently Asked Questions

Still have questions about RiskSphere? Reach out to our team via the contact page or the footer.

How is RiskSphere different from a spreadsheet risk register?

In a spreadsheet, criteria, scores, and decisions can change without a trace. In RiskSphere, criteria are versioned, every assessment stores the criteria version it used, and risk history, acceptances, and the audit log can only be appended to, never edited. You can import your existing register from Excel using a template, with row-by-row checks and a preview before anything is saved.

Can we use our own risk criteria?

Yes. You choose a 3×3, 4×4, or 5×5 matrix, then set scale names, impact dimensions, level thresholds, risk appetite, and review cycles from 1 to 36 months. You fill in the rupiah thresholds for the financial dimension yourself. The matrix size locks once a risk has been assessed so scores stay comparable, and every other change to the criteria is saved as a new version with its reason.

How does RiskSphere help with an ISO/IEC 27001 audit?

The risk register, risk profile, treatment plan, and SoA are available as PDF reports with a cover page or as Excel files that state the criteria version. Auditors can be given the Viewer role to trace each risk from scenario, assessment, and treatment through to acceptance, along with its history, without being able to change or export data. Evidence attached to risks, actions, and controls is recorded with a SHA-256 fingerprint.

Who can work in RiskSphere, and how is access limited?

There are four roles: Owner, Admin, User, and Viewer. The Owner can restrict a User to editing only their own records, which suits risk owners and action owners. Only the designated risk owner can accept a residual risk. Viewers have read-only access with member emails masked. Consultants can join several client workspaces with one account.

Is our risk data secure in RiskSphere?

Each company's data is separated in the application and in the database with row-level security, so no other workspace can see it. The server rejects any action outside a user's role. A workspace can require two-factor authentication (TOTP) and automatic sign-out after inactivity. The audit log is sequence-numbered with a chained SHA-256 hash, and Owners and Admins are alerted to suspicious patterns such as repeated failed sign-ins.

Ready to Try RiskSphere?

Schedule a free demo and see how RiskSphere works with realistic sample data.