The Art of Prioritization: When Everything Is a Security Risk
One of the most difficult responsibilities of cybersecurity leadership is deciding what not to do.
That might sound counterintuitive.
After all, cybersecurity professionals are trained to identify risks, address vulnerabilities, implement controls, and protect the organization.
But the reality is that there will always be more security work than available time, money, or people.
There will always be another vulnerability to remediate.
Another security tool to evaluate.
Another project that needs attention.
Another audit finding to address.
Another emerging threat that requires investigation.
And another business initiative that needs security involvement.
The challenge is not identifying things that need improvement.
The challenge is deciding which ones matter most.
That is where prioritization becomes one of the most important responsibilities of a cybersecurity leader.
Not Every Risk Deserves the Same Response
In cybersecurity, it can be tempting to treat every high-severity finding as an immediate priority.
A vulnerability scanner reports a critical vulnerability.
A security assessment identifies a control gap.
An audit produces several findings.
A vendor announces a newly discovered security issue.
Each one may be important.
But does that mean they all deserve the same urgency?
Not necessarily.
A critical vulnerability on an isolated system with limited exposure may represent less immediate business risk than a lower-rated vulnerability affecting an internet-facing application that supports essential operations.
A missing security control in a low-impact environment may be less concerning than an existing control that is failing to protect privileged access.
A vulnerability affecting a business-critical service may require immediate attention even when its technical severity score is not particularly remarkable.
This is why technical severity and business risk should not be treated as interchangeable.
Technical severity helps us understand the potential seriousness of an issue.
Business context helps us understand what that issue means to the organization.
Effective prioritization requires both.
And this is one of the reasons I believe cybersecurity leaders need a strong technical foundation.
Without understanding the systems, threats, and controls involved, it becomes difficult to challenge assumptions or determine whether a reported issue represents a meaningful exposure.
A security leader does not need to personally investigate every finding.
But they should understand enough to ask the right questions.
The Problem with Making Everything a Priority
When everything becomes a priority, something eventually suffers.
Teams become overloaded.
Projects stall.
Operational work gets delayed.
Technical debt accumulates.
And employees may find themselves constantly responding to the latest urgent request rather than making sustained progress on strategic improvements.
This creates a dangerous cycle.
A new vulnerability is announced, so the team shifts its attention.
An auditor requests evidence, so another initiative is interrupted.
A vendor identifies a new capability, so leadership wants it evaluated.
A business project runs into a security requirement, so resources are redirected again.
Individually, these requests may be reasonable.
Collectively, they can prevent the organization from making meaningful progress.
I believe one of the responsibilities of security leadership is to protect the team’s ability to execute.
That means establishing clear priorities, managing competing demands, and recognizing when taking on additional work creates more risk than it reduces.
Sometimes the best leadership decision is not to add another initiative.
It is to finish the important work already underway.
Understanding the Business Impact
Consider a hypothetical situation.
A security team is managing three significant initiatives.
The first involves remediating vulnerabilities across several internal systems.
The second is improving privileged access controls for critical infrastructure.
The third is implementing additional monitoring capabilities to improve threat detection.
All three initiatives have value.
All three address legitimate security concerns.
And all three require time from the same limited group of engineers.
Which one should come first?
The answer cannot be determined by looking at a project list alone.
A security leader needs to understand the underlying risk.
Are the vulnerable systems externally accessible?
Is there evidence of active exploitation?
Could compromised privileged credentials provide broad access to sensitive systems?
Does the organization currently lack visibility into activity that would indicate a significant compromise?
Are compensating controls already in place?
What business services depend on the affected systems?
How much effort is required to make a meaningful improvement?
These questions begin to establish context.
For example, if privileged access controls are weak across critical infrastructure, addressing that exposure may reduce the potential impact of multiple attack scenarios.
On the other hand, an actively exploited vulnerability affecting a critical externally exposed system may demand immediate remediation regardless of the broader project roadmap.
And if monitoring gaps prevent the organization from detecting suspicious activity in a critical environment, those gaps could materially affect its ability to identify and respond to an incident.
There is no universal answer.
The appropriate decision depends on the circumstances.
That is precisely why cybersecurity prioritization requires judgment rather than simply following a severity score or predetermined checklist.
Risk Reduction Should Drive Prioritization
I think security teams sometimes become too focused on measuring how much work they complete.
How many vulnerabilities were closed?
How many alerts were investigated?
How many policies were updated?
How many projects were delivered?
Those metrics can be useful for understanding activity and operational performance.
But they do not necessarily tell us how much risk has been reduced.
Closing fifty low-risk vulnerabilities may improve a dashboard while leaving a single serious exposure unresolved.
Implementing an expensive security platform may increase technical capability without producing meaningful improvements if the organization lacks the resources or processes to operate it effectively.
Completing an audit finding may satisfy a requirement without addressing the underlying weakness that created the finding.
Activity matters.
But outcomes matter more.
I believe cybersecurity leaders should regularly ask a simple question:
If we complete this initiative, what meaningful risk will we reduce?
That question changes the conversation.
Instead of focusing only on completing tasks, the team begins thinking about the exposures being addressed, the business consequences being reduced, and how success will be demonstrated.
It also creates a stronger foundation for communicating priorities to executive leadership.
The Cost of Constantly Changing Direction
Prioritization is not just about deciding which work should happen first.
It is also about understanding the consequences of changing direction.
Every new priority has a cost.
That cost may not always appear in the budget.
It can include delayed projects, interrupted engineering work, increased operational complexity, and additional pressure on employees.
For example, suppose a team is halfway through an identity security improvement project.
The work involves standardizing privileged access, improving access reviews, and reducing unnecessary permissions.
Then a new security technology becomes available.
It promises better visibility, improved automation, and additional detection capabilities.
The technology may be valuable.
But adopting it immediately would require the same engineers to stop their existing work, evaluate the platform, prepare integrations, and begin implementation.
The question is not simply whether the new technology is useful.
The question is whether pursuing it now delivers more value than completing the identity improvements already underway.
That is a very different decision.
Security leaders need to account for the opportunity cost of their recommendations.
Sometimes changing priorities is absolutely necessary.
An emerging threat, critical incident, or significant change in business risk may justify immediate action.
But not every new capability or finding warrants disrupting the roadmap.
Consistency and execution are important parts of building an effective security program.
Balancing Strategic Initiatives with Operational Reality
Another challenge is balancing long-term security improvements with the daily responsibilities of running a security function.
Security operations do not stop because the organization has a strategic roadmap.
Alerts still need investigation.
Incidents still require attention.
Vulnerabilities continue to emerge.
Access requests, change reviews, vendor assessments, and operational issues still need to be addressed.
At the same time, the organization expects progress on larger initiatives.
Identity improvements.
Security architecture changes.
Detection engineering.
Automation.
Governance.
Technology modernization.
The challenge is ensuring that operational demands do not consume all available capacity.
A security program that only reacts to daily issues may struggle to improve.
But a program that focuses exclusively on strategic projects while neglecting operational responsibilities can expose the business to unnecessary risk.
Leaders need to manage both.
That requires understanding team capacity, establishing realistic commitments, and being deliberate about how resources are allocated.
It may mean reserving time for strategic engineering work.
It may mean adjusting expectations when incident activity increases.
It may mean automating repetitive tasks or changing processes that consume disproportionate effort.
And sometimes it means telling leadership that an additional initiative cannot be delivered without delaying another priority or providing more resources.
That is not making excuses.
It is providing a realistic assessment of what the organization can accomplish.
Saying No Is Sometimes Part of Leadership
I do not believe cybersecurity leaders should become known as the people who simply say no.
Security should enable the business wherever reasonably possible.
But effective leadership also requires the ability to challenge requests and set boundaries.
Sometimes a proposed initiative does not meaningfully reduce risk.
Sometimes the technology already exists within the organization’s current platforms.
Sometimes the team does not have the capacity to implement another solution successfully.
And sometimes a project needs to wait because something more important requires attention.
The key is explaining the reasoning.
Instead of simply saying, “We cannot do that,” a security leader should be prepared to say:
“We can pursue this initiative, but doing so would delay another project addressing a more significant exposure. Based on the current risk and available resources, I recommend completing that work first.”
That is a business conversation.
It acknowledges the request.
It explains the tradeoff.
And it provides a recommendation.
Leadership should not require everyone to agree with every decision.
But the reasoning behind those decisions should be clear, consistent, and defensible.
Priorities Must Be Revisited
A security roadmap should provide direction.
It should not become so rigid that the organization cannot respond to changing circumstances.
Threats evolve.
Business objectives change.
New systems are introduced.
Vulnerabilities are discovered.
Acquisitions happen.
Regulatory and contractual expectations shift.
An initiative that was a lower priority six months ago may become critical today.
Likewise, an initiative that once appeared urgent may become less important because the environment or the available controls have changed.
That is why prioritization should be an ongoing leadership responsibility rather than an annual exercise.
Security leaders need a regular way to evaluate whether existing priorities still make sense.
That does not necessarily require another complicated scoring model or governance process.
It requires asking the right questions and being willing to adjust when new information justifies a change.
The objective is not to constantly rewrite the roadmap.
It is to keep the roadmap aligned with meaningful risk and business priorities.
Making Prioritization Visible to Leadership
One of the most important aspects of prioritization is helping executive leadership understand the decisions being made.
Executives should not have to interpret a long list of technical vulnerabilities or competing security projects to understand where the organization is focusing its resources.
They should be able to see:
Which risks require the most attention.
Why those risks matter to the business.
Which initiatives are currently being prioritized.
What improvements the organization expects to achieve.
What is being deferred and why.
What decisions or resources are needed from leadership.
This creates transparency.
It also helps establish shared accountability.
If a business chooses to defer an initiative because of competing priorities, that decision should be understood by the appropriate stakeholders, particularly when material risk remains.
Security leaders should not silently absorb every tradeoff or assume responsibility for business decisions they do not control.
Their responsibility is to provide informed recommendations, communicate the implications, and ensure that decisions involving significant risk are made at the appropriate level.
That is what turns prioritization from an internal security exercise into an effective part of business leadership.
Closing Thought
Cybersecurity will always involve more work than available resources.
There will always be another vulnerability.
Another control to improve.
Another project to deliver.
And another threat to investigate.
The measure of effective cybersecurity leadership is not whether every issue gets addressed immediately.
It is whether the organization is consistently directing its resources toward the issues that matter most.
That requires technical understanding.
It requires business context.
It requires honest conversations about capacity and tradeoffs.
And it requires the confidence to explain not only what the organization should do, but what it should reasonably defer.
Good cybersecurity teams identify risks. Good cybersecurity leaders determine which risks require action, in what order, and why.
In Part 3, I will explore how security leaders build the credibility and relationships needed to influence those decisions at the executive level.
Because identifying the right priorities is only part of the challenge.
Getting the organization to act on them is where leadership truly matters.

William Tulaba is a cybersecurity executive and security engineering leader focused on enterprise security strategy, cloud risk, and security operations.