> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/risk-management/threat-model-coverage/malware-propagation-prevention/crowdstrike-playbooks-for-malware-propagation-prevention.md).

# CrowdStrike playbooks for malware propagation prevention

To mitigate the risk associated with malware propagation in Google Drive, you can define automated workflows for these use cases: 

## Remediate malware propagation in Google Drive

When CrowdStrike Falcon detects malware on an endpoint, the malware file is automatically deleted from Google Drive.

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the CrowdStrike app or malware category.
3. Select the **Remediate malware propagation in Google Drive** playbook.
4. Give an action name.<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fgvs6mNYJQkgrF4w5k4E4%2FMAlware%20PB%20CrowdStrike.png?alt=media&amp;token=2f447284-654a-4443-9443-b5307ba9ed25" alt=""><figcaption></figcaption></figure>
5. Under the **Endpoint malware detection** event, define the relevant conditions:
   * The `Maximum severity` condition is equal or greater than 50.
   * Add any relevant conditions.
6. Customize the **Get files by hash** action to retrieve a list of Google Drive asset IDs according to a matching hash file value.
7. Customize the **Delete file** action to delete the affected Google Drive assets.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docontrol.io/docontrol-user-guide/risk-management/threat-model-coverage/malware-propagation-prevention/crowdstrike-playbooks-for-malware-propagation-prevention.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.