Threat Model Handoff to Client Security Owner (Handoff)

Threat Model Handoff to Client Security Owner (Handoff)

1. 01

   Freeze the threat model at a named version before the handoff meeting

   Tag the document with a date and revision number so the client's security owner can reference an exact artifact rather than a moving draft. Note which attack paths were modeled and which were explicitly out of scope.

2. 02

   Walk the client through each modeled attack path and its current control status

   Cover network paths, identity paths, and code or dependency paths in one pass. For each, state whether a control exists, is partial, or is absent, and who inside the client owns remediation.

3. 03

   Separate findings the agency will fix from findings the client must fix

   Agencies routinely over-commit here. Anything inside the client's production infrastructure, HR systems, or physical access stays with the client, even when the agency discovered it.

4. 04

   Record the client's acceptance of residual risk in writing

   A short signed acknowledgment that named risks remain open after the engagement closes protects the retainer relationship. Avoid language promising absolute security; describe controls and monitoring cadence instead.

5. 05

   Transfer monitoring credentials and alert routing to the client's team

   Confirm the client can receive and act on alerts without the agency in the loop. Test one alert end to end before the handoff call ends.

6. 06

   Schedule a 30-day post-handoff check on open findings

   Use the check to confirm remediation progress and to surface new exposure introduced by the client's own changes. This is also the natural opening for a recurring security retainer conversation.

7. 07

   Deliver the final artifact set in the client's own document system

   Hand over the threat model, control inventory, open-findings register, and the risk acceptance record. Do not leave the only copy inside agency tooling.