Updated on 2026-11-17 GMT+08:00

Handling a To-Do Task

Scenarios

Common task types include workflow release, playbook release, and playbook node review.

  • Workflow release: Before enabling a workflow, you need to review the workflow version. There are two methods for reviewing a workflow version:
    • Method 1: Choose Situation Awareness > Task Center > To-Dos and click Review in the Operation column of the target task. This method is described in this section.
    • Method 2: On the workflow version management page, click Review in the Operation column of the target workflow.
  • Playbook release: Before enabling a playbook, you need to review the playbook version. There are two methods for reviewing a playbook version:
    • Method 1: Choose Situation Awareness > Task Center > To-Dos and click Review in the Operation column of the target task. This method is described in this section.
    • Method 2: On the playbook version management page, click Review in the Operation column of the target playbook.
  • Playbook node review: If a playbook reaches a manual review node, it needs to be manually reviewed before it can proceed. For example, if the Mining host isolation playbook reports an HSS alarm whose Alarm Type is Mining program or Mining software, the playbook automatically generates a to-do task for O&M engineers to isolate the host.

If a workflow or playbook release to-do task is not handled within the specified period, the task will be deleted from the to-do task list. However, you can still handle it on the corresponding workflow or playbook version management page. For details, see Reviewing a Workflow Version and Reviewing a Playbook Version.

If a review task for a playbook node is not handled within the specified period, the corresponding workflow will either be interrupted or continue executing, depending on the post-expiration task handling mode configured for the manual review node.

So, you need to check and handle to-do tasks in a timely manner.

Basic Concepts

In security orchestration, playbooks and workflows are core elements. They are associated, dependent on each other, and work together to enable efficient security operations.

  • Playbooks

    A playbook is a formal representation of the security operations workflow in a security orchestration system. A playbook converts the security operations workflows and procedures into a machine-readable workflow. A playbook is a predefined, structured response plan used to handle specific types of incidents or threats. A playbook explicitly lists the steps and actions to be taken under certain trigger conditions, such as the detection of a specific security incident.

    Playbooks embody the logic of security controls and schedule security capabilities. Playbooks are flexible and scalable. They can be modified and extended based on actual requirements to adapt to ever-changing security threats and service requirements.

  • Workflows

    A workflow is a collaborative work mode that integrates various capabilities related to security operation, such as tools, technologies, processes, and personnel. It consists of multiple connected components. After being defined in a workflow, these components can be triggered externally. For example, when a new service ticket is generated, the automatic service ticket review workflow is automatically triggered. You can define component actions for each node in a workflow on a visual canvas.

    A workflow is a response mode when a playbook is triggered. Workflows convert instructions and procedures in the corresponding playbooks into specific actions and execution steps.

  • Relationship between playbooks and workflows

    A playbook provides guidance and rules for secure operations, and its workflow is responsible for converting these rules into specific execution steps and actions. A playbook and its workflow depend on each other. The playbook guides the execution of the workflow, while the workflow implements the intent and requirements of the playbook.

  • Differences between playbooks and workflows

    There are also some differences between playbooks and workflows. First, playbooks focus more on defining and describing security operation processes and regulations, so they focus on the overall framework and policies. Workflows focus more on specific actions and execution steps, so they focus on how to convert requirements in playbooks into actual actions. Second, playbooks are flexible and scalable, and can be modified and extended as required. However, workflows are relatively fixed. Once the design is complete, they need to follow the specified steps.

  • Examples

    Take a specific cyber security incident response case as an example. When an organization suffers from a cyber attack, the security orchestration system first identifies the attack type and severity based on the preset playbook. Then, the system automatically triggers corresponding security measures based on the workflow defined in the playbook, such as isolating the attacked system, collecting attack data, and notifying the security team. During the process, playbooks and workflows work closely to ensure the accuracy and timeliness of security responses.

Prerequisites

A playbook task has been triggered, and manual actions are required for completing the task.

Handling a To-Do Task

  1. Log in to the SecMaster console.
  2. Click in the upper left corner of the management console and select a region or project.
  3. In the navigation pane on the left, choose Workspaces > Management. In the workspace list, click the name of the target workspace.

    Figure 1 Workspace management page

  4. In the navigation pane on the left, choose Situation Awareness > Task Center.

    Figure 2 To-Dos

  5. In the row containing the target to-do task, click Approve in the Operation column.

    The approval mode varies according to the service type.
    • Playbook release: The Playbook Release page is displayed on the right. Enter review comments and approve the playbook as prompted.
    • Process release: The Process Release page is displayed on the right. Enter the Comment and approve the application as prompted.
    • Playbook-Node Review: The Playbook-Node Review page is displayed on the right. You can select Continue or Terminate. If the to-do node is in a sub-workflow, its details cannot be queried. However, you can view the playbook and workflow instances. To do so, choose Security Orchestration > Playbooks > Instance Management in the navigation pane on the left of the workspace and search for the playbook instance or workflow instance by the to-do node instance name.

  6. In the navigation pane on the left, choose Situation Awareness > Task Center, click the Completed tab, and check completed tasks.

Related Operations