> 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/sharepoint-playbooks-for-malware-propagation-prevention.md).

# SharePoint playbooks for malware propagation prevention

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

## Notify on ransomware encryption file upload

When someone uploads a ransomware encryption key to SharePoint, the Security team is automatically notified in Slack.

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the SharePoint app or malware category.
3. Select the **Notify on ransomware encryption file upload** 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%2FmPZZU0cVWMNcECjhzznC%2Fmalware%20PB%20SharePoint.png?alt=media&amp;token=8d188e69-be53-4b44-951d-6b47df5f8814" alt=""><figcaption></figcaption></figure>
5. Under the **Fileuploaded** event, define the relevant conditions:
   * The `Get file extension` condition is equal to a ransomware encryption file, such as .micro, .zepto, .cerber, .locky, .onion, etc.
   * Add any relevant conditions.
6. Customize the Slack message to send to the Security team.


---

# 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/sharepoint-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.