Your 2027 cybersecurity plan: connect each investment to a testable outcome

Security professionals reviewing a network diagram, risks and a work plan
AI-generated illustrative image.

Annual cybersecurity planning brings together renewals, new tools, monitoring, advisory services and technical assessments. Each request may have merit. The management challenge is to turn those requests into a plan the organization can deliver, evaluate and revise throughout the year.

Start with the business outcome. Which service needs to remain available? Which information needs restricted access? Where would misuse or an error be difficult to detect? These questions help establish what is known about the current position, which gaps matter most and what improvement should look like.

Define the current position and the target

NIST CSF 2.0 Organizational Profiles describe current and target cybersecurity outcomes. Comparing them helps organizations identify gaps and prioritize work in their business context. Profiles also support progress assessment and stakeholder communication. NIST SP 1301.

A practical starting point is to select three important business processes. For each, record its systems and people, a relevant risk scenario and the evidence already available. Three processes is a suggested starting scope, not a NIST requirement.

Keep verified facts separate from assumptions. A documented access policy establishes that a document exists. Evidence that access is actually restricted requires an appropriate test. Where testing has not taken place, record the gap rather than assuming the control works.

Create an investment card

Before approving a budget item, record:

  1. The business process and the potential harm to reduce.
  2. The current position, including evidence source and observation date.
  3. The proposed change and alternatives considered.
  4. The delivery owner, reviewer and acceptance decision-maker.
  5. Licensing or service costs, implementation and operating effort, and dependencies.
  6. The target date and agreed acceptance test.
  7. Remaining risk and how it will be managed.

This is a suggested working aid, not an official compliance template. Adjust it to the organization and its decision-making process.

Example: restricting supplier access

Consider a maintenance supplier that needs access to one business system. Replace a broad objective such as “improve access management” with an explicit outcome: an identifiable account, access limited to the necessary system and actions, an agreed work window and a revocation process.

Acceptance might involve confirming that an authorized action succeeds, an out-of-scope action is denied and access is revoked when the work window ends. Plan and authorize these checks beforehand so they do not put production at risk. Record the tested scope and limitations: a successful sample does not prove that every supplier connection is controlled.

This is an illustrative scenario, not a Cybecs customer case or a claim about a completed engagement.

Review progress during the year

Set review dates for each objective. Useful measures may include work that passed acceptance testing, issues reopened after an unsuccessful fix and unresolved exceptions awaiting a decision. Show sample scope and data quality alongside the numbers.

Document deferred investments too: who made the decision, what evidence supported it and when it will be revisited. The next budget discussion can then build on actual outcomes and prior decisions.

Start with a focused review

Select three business processes, complete the cards and review them jointly with business, IT and security owners. Identify what can be improved with existing resources and what needs additional investment.

Cybecs offers CISO-as-a-Service, GRC and cyber risk management, alongside technical security testing. Start with a conversation about priorities and how to evaluate results. Cybecs services.