800-53|AC-3(4)

Title

DISCRETIONARY ACCESS CONTROL

Description

The information system enforces [Assignment: organization-defined discretionary access control policy] over defined subjects and objects where the policy specifies that a subject that has been granted access to information can do one or more of the following:

Supplemental

When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. This control enhancement can operate in conjunction with AC-3(3). A subject that is constrained in its operation by policies governed by AC-3(3) is still able to operate under the less rigorous constraints of this control enhancement. Thus, while AC-3(3) imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, AC-3(4) permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside of the control of the information system, additional means may be required to ensure that the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control.

Reference Item Details

Category: ACCESS CONTROL

Parent Title: ACCESS ENFORCEMENT

Family: ACCESS CONTROL

Audit Items

View all Reference Audit Items

NamePluginAudit Name
1.1.1.2.1.6 Set 'System objects: Default owner for objects created by members of the Administrators group' to 'Object creator'WindowsCIS Windows 2003 MS v3.1.0
1.1.1.2.1.6 Set 'System objects: Default owner for objects created by members of the Administrators group' to 'Object creator'WindowsCIS Windows 2003 DC v3.1.0
1.1.1.2.1.28 Configure 'DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) syntax'WindowsCIS Windows 2003 DC v3.1.0
1.1.1.2.1.28 Configure 'DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) syntax'WindowsCIS Windows 2003 MS v3.1.0
1.6.1.3 Ensure SELinux policy is configuredUnixCIS Red Hat Enterprise Linux 7 STIG v2.0.0 STIG
1.6.1.5 Ensure the SELinux mode is enforcingUnixCIS Red Hat Enterprise Linux 7 STIG v2.0.0 STIG
1.6.1.9 Ensure non-privileged users are prevented from executing privileged functionsUnixCIS Red Hat Enterprise Linux 7 STIG v2.0.0 STIG
1.7.7 - Miscellaneous Enhancements - 'default umask = 27'UnixCIS AIX 5.3/6.1 L2 v1.1.0
1.8.10 Set default umask for users '/etc/csh.login'UnixCIS HP-UX 11i v1.5
1.8.10 Set default umask for users '/etc/d.login'UnixCIS HP-UX 11i v1.5
1.8.10 Set default umask for users '/etc/d.profile'UnixCIS HP-UX 11i v1.5
1.8.10 Set default umask for users '/etc/default/security'UnixCIS HP-UX 11i v1.5
1.8.10 Set default umask for users '/etc/profile'UnixCIS HP-UX 11i v1.5
2.0.3 Set umask value for DB2 admin user .profile fileUnixCIS IBM DB2 OS L1 v1.2.0
2.3 Set umask value for DB2 admin user .profile fileUnixCIS IBM DB2 9 Benchmark v3.0.1 Level 1 OS Linux
2.3 Set umask value for DB2 admin user .profile fileUnixCIS IBM DB2 v10 v1.1.0 Linux OS Level 2
2.3 Set umask value for DB2 admin user .profile fileUnixCIS IBM DB2 v10 v1.1.0 Linux OS Level 1
2.006 - ACLs for system files and directories do not conform to minimum requirements. - 'C:'WindowsDISA Windows Vista STIG v6r41
2.006 - ACLS FOR SYSTEM FILES AND DIRECTORIES DO NOT CONFORM TO MINIMUM REQUIREMENTS. - 'C:\Program Files'WindowsDISA Windows Vista STIG v6r41
2.006 - ACLS FOR SYSTEM FILES AND DIRECTORIES DO NOT CONFORM TO MINIMUM REQUIREMENTS. - 'C:\Windows'WindowsDISA Windows Vista STIG v6r41
2.008 - Local volumes are not formatted using NTFS.WindowsDISA Windows Server 2008 DC STIG v6r47
2.008 - Local volumes are not formatted using NTFS.WindowsDISA Windows Server 2008 MS STIG v6r46
2.008 - Local volumes must be formatted using NTFS.WindowsDISA Windows 7 STIG v1r32
2.008 - Local volumes will be formatted using NTFS.WindowsDISA Windows Server 2008 R2 MS STIG v1r33
2.008 - Local volumes will be formatted using NTFS.WindowsDISA Windows Server 2008 R2 DC STIG v1r34
2.020 - The system must prevent non-privileged users from executing privileged functions.UnixTenable Fedora Linux Best Practices v2.0.0
2.240 - The system must define default permissions for all users in such a way that the user can only read and modify their own files.UnixTenable Fedora Linux Best Practices v2.0.0
2.1040 - The umask must be set to 077 for all local interactive user accounts.UnixTenable Fedora Linux Best Practices v2.0.0
10.4 Set Default umask for Users - /etc/bash.bashrcUnixCIS Debian Linux 7 L1 v1.0.0
10.4 Set Default umask for Users - /etc/profile.d/*UnixCIS Debian Linux 7 L1 v1.0.0
10.4 Set Default umask for Users- '/etc/login.defs'UnixCIS Ubuntu 12.04 LTS Benchmark L1 v1.1.0
10.17 Setting Security Lifecycle Listener - check for umask present in startupUnixCIS Apache Tomcat 9 L1 v1.0.0 Middleware
10.17 Setting Security Lifecycle Listener - check for umask present in startupUnixCIS Apache Tomcat 9 L1 v1.0.0
10.17 Setting Security Lifecycle Listener - check for umask uncommented in startupUnixCIS Apache Tomcat 9 L1 v1.0.0 Middleware
10.17 Setting Security Lifecycle Listener - check for umask uncommented in startupUnixCIS Apache Tomcat 9 L1 v1.0.0
10.19 Setting Security Lifecycle Listener (check for umask present in startup)UnixCIS Apache Tomcat 7 L1 v1.1.0 Middleware
10.19 Setting Security Lifecycle Listener (check for umask present in startup)UnixCIS Apache Tomcat 7 L1 v1.1.0
10.19 Setting Security Lifecycle Listener (check for umask uncommented in startup)UnixCIS Apache Tomcat 7 L1 v1.1.0
10.19 Setting Security Lifecycle Listener (check for umask uncommented in startup)UnixCIS Apache Tomcat 7 L1 v1.1.0 Middleware
20.2 (L1) Ensure 'Event Logs are protected'WindowsCIS Microsoft Windows 10 EMS Gateway v3.0.0 L1
20.46 Ensure 'Permissions for program file directories must conform to minimum requirements'WindowsCIS Microsoft Windows Server 2022 STIG v1.0.0 STIG MS
20.46 Ensure 'Permissions for program file directories must conform to minimum requirements'WindowsCIS Microsoft Windows Server 2016 STIG v2.0.0 STIG MS
20.46 Ensure 'Permissions for program file directories must conform to minimum requirements'WindowsCIS Microsoft Windows Server 2022 STIG v1.0.0 STIG DC
20.46 Ensure 'Permissions for program file directories must conform to minimum requirements'WindowsCIS Microsoft Windows Server 2016 STIG v2.0.0 STIG DC
20.47 Ensure 'Permissions for program file directories must conform to minimum requirements'WindowsCIS Microsoft Windows Server 2019 STIG v2.0.0 STIG MS
20.47 Ensure 'Permissions for program file directories must conform to minimum requirements'WindowsCIS Microsoft Windows Server 2019 STIG v2.0.0 STIG DC
20.51 Ensure 'Permissions for the Windows installation directory conform to minimum requirements'WindowsCIS Microsoft Windows Server 2016 STIG v2.0.0 STIG DC
20.51 Ensure 'Permissions for the Windows installation directory conform to minimum requirements'WindowsCIS Microsoft Windows Server 2022 STIG v1.0.0 STIG DC
20.51 Ensure 'Permissions for the Windows installation directory conform to minimum requirements'WindowsCIS Microsoft Windows Server 2016 STIG v2.0.0 STIG MS
20.51 Ensure 'Permissions for the Windows installation directory conform to minimum requirements'WindowsCIS Microsoft Windows Server 2022 STIG v1.0.0 STIG MS