What Does a Fractional CISO Do? A Week-by-Week Look
November 20, 20266 min read
The short answer to what does a fractional CISO do: they own your security program part-time, including the risk register, the security roadmap, policies, compliance readiness, vendor reviews, incident response planning, and the answers to customer security questionnaires. They set direction and hold people accountable. Your IT and engineering teams, or a managed provider, do the hands-on work.
The job in one sentence, then in artifacts
A chief information security officer decides which security risks the company will reduce, accept, or transfer, and makes sure the agreed work happens. A fractional CISO does the same thing a day or two a week, or a few days a month.
The role produces:
- Risk register. A ranked list of security risks, each with an owner, a treatment decision, and a date.
- Security roadmap. Twelve months of sequenced projects tied to those risks and to a budget.
- Policy set. Acceptable use, access control, incident response, vendor management, data classification, and business continuity, written so people can follow them.
- Incident response plan. Who is called, who decides, who talks to customers, and where the plan lives if the network is down.
- Vendor risk file. A record of which suppliers hold your data and what review each one passed.
- Evidence for audits. The proof an auditor asks for under frameworks such as SOC 2 or ISO 27001: access reviews, change records, training logs.
- Board and leadership reporting. A short, readable summary of risk posture and progress.
A typical month, week by week
As an illustration, here is a month for a fractional CISO working roughly one day a week at a software company preparing for its first SOC 2 audit.
Week 1: risk and roadmap
- Review the risk register with the heads of engineering and IT. Close what is done, re-rank what changed.
- Check roadmap projects against dates: single sign-on rollout, endpoint management, logging.
- Read the vulnerability scan summary and confirm critical findings have owners and deadlines.
- Thirty minutes with the CEO or COO on anything that needs a decision or money.
Week 2: customers and vendors
- Work through open customer security questionnaires with sales. Update the standard answer library so the next one takes less time.
- Join a call with a prospect's security team when a deal needs it.
- Review new vendors that will touch company or customer data before contracts are signed.
- Check contract security clauses the company is being asked to accept, and flag ones it cannot meet.
Week 3: controls and evidence
- Run or review the periodic access review: who has admin rights, who left and still has an account.
- Spot-check controls. Was the last production change approved? Did the last new hire complete training? Was a backup restored as a test?
- Meet the compliance automation vendor or the auditor on evidence gaps.
- Revise one policy that is due for review.
Week 4: people and preparedness
- Review phishing simulation and security training results, and decide on follow-up.
- Debrief any security events from the month, including near misses.
- Prepare the monthly security summary for leadership.
- Plan the next quarter's tabletop exercise or penetration test.
Quarterly and annual work
| Cadence | Activity | Why it matters |
|---|---|---|
| Quarterly | Incident response tabletop exercise with leadership | People learn their role before a real event |
| Quarterly | Board or leadership risk report | Risk acceptance is a business decision and should be made by the business |
| Quarterly | Full user access review | Stale and excessive access is something auditors look for |
| Annually | Penetration test scoping, vendor selection, and remediation tracking | Customers ask for the report and the fixes |
| Annually | Risk assessment and roadmap rebuild | Resets priorities and budget |
| Annually | Audit support for the chosen framework | The CISO is the auditor's main contact |
| Annually | Cyber insurance application and renewal | The questionnaire needs accurate, defensible answers |
| Annually | Policy review and security awareness training refresh | Keeps documents matching practice |
The first 60 days look different
Before the steady rhythm starts, a new fractional CISO runs an assessment. Expect them to ask for an asset inventory (devices, cloud accounts, software services, and where sensitive data lives), admin access lists, existing policies, the last penetration test, recent incidents, and the customer contracts with security obligations. They will interview engineering, IT, HR, legal, and sales.
From that they produce a gap assessment against a recognized framework, an initial risk register, and a roadmap that separates quick fixes (multi-factor authentication everywhere, removing shared admin accounts, tested backups) from longer projects. If you are bringing one in, the guide to onboarding a fractional executive covers how to get access and introductions ready so those first weeks are not spent waiting.
What a fractional CISO does not do
- Watch alerts around the clock. Continuous monitoring belongs to a security operations team or a managed detection provider. The CISO selects and oversees that provider.
- Administer your systems. They will specify how the firewall, identity provider, or laptops should be configured. Your IT team or managed service provider makes the changes.
- Lead the forensics in a major breach. They run the response plan and coordinate, but hands-on investigation is usually an incident response firm's job, often arranged through your insurer and outside counsel.
- Certify you. An independent auditor issues a SOC 2 report or ISO certificate. The CISO gets you ready and manages the audit.
- Give legal advice. They interpret security requirements in privacy laws and contracts, but breach notification duties and regulatory questions go to a lawyer. Nothing in this article is legal advice either.
- Promise you will not be breached. The job is to reduce likelihood and limit damage.
- Build your product's security features. Secure design decisions sit with engineering leadership, often a CTO the CISO works alongside.
Signs you need one, and how to judge the fit
Companies usually hire this role after a specific trigger: a large customer's questionnaire stalls a deal, a contract requires a named security officer, an insurer asks questions nobody can answer, an investor raises it in diligence, or there has been an incident. If none of those apply and the team is small, a capable IT lead following a short baseline may be enough for now.
Questions that separate strong candidates:
- Can they explain your top three risks in plain language to a non-technical CEO?
- Do they start with an assessment, or with a product recommendation?
- Have they taken a company of similar size through the specific framework you need?
- Will they tell you which controls are excessive for your stage?
- Are they clear about response time during an incident, given they have other clients?
That last point deserves a line in the agreement. Decide in advance how the CISO is reached in an emergency, how quickly they will join, and who leads until they do. For the broader hiring process, see how to hire a fractional executive.
If you are an experienced security leader going independent, the weekly rhythm above is also your best sales material. Buyers often do not know what they are purchasing with this role. A one-page sample month with the artifacts named answers that, and it belongs on any profile you publish, including one on ExecRoster, ahead of your list of certifications.
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
What does a fractional CISO do on a weekly basis?+
A typical week includes reviewing the risk register and roadmap progress with IT and engineering, answering customer security questionnaires, reviewing new vendors, checking that controls such as access reviews and backups are working, and briefing leadership. The mix shifts by week, with reporting and incident planning usually at month end.
What is the difference between a fractional CISO and a managed security provider?+
A managed security provider operates tools and monitors alerts. A fractional CISO owns the security program: deciding priorities, writing policy, managing risk, preparing for audits, and overseeing providers. Many companies use both, with the CISO selecting the provider and holding it accountable for results.
Does a fractional CISO handle SOC 2 or ISO 27001 compliance?+
Yes, they typically lead readiness. That includes the gap assessment, policies, control design, evidence collection, and acting as the auditor's main contact. They do not issue the report or certificate. An independent audit firm does that, and the CISO prepares the company and manages the process.
When does a small company need a fractional CISO?+
Usually after a trigger: a customer security questionnaire stalls a deal, a contract requires a named security officer, a cyber insurer asks detailed questions, an investor raises security in diligence, or an incident occurs. Very small teams without those pressures can often start with an IT lead and a basic baseline.