How Many Hours Does a Fractional CISO Work?
November 20, 20265 min read
A fractional CISO works the hours the security workload demands, which usually lands in one of three shapes: a few hours a week of oversight, one to two days a week of program building, or a short surge around an audit or incident. Size the engagement by listing the work first, then adding up the time.
Start with a workload inventory, then count hours
Asking for an hours number before you know the work gets you a guess. A security program has three kinds of work, and each one consumes time differently. Write them down for your company before you talk about a retainer.
- Recurring work: risk register review, vendor security reviews, answering customer security questionnaires, quarterly access reviews, policy exceptions, the security steering meeting, and a report to the board or audit committee.
- Project work: SOC 2 or ISO 27001 readiness, scoping a penetration test and tracking remediation, writing the incident response plan, running a tabletop exercise, completing the cyber insurance application.
- Reactive work: a suspected incident, a customer escalation about a finding, a phishing campaign that got clicks, an urgent question from legal about a breach notification clause in a contract.
Recurring work sets the floor. Project work sets the peak. Reactive work is why the agreement needs a clause for hours nobody can predict.
One more input matters: who does the hands-on work. A fractional CISO with a security engineer or a capable IT lead to delegate to needs far fewer hours than one who has to configure the single sign-on rollout personally. If nobody on staff can execute, either the hours go up or the program stalls.
The three shapes most engagements take
| Shape | What fills the time | Fits when |
|---|---|---|
| Oversight | Monthly risk review, steering meeting, board report, questionnaire sign-off, availability for questions | Controls are in place, an internal person runs day-to-day security, and you need senior judgment and a named owner for the program |
| Program build | Everything above plus policy writing, control design, audit readiness, a vendor review process, a training plan, and weekly working sessions with IT and engineering | You are heading toward a first audit, a large customer requires a named security leader, or the program exists only on paper |
| Surge | Near-daily involvement for a bounded period: an audit window, incident response, a customer security review tied to a large deal, a post-acquisition assessment | A dated event needs concentrated leadership, then the work drops back to one of the other shapes |
Engagements move between shapes. A common path is program build for the first two quarters, a surge during the audit window, then a step down to oversight once evidence collection runs without supervision.
A worked sizing example
Here is a hypothetical. A 60-person software company sells to mid-size banks, has one IT manager, and needs a first SOC 2 report within the year. The figures below illustrate the method. They are not a benchmark.
| Work item | Cadence | Estimated hours per month |
|---|---|---|
| Security steering meeting and prep | Twice a month | 4 |
| Risk register and remediation tracking | Monthly | 3 |
| Customer questionnaires and security calls | About four a month | 8 |
| Policy drafting and control design for the audit | Weekly during the build | 16 |
| Working sessions with the IT manager and engineering lead | Weekly | 8 |
| Vendor reviews for new tools | As requested | 3 |
| Leadership or board update | Monthly | 2 |
| Total | 44 |
Forty-four hours a month is a little more than a day a week. After the audit, the policy and control line drops from 16 hours to perhaps 3 for maintenance, and the total falls to about 31. That is the step-down point. Write it into the agreement on day one so the change surprises nobody.
Notice what is missing: incident response. Add a separate line that says who can approve incident hours and how they are billed. The comparison of retainer and hourly structures shows how to split predictable work from unpredictable work.
Signs the engagement is under-scoped
- Security questionnaires sit for a week because the hours are used up by the middle of the month, and deals wait on them.
- The risk register has not changed since the day it was created.
- Penetration test findings are still open months later with no owner or due date.
- Policies were written, but nobody has tested the controls. Access reviews never happened. Backups were never restored.
- The CISO hears about new vendors, new integrations or a new product line after launch.
- Every conversation is reactive. The tabletop exercise and the roadmap keep moving to next quarter.
The fix is sometimes more CISO hours. More often the missing piece is execution capacity: a security analyst, a managed detection provider, or a compliance automation tool that collects evidence. A senior leader taking screenshots for an auditor is under-scoping in disguise, and an expensive form of it.
Signs it is over-scoped
- The weekly meeting contains status and no decisions.
- The CISO is doing help desk tickets or laptop setup to fill the retainer.
- Reports grow longer while the risk register stays flat.
- You pay for a program-build cadence, but the audit is done and the controls run without daily attention.
- No customer, auditor, insurer or regulator is asking for anything the current team cannot answer.
When you see these, step down to oversight. A good fractional CISO raises it first, because a client paying for idle hours does not renew.
Put the sizing in writing and revisit it
Whatever number you reach, tie it to the inventory. The scope document should list the recurring items, the dated projects, the response time for questions, and the rule for incidents. Review it each quarter against what happened. If the work drifted from the list, change the list or change the hours.
If you are the executive, track your time by work item for the first 60 days of every engagement, even on a flat retainer. That record is the evidence behind your next proposal. Watch capacity too. Two program-build clients with audits in the same quarter will collide, so ask about audit dates before you sign and stagger them.
A fractional executive in security carries real accountability for whatever is in scope, so the hours have to be enough to exercise it. A name on a policy with no time behind it helps nobody when an auditor or a customer starts asking questions. This article is general guidance, not legal or compliance advice for your specific obligations.
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%
Frequently asked questions
How many hours a week does a fractional CISO usually work?+
It depends on the workload. Oversight of a mature program can take a few hours a week. Building a program toward a first audit often takes one to two days a week. Audit windows and incidents need short surges. List the recurring, project and reactive work first, then add up the time.
How do I know if my fractional CISO has too few hours?+
Look for stalled work. Customer security questionnaires wait for days, penetration test findings stay open without owners, the risk register never changes, and the CISO learns about new vendors after launch. Before adding hours, check whether the real gap is hands-on execution capacity such as an analyst or a managed provider.
Should incident response be included in a fractional CISO retainer?+
Keep it separate. Incidents cannot be predicted, so a fixed retainer either overpays for idle time or runs out when you need it most. Write a clause that says who can approve incident hours, how they are billed and how quickly the CISO responds. This is general guidance, not legal advice.
Do fractional CISO hours go down after a SOC 2 audit?+
Usually, yes. Policy drafting and control design take the most time during the build. Once the audit is done and evidence collection runs on a schedule, that work shrinks to maintenance. Agree on the step-down point when you sign so both sides expect the change.