---
sourceDocument: Australia Security Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Using playbooks

# Using playbooks {#ariaid-title1}

Release version: Australia  
Updated June 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Threat Intelligence Security Center (TISC) provide analysts with a structured, stage-based workflow to guide threat investigations and responses.
When a Case record with the correct type and status is created, the relevant playbook starts automatically and is accessible via the Playbooks tab within the Case.
The playbook displays the current stage, pending activities, and overall progress, ensuring methodical case advancement.
Show full answer Show less  

## How Playbooks Work

Each playbook progresses through a predetermined sequence of stages, each containing specific activities such as data entry, task completion, or awaiting approvals. Analysts must complete all required activities in the current stage before the case owner can move the playbook to the next stage. The Playbooks tab highlights the active stage and remaining activities, while marking completed stages for easy progress tracking.

## Analyst Roles and Contributions

Any analyst with access to the Case can view playbook details and contribute by recording findings, linking related entities, selecting MITRE ATT\&CK techniques, and completing assigned tasks. However, only the case owner---designated in the Assigned to field---can approve stage transitions and advance the playbook. Non-owners should notify the case owner once their activities are complete.

## Monitoring and Managing Playbook Status

The Playbook card in the Case record's right-side context menu provides a convenient way to monitor the current stage and cancel the playbook if necessary. Key playbook events, including start, stage transitions, cancellations, and completion, are logged as work notes within the Case record for audit and tracking purposes.

## Playbook Completion and Reuse

A playbook runs only once per Case and cannot be rerun after completion. If a playbook execution is cancelled, the case owner or an administrator can manually add the playbook again. Final stages typically involve creating a security incident or report to document the investigation outcome, which requires create access on the Security Incident table. Without this access, the option to create a security incident is not available.

## Threat Hunting Playbook

The Threat Hunting playbook is a specific guided workflow designed to help analysts progress a threat hunt from initial hypothesis through to final outcome within a TISC Case record. It runs once per Case and supports systematic threat hunting investigations.  
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.{#tisc-playbooks-analyst__tisc-playbooks-analyst-p-1}

## How stages work {#tisc-playbooks-analyst__tisc-playbooks-analyst-section-stages}

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.{#tisc-playbooks-analyst__tisc-playbooks-analyst-p-2}

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.{#tisc-playbooks-analyst__tisc-playbooks-analyst-p-3}

## Analyst contributions {#tisc-playbooks-analyst__tisc-playbooks-analyst-section-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.{#tisc-playbooks-analyst__tisc-playbooks-analyst-p-4}

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.{#tisc-playbooks-analyst__tisc-playbooks-analyst-p-5}

## Monitoring playbook status {#tisc-playbooks-analyst__tisc-playbooks-analyst-section-context-menu}

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.{#tisc-playbooks-analyst__tisc-playbooks-analyst-p-6}

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.{#tisc-playbooks-analyst__tisc-playbooks-analyst-p-7}

## Playbook completion {#tisc-playbooks-analyst__tisc-playbooks-analyst-section-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.{#tisc-playbooks-analyst__tisc-playbooks-analyst-p-8}

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.{#tisc-playbooks-analyst__tisc-playbooks-analyst-p-9}
* **[Threat Hunting Playbook](https://www.servicenow.com/docs/GtI0yd~gKqu7478zSss2aQ)**   
  The Threat Hunting playbook is a guided workflow for a TISC Case record that helps analysts move a threat hunt from an initial hypothesis to a final outcome.

**Related concepts**   

* [Workbench Overview](https://www.servicenow.com/docs/v09QNspsdgUKsjcssQ44nQ "The Workbench Overview page consists of the Case Tasks and Cases that are under Threat Analysts and their team.")
* [Working with Investigation Canvas](https://www.servicenow.com/docs/EprH7pyEqFs2LVQ4KGvJ5w "The Investigation Canvas is a key significant feature, which provides more valuable information for the Threat Intelligence (TI) analysts. It provides a structured framework by mapping one to one or one to many relationships and visualizing information related to observables, indicators of compromise (IOCs), or entities.")
* [Threat Hunting Playbook](https://www.servicenow.com/docs/GtI0yd~gKqu7478zSss2aQ "The Threat Hunting playbook is a guided workflow for a TISC Case record that helps analysts move a threat hunt from an initial hypothesis to a final outcome.")  
**Related tasks**   

* [Creating cases using Threat Analyst Workbench](https://www.servicenow.com/docs/Xb8x3ylFD6FijaDvKqX3WA "Cases are used to track information about a campaign or threat actor threatening your organization. After a case is created, you can add artifacts that allow you to review and analyze all related information from a single case or case task.")
* [Summarize a Case using generative AI](https://www.servicenow.com/docs/cR_IUVt2~1oWmLQRzSERog "Use to generate a concise summary of a case, including its key findings and recommended next steps.")
* [Creating case task using Threat Analyst Workbench](https://www.servicenow.com/docs/QIyOkhiAbQsuKQ~ncYN_TQ "Create case tasks to associate with case(s).")
* [Add artifacts to cases or case tasks](https://www.servicenow.com/docs/w7jOBRuuDQT6Qje2vs23wg "After you have created a case, you can view or add artifacts, such as security incidents, CIs, and indicators of compromise, to the case. These artifacts act as clues in solving the case.")
* [Run Enrichment Actions within a case](https://www.servicenow.com/docs/Gh87urOsiF~BhNjGZQsVqg "Use this section to understand how enrichments actions are performed on case(s).")
* [Generate a Case Report using generative AI](https://www.servicenow.com/docs/1bdvh6WMLeuGwDMntyZLaA "Generate an AI-based, structured, threat intelligence case report from the data in a case and export it for stakeholder distribution.")
* [Generate a Case Report using a template](https://www.servicenow.com/docs/6Y9mhLC9aae1X07xvHOfBg "Use a predefined report template to generate case reports. These reports include post investigation report or an executive summary report.")
* [Create a security incident from a TISC case](https://www.servicenow.com/docs/7EbUdWlsxwChV5xDotZntQ "Create security incidents and associate observables to the security incidents from a TISC case.")
* [Upload Secure File Attachments](https://www.servicenow.com/docs/~1CsuAO80SPkjnX1j_LDpQ "Use this section to understand on how to upload the secure file attachments to the case(s).")
* [Use the Threat Hunting Playbook](https://www.servicenow.com/docs/n2yAquNl9roiQ0pbDZmnNg "Run threat hunt on a Case record — from capturing the hunt hypothesis through to creating a Security incident or reporting.")
* [Add the Threat Hunting Playbook to a Case](https://www.servicenow.com/docs/iP9HucJ2wUHgDbKW5ol_Yw "If a Case does not meet the auto-trigger conditions for the Threat Hunting playbook, you can attach the playbook to the Case manually.")