Skip to main content
Back to the blog

Cybersecurity Staffing: When the Skills You Need Aren’t the Skills You Have

Will Hayes

By Will Hayes

November 17, 2026
Updated: November 17, 2026

Categories: Cybersecurity, HiringIT

As security requirements grow more specialized, organizations must rethink how they develop, acquire, and deploy cybersecurity expertise.

According to the 2025 ISC2 Cybersecurity Workforce Study, 95% of respondents reported at least one cybersecurity skills need within their organizations, and 59% described those needs as significant or critical.

Yet 34% said their organizations had the right number of cybersecurity employees.

Those findings reveal an important distinction in today’s cybersecurity workforce. Organizations can have experienced, capable security teams and still lack the particular expertise required to protect an increasingly complex technology environment.

The challenge is no longer measured by the number of unfilled positions alone. It is also a question of whether existing teams possess the skills to address the risks their organizations face, especially as new technologies, applications, and infrastructure introduce unfamiliar security requirements.

For technology leaders, that changes the nature of cybersecurity workforce planning. Adding people remains necessary in many circumstances, but identifying the capabilities an organization needs has become just as important as determining how many employees it should have.

When Technology Moves Faster Than Security Expertise

Consider an organization introducing a new AI application that will access proprietary business information. Its security team already manages network protection, endpoint security, identity systems, and incident response. Those responsibilities don’t disappear when the new application arrives.

But the initiative introduces additional questions about data access, model behavior, third-party services, and the protection of sensitive information.

The existing team understands the organization’s systems and security priorities. What it needs is specialized expertise to evaluate the new technology and establish appropriate controls.

Cloud adoption creates similar demands. Securing a traditional network does not automatically prepare a team to manage cloud-native identities, distributed workloads, complex configurations, and the shared security responsibilities of cloud platforms.

The issue isn’t a lack of competence among existing employees. It’s the expanding range of disciplines that modern cybersecurity encompasses.

The ISC2 study reflects this shift. AI and cloud security were the two most frequently cited cybersecurity skills needs, identified by 41% and 36% of respondents, respectively. Risk assessment, application security, security engineering, and governance, risk, and compliance also ranked prominently.

These capabilities overlap, but they are not interchangeable. A strong security operations analyst isn’t necessarily an expert in cloud architecture. An experienced compliance professional won’t automatically possess the technical skills to secure a new application.

Recognizing those distinctions is the first step toward building a workforce capable of supporting the organization’s technology strategy.

Start With the Risk, Not the Job Description

When an organization identifies a cybersecurity gap, the natural response is often to open a requisition. But before deciding whom to hire, security and technology leaders should establish precisely what needs to be accomplished.

Suppose a company is expanding its cloud infrastructure and discovers that its security team needs additional support.

The immediate request might be for a cloud security engineer. Yet that title could encompass several different responsibilities, including reviewing architecture, strengthening identity and access controls, improving configuration management, or integrating cloud activity into existing security monitoring.

Those are related tasks, but they call for different combinations of experience.

The same principle applies to incident response. Does the organization need additional analysts to manage a growing volume of alerts? A specialist to improve detection capabilities? Someone to design and test an incident response plan? Or experienced leadership to coordinate a complex security program?

Defining the work first makes it easier to determine the appropriate skills, level of experience, and staffing arrangement.

It also prevents organizations from treating cybersecurity expertise as a single, broadly interchangeable resource.

Decide What the Team Should Learn and What It Needs Now

Cybersecurity skills development is essential because the field changes too quickly for any workforce to remain effective without continuous learning.

Organizations already have a substantial advantage in the professionals who understand their infrastructure, applications, business processes, and security history. Developing those employees can preserve institutional knowledge while expanding the team’s technical capabilities.

An infrastructure engineer with extensive networking experience, for example, could develop expertise in cloud security. A security analyst might move into detection engineering, while an application developer with a strong understanding of software architecture could pursue application security or DevSecOps.

These transitions require time, training, practical experience, and support from leadership. They also require opportunities to apply new skills in real operating environments.

Not every capability can be developed on the schedule a business initiative demands.

A company preparing to deploy a new platform may need an experienced security architect immediately. An organization responding to a regulatory requirement might require specialized governance or compliance expertise that its current team has not yet developed.

In these circumstances, workforce planning becomes an exercise in balancing long-term capability development with immediate operational needs.

The objective is to invest in existing employees without expecting them to acquire specialized expertise overnight.

Specialized Expertise Doesn’t Always Require a Permanent Position

Once an organization understands the capability it needs, the next decision concerns how that expertise should be supplied.

Some responsibilities warrant permanent internal ownership. Security leadership, ongoing risk management, institutional knowledge, and core operational functions often benefit from continuity and close integration with the business.

Other needs arise from a particular project, technology transition, or period of heightened demand.

A cloud modernization initiative, for example, might require a security architect during design and implementation, while deploying a new identity management platform calls for a different kind of engineering expertise. Other needs are less predictable. A security operations center experiencing an unexpected increase in workload could benefit from temporary support while the team improves its processes or automation.

In these situations, consultants, contract professionals, and staff augmentation can provide capabilities without requiring the organization to establish a permanent position for every specialized need.

That flexibility can also support internal development. An experienced specialist brought in for a defined initiative can work alongside existing employees, document decisions, and help transfer knowledge before the assignment concludes.

External expertise, however, still requires internal direction. The organization must retain accountability for its security priorities, risk decisions, and long-term operating model.

The most effective staffing arrangement is the one that matches the nature and duration of the work while strengthening the organization’s overall security capability.

Security Skills Must Connect Across the Business

Cybersecurity is increasingly embedded in activities that extend well beyond the security department.

Cybersecurity responsibilities extend throughout the organization, from the cloud engineers making infrastructure decisions to the developers responsible for application security and data protection. Data teams must consider how information is collected, accessed, and used, while business leaders influence the organization’s exposure through their technology investments and implementation priorities.

A cybersecurity workforce strategy must account for those relationships.

Hiring an experienced security specialist is valuable, but the impact depends partly on whether that person can work effectively with the teams responsible for the underlying technology.

For example, an application security engineer needs more than technical knowledge of vulnerabilities and testing tools. The role also requires collaboration with developers, an understanding of release processes, and the ability to help teams incorporate security into everyday development practices.

Similarly, cloud security specialists must understand how infrastructure teams deploy and manage resources, while governance professionals need to translate regulatory and risk requirements into controls the organization can actually implement.

Communication, collaboration, and judgment therefore matter alongside technical credentials.

Security expertise delivers the greatest value when it becomes part of how the organization builds, operates, and improves its technology.

Build the Capabilities the Business Will Need Next

Cybersecurity workforce planning has traditionally focused heavily on vacancies, recruiting difficulty, and the number of professionals available to fill open positions.

Those concerns remain important. But the changing demands on security teams require a more precise assessment.

Leaders need to understand which capabilities already exist, where expertise is becoming insufficient, and which emerging requirements deserve attention before they become urgent.

That assessment should inform a combination of professional development, internal mobility, permanent hiring, and specialized external support. The balance will differ among organizations and change as their technology environments evolve.

The strength of a cybersecurity team lies in its ability to address the organization’s particular risks, support its technology priorities, and adapt as those requirements change. That calls for the right combination of expertise, experience, and capacity, supported by a workforce strategy that evolves alongside the business.

Back to our blog