Join our Newsletter — 33% off our NHI Course
Home› Guides› Indonesia Cybersecurity Regulations Guide: GR 71/2019, BSSN, vital…
Guide Regulations & Frameworks

Indonesia Cybersecurity Regulations Guide: GR 71/2019, BSSN, vital infrastructure and OJK duties

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 17 min read
On this page

Indonesia has no single cybersecurity act: its cyber duties are spread across a government regulation on electronic systems, rules from the national cyber agency BSSN, a presidential regulation on vital information infrastructure and sector rules such as those of the financial regulator OJK, and an organisation can fall under several at once. Government Regulation No. 71 of 2019 (PP 71/2019, often written GR 71/2019) requires every electronic system operator to run security procedures and report serious attacks. BSSN Regulation No. 8 of 2020 sets the security standards and certification behind that duty, Presidential Regulation No. 82 of 2022 adds a 1 x 24 hour incident report for vital information infrastructure, and commercial banks face OJK's own 24 hour notice. This guide maps who is in scope, the obligations in each instrument, current status, enforcement and what the regime means for service accounts, API keys and AI agents. It is for CISOs, compliance leads and security architects at Indonesian operators and foreign providers serving Indonesia. Personal data duties are covered in the Indonesia PDP Law Guide; this page covers the cyber rules.

Sources: texts and metadata of PP 71/2019, BSSN Regulation 8/2020, Presidential Regulations 28/2021, 82/2022 and 47/2023, Law 1/2024 and Ministerial Regulation 5/2020 as published on the pasal.id legal database, and OJK's own summaries and FAQs, checked 14 November 2026. Translations from Indonesian are ours. Confirm against the official text before relying on any provision.

Key takeaways

  • PP 71/2019 is the base layer: Article 24 requires every electronic system operator to have and run security procedures and facilities, and, where another party's action causes a serious failure or disruption, to secure the information and report at the first opportunity to law enforcement and the relevant ministry or agency.
  • BSSN Regulation 8/2020 sets the standard: systems are classed as strategic, high or low, and SNI ISO/IEC 27001 is the baseline standard for all three, with certification valid for up to three years and an annual surveillance audit.
  • Vital infrastructure reports in 1 x 24 hours: Presidential Regulation 82/2022 requires operators of vital information infrastructure (IIV) to report incidents to their sectoral CSIRT, copying the national CSIRT, within 1 x 24 hours of discovery.
  • Banks have the tightest clock: under OJK's SEOJK 29/SEOJK.03/2022, a commercial bank sends an initial notification within 24 hours of becoming aware of a cyber incident and a full report within 5 working days.
  • Location rules differ by sector: public scope operators must keep systems and data in Indonesia unless the technology is unavailable, private scope operators may store abroad, and banks must keep core banking in Indonesia and need OJK permission to place other systems offshore.

Scope: who and what is covered

PP 71/2019 on the Operation of Electronic Systems and Transactions was enacted on 4 October 2019, promulgated on 10 October 2019 and revoked its predecessor, PP 82/2012 (Article 103). It implements the Electronic Information and Transactions Law (Law 11/2008, the ITE Law), most recently amended by Law 1/2024 of 2 January 2024. Article 2 splits electronic system operators (Penyelenggara Sistem Elektronik, PSE) into two groups, and the split decides several duties.

GroupWho it includes (PP 71/2019 Article 2)Key consequence
Public scope PSEState agencies and institutions appointed by themBusiness continuity plan and in-country storage (Article 20)
Private scope PSEOperators regulated by a ministry or agency, and operators of portals, sites or apps for trade, financial services, paid digital content, communications and social media, search engines, and processing of personal data for electronic transactionsRegistration before use (Article 6); may store in or outside Indonesia (Article 21)
Foreign private PSEOperators that serve users in Indonesia, do business there or offer their systems there (Ministerial Regulation 5/2020, Article 4)Must register and meet the same access and takedown rules
IIV operatorPSEs whose systems are vital information infrastructure in a Presidential Regulation 82/2022 sectorAnnual IIV identification, CSIRT, 1 x 24 hour reporting, annual maturity self-assessment
Commercial bankBanks supervised by OJKPOJK 11/POJK.03/2022, SEOJK 29/SEOJK.03/2022 and, from 1 March 2026, PADK 1/2026

Presidential Regulation 82/2022 on the Protection of Vital Information Infrastructure, set and promulgated on 24 May 2022, lists eight sectors in Article 4: government administration, energy and mineral resources, transportation, finance, health, information and communication technology, food, and defence, plus other sectors the President may set. Each sector has a lead ministry or agency, and the financial sector regulator leads for finance. PSEs in those sectors must identify their IIV at least once a year (Article 6).

BodyRoleSource
BSSN (Badan Siber dan Sandi Negara)National cyber and cryptography agency; assists the President in cyber security and cryptography; head appointed by and reports to the PresidentPresidential Regulation 28/2021, Articles 2 and 3
National CSIRTFormed by the national cyber agency; receives copies of IIV incident reportsPresidential Regulation 82/2022, Articles 12 and 13
Sectoral CSIRTsFormed by ministries and agencies; receive IIV incident reportsPresidential Regulation 82/2022, Article 12
Ministry of Communication and Digital Affairs (Komdigi)Registers private PSEs, orders access and takedownsMinisterial Regulation 5/2020
OJKFinancial services regulator; IT and cyber rules for banksPOJK 11/POJK.03/2022, SEOJK 29/SEOJK.03/2022

Presidential Regulation 28/2021, set on 13 April 2021, replaced the earlier BSSN regulations (Presidential Regulations 53/2017 and 133/2017).

Key obligations

PP 71/2019: security for every operator

  • Reliable and secure operation: Article 3 requires electronic systems to be operated reliably and securely, and Article 23 requires the system's components to be secured.
  • Security procedures and facilities (Article 24(1) and (2)): have and run procedures and facilities to avoid disruption, failure and loss, including systems to prevent and respond to threats and attacks.
  • Reporting serious attacks (Article 24(3)): when another party's action causes a failure or disruption with serious impact, secure the electronic information and documents and report at the first opportunity to law enforcement and the relevant ministry or agency. The regulation sets no hour count, so treat "first opportunity" as hours, not days.
  • Further detail from the cyber agency (Article 24(4)): the security system is detailed in a regulation of the head of the cyber security agency, which is BSSN Regulation 8/2020.
  • Personal data failures (Article 14(5)): written notice to the data owner. The PDP Law now adds a 3 x 24 hour notice; see the Indonesia PDP Law Guide.
  • Public scope operators (Article 20): keep a business continuity plan, manage and store systems and data in Indonesia unless the storage technology is not available domestically (a committee that includes the cyber agency decides), and classify data by risk when using third-party services.

BSSN Regulation 8/2020: categories, standards and certification

BSSN Regulation 8/2020 on Security Systems in the Operation of Electronic Systems was enacted on 19 November 2020 and promulgated on 23 November 2020.

Category (Articles 6 to 8)MeaningRequired standard (Articles 9 to 11)
Strategic (strategis)Serious impact on public interest, public services, state operations, or defence and securitySNI ISO/IEC 27001 plus cyber standards set by BSSN and the relevant ministry or agency
High (tinggi)Limited impact on a particular sector or regionSNI ISO/IEC 27001 and/or a BSSN standard, plus the ministry or agency standard
Low (rendah)All other systemsSNI ISO/IEC 27001 or a BSSN standard
  • Self-assessment: operators assess their own category and report it to BSSN for verification; the head of BSSN sets the final category (Articles 7 and 8).
  • Fallback: where BSSN or ministry standards are not yet issued, SNI ISO/IEC 27001 applies (Articles 10 and 11). Operators may use the Indeks KAMI assessment to prepare (Article 12).
  • People: operators implement the security management system with Indonesian citizens, or use Indonesian experts or BSSN-recognised consultancies (Articles 13 and 15).
  • Certification: issued by a BSSN-recognised certification body after an audit, valid for up to three years and renewed at least three months before expiry (Article 28). Certified systems need an annual surveillance audit and a special audit after an incident (Article 33); a failed surveillance audit gives up to 90 calendar days to fix (Article 34).

For building the management system itself, see the ISO 27001 Certification Guide.

Presidential Regulation 82/2022: vital information infrastructure

DutyRequirementArticle
Identify IIVAt least once a year6
Security standardsApply standards set by the relevant ministry or agency and/or the national cyber agency9
Risk managementImplement cyber risk management effectively10
Organisational CSIRTEstablish one11
Incident reportingTo the sectoral CSIRT, copied to the national CSIRT, within 1 x 24 hours of discovery13
Incident handlingRecover, share information, prevent wider impact14
ReadinessIncident response and business continuity plans, and simulations15
MaturitySelf-assess cyber security maturity at least once a year22

Presidential Regulation 47/2023 on the National Cyber Security Strategy and Cyber Crisis Management (20 July 2023) sits above this. It sets a five-year national action plan and a three-phase crisis model (before, during and after). The President declares a cyber crisis status on the proposal of the head of the agency and forms a task force, and PSEs must act on early warnings and take part in post-crisis work. See the Building a CSIRT Guide for setting up the organisational CSIRT.

OJK: commercial banks

  • POJK 11/POJK.03/2022 on IT operations by commercial banks replaced POJK 38/POJK.03/2016. OJK's FAQ states that core banking must stay in Indonesia, that other systems may go offshore only with OJK permission (OJK decides within three months and the bank must implement within six months or the permit lapses), and that cloud providers are IT service providers subject to the third-party rules even when offshore.
  • SEOJK 29/SEOJK.03/2022 on cyber resilience and security, issued and effective 27 December 2022, requires annual inherent risk and maturity assessments as of end-December, vulnerability analysis followed by penetration testing, scenario-based testing at least once a year with results to OJK within 10 working days, a cyber unit independent of IT management, and a CSIRT led by that unit.
  • Incident reporting: initial notification to the bank's supervisor within 24 hours of becoming aware, and a fuller report through OJK's system within 5 working days. If another authority has a shorter deadline, report to OJK at the same time.
  • PADK 1/2026, in force from 1 March 2026, details POJK 11/2022 further, including simpler permits for offshore data centre and disaster recovery placement. It refers banks to the cyber SEOJK for board and committee responsibilities.

For how these fit with other regional financial rules, see the Financial Services Cyber Regulation Map and the Bank Negara Malaysia RMiT.

Reporting clocks at a glance

TriggerDeadlineRecipientSource
Serious failure caused by another party (any PSE)At the first opportunityLaw enforcement and relevant ministry or agencyPP 71/2019 Article 24(3)
Incident affecting IIV1 x 24 hours from discoverySectoral CSIRT, copy to national CSIRTPresidential Regulation 82/2022 Article 13
Bank cyber incident, initial24 hours from awarenessOJK supervisorSEOJK 29/SEOJK.03/2022
Bank cyber incident, report5 working daysOJK reporting systemSEOJK 29/SEOJK.03/2022
Personal data protection failure3 x 24 hoursData subjects and the supervisory agencyLaw 27/2022 (PDP) Article 46
Access request for supervision or law enforcement (private PSE)5 calendar daysRequesting ministry, agency or law enforcementMinisterial Regulation 5/2020

One incident can trigger four of these at once, for example ransomware at a bank that is also IIV and holds personal data. Build one decision sheet with all clocks; see the Breach Notification Laws by Country Guide.

Timeline and current status

  • 10 October 2019: PP 71/2019 promulgated, replacing PP 82/2012.
  • 23 November 2020: BSSN Regulation 8/2020 promulgated.
  • 24 November 2020: Ministerial Regulation 5/2020 on private PSEs promulgated (amended in 2021).
  • 14 April 2021: Presidential Regulation 28/2021 on BSSN promulgated.
  • 24 May 2022: Presidential Regulation 82/2022 on IIV protection.
  • 27 December 2022: SEOJK 29/SEOJK.03/2022 issued and effective.
  • 20 July 2023: Presidential Regulation 47/2023 on national strategy and crisis management.
  • 2 January 2024: Law 1/2024, second amendment to the ITE Law, adding government orders to PSEs (Article 40A).
  • 1 March 2026: OJK PADK 1/2026 in force for commercial banks.

As of 14 November 2026 the legal database lists each instrument above as in force, with Ministerial Regulation 5/2020 marked as amended. Ministries and BSSN may issue further sector standards under these instruments, so check for new rules from your sector's lead ministry before relying on the fallback to SNI ISO/IEC 27001.

Enforcement and penalties

InstrumentEnforcement
PP 71/2019Article 100 provides administrative sanctions for breaches of listed articles, including registration (Article 6), data storage (Article 21) and security (Articles 23 and 24); the procedure is set by ministerial regulation (Article 101)
Ministerial Regulation 5/2020Escalating steps for unregistered operators up to access blocking by internet service providers on the Minister's order; fines per missed deadline for user-generated content platforms that miss takedown orders (1 x 24 hours, or 4 hours for urgent requests)
BSSN Regulation 8/2020Written reprimand to operators that breach listed obligations, with 15 working days to act (Articles 37 and 39); suspension or revocation of recognition for certification bodies
Law 1/2024 (ITE amendment)Administrative sanctions for failing to follow government orders under Article 40A
OJK rulesSupervisory action under OJK's banking powers; cyber risk results feed the bank soundness assessment

For most operators the practical risk is access blocking and regulatory findings rather than large fines. For banks, cyber results flow into supervisory ratings, which affects the board directly.

What it means for AI agents and non-human identities

None of these instruments names service accounts or AI agents, but each one reaches them through its security and reporting duties.

  • Security procedures cover machine access: PP 71/2019 Article 24 and the ISO/IEC 27001 baseline in BSSN Regulation 8/2020 apply to every account that can change the system, including API keys, CI/CD service principals and integration tokens. Keep an owned inventory; see the Non-Human Identity Guide.
  • Offshore placement includes identity planes: where a bank's systems run in an offshore data centre or cloud, the secrets stores and identity providers that control them are part of the arrangement OJK assesses. Document where keys and machine credentials live.
  • Incident clocks start on machine compromise: a leaked cloud key that leads to data access can start the 24 hour OJK clock and the IIV clock. Rotation and revocation runbooks must be fast enough to contain within those windows.
  • AI agents acting on systems: an agent with write access to an IIV system is part of that system's attack surface, so include agent identities in the annual IIV identification, maturity self-assessment and scenario-based tests.
  • Testing access: SEOJK 29/2022 scenario tests and penetration tests need controlled test accounts; create, monitor and remove them as part of the test plan.

Compliance steps

  1. Classify yourself: decide whether you are public or private scope, whether you must register with Komdigi, which BSSN category each system falls into, whether any system is IIV, and whether OJK rules apply.
  2. Map data location: record where each system and its backups, keys and logs are stored, against Article 20, Article 21 and OJK placement rules.
  3. Close the standard gap: assess against SNI ISO/IEC 27001 (Indeks KAMI is a starting point), then any BSSN or sector standard; plan certification for strategic systems.
  4. Stand up the CSIRT and reporting: name the organisational CSIRT, sectoral CSIRT contacts, OJK supervisor contacts and law enforcement routes; build a single reporting decision sheet with every clock.
  5. Test: run an annual scenario exercise that rehearses the 24 hour reports (mandatory for banks) and the IIV simulation duty.
  6. Self-assess and report: complete the annual IIV identification and maturity self-assessment, and for banks the end-December inherent risk and maturity assessments.
  7. Monitor change: track new BSSN, ministry and OJK instruments quarterly; status in this field changes.
Indonesian dutyISO/IEC 27001:2022 Annex A (closest)NIST CSF 2.0
Security procedures and facilities (PP 71 Art. 24(1)-(2))A.5.1 policies, A.8 technological controlsGV.PO-01, PR.PS-01
Incident reporting (PP 71 Art. 24(3), Perpres 82 Art. 13, SEOJK 29)A.5.24, A.5.26RS.CO-02
Risk management and maturity (Perpres 82 Arts. 10, 22; SEOJK 29)Clause 6.1 risk assessmentID.RA-05, GV.RM-01
IR and continuity plans, simulations (Perpres 82 Art. 15)A.5.29, A.5.30ID.IM-04, ID.IM-02
Third-party and cloud providers (POJK 11/2022)A.5.19 to A.5.23GV.SC-05

Common failure patterns

  • Treating Indonesia as "PDP only": teams build a 3 x 24 hour privacy process and miss the 1 x 24 hour IIV report and the 24 hour OJK notice, which can arrive first.
  • Self-assessing the BSSN category too low: a system that supports public services classed as low avoids certification on paper but not in a review, since BSSN sets the final category.
  • Reading "first opportunity" as optional: Article 24(3) has no hour count, but delay is hard to defend once law enforcement or the ministry asks when you knew.
  • Offshore drift: a bank adds a SaaS or AI service that processes production data offshore without the OJK permit process.
  • No named contacts: the sectoral CSIRT, OJK supervisor and Komdigi liaison are not in the incident contact sheet, so reports go late or to the wrong body.
  • Machine credentials outside scope: the ISO/IEC 27001 scope covers user accounts but not API keys, CI/CD tokens or agent identities, which are then missing from the asset register and the incident runbooks.

Practitioner checklist

  • Record your PSE scope (public or private) and Komdigi registration status.
  • Assign each system a BSSN category and keep the self-assessment report.
  • Confirm whether any system is IIV and complete the annual identification.
  • Map storage locations for systems, backups, keys and logs against the location rules.
  • Align the security management system to SNI ISO/IEC 27001 and plan certification for strategic systems.
  • Build one reporting decision sheet: first opportunity, 1 x 24 hours, 24 hours plus 5 working days, 3 x 24 hours.
  • Name the organisational CSIRT and record sectoral CSIRT and OJK contacts.
  • Run an annual scenario exercise that includes a machine credential compromise.
  • Include service accounts, API keys and AI agent identities in asset registers and risk assessments.
  • Review new BSSN, ministry and OJK rules every quarter.

Standards and references

Related NHI Mgmt Group resources: Indonesia PDP Law Guide · Malaysia Cyber Security Act 2024 · Thailand Cybersecurity Act · Critical Infrastructure Regulation Map. This guide summarises Indonesian cybersecurity regulations and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.