Skip to main content
← BlogCompliance

Reporting a cyber incident to OJK: deadlines, formats, and test reports

Commercial banks report IT incidents to OJK in 24 hours and 5 working days, BPR in 24 hours and 7 working days, BI-regulated operators in 1 hour, and personal data breaches in 3x24 hours. Article by article, with the report formats and the separate route for security test reports.

M
Mirna Indriasari · Security Program Manager
August 21, 2026·Updated October 10, 2026·14 min read

When a cyber incident hits a financial institution in Indonesia, the reporting deadline depends on what kind of institution you are and what happened. A commercial bank sends OJK an initial notification within 24 hours and an incident report within 5 working days of the incident becoming known. A BPR or BPRS also has 24 hours, with 7 working days for the report. Parties regulated by Bank Indonesia notify BI within 1 hour, and when a bank is also a payment system operator that 1 hour pulls its OJK deadline forward too. If personal data was affected, whether leaked, destroyed, lost or made unavailable, UU PDP adds a separate obligation: written notice within 3x24 hours to the data subjects and the supervisory body.

This post goes through each of those deadlines article by article, how to decide whether an incident is also a failure of personal data protection, where the report formats are set, and then the different route for reporting security test results.

Who reports to whom, and when

WhoBasisInitial noticeFull reportReport to
Commercial banksPOJK 11/2022 Pasal 6024 hours from the incident becoming known5 working days from the incident becoming knownOJK
BPR and BPRSPOJK 34/2025 Pasal 46, from 18 Dec 202624 hours from the incident becoming known7 working days from the incident becoming knownOJK
Parties regulated by BI, including PJP and PIPPBI 2/2024 Pasal 401 hour from the incident becoming known3 calendar days from the incident occurringBank Indonesia
Any personal data controller, in any sectorUU PDP Pasal 46; from 16 Jan 2027 also PP 33/2026 Pasal 114Written notice within 3x24 hoursOne notice with minimum contentsData subjects and the supervisory body

Watch the start points. The OJK clocks and the BI notification run from when the incident became known, but BI's 3 calendar day report runs from when the incident occurred, so that clock can already be running before anyone has noticed. UU PDP itself does not say when its 3x24 hours start. That is about to change: according to Hukumonline's summary of PP 33/2026, Pasal 114 ayat (2) counts them from when the personal data protection failure is known "secara pasti, patut, dan wajar", with certainty, properly and reasonably, and the PP applies from 16 January 2027. That wording still leaves room to argue about when a controller reasonably should have known, so record the first discovery time and each step of confirmation from the start. The official text of PP 33/2026 was not yet on the government's legal databases when we checked on 21 October 2026.

Commercial banks: 24 hours and 5 working days

Pasal 60 ayat (1) governs a different route from test reporting. Where an IT incident occurs that potentially or actually caused significant loss or disrupted the smooth running of the bank's operations, the bank must submit an initial notification at most 24 hours after the IT incident became known, and an IT incident report at most 5 working days after the IT incident became known.

Two things in that sentence deserve attention. The count starts from when the incident became known, not from when it happened, which makes the record of the discovery time an important document. The trigger is also not every incident, but one that potentially or actually caused significant loss or disrupted operations, and that assessment sits with the bank. For the initial notification, Pasal 60 ayat (2) states it is submitted in writing by electronic means to OJK based on the initial information available. So the 24 hour notification does not demand a settled root cause, only the initial information you have.

BPR and BPRS: 24 hours and 7 working days

POJK 34/2025 Pasal 46 ayat (1) uses the same trigger as the commercial bank rule: an IT incident that potentially or actually caused significant loss or disrupted the smooth running of the BPR's or BPR Syariah's operations. The initial notification is due within 24 hours of the incident becoming known, and the IT incident report within 7 working days of the incident becoming known. Ayat (2) matches the commercial bank rule too: the initial notification goes to OJK in writing by electronic means, based on the initial information available.

The report is submitted online through the OJK reporting system as an incidental report (Pasal 47), and Pasal 48 leaves the procedure and format to OJK. The provisions apply from 18 December 2026, so a BPR without a written escalation procedure has roughly two months to put one in place. We cover the preparation in incident response and OJK reporting for rural banks.

When another regulator moves faster

The part that is least known sits in Pasal 60 ayat (4) and (5) of POJK 11/2022, and POJK 34/2025 Pasal 46 ayat (3) and (4) set the same rule for BPR. Where another authority regulates the submission of an initial notification or an incident report within a faster period, the bank must submit to OJK at the same time as that authority's rule requires. A bank that has done so is treated as having met the OJK deadlines.

The consequence is real for a bank that is also a payment system operator. PBI 2/2024 Pasal 40 requires an initial cyber incident notification within 1 hour, so the effective deadline to OJK becomes 1 hour as well, not 24 hours. The fastest clock pulls the others with it, and that changes how the escalation procedure has to be built.

Is this incident also a personal data protection failure?

This is the question that decides whether there is a second obligation, and the answer does not follow automatically from the OJK report. OJK's trigger is significant loss or operational disruption. UU PDP's trigger is a failure of personal data protection, and that is wider than a leak. The explanatory note to Pasal 46 ayat (1) defines it as a failure to protect personal data in terms of confidentiality, integrity and availability, including deliberate or accidental security breaches that lead to destruction, loss, alteration, disclosure or unauthorised access. So ransomware that encrypts a customer database can trigger the UU PDP duty even when nothing was stolen, because the availability of that data was not protected. The same goes for data that is deleted, corrupted or altered without authorisation. An incident that only stops a service, without touching any system that processes personal data, can trigger the OJK duty alone, and unauthorised access to a single customer database can trigger the UU PDP duty without disrupting operations at all. If you are unsure whether personal data was affected, treat it as affected until you can show otherwise.

Where personal data protection has failed, UU PDP Pasal 46 ayat (1) requires written notice within 3x24 hours to the data subject and to the supervisory body, and ayat (2) sets the minimum content: the personal data that was exposed, when and how it was exposed, and the controller's handling and recovery efforts. The recipients are different from OJK, and the OJK report does not replace this notice. The dedicated data protection authority has not been established and Komdigi supervises in the interim, so confirm the current notification channel before an incident, not once the clock is running. We cover the obligations of vendors who process data for you in vendor obligations and DPAs under UU PDP.

The call on whether an incident is a personal data protection failure should have a named owner in the procedure, usually the data protection officer together with the head of information security. Without one, the decision stalls while each waits for the other, and the 3x24 hours run out in a meeting.

Notification and incident report formats

For commercial banks, since 1 March 2026 the formats for IT reports and notifications are in Lampiran III of PADK 1/2026, a regulation of an OJK board member that replaced SEOJK 21/SEOJK.03/2017. The submission procedures are in its Lampiran II. Pasal 62 of POJK 11/2022 remains the basis for reports going online through the OJK reporting system.

For BPR and BPRS, Pasal 48 of POJK 34/2025 leaves procedure and format to OJK, and the implementing provisions for POJK 34/2025 are in PADK 43/PADK.03/2025. One point applies to both: the initial notification only needs the initial information available, so do not hold it back waiting for a root cause analysis. An incomplete notification is not late; an unsent one is.

Security test reports: a different route

POJK 11/2022 names the minimum content of the report, and SEOJK 29/2022 sets its format in Lampiran VI. For the scenario-based cyber security test report, Pasal 25 ayat (4) sets three things: a summary of how the test was carried out, lessons learned or observations drawn from the results, and the plan or the corrections already carried out. The format follows Lampiran VI of SEOJK 29/2022, and submission is online through the OJK reporting system under Pasal 62 ayat (1).

Three items is less than most people expect, and it does not mean a thin report will do. Minimum content is the floor for compliance, not a measure of a useful report.

Two kinds of testing, two reporting routes

Pasal 23 requires two forms of testing, one based on vulnerability analysis and one based on scenarios, and each is reported differently. This distinction is a frequent source of confusion.

For vulnerability-analysis testing, which is the stream a penetration test belongs to, Pasal 24 ayat (1) requires it to be carried out periodically without naming a figure, and ayat (2) requires the results to be submitted to OJK as part of the report on the current condition of the bank's IT implementation. The deadline for that sits in SEOJK 29/2022 romawi VII point 4 letter b: at most 15 working days after the end of the reporting year. What goes in is a compilation, not one report per test. The SEOJK's own worked example makes it concrete: a bank that ran penetration tests in March, July, and November 2022 submits the compilation by 20 January 2023 at the latest.

For scenario-based testing, Pasal 25 ayat (1) sets a minimum of once a year, and ayat (3) gives it a deadline of its own: the report goes to OJK at most 10 working days after the cyber security testing is completed. When the testing counts as completed is not left to interpretation. SEOJK 29/2022 romawi VII point 4 letter b defines it: the testing is deemed complete when the test report has finished being compiled. So the count starts from the completion of the report, not from the last day of testing activity, and the SEOJK's example shows it: a test run on 3 November 2023 whose report was finished on 14 November 2023 must be submitted by 28 November 2023.

What the scenario test itself has to cover

Before the report, Pasal 25 ayat (2) sets the coverage of the test itself, at least four things: setting the objectives, scope, and test scenarios; carrying out the test; evaluating the results; and assessing the effectiveness of the bank's mitigation, response, and recovery measures against cyber attacks.

That fourth item is the one most often missed. A test that produces only a list of vulnerabilities has not met this ayat, because what is asked for is an assessment of how effectively the bank contains and recovers. That puts scenario-based testing closer to an incident response exercise than to a technical scan, and it means the bank's incident response team has to be genuinely involved.

The test report format is in Lampiran VI of SEOJK 29/2022

POJK 11/2022 names only the minimum content, which makes it easy to conclude that no official format exists. That conclusion is wrong. SEOJK 29/2022 romawi VII point 4 letter b requires scenario test results to be submitted in the format set out in Lampiran VI, which forms an inseparable part of the circular.

Lampiran VI is a table headed "Laporan Hasil Pengujian Keamanan Siber Berdasarkan Skenario", filled in per test, with the bank name and year above it. Its columns are the test objective, the type of test, the test scope, the date testing started, the date testing finished, the parties involved, the test result, the corrections carried out, and the follow-up plan.

Two of its footnotes are worth reading. The parties-involved column explicitly covers the IT service provider or third party the bank used to perform the testing, so the form itself treats a third-party tester as ordinary. And the corrections column is filled in where the bank has already remediated, while the follow-up plan is filled in where it has not, so the two are not meant to be completed together.

For submission, Pasal 62 ayat (3) of POJK 11/2022 leaves the online reporting procedure to the OJK rules on bank reporting through the OJK reporting system. So Lampiran VI governs the content and shape of the report, while those reporting rules govern the mechanics of sending it.

In practice, the gap we find most often is not the format but the third item in Pasal 25 ayat (4). Reports name a remediation plan with no owner and no date, or claim corrections already made with no retest evidence. Both pass formally and are hard to defend in an examination.

Sanctions for late and incomplete reports

Pasal 27 sets the sanctions for failing to test: a written warning first, then a ban on issuing new bank products, suspension of certain business activities, or a downgrade of the governance factor if the requirement is still not met. For reporting, Pasal 63 sets the same pattern for a bank that is late with the initial IT incident notification. For BPR, POJK 34/2025 Pasal 49 ayat (3) imposes a written warning for a late initial notification, and ayat (4) adds temporary suspension of part of the bank's operations, a ban on expanding business activities, or a downgrade of its soundness rating if the requirement is still not met after the warning. Pasal 62 ayat (2) states that breaches relating to report submission carry an administrative sanction, and Pasal 64 provides that a bank submitting an incomplete report is sanctioned for information error under the bank reporting rules. There is no fine in any of those articles.

For the wider picture of the testing obligation and who may carry it out, see who is allowed to run a bank's penetration test and cybersecurity compliance for commercial banks.

References

  1. OJK Regulation No. 11/POJK.03/2022 on Information Technology Implementation by Commercial Banks, BPK RI regulation database. Pasal 23 to 27 govern testing and its sanctions, Pasal 60 governs incidental reports, and Pasal 62 to 64 govern report submission and its sanctions.
  2. Law Number 27 of 2022 on Personal Data Protection, BPK RI regulation database, Pasal 46 and its explanatory note for the notice and the definition of a personal data protection failure.
  3. Hukumonline, Tanggung jawab pemerintah atas kebocoran data pribadi, updated 5 October 2026, for its summary of PP 33/2026 Pasal 114 ayat (2).
  4. SEOJK No. 29/SEOJK.03/2022 on Cyber Resilience and Security for Commercial Banks, OJK (full text). Romawi VII point 4 sets the submission deadlines for both kinds of test result and defines when testing is complete, point 5 governs who may run the testing, and Lampiran VI carries the report format.
  5. Bank Indonesia Regulation No. 2 of 2024 on Information System Security and Cyber Resilience, Bank Indonesia, Pasal 40 for the cyber incident notification deadline.
  6. OJK Regulation No. 34 of 2025 on Information Technology Implementation by BPR and BPR Syariah, OJK. Pasal 46 governs IT incident notification and reporting, Pasal 47 and 48 submission, Pasal 49 sanctions.
  7. OJK Board Member Regulation (PADK) No. 1 of 2026 on Information Technology Implementation by Commercial Banks, OJK. Lampiran II sets the report submission procedures, Lampiran III the report and notification formats.
WhatsApp