The Philippines has no single cybersecurity act: its cyber rules are spread across a criminal statute, the law that created the Department of Information and Communications Technology (DICT), an executive order on the national plan, and a stack of Bangko Sentral ng Pilipinas (BSP) circulars for financial institutions. Security teams that know only the Data Privacy Act miss the evidence preservation duties of the Cybercrime Prevention Act, the two-hour incident clock for BSP-supervised institutions, and the new BSP cybersecurity maturity self-assessment. This guide maps those instruments as checked on 14 November 2026: who they cover, what they require, how they are enforced, and what they mean for privileged, service and API access. It is for CISOs, compliance leads and engineering managers at Philippine organisations, banks, e-money issuers and payment providers, and at offshore firms with operations or outsourcing in the country. Data privacy obligations, including the National Privacy Commission's breach rules, sit in the companion Philippines Data Privacy Act Guide and are not repeated here.
Key takeaways
- Cybercrime is a criminal law matter. Republic Act No. 10175, the Cybercrime Prevention Act of 2012, defines offences such as illegal access, data interference and computer-related identity theft, and imposes corporate fines of up to PHP 10 million where the offence is committed by a leading person in the company.
- Service providers carry preservation duties. Section 13 requires traffic data and subscriber information to be kept for at least six months, and Section 14 gives 72 hours to comply with a court-warranted disclosure order.
- DICT owns national cybersecurity policy. RA 10844 moved all cybersecurity powers to DICT, including the National Cybersecurity Plan and the national CERT, and Executive Order No. 58 (2024) directs national agencies and government-owned corporations to adopt plans consistent with the NCSP 2023-2028.
- BSP rules are the most prescriptive. Circular No. 982 (2017) sets the information security risk management framework, a CISO independent of IT, yearly external testing for digital services and MFA for high-risk transactions; according to press reports of 2018 BSP rules, BSP-supervised institutions report major cyber incidents within two hours of discovery.
- 2026 adds maturity scoring and 2024 adds fraud liability. Circular No. 1232 (2026) introduces a Cybersecurity Maturity Framework and a yearly self-assessment, and RA 12010 makes institutions that lack required controls such as MFA and fraud management systems restore customer losses.
The instruments at a glance
| Instrument | Date | Who it covers | What it does |
|---|---|---|---|
| RA 10175, Cybercrime Prevention Act | Approved 12 September 2012 | Everyone; service providers for preservation and disclosure | Defines cybercrime offences, penalties, corporate liability, data preservation, warrants and jurisdiction; creates the Cybercrime Investigation and Coordinating Center (CICC) |
| Disini v Secretary of Justice (G.R. No. 203335) | Decided 11 February 2014 | Reading of RA 10175 | Supreme Court voided Sections 4(c)(3), 12 and 19, limited online libel to the original author, and upheld the core offences and Sections 13 to 15 |
| RA 10844, DICT Act | Approved 23 May 2016 | Government; national policy | Transfers all cybersecurity powers to DICT, including the National Cybersecurity Plan and national CERT; attaches NTC, NPC and CICC to DICT |
| Executive Order No. 58 | Signed 4 April 2024 | National government agencies and GOCCs (LGUs encouraged) | Adopts the National Cybersecurity Plan 2023-2028; DICT monitors and reports twice a year |
| BSP Circular No. 982 | Approved November 2017 (Monetary Board Resolution No. 1854, 2 November 2017) | BSP-supervised financial institutions (BSFIs) | Enhanced Guidelines on Information Security Management; amends the IT risk management sections of the Manual of Regulations for Banks (Section X177) and for non-bank institutions |
| BSP incident reporting rules | Announced 2018, as reported by the Philippine Daily Inquirer | BSFIs | Initial report of major cyber incidents and disruptions within two hours of discovery, follow-up within 24 hours |
| RA 12010, Anti-Financial Account Scamming Act (AFASA) | Approved 20 July 2024 | Banks, non-bank financial institutions and payment providers under BSP | Requires risk controls such as MFA and fraud management systems, allows 30-day holds on disputed funds, criminalises money muling and social engineering schemes |
| BSP Circular No. 1232 | Issued 27 April 2026 | BSFIs | Cybersecurity Maturity Framework and Cybersecurity Controls Self-Assessment (CCSA) |
The Cybercrime Prevention Act for security teams
RA 10175 is mainly a prosecution tool, but several parts shape how organisations run security and respond to incidents.
| Section | Content | Practical effect |
|---|---|---|
| 4(a) | Offences against confidentiality, integrity and availability: illegal access, illegal interception, data interference, system interference, misuse of devices, cyber-squatting | The legal basis for a complaint after an intrusion; also a reason to authorise penetration testing in writing |
| 4(b) | Computer-related forgery, fraud and identity theft | Covers account takeover and credential misuse cases |
| 6 | Revised Penal Code crimes committed through ICT carry a penalty one degree higher | Online fraud and extortion are punished more heavily than offline equivalents |
| 8 | Prision mayor or a fine of at least PHP 200,000 up to the damage caused for 4(a) and 4(b) offences; up to PHP 500,000 for misuse of devices; reclusion temporal or at least PHP 500,000 for 4(a) offences against critical infrastructure | Attacks on critical infrastructure attract the heaviest penalties |
| 9 | Corporate liability: fines at least double, up to PHP 10 million where a leading person acts for the company; up to PHP 5 million where lack of supervision made the offence possible | Weak oversight of insiders and privileged users is itself a corporate exposure |
| 13 | Traffic data and subscriber information kept at least six months; content data kept six months from a preservation order, extendable once by six months | Service providers need retention that meets this, and a process for preservation orders |
| 14 and 15 | Disclosure orders under a court warrant answered within 72 hours; search, seizure and examination under warrant, with extensions capped at 30 days | Legal and security teams need a warrant-handling runbook |
| 21 | Regional Trial Courts have jurisdiction where any element occurred in the Philippines or damage was caused to a person there | Offshore attackers and victims can fall within Philippine jurisdiction |
Two points from Disini matter for compliance work. Section 12, which authorised real-time collection of traffic data, was declared void, so do not build processes on it. Section 19, which let the Department of Justice block access to computer data, was also struck down. The National Bureau of Investigation and the Philippine National Police each run cybercrime units under Section 10, and the CICC coordinates policy under Section 24. For the international treaty context, see the Budapest Convention and UN Cybercrime Convention Guide.
DICT and the National Cybersecurity Plan
- Mandate: Section 15(b)(i) of RA 10844 transfers to DICT all powers and functions related to cybersecurity, including formulating the National Cybersecurity Plan, establishing the National Computer Emergency Response Team and facilitating international cooperation on cybersecurity intelligence.
- Attached agencies: the National Telecommunications Commission, the National Privacy Commission and the CICC are attached to DICT for policy and programme coordination, and the DICT Secretary chairs the CICC.
- Critical ICT infrastructure: Section 2(m) makes securing critical ICT infrastructures a state policy.
- Executive Order No. 58: national government agencies and government-owned or controlled corporations must formulate, adopt and implement cybersecurity plans consistent with the NCSP 2023-2028; local government units are encouraged to do the same. DICT runs the implementation and monitoring system and reports to the President twice a year through the National Cybersecurity Inter-Agency Committee.
- Private sector: EO 58 does not itself impose duties on private companies. Suppliers to government should expect agency plans to flow down as contract requirements.
BSP information security rules for financial institutions
Circular No. 982 applies to BSFIs and scales by IT profile: Complex, Moderate or Simple. Rural and cooperative banks and non-bank institutions default to Simple unless BSP says otherwise. The Monetary Board gave institutions one year from effectivity to comply.
| Area | Circular 982 expectation | Evidence a supervisor will look for |
|---|---|---|
| Framework | An information security risk management cycle of identify, prevent, detect, respond, recover and test, supported by cyber threat intelligence and collaboration | Documented framework mapped to the six phases |
| Governance | Board approves the information security strategic plan and programme at least once a year; a CISO who is a senior executive, independent of the IT department, reporting to the board, a board committee or senior management | Board minutes, CISO appointment and reporting line |
| Access control | Least privilege, segregation of duties, periodic recertification of access, timely removal of obsolete accounts | Access review records, leaver evidence |
| Authentication | MFA for high-risk transactions such as large-value fund transfers and systems administration | MFA coverage for admin consoles and payment approval flows |
| Detection | Security operations monitoring; for Moderate and Complex institutions, largely automated detection such as SIEM | Use cases, alert handling records |
| Testing | Vulnerability assessment and penetration testing by an external party at least yearly for institutions offering digital or electronic financial services | Test reports and remediation tracking |
| Patching | Patches tested and approved before deployment; critical patches deployed within an appropriate timeframe | Patch SLAs and exceptions |
| Third parties | Due diligence and oversight of providers, with security requirements in contracts, especially where customer data is handled | Contracts, assessments |
For the CISO reporting question, see Where Should the CISO Report. For scoping the yearly external test, see the Penetration Testing Guide.
Incident reporting
According to a 2018 Philippine Daily Inquirer report, BSP rules require BSFIs to make an initial report of major cyber-related incidents and operational disruptions within two hours of discovery, and a follow-up within 24 hours covering how and when the incident was detected, its impact and the initial response. Where personal data is involved, National Privacy Commission rules apply in parallel, so one incident can trigger two clocks. See the Cyber Incident Reporting Requirements Map for how these sit beside other regimes.
Circular No. 1232: maturity and self-assessment
Issued on 27 April 2026, Circular No. 1232 introduces the Cybersecurity Maturity Framework and the Cybersecurity Controls Self-Assessment. BSP rates institutions at one of four levels, using the CCSA and other supervisory work:
| IT profile | Expected maturity range | Self-assessment filing |
|---|---|---|
| Simple | Foundational to Established | When BSP requires it |
| Moderate | Established to Managed | CCSA by 31 March after the reference year |
| Complex | Managed to Optimised | CCSA by 31 March after the reference year |
The annual IT profile report is due within 25 calendar days after the reference year, filed through BSP's ASPIRE platform, and the first CCSA is due 60 calendar days after BSP releases its reporting guidelines. Reporting procedures were to be issued separately, so check BSP's current issuances before relying on dates.
The Anti-Financial Account Scamming Act
- Required controls: covered institutions must protect accounts with risk controls such as MFA, fraud management systems and account owner verification, proportionate to size and complexity.
- Liability shift: institutions BSP finds compliant are shielded from losses caused by covered offences; non-compliant institutions must restore the customer's funds, without waiting for a conviction.
- Temporary holds: funds in a disputed transaction may be held for up to 30 calendar days unless a court extends it, with prompt notice to BSP. Holding wrongly or too long creates liability too.
- Offences: money muling carries 6 to 8 years and/or PHP 100,000 to 500,000; social engineering schemes 10 to 12 years and/or PHP 500,000 to 1,000,000; economic sabotage (for example three or more conspirators or victims) carries life imprisonment and/or PHP 1,000,000 to 5,000,000. Fines for juridical persons are doubled, up to PHP 10 million.
- BSP powers: BSP may investigate accounts linked to covered acts, apply for cybercrime warrants and share information with law enforcement.
See the Money Mule Detection Guide for detection patterns.
Where identity fits
Several Philippine duties land directly on non-human and privileged access. Circular 982 names systems administration as a high-risk activity needing MFA, which covers the admin accounts that manage service accounts, keys and automation. Recertification and removal of obsolete accounts apply to service accounts and API credentials as much as to staff. Section 9 of RA 10175 penalises lack of supervision, which is what an unowned, over-privileged automation credential represents. Build an inventory of machine identities with named owners and include them in access reviews. See the Privileged Access Management Guide and the Access Reviews Guide.
Framework mapping
| Philippine requirement | NIST CSF 2.0 |
|---|---|
| Board approval of the security programme, independent CISO (Circular 982) | GV.RR Roles, Responsibilities, and Authorities; GV.OV Oversight |
| Third-party due diligence and contract clauses (Circular 982) | GV.SC Cybersecurity Supply Chain Risk Management |
| Least privilege, recertification, MFA for admin and high-risk transactions (Circular 982, AFASA) | PR.AA Identity Management, Authentication, and Access Control |
| SIEM-based detection, fraud management systems (Circular 982, AFASA) | DE.CM Continuous Monitoring |
| Two-hour and 24-hour BSP reports | RS.CO Incident Response Reporting and Communication |
| Maturity self-assessment and yearly testing (Circular 1232, Circular 982) | ID.RA Risk Assessment |
Compliance steps
- Classify your exposure: record whether you are a BSFI (and which IT profile), a government agency or GOCC, a supplier to government, a service provider holding traffic data, or none of these.
- Close Circular 982 gaps first: CISO independence, board approval cycle, MFA for administration, access recertification including service accounts, yearly external testing.
- Prepare the CCSA: run the self-assessment against your expected maturity range, and fix the lowest scoring domains before the 31 March filing.
- Write the incident clock into the playbook: a two-hour BSP notice, a 24-hour follow-up and parallel NPC steps, with named decision makers and a test exercise each year. See the Incident Response Guide.
- Set retention and warrant handling: confirm six-month retention for traffic data and subscriber information where you are a service provider, and a 72-hour response path for disclosure orders.
- Map AFASA controls: evidence MFA, fraud monitoring, account verification and the 30-day hold process so that BSP can find you compliant.
Measuring progress
- Share of administrative and high-risk transaction access protected by MFA (target 100%).
- Service accounts and API credentials with a named owner and a recertification in the last cycle.
- Time from detection to BSP initial report in exercises and real incidents, against two hours.
- Assessed CCSA maturity against the expected range for your IT profile.
- Open critical findings from the yearly external test past their remediation date.
Common failure patterns
- Only tracking the privacy clock: teams prepare for NPC notification and miss the two-hour BSP report.
- CISO inside IT: a CISO reporting to the CIO does not meet the independence Circular 982 expects.
- MFA only for customers: high-risk transaction MFA is in place but systems administration still runs on passwords.
- Service accounts outside reviews: recertification covers staff but not automation and integration credentials.
- Relying on voided powers: processes that assume real-time traffic data collection or blocking under Sections 12 and 19.
- Treating AFASA as a fraud team issue: missing controls shift customer losses to the institution, so security owns part of the evidence.
Practitioner checklist
- Decide which instruments apply and record the reasoning.
- Confirm your BSP IT profile and expected maturity range.
- Check CISO reporting line and annual board approval.
- Extend MFA to all administrative access, including tools that manage machine credentials.
- Bring service accounts and API keys into access recertification.
- Test the two-hour and 24-hour BSP reporting path at least yearly.
- Schedule external vulnerability assessment and penetration testing every year.
- Set retention and a 72-hour warrant response where you are a service provider.
- Recheck BSP issuances for Circular 1232 reporting guidelines.
Standards and references
- Republic of the Philippines: Republic Act No. 10175, Cybercrime Prevention Act of 2012
- Supreme Court of the Philippines: Disini v Secretary of Justice, G.R. No. 203335
- Republic of the Philippines: Republic Act No. 10844, Department of Information and Communications Technology Act of 2015
- Office of the President: Executive Order No. 58, s. 2024, National Cybersecurity Plan 2023-2028
- Bangko Sentral ng Pilipinas: Circular No. 982, Enhanced Guidelines on Information Security Management
- Republic of the Philippines: Republic Act No. 12010, Anti-Financial Account Scamming Act
- DivinaLaw: Legal Watch on BSP Circular No. 1232, Series of 2026
- Philippine Daily Inquirer: BSP orders banks to report cyberhacks within 2 hours
Related NHI Mgmt Group resources: Philippines Data Privacy Act Guide · Cyber and Privacy Regulator Directory · Indonesia Cybersecurity Regulations Guide · Cyber Incident Reporting Requirements Map. This guide summarises Philippine cybersecurity laws and BSP rules as of November 2026 and is not legal advice.