diff --git a/docs/api/data-deletion-rules.md b/docs/api/data-deletion-rules.md new file mode 100644 index 0000000000..59ea094326 --- /dev/null +++ b/docs/api/data-deletion-rules.md @@ -0,0 +1,44 @@ +--- +id: data-deletion-rules +title: Data Deletion Rules APIs +sidebar_label: Data Deletion Rules +description: Data Deletion Rules APIs allow you to delete ingested data from Sumo Logic. +--- + + + + + +

Beta

+ +import useBaseUrl from '@docusaurus/useBaseUrl'; +import ApiIntro from '../reuse/api-intro.md'; +import ApiRoles from '../reuse/api-roles.md'; + +icon + +Data Deletion Rules allow you to quickly and easily request the removal of ingested data from Sumo Logic. This helps you with removal of inadvertently ingested sensitive data. + +## Documentation + + + +|Deployment|Documentation URL | +|:----------|:-------------------| +|AU |https://api.au.sumologic.com/docs/#tag/dataDeletionRules | +|CA |https://api.ca.sumologic.com/docs/#tag/dataDeletionRules | +|DE |https://api.de.sumologic.com/docs/#tag/dataDeletionRules | +|EU |https://api.eu.sumologic.com/docs/#tag/dataDeletionRules | +|FED |https://api.fed.sumologic.com/docs/#tag/dataDeletionRules | +|JP |https://api.jp.sumologic.com/docs/#tag/dataDeletionRules | +|KR |https://api.kr.sumologic.com/docs/#tag/dataDeletionRules | +|US1 |https://api.sumologic.com/docs/#tag/dataDeletionRules | +|US2 |https://api.us2.sumologic.com/docs/#tag/dataDeletionRules | + +## Required role capabilities + + + +* Review Deletion Requests +* Manage Deletion Requests +* View Deletion Requests diff --git a/docs/manage/deletion-requests.md b/docs/manage/deletion-requests.md index ae2cc2b080..246be87a6c 100644 --- a/docs/manage/deletion-requests.md +++ b/docs/manage/deletion-requests.md @@ -34,6 +34,7 @@ After a data deletion request is approved, data will be deleted from the organiz :::note - During the data deletion process, existing messages may temporarily appear duplicated for a few seconds. These duplicated messages will automatically disappear once the data deletion is complete. - Pinned queries may continue to display data identified for deletion for up to 24 hours from the initial run, prior to the data deletion request approval. +- Data deletion requests are automatically canceled after 30 days if no action is taken. ::: :::info @@ -52,7 +53,11 @@ Data cannot be recovered once it gets deleted. Ensure that you have appropriatel ::: 1. Select the **Time Range** when the data was ingested. 1. When you're done, click **Save**. -1. Your request will go to a Sumo Logic Customer Support Manager (CSM) for review and approval. You can check on your request in the **Status** column.
deletion request status +1. An email about your request will be sent to 50 most recently active approval users with [approval access](#approve-the-deletion-request). You can check on your request in the **Status** column. + :::note + If you require an approval apart from this 50 users, you can forward the deletion request approval email to the required users. + ::: + deletion request status ### From a Log Search @@ -88,12 +93,27 @@ To cancel a data deletion request: screenshot showing how to cancel a deletion request +## Approve the deletion request + +:::note +To approve or reject a request, ensure you have the **Review Deletion Requests** [role capability](/docs/manage/users-roles/roles/role-capabilities/). By default, **Manage Deletion Requests** and **View Deletion Requests** capabilities will be added if you have the **Review Deletion Requests** capability. +::: + +Once the deletion request is created, an email notification will be sent to the users who have approval access. To approve or reject the request, follow the steps below: + +1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). Go to **Manage Data > Logs > Deletion Requests**.
[**New UI**](/docs/get-started/sumo-logic-ui). In the Sumo Logic main menu select **Data Management**, and then under **Logs** select **Deletion Requests**. +1. Filter for the status with **Pending review**. filter for pending deletion requests +1. Click the deletion request to review it. +1. **Approve** or **Reject** the request based on your requirement.
Approve/Reject deletion requests side panel + - **Approve**. Enter **Delete** in the **Approve Deletion Request** pop-up to permanently delete the data, and click the **Delete Data** button.
Approve deletion requests pop-up + - **Reject**. Enter the reason for rejection in the **Reject Deletion Request** pop-up to help the requester understand the reason for rejection and take any necessary actions, and click the **Reject Request** button.
Reject deletion requests pop-up + ## Limitations - Deletion requests will be processed one by one. - You can create upto 100 deletion requests at a time. - Each deletion request can include up to 1 petabyte (PB) of scanned data. -- You can delete up to 1,000,000 messages per request. +- You can delete up to 1,000,000 messages per request. - The maximum time range for each deletion request is one year. - Your system can support up to 10 active concurrent deletion tasks across different customers. - Ensure that the requests initiated are not deleting the data prior to `1st February 2024`. Any request before this timestamp will fail in creation. diff --git a/static/img/search/get-started-search/approve-deletion-request.png b/static/img/search/get-started-search/approve-deletion-request.png new file mode 100644 index 0000000000..6160c2a05c Binary files /dev/null and b/static/img/search/get-started-search/approve-deletion-request.png differ diff --git a/static/img/search/get-started-search/approve-reject-deletion-request.png b/static/img/search/get-started-search/approve-reject-deletion-request.png new file mode 100644 index 0000000000..fcff545c1e Binary files /dev/null and b/static/img/search/get-started-search/approve-reject-deletion-request.png differ diff --git a/static/img/search/get-started-search/pending-requests.png b/static/img/search/get-started-search/pending-requests.png new file mode 100644 index 0000000000..84586eca93 Binary files /dev/null and b/static/img/search/get-started-search/pending-requests.png differ diff --git a/static/img/search/get-started-search/reject-deletion-request.png b/static/img/search/get-started-search/reject-deletion-request.png new file mode 100644 index 0000000000..0acd1a6f4a Binary files /dev/null and b/static/img/search/get-started-search/reject-deletion-request.png differ