Infoflow LSM
summary
A new LSM called Infoflow enforces a concrete integrity policy by mapping SELinux source labels to an explicit TCB and setting a TCB bit in xattr on created files; a user‑space analysis tool ingests observed process‑file interactions and emits policy that Infoflow loads into a red‑black tree of SIDs. It runs in discover/enforce/permissive modes, integrates EVM HMACs and TPM sealing for stable PCRs, blocks out‑of‑TCB writes in the demo, and is published on GitHub; current overhead comes from per‑permission tree lookups with a proposed creds‑based optimization.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:50Agenda
- 1:05Integrity Policy
- 1:51Integrity Definition
- 2:17Integrity Policies
- 3:20Linux Security Model
- 5:53Multilevel Security Model
- 8:01Integrity Policy Enforcement
- 8:57Multiple Security Models
- 9:47LSM Framework
- 11:10Decision Part
- 11:50Policy Format
- 13:14Security Context
- 15:30Security Identifier
- 16:07Case Study
- 28:57Conclusion
- 30:52Filtering interface
- 32:54Remote attestation
- 36:32TCB
- 37:53Flame Protection
- 41:42Linux Enforcement
related talks
43mIntegrity Policy Enforcement: Full System Integrity Verification
27mBPF LSM - Updates and What next?
01h 14mLSM Updates: IMA, SELinux, AppArmor, SMACK &...
41mThe State and Direction of LSM Stacking
52mLSM Maintainers Panel
30mLSM Stacking - What You Can Do Now and What's Next
34mTying EVM into LSM Policy
26mHornet LSM