Ensure alerting after a threshold of credit card or Social Security numbers is detected is enabled

How it is checked

Audit method: Configuration pattern

Pattern

(?m)^set (?:shared |vsys \S+ |device-group \S+ |template \S+ config (?:shared |vsys \S+ )?)?profiles data-filtering (?:"[^"\n]*"|\S+) rules (?:"[^"\n]*"|\S+) [^\n]*\balert-threshold [1-9]\d*\b

How it is fixed

Fix method: Guidance or infrastructure patch

configure set profiles data-filtering <profile> rules cc-ssn data-object <pattern> alert-threshold 20 block-threshold 0 log-severity informational commit # CIS guidance: Navigate to Objects > Custom Objects > Data Patterns. Create an appropriate Data Pattern that accounts for sensitive information within your organization. In most cases this will include Credit Card Numbers, and your jurisdiction's equivalent of Social Insurance Numbers. In many cases these can simply be picked from the list of Predefined Patterns. Navigate to Objects > Security Profiles > Data Filtering. Create appropriate Data Filtering Profile, using the created Data Patterns. Ensure that an Alert Threshold is set that generates alerts appropriately. A typical starting value for Alert Threshold is 20, but this should be adjusted after appropriate testing.

Check this host

Run this on a machine you are allowed to audit. The scan is read-only.

tmaegis scan --target paloalto