Skip to content
Lacambra Web Portal Services
← 2026, week by week
Security · Week 45, 2 to 8 November 2026

Government hacking claims and the NPC's 72-hour rule

Reported hacks of Philippine agencies on 5 November, and ten breach notifications to the NPC by the 10th. What its 72-hour rule asks of any office.

Three plain glass hourglasses in a row on a bare desk, the first run out, the second half run and the third still full.

After reported attacks on 5 November, the watchdog Deep Web Konek and the civic-tech group BetterGov.PH named Philippine government systems as reportedly hit, among them the Presidential Commission on Good Government, the DICT, the Philippine Air Force's clearance system and the Vice President's scheduling system. On 6 November the National Privacy Commission said it had no breach notifications from the agencies yet, and that reports of alleged leaks "do not, by themselves, establish that a personal data breach has occurred". It also pointed to the rule that sets the pace: under NPC Circular 16-03, a breach that requires notification must be reported to the NPC and to the people affected within 72 hours of knowing, or reasonably believing, that it happened.

By 10 November, ten agencies had filed

On 9 November the BIR said in an advisory that breach claims were being handled with the Cybercrime Investigation and Coordinating Center and the DICT's emergency response team. Deep Web Konek had circulated claims by a threat actor calling itself Happy Go Lucky PH to hold records on more than 10 million taxpayers; none of it had been independently verified, and the advisory did not confirm a breach. The same day the SEC said it was investigating an incident detected on 6 November, and had notified the NPC. Its advisory to users, reported on 10 November, said their names, usernames, contact details, birth dates, addresses and TINs may have been exposed; the SEC maintained that no passwords in its databases had leaked.

On 10 November the NPC confirmed breach notifications from ten agencies, among them the BIR, the SEC and the DICT, without saying how many people were affected or whether the incidents were connected. The PCGG and the DICT, both named in those posts, were on its list, with no detail of when or how. The NPC also warned the public about phishing that could feed on the worry.

What the 72-hour rule asks of an office

A post naming your organisation does not by itself establish a breach, as the NPC said, but the clock runs from knowledge or reasonable belief, not from certainty. Section 20(f) of the Data Privacy Act of 2012 (Republic Act 10173) requires prompt notice when sensitive personal information, or information that could enable identity fraud, is reasonably believed to have been acquired by someone unauthorised in a way likely to give rise to a real risk of serious harm. So an office has about three days to answer three questions: is this really our data, which systems and people does it cover, and does it meet that bar? That only works if the answers were prepared before the claim arrived.

Connections and contractors

Most offices' systems talk to each other: HR feeds payroll, the sales system feeds accounting, a web form feeds a spreadsheet. Connections like those change what a claim means: a question about one system becomes a question about every system it shares data with, and an inventory that lists the systems but not the connections will not answer it in 72 hours.

Contractors belong in the plan too. The NPC said on 10 November that agencies stay responsible for data a contractor processes, and Section 21 of the Act says the same of every personal information controller. A data processing agreement is in place before I touch personal data, and one like that should also say who the contractor calls, and how fast, when something looks wrong.

Five things to settle before the next claim

  • Name who assesses a claim, and a deputy. A post naming your organisation needs an owner within the hour, weekends included.
  • List every system that faces the internet, small ones included: a scheduling tool, a test site, a portal a contractor built, and the backups and exports that hold a whole database in one file.
  • Know where your logs are and how far back they go. "Did anyone download the member list?" should take an afternoon to answer, not a week.
  • Draft the NPC notice and the message to users in advance, with blanks for the facts. Seventy-two hours is too short to start from nothing.
  • Write to users the way a phishing message cannot. Say what you will never ask for, as the SEC did: "The SEC will never ask for your passwords or security PINs."

If that list turns up systems nobody owns any more, the fit check is a place to start.

Sources

  1. Newsbytes.PH, NPC checking data leaks following Nov. 5 cyberattack reports, 6 November 2026
  2. Newsbytes.PH, BIR probes alleged data breach involving over 10 million taxpayer records, 9 November 2026
  3. Newsbytes.PH, SEC says company records unaffected after confirming data breach, 9 November 2026
  4. Philstar.com, SEC confirms data breach on its digital platforms, 10 November 2026
  5. Newsbytes.PH, NPC confirms data breach reports from 10 gov't agencies, 10 November 2026
  6. Lawphil, Republic Act No. 10173

Enrique Lacambra III builds internal business systems from Cainta, Rizal.

Email me← All writing

Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.