Checklist for Service Suspension Decisions and Conditions for Restarting When Unauthorized Access Is Suspected
SUMMARY
When unauthorized access is suspected, functions that could lead to further damage or whose safety cannot be confirmed should be suspended, and restart timing should be determined by conditions rather than dates. This guideline-style summary recommends stopping services when cause or scope is unclear, as seen in October 2026 when コミックシーモア and ふるさとチョイス halted services before causes and impacts were known and later confirmed millions of records of personal data leakage. Suspension is classified into four levels (full suspension and three graduated functional suspensions), and restarting is recommended in stages from low-impact functions to login, payments, and new registrations as each condition is satisfied.
This article organizes, for e-commerce and membership sites, what to stop and when to stop it when unauthorized access is suspected, and under what conditions to restart services step by step. It is based on the thinking of public guidance (IPA, JPCERT/CC, NIST, etc.) and uses the potential for damage expansion and the ability to verify safety as central criteria.
A concrete checklist for suspension decisions is provided (10 items: unfamiliar operations in administrative screens, possible access to personal or card information, continued tampering or anomalous communications, unknown intrusion route, etc.), and it is recommended that if even one item is answered “yes” or “unknown,” the relevant function should be considered for suspension. Suspension should be considered in four stages: full stop, member functions stop, purchase/payment stop, and continue with increased monitoring.
As examples, in October 2026 コミックシーモア and ふるさとチョイス stopped services before causes and scope were clarified, and later each company confirmed leaks of member information (ふるさとチョイス announced 4,454,097 records). The article also explains initial actions in the first 24 hours after suspension (evidence preservation, first notification, contacting relevant parties) and the importance of isolating affected systems from the network rather than simply cutting power.
Regarding restarting, the article advises not to promise a restart date in advance; instead, functions should be brought back in order once restart conditions are met (root cause identified, intrusion route closed, tampering removed, authentication data changed, monitoring strengthened, etc.). It emphasizes that restarting card payments requires the judgment of card companies and payment service providers and cannot be done solely on the company’s own decision.
Finally, it recommends summarizing suspension and restart rules on a single sheet in peacetime, preparing decision authorities, contact points, reporting deadlines, and loss estimates for anticipated suspensions, and validating them with an annual tabletop exercise. This article can be regarded as a practical guide focused on a working checklist and procedures.
- #Unauthorized access
- #Service suspension
- #Incident response
Source
mad MEDIA (mad2007.co.jp) — https://mad2007.co.jp/media/pr7__s5e54u/xrpgu82ybp.htmlThis article summarizes the content of the source below. Refer to the original source for accuracy. Last updated: October 21, 2026
Was this article helpful?
Written & reviewed

Reviewed byYutaro SasaoFounder & CEO, MediaLeap Inc.
CEO of MediaLeap Inc. Working on both sides of web advertising and web media since 2013; founded the company in May 2025.
Review scope: cross-checking against primary sources (official and government announcements), verifying claims stay within the facts, and checking source attribution。Last reviewed:
Written by:Leak Watch editorial team (AI-assisted drafts verified against sources by the editorial team) · Reviewer profile · Request a correction