ExecRoster

Fractional CISO KPIs and Deliverables: How to Measure

November 20, 20266 min read

Fractional CISO KPIs and deliverables fall into two groups. The deliverables are documents and programs the role owns, such as the risk register, security roadmap, policies and incident response plan. The KPIs are a short set of coverage and speed measures (MFA coverage, patch time, access review completion, time to contain an incident) reported monthly.

Why security work needs both artifacts and numbers

Security is hard to measure because the best outcome is that nothing happens. A part-time security leader can look busy without changing the company's exposure, and a good one can go unrecognized.

The fix is to measure two things separately. Artifacts answer "does the program exist?" Metrics answer "is it working?" A company with a polished policy set and no access reviews has artifacts without results. A company with strong patching and no written incident plan has results without the paper that customers and auditors will ask for. You need both columns filled in.

This article is educational and is not legal or compliance advice. Your obligations depend on your contracts, your industry and where your customers are.

The deliverables a fractional CISO owns

These are the things you should be able to open and read. If you are hiring, ask for the list at the start. If you are the executive, put it in your scope.

  • Risk register. A ranked list of the specific ways the company could be hurt, each with an owner, a likelihood and impact rating, and a treatment decision (fix, accept, transfer, avoid).
  • Security roadmap. Twelve months of work in priority order, tied to the risk register and to any framework the company is pursuing, such as SOC 2 or ISO 27001.
  • Policy set. Acceptable use, access control, incident response, vendor management, data classification, and business continuity. Short, readable, and approved by leadership.
  • Incident response plan and runbooks. Who declares an incident, who talks to customers, who calls counsel, and step-by-step guides for the likely scenarios: a compromised account, ransomware, a lost laptop, a leaked credential in a code repository.
  • Asset and data inventory. What systems exist, who owns each, and where sensitive data lives.
  • Vendor risk reviews. A tiered list of third parties with a completed review for every one that touches customer data.
  • Audit evidence and readiness. Control descriptions mapped to the framework, with evidence collected on schedule.
  • Customer-facing security package. A standard answer library for security questionnaires and a short overview document sales can send.
  • Quarterly board or leadership report. Top risks, what changed, what needs a decision or budget.

The KPI table: what to track and what good looks like

Pick eight to ten measures and hold them steady so trends are visible. The targets below are common starting points, not standards. Set yours against your own risk register and contract commitments.

KPIHow it is measuredWhat good looks like
MFA coverageAccounts with multi-factor enforced, divided by all accounts, across identity provider, email, cloud console and code hostingAll human accounts covered, exceptions listed by name with an end date
Critical patch timeDays from a critical vulnerability being published to it being fixed on affected systemsInside the window your policy states, with misses explained
Open critical and high findingsCount from vulnerability scans and the last penetration test, with ageTrending down, none older than the policy window without a signed risk acceptance
Access review completionSystems reviewed on schedule, divided by systems in scopeEvery in-scope system reviewed each quarter, removals actually carried out
Offboarding timeHours from an employee's departure to all access being removedSame day, verified against the HR leaver list
Endpoint coverageLaptops with disk encryption, endpoint protection and device management, divided by all laptopsFull coverage, unmanaged devices blocked from company systems
Time to detect and containFrom first malicious activity to detection, and from detection to containment, per incidentShrinking across incidents and tabletop exercises
Phishing simulation resultsShare who reported the test, and share who clickedReport rate rising over time. Reporting matters more than clicking.
Backup restore testDate of last successful restore of a production system, and how long it tookTested on a schedule, restore time inside what the business said it can tolerate
Questionnaire turnaroundBusiness days from a customer security questionnaire arriving to it being returnedFast enough that security is never the reason a deal slips

Two cautions. First, avoid counting activity. "Number of alerts triaged" or "policies written" says nothing about exposure. Second, do not reward zero incidents. A year with no reported incidents can mean weak detection, so ask how incidents would be noticed.

A monthly cadence that keeps the numbers honest

A part-time security leader cannot watch dashboards every day, so the rhythm has to do the work.

  • Weekly (30 minutes): sync with the IT or engineering owner. New vulnerabilities, open exceptions, upcoming customer questionnaires, joiners and leavers.
  • Monthly: KPI report to the CEO or CTO. Risk register review, with at least one risk re-rated or closed. Evidence collection check for audit controls.
  • Quarterly: access reviews across in-scope systems, vendor review refresh, a tabletop incident exercise with leadership, and the board or leadership report.
  • Annually: penetration test, policy review and re-approval, full restore test, security training refresh, and audit fieldwork if a framework is in place.

If the company also has a part-time technology leader, agree on who owns which metric. Patch time and endpoint coverage often sit with engineering or IT, with the CISO setting the target and reporting on it. The split is covered in more detail in this guide to the fractional CTO role.

A one-page monthly report you can copy

  1. Headline. One sentence on whether exposure went up, down or stayed flat this month, and why.
  2. KPI table. This month, last month, target. Red, amber or green for each.
  3. Top five risks. From the register, with any change in rating.
  4. Incidents and near misses. What happened, time to detect, time to contain, what changed as a result.
  5. Roadmap progress. Items finished, items slipped, reason for each slip.
  6. Decisions needed. Budget requests, risk acceptances that need a signature, policy exceptions.

The "decisions needed" section is where a fractional CISO earns trust. Risk acceptance belongs to the business, not to security. Your job is to make the choice clear and get it signed by someone with authority.

Setting expectations at the start of the engagement

Whether you are hiring or being hired, write the deliverables and the KPI list into the scope. A simple approach: list the artifacts due in the first 90 days (risk register, roadmap, incident plan, baseline KPI report), then name the recurring reports. The guide to scoping a fractional engagement covers the structure, and onboarding a fractional executive covers the access a security leader needs on day one, including read access to the identity provider, cloud accounts and ticketing system.

Baseline first, then targets. The first monthly report will probably look bad, because nobody was measuring before. Say so up front, so the first honest numbers are read as a starting line and not as a verdict on the person who produced them.

For experienced executives

Get found and hired for fractional work.

  • A profile companies can find
  • A calendar they can book
  • Paid to your bank, you keep 90%
Join the Roster Hiring? Browse the roster →

Frequently asked questions

What KPIs should a fractional CISO report every month?+

A steady set of eight to ten coverage and speed measures: MFA coverage, critical patch time, open critical and high findings with age, access review completion, offboarding time, endpoint coverage, time to detect and contain incidents, phishing report rate, backup restore test results, and security questionnaire turnaround. Report this month, last month and target for each.

What deliverables should a company expect from a fractional CISO?+

Expect a ranked risk register, a twelve-month security roadmap, an approved policy set, an incident response plan with runbooks, an asset and data inventory, vendor risk reviews, audit evidence mapped to your framework, a questionnaire answer library for sales, and a quarterly leadership or board report covering top risks and decisions needed.

How do you measure whether a fractional CISO is effective?+

Look at artifacts and trends together. The artifacts should exist and be current. The metrics should move in the right direction over several months, with misses explained. Avoid judging on activity counts or on having zero incidents, since a lack of reported incidents often means weak detection, not strong prevention.

How often should a fractional CISO report to the board?+

Quarterly is a common rhythm, with a monthly KPI report to the CEO or CTO in between. The board report should be short: top risks from the register, what changed since last quarter, incidents and lessons, progress on the roadmap, and any budget or risk acceptance decisions that need leadership sign-off.

Put your experience to work.

Get on the roster, get found by companies that need exactly your background, and get paid on your terms.

Qualified, paid engagements · Your rate, your calendar · Cancel anytime

We use cookies to understand how the site is used and to measure our marketing. See our cookie policy.