Closed Bug 2013488 Opened 7 months ago Closed 5 months ago

Security layer - Implement tainting for all actions/input and enforce policy based on those two criteria

Categories

(Core :: Machine Learning: General, task)

task

Tracking

()

RESOLVED WONTFIX

People

(Reporter: freddy, Unassigned)

References

(Blocks 1 open bug)

Details

  1. Implement Global Taint State per context
  2. Implement Input Taint Injection & Tagging.
  3. Define Taint Propagation Rules for LLM output.

Once that is done:

  • Implement Action Sensitivity Mapping (Sinks).
  • Implement Policy Enforcement Logic
  • Implement/Experiment with different (user visible) enforcement results (url filtering, compacting context, asking for permission)
Summary: Security layer - Implement tainting for all actions/input → Security layer - Implement tainting for all actions/input and enforce policy based on those two criteria
Depends on: 2014959
Depends on: 2014958
Depends on: 2014960
Depends on: 2014961
Depends on: 2016727
Depends on: 2019693
Depends on: 2018787

I'm taking this out of blocking the MVP as it's a bit of a duplicate of Bug 2020825 (which I filed). However, there are more details here that aren't in the security alignment doc. There are a bunch of dependent bugs so I'm hesitant to do any more work moving things around until after the MVP.

No longer blocks: swsecmvp

This isn't in the security alignment doc, and pieces of this work have been completed. We can file new bugs for more well defined work here. We implemented SecurityProperties and other mechanisms for tracking "tainting flags" and their enforcement. If we want a more elegant design, we can specify that work.

Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.