> 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/workflows/bulk-remediation/preparation-and-best-practices.md). # Preparation and best practices DoControl bulk remediation at scale is a powerful and unique capability. Follow our [preparation](#prepare-for-bulk-remediation) recommendations and [best practices t](#best-practices-for-bulk-remediation)o make informed decisions and take action swiftly. With our [step-by-step ](/docontrol-user-guide/workflows/bulk-remediation/apply-a-bulk-action.md)instructions, DoControl will enable you to confidently and effectively remediate file permissions, reduce risk, and enhance your organization's data security. ## Prepare for bulk remediation With bulk remediation, the number of assets that match your criteria could be very high, even hundreds of thousands, or millions. The best way to remediate is to understand your requirements first, and then break them down into a few remediation iterations. ### Export report of exposed assets DoControl recommends exporting a CSV report of your exposed assets before running a bulk remediation action. 1. In **Assets**, use the inventory filters and export a CSV report of your selected assets. 2. If necessary, refine your inventory filters. 3. Send the selected files for remediation assessment. You’ll receive a report indicating the number of assets and their breakdown, as well as affected folders. 4. Break the filters into smaller batches that you can remediate in iterations, in order to monitor the remediation progress. #### Here's an example of filtering assets for bulk remediation: 1. You wish to remediate all files with these filters:\ Sharing status equals `external` and `last modified before 01/01/2023.` 2. Break your remediation into the following batches: * **My Drive:** Sharing status equals `external` and `last modified before 01/01/2020` * **Shared drives:** Sharing status equals `external` and `last modified before 01/01/2020` * **My Drive:** Sharing status equals `external` and `last modified before 01/01/2022` * **Shared drives:** Sharing status equals `external` and `last modified before 01/01/2022` ### Create a new workflow 1. If you don't have the relevant workflow in place, make sure to use the DoControl playbooks to create a new workflow, such as Remove External Collaborator, to remediate assets. 2. When remediation is complete, you can monitor the progress and results of your action in the [workflow activity](/docontrol-user-guide/workflows/activity-dashboard.md#filter-workflow-activity) screen. ## Best practices for bulk remediation DoControl recommends following these best practices to achieve the best results when remediating in bulk: 1. **Define clear objectives and file exposure criteria**\ Before initiating the remediation process, it's crucial to establish precise goals and criteria. Identify which files or folders are considered overexposed. \ Clarity in objectives ensures that your remediation efforts are aligned with your organization's security and compliance objectives. 2. **Review and test the remediation workflow**\ Review and test the remediation workflow and its impact on test file permissions. It's essential to test the workflow in a controlled environment to identify any issues or unintended consequences. This step minimizes risks and helps fine-tune the process for optimal results. 3. **Communicate changes to users before remediation**\ Effective communication is key to a successful remediation process. Notify relevant users or stakeholders about the upcoming changes in file permissions. Explain the reasons behind the changes, address concerns, and offer support if needed. Transparent communication builds trust and ensures that users are prepared for the adjustments, reducing potential disruptions or misunderstandings. {% hint style="warning" %} **Remember**: The remediation process only remediates permissions. DoControl does not edit or delete the files themselves. So bulk remediation should not result in any major business impact. If a permission was removed by mistake, it can always be added again. {% endhint %} --- # 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/workflows/bulk-remediation/preparation-and-best-practices.md?ask=&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.