Access control list
An access control list (ACL), with respect to a computer file system, is a list of permissions attached to an object. An ACL specifies which users or system processes are granted access to objects, as well as what operations are allowed on given objects.[1] Each entry in a typical ACL specifies a subject and an operation. For instance, if a file object has an ACL that contains (Alice: read,write; Bob: read), this would give Alice permission to read and write the file and Bob to only read it.
Implementations
Many kinds of systems implement ACLs, or have a historical implementation.
Filesystem ACLs
A filesystem ACL is a data structure (usually a table) containing entries that specify individual user or group rights to specific system objects such as programs, processes, or files. These entries are known as access-control entries (ACEs) in the Microsoft Windows NT,[2] OpenVMS, Unix-like, and Mac OS X operating systems. Each accessible object contains an identifier to its ACL. The privileges or permissions determine specific access rights, such as whether a user can read from, write to, or execute an object. In some implementations, an ACE can control whether or not a user, or group of users, may alter the ACL on an object.
Most of the Unix and Unix-like operating systems (e.g. Linux,[3] BSD, or Solaris) support POSIX.1e ACLs, based on an early POSIX draft that was withdrawn in 1997. Many of them, for example AIX, FreeBSD,[4] Mac OS X beginning with version 10.4 ("Tiger"), or Solaris with ZFS filesystem,[5] support NFSv4 ACLs, which are part of the NFSv4 standard. There are two experimental implementations of NFSv4 ACLs for Linux: NFSv4 ACLs support for Ext3 filesystem[6] and the more recent Richacls,[7] which brings NFSv4 ACLs support for Ext4 filesystem.
PRIMOS featured ACLs at least as early as 1984.[8]
In the 1990s the ACL and RBAC models were extensively tested[by whom?] and used to administer file permissions.
Networking ACLs
On some types of proprietary computer-hardware (in particular routers and switches), an access control list provides rules that are applied to port numbers or IP addresses that are available on a host or other layer 3, each with a list of hosts and/or networks permitted to use the service. Although it is additionally possible to configure access control lists based on network domain names, this is a questionable idea because individual TCP, UDP, and ICMP headers do not contain domain names. Consequently, the device enforcing the access control list must separately resolve names to numeric addresses. This presents an additional attack surface for an attacker who is seeking to compromise security of the system which the access control list is protecting. Both individual servers as well as routers can have network ACLs. Access control lists can generally be configured to control both inbound and outbound traffic, and in this context they are similar to firewalls. Like firewalls, ACLs could be subject to security regulations and standards such as PCI DSS.
SQL implementations
ACL algorithms have been ported to SQL and to relational database systems. Many "modern" (2000s and 2010s) SQL-based systems, like enterprise resource planning and content management systems, have used ACL models in their administration modules.
Comparing with RBAC
The main alternative to the ACL model is the role-based access control (RBAC) model. A "minimal RBAC model", RBACm, can be compared with an ACL mechanism, ACLg, where only groups are permitted as entries in the ACL. Barkley (1997)[9] showed that RBACm and ACLg are equivalent.
In modern SQL implementations, ACL also manage groups and inheritance in a hierarchy of groups. So "modern ACLs" can express all that RBAC express, and are notably powerful (compared to "old ACLs") in their ability to express access control policy in terms of the way in which administrators view organizations.
For data interchange, and for "high level comparisons", ACL data can be translated to XACML.[10]
See also
- Cacls
- Capability-based security
- C-list
- Confused deputy problem
- DACL
- Role-based access control (RBAC)
References
- ↑ RFC 4949
- ↑ "Managing Authorization and Access Control". Microsoft Technet. 2005-11-03. https://technet.microsoft.com/en-us/library/bb457115.aspx. Retrieved 2013-04-08.
- ↑ "Red Hat Enterprise Linux AS 3 Release Notes (x86 Edition)". Red Hat. 2003. https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/3/html/Release_Notes/as-x86/index.html. Retrieved 2013-04-08. "EA (Extended Attributes) and ACL (Access Control Lists) functionality is now available for ext3 file systems. In addition, ACL functionality is available for NFS."
- ↑ "NFSv4 ACLs". FreeBSD. 2011-09-12. https://wiki.freebsd.org/NFSv4_ACLs. Retrieved 2013-04-08.
- ↑ "Chapter 8 Using ACLs and Attributes to Protect ZFS Files". Oracle Corporation. 2009-10-01. http://docs.oracle.com/cd/E19082-01/817-2271/ftyxi/index.html. Retrieved 2013-04-08.
- ↑ Grünbacher, Andreas (May 2008). "Native NFSv4 ACLs on Linux". SUSE. http://users.suse.com/~agruen/nfs4acl/. Retrieved 2013-04-08.
- ↑ Grünbacher, Andreas (July–September 2010). "Richacls - Native NFSv4 ACLs on Linux". bestbits.at. http://www.bestbits.at/richacl/. Retrieved 2013-04-08.
- ↑ "P.S.I. Pacer Software, Inc. Gnet-II revision 3.0". Computerworld 18 (21): p. 54. 1984-05-21. ISSN 0010-4841. https://books.google.com/books?id=KAUpSdv4AO4C. "The new version of Gnet-II (revision 3.0) has added a line-security mechanism which is implemented under the Primos ACL subsystem."
- ↑ J. Barkley (1997) "Comparing simple role based access control models and access control lists", In "Proceedings of the second ACM workshop on Role-based access control", pages 127-132.
- ↑ G. Karjoth, A. Schade and E. Van Herreweghen (2008) "Implementing ACL-based Policies in XACML", In "2008 Annual Computer Security Applications Conference".
Further reading
- Rhodes, Tom. "File System Access Control Lists (ACLs)". FreeBSD Handbook. https://www.freebsd.org/doc/en/books/handbook/fs-acl.html. Retrieved 2013-04-08.
- "SELinux and grsecurity: A Case Study Comparing Linux Security Kernel Enhancements". University of Virginia. 2005-08-24. Archived from the original on 2012-02-24. https://web.archive.org/web/20120224213801/http://www.cs.virginia.edu/~jcg8f/GrsecuritySELinuxCaseStudy.pdf. Retrieved 2013-04-08.
- Hinrichs, Susan (2005). "Operating System Security". CyberSecurity Spring 2005. University of Illinois. http://www.cs.uiuc.edu/class/fa05/cs498sh/seclab/slides/OSNotes.ppt. Retrieved 2013-04-08.
- Mitchell, John. "Access Control and Operating System Security". Stanford University. https://crypto.stanford.edu/cs155old/cs155-spring03/lecture9.pdf. Retrieved 2013-04-08.
- Clarkson, Michael. "Access Control". Cornell University. https://www.cs.cornell.edu/courses/cs513/2007fa/NL.accessControl.html. Retrieved 2013-04-08.
- Klein, Helge (2009-03-12). "Permissions: A Primer, or: DACL, SACL, Owner, SID and ACE Explained". http://helgeklein.com/blog/2009/03/permissions-a-primer-or-dacl-sacl-owner-sid-and-ace-explained/. Retrieved 2013-04-08.
- "Access Control Lists". MSDN Library. 2012-10-26. http://msdn.microsoft.com/en-us/library/aa374872(VS.85).aspx. Retrieved 2013-04-08.
- "How Permissions Work". Microsoft Technet. 2003-03-28. https://technet.microsoft.com/en-us/library/cc783530(WS.10).aspx. Retrieved 2013-04-08.
 |
