ExecRoster

Fractional CISO Job Description: Scope and Template

November 20, 20266 min read

A fractional CISO job description should state the security outcomes the person owns (risk register, compliance program, incident readiness, customer assurance), the hours you are buying, who they report to, and what stays with your IT or engineering team. Below is the real scope of the role, how it changes by hours, and a template you can copy.

What a fractional CISO is responsible for

The role is accountable for the security program, and it works through other people's hands. A realistic list:

  • Risk management. Maintain the risk register, run a risk assessment at least once a year, and bring risk acceptance decisions to a named executive.
  • Policies and standards. Own the policy set (acceptable use, access control, incident response, vendor management, data classification, business continuity) and make sure it matches what the company does in practice.
  • Compliance programs. Lead readiness and audits for the frameworks you need, such as SOC 2, ISO 27001, HIPAA, or PCI DSS, including the auditor relationship and the evidence calendar.
  • Incident readiness and response. Write the incident response plan, run a tabletop exercise, and act as incident lead or senior advisor when something happens.
  • Customer and partner assurance. Answer security questionnaires, join sales calls when a buyer's security team is involved, and maintain a trust packet.
  • Vendor risk. Review critical third parties before purchase and on a schedule after.
  • Roadmap and budget. Set the 12-month security plan, recommend tooling, and review architecture decisions that carry security weight.
  • Reporting. Give leadership a monthly summary and the board a periodic security update.

Scope by hours: what each level buys

Hours decide how much of that list is realistic. Write the job description for the level you can fund, and cut the rest.

TimeWhat fitsWhat does not fit
About half a day a weekAdvisory oversight: quarterly risk review, policy approval, questionnaire escalations, a board update, advice during an incidentRunning an audit, vendor reviews at volume, anything hands-on
About one day a weekProgram ownership for a small company: risk register, one compliance framework, a vendor review process, monthly leadership report, one tabletop exerciseA second framework in the same year, daily security operations
Two to three days a weekProgram build: a first audit from scratch, security hiring, architecture reviews, customer assurance at sales pace, managing an outsourced monitoring providerReplacing an engineer on the keyboard

If the work you need is mostly configuration and alert monitoring, you need a security engineer or a managed provider, with a CISO overseeing them for a few hours. The guide on scoping a fractional engagement helps you size the role before you post it.

Copyable fractional CISO job description

Replace the bracketed text. Keep the finished version to one page.

Title: Fractional Chief Information Security Officer (contract, part-time)

Reports to: [CEO / CTO / COO]. Presents to the board [quarterly / twice a year].

Time commitment: [X] days per month, a standing [weekly / biweekly] security meeting, and availability for incidents as defined below.

About the company: [Two sentences: what you sell, headcount, where your data lives, which regulated data you handle.]

Why we are hiring now: [The trigger: customers asking for SOC 2 Type II, an insurance renewal, new healthcare customers, a recent incident.]

Outcomes for the first six months:

  1. Complete a risk assessment and deliver a risk register with owners within [45] days.
  2. Deliver a 12-month security roadmap with a budget estimate within [60] days.
  3. Lead [framework] readiness and reach [audit milestone] by [date].
  4. Publish and roll out the core policy set, and run one incident tabletop exercise.
  5. Stand up a process that answers customer security questionnaires within [5] business days.

Ongoing responsibilities: maintain the risk register; own security policies; manage the auditor and the evidence calendar; review critical vendors; advise engineering and IT on architecture and access decisions; report monthly to leadership.

Incident response: acts as [incident lead / senior advisor]. Responds to a declared incident within [4] business hours. Time beyond the retainer is billed at [terms].

Works with: [IT lead or managed service provider], [head of engineering], [legal counsel], [HR].

Not in scope: day-to-day system administration, alert monitoring, penetration testing, and tool implementation, which are handled by [team or vendor].

Background we are looking for: has owned a security program at a company of [similar size or sector]; has led at least one [framework] audit; has run a real incident; can explain risk to non-technical executives.

Engagement terms: independent contractor, monthly retainer, [30] days notice on either side, initial term of [6] months.

What to leave out

  • A product list. Naming firewalls, scanners, and endpoint tools attracts engineers and tells security leaders you want an administrator.
  • "Available 24/7." Unless you are paying for on-call coverage, write a response time during business hours and say how after-hours incidents are handled.
  • A wall of certifications. One line is enough. Ask for the experience you need and let certifications support it.
  • "Responsible for preventing all security incidents." Nobody can promise that, and strong candidates will pass. Make the role responsible for the program, the plan, and the response.
  • IT director duties. Help desk, laptop provisioning, and license management belong in a different role.
  • Legal conclusions. Interpreting privacy law and breach notification duties belongs with counsel. The CISO supplies facts and works alongside them.

Have counsel review the contractor terms and any officer designation before you send an offer. This article is general information, not legal advice.

How to use the description in the hiring process

Send the one-page version before the first call and ask each candidate to mark it up. A good fractional CISO will push back on something: the hours against the audit date, a missing owner for risk acceptance, a managed provider contract that does not cover monitoring. That markup tells you more than a resume.

Then ask for a rough 90-day plan against your six-month outcomes. You are checking that they sequence the work around your trigger and that they name what they need from your team. The wider process is in the guide to hiring a fractional executive, and once you have chosen, onboarding for this role should include read access to your identity provider, cloud accounts, policy folder, and vendor list in week one.

If you are the executive reading one

Read a client's job description as a diagnostic. Check five things before you reply:

  1. Reporting line. Reporting to the CEO or COO gives you room to raise risk. Reporting to the IT manager you are meant to oversee does not.
  2. Who accepts risk. If no executive is named, ask who signs off when a fix is declined.
  3. Hours against the deadline. A first SOC 2 audit on half a day a week with no internal help is a plan to miss the date. Say so early.
  4. Hands-on expectations. Phrases like "configure" and "monitor" mean they want an engineer. Decide whether to rescope or decline.
  5. Incident terms. If the description is silent, propose your own response window and after-hours billing in your reply.

A short reply that rewrites their scope into three outcomes and a day count often wins the work, because it shows the judgment they are trying to hire.

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 does a fractional CISO do on a day-to-day basis?+

A fractional CISO owns the security program and works through your IT and engineering teams. Typical work includes maintaining the risk register, leading compliance audits such as SOC 2, reviewing vendors, answering customer security questionnaires, preparing leadership and board reports, and leading or advising on incident response. They usually do not administer systems or monitor alerts.

How many hours a week does a fractional CISO usually work?+

Anywhere from half a day to three days a week, depending on scope. About half a day covers advisory oversight. About one day a week covers program ownership for a small company with one compliance framework. Two to three days a week fits a program build, such as a first audit from scratch plus security hiring and architecture reviews.

What should not be included in a fractional CISO job description?+

Leave out long tool lists, round-the-clock availability you are not paying for, a wall of certifications, help desk and IT administration duties, and any promise to prevent all incidents. Those items attract the wrong candidates or push strong ones away. Keep legal interpretation with your counsel.

Who should a fractional CISO report to in a small company?+

Reporting to the CEO, COO, or CTO works best, with periodic access to the board. The role needs enough independence to raise risks and bring risk acceptance decisions to a named executive. Reporting to the IT manager whose work they oversee weakens that independence and makes hard findings easier to bury.

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.