jcoffey-dev is traveling from Thursday 1 October through Sunday 4 October. Issues and pull requests are welcome, and will get an answer after that. Thanks for your patience.
Phase 1 of DLP and the rule builder, specced together: docs/spec/features/dlp-and-mail-flow-rules.md.
One native rule engine at DATA, after the system Sieve script and before DKIM signing; hand-written Sieve untouched.
DLP on outgoing mail: counted detectors (payment cards with Luhn, IBAN mod 97, US SSN, word lists, patterns) plus attachment conditions; block, warn with an audited override, or hold for review.
Hold keeps the message in the queue unscheduled with a review record, so the queue format is unchanged across a rolling upgrade.
Audit records name the rules and counts, never the matched text.
Six questions under For John; nothing is built until they are answered.
Phase 1 of DLP and the rule builder, specced together: `docs/spec/features/dlp-and-mail-flow-rules.md`.
- One native rule engine at DATA, after the system Sieve script and before DKIM signing; hand-written Sieve untouched.
- DLP on outgoing mail: counted detectors (payment cards with Luhn, IBAN mod 97, US SSN, word lists, patterns) plus attachment conditions; block, warn with an audited override, or hold for review.
- Hold keeps the message in the queue unscheduled with a review record, so the queue format is unchanged across a rolling upgrade.
- Audit records name the rules and counts, never the matched text.
- Six questions under **For John**; nothing is built until they are answered.
Phase 1: one native rule engine at DATA, after the system Sieve script,
for both DLP policies and transport rules. DLP checks outgoing mail
with counted detectors (payment cards, IBAN, US SSN, word lists,
patterns) and blocks, warns with an audited override, or holds for
review. Held mail stays in the queue unscheduled, with its own review
record, so the queue's stored format is unchanged. Matches go to the
audit log without the matched text. Six questions for John at the end.
All six settled as recommended. Answer 6 ("and any other recognized and protected PII") becomes a catalog of identifiers with published formats and checks, grouped by region, each either checked by its check digit or counted only beside a corroborating word, plus templates named for what they find. Data with no number to find is covered by word lists and not claimed as detection. Office documents are read; PDF counts as can't be inspected.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Phase 1 of DLP and the rule builder, specced together:
docs/spec/features/dlp-and-mail-flow-rules.md.All six settled as recommended. Answer 6 ("and any other recognized and protected PII") becomes a catalog of identifiers with published formats and checks, grouped by region, each either checked by its check digit or counted only beside a corroborating word, plus templates named for what they find. Data with no number to find is covered by word lists and not claimed as detection. Office documents are read; PDF counts as can't be inspected.