Mandatory access control

Short description: Type of access control

Not to be confused with Message authentication code or Medium access control.

In computer security, mandatory access control (MAC) refers to a type of access control by which a secured environment (e.g., an operating system or a database) constrains the ability of a subject or initiator to access or modify on an object or target.[1] In the case of operating systems, the subject is a process or thread, while objects are files, directories, TCP/UDP ports, shared memory segments, or IO devices. Subjects and objects each have a set of security attributes. Whenever a subject attempts to access an object, the operating system kernel examines these security attributes, examines the authorization rules (aka policy) in place, and decides whether to grant access. A database management system, in its access control mechanism, can also apply mandatory access control; in this case, the objects are tables, views, procedures, etc.

In mandatory access control, the security policy is centrally controlled by a policy administrator and is guaranteed (in principle) to be enforced for all users. Users cannot override the policy and, for example, grant access to files that would otherwise be restricted. By contrast, discretionary access control (DAC), which also governs the ability of subjects to access objects, allows users the ability to make policy decisions or assign security attributes.

Historically and traditionally, MAC has been closely associated with multilevel security (MLS) and specialized military systems. In this context, MAC implies a high degree of rigor to satisfy the constraints of MLS systems. More recently,[when?] however, MAC has deviated out of the MLS niche and has started to become more mainstream. The more recent MAC implementations, such as SELinux and AppArmor for Linux and Mandatory Integrity Control for Windows, allow administrators to focus on issues such as network attacks and malware without the rigor or constraints of MLS.

## Contents

* 1 History and background
* 2 In operating systems
* 2.1 Microsoft
* 2.2 Apple
* 2.3 Google
* 2.4 Linux family
* 2.5 Other OSes
* 3 See also
* 3.1 Access control
* 3.2 Other topics
* 4 Footnotes
* 5 References
* 6 External links

## History and background

Historically, MAC was strongly associated with multilevel security (MLS) as a means of protecting classified information of the United States. The Trusted Computer System Evaluation Criteria (TCSEC), the seminal work on the subject and often known as the Orange Book, provided the original definition of MAC as "a means of restricting access to objects based on the sensitivity (as represented by a label) of the information contained in the objects and the formal authorization (i.e., clearance) of subjects to access information of such sensitivity".[2] Early implementations of MAC such as Honeywell's SCOMP, USAF's SACDIN, NSA's Blacker, and Boeing's MLS LAN[3][4] focused on MLS to protect military-oriented security classification levels with robust enforcement.

The word "mandatory" in MAC has acquired a special meaning derived from its use with military systems. In this context, MAC implies an extremely high degree of robustness that assures that the control mechanisms can resist any type of subversion, thereby enabling them to enforce access controls that are mandated by the order of a government such as the Executive Order 12958. Enforcement is supposed to be more imperative than for commercial applications. This precludes enforcement by best-effort mechanisms. Only mechanisms that can provide absolute or near-absolute enforcement of the mandate are acceptable for MAC. This is a tall order and sometimes assumed unrealistic by those unfamiliar with high assurance strategies, and very difficult for those who are.

In some systems, users have the authority to decide whether to grant access to any other user. To allow that, all users have clearances for all data. This is not necessarily true of an MLS system. If individuals or processes exist that may be denied access to any of the data in the system environment, then the system must be trusted to enforce MAC. Since there can be various levels of data classification and user clearances, this implies a quantified scale for robustness. For example, more robustness is indicated for system environments containing classified "Top Secret" information and uncleared users than for one with "Secret" information and users cleared to at least "Confidential." To promote consistency and eliminate subjectivity in degrees of robustness, an extensive scientific analysis and risk assessment of the topic produced a landmark benchmark standardization quantifying security robustness capabilities of systems and mapping them to the degrees of trust warranted for various security environments. The result was documented in CSC-STD-004-85.[5] Two relatively independent components of robustness were defined: Assurance level and functionality. Both were specified with a degree of precision that warranted significant confidence in certifications based on these criteria.

The Common Criteria standard[6] is based on this science and it intended to preserve the assurance level as EAL levels and the functionality specifications as Protection Profiles. Of these two essential components of objective robustness benchmarks, only EAL levels were faithfully preserved. In one case, TCSEC level C2[7] (not a MAC-capable category) was fairly faithfully preserved in the Common Criteria, as the Controlled Access Protection Profile (CAPP).[8] MLS Protection Profiles (such as MLSOSPP similar to B2)[9] is more general than B2. They are pursuant to MLS, but lack the detailed implementation requirements of their Orange Book predecessors, focusing more on objectives. This gives certifiers more subjective flexibility in deciding whether the evaluated product’s technical features adequately achieve the objective, potentially eroding consistency of evaluated products and making it easier to attain certification for less trustworthy products. For these reasons, the importance of the technical details of the Protection Profile is critical to determining the suitability of a product.

Such an architecture prevents an authenticated user or process at a specific classification or trust-level from accessing information, processes, or devices in a different level. This provides a containment mechanism of users and processes, both known and unknown. An unknown program might comprise an untrusted application where the system should monitor or control accesses to devices and files.

A few MAC implementations, such as Unisys' Blacker project, were certified robust enough to separate Top Secret from Unclassified late in the last millennium. Their underlying technology became obsolete and they were not refreshed. Today there are no current implementations certified by TCSEC to that level of robust implementation. However, some less robust products exist.

## In operating systems

### Microsoft

Starting with Windows Vista and Server 2008, Microsoft has incorporated Mandatory Integrity Control (MIC) in the Windows operating system, which adds integrity levels (IL) to running processes. The goal is to restrict access of less trustworthy processes to sensitive info. MIC defines four integrity levels: Low, medium, high, and system.[10] By default, processes started at medium IL. Elevated processes receive high IL.[11] Child processes, by default, inherit their parent's integrity, although the parent process can launch them with a lower IL. For example, Internet Explorer 7 launches its subprocesses with low IL. Windows controls access to objects based on ILs. Named objects, including files, registry keys or other processes and threads, have an entry in their ACL indicating the minimum IL of the process that can use the object. MIC enforces that a process can write to or delete an object only when its IL is equal to or higher than the object’s IL. Furthermore, to prevent access to sensitive data in memory, processes can’t open processes with a higher IL for read access.[12]

### Apple

Apple Inc. has incorporated an implementation of the TrustedBSD framework in its iOS and macOS operating systems.[13] (The word "mac" in "macOS" is short for "Macintosh" and has nothing to do with the abbreviation of "mandatory access control.") The command-line function `sandbox_init` provides a limited high-level sandboxing interface.[14]

### Google

Version 5.0 and later of the Android operating system, developed by Google, use SELinux (as SEAndroid) to enforce a MAC security model on top of its original UID-based DAC approach.[15]

### Linux family

Linux and many other Unix distributions have MAC for CPU (multi-ring), disk, and memory. While OS software may not manage privileges well, Linux became famous during the 1990s as being more secure and far more stable than non-Unix alternatives. The three main Linux Security Modules implementing MAC are SELinux, AppArmor, and TOMOYO Linux.[16]

Security-Enhanced Linux (SELinux) was originally developed by the NSA and released to the Open Source community in 2000.[17] It is one of the first MAC implementations for Linux and is also one of the most popular.[18] It has been incorporated into Linux kernels since v2.4, and is enabled by default on Android 5.0+, Red Hat Enterprise Linux/Fedora Linux, and SUSE Linux Enterprise/openSUSE.[19] SELinux provides powerful fine-grained control which makes it suitable for high-security environments, but many users find that its power and granularity come with a high degree of complexity and a steep learning curve.[16]

TOMOYO Linux is a lightweight MAC implementation for Linux and Embedded Linux, developed by NTT Data Corporation. It has been merged in Linux Kernel mainline version 2.6.30 in June 2009.[20] Differently from the label-based approach used by SELinux, TOMOYO Linux performs a pathname-based Mandatory Access Control, separating security domains according to process invocation history, which describes the system behavior. Policy are described in terms of pathnames. A security domain is simply defined by a process call chain, and represented by a string. There are 4 modes: disabled, learning, permissive, enforcing. Administrators can assign different modes for different domains. TOMOYO Linux introduced the "learning" mode, in which the accesses occurred in the kernel are automatically analyzed and stored to generate MAC policy: this mode could then be the first step of policy writing, making it easy to customize later.

AppArmor is a MAC implementation which utilizes the Linux Security Modules (LSM) interface of Linux 2.6 and is incorporated into SUSE Linux and Ubuntu 7.10. LSM provides a kernel API that allows modules of kernel code to govern ACL (DAC ACL, access-control lists). AppArmor is not capable of restricting all programs and is optionally in the Linux kernel as of version 2.6.36.[21] SUSE moved to SELinux for new installations since 2025, Ubuntu is using AppArmor by default, along with Debian and Solus.[19][22][23]

Amon Ott's RSBAC (Rule Set Based Access Control) provides a framework for Linux kernels that allows several different security policy / decision modules. One of the models implemented is Mandatory Access Control model. A general goal of RSBAC design was to try to reach (obsolete) Orange Book (TCSEC) B1 level. The model of mandatory access control used in RSBAC is mostly the same as in Unix System V/MLS, Version 1.2.1 (developed in 1989 by the National Computer Security Center of the USA with classification B1/TCSEC). RSBAC requires a set of patches to the stock kernel, which are maintained quite well by the project owner.

Smack (Simplified Mandatory Access Control Kernel) is a Linux kernel security module that protects data and process interaction from malicious manipulation using a set of custom mandatory access control rules, with simplicity as its main design goal.[24] It has been officially merged since the Linux 2.6.25 release.[25]

`grsecurity` is a patch for the Linux kernel providing a MAC implementation (precisely, it is an RBAC implementation). `grsecurity` is not implemented via the LSM API.[26]

Astra Linux OS developed for Russian Army has its own mandatory access control.[27]

### Other OSes

FreeBSD supports Mandatory Access Control, implemented as part of the TrustedBSD project. It was introduced in FreeBSD 5.0. Since FreeBSD 7.2, MAC support is enabled by default. The framework is extensible; various MAC modules implement policies such as Biba and multilevel security.

Sun's Trusted Solaris uses a mandatory and system-enforced access control mechanism (MAC), where clearances and labels are used to enforce a security policy. However note that the capability to manage labels does not imply the kernel strength to operate in multilevel security mode . Access to the labels and control mechanisms are not{{Citation needed|date=November 2009} n protected domain maintained by a kernel. The applications a user runs are combined with the security label at which the user works in the session. Access to information, programs and devices are only weakly controlled[citation needed].

## See also

### Access control

* Attribute-based access control (ABAC)
* Context-based access control (CBAC)
* Discretionary access control (DAC)
* Lattice-based access control (LBAC)
* Organisation-based access control (OrBAC)
* Role-based access control (RBAC)
* Rule-set-based access control (RSBAC)

### Other topics

* Bell–LaPadula model
* Capability-based security
* Clark–Wilson model
* Graham–Denning model
* Multiple single-level
* Risk-based authentication
* Security modes
* Systrace
* Take-grant protection model
* Type enforcement

## Footnotes

1. ↑ Belim, S. V.; Belim, S. Yu. (December 2018). "Implementation of Mandatory Access Control in Distributed Systems" (in en). Automatic Control and Computer Sciences 52 (8): 1124–1126. doi:10.3103/S0146411618080357. ISSN 0146-4116. http://link.springer.com/10.3103/S0146411618080357.
2. ↑ "Trusted Computer Evaluation Criteria". National Institute of Standards and Technology. 15 August 1983. https://csrc.nist.gov/csrc/media/publications/conference-paper/1998/10/08/proceedings-of-the-21st-nissc-1998/documents/early-cs-papers/dod85.pdf.
3. ↑ ﻿Product Evaluation Bulletin: Boeing MLS LAN﻿ (Report). National Computer Security Center (NCSC). September 14, 1988. Report No. CSC-PB-003-88. https://commons.wikimedia.org/wiki/File:NCSC_Product_Evaluation_Bulletin_CSC-PB-003-88_Boeing_MLS_LAN.pdf. "Identifies the Secure Network Server (SNS) as a candidate for the A1-MI rating, enforcing MAC with 8 hierarchical levels and 256 categories." See also the Product Brochure (1988).
4. ↑ Stover, Philip C. (February 1987). "Designing Multilevel Secure Networks". Alexandria, VA: Boeing Aerospace Company. https://commons.wikimedia.org/wiki/File:Stover_1987_Designing_Multilevel_Secure_Networks_Abstract.jpg.
5. ↑ "Technical Rational Behind CSC-STD-003-85: Computer Security Requirements". 1985-06-25. Archived from the original on July 15, 2007. https://web.archive.org/web/20070715134110/http://csrc.nist.gov/secpubs/rainbow/std004.txt. Retrieved 2008-03-15.
6. ↑ "The Common Criteria Portal". http://www.commoncriteriaportal.org/. Retrieved 2008-03-15.
7. ↑ US Department of Defense (December 1985). "DoD 5200.28-STD: Trusted Computer System Evaluation Criteria". https://fas.org/irp/nsa/rainbow/std001.htm. Retrieved 2008-03-15.
8. ↑ "Controlled Access Protection Profile, Version 1.d". National Security Agency. 1999-10-08. http://www.niap-ccevs.org/cc-scheme/pp/pp.cfm/id/PP_OS_CA_V1.d/. Retrieved 2008-03-15.
9. ↑ "Protection Profile for Multi-Level Operating Systems in Environments Requiring Medium Robustness, Version 1.22". National Security Agency. 2001-05-23. https://www.commoncriteriaportal.org/files/ppfiles/PP_OS_ML_MR_V1.22.pdf. Retrieved 2018-10-06.
10. ↑ Microsoft. "Mandatory Integrity Control mechanism". https://learn.microsoft.com/en-us/windows/win32/secauthz/mandatory-integrity-control. Retrieved 2025-11-29.
11. ↑ Steve Riley. "Mandatory Integrity Control in Windows Vista". http://blogs.technet.com/steriley/archive/2006/07/21/442870.aspx. Retrieved 2007-10-08.
12. ↑ Mark Russinovich. "PsExec, User Account Control and Security Boundaries". http://blogs.technet.com/markrussinovich/archive/2007/02/12/638372.aspx. Retrieved 2007-10-08.
13. ↑ TrustedBSD Project. "TrustedBSD Mandatory Access Control (MAC) Framework". http://www.trustedbsd.org/mac.html. Retrieved 2008-03-15.
14. ↑ "sandbox_init(3) man page". 2007-07-07. https://developer.apple.com/DOCUMENTATION/Darwin/Reference/ManPages/man3/sandbox_init.3.html. Retrieved 2008-03-15.
15. ↑ "Security-Enhanced Linux in Android". Android Open Source Project. https://source.android.com/docs/security/features/selinux.
16. ↑ 16.0 16.1 "Linux Security Modules Overview: SELinux, AppArmor, and TOMOYO Comparison". 2024-09-24. https://linuxsecurity.com/news/security-projects/linux-security-modules-lsm-selinux-vs-apparmor-vs-tomoyo.
17. ↑ "National Security Agency Shares Security Enhancements to Linux". NSA Press Release. Fort George G. Meade, Maryland: National Security Agency Central Security Service. 2001-01-02. https://www.nsa.gov/news-features/press-room/press-releases/2001/se-linux.shtml.
18. ↑ "Introduction to SELinux". 2023-07-05. https://github.blog/developer-skills/programming-languages-and-frameworks/introduction-to-selinux/.
19. ↑ 19.0 19.1 Gompa, Neal (2025-02-13). "Re: Announcement: SELinux as default MAC system on new Tumbleweed installations - openSUSE Factory" (in en). https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message/3JUSAOAXUWDXG4BSU3CEKY4Z3QUMI2US/.
20. ↑ "TOMOYO Linux, an alternative Mandatory Access Control". Linux 2 6 30. Linux Kernel Newbies. http://kernelnewbies.org/Linux_2_6_30#head-eeb259e0ba81d96d59015b8f79456d9a5283c650.
21. ↑ "Linux 2.6.36 released 20 October 2010". Linux 2.6.36. Linux Kernel Newbies. http://kernelnewbies.org/Linux_2_6_36.
22. ↑ "Solus 3 Linux Distribution Released For Enthusiasts" (in en). https://www.phoronix.com/news/Solus-3-Released.
23. ↑ "NewInBuster". https://wiki.debian.org/NewInBuster.
24. ↑ "Official SMACK documentation from the Linux source tree". Archived from the original on 2013-05-01. https://web.archive.org/web/20130501010740/http://schaufler-ca.com/description_from_the_linux_source_tree.
25. ↑ Jonathan Corbet. "More stuff for 2.6.25". Archived from the original on 2012-11-02. https://web.archive.org/web/20121102083054/http://lwn.net/Articles/267849/.
26. ↑ "Why doesn't grsecurity use LSM?". http://grsecurity.net/lsm.php.
27. ↑ Script error: The function "in_lang" does not exist. Ключевые особенности Astra Linux Special Edition по реализации требований безопасности информации

## References

* P. A. Loscocco, S. D. Smalley, P. A. Muckelbauer, R. C. Taylor, S. J. Turner, and J. F. Farrell. The Inevitability of Failure: The Flawed Assumption of Security in Modern Computing Environments. In Proceedings of the 21st National Information Systems Security Conference, pages 303–314, Oct. 1998.
* P. A. Loscocco, S. D. Smalley, Meeting Critical Security Objectives with Security-Enhanced Linux Proceedings of the 2001 Ottawa Linux Symposium.
* ISO/IEC DIS 10181-3, Information Technology, OSI Security Model, Security FrameWorks, Part 3: Access Control, 1993
* Robert N. M. Watson. "A decade of OS access-control extensibility". Commun. ACM 56, 2 (February 2013), 52–63.

## External links

* Weblog post on the how virtualization can be used to implement Mandatory Access Control.
* Weblog post from a Microsoft employee detailing Mandatory Integrity Control and how it differs from MAC implementations.
* GWV Formal Security Policy Model A Separation Kernel Formal Security Policy, David Greve, Matthew Wilding, and W. Mark Vanfleet.

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Mandatory access control. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Mandatory_access_control&oldid=4529859"