Every institution should have an ongoing
cybersecurity program.Technology changes, the way we use technology changes, threat actor behaviour changes, systems and services go out of support and compliance requirements change.
For example in federal government in Australia the Information Security Manual is updated on a quarterly cadence and material changes are made to controls and coverage requirements.
The expectation has been set that you need to be running contemporary technology configured to industry standards run with best practices.
You cannot be expecting that operational personnel do more than incremental process and technology improvement.
Cybersecurity is not a “solved problem” like say “fire” with fire detection suppression EWIS, drills, mature standards, fire fighting and ubiquitous reliable insurance cover. It requires constant adjustment to get it right for the organisation.
A well running program will be:
1. Regularly delivering risk reduction outcomes on at least a twice a year cadence.
2. Have “non-lumpy” spend and a three year commitment from management on ongoing budget and hopefully a slight downward trend in spend
3. Have a tactical stream of work to execute on opportunities to reduce risk arising from audit issues, observations and changes to technology
4. Have one to three strategic streams of work potentially aligned with security transformation to help the cyber team deliver more effectively or delivering risk reduction in a known control domain or an outcome to enable the organisation in a non security manner
5. Running a planning session well prior to the beginning of the calendar year to develop candidate work packages for prioritisation by the steering committee
6. Aligned with the organisation’s overall and IT work cadence so that change management considerations do not derail regular delivery outcomes
7. Give project managers a “project on a page” document with scope and outcomes to enable them to develop a more detailed project scoping document with their team
8. Run a risk register with primarily delivery related risks to be actively managed so that delivery does not “stall on a known speed bump”
9. Be advertising and promoting the program with a “catch phrase” an “elevator pitch” for each stream of work and collateral describing the program and its successes on an intranet page.
10. Have a register of key stakeholders and schedule regular contact between the right people in the program and them
11. Consider external stakeholder impact from each project and stream of delivery and “batch request” information and activities on a program wide basis so key stakeholders are not bombarded with agenda less meeting requests