# Runbooks

In the **Runbooks** module, users can create detailed guides for red teaming and penetration testing, documenting the procedures, vulnerabilities, and recommendations for enhancing security.

Runbooks work with the [**RunbooksDB**](https://docs.plextrac.com/plextrac-documentation/product-documentation/content-library/runbooksdb) repository in the **Content Library**, enabling the reuse of existing procedures, tactics, and methodologies with or without modifications to fit new test plans.

Users access the module by clicking **Runbooks** in the application's main menu.

<div align="left"><figure><img src="https://4252973360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXA6EayCcg12qfDcfXd%2Fuploads%2FqGbIQbCM1tPxSDfTyh3S%2Fimage.png?alt=media&#x26;token=1d9b7c25-0301-4157-941f-9348f236572d" alt=""><figcaption></figcaption></figure></div>

## Overview

In cybersecurity, professionals often rely on red teaming to test and strengthen their defenses. This process involves simulating real-world cyberattacks to assess vulnerabilities and response capabilities. During such engagements, teams create runbooks to guide actions and record findings.

These runbooks serve as comprehensive records, documenting various procedures and tactics employed during the engagements. They outline the steps the red team takes, the vulnerabilities they exploit, and the recommendations they make to improve security. In essence, runbooks are the playbook for these security exercises.

The ultimate objective of these engagements is to evaluate the red team's proficiency in executing attack procedures and the blue team's capability to detect, protect against, and respond to them. The outcomes of these engagements are compiled in reports, which are then shared with clients or internal teams. These reports offer valuable insights into the effectiveness of the existing security measures and provide recommendations for improvements.

The **Runbooks** module has two tabs:&#x20;

* **Engagements:** Displays all runbooks created for a client, including those in progress and those submitted as a report (if not deleted).&#x20;

<div align="left"><figure><img src="https://4252973360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXA6EayCcg12qfDcfXd%2Fuploads%2Ff8SJPDnQ3tPKByQtcaBp%2Fimage.png?alt=media&#x26;token=8bedb0b4-e2ca-4e36-8c31-7158ffe2f883" alt="" width="563"><figcaption></figcaption></figure></div>

* **Test Plans**: Displays all existing test plans created or imported.&#x20;

<div align="left"><figure><img src="https://4252973360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXA6EayCcg12qfDcfXd%2Fuploads%2FnPUwXyz41TLewshKFxgk%2Fimage.png?alt=media&#x26;token=8b39bdff-1c62-4173-a2d3-77c10ae6c6fd" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**RunbooksDB** is accessible from both tabs by clicking **Manage RunbooksDB**.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.plextrac.com/plextrac-documentation/product-documentation/runbooks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
