| Name Description Labeling Load time
mac_biba 4 Biba integrity policy yes boot only
mac_bsdextended 4 File system firewall no any time
mac_ifoff 4 Interface silencing no any time
mac_lomac 4 Low-Watermark MAC policy yes boot only
mac_mls 4 Confidentiality policy yes boot only
mac_none 4 Sample no-op policy no any time
mac_partition 4 Process partition policy yes any time
mac_portacl 4 Port bind(2) access control no any time
mac_seeotheruids 4 See-other-UIDs policy no any time
mac_test 4 MAC testing policy no any time
Each system subject (processes, sockets, etc.) and each system object (file system objects, sockets, etc.) can carry with it a MAC label. MAC labels contain data in an arbitrary format taken into consideration in making access control decisions for a given operation. Most MAC labels on system subjects and objects can be modified directly or indirectly by the system administrator. The format for a given policys label may vary depending on the type of object or subject being labeled. More information on the format for MAC labels can be found in the maclabel(7) man page.
By default, file system enforcement of labeled MAC policies relies on a single file system label (see MAC Labels) in order to make access control decisions for all the files in a particular file system. With some policies, this configuration may not allow administrators to take full advantage of features. In order to enable support for labeling files on an individual basis for a particular file system, the "multilabel" flag must be enabled on the file system. To set the "multilabel" flag, drop to single-user mode and unmount the file system, then execute the following command:
tunefs -l enable filesystem
where filesystem is either the mount point (in fstab(5)) or the special file (in /dev) corresponding to the file system on which to enable multilabel support.
Policy enforcement is divided into the following areas of the system:
File System File system mounts, modifying directories, modifying files, etc. KLD Loading, unloading, and retrieving statistics on loaded kernel modules Network Network interfaces, bpf(4), packet delivery and transmission, interface configuration ( ioctl 2, ifconfig(8)) Pipes Creation of and operation on pipe(2) objects Processes Debugging (e.g. ktrace(2)), process visibility (ps(1)), process execution (execve(2)), signalling (kill(2)) Sockets Creation of and operation on socket(2) objects System Kernel environment (kenv(1)), system accounting (acct(2)), reboot(2), settimeofday(2), swapon(2), sysctl(3), nfsd 8 -related operations VM mmap 2 -ed files
From the command line, each type of system object has its own means for setting and modifying its MAC policy label.
File system object setfmac 8, setfsmac(8)
Network interface ifconfig(8)
TTY (by login class) login.conf(5)
User (by login class) login.conf(5)
MAC security enforcement itself is transparent to application programs, with the exception that some programs may need to be aware of additional errno(2) returns from various system calls.
The interface for retrieving, handling, and setting policy labels is documented in the mac(3) man page.
mac(3), mac_biba(4), mac_bsdextended(4), mac_ifoff(4), mac_lomac(4), mac_mls(4), mac_none(4), mac_partition(4), mac_portacl(4), mac_seeotheruids(4), mac_test(4), login.conf(5), maclabel(7), getfmac(8), getpmac(8), setfmac(8), setpmac(8), mac(9)
.Rs Mandatory Access Control
The mac implementation first appeared in
.Fx 5.0 and was developed by the TrustedBSD Project.
This software was contributed to the
.Fx Project by Network Associates Labs, the Security Research Division of Network Associates Inc. under DARPA/SPAWAR contract N66001-01-C-8035 ("CBOSS"), as part of the DARPA CHATS research program.
While the MAC Framework design is intended to support the containment of the root user, not all attack channels are currently protected by entry point checks. As such, MAC Framework policies should not be relied on, in isolation, to protect against a malicious privileged user.