Open Bug 2086267 Opened 19 days ago

Upstream the built-in (wasm) DLP engine policies and integration

Categories

(Firefox :: Data Loss Prevention, enhancement)

enhancement

Tracking

()

People

(Reporter: jmendez, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

Firefox Enterprise has a built-in data loss prevention (DLP) engine: an in-process wasm module that warns on or blocks data actions according to rules set by the DataLossPrevention enterprise policy, as an alternative to an external Content Analysis agent. The runtime host for the module (WasmModuleBackend, ContentAnalysisWasmRunner, the rule parser) is already in mozilla-central (bug 2044479, bug 2050473, bug 2044490), although now somewhat outdated in how to retrieve the wasm module. This bug upstreams the rest of the enterprise-firefox work. All of it is active only in MOZ_ENTERPRISE builds.

  • The DataLossPrevention policy, and its precedence against the external ContentAnalysis policy (bug 2044495, bug 2042853, bug 2071818).
  • Fetching the wasm module from the enterprise console instead of from a signed extension (bug 2044493). If the enterprise console client is not upstream yet, this may add a stub ConsoleClient that the real implementation can replace once it is upstreamed.
  • Showing the admin-provided rule message in the warn and block dialogs, with a test wasm module built from source (bug 2062380, bug 2067909).
  • DLP verdict telemetry in the enterprise ping, controlled by a new ContentAnalysisTelemetry policy (bug 2043142).
  • Live updates of the ContentAnalysis and DataLossPrevention policies (bug 2058222). If live policy support for Firefox Enterprise is not yet upstreamed, this would stay inert until that happens.
  • Update about:support to show whether Content Analysis is using the built-in engine (bug 2078668).
You need to log in before you can comment on or make changes to this bug.