Who this is for: CIOs, ICT heads and planning officers in national agencies, GOCCs, LGUs and SUCs who need a cybersecurity plan that is both compliant and usable.
In April 2024, the President signed Executive Order No. 58, adopting the National Cybersecurity Plan (NCSP) 2023-2028 as the "whole-of-nation roadmap" for the country's cybersecurity.
The order is short, but its message to government is clear. All national government agencies and instrumentalities, including government-owned or -controlled corporations, are directed to "formulate, adopt and implement their cybersecurity plans and strategies" in line with the NCSP. Local government units are encouraged to do the same.
Many agencies have responded by producing a document. Fewer have produced a plan that changes what happens on a normal Tuesday. This guide is about closing that gap.
What EO 58 actually asks of you
It helps to separate what the order says from what people assume it says.
The order asks your agency to have a cybersecurity plan and strategy that is relevant to your mandate and consistent with the NCSP. It gives the Department of Information and Communications Technology (DICT) the job of setting up a system to implement, monitor and review the national plan, and of providing technical assistance to agencies together with the private sector. DICT also reports on progress to the President twice a year.
On funding, the order says implementation is charged first against agencies' current and available appropriations. After that, continued funding goes through the General Appropriations Act and the usual budget process.
Two practical points follow from this.
First, "relevant to your mandate" matters. A plan for a revenue agency, a hospital GOCC, a city LGU and a state university should not look the same. Copying another agency's plan is the fastest way to end up with controls you cannot run and gaps you cannot see.
Second, funding is tied to the budget cycle. If your plan does not translate into budget lines, it will struggle to survive past its first year.
Why many agency plans stall
In our experience working with public and private organisations in the Philippines and Australia, cybersecurity plans tend to stall for the same few reasons.
The plan was written for the reviewer, not the operator. It reads well, but the people who manage servers, accounts and suppliers were never asked whether it was achievable.
Nobody owns it after approval. The plan is signed, filed and then left without a named owner, a review date or a way to measure progress.
It skips the basics. Ambitious items such as a security operations centre sit alongside an unknown number of systems, shared administrator passwords and backups that have never been restored.
It is disconnected from the budget. Actions are listed without cost, timing or a link to the agency's annual planning and budget submissions.
It treats cybersecurity as an ICT problem only. Records, HR, procurement, finance and frontline units are left out, even though many incidents start in those areas.
None of these are failures of effort. They are signs that the plan was built as a compliance output rather than a management tool.
The building blocks of a workable plan
A workable agency cybersecurity plan does not need to be long. It needs to be clear about a small number of things.
1. A clear link to your mandate and services
Start with what your agency must keep running. Which services do citizens, other agencies or partners depend on? Which information would cause the most harm if it were lost, changed or exposed? This gives your plan a reason for its priorities, and it gives leadership a way to understand the risk in their own terms.
2. An honest picture of where you stand today
You cannot plan a route without knowing your starting point. That means knowing, at a reasonable level, what systems and data you have, who has access, which suppliers connect to your environment and how you would detect and respond to an incident. Our recommendation is to keep this assessment evidence-based. "We think MFA is on" is not the same as "we checked, and here is where it is not."
3. Named ownership and simple governance
Every plan needs an executive sponsor, a working owner and a small group that meets regularly to track progress. In many agencies this sits naturally with the CIO or ICT head, supported by a designated information security officer. What matters is that people know who decides, who does the work and who reports upward.
4. A short list of priorities, sequenced over time
Rather than fifty actions in year one, choose a handful that reduce the most risk and build capability for later. Group them across the plan period so that early work, such as asset visibility, access control and tested backups, supports later work.
Aligning each priority with the relevant NCSP outcome makes it easier to show how your plan supports the national roadmap. The NCSP organises its work around three outcomes: protecting the state and its people in cyberspace, increasing cybersecurity workforce capabilities and strengthening the cybersecurity policy framework.
5. People and capability
Technology is rarely the limiting factor. Skills, workload and turnover usually are. A workable plan is honest about who will deliver each action, what training they need and where outside support is genuinely required. It also includes awareness for staff outside ICT, since phishing and data-handling mistakes affect every unit.
6. Budget that follows the plan
Each priority should have an estimated cost, a likely funding source and a target budget year. This is what turns a plan into something the agency's planning and budget offices can work with, and it is consistent with how EO 58 expects implementation to be funded.
7. A way to measure and review progress
Choose a few measures you can track without a large reporting effort, for example the percentage of critical systems with MFA, the date of the last successful restore test or the time taken to remove access for staff who leave. Review the plan at least yearly, and whenever there is a significant incident, reorganisation or new system.
Common pitfalls to avoid
- Treating the plan as a one-off submission. Plans need owners, reviews and updates.
- Buying tools before agreeing priorities. New platforms without the people and process to run them often add risk.
- Ignoring suppliers. Many agencies rely on vendors and shared services. Their access and obligations belong in the plan.
- Leaving incident response untested. A response plan nobody has practised is unlikely to work under pressure.
- Writing in a language leadership does not use. If heads of agency cannot explain the plan's purpose in two sentences, it needs simplifying.
Where to start this quarter
If your agency already has a plan, ask three questions: Who owns it today? When was it last reviewed? Which three actions were completed in the last twelve months? The answers will tell you whether it is working.
If you are starting from scratch, begin with your mandate and critical services, take an evidence-based look at where you stand and agree a short list of first-year priorities with a named owner and budget line. That foundation will carry the rest of the plan.
Cybersecurity planning in government is not about producing the thickest document. It is about making steady, visible progress that leadership can support and auditors can verify.
Free download
Download the one-page Agency Cybersecurity Plan Outline
A short outline of the headings and guiding questions a workable agency plan should cover. Use it to check your current plan or start a new one.
We use your details to send the outline and occasional relevant insights. See our privacy information.
Prefer to talk it through? Discuss your agency's priorities with our team, or learn how our CIO and CISO as a service and governance, risk and compliance advisory support public-sector teams.
Gardoce Inc. | info@gardoce.ph | 0917 1892610
This article is general information, not legal or professional advice.