Give security an owner
CISO as
a Service
A senior security leader joins your team part time and owns the program: the roadmap, the risk register, board reporting, and the answers auditors and customers ask for. You get the judgement of an experienced CISO without a full time hire, and the person you meet in scoping is the person who does the work.
How the retainer runs
A program with
a named owner.
Your CISO works from NIST CSF 2.0 and maps the program to the standards you answer to, such as ISO/IEC 27001 or SOC 2. Each cycle starts with what changed, sets priorities with leadership, moves the work forward with your team, and reports progress in plain terms to executives and the board.
Step 01 · Take stock
Start each cycle with what changed.
A current risk register that reflects new systems, vendors, incidents and audit findings.
- Review open risks, incidents and audit findings since the last cycle.
- Check new systems, vendors and business plans for security impact.
- Score the program against NIST CSF 2.0 outcomes.
Step 02 · Set priorities
Decide what gets done next and what waits.
A ranked plan for the cycle, agreed with leadership, with owners and budget requests attached.
- Rank work by risk reduction and audit exposure.
- Agree owners across IT, engineering and the business.
- Put a number on every budget request before it reaches finance.
Step 03 · Run the program
Own the work between meetings.
Policies approved, controls in place, and decisions recorded with the reasoning behind them.
- Write and maintain policies your team can follow.
- Direct internal staff and outside vendors on security work.
- Answer customer security questionnaires and join sales calls when a deal needs it.
- Make the calls on exceptions and accepted risk.
Step 04 · Face the auditors
Represent security to auditors and customers.
Audit evidence gathered before the auditor asks, and answers that match what you actually do.
- Prepare evidence for SOC 2, ISO/IEC 27001 or the audits you face.
- Meet auditors and assessors as your security lead.
- Track audit findings to closure with named owners.
Step 05 · Report to the board
Tell the board where security stands, in plain language.
A board report showing the risk trend, progress against plan, and the decisions leadership needs to make.
- Brief executives and the board on risk, not tool counts.
- Bring the decisions that need their approval, with options.
- Reset priorities for the next cycle based on what they decide.
Start each cycle with what changed.
A current risk register that reflects new systems, vendors, incidents and audit findings.
- Review open risks, incidents and audit findings since the last cycle.
- Check new systems, vendors and business plans for security impact.
- Score the program against NIST CSF 2.0 outcomes.
Decide what gets done next and what waits.
A ranked plan for the cycle, agreed with leadership, with owners and budget requests attached.
- Rank work by risk reduction and audit exposure.
- Agree owners across IT, engineering and the business.
- Put a number on every budget request before it reaches finance.
Own the work between meetings.
Policies approved, controls in place, and decisions recorded with the reasoning behind them.
- Write and maintain policies your team can follow.
- Direct internal staff and outside vendors on security work.
- Answer customer security questionnaires and join sales calls when a deal needs it.
- Make the calls on exceptions and accepted risk.
Represent security to auditors and customers.
Audit evidence gathered before the auditor asks, and answers that match what you actually do.
- Prepare evidence for SOC 2, ISO/IEC 27001 or the audits you face.
- Meet auditors and assessors as your security lead.
- Track audit findings to closure with named owners.
Tell the board where security stands, in plain language.
A board report showing the risk trend, progress against plan, and the decisions leadership needs to make.
- Brief executives and the board on risk, not tool counts.
- Bring the decisions that need their approval, with options.
- Reset priorities for the next cycle based on what they decide.
Key benefits
Security with a name and a seat at the table.
Questions from the board, auditors and customers go to one senior leader who knows your program, not a rotating cast. Decisions get made and written down with the reasoning behind them.
You get a senior security leader for the hours your organization needs. If you hire a full time CISO later, the program, the documents and the decision history are ready to hand over.
Security questionnaires and customer due diligence get a senior answer. Your CISO handles the questions, joins the calls when a deal depends on it, and points to evidence that matches your controls.
What you get
What lands on
your desk.
What you hold at the end of every cycle, written for the people who act on it.
The document
The security program plan
The roadmap, policies and risk register your CISO maintains, mapped to NIST CSF 2.0 and the standards you answer to. It belongs to you and stays with you if the engagement ends.
The working file
The risk and action register
Every open risk and action in one place: owner, rating, status, the date your team committed to, and the reasoning behind any accepted risk. Auditors can trace each decision.
The conversation
The board briefing
Your CISO presents to executives and the board each cycle: where risk stands, what moved, what it would cost to move further, and the decisions waiting on them.
Client case studies
Real engagements.
Documented outcomes.
In their words
"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
In their words
"ForgePath has become a trusted security partner for YHB. Beyond helping us comply with FTC Safeguards requirements, they provide the governance, oversight, and guidance we rely on to protect our firm and our clients’ data. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
Trusted by industry leaders.
Before you sign
What leaders
ask first.
Straight answers from the practitioners who do the work. If yours is not here, ask us directly.
That is set in scoping, based on the size of your program and what you need owned. We agree the scope in writing and revisit it as priorities change, so the retainer follows the work rather than a fixed block of hours.
Yes, if you want that. Your CISO can present to the board or audit committee, brief the CEO, and sit in executive meetings where security decisions get made. Reporting lines are agreed during scoping.
The senior practitioner you meet during scoping is the person who leads your program. There is no junior bench behind them and no handoff to someone you have not met. Your team still does much of the hands on work, directed by your CISO.
Your CISO prepares the program and the evidence those audits look for, and represents security in front of the auditor. The audit opinion belongs to the auditor, so we do not promise a result, but you go in knowing where you stand.
That is a good outcome. We can help write the role, sit in on interviews if you ask, and hand over the program, documents and history so your new hire starts with a working program instead of a blank page.
Ready?
Bring us
the problem.
One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.








