IncidentSphere

IncidentSphere: Handle security incidents without missing a reporting deadline

When an incident hits, your team has to contain it while racing notification deadlines. IncidentSphere records every incident from first report to post-incident review, and counts down PDP Law, BSSN, and OJK reporting obligations from the moment the incident is known.

IncidentSphere dashboard with sample data

72 hours

Deadline for written notice to data subjects and the PDP authority after a personal data protection failure

Source: Law No. 27 of 2022 (PDP Law), Article 46(1)

24 hours

Deadline for a commercial bank's initial cyber incident notice to OJK, followed by a full report within 5 business days

Source: SEOJK 29/SEOJK.03/2022

11

Reporting obligations in the IncidentSphere catalog: PDP Law, BSSN, OJK, board of directors, customers or partners, police, and insurers

Product fact: each organization switches on the obligations that apply to it

Incidents handled in group chats are hard to account for

Without a structured system, incident handling lives in group chats and spreadsheets: nobody is sure who owns which task, the timeline gets rebuilt from memory, and evidence sits on individual laptops with no record of who has held it.

Meanwhile the regulatory clock starts when the incident is known. Article 46 of the PDP Law gives you 3 × 24 hours to notify data subjects and the PDP authority of a personal data protection failure, and commercial banks must send OJK an initial notice within 24 hours. Deadlines like these slip easily while the team is busy containing damage.

When an ISO 27001 auditor or a regulator asks for evidence, you need to show when the incident was known, which decisions were made and by whom, which notifications went out, and which lessons were acted on. A chat history won't cover that.

How IncidentSphere Works

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

  1. 01

    Report the incident

    Team members log incidents through a structured form: what happened, when it was detected, the source, a TLP label, affected systems, and a coordinator. Employees, customers, or the public can also report through your organization's public reporting page, anonymously if they prefer.

  2. 02

    Triage and classify

    The coordinator scores impact on each dimension plus urgency; priority P1 to P4 comes from your own criteria matrix, and response, containment, and recovery targets start running. Events that turn out not to be incidents are closed with a reason, and duplicate reports are linked or merged.

  3. 03

    Respond with playbooks and tasks

    The category's playbook turns into tasks per phase, each with an owner and a due date. Status moves through containment, eradication, and recovery, while evidence and indicators of compromise are recorded on the same incident.

  4. 04

    Meet reporting obligations

    The PDP assessment, incident priority, and critical-infrastructure status determine which obligations apply, each with its own deadline and countdown. The team edits a draft notice that already contains the required content, sends it through the official channel, then records the send time, recipient, and reference number.

  5. 05

    Review, fix, and close

    The post-incident review captures root cause and lessons learned, and corrective actions are tracked to completion. An incident can only be closed once it is classified, has no pending reporting obligations, and has been reviewed when its priority requires it.

Features & Capabilities

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

01
Reporting from inside and outside the organization
An incident form for your team, plus a public reporting page for employees, customers, or the public, with an anonymous option and a tracking code for status checks. Public reports are triaged before they become incidents, and reporter identity is visible only to authorized roles.
02
Classification with versioned criteria
A 4 × 4 impact-by-urgency matrix sets priority P1 to P4 along with response, containment, and recovery targets. Changing the criteria creates a new version, so every incident is still measured against the criteria in force when it was classified.
03
Reporting clocks and draft notices
PDP Law, BSSN, OJK, and internal obligations are calculated from the facts of the incident, with business days that respect your holiday calendar. Reminders appear in in-app notifications as deadlines approach. Drafts include the content each rule requires, and every submission is logged as on time or late.
04
Playbooks, tasks, and timeline
Nine built-in playbooks for ransomware, phishing, data leaks, online gambling injection, DDoS, and more, all editable. Every change to status, classification, tasks, and notes lands in a timeline that cannot be edited, with who did it and when.
05
Evidence and indicators of compromise
Each evidence file gets a SHA-256 fingerprint on upload, and every handover is recorded in an append-only chain of custody. Paste IPs, domains, and hashes in bulk, and see right away when a value has appeared in another incident.
06
Post-incident review and audit-ready reports
The review records root cause, what went well, and lessons learned, and corrective actions are tracked to completion. Download a PDF report per incident, the incident register, the notification log, and the audit log, with every download logged.

IncidentSphere Modules in Detail

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

Detection & reporting

2 modules

Incidents
A register of every incident with its priority, status, coordinator, and nearest target. Search, filter, and save views, then open an incident to classify it and manage tasks, evidence, and reporting obligations.
Public reports
An inbox for reports from your public reporting page, including anonymous ones. Your team posts a response the reporter sees through a tracking code, or turns the report into an incident.

Response

3 modules

Response tasks
Tasks from every incident, filterable by status, owner, phase, and due date. Update the status, owner, or due date of many tasks at once, with each change recorded in the incident timeline.
Evidence & chain of custody
A cross-incident evidence register searchable by name, SHA-256 fingerprint, or incident code. Each item shows its custody history, so you can show auditors it is intact and who has handled it.
Indicators of compromise
A library of IPs, domains, URLs, email addresses, and hashes from every incident. The Also in column flags the same indicator in other incidents, so repeat attacks are spotted sooner.

Compliance & learning

3 modules

Reporting obligations
A board of PDP Law, BSSN, OJK, and internal reporting obligations across all open incidents, nearest deadline first. See at a glance what has not been sent, what is due soon, and what is overdue.
Post-incident reviews
Incidents awaiting review or already reviewed, with a flag where your priority threshold makes a review mandatory. Root cause, reviewer, and open corrective actions are visible in one place.
Corrective actions
Follow-up actions from post-incident reviews, each with an owner, due date, and status. Filter for overdue items and export to Excel as evidence of continual improvement.

Preparedness

3 modules

Playbooks
Nine built-in playbooks you can adapt, with steps for each response phase. Playbooks are linked to incident categories and applied as tasks, so the team never starts from a blank page.
Contacts & exercises
Emergency contacts for internal teams, regulators, CSIRT/BSSN, vendors, legal, PR, police, and insurers, plus records of tabletop, simulation, or technical exercises with findings and follow-ups.
Classification criteria
Impact and urgency scales, the 4 × 4 matrix, and time targets per priority, managed in Settings. Every change is saved as a new version with a reason, so earlier classifications remain defensible.

Reports & data

2 modules

Reports
Download the incident register, notification log, corrective actions, and public reports in Excel, and indicators of compromise in CSV. Each file is built from current data, and every download is logged.
Activity log
The handling timeline of every incident in one view, plus workspace administration actions for Owners and Admins. Entries cannot be edited or deleted.

Compliance & Supported Standards

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

A.5.25

Assessment and decision on information security events

Every report is assessed against your impact-by-urgency criteria and either given a priority or declared not an incident with a reason. The assessor, time, and criteria version are recorded in the timeline.

A.5.27

Learning from information security incidents

The post-incident review records root cause and lessons learned, is required before closing incidents at or above the priority threshold, and its corrective actions are tracked with an owner and a due date.

A.5.28

Collection of evidence

Evidence is stored with a SHA-256 fingerprint taken on upload and an append-only chain of custody, so you can show auditors that it is intact and how it was handled.

PDP Law

Law No. 27 of 2022, Article 46

A personal data protection failure assessment triggers the 3 × 24-hour notice to data subjects and the PDP authority, with a countdown, a draft covering the three minimum contents, and a record of when it was sent.

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 IncidentSphere?

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

01
Incident Response Coordinator / CSIRT
Tracks several incidents and deadlines at once under pressure, and needs one place for priorities, team tasks, evidence, and reporting clocks instead of group chats and spreadsheets.
02
Compliance Manager / ISO 27001 Owner
Has to show auditors that controls A.5.24 to A.5.28 are working: the incident register, decisions with their reasons, the evidence chain, PDP Law notifications, reviews, and corrective actions followed through.
03
CISO / Head of IT
Needs to see open incidents, those past their targets, pending reporting obligations, and the team's average response time, then take a summary to the board.

Frequently Asked Questions

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

What counts as an incident in IncidentSphere?

Information security incidents in the broad sense: ransomware, phishing, account takeover, data leaks, online gambling injection, DDoS, lost devices, insider misuse, and incidents at your suppliers. There are 16 built-in categories mapped to ENISA classes, and you can add, edit, or deactivate them. A report that turns out not to be an incident is marked Not an incident with a reason rather than deleted.

Who can report an incident?

Team members with the Owner, Admin, or User role report from inside the application. Employees without an account, customers, or the public can use your organization's public reporting page, with or without their identity, and check progress with a tracking code. Your team reviews each report and turns it into an incident when needed. The reporting page and the application are in Indonesian.

Does IncidentSphere send notifications to regulators automatically?

No. IncidentSphere works out which obligations apply and their deadlines, then prepares a draft with the content the rule requires, such as the three minimum contents of a PDP Law notice. Your team sends it through the official channel and records the send time, recipient, channel, and reference number, so the obligation is logged as on time or late.

Can incident data be changed or deleted?

Incidents cannot be deleted: they are closed, or declared not an incident with a reason. The timeline, chain of custody, criteria version history, and audit log are append-only. A closed incident must be reopened with a reason before its details, classification, tasks, or evidence can change. Data is kept while the workspace is active, and only the Owner can delete all incident data, with a confirmation that is recorded in the audit log.

How does IncidentSphere help during an ISO 27001 audit?

Auditors will ask for evidence that incidents are recorded, assessed, handled, and learned from according to procedure. From IncidentSphere you can download the incident register, notification log, and corrective actions in Excel, a PDF report per incident with its timeline and SHA-256 evidence, and the audit log. You can also give auditors the Viewer role to read every record without being able to change data, export, or download evidence.

Ready to Try IncidentSphere?

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