Using playbooks

  • Release version: Zurich
  • Updated June 5, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Using playbooks

    Playbooks in the Threat Intelligence Security Center provide a structured workflow for threat investigation by guiding analysts through defined stages. Each stage comprises specific actions that must be completed before advancing to the next phase. Playbooks start automatically when a Case record is created with the appropriate type and status, and they appear in the Playbooks tab of the Case record to show current progress and pending activities.

    Show full answer Show less

    How Playbooks Operate

    A playbook progresses through a predetermined sequence of stages, each containing activities such as data entry, task completion, or approvals. Completion of all required activities in a stage is necessary to move forward. The Playbooks tab clearly displays the active stage and remaining activities, while marking completed stages for easy progress tracking.

    Analyst Roles and Collaboration

    Any analyst with access to the Case record can contribute information throughout the playbook stages by recording findings, linking related entities, selecting MITRE ATT&CK techniques, and completing tasks. However, only the case owner (assigned user) can transition stages and make approval decisions. Non-owners complete their tasks and notify the case owner when ready to advance.

    Monitoring and Managing Playbooks

    While working on other Case tabs, analysts can monitor playbook status via the Playbook card in the context menu, which shows the current stage and allows cancellation if necessary. Key playbook events, including stage transitions and completion, are logged in the Case record’s work notes for audit and tracking.

    Playbook Completion and Reuse

    Each playbook runs once per Case and cannot be rerun after completion. If a playbook execution is cancelled, the case owner or administrator can manually add it again. Upon reaching the final stage, analysts typically create a security incident or generate a report to document outcomes—this requires create access on the Security Incident table. Without this access, the option is not displayed.

    Threat Hunting Playbook Specifics

    The Threat Hunting playbook is a guided process that helps analysts transition a threat hunt from hypothesis to resolution within a TISC Case record. It runs once per Case and follows the same principles of stage progression and collaboration.

    Playbooks in Threat Intelligence Security Center guide analysts through structured threat investigation stages. Each stage defines the actions to complete before the case advances to the next phase of the response process.

    When a Case record is created in Threat Intelligence Security Center with the appropriate Case type and status, a playbook starts automatically. The playbook appears in the Playbooks tab of the Case record and shows the current stage, pending activities, and overall progress. The Threat Hunting playbook runs once per Case. After the playbook reaches completion, you can't run it on the same Case. You can add the playbook again for cancelled executions.

    How stages work

    A playbook moves through a fixed sequence of stages. Each stage contains activities — such as entering data, completing tasks, or waiting for an approval. You must complete all required activities in a stage before the case owner can advance the playbook to the next stage.

    The Playbooks tab shows which stage is active and what activities remain. The playbook marks completed stages so you can track progress at a glance.

    Analyst contributions

    Any analyst with access to a Case record can read playbook details and contribute information at each stage. Typical analyst activities include recording findings, linking related entities, selecting MITRE ATT&CK techniques, and completing case tasks.

    Stage transitions and approval decisions are made by the case owner — the user in the Assigned to field. If you aren't the case owner, complete your assigned activities and notify the case owner when the stage is ready to advance.

    Monitoring playbook status

    While you work on other tabs of the Case record, you can monitor playbook status from the Playbook card in the right-side context menu. The card shows the current stage and lets you cancel the playbook if needed.

    The system adds a work note to the Case record when the playbook starts. Check the work notes for a record of key playbook events, including stage transitions and completion.

    Playbook completion

    A playbook runs once per Case. After it reaches completion, it can't run again on the same Case. If a playbook execution is cancelled, the case owner or an administrator can attach the playbook again manually.

    At the final stage, analysts typically create a security incident or a report to document the outcome. This action requires create access on the Security Incident table. If you don't have this access, the playbook does not display the option.