Join our Newsletter — 33% off our NHI Course
Home› Guides› China Cybersecurity Incident Reporting Measures Guide: One-Hour and…
Guide Regulations & Frameworks

China Cybersecurity Incident Reporting Measures Guide: One-Hour and Four-Hour Reporting Rules Explained

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

Since 1 November 2025, a network operator in China that suffers a serious cybersecurity incident has as little as one hour to report it, and multinational incident response plans written around 72-hour regimes are not built for that. The Measures for the Administration of National Cybersecurity Incident Reporting (国家网络安全事件报告管理办法), issued by the Cyberspace Administration of China (CAC), set a single national procedure: classify the incident against a four-level grading annex, report anything graded 较大 (serious) or above within 1, 2 or 4 hours depending on who you are, supplement the report as facts emerge, and file a summary report within 30 days of closing the incident. This guide explains the scope, the thresholds, the report contents, the link to the amended Cybersecurity Law's penalties, and how to build a China reporting runbook. It is for CISOs, incident response leads and compliance teams of companies with networks or services in mainland China. Status: summarised from the CAC's published text of the Measures and of the amended Cybersecurity Law, checked 27 October 2026. English renderings of Chinese terms are our own.

Key takeaways

  • Grade first, then report. Operators must grade each incident against the Annex (特别重大, 重大, 较大, 一般), and the mandatory reporting procedure applies to incidents graded 较大 or above (Article 4).
  • The clock depends on who you are. Critical information infrastructure (CII) operators report within 1 hour, central government departments within 2 hours, and all other network operators to the provincial cyberspace office within 4 hours.
  • Partial reports are expected. If cause, impact or trend are not yet known, the operator reports its identity, system details, time, place, type, level, impact and measures first, and supplements the rest later (Article 7).
  • Suppliers must be contracted to help. Article 5 requires operators to oblige security, maintenance and other service providers, by contract or similar means, to report incidents they detect promptly and help the operator report.
  • Timely reporting can reduce penalties. Late, missed, false or concealed reports causing serious harm attract heavier penalties, while operators that took reasonable measures, followed their plan and reported on time may receive lighter or no penalties (Articles 10 and 11).

Scope: who and what is covered

The Measures rest on the Cybersecurity Law, the Data Security Law, the Personal Information Protection Law and the Regulations on Critical Information Infrastructure Security Protection (Article 1). They apply to network operators that build or operate networks, or provide services through networks, within the territory of China (Article 2). For the wider framework see the China Cybersecurity Law Guide.

ElementText of the Measures (paraphrased)Practical reading
Who must report网络运营者 (network operators) in China (Article 2)Includes foreign-invested companies operating systems or services in mainland China, not only Chinese firms
What is an incidentAn event caused by human factors, attack, vulnerabilities, software or hardware defects or failures, or force majeure that harms networks, information systems or their data and business applications and has a negative effect on the state, society or economy (Article 12)Outages and data leaks count, not only attacks
Grading basisThe Annex, based on national standard GB/T 20986-2023 (Article 12)Align internal severity levels to the Annex rather than mapping afterwards
CoordinationNational CAC coordinates nationally; provincial cyberspace offices within their regions (Article 3)Know which provincial office is "local" for each Chinese entity
State secretsIncidents involving state secrets follow separate rules (Article 13)Out of scope of this guide

Incident grading thresholds (Annex)

Meeting any one typical criterion places an incident at that level; "以上" (and above) includes the stated figure.

Criterion特别重大 (especially major)重大 (major)较大 (serious)
CII interruptionWhole operation 6 hours or more, or main functions 24 hours or moreWhole operation 1 hour or more, or main functions 3 hours or moreWhole operation 10 minutes or more, or main functions 30 minutes or more
Portal and key news site unavailabilityProvincial-level or higher party and government portals or central key news sites, 24 hours or morePrefecture-level or higher portals of party, government, enterprises and institutions, or provincial key news sites, 6 hours or moreSame classes of site, 2 hours or more
Personal information leaked100 million people or more10 million or more1 million or more
Core or important dataLeaked, stolen, tampered with or counterfeited, extremely severe threat to national security and social stabilitySame, serious threatImportant data leaked or stolen, relatively serious threat
Direct economic lossRMB 100 million or moreRMB 20 million or moreRMB 5 million or more
Harmful content after defacementFor example on a homepage 6 hours or more, 100,000 reposts or 1 million viewsHomepage 2 hours, 10,000 reposts or 100,000 viewsHomepage 30 minutes, 1,000 reposts or 10,000 views

一般 (general) incidents are those below these thresholds that still threaten or affect national security, social order, economic development or the public interest. They are not in the Article 4 mandatory procedure, but sector rules and regulator instructions may still require reporting, and suspected crimes must be reported to public security organs regardless of grade.

Key obligations

Reporting deadlines (Article 4)

Operator typeReport toDeadlineOnward escalation for 重大 and 特别重大
CII operatorIts protection work department (保护工作部门) and public security organsAs soon as possible, no later than 1 hourProtection department reports to national CAC and the State Council public security department no later than 30 minutes after receipt
Central and state organ departments and directly affiliated unitsTheir departmental cyberspace work bodyNo later than 2 hoursDepartment reports to national CAC no later than 1 hour
All other network operatorsProvincial cyberspace office where the operator is located (属地省级网信部门)No later than 4 hoursProvince reports to national CAC no later than 1 hour

Where industry regulators have their own reporting rules, those also apply, so a bank, telecoms carrier or energy company may face parallel sector channels.

Report contents (Article 7)

  1. Name of the entity and basic information on the affected facilities and systems.
  2. Time and place of discovery, incident type, grade, impact and harm, and measures taken; for ransomware, also the ransom amount, payment method and date demanded.
  3. Likely development and further harm.
  4. Preliminary cause analysis.
  5. Leads for tracing, including attacker information, attack path and vulnerabilities exploited.
  6. Planned further measures and any requests for support.
  7. Status of evidence preservation.
  8. Other information to report.

Items 1 and 2 may be reported first where the rest is not yet clear, with timely supplements and reports of significant new developments.

After the incident

  • Summary report (Article 8): within 30 days after handling ends, submit a summary report through the original channel covering cause, response, harm, accountability, remediation and lessons learned.
  • Channels (Article 9): the 12387 cybersecurity incident reporting hotline, plus website, email and fax channels published by the authorities.
  • Service providers (Article 5): contracts with security service, maintenance and other providers must require them to report incidents they find and assist the operator.
  • Emergency plans (Cybersecurity Law Article 27): the amended law requires operators to maintain incident emergency plans, handle vulnerabilities, malware, attacks and intrusions promptly, activate the plan when an incident occurs and report to the competent authorities as required.

Timeline and current status

DateEvent
11 September 2025Measures adopted by the CAC
15 September 2025Measures published on the CAC website
28 October 2025NPC Standing Committee adopts the decision amending the Cybersecurity Law
1 November 2025Measures take effect (Article 14)
29 December 2025Amended Cybersecurity Law text published in the CAC laws column
27 October 2026Status check for this guide: Measures in force; no amendment found in the CAC normative documents column

Article numbers for the Cybersecurity Law in this guide follow the amended text as published by the CAC. Older English translations use the 2016 numbering, so check which version a contract or policy cites.

Enforcement and penalties

The Measures do not set fines themselves. Article 10 refers to penalties under existing laws and administrative regulations, and provides for heavier treatment where late, missed, false or concealed reporting causes serious harm. Article 11 allows lighter or no penalties where the operator took reasonable protective measures, handled the incident under its emergency plan, effectively prevented or reduced harm and reported on time. The main penalty route is Article 61 of the amended Cybersecurity Law, which covers failure to perform the security protection duties in Articles 23 and 27, including incident reporting.

Situation (Cybersecurity Law Article 61)EntityDirectly responsible managers and staff
Ordinary operator, first instanceCorrection order, warning, RMB 10,000 to 50,000No separate figure stated for this tier
Ordinary operator refuses to correct or causes harmRMB 50,000 to 500,000RMB 10,000 to 100,000
CII operator breaching the CII duties in Articles 35, 36, 38 and 40RMB 50,000 to 100,000; RMB 100,000 to 1,000,000 if it refuses to correct or causes harmRMB 10,000 to 100,000
Serious consequences, such as large-scale data leaks or partial loss of CII functionRMB 500,000 to 2,000,000RMB 50,000 to 200,000
Especially serious consequences, such as loss of main CII functionsRMB 2,000,000 to 10,000,000RMB 200,000 to 1,000,000

The personal liability column matters for multinational boards: named managers in the Chinese entity carry their own exposure, which is an argument for clear delegation of reporting authority.

What it means for AI agents and non-human identities

  • Credential compromise often drives the grade: a stolen service account or API key that exposes customer records can cross the 1 million person threshold quickly. Tie non-human identity alerts to the grading process so data volumes reachable by the compromised identity are known in minutes. See the Detection Engineering for Non-Human Identities Guide.
  • Tracing leads include machine paths: Article 7 asks for the attack path and exploited vulnerabilities. Keep token issuance, OAuth grant and workload identity logs for China systems so you can describe the path inside the first report.
  • Agents can cause qualifying incidents: the definition covers human factors and software defects, not only attacks. An AI agent that deletes data or takes a service offline through an erroneous action is a potential incident to grade.
  • Automate the clock, not the judgement: automation can open a China reporting ticket, start the 1 or 4 hour timer and collect items 1 and 2 of Article 7, but grading and submission should stay with named people.
  • Supplier contracts cover MSSPs and AI service providers: any provider operating detection, maintenance or agent platforms on your China systems falls within Article 5 and needs a reporting clause.

Compliance steps

  1. Classify each Chinese entity: CII operator, central government unit or other network operator, and identify the protection department or provincial cyberspace office for each.
  2. Adopt the Annex grades: map your severity scale to 特别重大, 重大, 较大 and 一般, with the numeric thresholds embedded in triage forms.
  3. Pre-fill reports: keep entity and system details (Article 7 item 1) ready for every in-scope system so a first report can go within the hour.
  4. Delegate authority locally: name who in the Chinese entity can file a report without waiting for global approval, with deputies for nights and holidays.
  5. Update supplier contracts: add Article 5 reporting and assistance obligations to security, maintenance, cloud and managed service agreements.
  6. Preserve evidence early: evidence preservation status is a report item, so build preservation steps into the first hour.
  7. Plan the 30-day summary: assign ownership of the summary report and track the deadline from the date handling ends.
  8. Exercise it: run a tabletop where a ransomware incident hits a China system at night and the team must grade and report within 4 hours (1 hour for CII).

Measuring it

  • Time to grade: minutes from detection to an Annex grade decision.
  • Time to first report: against the 1, 2 or 4 hour deadline, for each reportable incident and exercise.
  • Supplement timeliness: hours between new material facts and the supplementary report.
  • Summary report on time: percentage filed within 30 days of the end of handling.
  • Contract coverage: percentage of China service providers with Article 5 clauses.

Framework mapping

ObligationNIST CSF 2.0NIST SP 800-53 Rev 5ISO/IEC 27001:2022 Annex A
Grading incidentsRS.MA-03IR-45.25 Assessment and decision on information security events
Reporting to authoritiesRS.CO-02IR-65.5 Contact with authorities, 5.26 Response to information security incidents
Supplier reporting dutiesGV.SC-05SR-85.20 Addressing information security within supplier agreements
Emergency plansRS.MA-01IR-85.24 Information security incident management planning and preparation
Evidence and summary reportRS.AN-03IR-45.27 Learning from information security incidents, 5.28 Collection of evidence

Common failure patterns

  • Global approval chains: the Chinese entity waits for headquarters sign-off, and a 4-hour deadline passes overnight.
  • Severity scales that do not translate: internal "P2" incidents that meet a 较大 threshold, such as a 30-minute loss of main CII functions, are not reported.
  • Counting records late: the number of individuals affected is unknown for days, so the grade and the reporting decision slip.
  • Ignoring non-attack incidents: outages from faults or failed changes are not graded, though the definition covers defects and failures.
  • Silent suppliers: an MSSP sees an intrusion but has no contractual duty to tell the operator quickly.
  • Forgetting the summary: the 30-day summary report is missed once the incident is closed internally.

Practitioner checklist

  • Each Chinese entity is classified and its reporting authority identified.
  • Internal severity levels map to the four Annex grades with thresholds in the triage form.
  • First report templates with Article 7 items 1 and 2 are pre-filled per system.
  • Local staff are authorised to file reports within 1, 2 or 4 hours, with deputies.
  • Supplier contracts carry Article 5 reporting and assistance clauses.
  • Non-human identity and token logs for China systems are retained to support tracing.
  • Suspected crimes are routed to public security organs regardless of grade.
  • Summary reports are tracked to the 30-day deadline.
  • Sector regulator reporting duties are mapped alongside the Measures.

Standards and references

Related NHI Mgmt Group resources: Breach Notification Laws by Country Guide · China Cybersecurity Law Guide · China Data Security Law and Network Data Security Regulations Guide · Incident Response Plan Template. This guide summarises China's National Cybersecurity Incident Reporting Measures and related provisions of the Cybersecurity Law 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 27 October 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.