Data Loss Prevention (DLP) Profile

Updated: July 8, 2026

Want to summarize with AI?

Learn how a Data Loss Prevention profile detects sensitive data in egress traffic and supports compliance protection with predefined or custom patterns.

The DLP (Data Loss Prevention) profile provides Multicloud Defense customers with the ability to specify policy rules to detect and take action upon finding exfiltration patterns in the data when the Multicloud Defense solution is deployed in the forward proxy (egress) mode.

Multicloud Defense allows customers to specify common pre-packaged data patterns such as Social Security Numbers (SSN), AWS secrets, credit card numbers etc., in addition to custom PCRE based regular expression patterns. This makes it easy to enforce protections for PCI, PII, and PHI data to meet compliance requirements. This feature is integrated with the existing Multicloud Defense feature set requiring no separate DLP services.

Create a Data Loss Prevention Profile

Procedure

	1.	Navigate to Policies > Profiles > Data Loss Prevention.
	2.	Click Create Intrusion Profile.
	3.	Select Data Loss Prevention.
	4.	Provide a unique Name and enter a description for the profile.
	5.	Enter the DLP Filter List in the table.
	6.	Click Add to insert more rows as needed.
	7.	Provide a Description for the filter.
	8.	Choose a predefined static pattern (e.g CVE Number) from the dropdown list or provide a custom Regular expression.
	9.	Provide a count to define the number of times the pattern must be seen in the traffic.
	10.	Select an Action to take if the pattern matches the count number of times. Note There are cases where the pre-defined pattern for AWS Access Key and AWS Secret Key doesn’t match in DLP inspection due to pattern being more restrictive. Use the following relaxed custom pattern in DLP profile to detect AWS Access Key and AWS Secret Key. Be aware that this could generate false positives log events. `AWS Access Key: (?<![A-Z0-9])[A-Z0-9]{20}(?![A-Z0-9])` `AWS Secret Key: (?<![AZa-z0-9/+=])[A-Za-z0-9/+=]{40}(?![A-Za-z0-9/+=])`

What to do next

Attach the profile to a policy rule set. See Rule Sets and Rule Set Groups for more information.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.