Skip to content

Forum

AI Assistant
Forums
OpenClaw
Sandboxing and Exec...
Seccomp, AppArmor, ...
 
Notifications
Clear all

Seccomp, AppArmor, and LSM Profiles

Writing and tuning Linux Security Module profiles for OpenClaw workloads — sharing working seccomp filters, AppArmor profiles, and discussion of what each syscall restriction actually buys you.
RSS
Page 1 / 4

Thoughts on the new kernel lockdown LSM and whether it helps with agent security?

Last post by David Kim, 13 minutes ago

Posts: 3
Views: 4


ELI5: what is an LSM and why should I care about it for my local agent?

Last post by Priya Nair, 46 minutes ago

Posts: 1
Views: 0


Check out what I made: a reusable AppArmor profile for agents that only need HTTP/2 access

Last post by Sasha Volkov, 5 days ago

Posts: 35
Views: 9


Guide: writing an AppArmor profile that allows file reads but blocks all writes except to /tmp

Last post by Connie Becker, 5 days ago

Posts: 1
Views: 2


Step-by-step: using bpftrace to trace syscalls and build a seccomp whitelist

Last post by David Kirsch, 5 days ago

Posts: 38
Views: 7


Help: my seccomp filter works on x86 but breaks on ARM — what am I missing?

Last post by Samir Patel, 5 days ago

Posts: 26
Views: 23


Hot take: the seccomp filters in most agent SDKs are security theater without a threat model

Last post by Raj P., 7 days ago

Posts: 14
Views: 3


Check out what I made: a GitHub repo of battle-tested AppArmor profiles for Claw runtimes

Last post by Luis G., 7 days ago

Posts: 11
Views: 5


What's the best way to log seccomp violations without killing the agent process?

Last post by Mike Chen, 1 week ago

Posts: 11
Views: 12


Switched from a generic seccomp filter to one generated by sysdig, here's the difference

Last post by Tom Smith, 1 week ago

Posts: 7
Views: 4


Page 1 / 4
Share:
Share
Tweet
Share