Moving a school information system to a vendor's cloud does not outsource the security responsibility. Schools and agencies need to prepare their contracts, data and notification plans in advance so they can respond when an incident happens.
What happened: one cloud system, several schools affected
The bottom line: the scope of this incident was determined by a single vendor's system, not by any one school's defenses.
According to announcements on the websites of several Taichung high schools and to media reports, ischool, a cloud-based school information system operated by the contractor Haoxue Learning Co., Ltd. (澔學學習股份有限公司), was accessed by an unauthorized third party on November 5, 2026. The vendor suspended external connections to the platform at 1 p.m. on November 6 and reported the case to the police on November 8. Wenhua, Huiwen, Zhongming and Xiyuan high schools posted notices one after another, and Shinmin High School also published an explanation on November 13.
Notices from Huiwen High School and other schools said that basic information on students, parents, and faculty and staff in the system, such as names and contact details, may have been exposed. The actual scope will be confirmed by an external security team's digital forensics. On November 13, the Taichung City Education Bureau said that it had initially found no tampering with grades or student records, that students' admissions and learning rights were not affected for now, and that it had urged the schools and the vendor to activate incident response. If the vendor is found to have breached its contract, the schools may claim compensation under the contract.
The forensic findings have not been released, and there is no official account yet of how the intrusion happened or how many records were exposed. This article does not speculate on the cause. It only uses publicly available facts to outline what schools and agencies can prepare now.
Outsourcing is not a liability shield: risk follows whoever's system holds the data
The bottom line: even when the system sits in a vendor's cloud, the school still has to answer to parents, regulators and the public.
According to the notices, most of the response actions were carried out by the vendor: closing the intrusion path, removing the backdoor programs and accounts left by the attacker, patching system weaknesses, and engaging an external forensics team. On the school side, the work was reporting to the education authorities, setting up a task force, pressing the vendor to finish the investigation, and handling questions from parents.
That division of labor is not wrong in itself, but it shows one thing clearly: a school cannot see the logs inside a vendor's system and cannot judge the scope of a breach on its own. It has to wait for reports from the vendor and the forensics team. If the contract does not spell out notification deadlines, how the vendor will cooperate with forensics, and what information will be disclosed, the school has very little to tell parents in the early days of an incident.
Not just a Taiwan problem: when a provider is hit, everyone downstream is affected
The bottom line: cases in South Korea during the same week show that once a supplier is attacked, the impact spreads to every organization that uses it.
According to an Economic Daily News report citing Central News Agency on November 15, South Korea has seen a series of personal data breaches. Inje University confirmed that 24,011 records of students and faculty and staff were exposed, including student IDs, employee numbers, names, email addresses and mobile phone numbers. Information on about 3,000 users of "chak", a mobile local gift certificate platform run by the Korea Minting and Security Printing Corporation, was exposed. The Financial Security Institute was hit by a cyberattack on the 9th, and an estimated 130 files from 48 companies were exposed.
The same report said that after ERP software provider Douzone Bizon was hacked last month, organizations using its system, including the Gwangju Research Institute, the Gwangju Women and Family Foundation and the Jeonnam Information and Cultural Industry Promotion Agency, were affected one after another. This mirrors the Taichung case: when one shared system has a problem, every downstream organization has to deal with the aftermath on its own.
What parents worry about most is the fraud that follows
The bottom line: the direct risk of leaked basic information is the fraudulent messages that later impersonate schools or teachers.
Shinmin High School's notice was very specific. The school said passwords had not been stolen, but still advised teachers and students to change their Google account passwords (school email and student email) and their ischool passwords. It also reminded families that the school and teachers will never ask anyone by phone, text message or LINE to click a link, enter account credentials, operate an ATM or transfer money, nor ask them to join an unfamiliar LINE group, and that anyone with concerns can call the 165 anti-fraud hotline. The notice also listed a contact window for personal data protection.
Huiwen High School's notice similarly reminded families that, until the investigation is confirmed, they should be wary of unknown calls and messages claiming to be from the school, teachers or the vendor, and should not click suspicious links or transfer money as instructed.
Whether such reminders can go out early in an incident depends on whether the school prepared notification templates and contact windows beforehand. Writing them only after an incident starts usually costs several days.
Security for outsourced systems can be managed starting with the contract
The bottom line: most risk control points are set when the contract is signed, and there is limited room for remediation afterwards.
Looking at the timeline of this incident, 8 days passed between the intrusion on November 5 and the Education Bureau's public statement on November 13. How fast each step must happen, who must notify whom, and whether the forensic report must be shared with the school can all be written into the contract.
Beyond the contract, the data itself matters. A school information system concentrates contact information for students, parents, and faculty and staff. Fields that are not necessary for operations should not be kept in the system long term, and data on graduates and former staff should have a clear retention period and deletion procedure. The less data there is, the smaller the impact of a breach.
Finally, there is verification. When a vendor says its system is secure, the school or agency should have a way to confirm it, for example by requiring third-party vulnerability testing reports, regularly reviewing accounts and permissions, or reserving audit rights in the contract. JIE HENG has long helped government agencies and schools build online application services, single sign-on and school data APIs, and provides security operations under an ISO/IEC 27001:2022 management framework. In our practical experience, the earlier these requirements are written into the specifications, the fewer disputes arise later.
Recommendations for businesses
These recommendations apply equally to schools, agencies, and small and medium-sized businesses that keep member or employee data on SaaS platforms:
- Take inventory of all outsourced and cloud systems, and list what personal data each one holds, which vendor operates it, and who the contact person is.
- Specify in the contract the notification deadline for security incidents, how forensic reports will be provided, and the procedure for returning or deleting data when the contract ends.
- Review the data fields and retention periods in each system. Do not keep personal data that is not necessary, and regularly purge data on graduates and former employees.
- Prepare notification templates and anti-fraud reminders for affected individuals in advance, and designate a personal data protection contact, so notices can go out the same day an incident occurs.
- Require vendors to provide vulnerability testing or third-party certification evidence regularly, and reserve the right to conduct your own audits.
Sources
- Multiple Taichung school information systems hacked; Education Bureau says grades and records not tampered with (Taisounds, via Yahoo News)
- Four Taichung high schools hacked (ETtoday)
- Statement on the ischool security incident (Huiwen High School)
- Haoxue ischool security incident explanation and guidance (Shinmin High School)
- South Korea data breach alarm: universities and public institutions also hacked (Economic Daily News)