Business

Indonesia's Cybersecurity Bill Enters First-Level Deliberation: What to Prepare For

November 13, 2026 · 5 min read · Etzal Group Team

Katadata reported on 10 November 2026 that Indonesia's Cybersecurity and Cyber Resilience Bill (Rancangan Undang-Undang Keamanan dan Ketahanan Siber, or RUU KKS) is in first-level deliberation in the House of Representatives (DPR), after all party factions and the government agreed to it in mid-2026. A day earlier, Oleh Soleh, a member of the DPR's Commission I, pressed for the deliberation to be completed.

This is a bill, not a law. Its articles are not in the source we read, the timetable for passage is unknown, and this whole account rests on a single news report. So this article will not describe any obligation, penalty or deadline as if it were in force. What can honestly be discussed is the direction being voiced in parliament, and the work that makes sense whatever the outcome.

What was reported

Every point below comes from Katadata, 10 November 2026.

  • The bill is in first-level deliberation in the DPR. All factions and the government agreed to it in mid-2026.
  • On 9 November 2026 Oleh Soleh urged completion of the bill in order to establish legal authority, mandatory security standards for electronic systems, and fast incident response. He said Indonesia must not "only move after the damage is done".
  • Commission I will summon the National Cyber and Crypto Agency (BSSN) and ask for a report on coordination with the Financial Services Authority (OJK), Bank Indonesia and the Ministry of Communication and Digital Affairs (Komdigi). He said targets could include banking, electricity and public services.
  • Katadata asked BSSN for comment and had received none by the time of publication.
  • The FortiGuard Labs dashboard as of Monday 9 November 2026, 20:00 Jakarta time, showed 2.2 million attacks on Indonesia in 24 hours, 1.2 million of them on finance and banking. That figure counts attacks, not successful breaches.

How to read this news

Three phrases in the lawmaker's statement deserve attention, because they show the direction some legislators want: legal authority, mandatory security standards for electronic systems, and fast incident response.

That is a statement of aims by one member of parliament, not the wording of an article. A bill can change a great deal in deliberation. But if those three ideas survive in any form, operators of electronic systems will one day be asked three plain questions: what do you have, what do you do when an incident happens, and who do you call.

All three can be answered with work that does not depend on the wording of the law.

Could your company be covered

Nobody can say for certain from the sources available. What you can do is assess your own position with two questions.

Do you operate an electronic system that others use? A customer portal, a booking app, a platform used by partners, a system holding many people's data. The phrase "mandatory security standards for electronic systems" sits closest to this group.

Do you supply a sector named as a target? The lawmaker mentioned banking, electricity and public services. If your customers are banks, power companies or government bodies, security demands usually arrive through contracts long before a law requires them. Many suppliers will first meet a new rule as a procurement annex, not as a letter from a regulator.

If the answer to both is no, the Indonesia cybersecurity bill may only touch you indirectly. The steps below are still worth taking, because incidents do not wait for legislation.

Three no-regret steps

They are no-regret because the result is useful whatever is finally passed. This is our practical advice.

1. An asset inventory

You cannot secure or report on something you do not know exists.

  • A list of servers, cloud services, applications, domains and certificates, with an owner named on each row.
  • Mark which face the internet and which hold customer or financial data.
  • Include operational devices such as point-of-sale machines, machine controllers and cameras if they are on the network.
  • Record vendors that hold remote access to your systems.

2. An incident log

Start recording now, small events included.

  • One simple form: when it was discovered, who found it, which system, the impact, the action taken, when service was restored.
  • Keep it somewhere that still opens when the main systems are down.
  • Review it quarterly. The pattern across ten small events often points to one large weakness.

A log like this is the cheapest evidence that a company takes incidents seriously, and it becomes the main input if a reporting duty arrives.

3. Emergency contacts

  • Who has authority to decide a system is shut down, and who deputises.
  • Numbers for key vendors, the cloud provider, the bank and legal counsel, printed and kept outside the systems.
  • One tabletop exercise a year: one scenario, one hour, every decision-maker in the room.

What not to do yet

  • Do not buy tools to comply with a rule that does not exist. The technical standards are unknown. Spending justified by the bill may miss what is eventually required.
  • Do not postpone basic fixes while you wait. Multi-factor authentication, backups that have been tested by restoring them, and system updates need no legislation.
  • Do not write a thick policy. Three pages that are followed are worth more than thirty that are filed.

The trade-off is timing. Waiting for the final text saves effort, but laws of this kind tend to come with a transition period that feels short to a company starting from zero. The three steps above were chosen because they cost little and will not need redoing.

If your estate includes operational devices and factory networks, Etzal Group's IoT and control systems team can help build an inventory that covers both.

The status of the bill can change quickly. Check the latest official announcements from parliament and the government, and confirm the impact on your company with legal counsel once the text is available.

Sources

Frequently asked questions

Is Indonesia's cybersecurity bill in force?

No. According to Katadata on 10 November 2026 it is still in first-level deliberation in parliament, and the timetable for passage is not known.

What obligations will it place on companies?

The article text is not in the source we read, so nothing can be stated yet. A lawmaker has only named aims such as mandatory security standards and fast incident response.

What can be done now without waiting?

An asset inventory, an incident log and an emergency contact list. All three are useful whatever the final law says.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Free consultation

Not sure where to start? We will map the right system for your business, free.