DLP: Brazil CPF Number

Severity: high
Type: dlp
Source: github.com/sublime-security/sublime-rules

Detects messages containing Brazilian Natural Persons Register (CPF) numbers.

Event coverage

Message attribute
body.current_thread
sender.email
subject
type

Rule body MQL

type.outbound
and any([body.current_thread.text, subject.subject],
        // CPF: 11 digits in XXX.XXX.XXX-XX format
        regex.contains(., '\b\d{3}\.?\d{3}\.?\d{3}-?\d{2}\b')
)
and any([body.current_thread.text, subject.subject],
        regex.icontains(., 'CPF|cadastro\s+de\s+pessoas|tax\s+ID')
)
and (
  strings.icontains(sender.email.domain.tld, "br")
  or strings.icontains(body.current_thread.text, "brazil")
  or strings.icontains(body.current_thread.text, "brasil")
)

Detection logic

Scope: outbound message.

Detects messages containing Brazilian Natural Persons Register (CPF) numbers.

outbound message
any of [body.current_thread.text, subject.subject] where:
- . matches '\\b\\d{3}\\.?\\d{3}\\.?\\d{3}-?\\d{2}\\b'
any of [body.current_thread.text, subject.subject] where:
- . matches 'CPF|cadastro\\s+de\\s+pessoas|tax\\s+ID'
any of:
- sender.email.domain.tld contains 'br'
- body.current_thread.text contains 'brazil'
- body.current_thread.text contains 'brasil'

Inspects: body.current_thread.text, sender.email.domain.tld, subject.subject, type.outbound. Sensors: regex.contains, regex.icontains, strings.icontains.

Indicators matched (5)

Field	Match	Value
`regex.contains`	regex	`\b\d{3}\.?\d{3}\.?\d{3}-?\d{2}\b`
`regex.icontains`	regex	`CPF\|cadastro\s+de\s+pessoas\|tax\s+ID`
`strings.icontains`	substring	`br`
`strings.icontains`	substring	`brazil`
`strings.icontains`	substring	`brasil`

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)

DLP: Brazil CPF Number

Event coverage

Rule body MQL

Detection logic

Indicators matched (5)

Keyboard shortcuts

Search operators