|Developer(s)||Originally by Immunix (1998-2005), then by SUSE as part of Novell (2005-2009), and currently by Canonical Ltd (since 2009).|
2.13.2 / December 21, 2018
|Written in||C, Perl, C++, sh|
|Type||Security, Linux Security Modules (LSM)|
|License||GNU General Public License|
AppArmor ("Application Armor") is a Linux kernel security module that allows the system administrator to restrict programs' capabilities with per-program profiles. Profiles can allow capabilities like network access, raw socket access, and the permission to read, write, or execute files on matching paths. AppArmor supplements the traditional Unix discretionary access control (DAC) model by providing mandatory access control (MAC). It has been included in the mainline Linux kernel since version 2.6.36 and its development has been supported by Canonical since 2009.
In addition to manually creating profiles, AppArmor includes a learning mode, in which profile violations are logged, but not prevented. This log can then be used for generating an Apparmor profile, based on the program's typical behavior.
AppArmor is implemented using the Linux Security Modules (LSM) kernel interface.
AppArmor is offered in part as an alternative to SELinux, which critics consider difficult for administrators to set up and maintain. Unlike SELinux, which is based on applying labels to files, AppArmor works with file paths. Proponents of AppArmor claim that it is less complex and easier for the average user to learn than SELinux. They also claim that AppArmor requires fewer modifications to work with existing systems: for example, SELinux requires a filesystem that supports "security labels", and thus cannot provide access control for files mounted via NFS. AppArmor is filesystem-agnostic.
This section needs additional citations for verification. (June 2009) (Learn how and when to remove this template message)
AppArmor represents one of several possible approaches to the problem of restricting the actions that installed software may take.
The SELinux system generally takes an approach similar to AppArmor. One important difference, SELinux identifies file system objects by inode number instead of path. Under AppArmor an inaccessible file can become accessible if a hard link to it is created. SELinux's inode-based model would still deny access through newly created hard links because the hard link would be pointing to an inaccessible inode.
SELinux and AppArmor also differ significantly in how they are administered and how they integrate into the system.
In 2007, the Simplified Mandatory Access Control Kernel was introduced.
In 2009, a new solution called Tomoyo was included in Linux 2.6.30; like AppArmor, it also uses path-based access control.
AppArmor was first used in Immunix Linux 1998–2003. At the time, AppArmor was known as SubDomain, a reference to the ability for a security profile for a specific program to be segmented into different domains, which the program can switch between dynamically. AppArmor was first made available in SLES and openSUSE and was first enabled by default in SLES 10 and in openSUSE 10.1.
In May 2005 Novell acquired Immunix and rebranded SubDomain as AppArmor and began code cleaning and rewriting for the inclusion in the Linux kernel. From 2005 to September 2007, AppArmor was maintained by Novell. From Novell to now SUSE is the legal owner of the trademarked name AppArmor.
AppArmor was first successfully ported/packaged for Ubuntu in April 2007. AppArmor became a default package starting in Ubuntu 7.10, and came as a part of the release of Ubuntu 8.04, protecting only CUPS by default. As of Ubuntu 9.04 more items such as MySQL have installed profiles. AppArmor hardening continued to improve in Ubuntu 9.10 as it ships with profiles for its guest session, libvirt virtual machines, the Evince document viewer, and an optional Firefox profile.
AppArmor has been integrated to Synology's DSM 5.1 Beta in 2014.
- "Release Notes 2.13.2". AppArmor development team.
- Mayank Sharma (2006-12-11). "Linux.com :: SELinux: Comprehensive security at the price of usability". Archived from the original on 2009-02-02. Retrieved 2007-10-25.
- Ralf Spenneberg (August 2006). "Protective armor: Shutting out intruders with AppArmor". Linux Magazine. Archived from the original on 21 August 2008. Retrieved 2008-08-02.
- Vincent Danen (2001-12-17). "Immunix System 7: Linux security with a hard hat (not a Red Hat)". Archived from the original on May 23, 2012.
- WireX Communications, Inc. (2000-11-15). "Immunix.org: The Source for Secure Linux Components and Platforms". Archived from the original on 2001-02-03.
- "AppArmor History". AppArmor. Archived from the original on 2017-07-02.CS1 maint: BOT: original-url status unknown (link)
- "AppArmor". United States Patent and Trademark Office.
- "SecurityTeam/KnowledgeBase/AppArmorProfiles – Ubuntu Wiki". Retrieved 9 January 2011.
- James Corbet (2010-10-20). "The 2.6.36 kernel is out".
- Linus Torvalds (2010-10-20). "Change Log". Archived from the original on 2011-09-04.
- "Linux 2 6 36". 2010-10-20.
- Sean Michael Kerner (2010-10-20). "Linux Kernel 2.6.36 Gets AppArmor".
- "Release Notes for DSM 5.1 Beta Program".
- "Solus 3 Linux Distribution Released For Enthusiasts".
- "New in Buster".
- "AppArmor wiki". gitlab. Retrieved 2018-04-25.
- AppArmor Wiki (Archived)
- AppArmor description from openSUSE.org
- "AppArmor detailed documentation". ArchLinux. Retrieved 2018-04-25.
- LKML thread containing comments and criticism of AppArmor
- Apparmor packages for Ubuntu
- Counterpoint: (subscription required) Novell and Red Hat security experts face off on AppArmor and SELinux
- AppArmor Application Security for Linux