access control list (ACL)
An access control list (ACL) is a table that tells a computer operating
system which access rights each
user has to a particular system object, such as a file directory or
individual file. Each
object has a security attribute that identifies its access control list. The list has an entry
for
each system user with access privileges. The most common privileges include the ability to read a
file (or all the files in a directory), to write to the file or files, and to execute the file (if
it is an executable file, or program). Microsoft Windows NT/2000, Novell's NetWare,
Digital's OpenVMS,
and UNIX-based
systems are among the operating systems that use access control lists. The list is implemented
differently by each operating system.
In Windows NT/2000, an access control list (ACL) is associated with each system object. Each ACL
has one or more access control entries (ACEs) consisting of the name of a user or group of users.
The user can also be a role name, such as "programmer," or "tester." For each of these users,
groups, or roles, the access privileges are stated in a string of bits called an access
mask. Generally, the system administrator or the object owner creates the access control list
for an object.
Contributor(s): Nanci Ellen
This was last updated in August 2000
Dig Deeper
-
Software consultant Nari Kannan describes how agile practices and work can be scaled appropriately for success in large organizations. Using lean thinking, reduction of waste, and appropriately organizing work and people, agile can be successfully adapted, regardless of the size of the organization.
-
Undiscovered software glitches in complex systems are common, and one of the primary drivers is the loss of mainframe knowledge of a retiring workforce. Software glitches are lurking in many large systems, particularly mainframe systems, and the COBOL programmers that understand the code best are retiring, according to Jeff Papows, author of the new book, "Glitch - The hidden impact of faulty software." Papows describes how faulty software caused a huge charge to debit card holder's account and why such mistakes are on the rise in this interview. Papows notes the three most pressing drivers for software glitches: loss of intellectual knowledge, market consolidation and the ubiquity of technology
-
Karen Johnson explains the situations in which SQL skills are important for a software tester as well as times when the expertise is not required.
-
People who read this also read...
-
Resources from around the Web