Japan FSA Adopts Common Cyber Incident Reporting Forms in Supervisory Guidelines Effective October 1

Key Takeaways
- Japan's Financial Services Agency has finalized revisions to its supervisory guidelines for major banks and many other financial sectors, replacing its legacy system failure and cyber incident reporting formats with the interagency Common Forms.
- The revisions take effect October 1, 2026, so compliance teams must update incident reporting templates and procedures quickly.
- Seven public comments were received.
Deep Dive
Japan's Financial Services Agency has finalized revisions to its supervisory guidelines for major banks and many other financial sectors, replacing its legacy system failure and cyber incident reporting formats with the interagency Common Forms. The revisions take effect October 1, 2026, so compliance teams must update incident reporting templates and procedures quickly. Seven public comments were received.
The interagency "Agreement on Reporting Procedures, etc., in Case of Damage Caused by Cyberattacks" (originally May 28, 2025) was amended on September 15, 2026. It retains the Common Form for DDoS Attack Cases (Form 1) and the Common Form for Ransomware Cases (Form 2), and adds a new Common Form for Other Cyberattack Cases, etc. (Form 3). The FSA is moving from its own reporting format for computer system failures and cybersecurity incidents to these Common Forms and is revising its Supervisory Guidelines to match. The FSA will also publish the Common Forms and supplementary material, including a correspondence table between old and new form items, under "Application Forms for Various Procedures."
Although the headline guideline is the one for Major Banks, Attachments 2-18 extend the revisions to regional and small and medium-sized financial institutions, insurers, securities firms, money lenders, intermediaries, clearing and transfer institutions, prepaid payment issuers, money transfer providers, crypto asset exchange operators, electronic payment service providers and intermediaries, system financial institutions, and fisheries cooperative credit businesses. The revised guidelines are effective Thursday, October 1, 2026, which leaves only about two weeks after the interagency amendment. The FSA did not state a transition period.
Recommended Actions:
- Review the comparison tables for your sector and the FSA's response to the seven comments (Attachment 1).
- Map existing incident templates to the Common Forms using the FSA's old-to-new item correspondence.
- Update incident response playbooks, escalation matrices, and regulatory notification procedures to specify which form (DDoS, ransomware, or other) applies.
- Train the security operations, IT risk, and compliance staff who complete and file reports.
- Confirm that third-party and outsourced providers can supply the data the new forms require.
- Run a tabletop exercise before or soon after October 1.
The change is largely procedural and aims to reduce duplicate reporting across agencies. The main risk is operational: inaccurate, incomplete, or late reports caused by unfamiliar forms or an incorrect form-type selection could draw supervisory scrutiny. Institutions with several licensed entities or cross-sector groups face added complexity because multiple guideline sets are amended. The new "Other Cyberattack Cases" form widens the range of incidents that need structured reporting, so incident classification procedures should be reviewed.

