CyberSN
Book a Discovery Call

Workforce Intelligence, by example

Mutechs had a roadmap, a security team of 31, and a question nobody could answer.

This is the story of one Workforce Intelligence assessment: what it saw, what it changed, and what it handed leadership. Scroll to follow it.

Illustrative example. Mutechs is a fictional composite, and every figure on this page is built from it.

The company

A SaaS company moving upmarket, fast.

Mutechs runs a multi-tenant platform that enterprise customers trust with sensitive data. It grew organically and by acquiring Lumify, whose cloud and identity stacks are still being folded in.

For its buyers, security stopped being a back-office concern. It became a condition of the deal.

What leadership could see

Seven teams. On the org chart, every function had an owner.

Leadership, product security, cloud, detection and response, identity, GRC and security engineering. Reporting lines were clear and the headcount was approved.

The workforce

22 permanent employees and 9 contractors from 3 providers.

Workforce means everyone and everything doing the work: permanent employees, contractors, consultants, interns, service providers and AI agents.

At Mutechs, 29% of the security team came through providers.

The question

The roadmap had seven priorities. Could this workforce execute them?

The CISO could feel the risk but could not see it precisely. Headcount and titles do not say who does which tasks, how deep that coverage goes, or where it stops matching the plan.

The Workforce Intelligence view

The same 31 people, sorted by the work they actually do.

The assessment started from the work, not the titles. CyberSN recorded the tasks each person actually does and placed their time against the capabilities the roadmap needs.

What it found

Six capabilities the roadmap depends on had low coverage.

Detection engineering, cloud guardrails, identity architecture, audit readiness, vulnerability management and acquisition integration.

The capability was real in every case. The depth behind its tasks was not.

Who carries the work

Identity, the control plane for every system, ran almost entirely through one provider.

Three of the four people on the identity team came from a single provider, and the architect seat was empty. Nothing on the org chart showed it.

How the team felt

The team trusted each other. They were less sure about the plan above them.

In the anonymous survey, team culture scored 4.4 out of 5 and company culture 3.3. Job satisfaction was lowest on the teams carrying the capabilities with the lowest coverage.

“We hold it together ourselves; nobody is really planning for how long that lasts.”
Survey response (illustrative)
From the Workforce Intelligence ReportThe org chart, with the work inside
Security Leadership2 people

Led by CISO

  • Project Management35% of team time
  • Leadership: Cyber Planning30% of team time
  • Product Security5 people

    Led by Director, Product Security

    1 from Arclight

    • Application Security54% of team time
    • DevSecOps20% of team time
  • Cloud & Platform Security5 people

    Led by Senior Manager, Cloud & Platform Security

    1 from Arclight

    • Cloud Security Engineering60% of team time
    • Leadership: Cyber Planning8% of team time
  • Detection & Response6 people

    Led by Manager, Detection & Response

    3 from Northbeam

    • Security Operations68.3% of team time
    • Incident Response16.7% of team time
  • Identity & Access4 people

    Led by Manager, Identity & Access

    3 from Keystone1 vacant seat

    • Identity and Access Management (IAM)70% of team time
    • Leadership: Cyber Planning10% of team time
  • Governance, Risk & Compliance5 people

    Led by Director, Governance Risk & Compliance

    • Compliance52% of team time
    • Risk26% of team time
  • Security Engineering4 people

    Led by Manager, Security Engineering

    1 from Arclight

    • Vulnerability Threat Management50% of team time
    • Security Engineering32.5% of team time
Illustrative. Mutechs is a fictional composite.See it in the deliverable
One teammate's job description

Incident Response Analyst

Team
Detection & Response
Reports to
Manager, Detection & Response
Workforce band
Permanent employee
  • Incident Response

    • Respond to incidents involving malware
      • Extract malware
      • Analyze malware
    • Respond to incidents involving Business Email Compromise (BEC)
      • Targeted phishing emails or campaigns
      • Invoice fraud and ACH transfers
    • Respond to network based attacks
      • Cloud infrastructure attacks
      • Web Application Attacks
    • Improve the incident response process
      • Facilitating and supporting table top exercises
      • Create and maintain run books and playbooks for security alerts
  • Security Operations

    Its responsibilities and tasks, recorded the same way.

Task names from the CyberSN cybersecurity taxonomy; the role and its split of time are illustrative.

Illustrative. Mutechs is a fictional composite.
From the Workforce Intelligence ReportRoadmap alignment
Roadmap priorityAlignmentPeople
(Workforce)
ProcessTechnologyMetrics
P1 Operating modelPartialOver-coveredLowMediumLow
P2 Detection and responseNot yetLow coverageMediumMediumLow
P3 Secure developmentPartialCoveredLowMediumLow
P4 Cloud guardrailsPartialLow coverageMediumStrongMedium
P5 Unified identityNot yetLow coverageMediumMediumLow
P6 Audit and trustPartialLow coverageMediumLowMedium
P7 Third-party riskNot yetLow coverageLowLowLow
Illustrative. Mutechs is a fictional composite.See it in the deliverable
From the Workforce Intelligence ReportBusiness objectives and the workforce signal behind each
  1. Net-new ARR and enterprise deal velocitySecurity questionnaire turnaround gates enterprise deals, and the work behind it has low coverage.
  2. Audit readiness (SOC 2, ISO 27001)The audit calendar and customer-trust commitments rest on low coverage and an overloaded team.
  3. Platform availability and customer trustDetection and incident response are concentrated, with incident command held informally.
  4. Safe growth through acquisitionUnintegrated acquisition stacks and a new third-party risk program turn each deal into unmanaged exposure.
Illustrative. Mutechs is a fictional composite.See it in the deliverable
From the Workforce Risk TableFifteen risks by severity and likelihood
Severity ↓Likelihood →HighMediumLow
Critical200
High610
Medium420
Low000
Illustrative. Mutechs is a fictional composite.See it in the deliverable
From the Workforce Intelligence ReportRecommendations by horizon

Now0 to 3 months

  • Critical priority: Operating model and ownership
  • Critical priority: Detection engineering depth
  • Critical priority: Codify cloud guardrails

Near3 to 6 months

  • High priority: Incident command
  • High priority: Permanent identity ownership
  • High priority: Product security authority
  • High priority: MDR service levels
  • Medium priority: One vulnerability program owner
  • Medium priority: Questionnaire automation

Mid6 to 12 months

  • High priority: Integrate the acquired stack
  • High priority: GRC capacity
  • High priority: Contractor spend to permanent roles
  • Medium priority: Third-party risk program
  • Medium priority: Cross-training and continuity
  • Medium priority: Detection as code
  • Medium priority: Career framework
  • Medium priority: Security metrics
Illustrative. Mutechs is a fictional composite.See it in the deliverable
From the Workforce Intelligence ReportEach move's path through the funding gate
  • No net-new budget: Existing leadership timeREC-001
  • No net-new budget: Contractor-to-permanent swapREC-002, 017
  • No net-new budget: Codify and cross-train within the teamREC-003, 013
  • Scoped business case: Contractor conversion plus one open roleREC-005
  • Scoped business case: Time-boxed integration projectREC-006
  • No net-new budget: A charter change, not a new roleREC-007
  • Scoped business case: Phased business caseREC-008
  • No net-new budget: Renegotiated within the existing vendor contractREC-010
Illustrative. Mutechs is a fictional composite.See it in the deliverable
From the Training PlansOne teammate's plan, by role

GRC Analyst, Customer Trust

Year 1
Build an answer library so questionnaires come from curated content.
Year 2
Own customer trust as a program that scales with deal volume.
Year 3
Lead security assurance and bring a junior analyst into the work.
Continuity
A second person trained in the work and a documented workflow, so commitments keep moving.

19%had a written career plan before the assessment (4 of 21)

Illustrative. Mutechs is a fictional composite.See it in the deliverable

The org chart, redrawn

The same org chart, with the work inside every box.

Each team's time by capability, with permanent employees and each provider's contractors side by side. The reporting structure had not changed. Now it showed the work.

The record

Behind every box, the tasks each person actually does.

CyberSN recorded all 31 against its taxonomy. One of them, opened up: how the role's time splits across capabilities, then the responsibilities and tasks inside each.

Tasks are where gaps hide, and where AI changes the work.

Strategy alignment

None of the seven priorities was fully supported by the workforce behind it.

Four were partly supported and three not yet. The strategy was sound; ownership and structure held it back. Each priority was rated on people (workforce) coverage, process, technology and metrics.

In the business's language

Every finding tied to an objective leadership already runs the business on.

Deal velocity, audit readiness, uptime and safe acquisitions. Nobody had to learn a new vocabulary to act on what the assessment found.

Workforce risk

Fifteen workforce risks, named, ranked, and tied to the actions that retire them.

Ranked two critical, eight high and five medium in priority, each rated for severity and likelihood, with the places where one risk amplifies another called out.

The plan

Seventeen recommendations, in order. Three start now.

Each one names the priority it serves, the risk it retires and the window it lands in. Two were already under way by the time the report was delivered.

Two of them automate work done by hand today: answering customer security questionnaires, and validating detections.

Funding the plan

Most of it needed no new budget.

Five of the eight funding paths needed no net-new budget: existing leadership time, contractor-to-permanent swaps, codified knowledge, a charter change and a renegotiated contract.

Each funding path arrived with its approval case already drafted.

The people

Every teammate got a growth path, and the organization got depth.

Only 19% of surveyed employees had a written career plan. Every teammate now has a one to three year plan, and read together the plans are one cross-training program behind the capabilities with low coverage.

Mutechs' assessment covered security. The same method covers IT, because security depends on functions that sit inside IT and risk crosses between them.

The short version

So, what is Workforce Intelligence?

Your strategy runs on tasks. Workforce Intelligence shows which cybersecurity and IT tasks it depends on, who and what is doing each one, and which have no coverage.

Why now

Org charts and headcount reports count people, not tasks. AI changes work one task at a time, where they cannot see.

Capability coverage gaps (52%) outpace headcount gaps (48%). 2026 SANS Cybersecurity Workforce Study

The value

  • Find tasks with low or no coverage before an incident does.
  • Tie each workforce move to a business metric.
  • Walk into budget with a funding path, not a request.
  • Decide where AI should take on work, task by task.

Start with a single assessment. Refresh it on your schedule.

A real CISO, on the same work

“[CyberSN] allowed me to show the gaps and unmet capability requirements in a way I simply couldn't before, while clearly representing what our talent was currently responsible for.”
Carraig Stanwyck, Fortune 200 CISO
Read the Fortune 200 case study

Your turn

Is your team a Mutechs?

Six questions, a few minutes. Nothing is stored or sent anywhere.

1Which capabilities does your roadmap depend on most?

Pick up to eight.

3How much of the work runs through contractors and providers?
4Could you show which roadmap priority each team's work supports?
5Is AI already doing part of this work?
6How many people on the team have a written career plan?

The evidence room

The four deliverables, for when you want the detail

Everything in the story came from these. Open any of them, or skip them.

01Workforce Intelligence ReportCapabilities, roadmap alignment, sequenced recommendations and a funding path for each.Preview it here
02Workforce Risk TableEach workforce risk, rated and tied to the actions that retire it.Preview it here
03Workforce Happiness SurveyThe anonymous retention signal beneath the org chart.Preview it here
04Individual Training PlansA one to three year growth plan for every teammate.Preview it here

Illustrative. Mutechs is a fictional composite.

Bringing this to your CFO?

The business case, on one page

What Workforce Intelligence is, what it answers, and how most of the Mutechs plan needed no new budget.

Choose Save as PDF to keep a copy.

Start here

What would an assessment show about your team?

Talk through the tasks behind your priorities, no spreadsheets required.

Book a 30-minute Discovery Call

Start with a single assessment, no long-term commitment required.

Read how Workforce Intelligence works