Open Access Articles- Top Results for AppArmor


Original author(s) Immunix
Developer(s) Canonical Ltd.
Initial release 1998
Stable release 2.9.1 / 2014-12-15
Written in C, Perl, C++, sh
Operating system Linux
Type Security
License GNU General Public License

AppArmor ("Application Armor") is a Linux kernel security module released under the GNU General Public License. AppArmor allows the system administrator to associate with each program a security profile that restricts the capabilities of that program. It supplements the traditional Unix discretionary access control (DAC) model by providing mandatory access control (MAC). It was included as of the 2.6.36 version of the mainline Linux kernel. Since 2009, Canonical Ltd. contributes to the ongoing AppArmor development.

In addition to manually specifying profiles, AppArmor includes a learning mode, in which violations of the profile are logged, but not prevented. This log can then be turned into a 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.[1] 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.[2] They also claim that AppArmor requires fewer modifications to work with existing systems:[citation needed] 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.

Other systems

AppArmor represents one of several possible approaches to the problem of restricting the actions that installed software may take.

The SELinux system generally takes a similar approach to AppArmor. One important difference is that SELinux identifies file system objects by inode number instead of path. This means that, for example, while a file that is inaccessible may become accessible under AppArmor when a hard link is created to it, SELinux would still deny access through the newly created hard link, since the underlying data that is referenced by the inode would be the same.

While there has been considerable debate about which approach is better, there is as yet no strong evidence that either approach is preferable. Discussion about their relative merits often revolves around which approach is more aligned with existing Unix/Linux access control mechanisms, but Unix and Linux use a combination of path-based and inode-based access control. Note also that existing access control mechanisms remain in place with either system.[citation needed]

SELinux and AppArmor also differ significantly in how they are administered and how they integrate into the system.

Isolation of processes can also be accomplished by mechanisms like virtualization; the One Laptop per Child (OLPC) project, for example, sandboxes individual applications in lightweight Vserver.

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,[3][4] 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 SUSE and openSUSE, and was first enabled by default in SUSE Linux Enterprise Server 10 and in openSUSE 10.1.

From 2005 to September 2007, AppArmor was maintained by Novell.

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.[5]

AppArmor was integrated into the October 2010, 2.6.36 kernel release.[6][7][8][9]

AppArmor has been integrated to Synology's DSM 5.1 Beta in 2014.[10]

See also


  1. ^ Mayank Sharma (2006-12-11). " :: SELinux: Comprehensive security at the price of usability". 
  2. ^ 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. 
  3. ^ Vincent Danen (2001-12-17). "Immunix System 7: Linux security with a hard hat (not a Red Hat)". 
  4. ^ WireX Communications, Inc. (2000-11-15). " The Source for Secure Linux Components and Platforms". Archived from the original on 2001-02-03. 
  5. ^ "SecurityTeam/KnowledgeBase/AppArmorProfiles - Ubuntu Wiki". Retrieved 9 January 2011. 
  6. ^ James Corbet (2010-10-20). "The 2.6.36 kernel is out". 
  7. ^ Linus Torvalds (2010-10-20). "Change Log". 
  8. ^ "Linux 2 6 36". 2010-10-20. 
  9. ^ Sean Michael Kerner (2010-10-20). "Linux Kernel 2.6.36 Gets AppArmor". 
  10. ^ "Release Notes for DSM 5.1 Beta Program". 

External links