Tying EVM into LSM Policy
summary
EVM gets tied into LSMs by using AppArmor profile attachments based on extended attributes so files with a protected security.EVM xattr run in a trusted profile while others run untrusted; IMA appraises signatures after credentials commit via the IMA creds_check hook so elevated rights require a valid signature. Supports HMAC and non–SHA1 hashes, handles 500 MB binaries (FUSE forces rehash on every open), Debian packaging integration remains work in progress, and runtime overhead is minimal.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:40How do you secure a fleet of developer machines?
- 5:31Integrity Measurement Architecture (IMA)
- 6:56Taking IMA further - Extended Validation Module
- 9:03EVM wasn't ideally suited for what we wanted
- 11:28How do we tie these together?
- 16:07What does it look like?
- 17:00But what about interpreted languages?
- 19:39We can add more complexity
- 21:25But hashing is slow
- 27:25Summary
related talks
01h 14mLSM Updates: IMA, SELinux, AppArmor, SMACK &...
16mSub-system Update: Linux Integrity Status Update
43mIntegrity Policy Enforcement: Full System Integrity Verification
39mIntegrity Protection and Access Control - Who Do You Trust?
33mBinary Policy with IMA and AppArmor
32mUsing a Different LSM from the Host in a Container
19mSubsystem Update: Linux Integrity Status Update
30mLSM Stacking - What You Can Do Now and What's Next
