# Indonesian bank cyber reporting: Verify OJK deadlines and log evidence

Andi Pratama · November 15, 2026

> Indonesian banks must report cyber incidents to OJK within one hour, following six steps to verify evidence, classify severity, and retain logs.

The mechanism works in sequence. First, detection creates an incident record. Second, responders query the centralized repository for the affected assets, accounts, and time range. Third, they reconcile gaps such as missing sources, clock skew, or truncated records. Fourth, they classify severity and materiality based on the verified evidence. Fifth, they submit the report within the one-hour clock using facts supported by that evidence. Sixth, they retain the log set for follow-up review, audit, or deeper investigation.

Materiality means the incident’s impact on customers, operations, data, or regulatory obligations. Chain of custody means documented handling of the log evidence so its source and integrity can be explained. Retention means keeping the logs available for investigation and audit under the bank’s policy. The “live, complete option” is the current, fully assembled evidence set, not a cached partial view or an early alert summary.

![Modern glass and steel banking towers Jakarta s financial district dusk](https://static.mm-ais.com/article-images-ai/indonesian-bank-cyber-reporting-verify-o-ai-f5d242de.jpg)
Modern glass and steel banking towers Jakarta s financial district dusk

## Key Factors to Consider

First criterion: verified time to report. Measure the full path from detection to a report the bank can stand behind, including log search, correlation, analyst review, and approval. Check when the clock starts, what counts as “reported,” and whether the vendor’s metric stops at alert generation or includes human verification. A fast alert that still needs manual reconstruction is not the same as a verified report.

Second criterion: retention completeness. Confirm that every in-scope system, channel, and third party is actually retained and searchable in one place. Test with a realistic incident spanning core banking, payments, identity, endpoints, and vendor logs. Check retention period, immutability, access controls, and whether exports are usable by auditors and regulators without vendor assistance.

| Criterion | Verify before committing | Common comparison trap |
| --- | --- | --- |
| Verified time to report | Clock start, report definition, human review included | Alert speed quoted as report speed |
| Retention completeness | Systems covered, searchability, export format | “Centralized” that excludes key logs |
| Total cost and terms | Same units, same horizon, all fees, exit rights | Low headline price with overage or lock-in |

Third criterion: total cost and terms. Compare like-for-like across ingestion, storage, retention, search, support, professional services, renewal increases, and exit or transition costs. Check whether “unlimited” has caps, whether pricing is based on data volume, events, or users, and whether the contract grants audit rights and data portability. A lower first-year quote can be more expensive if overage or migration costs are hidden.

Compare costs only from live quotes and contracts using identical units and the same retention horizon. Treat any missing unit price, minimum commitment, overage, or renewal assumption as unverified and exclude that option until the vendor provides it in writing rather than counting it as a saving.

Finally, require evidence, not promises: ask for a documented test result, a sample export, and a named owner for each criterion. The decision should be recorded as “verified” only when the bank can repeat the check without relying on the vendor’s interpretation.

![Key Factors to Consider — Indonesian bank cyber reporting](https://static.mm-ais.com/article-images-ai/indonesian-bank-cyber-reporting-verify-o-ai-527423c8.jpg)

## Common Mistakes

Even with strong intent to comply, banks often stumble by committing to a report before the underlying evidence is complete. A common pitfall is relying on a single alert source while critical records remain scattered across systems. For example, a security operations team may detect unusual outbound traffic from a payment gateway and immediately submit a report based only on a firewall alert. Hours later, once application and authentication records are reviewed, the team discovers the activity stemmed from a compromised service account rather than the initially suspected malware. The result is a corrective filing that weakens credibility with supervisors and creates avoidable rework. Before committing, teams should verify that records from all affected assets and relevant systems are accessible, time-synchronized, and correlated into a single, reviewable timeline.

A second pitfall is confusing the moment an alert is noticed with the moment the incident can be factually established. Consider an analyst who begins a shift, sees a high-severity notification, and treats that timestamp as the start of the event. When retained records are examined, they reveal that suspicious access began earlier during an overnight batch process. Reporting on the basis of discovery time alone, without checking the earliest corroborated evidence, can produce an inaccurate chronology that is difficult to defend during supervisory follow-up. A practical check is to require sign-off that the reported timeline distinguishes detection, validation, and the earliest confirmed activity supported by retained records.

Banks also undermine their own reports when evidence handling is treated as an afterthought. In a rushed response, responders may export logs manually, rename files, or copy data between shared folders without preserving integrity controls. If a later review cannot confirm that the records are unchanged from the time of collection, the bank may struggle to substantiate what it reported or to explain discrepancies between initial and subsequent submissions. To avoid this, teams should use a consistent collection procedure that preserves original records, documents who accessed them, and maintains a clear chain of custody from capture through reporting.

Finally, many reporting errors originate from unclear internal ownership at the moment of escalation. For instance, a fraud unit, network team, and compliance officer may each assume another group is responsible for validating the incident narrative, leading to a report that mixes unverified assumptions with confirmed facts. A simple pre-commitment check is to confirm that one accountable owner has reviewed the consolidated evidence, reconciled conflicting inputs, and approved the final statement of what is known versus what remains under investigation. This discipline helps ensure the submission reflects verified facts rather than the fastest available interpretation.

## Insider Tactics

The least obvious tactic is to prepare the notification format before anything goes wrong. Maintain a pre-approved draft with entity details, regulator routing, classification language, and the minimum fact set you consider defensible. When the reporting window starts, the team should be adding verified log evidence to that prepared draft, not drafting from a blank page. Check that every field in the pre-approved draft can be answered directly from the centralized log platform without manual hunting.

A second tactic is to make the clock visible and owned. Assign a single timeline owner whose first move after an incident is confirmed is a time-stamped capture from the central log, not a discussion. Write an explicit, objective trigger for when the reporting window opens into the runbook, so the start point is decided by procedure rather than by the mood of the room.

For timing, back-time rather than front-load. Set a fixed internal evidence cutoff relative to the deadline and protect a sign-off buffer at the end of the window. Do not spend the opening minutes chasing deep forensics; assemble the verified minimum fact set first, then let verification fill in detail. If that minimum fact set is not assembled by your cutoff, escalate for a decision on submitting an initial report with verified facts and clearly flagged pending items while investigation continues.

Rehearse against the clock. Run timed drills where the team must produce the notification from the log platform inside the one-hour window, then map where the minutes actually went. Handoff friction — who pulls logs, who classifies, who approves — usually consumes more of the window than the technical work, so practice the transitions specifically. Check: if any step depends on a person who is not on call, fix the roster before an incident fixes it for you.

Finally, turn retrieval into a shared artifact rather than an individual skill. Maintain saved searches or dashboards for each likely incident type so the first responder produces standardized evidence in a few clicks instead of writing queries under pressure. Rule: any dashboard used inside the hour should emit timestamps from a single synchronized clock source, because mismatched clocks undermine the very evidence the report rests on.

## Comparison

To verify an option before committing, compare centralized log retention deployments side by side using measurements from your own environment under OJK Regulation No. 11/POJK.03/2022. Run one timed incident scenario and record the same criteria for each option: query-to-export time, count of covered in-scope systems, export format and tamper evidence, and contract terms for access, support, and exit. Judge each option on those like-for-like results rather than assumptions.

**On-premises centralized retention wins** when your measured drill shows it can assemble a complete, exportable timeline fastest with full coverage of in-scope systems, and when internal teams retain uninterrupted access and control under existing support arrangements. It is the stronger choice if contractual dependencies on external providers would slow evidence retrieval during an active incident.

**Cloud-native centralized retention wins** when live tests demonstrate equal or better query-to-export performance across distributed environments and the provider’s contractual terms guarantee the access, support responsiveness, and data portability your bank requires. It is preferable when scaling coverage to new systems can be verified without creating gaps in the consolidated view.

**Hybrid centralized retention wins** when neither single model delivers complete, timely evidence on its own, but a combined design does: for example, when local retention secures immediate access to critical systems while a secondary repository completes coverage. The overall winner is the option whose verified measurements and contract terms together prove it can deliver a complete, defensible evidence package before the bank commits to its report.

## What to do next

| Step | Action | Why it matters |
| --- | --- | --- |
| 1 | Review the current, complete text of OJK Regulation No. 11/POJK.03/2022 on the official OJK website to confirm all cyber incident reporting obligations. | Verifies the live regulatory requirements before committing to any compliance solution or workflow changes. |
| 2 | Map your existing incident detection, logging, and reporting workflows against the specific obligations set out in OJK Regulation No. 11/POJK.03/2022. | Identifies gaps that could prevent your bank from meeting the 1-hour reporting deadline after detection. |
| 3 | Assess whether your current log infrastructure supports centralized log retention for rapid collection and verification of incident evidence. | Centralized logs are critical to gathering the evidence needed to submit an initial cyber incident report to OJK within the required timeframe. |
| 4 | Compare like-for-like centralized logging and incident response options, evaluating total costs, implementation terms, and alignment with OJK’s reporting requirements. | Ensures you select a solution that fully supports compliance without hidden costs or capability gaps. |
| 5 | Conduct incident response drills to test your team’s ability to detect, consolidate evidence, and submit an initial report to OJK within the 1-hour deadline. | Validates that your processes and systems perform under real-world conditions and meet the mandated reporting window. |
| 6 | Establish ongoing monitoring of official OJK communications to track any updates to OJK Regulation No. 11/POJK.03/2022 and adjust workflows accordingly. | Keeps your reporting processes aligned with the latest regulatory obligations and maintains continuous compliance. |

## Frequently Asked Questions

**Within what timeframe must a bank submit a cyber incident report after detection?**

The bank must submit the report within the one-hour clock using facts supported by verified evidence.

**What types of gaps must responders reconcile when gathering log evidence?**

Responders must reconcile gaps such as missing sources, clock skew, or truncated records.

**How is materiality defined for a cyber incident?**

Materiality means the incident’s impact on customers, operations, data, or regulatory obligations.

**What does chain of custody mean in the context of log evidence?**

Chain of custody means documented handling of the log evidence so its source and integrity can be explained.

**What constitutes the "live, complete option" for incident evidence?**

The "live, complete option" is the current, fully assembled evidence set, not a cached partial view or an early alert summary.

**Why is a fast alert insufficient as a measure of verified time to report?**

A fast alert that still needs manual reconstruction is not the same as a verified report, as verified time to report includes log search, correlation, analyst review, and approval.

## Quick answers

| Within what timeframe must a cyber incident report be submitted? | The report must be submitted within the one-hour clock using facts supported by that evidence. |
| --- | --- |
| What does materiality mean in the context of cyber incident reporting? | Materiality means the incident’s impact on customers, operations, data, or regulatory obligations. |
| What is chain of custody in relation to log evidence? | Chain of custody means documented handling of the log evidence so its source and integrity can be explained. |
| What does retention mean for cyber incident logs? | Retention means keeping the logs available for investigation and audit under the bank’s policy. |
| What is the 'live, complete option' for evidence? | The 'live, complete option' is the current, fully assembled evidence set, not a cached partial view or an early alert summary. |

Also worth reading: **2026 OJK/BI AI: Avoid Heavy Models & Procurement Traps**: [2026 OJK/BI AI: Avoid Heavy](https://infonesia.fyi/blog/2026-ojkbi-ai-avoid-heavy-models-procurement-traps.php) · **IDX/OJK Recall: Build vs Buy Scorecard & Coverage Gaps**: [IDX/OJK Recall: Build vs Buy](https://infonesia.fyi/blog/idxojk-recall-build-vs-buy-scorecard-coverage-gaps.php) · **Automating market intelligence for Indonesian e-commerce**: [Automating market intelligence for Indonesian](https://infonesia.fyi/blog/automating-market-intelligence-for-indonesian-e-commerce.php)

### Related reading

- [How Indonesian Fintechs Should Verify the Nasdaq Singapore Desk by Q1 2026](https://infonesia.fyi/blog/how-indonesian-fintechs-should-verify-the-nasdaq-singapore-desk-by-q1-2026.php)
- [Lenovo AI Express: Verify the Live Option Before Indonesian Firms Commit](https://infonesia.fyi/blog/lenovo-ai-express-verify-the-live-option-before-indonesian-firms-commit.php)
- [Indonesia supplier payments: verify Bank Indonesia FAST vs real-time rail caps](https://infonesia.fyi/blog/indonesia-supplier-payments-verify-bank-indonesia-fast-vs-real-time-rail-caps.php)
- [Structured Data Pilot for Indonesian Sites: Test 10 Pages, Wait 90 Days](https://infonesia.fyi/blog/structured-data-pilot-for-indonesian-sites-test-10-pages-wait-90-days.php)
- [Landed Cost Reconciliation for Indonesian Importers: Beating the Post-Order Surprise](https://infonesia.fyi/blog/landed-cost-reconciliation-for-indonesian-importers-beating-the-post-order-surprise.php)
- [Indonesian regulation research: live vs static cuts 38% citation errors](https://infonesia.fyi/blog/indonesian-regulation-research-live-vs-static-cuts-38-citation-errors.php)

### Latest

- [Coretax e-invoicing 2026: build-vs-buy checklist for VAT reconciliation](https://infonesia.fyi/blog/coretax-e-invoicing-2026-build-vs-buy-checklist-for-vat-reconciliation.php)
- [Structured Data Pilot for Indonesian Sites: Test 10 Pages, Wait 90 Days](https://infonesia.fyi/blog/structured-data-pilot-for-indonesian-sites-test-10-pages-wait-90-days.php)
- [Indonesia data privacy 2026: treat $80K-$300K as a quote envelope, not a budget](https://infonesia.fyi/blog/indonesia-data-privacy-2026-treat-80k-300k-as-a-quote-envelope-not-a-budget.php)

Canonical: https://infonesia.fyi/blog/indonesian-bank-cyber-reporting-verify-ojk-deadlines-and-log-evidence.php
Markdown: https://infonesia.fyi/blog/indonesian-bank-cyber-reporting-verify-ojk-deadlines-and-log-evidence.php/index.md
