Personal Data Breach Report and Notice (Japan) | Meet the PPC and Data Subject Deadlines

Business & Strategy

Personal Data Breach Report and Notice (Japan) | Meet the PPC and Data Subject Deadlines

Intermediate | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)

Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.

Under Japanese law, a reportable personal data breach (including a suspected one) must be reported to the PPC (Personal Information Protection Commission), and the people affected notified. Counting from the day the company becomes aware, this template lines up the preliminary report (about 3 to 5 days), final report (30 days, or 60 if a wrongful purpose is suspected) and when to notify. Rules can change, so check the PPC's latest guidance first. Check in turn whether it is personal data, a breach, strongly encrypted, or one of four reportable cases. An announcement has no legal deadline; it can substitute when notice is hard. Traps include waiting for certainty before the preliminary report, counting from the end of the investigation, unclear contractor roles and a delayed notice; each gets a check and a fix. Start by opening the PPC guidance and noting the incident and discovery date on page 1. It has four A4 pages, 5 task columns, 4 parent tasks and 12 subtasks.

0 Likes 0 Copies Author: WeProcess
personal data breach breach report Japan PPC Japan notify data subjects information security
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Read the whiteboard text as plain text

Personal Data Breach Report and Notice (Japan)

How to use (4 pages): ① On page 1, check whether it is reportable with the five steps and a table → ② On page 2, gather the facts with 5W1H and check the traps → ③ On page 3, line up the dates from discovery to the final report and set deadlines and owners → ④ On page 4, write the notice and set contact and prevention owners

1/4 Check if reportable

① Incident and goal (start writing here)

  • What you are using it for e.g. A contractor told us customer data may have leaked. Move the report and notices forward within the deadlines
  • The incident and the day you noticed e.g. Customer data of a member service. Noticed on day 1 (Monday) at 10:00
  • Who gathers and who is responsible e.g. Legal, IT and the customer help desk. The person responsible for personal data management leads

② Five steps to decide whether to report (from the top)

  1. Personal data? Is it personal information organized in a database or similar? If a wrongful purpose is suspected, personal information meant to become personal data (for example, data still arriving through a web form) can also be covered. Check the latest guidance e.g. Names and emails in the customer system → yes
  2. Breach? Is there a leak, loss or damage, or a risk of one? e.g. It may have been visible to people outside the company → yes
  3. Protected? Strong encryption and similar safeguards can exempt it e.g. It was not encrypted → next step
  4. One of the 4 cases? Check the table in ③ for the four cases that require a report e.g. Possibly over 1,000 people → yes
  5. Report and notify If yes, go to the preliminary and final reports and notice to individuals. If no, still record what happened e.g. Line up the deadlines on page 3

③ The 4 cases that require a report (any one means report; check the latest guidance)

Applies? Basis (what is known) Who checks
Special care-required info e.g. Does not apply e.g. No medical history or similar e.g. IT owner
Financial loss e.g. Does not apply e.g. No credit card numbers e.g. Legal owner
Wrongful purpose e.g. Possible e.g. Possible external unauthorized access (under investigation) e.g. IT owner
Over 1,000 people e.g. Applies e.g. About 1,200 people e.g. Legal owner

2/4 Gather the facts

④ Gather the facts behind ③ using 5W1H (write “under investigation” if unknown)

  • Breach incident
    • What Data involved e.g. The items that may have leaked (names, emails) and the expected number of records
    • Why Cause e.g. The likely cause. If not certain, write “under investigation”
    • Who Who is affected e.g. The affected people (about 1,200 customers) and the first person to notice
    • When Date and time e.g. When the company became aware, and when it seems to have happened
    • Where System e.g. Which system, contractor or device it happened on
    • How How found e.g. How you found out (a customer inquiry, a call from the contractor)

⑤ Trap: stalling at the “possible leak” stage

  • What happens: e.g. You wait until the leak is confirmed and miss the preliminary report deadline
  • How to check: e.g. Even with “under investigation” left in ④, check whether any of the four cases in ③ may apply
  • How to prevent: e.g. Send the preliminary report while it is still a possible leak, and add findings in the final report
  • Owner: e.g. The legal owner reviews ④ every morning

⑥ Trap: miscounting the preliminary report deadline

  • What happens: e.g. You count from the day the investigation ends, and the deadline is off by days
  • How to check: e.g. See that the date and time anyone at the company noticed is recorded under “When” in ④
  • How to prevent: e.g. Count the day you noticed as day 1 and write the deadline in ⑨. Check how to count in the latest guidance
  • Owner: e.g. The legal owner sets the start date in ⑧

⑦ Trap: unclear roles for a breach at a contractor

  • What happens: e.g. The contractor and your company each think the other will report, and nobody does
  • How to check: e.g. See whether the contract sets a contact point and a deadline for informing you
  • How to prevent: e.g. Have the contractor inform you, decide that your company reports and notifies, and write it in ⑩
  • Owner: e.g. The person who handles the contractor

3/4 Line up the deadlines

⑧ Line up the dates from the day you noticed to the final report, using the facts from ④ to ⑦ (timeline)

  1. Start (day you noticed) e.g. Day 1 (Monday), 10:00, the contractor called. Count from here
  2. Phase 1 Escalate internally e.g. Escalate to the person responsible on day 1 and decide in ② and ③ whether it is reportable
  3. Phase 2 Preliminary report e.g. About 3 to 5 days. Put “under investigation” for items you do not know
  4. Phase 3 Notify individuals e.g. Promptly, depending on the situation. Use the notice in ⑪ to ⑬
  5. Phase 4 Finish the investigation e.g. Confirm the cause and the scope of impact, and draft the prevention plan
  6. Goal (final report) e.g. Within 30 days (60 days if a wrongful purpose is suspected). Check the latest guidance

⑨ Target deadlines, timing and owners (fill in the dates from ⑧)

Target deadline or timing Owner Planned date (record done in ⑭)
Preliminary report e.g. About 3 to 5 days from the day you noticed e.g. Legal owner e.g. File on day 3
Final report e.g. Within 30 days (60 if a wrongful purpose is suspected) e.g. Legal owner e.g. Plan to file on day 28
Notice to individuals e.g. Promptly, depending on the situation (no fixed number of days) e.g. Customer help desk owner e.g. Send by email on day 7
Announcement e.g. No legal deadline. Decide it, for example, as a substitute when notice is hard e.g. PR owner e.g. Decide on day 5 whether to release it the same day as the notice

⑩ Roles with the contractor (write this from the trap in ⑦)

  • What the contractor does e.g. Tell your company as soon as they notice, help with the investigation and hand over records
  • What your company does e.g. Your company reports to the PPC and notifies individuals. If the contractor informs your company, the contractor need not report or notify individuals, and the company that receives the notice reports (check the General Rules guidelines)
  • What to agree in advance e.g. Check in the contract or a memo the contact point, the deadline for informing you and how to hand over investigation records

4/4 Report and notify

⑪ What happened (write from the 5W1H in ④ and finish by the notice date in ⑨)

  • e.g. When, what information, and how many people may have been affected. Also the known cause and whether impersonation or other secondary harm is possible
  • e.g. Write “under investigation” for what is not known, and only what is certain
  • e.g. What your company has already done (for example, shut down the affected system)
  • e.g. An apology, and when you will next update them

⑫ What to ask of them (only what they can do)

  • e.g. If a message claiming to be from us arrives, do not click the link; open our official site or app instead
  • e.g. If you see a charge you do not recognize, tell your card company or our help desk
  • e.g. If the password may also have leaked, change it, and change it anywhere else you use the same one
  • e.g. If they need to do nothing, say so

⑬ Contact point

  • e.g. A dedicated phone number and its hours
  • e.g. An email address and how many days a reply takes
  • e.g. A page with frequently asked questions
  • e.g. Add that we never ask for passwords or card numbers by phone or email

⑭ Contacts, owners and done dates (match the deadlines in ⑨)

What to tell or do Owner Done date
Individuals e.g. Send the notice from ⑪ to ⑬ by email e.g. As in ⑨ (customer help desk owner) e.g. Sent on day 7
PPC e.g. Preliminary and final reports (by the deadlines in ⑨). Depending on the business, the report may go to the ministry in charge, so check the PPC guidance e.g. As in ⑨ (legal owner) e.g. Filed the preliminary report on day 3
Contractor and internal e.g. Ask the contractor for material for the final report. Report to executives daily e.g. IT owner e.g. Report at 10:00 every morning
Prevention e.g. Fix the cause and review the contractor checks e.g. Information security lead e.g. Write the plan before the final report

⑮ Trap: the notice to individuals gets pushed back (check before sending ⑪ to ⑬)

  • What happens e.g. Busy with the report to the PPC, you delay the notice, and worry and inquiries grow
  • How to check e.g. See whether the Individuals row in ⑭ has a send date and an owner
  • How to prevent e.g. Start the draft of ⑪ to ⑬ the same day as the preliminary report. For people who are hard to reach, decide a substitute such as an announcement

Task board contents

Not started 16 items

Is it reportable?

On page 1, write the purpose and scope of the incident, follow the five steps to see whether a report is needed, and check the four cases in the table. Done when you can write whether it is reportable and why. Press Ctrl+F (⌘F on Mac) and type “3/4” to jump to page 3.

Open PPC guidance

Open it as soon as you notice the incident, without waiting for the investigation. On the PPC website, read the breach reporting guidance: the four cases that require a report, the preliminary and final report deadlines, and whether the report goes to the PPC or to the ministry in charge of your business (delegated authority). Then write the incident name and discovery date in section ①. If the guidance differs from the examples in sections ③ and ⑨, rewrite them to match.

Walk the 5 steps

Follow the five steps in section ② from the top. For each step, write yes, no, or under investigation, with the basis in one line. Done when you reach step 5.

Check the 4 cases

In the table in section ③, write for each of the four cases whether it applies, the basis, and who checks. If even one is yes or possible, treat it as reportable, then gather facts on page 2 while you start lining up deadlines on page 3.

Gather the facts

On page 2, re-collect the facts behind the judgment in ③ using 5W1H, and check the three traps that are easy to fall into. Done when every unknown item has an owner and the trap notes are filled in.

Gather 5W1H facts

In the six questions in section ④, write only what you know. Write “under investigation” for what you do not know, and leave no blanks.

Check the 3 traps

For each trap in sections ⑤ to ⑦, rewrite what happens, how to check, and how to prevent it for your situation, and write an owner for each that applies.

Assign open items

For each question marked “under investigation” in section ④, write who investigates and the date the answer is due. Done when they are scheduled to be filled in before the final report.

Line up deadlines

On page 3, line up the dates from the day you noticed to the final report, and decide the deadlines for the preliminary and final reports and the timing and owner for notice and announcement. Until the preliminary report date is set, do this before other work.

Draw the timeline

In the six steps in section ⑧, write by day number: the day you noticed, the day you escalated internally, the preliminary report, notice to individuals, the end of the investigation, and the final report.

Deadline table

In the table in section ⑨, write the target timing and owner for the preliminary report, final report, notice to individuals, and announcement. Check deadlines against the PPC's latest guidance first. Done when all four rows have an owner.

Contractor roles

In section ⑩, write what the contractor does, what your company does, and what you agree in advance. Done when you can say in one sentence who reports a breach that happened at the contractor.

Report and notify

On page 4, write the elements of the notice to individuals, track the owner and done date for each contact in the table, and decide who owns prevention. Track what you decide by moving cards from the Reported and notified column to the Prevention done column on the task board.

Write the notice

In the three frames in sections ⑪ to ⑬, write what happened, what the person should do, and the contact point, and check section ⑮ to see that the notice is not being pushed back. Done when you have a draft of the notice.

Fill contact table

In the table in section ⑭, write for the individuals, the PPC, the contractor and internal contacts what to tell them, the owner, and the done date. Done when the done column is filled in for all three rows.

Assign prevention

In the Prevention row of section ⑭, write the fix for the cause, the owner, and the date to write the plan. Done when you know what goes in with the final report.

Investigating 0 items

Deadlines confirmed 0 items

Reported and notified 0 items

Prevention done 0 items

← Back to templates

Preview mode Personal Data Breach Report and Notice (Japan) | Meet the PPC and Data Subject Deadlines

Whiteboard preview

① Incident and goal (start writing here) ② Five steps to decide whether to rep... ③ The 4 cases that require a report (... ⑤ Trap: stalling at the “possible lea... ⑥ Trap: miscounting the preliminary r... ⑦ Trap: unclear roles for a breach at... ⑨ Target deadlines, timing and owners... ⑩ Roles with the contractor (write th... ⑪ What happened (write from the 5W1H ... ⑫ What to ask of them (only what they... ⑬ Contact point ⑭ Contacts, owners and done dates (ma... ⑮ Trap: the notice to individuals get... Personal Data Bre... How to use (4 pag... Goal and what you... Rules, deadlines ... Traps What you learned ... 1/4 Check if reportable Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Gather the facts ↙ 3/4 What you are using it fore.g. A contractor told us customer data may have leaked. Move the report and notices forward within the deadlines The incident and the day you noticede.g. Customer data of a member service. Noticed on day 1 (Monday) at 10:00 Who gathers and who is responsiblee.g. Legal, IT and the customer help desk. The person responsible for personal data management leads Personal data?Is it personal information organized in a database or similar? If a wrongful purpose is suspected, personal information meant to become personal data (for example, data still arriving through a web form) can also be covered. Check the latest guidancee.g. Names and emails in the custom… Breach?Is there a leak, loss or damage, or a risk of one?e.g. It may have been visible to people outside the company → yes Protected?Strong encryption and similar safeguards can exempt ite.g. It was not encrypted → next step One of the 4 cases?Check the table in ③ for the four cases that require a reporte.g. Possibly over 1,000 people → yes Report and notifyIf yes, go to the preliminary and final reports and notice to individuals. If no, still record what happenede.g. Line up the deadlines on page 3 Applies? Basis (what is kn... Who checks Special care-requ... e.g. Does not apply e.g. No medical history or similar e.g. IT owner Financial loss e.g. Does not apply e.g. No credit card numbers e.g. Legal owner Wrongful purpose e.g. Possible e.g. Possible external unauthorized access (under investigation) e.g. IT owner Over 1,000 people e.g. Applies e.g. About 1,200 people e.g. Legal owner ④ Gather the fact... Breach incident WhatData involved e.g. The items that may have leaked (names, emails) and the expected number of records WhyCause e.g. The likely cause. If not certain, write “under investigation” WhoWho is affected e.g. The affected people (about 1,200 customers) and the first person to notice WhenDate and time e.g. When the company became aware, and when it seems to have happened WhereSystem e.g. Which system, contractor or device it happened on HowHow found e.g. How you found out (a customer inquiry, a call from the contractor) What happens: e.g. You wait until the leak is confirmed and miss the preliminary report deadline How to check: e.g. Even with “under investigation” left in ④, check whether any of the four cases in ③ may apply How to prevent: e.g. Send the preliminary report while it is still a possible leak, and add findings in the final report Owner: e.g. The legal owner reviews ④ every morning What happens: e.g. You count from the day the investigation ends, and the deadline is off by days How to check: e.g. See that the date and time anyone at the company noticed is recorded under “When” in ④ How to prevent: e.g. Count the day you noticed as day 1 and write the deadline in ⑨. Check how to count in the latest guidance Owner: e.g. The legal owner sets the start date in ⑧ What happens: e.g. The contractor and your company each think the other will report, and nobody does How to check: e.g. See whether the contract sets a contact point and a deadline for informing you How to prevent: e.g. Have the contractor inform you, decide that your company reports and notifies, and write it in ⑩ Owner: e.g. The person who handles the contractor 3/4 Line up the deadl... → 4/4 4/4 Report and notify ⑧ Line up the dat... Start (day you noticed) e.g. Day 1 (Monday), 10:00, the contractor called. Count from here Phase 1 Escalate internally e.g. Escalate to the person responsible on day 1 and decide in ② and ③ whether it is reportable Phase 2 Preliminary report e.g. About 3 to 5 days. Put “under investigation” for items you do not know Phase 3 Notify individuals e.g. Promptly, depending on the situation. Use the notice in ⑪ to ⑬ Phase 4 Finish the investigation e.g. Confirm the cause and the scope of impact, and draft the prevention plan Goal (final report) e.g. Within 30 days (60 days if a wrongful purpose is suspected). Check the latest guidance Target deadline o... Owner Planned date (rec... Preliminary report e.g. About 3 to 5 days from the day you noticed e.g. Legal owner e.g. File on day 3 Final report e.g. Within 30 days (60 if a wrongful purpose is suspected) e.g. Legal owner e.g. Plan to file on day 28 Notice to individ... e.g. Promptly, depending on the situation (no fixed number of days) e.g. Customer help desk owner e.g. Send by email on day 7 Announcement e.g. No legal deadline. Decide it, for example, as a substitute when notice is hard e.g. PR owner e.g. Decide on day 5 whether to release it the same day as the notice What the contractor doese.g. Tell your company as soon as they notice, help with the investigation and hand over records What your company doese.g. Your company reports to the PPC and notifies individuals. If the contractor informs your company, the contractor need not report or notify individuals, and the company that receives the notice reports (check the General Rules guidelines) What to agree in advancee.g. Check in the contract or a memo the contact point, the deadline for informing you and how to hand over investigation records e.g. When, what information, and how many people may have been affected. Also the known cause and whether impersonation or other secondary harm is possible e.g. Write “under investigation” for what is not known, and only what is certain e.g. What your company has already done (for example, shut down the affected system) e.g. An apology, and when you will next update them e.g. If a message claiming to be from us arrives, do not click the link; open our official site or app instead e.g. If you see a charge you do not recognize, tell your card company or our help desk e.g. If the password may also have leaked, change it, and change it anywhere else you use the same one e.g. If they need to do nothing, say so e.g. A dedicated phone number and its hours e.g. An email address and how many days a reply takes e.g. A page with frequently asked questions e.g. Add that we never ask for passwords or card numbers by phone or email What to tell or do Owner Done date Individuals e.g. Send the notice from ⑪ to ⑬ by email e.g. As in ⑨ (customer help desk owner) e.g. Sent on day 7 PPC e.g. Preliminary and final reports (by the deadlines in ⑨). Depending on the business, the report may go to the ministry in charge, so check the PPC guidance e.g. As in ⑨ (legal owner) e.g. Filed the preliminary report on day 3 Contractor and in... e.g. Ask the contractor for material for the final report. Report to executives daily e.g. IT owner e.g. Report at 10:00 every morning Prevention e.g. Fix the cause and review the contractor checks e.g. Information security lead e.g. Write the plan before the final report What happense.g. Busy with the report to the PPC, you delay the notice, and worry and inquiries grow How to checke.g. See whether the Individuals row in ⑭ has a send date and an owner How to prevente.g. Start the draft of ⑪ to ⑬ the same day as the preliminary report. For people who are hard to reach, decide a substitute such as an announcement → 2/4 Gather the facts ↙ 3/4 Line up the deadl... → 4/4 Report and notify
100%

Drag to move, scroll to zoom