Speaker
Description
Linux users are familiar with users, groups, ownership, and file permissions. But an application normally runs with the permissions of the user - or service account - that started it, and unless it is otherwise confined, it can often access whatever those credentials allow. So how do we restrict what one particular application is allowed to do, even when its Unix credentials would permit more?
This talk builds AppArmor from that starting point. It begins with Discretionary Access Control (DAC) and the traditional Linux permission model, looking at how access decisions are primarily based on the credentials under which a process runs. From there, it introduces Mandatory Access Control (MAC) as an additional layer of policy that can restrict an application independently of ordinary ownership and permissions. It then takes a brief look at the Linux Security Module (LSM) framework that allows security modules to participate in kernel access-control decisions, before arriving at AppArmor, the security module Ubuntu uses by default for application confinement, and its path-based profiles.
From there, the talk moves from concepts to practice. It reads a simple AppArmor profile, shows how rules govern the files an application may access and the programs it may execute, explores the difference between complain and enforce modes, and looks at how AppArmor reports denied operations. A short live demo ties these pieces together: a profile is applied to an application, a policy violation is deliberately triggered, the resulting denial is inspected, and the profile is refined in response.
The goal is not to cover every AppArmor rule or feature, but to leave attendees with a clear mental model of where AppArmor fits into Linux security and enough practical understanding to begin reading, troubleshooting, and experimenting with profiles on their own.
Learning outcomes:
- Explain how DAC, MAC, and the LSM framework relate to AppArmor
- Read and make sense of a simple AppArmor profile
- Recognise an AppArmor denial and understand what it is telling you
- Know how to begin investigating and refining a profile
Prerequisites
Basic comfort with the Linux command line and standard file permissions (users, groups, chmod). No prior security or AppArmor experience needed.
Summary
An application running under a user's account can often access much of what that account can — but what if it should be allowed to do far less? This talk builds AppArmor from first principles, moving from familiar Linux access control through DAC, MAC, and the LSM framework to a practical look at profiles, complain and enforce modes, and policy denials.
Speaker Bio
Safeer CM is a technology generalist with 20+ years of experience in site reliability engineering, DevOps, infrastructure, and platform engineering. A site reliability engineer by trade, Safeer has managed large-scale production infrastructures at internet giants like Yahoo, LinkedIn, and Flipkart, and is currently a Principal Engineer at MoEngage. He has experience in cloud management and consulting for budding and established startups as a cloud architect, and is the author of Architecting Cloud-Native Serverless Solutions. He was a Continuous Delivery Foundation ambassador from 2022 to 2025 and contributes to the CD and DevOps communities. As a technology speaker, blogger, and meetup organizer - most recently at KubeCon India 2025 - Safeer enjoys mentoring new technology talent, especially in SRE and DevOps.
| Speaker LinkedIn / Socials | https://www.linkedin.com/in/safeer/ |
|---|---|
| Difficulty | Beginner |