Tabletop exercise facilitator contract work, along with threat and risk assessments and technical due diligence, is the project side of security leadership. Each is a fixed piece of work with a clear deliverable: an after-action report, a risk register with treatment decisions, or a due diligence report for an investor. It suits experienced security leaders who can run a room and write for executives.
Why these three engagements go together
Tabletops, threat and risk assessments (TRAs) and due diligence reviews look different on the surface, and they draw on the same skills. You have to understand how a business actually operates, judge which risks matter, get candid answers from people who may be nervous about giving them, and write something a CEO, a board member or an investor can read in one sitting. None of them needs you to sit inside the client's organization for months.
That is what separates them from a vCISO retainer. A retainer is ongoing ownership of a security program. These are bounded projects with a start, an end and a document. Many people who do retainer work take these on between or alongside retainers, and many clients who start with a TRA or a tabletop later want ongoing help. If the retainer side is what interests you, our post on becoming a fractional CISO in Canada covers it. This post is about the projects.
Designing and running a tabletop exercise
A tabletop is a discussion-based exercise in which a team walks through a realistic incident and decides what it would do. Nothing is touched in production. The point is to test the plan and the people against a scenario before a real incident does it for them. Clients usually commission one because an auditor wants evidence that the incident response plan has been tested, a customer or insurer asked, or leadership has changed and nobody knows whether the plan still works. NIST SP 800-84 is a useful public reference for how exercises fit into a testing and training program.
A good tabletop is mostly built before anyone enters the room:
- Objectives. Agree with the sponsor what the exercise is testing: decision-making on a ransomware payment, breach notification under PIPEDA or Law 25, coordination with a key vendor, communication with customers. Three or four objectives is plenty.
- Scenario. Build it on the client's actual systems, vendors and business. A ransomware scenario that hits the system that really runs billing is far more useful than a generic one. Read the incident response plan first, and design the scenario to land on its weak points.
- Injects. Timed pieces of new information that move the scenario forward and force decisions: a ransom note, a journalist's email, a regulator's question, a backup restore that fails, a vendor who stops answering. Plan each inject around a decision you want the room to make.
- Roles. Decide who plays, who observes and who takes notes. The facilitator does not play. A separate note-taker is worth insisting on, because you cannot run the room and capture decisions at the same time.
- Ground rules. It is a no-fault exercise. Say so at the start, and mean it. People who feel tested in front of their boss stop telling you what they would really do.
In the room, the facilitator's job is to keep the scenario moving, draw out quieter participants, and ask the uncomfortable follow-up. "Who decides?" and "How would you know?" are the two questions that find most gaps. Watch for the moment the room relies on one person who is not there, or a document nobody has opened in a year.
The after-action report is the deliverable the client keeps. It should record the scenario and objectives, what went well, the gaps found, and a short list of specific improvements with owners and target dates. Keep it factual and avoid naming individuals as the cause of a gap; name the role or the process. Our post on building an incident response plan from scratch shows what clients are trying to test, and the improvements from a tabletop usually feed straight back into that plan.
Running a threat and risk assessment
A TRA asks what could go wrong with a system, a service or a whole organization, how likely it is, how bad it would be, and what the organization should do about it. In Canada, the federal Harmonized TRA methodology published by the Communications Security Establishment and the RCMP is a common reference, especially for work touching government. ISO/IEC 27005 and NIST SP 800-30 are the other usual starting points. Clients pursuing ISO 27001 or SOC 2 need a documented risk assessment as part of their program, and a TRA often supplies it.
The steps are familiar, and the quality is in the detail:
- Scope and assets. Name the system or service, its boundaries, and the assets that matter: data, systems, people, suppliers, and the business processes they support. Rate each asset's sensitivity for confidentiality, integrity and availability.
- Threats. Who or what could cause harm, from criminal groups and insiders to supplier failure and plain operational error. Ground this in the client's sector rather than a generic list.
- Vulnerabilities and existing controls. What is actually in place, verified where possible rather than taken from a policy document.
- Likelihood and impact. Rated on a stated scale that the client agrees with before you start. Agreeing the scale late is how TRAs turn into arguments.
- Treatment. For each significant risk: mitigate, transfer, avoid or accept, with an owner. Acceptance is a legitimate decision, and it belongs to someone with authority, not to the assessor.
The deliverable is usually a report plus a risk register the client can maintain. Write the register so the client can update it without you, and resist the urge to produce a hundred risks. Twenty well-described risks with real owners are worth more. Our buyer guides on how a threat and risk assessment engagement runs and on a risk assessment a startup can actually run show what clients expect to receive.
Technical due diligence for investors and acquirers
Due diligence work comes from the buy side: a venture fund about to invest, a private equity firm or a strategic acquirer about to buy, sometimes a lender. They want an independent view of the target's security and technology risk before they commit. The target is often cooperative but busy, and the timeline is set by the deal, not by you.
What a security due diligence review usually covers:
- Security governance: who owns security, what policies exist and whether they are followed.
- Past incidents and breaches, and how they were handled and disclosed.
- Identity and access, cloud configuration, and how production is protected.
- Compliance status: SOC 2 reports, ISO 27001 certificates, privacy obligations under PIPEDA, Law 25 or GDPR, and any gaps between what sales materials claim and what exists.
- Third-party and open-source dependencies, and key-person risk in the engineering team.
- The cost and effort to fix what you find, since that is often what the investor is really asking.
Two habits matter more than anything else here. First, be clear about who your client is. You work for the investor or acquirer, and the target needs to know what will be shared. Second, separate what you verified from what you were told. A report that says "management states that MFA is enforced" and one that says "we observed MFA enforced on the identity provider" are very different documents to an investment committee. Expect confidentiality obligations from the deal, and keep deal information off anything but your work machine. Our buyer guide on technical due diligence for VCs shows the review from the investor's side.
Who suits this work
These engagements suit people who have held security leadership or senior consulting roles: security managers, directors, CISOs, incident response leads, and senior consultants who have spent years in front of executives. The common thread is judgement plus communication. A technically brilliant tester who has never had to explain a risk to a board will find tabletops and due diligence harder than they look.
Credentials such as the CISSP, CISM or CRISC are common and help firms place you, and incident response experience counts for a lot with tabletops. Nothing here is legally licensed in Canada, so the evidence that counts most is a sample after-action report, a redacted TRA, or a due diligence summary written against a fictional company.
Practical setup is the same as other security consulting: professional liability insurance, an encrypted work machine, a clear retention rule for client material, and GST/HST registration once you pass the small supplier threshold.
Where the TrazTech Associate Network fits
We run the TrazTech Associate Network, so weigh this accordingly. The Associate Network is how TrazTech brings independent practitioners into client work, and security leadership, covering vCISO work, threat and risk assessments, due diligence and tabletop exercises, is one of its practices. The other practices and roles are listed on our careers page.
Associates are independent contractors working remotely from Canada or the US, part-time or full-time, with no exclusivity. You need at least five hours a week, and if you are employed, your employer has to allow side work. There is no experience minimum, and newer associates are paired with a paid senior mentor, though leadership work naturally goes to people with the background for it.
Applying takes about five minutes. A verified credential such as the CISSP lets you skip the simulated assessment. Otherwise you complete a simulated client engagement of about three hours of work, with 72 hours to submit, then a selection call and portal setup with the agreement signed online.
Work is offered as fixed-scope work orders. You see the scope and the fee before accepting, you can decline, and the fee is fixed per milestone and agreed before work starts. You are paid every Friday by Interac e-Transfer or against your own invoice in CAD or USD. Larger engagements run as teams with a Lead, coverage checklists keep the work consistent, and a TrazTech Principal reviews and signs off every deliverable before the client sees it. You also get a TrazTech email address, a verified credential for LinkedIn, paid mentoring and Lead reviews, referral bonuses, and a path from Associate to Senior, Lead and the core team. Work follows client demand in your practice, so approval does not guarantee a volume of work.
Common questions about tabletop exercise and TRA contract work
What does a tabletop exercise facilitator do?
They design a realistic incident scenario around the client's own systems, write the injects, run the session without playing a role, and produce an after-action report that records gaps and improvements with owners and dates.
How is a threat and risk assessment different from a risk assessment?
The terms overlap. A TRA usually focuses on a specific system or service and works explicitly through assets, threats, vulnerabilities, likelihood and impact, often following a named method such as the Harmonized TRA methodology. An organization-wide risk assessment is broader and may be lighter on threat analysis.
Who do I work for on a due diligence engagement?
The investor, acquirer or lender who engaged you. The target company cooperates but is not your client, so be clear with them about what you will share and separate what you verified from what you were told.
Do I need to be a CISO to do this work?
No title is required, but these engagements depend on judgement and on credibility with executives. People with security leadership, senior consulting or incident response backgrounds usually find them the most natural fit.
How does this work relate to vCISO retainers?
They are the project side of the same skill set. A vCISO retainer is ongoing ownership of a security program, while tabletops, TRAs and due diligence are bounded pieces of work. Many practitioners do both.
Take scoped security leadership work as an independent associate. Tabletops, TRAs and due diligence come as fixed-scope work orders, and you see the scope and fee before you accept.
Apply to the networkSee the role