2016 · Philippines · O - Public administration and defence · Distributed denial-of-service attacks on government websites, with follow-on defacements
Analysed 2026-11-06 by Hermes
Open this case in the tool →Distributed denial-of-service attacks on government websites, with follow-on defacements
Expertise to Execution
Evidence coverage: 2/6 stages, weight 9/60
Decisive stage: response (clearest evidence) · Alternative: Expertise to Leadership
(1) Expectation at the victim: the Philippine government runs public e-government web assets under the gov.ph estate from national departments down to small municipalities and must keep them available; after foreign DDoS attempts on gov.ph were detected and blocked by government IT administrators in April 2012, IT experts called for tighter, uniform online security standards and DOST-ICTO began drafting the executive order for a top-level cyber body. (2) In practice, within hours of the PCA ruling on 12 July 2016 a sustained DDoS campaign knocked at least 68 national and local government websites offline - the Department of Foreign Affairs, Department of National Defense, DILG, the central bank, MMDA, NDRRMC, the Presidential Management Staff, the newly installed DICT, Manila City Hall, a medical center and LGU portals - with the same intensity on 13 July, and two municipal sites remained defaced for days afterwards; officials could not determine the attack source. (3) The classification rests on the response stage (availability protection under attack): the expectation and the remedy sit in the material column (flood mitigation is a known technical capability the government's own administrators had demonstrated in 2012), and the chain broke at execution - no such protection or redundancy was realised across the web estate four years later, so a commodity-scale botnet produced a nationwide outage of more than 24 hours. No source documents a decided and resourced protection programme that leadership deferred, so a leadership break is not evidenced; the entry vector (botnet traffic) is not a victim-side condition and is not load-bearing. Recovery adds a contributing execution gap (restoration only as the flood subsided; small LGU sites left defaced for days). (4) RM32 (Expertise to Execution lens): experts could not scale or protect the services because of the estate's architecture - government web presence from ministry portals to town sites had no flood mitigation or redundancy capable of holding services up, so the documented outage across 68 sites for more than 24 hours shows the known remedy was absent in operations (causal role: Enabling). RM21 (Expertise to Execution lens): the comparable 2012 gov.ph flood attacks and the expert recommendations for uniform government security standards were documented, but were not implemented or validated as changes, and the same class of flood succeeded in 2016 at far larger scale (causal role: Perpetuating / learning-blocking).
RM32 — Capacity / availability-protection gapRM21 — Recurring weakness / learning failureAttribution is victim-side/media only: the dataset records initiator Unknown with China as suspected initiator country, and officials said they could not pinpoint the source; the case is kept on the victim side despite the state-linked context because the victim is a real organisation set (the Philippine government web estate), not attacker-side infrastructure. The dataset's source_url (news.softpedia.com) no longer opens (HTTP 403); the Internet Archive snapshot 20160719141843 of that exact article was opened and is cited instead. The April 2012 DOST-ICTO statement (the government's own page) documents an earlier comparable gov.ph DDoS episode and the expert calls for uniform standards; it is used for RM21, and the link between the unimplemented 2012 recommendations and the 2016 impact is the coder's reading, not stated by any source. No source documents the government's internal DDoS-mitigation decisions, so both gap stages carry source type inference. Dataset disruption coding (long-term, > 24h) matches the reported July 12-13 timeline. Case file carries no related_rows; nothing in the run required an action needing consent. Link check: politiko.com.ph blocks automated access (HTTP 403); the page was opened and read during research. Link check: dost.gov.ph was unreachable at check time (timeout); the page was opened and read during research.