: Test an Enterprise DLP Data Profile Using Dry Run Mode
Focus
Focus

Test an Enterprise DLP Data Profile Using Dry Run Mode

Table of Contents

Test an Enterprise DLP Data Profile Using Dry Run Mode

Test the efficacy of your Enterprise Data Loss Prevention (E-DLP) data profiles to verify it accurately detect the expected sensitive data.
Test the efficacy of your Enterprise Data Loss Prevention (E-DLP) data profiles before adding them to your Security policy rule and pushing them to your production NGFW and Prisma Access tenants. This allows you to validate your data profiles against a file containing known sensitive data to ensure accurate detection by Enterprise DLP. Testing and fine-tuning your data profile match criteria before pushing them to your production environment strengths your security posture by allowing you to continuously iterate on your data patterns and profiles to identify and address gaps in a controlled environment. You can run a test on a data profile currently being configured or on an existing data profile. The data profile test results show a high-level summary of the type of data profile you're testing, the number of instances of High, Medium, and Low confidence detections, and snippets of the sensitive data detected.
There are two types of test results Enterprise DLP can return:
  • Matched Test ResultEnterprise DLP returns a Matched verdict and successfully detected sensitive data matching the sensitive data match criteria configured in the data profile. There are two types of matched test results:
    • Successful Test ResultEnterprise DLP successfully detected all sensitive match criteria configured in the data profile.
    • Partial Test ResultEnterprise DLP returns a Matched verdict and successfully detected some but not all sensitive match criteria configured in the data profile.
  • No Match Test ResultEnterprise DLP returns a Not Matched verdict result because Enterprise DLP did not detect any sensitive data in the test file matching the sensitive data match criteria configured in the data profile.