Closed Bug 1415337 Opened 7 years ago Closed 1 year ago

Collect telemetry on dll blocklist startup and use

Categories

(Toolkit :: Blocklist Implementation, enhancement, P3)

Product:
Toolkit
Component:
Blocklist Implementation
Platform:
All
Windows
Type:
enhancement

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: jimm, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: inj+) 

We have various dll blocking mechanism in different processes. We should collect telemetry on the successful initialization of these lists. We should also collect information on what dlls they block.
Summary: Collect telemetry on dll blocklist startup → Collect telemetry on dll blocklist startup and use
Priority: -- → P3
Whiteboard: inj+
Component: Blocklist Policy Requests → Blocklist Implementation
Severity: normal → S3

FWIW we do have telemetry around entries around the dynamic DLL blocklist and DLLs that actually get blocked (whether from the static or dynamic DLL blocklist)

(In reply to Greg Stoll from comment #1)

FWIW we do have telemetry around entries around the dynamic DLL blocklist and DLLs that actually get blocked (whether from the static or dynamic DLL blocklist)

Should we close this as WFM?

Flags: needinfo?(gstoll)

(In reply to :Gijs (he/him) from comment #2)

(In reply to Greg Stoll from comment #1)

FWIW we do have telemetry around entries around the dynamic DLL blocklist and DLLs that actually get blocked (whether from the static or dynamic DLL blocklist)

Should we close this as WFM?

Yes, I think so.

For the record, the third-party-modules ping records blockedModules, which is the list of modules that are on the dynamic blocklist, and processes.events.loadStatus tracks whether a module's load was successful or blocked.

Flags: needinfo?(gstoll)
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.