Forensics for Public Cloud
Forensics for Public Cloud
With Forensics, you can see all the information you need in terms of what your users are doing in the cloud and what you should be looking at. When a violation is found, the object is placed in a forensics folder so you can review the specific types of sensitive data that are exposed. An automated cloud policy enforcement program is necessary for getting to a quick resolution and remediation.
To use forensics, you need to:
- Configure API Data Protection for the public cloud service you want to store forensics data.
- Create a forensic profile to define the destination folder in which files that violate DLP policies can be stored.
- Enable the forensic profile.
- Review the violations within specific files and take remedial action by contacting users and managing files in the forensics folder.
To learn more, review the following sections:
- Getting Started with Forensics for Public Cloud
- Enabling Forensics for Amazon Web Services S3
- Enabling Forensics for Azure Blob Storage
- Enabling Forensics for Google Cloud Storage
- Creating a Forensic Profile for Public Cloud Storage
- Viewing Forensic Alerts for Public Cloud Storage
- Troubleshooting Forensics Setup for Public Cloud
Articles
- Getting Started with Forensics for Public Cloud
- Enabling Forensics for Amazon Web Services S3
- Enabling Forensics for Azure Blob Storage
- Step 1/3: Configure a Microsoft Entra ID Application for Forensics
- Deprecation Notice for Classic Azure Blob Storage as a Forensic Destination
- Step 2/3: Assign Azure permissions to store forensic objects
- Step 3/3: Set up a Netskope instance with Azure App Registration credentials
- Azure forensics Instance Re-grant FAQs
- Enabling Forensics for Google Cloud Storage
- Creating a Forensic Profile for Public Cloud Storage
- Viewing Forensic Alerts for Public Cloud Storage
- Troubleshooting Forensics Setup for Public Cloud
