{"slug": "apparmor", "name": "AppArmor", "category": "security", "category_name": "Security and passwords", "description": "", "recommenders": 3, "commenters": 3, "warners": 0, "score": 2.899, "rising": 3.0, "first": "2026-08-19", "latest": "2026-10-06", "why": "It's evident that Mandatory Access Control has become, ahem, mandatory.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 0, "compare": 0, "warn": 0}, "spark": [0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 0, 1], "listed": true, "loved": [], "caveat": "", "short_quote": "It's evident that Mandatory Access Control has become, ahem, mandatory.", "icon": true, "domain": null, "github_repo": null, "official_url": "https://apparmor.net", "pricing": "", "aliases": ["AppArmor"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 799567489, "item_id": 49972968, "url": "https://news.ycombinator.com/item?id=49972968", "by": "johnsmith1840", "date": "2026-10-06", "stance": "recommend", "quote": "App armor in linux is also nice gvisor like tool.", "excerpt": "For my assumed goal of yours I would say none of these are good options. A simple VM or ec2 node hosting a coding sandbox is likely the better option. All 3 of these are vastly different tech. Confusingly, you could run all 3 of these at the same time. I know that probally doesn't help. If you want to learn more I'd go get a linux machine somewhere like aws and play around with them. A local agent harness is a \"light", "context": "", "use_case": "sandboxing", "switched_from": "", "story": "Linux containers in 500 lines of code (2016)"}, {"id": 791329376, "item_id": 49458086, "url": "https://news.ycombinator.com/item?id=49458086", "by": "nobody42", "date": "2026-08-27", "stance": "recommend", "quote": "It's evident that Mandatory Access Control has become, ahem, mandatory.", "excerpt": "> it found a CUPS server (with a known CVE that had not made it to oldstable packages), but was not able to complete exploitation due to AppArmor. It's evident that Mandatory Access Control has become, ahem, mandatory. Both VM and inference engine processes should be confined, at least. There's a project where it's already done for many applications. [0] Additionally, `lockdown=confidentiality` in kernel boot flags g", "context": "", "use_case": "confining VM and inference processes", "switched_from": "", "story": "VMs won't contain cyber-capable agents"}, {"id": 789940529, "item_id": 49371283, "url": "https://news.ycombinator.com/item?id=49371283", "by": "insanitybit", "date": "2026-08-19", "stance": "recommend", "quote": "apparmor/selinux pair incredibly well", "excerpt": "> Moving code into gvisor virtually eliminates privilege escalation. Rereading this, it's an overstatement. It doesn't \"virtually eliminate\" it. It drives the cost up by like 3 orders of magnitude and it pairs well with other mitigations. gVisor escapes can and will happen, I highly recommend you do more than just stuff something into gvisor - additional seccomp can go a long way, and apparmor/selinux pair incredibly", "context": "", "use_case": "hardening", "switched_from": "", "story": "Pacing model development in an era of cyber-critical capabilities"}]}], "caveats": [], "who": [], "tags": [], "use_cases": ["sandboxing", "confining vm and inference processes", "hardening"], "compared": [{"slug": "bubblewrap", "name": "bubblewrap", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=49965118", "title": "Linux containers in 500 lines of code (2016)", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49450188", "title": "VMs won't contain cyber-capable agents", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49350031", "title": "Pacing model development in an era of cyber-critical capabilities", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {"recommend": 2}, "2026-09": {}, "2026-10": {"recommend": 1}}, "quotes": [{"id": 799567489, "item_id": 49972968, "url": "https://news.ycombinator.com/item?id=49972968", "by": "johnsmith1840", "date": "2026-10-06", "stance": "recommend", "quote": "App armor in linux is also nice gvisor like tool.", "excerpt": "For my assumed goal of yours I would say none of these are good options. A simple VM or ec2 node hosting a coding sandbox is likely the better option. All 3 of these are vastly different tech. Confusingly, you could run all 3 of these at the same time. I know that probally doesn't help. If you want to learn more I'd go get a linux machine somewhere like aws and play around with them. A local agent harness is a \"light", "context": "", "use_case": "sandboxing", "switched_from": "", "story": "Linux containers in 500 lines of code (2016)"}, {"id": 791329376, "item_id": 49458086, "url": "https://news.ycombinator.com/item?id=49458086", "by": "nobody42", "date": "2026-08-27", "stance": "recommend", "quote": "It's evident that Mandatory Access Control has become, ahem, mandatory.", "excerpt": "> it found a CUPS server (with a known CVE that had not made it to oldstable packages), but was not able to complete exploitation due to AppArmor. It's evident that Mandatory Access Control has become, ahem, mandatory. Both VM and inference engine processes should be confined, at least. There's a project where it's already done for many applications. [0] Additionally, `lockdown=confidentiality` in kernel boot flags g", "context": "", "use_case": "confining VM and inference processes", "switched_from": "", "story": "VMs won't contain cyber-capable agents"}, {"id": 789940529, "item_id": 49371283, "url": "https://news.ycombinator.com/item?id=49371283", "by": "insanitybit", "date": "2026-08-19", "stance": "recommend", "quote": "apparmor/selinux pair incredibly well", "excerpt": "> Moving code into gvisor virtually eliminates privilege escalation. Rereading this, it's an overstatement. It doesn't \"virtually eliminate\" it. It drives the cost up by like 3 orders of magnitude and it pairs well with other mitigations. gVisor escapes can and will happen, I highly recommend you do more than just stuff something into gvisor - additional seccomp can go a long way, and apparmor/selinux pair incredibly", "context": "", "use_case": "hardening", "switched_from": "", "story": "Pacing model development in an era of cyber-critical capabilities"}]}