Glean lint should automatically flag event dictionary keys labeled "url" or other potentially-indicative-of-PII key names
Categories
(Data Platform and Tools :: Glean: SDK, enhancement, P1)
Tracking
(Not tracked)
People
(Reporter: Gijs, Assigned: janerik)
Details
Attachments
(1 file)
We already have some checks that enforce that certain types of metrics have a particular declared data sensitivity (though I looked and couldn't easily find the code that does that?), but we should expand this to event keys to avoid mis-collecting data at the patch creation stage, instead of later in the process during human review.
Comment 1•4 months ago
•
|
||
(In reply to :Gijs (he/him) from comment #0)
We already have some checks that enforce that certain types of metrics have a particular declared data sensitivity (though I looked and couldn't easily find the code that does that?),
It's enforced by the schema, and apparently it's only for text, not for url like I expected. Huh.
| Assignee | ||
Updated•4 months ago
|
Comment 2•4 months ago
|
||
| Assignee | ||
Comment 3•3 months ago
|
||
badboy merged PR [mozilla/glean_parser]: Bug 1973017 - New lint: HIGHER_DATA_SENSITIVITY_REQUIRED for when an event extra key could potentially contain sensitive data (#799) in fa3cfc5.
Description
•