CIS Apple MacOS 12.0 Monterey Benchmark v1.0.0
CIS Apple MacOS 12.0 Monterey Benchmark v1.0.0
Terms of Use
Please see the below link for our current terms of use:
https://www.cisecurity.org/cis-securesuite/cis-securesuite-membership-terms-of-use/
1 | P a g e
Table of Contents
2 | P a g e
2.4 Sharing ...................................................................................................................................................... 71
2.4.1 Ensure Remote Apple Events Is Disabled (Automated) ......................................... 72
2.4.2 Ensure Internet Sharing Is Disabled (Automated) ................................................... 74
2.4.3 Ensure Screen Sharing Is Disabled (Automated) ...................................................... 78
2.4.4 Ensure Printer Sharing Is Disabled (Automated) ..................................................... 80
2.4.5 Ensure Remote Login Is Disabled (Automated) ........................................................ 82
2.4.6 Ensure DVD or CD Sharing Is Disabled (Automated) .............................................. 86
2.4.7 Ensure Bluetooth Sharing Is Disabled (Automated) ................................................ 89
2.4.8 Ensure File Sharing Is Disabled (Automated) ............................................................ 93
2.4.9 Ensure Remote Management Is Disabled (Automated) ......................................... 96
2.4.10 Ensure Content Caching Is Disabled (Automated) ................................................. 99
2.4.11 Ensure AirDrop Is Disabled (Automated) ............................................................... 102
2.4.12 Ensure Media Sharing Is Disabled (Automated) .................................................. 107
2.4.13 Ensure AirPlay Receiver Is Disabled (Automated) ............................................. 112
2.5 Security & Privacy ............................................................................................................................. 115
2.5.1 Encryption .................................................................................................................................... 116
2.5.1.1 Ensure FileVault Is Enabled (Automated) ............................................................. 117
2.5.1.2 Ensure all user storage APFS volumes are encrypted (Manual) .................. 119
2.5.1.3 Ensure all user storage CoreStorage volumes are encrypted (Manual) ... 123
2.5.2 Firewall .......................................................................................................................................... 127
2.5.2.1 Ensure Gatekeeper is Enabled (Automated) ........................................................ 128
2.5.2.2 Ensure Firewall Is Enabled (Automated) .............................................................. 132
2.5.2.3 Ensure Firewall Stealth Mode Is Enabled (Automated) .................................. 138
2.5.3 Ensure Location Services Is Enabled (Automated) ............................................... 142
2.5.4 Audit Location Services Access (Manual) .................................................................. 145
2.5.5 Ensure Sending Diagnostic and Usage Data to Apple Is Disabled (Automated)
................................................................................................................................................................. 148
2.5.6 Ensure Limit Ad Tracking Is Enabled (Automated) .............................................. 152
2.5.7 Audit Camera Privacy and Confidentiality (Manual) ............................................ 157
2.6 Apple ID ................................................................................................................................................. 160
2.6.1 iCloud ............................................................................................................................................. 161
3 | P a g e
2.6.1.1 Audit iCloud Configuration (Manual) ...................................................................... 162
2.6.1.2 Audit iCloud Keychain (Manual) ................................................................................ 167
2.6.1.3 Audit iCloud Drive (Manual) ....................................................................................... 171
2.6.1.4 Ensure iCloud Drive Document and Desktop Sync is Disabled (Automated)
................................................................................................................................................................. 174
2.6.2 Audit App Store Password Settings (Manual) ......................................................... 178
2.7 Time Machine ...................................................................................................................................... 180
2.7.1 Ensure Backup Up Automatically is Enabled (Automated) ............................... 182
2.7.2 Ensure Time Machine Volumes Are Encrypted (Automated) .......................... 187
2.8 Ensure Wake for Network Access Is Disabled (Automated) ................................. 190
2.9 Ensure Power Nap Is Disabled (Automated) ............................................................... 193
2.10 Ensure Secure Keyboard Entry terminal.app is Enabled (Automated) ......... 196
2.11 Ensure EFI Version Is Valid and Checked Regularly (Automated) .................. 200
2.12 Audit Automatic Actions for Optical Media (Manual) ........................................... 202
2.13 Audit Siri Settings (Manual) ............................................................................................. 206
2.14 Audit Sidecar Settings (Manual) ..................................................................................... 212
2.15 Audit Touch ID and Wallet & Apple Pay Settings (Manual) ................................ 216
2.16 Audit Notification System Preference Settings (Manual) .................................... 218
2.17 Audit Passwords System Preference Setting (Manual) ........................................ 220
3 Logging and Auditing ................................................................................................................................ 222
3.1 Ensure Security Auditing Is Enabled (Automated) ................................................... 223
3.2 Ensure Security Auditing Flags Are Configured Per Local Organizational
Requirements (Automated) ........................................................................................................ 225
3.3 Ensure install.log Is Retained for 365 or More Days and No Maximum Size
(Automated) ...................................................................................................................................... 228
3.4 Ensure Security Auditing Retention Is Enabled (Automated) ............................. 231
3.5 Ensure Access to Audit Records Is Controlled (Automated) ................................ 233
3.6 Ensure Firewall Logging Is Enabled and Configured (Automated) ................... 236
3.7 Audit Software Inventory (Manual) ................................................................................ 240
4 Network Configurations .......................................................................................................................... 243
4.1 Ensure Bonjour Advertising Services Is Disabled (Automated) ......................... 244
4 | P a g e
4.2 Ensure Show Wi-Fi status in Menu Bar Is Enabled (Automated) ....................... 247
4.3 Audit Network Specific Locations (Manual) ................................................................ 251
4.4 Ensure HTTP Server Is Disabled (Automated) ........................................................... 254
4.5 Ensure NFS Server Is Disabled (Automated) ............................................................... 256
4.6 Audit Wi-Fi Settings (Manual) ............................................................................................ 258
5 System Access, Authentication and Authorization ...................................................................... 261
5.1 File System Permissions and Access Controls ...................................................................... 262
5.1.1 Ensure Home Folders Are Secure (Automated) ..................................................... 263
5.1.2 Ensure System Integrity Protection Status (SIPS) Is Enabled (Automated)
................................................................................................................................................................. 266
5.1.3 Ensure Apple Mobile File Integrity Is Enabled (Automated) ............................ 268
5.1.4 Ensure Library Validation Is Enabled (Automated) ............................................. 270
5.1.5 Ensure Sealed System Volume (SSV) Is Enabled (Automated) ........................ 274
5.1.6 Ensure Appropriate Permissions Are Enabled for System Wide Applications
(Automated) ...................................................................................................................................... 277
5.1.7 Ensure No World Writable Files Exist in the System Folder (Automated) . 279
5.1.8 Ensure No World Writable Files Exist in the Library Folder (Automated) 281
5.2 Password Management ................................................................................................................... 283
5.2.1 Ensure Password Account Lockout Threshold Is Configured (Automated)
................................................................................................................................................................. 284
5.2.2 Ensure Password Minimum Length Is Configured (Automated) .................... 287
5.2.3 Ensure Complex Password Must Contain Alphabetic Characters Is
Configured (Manual) ...................................................................................................................... 290
5.2.4 Ensure Complex Password Must Contain Numeric Character Is Configured
(Manual) .............................................................................................................................................. 293
5.2.5 Ensure Complex Password Must Contain Special Character Is Configured
(Manual) .............................................................................................................................................. 296
5.2.6 Ensure Complex Password Must Contain Uppercase and Lowercase
Characters Is Configured (Manual) ......................................................................................... 299
5.2.7 Ensure Password Age Is Configured (Automated) ................................................ 301
5.2.8 Ensure Password History Is Configured (Automated) ........................................ 304
5.3 Ensure the Sudo Timeout Period Is Set to Zero (Automated) .............................. 307
5 | P a g e
5.4 Ensure a Separate Timestamp Is Enabled for Each User/tty Combo
(Automated) ...................................................................................................................................... 310
5.5 Ensure login keychain is locked when the computer sleeps (Manual) ............ 312
5.6 Ensure the "root" Account Is Disabled (Automated) ............................................... 315
5.7 Ensure Automatic Login Is Disabled (Automated) .................................................... 317
5.8 Ensure a Password is Required to Wake the Computer From Sleep or Screen
Saver Is Enabled (Automated) ................................................................................................... 320
5.9 Ensure system is set to hibernate (Automated) ......................................................... 324
5.10 Require an administrator password to access system-wide preferences
(Automated) ...................................................................................................................................... 329
5.11 Ensure an administrator account cannot login to another user's active and
locked session (Automated) ....................................................................................................... 332
5.12 Ensure a Custom Message for the Login Screen Is Enabled (Automated) ... 334
5.13 Ensure a Login Window Banner Exists (Automated) ............................................ 337
5.14 Ensure Users' Accounts Do Not Have a Password Hint (Automated) ............ 340
5.15 Ensure Fast User Switching Is Disabled (Manual) .................................................. 342
6 User Accounts and Environment ......................................................................................................... 345
6.1 Accounts Preferences Action Items ........................................................................................... 346
6.1.1 Ensure Login Window Displays as Name and Password Is Enabled
(Automated) ...................................................................................................................................... 347
6.1.2 Ensure Show Password Hints Is Disabled (Automated) ..................................... 350
6.1.3 Ensure Guest Account Is Disabled (Automated) .................................................... 353
6.1.4 Ensure Guest Access to Shared Folders Is Disabled (Automated) .................. 357
6.1.5 Ensure the Guest Home Folder Does Not Exist (Automated) ........................... 361
6.2 Ensure Show All Filename Extensions Setting is Enabled (Automated) ......... 363
6.3 Ensure Automatic Opening of Safe Files in Safari Is Disabled (Automated) .. 366
7 Appendix: Additional Considerations ............................................................................................... 370
7.1 Extensible Firmware Interface (EFI) password (Manual) ..................................... 371
7.2 FileVault and Local Account Password Reset using AppleID (Manual) ........... 373
Appendix: Recommendation Summary Table ........................................................................................ 375
Appendix: CIS Controls v7 IG 1 Mapped Recommendations ........................................................... 380
Appendix: CIS Controls v7 IG 2 Mapped Recommendations ........................................................... 383
6 | P a g e
Appendix: CIS Controls v7 IG 3 Mapped Recommendations ........................................................... 387
Appendix: CIS Controls v8 IG 1 Mapped Recommendations ........................................................... 391
Appendix: CIS Controls v8 IG 2 Mapped Recommendations ........................................................... 394
Appendix: CIS Controls v8 IG 3 Mapped Recommendations ........................................................... 398
Appendix: Change History .............................................................................................................................. 402
7 | P a g e
Overview
This document, CIS Apple macOS 12.0 Monterey Benchmark, provides prescriptive
guidance for establishing a secure configuration posture for Apple macOS 12.0 Monterey
This guide was tested against Apple macOS 12.0 Monterey. To obtain the latest version of
this guide, please visit http://benchmarks.cisecurity.org. If you have questions, comments,
or have identified ways to improve this guide, please write us at [email protected].
This Benchmark includes instructions for auditing and remediation that includes three
different methods (Graphical User Interface (GUI), Command Line Interface using Terminal
(CLI), Configuration Profiles) to evaluate the current configuration status and make
changes as desired. In most cases all methods are supported by the Operating System and it
is up to organizational implementation personnel on how best to implement. There are
some recommendations that can only be managed through one of the methods. Each
organization must decide if control management outside their standard process is required
if no solution is possible through their organization's specific choice of implementation. It
is best practice, for Enterprise managed devices at this time, to use profiles for
management, a mix of both profile device management, and command line hardening
scripts will be the most comprehensive solution.
More profile information
https://developer.apple.com/documentation/devicemanagement
https://developer.apple.com/documentation/devicemanagement/configuring_multiple_de
vices_using_profiles
Intended Audience
This document is intended for system and application administrators, security specialists,
auditors, help desk, and platform deployment personnel who plan to develop, deploy,
assess, or secure solutions that incorporate Apple macOS 12.0.
8 | P a g e
Consensus Guidance
This benchmark was created using a consensus review process comprised of subject
matter experts. Consensus participants provide perspective from a diverse set of
backgrounds including consulting, software development, audit and compliance, security
research, operations, government, and legal.
Each CIS benchmark undergoes two phases of consensus review. The first phase occurs
during initial benchmark development. During this phase, subject matter experts convene
to discuss, create, and test working drafts of the benchmark. This discussion occurs until
consensus has been reached on benchmark recommendations. The second phase begins
after the benchmark has been published. During this phase, all feedback provided by the
Internet community is reviewed by the consensus team for incorporation in the
benchmark. If you are interested in participating in the consensus process, please visit
https://workbench.cisecurity.org/.
9 | P a g e
Typographical Conventions
The following typographical conventions are used throughout this guide:
Convention Meaning
Stylized Monospace font Used for blocks of code, command, and script examples.
Text should be interpreted exactly as presented.
Monospace font Used for inline code, commands, or examples. Text should
be interpreted exactly as presented.
<italic font in brackets> Italic texts set in angle brackets denote a variable
requiring substitution for a real value.
Assessment Status
An assessment status is included for every recommendation. The assessment status
indicates whether the given recommendation can be automated or requires manual steps
to implement. Both statuses are equally important and are determined and supported as
defined below:
Automated
Manual
10 | P a g e
Profile Definitions
The following configuration profiles are defined by this Benchmark:
• Level 1
• Level 2
This profile extends the "Level 1" profile. Items in this profile exhibit one or more of
the following characteristics:
11 | P a g e
Acknowledgements
This benchmark exemplifies the great things a community of users, vendors, and subject matter
experts can accomplish through consensus collaboration. The CIS community thanks the entire
consensus team with special recognition to the following individuals who contributed greatly to
the creation of this guide:
Author
Ron Colvin
Contributor
William Harrison
Mark Andersen CISSP, GMOB
Ben Montour
Sara Archacki
Hao Shu
Jeffrey Compton
Jorge Escobar
Tim Harrison CISSP, ICP, KMP, Center for Internet Security
Laura Gardner
Michael Scarborough
Mauro Faccenda
Jason Olsen BSCS, ACSP 10.9, ACMT 2015, Comerica Bank
Mischa van der Bent
Bob Gendler
Dan Brodjieski
Allen Golbig
Jason Blake
Isaac Ordonez
Editor
Eric Pinnell
Edward Byrd
12 | P a g e
Recommendations
1 Install Updates, Patches and Additional Security Software
Install Updates, Patches and Additional Security Software
• Level 1
Description:
Software vendors release security patches and software updates for their products when
security vulnerabilities are discovered. There is no simple way to complete this action
without a network connection to an Apple software repository. Please ensure appropriate
access for this control. This check is only for what Apple provides through software update.
Software updates should be run at minimum every 30 days. Run the following command to
verify when software update was previously run: $ sudo defaults read
/Library/Preferences/com.apple.SoftwareUpdate | grep -e
LastFullSuccessfulDate. The response should be in the last 30 days (Example):
LastFullSuccessfulDate = "2020-07-30 12:45:25 +0000";
Rationale:
Impact:
13 | P a g e
Audit:
Terminal Method:
Run the following command to verify there are no software updates:
$ sudo /usr/sbin/softwareupdate -l
Computers that have installed pre-release software in the past will fail this check if there
are pre-release software updates available when audited. In the App Store setting System
Preferences the computer may be set to no longer receive pre-release software.
14 | P a g e
Remediation:
Terminal Method:
Run the following command to verify what packages need to be installed:
$ sudo /usr/sbin/softwareupdate -l
$ sudo /usr/sbin/softwareupdate -i -a -R
example:
$ sudo /usr/sbin/softwareupdate -l
Software Update Tool
Downloaded iTunes
Installing iTunes
Done with iTunes
Done.
15 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
16 | P a g e
1.2 Ensure Auto Update Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
Auto Update verifies that your system has the newest security patches and software
updates. If "Automatically check for updates" is not selected background updates for new
malware definition files from Apple for XProtect and Gatekeeper will not occur.
http://macops.ca/os-x-admins-your-clients-are-not-getting-background-security-updates/
https://derflounder.wordpress.com/2014/12/17/forcing-xprotect-blacklist-updates-on-
mavericks-and-yosemite/
Rationale:
It is important that a system has the newest updates applied so as to prevent unauthorized
persons from exploiting identified vulnerabilities.
Impact:
Without automatic update, updates may not be made in a timely manner and the system
will be exposed to additional risk.
17 | P a g e
Audit:
Perform the following to ensure the system is automatically checking for updates:
Graphical Method:
Terminal Method:
Run the following command to verify that software updates are automatically checked:
Note: If automatic updates were selected during system set-up this setting may not have
left an auditable artifact. Please turn off the check and re-enable when the GUI does not
reflect the audited results.
or
Run the following command to verify that a profile is installed that enables software
updates to be automatically checked:
AutomaticCheckEnabled = 1;
18 | P a g e
Remediation:
Perform the following to enable the system to automatically check for updates:
Graphical Method:
Terminal Method:
Run the following command to enable auto update:
Profile Method:
19 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
20 | P a g e
1.3 Ensure Download New Updates When Available is Enabled
(Automated)
Profile Applicability:
• Level 1
Description:
In the GUI both "Install macOS updates" and "Install app updates from the App Store" are
dependent on whether "Download new updates when available" is selected.
Rationale:
It is important that a system has the newest updates downloaded so that they can be
applied.
Impact:
If "Download new updates when available" is not selected, updates may not made in a
timely manner and the system will be exposed to additional risk.
21 | P a g e
Audit:
Perform the following to ensure the system is automatically checking for updates:
Graphical Method:
Terminal Method:
Run the following command to verify that software updates are automatically checked:
Note: If automatic updates were selected during system set-up this setting may not have
left an auditable artifact. Please turn off the check and re-enable when the GUI does not
reflect the audited results.
or
Run the following command to verify that a profile is installed that enables software
updates to be downloaded when available:
AutomaticDownload = 1;
22 | P a g e
Remediation:
Perform the following to enable the system to automatically check for updates:
Graphical Method:
Terminal Method:
Run the following command to enable auto update:
Profile Method:
23 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
24 | P a g e
1.4 Ensure Installation of App Update Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
Ensure that application updates are installed after they are available from Apple. These
updates do not require reboots or admin privileges for end users.
Rationale:
Patches need to be applied in a timely manner to reduce the risk of vulnerabilities being
exploited.
Impact:
25 | P a g e
Audit:
Perform the following to ensure that App Store updates install automatically:
Graphical Method:
or
Terminal Method:
Run the following command to verify that App Store updates are auto updating:
or
Run the following command to verify that a profile is installed that enables App Store
updates to be automatically installed:
AutomaticallyInstallAppUpdates = 1;
26 | P a g e
Remediation:
Terminal Method:
Run the following command to turn on App Store auto updating:
Note: This remediation requires a log out and log in to show in the GUI.
Profile Method:
27 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
28 | P a g e
1.5 Ensure System Data Files and Security Updates Are Downloaded
Automatically Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
Ensure that system and security updates are installed after they are available from Apple.
This setting enables definition updates for XProtect and Gatekeeper. With this setting in
place new malware and adware that Apple has added to the list of malware or untrusted
software will not execute. These updates do not require reboots or end user admin rights.
http://www.thesafemac.com/tag/xprotect/
https://support.apple.com/en-us/HT202491
Rationale:
Patches need to be applied in a timely manner to reduce the risk of vulnerabilities being
exploited.
Impact:
29 | P a g e
Audit:
Perform the following to ensure that system data files and security updates install
automatically:
Graphical Method:
Terminal Method:
Run the following commands to verify that system data files and security updates are
automatically checked:
Note: If automatic updates were selected during system set-up this setting may not have
left an auditable artifact. Please turn off the check and re-enable when the GUI does not
reflect the audited results.
or
Run the following commands to verify that a profile is installed that enables system data
files and security updates to automatically download:
ConfigDataInstall = 1;
CriticalUpdateInstall = 1;
30 | P a g e
Remediation:
Perform the following to enable system data files and security updates to install
automatically:
Graphical Method:
Terminal Method:
Run the following commands to enable automatically checking of system data files and
security updates:
Profile Method:
31 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
32 | P a g e
1.6 Ensure Install of macOS Updates Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
Ensure that macOS updates are installed after they are available from Apple. This setting
enables macOS updates to be automatically installed. Some environments will want to
approve and test updates before they are delivered. It is best practice to test first where
updates can and have caused disruptions to operations. Automatic updates should be
turned off where changes are tightly controlled and there are mature testing and approval
processes. Automatic updates should not be turned off so the admin can call the users first
to let them know it's ok to install. A dependable, repeatable process involving a patch agent
or remote management tool should be in place before auto-updates are turned off.
Rationale:
Patches need to be applied in a timely manner to reduce the risk of vulnerabilities being
exploited.
Impact:
33 | P a g e
Audit:
Perform the following to ensure that macOS updates are set to auto update:
Graphical Method:
or
Terminal Method:
Run the following command to verify that macOS updates are automatically checked and
installed:
Note: If automatic updates were selected during system set-up this setting may not have
left an auditable artifact. Please turn off the check and re-enable when the GUI does not
reflect the audited results.
or
Run the following command to verify that a profile is installed that enables the installation
of macOS updates:
AutomaticallyInstallMacOSUpdates = 1;
34 | P a g e
Remediation:
Terminal Method:
Run the following command to to enable automatic checking and installing of macOS
updates:
Profile Method:
35 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
36 | P a g e
1.7 Audit Computer Name (Manual)
Profile Applicability:
• Level 2
Description:
If the computer is used in an organization that assigns host names, it is a good idea to
change the computer name to the host name. This is more of a best practice than a security
measure. If the host name and the computer name are the same, computer support may be
able to track problems down more easily.
Standard naming patterns avoid collisions and mitigate risk for computer users.
With mobile devices using DHCP IP tracking has serious drawbacks; hostname or computer
name tracking makes much more sense for those organizations that can implement it. If the
computer is using different names for the "Computer Name" DNS and Directory
environments it can be difficult to manage Macs in an Enterprise asset inventory.
Rationale:
Part of IT security is having visibility into all of the devices that the organization is
responsible for. Without a complete inventory it is impossible to ensure all security
controls are met on all organizational devices.
Default macOS naming deconfliction controls can create issues for appropriate
management and tracking as well as privacy exposure. By default the name of a macOS
computer is derived from the first user created. If the user has multiple computers or an
image is used without an appropriate name change there will be multiple computers with
names derived from the same user for discovery deconfliction. How many "Ron Colvin's
MacBook Pro" should there be, are any missing?
Local network auto renaming to avoid collisions also allows for the enumeration of local
computer names. Computers should not be named after their users, especially on untrusted
networks. For social engineering purposes the computer name should not provide a full
name of the user or an identifiable name that might be used to assist in targeted user
attacks.
A documented plan to better enable a complete device inventory without exposing user or
organizational information is part of mature security.
37 | P a g e
Audit:
Remediation:
References:
1. https://support.apple.com/en-ca/guide/mac-help/mchlp1177/11.0/mac/11.0
2. https://uberagent.com/blog/choosing-macos-computer-names-wisely/
3. https://support.apple.com/en-ca/guide/mac-help/mchlp2322/11.0/mac/11.0
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
38 | P a g e
2 System Preferences
This section contains recommendations related to configurable options in the System
Preferences panel.
39 | P a g e
2.1 Bluetooth
Bluetooth is a short-range, low-power wireless technology commonly integrated into
portable computing and communication devices and peripherals. Bluetooth is best used in
a secure environment where unauthorized users have no physical access near the Mac. If
Bluetooth is used, it should be secured properly (see below).
40 | P a g e
2.1.1 Ensure Bluetooth Is Disabled If No Devices Are Paired (Automated)
Profile Applicability:
• Level 1
Description:
Bluetooth devices use a wireless communications system that replaces the cables used by
other peripherals to connect to a system. It is by design a peer-to-peer network technology
and typically lacks centralized administration and security enforcement infrastructure.
Rationale:
Impact:
There have been many Bluetooth exploits. While Bluetooth can be hardened, it does create
a local wireless network that can be attacked to compromise both devices and information.
Apple has emphasized the ease of use in Bluetooth devices so it is generally expected that
Bluetooth will be used. Turning off Bluetooth with this control will also disable the
Bluetooth sharing capability that is more strongly recommended against in control 2.4.7.
Audit:
Perform the following to ensure that Bluetooth is only enabled if there are paired devices:
Run the following command to verify that Bluetooth is disabled:
If the value 1 is returned it indicates that Bluetooth is enabled. The computer is compliant
only if paired devices exist.
Run the following command to verify if there are paired devices:
Connected: Yes
41 | P a g e
Remediation:
Terminal Method:
Run the following command to disable Bluetooth
Note: When using the terminal method to disable Bluetooth, the prescribed state will not
be properly shown in the GUI. Use the terminal method of the audit to verify if Bluetooth is
enabled/disabled.
42 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
43 | P a g e
2.1.2 Ensure Show Bluetooth Status in Menu Bar Is Enabled
(Automated)
Profile Applicability:
• Level 1
Description:
By showing the Bluetooth status in the menu bar, a small Bluetooth icon is placed in the
menu bar. This icon quickly shows the status of Bluetooth, and can allow the user to quickly
turn Bluetooth on or off.
Rationale:
Enabling "Show Bluetooth status in menu bar" is a security awareness method that helps
understand the current state of Bluetooth, including whether it is enabled, discoverable,
what paired devices exist, and what paired devices are currently active.
Impact:
Bluetooth is a useful wireless tool that has been widely exploited when configured
improperly. The user should have insight into the Bluetooth status.
44 | P a g e
Audit:
Perform the following to ensure that Bluetooth status shows in the menu bar:
Graphical Method:
or
Terminal Method:
For each user, run the following command to verify that the Bluetooth status is enabled to
show in the menu bar:
18
Note: If the settings has not been changed from the default, then this audit will fail on the
command line. Follow the remediation instructions to verify that it is set to a disabled
status.
example:
18
or
Run the following command to verify that a profile is installed that enables Bluetooth to be
shown in the menu bar:
Bluetooth = 18;
45 | P a g e
Remediation:
Terminal Method:
For each user, run the following command to enable Bluetooth status in the menu bar:
example:
Profile Method:
46 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
47 | P a g e
2.2 Date & Time
This section contains recommendations related to the configurable items under the Date &
Time panel.
48 | P a g e
2.2.1 Ensure "Set time and date automatically" Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
Correct date and time settings are required for authentication protocols, file creation,
modification dates and log entries.
Note: If your organization has internal time servers, enter them here. Enterprise mobile
devices may need to use a mix of internal and external time servers. If multiple servers are
required use the Date & Time System Preference with each server separated by a space.
Rationale:
Kerberos may not operate correctly if the time on the Mac is off by more than 5 minutes.
This in turn can affect Apple's single sign-on feature, Active Directory logons, and other
features.
Impact:
Apple's automatic time update solution will enable an NTP server that is not controlled by
the Application Firewall. Turning on "Set time and date automatically" allows other
computers to connect to set their time and allows for exploit attempts against ntpd. It also
allows for more accurate network detection and OS fingerprinting
Current testing shows scanners can easily determine the MAC address and the OS vendor.
More extensive OS fingerprinting may be possible.
49 | P a g e
Audit:
Perform the following to ensure that the system's date and time are set automatically:
Graphical Method:
Terminal Method:
Run the following command to ensure that date and time are automatically set:
Network Time: On
or
Run the following command to verify that a profile is installed that enables date and time to
be set automatically:
forceAutomaticDateAndTime = 1;
50 | P a g e
Remediation:
Perform the following to enable the date and time to be set automatically:
Graphical Method:
Terminal Method:
Run the following commands to enable the date and time setting automatically:
setNetworkTimeServer: <your.time.server>
setUsingNetworkTime: On
example:
setNetworkTimeServer: time.apple.com
setUsingNetworkTime: On
Run the following commands if you have not set, or need to set, a new time zone:
example:
Time Zones:
Africa/Abidjan
Africa/Accra
Africa/Addis_Ababa
...
Pacific/Wake
Pacific/Wallis
51 | P a g e
Profile Method:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
52 | P a g e
2.2.2 Ensure time set is within appropriate limits (Automated)
Profile Applicability:
• Level 1
Description:
Correct date and time settings are required for authentication protocols, file creation,
modification dates and log entries. Ensure that time on the computer is within acceptable
limits. Truly accurate time is measured within milliseconds. For this audit, a drift under
four and a half minutes passes the control check. Since Kerberos is one of the important
features of macOS integration into Directory systems the guidance here is to warn you
before there could be an impact to operations. From the perspective of accurate time, this
check is not strict, so it may be too great for your organization. Your organization can
adjust to a smaller offset value as needed.
Note: ntpdate has been deprecated with 10.14. sntp replaces that command.
Rationale:
Kerberos may not operate correctly if the time on the Mac is off by more than 5 minutes.
This in turn can affect Apple's single sign-on feature, Active Directory logons, and other
features. Audit check is for more than 4 minutes and 30 seconds ahead or behind.
Impact:
53 | P a g e
Audit:
Run the following commands to verify the time is set within an appropriate limit:
The output will include Network Time Server: and the name of your time server.
example: Network Time Server: time.apple.com
Ensure that the offset result(s) are between -270.x and 270.x seconds.
example:
Remediation:
Run the following commands to ensure your time is set within an appropriate limit:
The output will include Network Time Server: and the name of your time server
example: Network Time Server: time.apple.com.
example:
54 | P a g e
Additional Information:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
55 | P a g e
2.3 Desktop & Screen Saver
This section contains recommendations related to the configurable items under the
Desktop & Screen Saver panel.
56 | P a g e
2.3.1 Ensure an Inactivity Interval of 20 Minutes Or Less for the Screen
Saver Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
A locking screensaver is one of the standard security controls to limit access to a computer
and the current user's session when the computer is temporarily unused or unattended. In
macOS, the screensaver starts after a value is selected in the drop down menu. 20 minutes
or less is an acceptable value. Any value can be selected through the command line or script
but a number that is not reflected in the GUI can be problematic. 20 minutes is the default
for new accounts.
Rationale:
Setting an inactivity interval for the screensaver prevents unauthorized persons from
viewing a system left unattended for an extensive period of time.
Impact:
If the screensaver is not set users may leave the computer available for an unauthorized
person to access information.
57 | P a g e
Audit:
The preferred audit procedure for this control will evaluate every user account on the
computer and will report on all users where the value has been set. If the default value of
20 minutes is used and the user has never changed the setting there will not be an audit
result on their compliant setting. The time is set in seconds so all outputs will be in that
format.
Perform the following to ensure the system is set for the screen saver to activate in 20
minutes of less:
Run this script to verify the idle times for all users:
58 | P a g e
For Macs with a single user:
Graphical Method:
or
Terminal Method:
Run the following command to verify that the screen saver idle time is set to less than or
equal to 20 minutes:
The output should be less than or equal to 20 minutes (≤1200). example: 60, 120, 300, 600,
or 1200
Note: If the output is The domain/default pair of (com.apple.screensaver,
idleTime) does not exist, then the setting has not been changed from the default. Follow
the remediation instructions to set the idle time to match your organization's policy.
or
Run the following command to verify that a profile is installed that enables a screensaver
idle time of less than or equal to 20 minutes:
The output should be less than or equal to 20 minutes (≤1200). example: 60, 120, 300, 600,
or 1200
59 | P a g e
60 | P a g e
Remediation:
Perform the following to set the screen saver to activate in 20 minutes of less:
Graphical Method:
Terminal Method:
Run the following command to verify that the idle time of the screen saver is set to 20
minutes of less (≤1200)
example:
If there are multiple users out of compliance with the prescribed setting, run this command
for each user to set their idle time:
example:
600
**Note:**Issues arise if the command line is used to make the setting something other than
what is available in the GUI Menu. Choose either 1 (60), 2 (120), 5 (300), 10 (600), or 20
(120) minutes to avoid any issues.
Profile Method:
61 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
62 | P a g e
2.3.2 Ensure Screen Saver Corners Are Secure (Automated)
Profile Applicability:
• Level 2
Description:
Hot Corners can be configured to disable the screen saver by moving the mouse cursor to a
corner of the screen.
Rationale:
Setting a hot corner to disable the screen saver poses a potential security risk since an
unauthorized person could use this to bypass the login screen and gain access to the
system.
Audit:
Perform the following to ensure that a Hot Corner is not set to Disable Screen Saver:
Graphical Method:
or
63 | P a g e
Terminal Method:
For all users, run the following commands to verify that Disable Screen Saver is not set as a
Hot Corner:
Verify that the output does not have 6 as a key value. Any other number, or an output that
includes does not exist, is compliant.
example:
10
$ sudo -u seconduser /usr/bin/defaults read com.apple.dock wvous-bl-corner
Run the following command to verify that a profile is installed secures screen saver
corners:
64 | P a g e
Remediation:
Perform the following to disable a Hot Corner set to Disable Screen Saver:
Graphical Method:
Terminal Method:
Run the following command to turn off Disable Screen Saver for a Hot Corner:
example:
Profile Method:
<array>
<dict>
<key>mcx_preference_settings</key>
<dict>
<key>wvous-bl-corner</key>
<integer><≠6></integer>
<key>wvous-br-corner</key>
<integer><≠6></integer>
<key>wvous-tl-corner</key>
<integer><≠6></integer>
<key>wvous-tr-corner</key>
<integer><≠6></integer>
</dict>
</dict>
</array>
65 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
66 | P a g e
2.3.3 Audit Lock Screen and Start Screen Saver Tools (Manual)
Profile Applicability:
• Level 1
Description:
In 10.13 Apple added a "Lock Screen" option to the Apple Menu. Prior to this the best quick
lock options were to use either a lock screen option with the screen saver or the lock
screen option from Keychain Access if status was made available in the menu bar. With
10.13 the menu bar option is no longer available. The intent of this control is to resemble
control-alt-delete on Windows Systems as a means of quickly locking the screen. If the user
of the system is stepping away from the computer the best practice is to lock the screen
and setting a hot corner is an appropriate method.
Rationale:
Ensuring the user has a quick method to lock their screen may reduce the opportunity for
individuals in close physical proximity of the device to see screen contents.
Audit:
Perform the following to ensure that a Hot Corner is set to either Start Screen Saver or Put
Display to Sleep:
Graphical Method:
or
67 | P a g e
Terminal Method:
For all users, run the following commands to verify that Start Screen Saver or Put Display
to Sleep is set as a Hot Corner:
For each user, verify at least one of the key values is set to 5 or 10. example "wvous-tr-
corner" = 5;or "wvous-br-corner" = 10;
example:
10
68 | P a g e
Remediation:
Perform the following to set a Hot Corner to either Start Screen Saver or Put Display to
Sleep:
Graphical Method:
Terminal Method:
For all users, run the following commands to set Start Screen Saver or Put Display to Sleep
as a Hot Corner:
example:
10
10
69 | P a g e
Profile Method:
<array>
<dict>
<key>mcx_preference_settings</key>
<dict>
<key>wvous-bl-corner</key>
<integer><5 or 10></integer>
<key>wvous-br-corner</key>
<integer><5 or 10></integer>
<key>wvous-tl-corner</key>
<integer><5 or 10></integer>
<key>wvous-tr-corner</key>
<integer><5 or 10></integer>
</dict>
</dict>
</array>
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
70 | P a g e
2.4 Sharing
This section contains recommendations related to the configurable items under the Sharing
panel.
71 | P a g e
2.4.1 Ensure Remote Apple Events Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
Apple Events is a technology that allows one program to communicate with other
programs. Remote Apple Events allows a program on one computer to communicate with a
program on a different computer.
Rationale:
Disabling Remote Apple Events mitigates the risk of an unauthorized program gaining
access to the system.
Impact:
With remote Apple events turned on, an AppleScript program running on another Mac can
interact with the local computer.
Audit:
Perform the following to ensure that Remote Apple Events is not enabled:
Graphical Method:
Terminal Method:
Run the following commands to verify that Remote Apple Events is not set
72 | P a g e
Remediation:
Terminal Method:
Run the following commands to set Remote Apple Events to Off:
setremoteappleevents: Off
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
73 | P a g e
2.4.2 Ensure Internet Sharing Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
Internet Sharing uses the open source natd process to share an internet connection with
other computers and devices on a local network. This allows the Mac to function as a router
and share the connection to other, possibly unauthorized, devices.
Rationale:
Disabling Internet Sharing reduces the remote attack surface of the system.
Impact:
Internet Sharing allows the computer to function as a router and other computers to use it
for access. This can expose both the computer itself and the networks it is accessing to
unacceptable access from unapproved devices.
74 | P a g e
Audit:
Terminal Method:
Run the following commands to verify that Internet Sharing is not set:
forceInternetSharingOff = 1;
75 | P a g e
Remediation:
Terminal Method:
Run the following command to turn off Internet Sharing:
Note: Using the Terminal Method will not uncheck the setting in System
Preferences>Sharing but will disable the underlying service.
Profile Method:
References:
1. STIGID AOSX-12-001270
76 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
77 | P a g e
2.4.3 Ensure Screen Sharing Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
Rationale:
Disabling Screen Sharing mitigates the risk of remote connections being made without the
user of the console knowing that they are sharing the computer.
Audit:
Terminal Method:
Run the following commands to verify that Screen Sharing is not set:
Note: If the settings has not been changed from the default, then this audit will fail on the
command line. Follow the remediation instructions to verify that it is set to a disabled
status.
78 | P a g e
Remediation:
Terminal Method:
Run the following command to turn off Screen Sharing:
References:
1. http://support.apple.com/kb/ph11151
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
79 | P a g e
2.4.4 Ensure Printer Sharing Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
By enabling Printer Sharing the computer is set up as a print server to accept print jobs
from other computers. Dedicated print servers or direct IP printing should be used instead.
Rationale:
Disabling Printer Sharing mitigates the risk of attackers attempting to exploit the print
server to gain access to the system.
Audit:
Terminal Method:
Run the following command to verify that Printer Sharing is not enabled:
Note: If the setting has not been changed from the default, then this audit will fail on the
command line. Follow the remediation instructions to verify that it is set to a disabled
status.
80 | P a g e
Remediation:
Terminal Method:
Run the following command to disable Printer Sharing:
References:
1. http://support.apple.com/kb/PH11450
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
81 | P a g e
2.4.5 Ensure Remote Login Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
Rationale:
Disabling Remote Login mitigates the risk of an unauthorized person gaining access to the
system via Secure Shell (SSH). While SSH is an industry standard to connect to posix
servers, the scope of the benchmark is for Apple macOS clients, not servers.
macOS does have an IP based firewall available (pf, ipfw has been deprecated) that is not
enabled or configured. There are more details and links in section 7.5. macOS no longer has
TCP Wrappers support built-in and does not have strong Brute-Force password guessing
mitigations, or frequent patching of openssh by Apple. Since most macOS computers are
mobile workstations, managing IP-based firewall rules on mobile devices can be very
resource-intensive. All of these factors can be parts of running a hardened SSH server.
82 | P a g e
Impact:
The SSH server built-in to macOS should not be enabled on a standard user computer,
particularly one that changes locations and IP addresses. A standard user that runs local
applications including email, web browser and productivity tools should not use the same
device as a server. There are Enterprise management tool-sets that do utilize SSH. If they
are in use, the computer should be locked down to only respond to known, trusted IP
addresses and appropriate admin service accounts.
For macOS computers that are being used for specialized functions there are several
options to harden the SSH server to protect against unauthorized access including brute
force attacks. There are some basic criteria that need to be considered:
• Do not open an SSH server to the internet without controls in place to mitigate SSH
brute force attacks. This is particularly important for systems bound to Directory
environments. It is great to have controls in place to protect the system, but if they
trigger after the user is already locked out of their account they are not optimal. If
authorization happens after authentication directory accounts for users that don't
even use the system can be locked out.
• Do not use SSH key pairs when there is no insight to the security on the client
system that will authenticate into the server with a private key. If an attacker gets
access to the remote system and can find the key they may not need a password or a
key logger to access the SSH server.
• Detailed instructions on hardening an SSH server, if needed, are available in the CIS
Linux Benchmarks but it is beyond the scope of this benchmark.
Audit:
Terminal Method:
Run the following command to verify that Remote Login is disabled:
83 | P a g e
Remediation:
Terminal Method:
Run the following command to disable Remote Login:
Do you really want to turn remote login off? If you do, you will lose this
connection and can only turn it back on locally at the server (yes/no)?
Additional Information:
man sshd_config
84 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
85 | P a g e
2.4.6 Ensure DVD or CD Sharing Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
DVD or CD Sharing allows users to remotely access the system's optical drive. While Apple
does not ship Macs with built-in optical drives any longer, external optical drives are still
recognized when they are connected. In testing the sharing of an external optical drive
persists when a drive is reconnected.
Rationale:
Disabling DVD or CD Sharing minimizes the risk of an attacker using the optical drive as a
vector for attack and exposure of sensitive data.
Impact:
Many Apple devices are now sold without optical drives and drive sharing may be needed
for legacy optical media. The media should be explicitly re-shared as needed rather than
using a persistent share. Optical drives should not be used for long term storage. To store
necessary data from an optical drive it should be copied to another form of external
storage. Optionally, an image can be made of the optical drive so that it is stored in it's
original form on another form of external storage
86 | P a g e
Audit:
Terminal Method:
Run the following command to verify that DVD or CD Sharing is disabled
Note: If the settings has not been changed from the default, then this audit will fail on the
command line. Follow the remediation instructions to verify that it is set to a disabled
status.
Remediation:
Terminal Method:
Run the following command to disable DVD or CD Sharing:
Note: If using the Terminal method, the GUI will still show the service checked until after a
reboot.
87 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
88 | P a g e
2.4.7 Ensure Bluetooth Sharing Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
Rationale:
Disabling Bluetooth Sharing minimizes the risk of an attacker using Bluetooth to remotely
attack the system.
Impact:
Control 2.1.1 discusses disabling Bluetooth if no paired devices exist. There is a general
expectation that Bluetooth peripherals will be used by most users in Apple's ecosystem. It
is possible that sharing is required and Bluetooth peripherals are not. Bluetooth must be
enabled if sharing is an acceptable use case.
89 | P a g e
Audit:
or
Terminal Method:
Run the following command to verify that Bluetooth Sharing is disabled:
or
Run the following command to verify that a profile is installed that disables Bluetooth
sharing:
PrefKeyServicesEnabled = 0;
90 | P a g e
Remediation:
Profile Method:
<dict>
<key>Forced</key>
<array>
<dict>
<key>mcx_preference_settings</key>
<dict>
<key>PrefKeyServicesEnabled</key>
<false/>
</dict>
</dict>
</array>
</dict>
91 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
92 | P a g e
2.4.8 Ensure File Sharing Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
Server Message Block (SMB), Common Internet File System (CIFS) When Windows (or
possibly Linux) computers need to access file shared on a Mac, SMB/CIFS file sharing is
commonly used. Apple warns that SMB sharing stores passwords is a less secure fashion
than AFP sharing and anyone with system access can gain access to the password for that
account. When sharing with SMB, each user that will access the Mac must have SMB
enabled.
Rationale:
By disabling File Sharing, the remote attack surface and risk of unauthorized access to files
stored on the system is reduced.
Impact:
File Sharing can be used to share documents with other users but hardened servers should
be used rather than user endpoints. Turning on File Sharing increases the visibility and
attack surface of a system unnecessarily.
93 | P a g e
Audit:
Terminal Method:
Run the following command to verify that SMB File Sharing is not enabled:
Note: If the settings have not been changed from the default, then this audit will fail on the
command line. Follow the remediation instructions to verify that it is set to a disabled
status.
Remediation:
Terminal Method:
Run the following command to disable SMB file sharing:
Additional Information:
macOS also supported file sharing using Apple File Protocol (AFP) until 10.15 Catalina. AFP
was removed in 11.0 Big Sur.
94 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
95 | P a g e
2.4.9 Ensure Remote Management Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
Remote Management is the client portion of Apple Remote Desktop (ARD). Remote
Management can be used by remote administrators to view the current screen, install
software, report on, and generally manage client Macs.
The screen sharing options in Remote Management are identical to those in the Screen
Sharing section. In fact, only one of the two can be configured. If Remote Management is
used, refer to the Screen Sharing section above on issues regard screen sharing.
Remote Management should only be enabled when a Directory is in place to manage the
accounts with access. Computers will be available on port 5900 on a macOS System and
could accept connections from untrusted hosts depending on the configuration, definitely a
concern for mobile systems.
Rationale:
Remote Management should only be enabled on trusted networks with strong user
controls present in a Directory system. Mobile devices without strict controls are
vulnerable to exploit and monitoring.
Impact:
Audit:
Run the following command to verify that Remote Management is not enabled:
96 | P a g e
Remediation:
Terminal Method:
Run the following command to disable Remote Management:
$ sudo
/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources
/kickstart -deactivate -stop
Starting...
Removed preference to start ARD after reboot.
Done.
Additional Information:
/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources
/kickstart -help
97 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
98 | P a g e
2.4.10 Ensure Content Caching Is Disabled (Automated)
Profile Applicability:
• Level 2
Description:
Starting with 10.13 (macOS High Sierra) Apple introduced a service to make it easier to
deploy data from Apple, including software updates, where there are bandwidth
constraints to the Internet and fewer constraints and greater bandwidth on the local
subnet. This capability can be very valuable for organizations that have throttled and
possibly metered Internet connections. In heterogeneous enterprise networks with
multiple subnets the effectiveness of this capability would be determined on how many
Macs were on each subnet at the time new large updates were made available upstream.
This capability requires the use of mac OS clients as P2P nodes for updated Apple content.
Unless there is a business requirement to manage operational Internet connectivity
bandwidth user endpoints should not store content and act as a cluster to provision data.
Rationale:
The main use case for Mac computers is as mobile user endpoints. P2P sharing services
should not be enabled on laptops that are using untrusted networks. Content Caching can
allow a computer to be a server for local nodes on an untrusted network. While there are
certainly logical controls that could be used to mitigate risk, they add to the management
complexity. Since the value of the service is in specific use cases organizations with the use
case described above can accept risk as necessary.
Impact:
This setting will adversely affect bandwidth usage between local subnets and the Internet.
99 | P a g e
Audit:
or
Terminal Method:
Run the following command to verify that Content Caching is not enabled:
or
Run the following command to verify that a profile is installed that disables content
caching:
allowContentCaching = 0;
100 | P a g e
Remediation:
Terminal Method:
Run the following command to disable Content Caching:
References:
1. https://support.apple.com/guide/mac-help/about-content-caching-
mchl9388ba1b/
2. https://support.apple.com/guide/mac-help/set-up-content-caching-on-mac-
mchl3b6c3720/
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
101 | P a g e
2.4.11 Ensure AirDrop Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
AirDrop is Apple's built-in on demand ad hoc file exchange system that is compatible with
both macOS and iOS. It uses Bluetooth LE for discovery that limits connectivity to Mac or
iOS users that are in close proximity. Depending on the setting it allows everyone or only
Contacts to share files when they are nearby to each other.
In many ways this technology is far superior to the alternatives. The file transfer is done
over a TLS encrypted session, does not require any open ports that are required for file
sharing, does not leave file copies on email servers or within cloud storage, and allows for
the service to be mitigated so that only people already trusted and added to contacts can
interact with you.
While there are positives to AirDrop, there are privacy concerns that could expose personal
information. For that reason, AirDrop should be disabled, and should only be enabled when
needed and disabled afterwards.
Rationale:
AirDrop can allow malicious files to be downloaded from unknown sources. Contacts Only
limits may expose personal information to devices in the same area.
Impact:
Disabling AirDrop can limit the ability to move files quickly over the network without using
file shares.
102 | P a g e
Audit:
or
103 | P a g e
Terminal Method:
For all users, run the following commands to verify whether AirDrop is disabled:
Note: If the setting has not been changed from the default, then this audit will fail on the
command line. Follow the remediation instructions to verify that it is set to a disabled
status.
example:
or
Run the following command to verify that a profile is installed that disabled AirDrop:
DisableAirDrop = 1;
104 | P a g e
Remediation:
Terminal Method:
Run the following commands to disable AirDrop:
example:
Profile Method:
<array>
<dict>
<key>mcx_preference_settings</key>
<dict>
<key>DisableAirDrop</key>
<true/>
</dict>
</dict>
</array>
References:
1. https://www.techrepublic.com/article/apple-airdrop-users-reportedly-vulnerable-
to-security-flaw/
2. https://www.imore.com/how-apple-keeps-your-airdrop-files-private-and-secure
3. https://en.wikipedia.org/wiki/AirDrop
105 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
106 | P a g e
2.4.12 Ensure Media Sharing Is Disabled (Automated)
Profile Applicability:
• Level 2
Description:
Starting with macOS 10.15 Apple has provided a control to allow a user to share Apple
downloaded content on all Apple devices that are signed in with the same Apple ID. This
allows a user to share downloaded Movies, Music or TV shows with other controlled
macOS, iOS and iPadOS devices as well as photos with Apple TVs.
With this capability guest users can also use media downloaded on the computer.
The recommended best practice is not to use the computer as a server but to utilize Apple's
cloud storage to download and use content stored there if content stored with Apple is
used on multiple devices.
https://support.apple.com/guide/mac-help/set-up-media-sharing-on-mac-
mchlp13371337/mac
Rationale:
Disabling Media Sharing reduces the remote attack surface of the system.
Impact:
Media Sharing allows for pre-downloaded content on a Mac to be available to other Apple
devices on the same network. Leaving this disabled forces device users to stream or
download content from each Apple authorized device. This sharing could even allow
unauthorized devices on the same network media access.
107 | P a g e
Audit:
or
108 | P a g e
Terminal Method:
Run the following command to verify that Media Sharing is not enabled:
example:
or
Run the following command to verify that a profile is installed that disablesMedia Sharing:
homeSharingUIStatus = 0;
legacySharingUIStatus = 0;
mediaSharingUIStatus = 0;
109 | P a g e
Remediation:
Terminal Method:
Run the following command to disable Media Sharing:
example:
Profile Method:
110 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
111 | P a g e
2.4.13 Ensure AirPlay Receiver Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
In macOS Monterey (12.0) Apple has added the capability to share content from another
Apple device to the screen of a host Mac. While there are many valuable uses of this
capability this sharing on a standard Mac user workstation should be enabled ad hoc as
required rather than allowing a continuous sharing service. The feature can be restricted
by Apple ID or network and is configured to use accepting the connection on the Mac. Part
of the concern is frequent connection requests may function as a denial-of-service and
access control limits may provide too much information to an attacker.
https://macmost.com/how-to-use-a-mac-as-an-airplay-receiver.html
https://support.apple.com/guide/mac-pro-rack/use-airplay-apdf1417128d/mac
Rationale:
This capability appears very useful for kiosk and shared work spaces. The ability to allow
by network could be especially useful on segregated guest networks where visitors could
share there screens on computers with bigger monitors, including computers connected to
projectors.
Impact:
Turning off AirPlay sharing by default will not allow users to share without turning the
service on. The service should be enable as needed rather than left on.
112 | P a g e
Audit:
Perform the following to ensure that Bluetooth status shows in the menu bar:
Graphical Method:
or
Terminal Method:
For each user, run the following command to verify that the Bluetooth status is enabled to
show in the menu bar:
Note: If the settings has not been changed from the default, then this audit will fail on the
command line. Follow the remediation instructions to verify that it is set to a disabled
status.
example:
or
Run the following command to verify that a profile is installed that disables the ability to
use the computer as an AirPlay Receiver:
AirplayRecieverEnabled = 0;
113 | P a g e
Remediation:
Terminal Method:
For each user, run the following command to enable Bluetooth status in the menu bar:
example:
Profile Method:
Default Value:
114 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
115 | P a g e
2.5.1 Encryption
Apple has created simple easy to use encryption capabilities built-in to macOS. In order to
protect data and privacy, those tools need to be utilized to protect information processed
by macOS computers.
116 | P a g e
2.5.1.1 Ensure FileVault Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
FileVault secures a system's data by automatically encrypting its boot volume and
requiring a password or recovery key to access it.
FileVault may also be enabled using command line using the fdesetup command. To use
this functionality, consult the Der Flounder blog for more details:
https://derflounder.wordpress.com/2015/02/02/managing-yosemites-filevault-2-with-
fdesetup/ https://derflounder.wordpress.com/2019/01/15/unlock-or-decrypt-your-
filevault-encrypted-boot-drive-from-the-command-line-on-macos-mojave/
Rationale:
Encrypting sensitive data minimizes the likelihood of unauthorized users gaining access to
it.
Impact:
Mounting a FileVault encrypted volume from an alternate boot source will require a valid
password to decrypt it.
Audit:
Terminal Method:
Run the following command to verify that FileVault is enabled:
FileVault is On
117 | P a g e
Remediation:
Additional Information:
FileVault may not be desirable on a virtual OS. As long as the hypervisor and file storage are
encrypted the virtual OS does not need to be. Rather than checking if the OS is virtual and
passing the control regardless of the encryption of the host system the normal check will be
run. Security officials can evaluate the comprehensive controls outside of the OS being
tested.
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
118 | P a g e
2.5.1.2 Ensure all user storage APFS volumes are encrypted (Manual)
Profile Applicability:
• Level 1
Description:
Apple developed a new file system that was first made available in 10.12 and then became
the default in 10.13. The file system is optimized for Flash and Solid State storage and
encryption. https://en.wikipedia.org/wiki/Apple_File_System macOS computers generally
have several volumes created as part of APFS formatting including Preboot, Recovery and
Virtual Memory (VM) as well as traditional user disks.
All APFS volumes that do not have specific roles that do not require encryption should be
encrypted. "Role" disks include Preboot, Recovery and VM. User disks are labelled with
"(No specific role)" by default.
Rationale:
In order to protect user data from loss or tampering volumes carrying data should be
encrypted.
Impact:
While FileVault protects the boot volume data may be copied to other attached storage and
reduce the protection afforded by FileVault. Ensure all user volumes are encrypted to
protect data.
119 | P a g e
Audit:
120 | P a g e
| +-> Volume disk1s4 XXXXXYYY
| ---------------------------------------------------
| APFS Volume Disk (Role): disk1s4 (VM)
| Name: VM (Case-insensitive)
| Mount Point: /private/var/vm
| Capacity Consumed: 6442704896 B (6.4 GB)
| FileVault: No
|
+-- Container disk4 XXXXXYYYY
====================================================
APFS Container Reference: disk4
Size (Capacity Ceiling): 119824367616 B (119.8 GB)
Minimum Size: 143192064 B (143.2 MB)
Capacity In Use By Volumes: 126492672 B (126.5 MB) (0.1% used)
Capacity Not Allocated: 119697874944 B (119.7 GB) (99.9% free)
|
+-< Physical Store disk3s2 XXXXXYYYYYY
| -----------------------------------------------------------
| APFS Physical Store Disk: disk3s2
| Size: 119824371200 B (119.8 GB)
|
+-> Volume disk4s1 C4D99580-1FDA-43BF-BB62-B21BF7EE568C
---------------------------------------------------
APFS Volume Disk (Role): disk4s1 (No specific role)
Name: Passport (Case-insensitive)
Mount Point: /Volumes/Passport
Capacity Consumed: 839680 B (839.7 KB)
FileVault: Yes (Unlocked)
Remediation:
Use Disk Utility to erase a user disk and format as APFS (Encrypted).
Note: APFS Encrypted disks will be described as "FileVault" whether they are the boot
volume or not in the ap list.
121 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
122 | P a g e
2.5.1.3 Ensure all user storage CoreStorage volumes are encrypted
(Manual)
Profile Applicability:
• Level 1
Description:
Apple introduced CoreStorage with 10.7. It is used as the default for formatting on macOS
volumes prior to 10.13.
Rationale:
In order to protect user data from loss or tampering, volumes carrying data should be
encrypted
Impact:
While FileVault protects the boot volume data may be copied to other attached storage and
reduce the protection afforded by FileVault. Ensure all user volumes are encrypted to
protect data.
123 | P a g e
Audit:
124 | P a g e
+-- Logical Volume Group XXXXXYYYY
=========================================================
Name: Passport
Status: Online
Size: 119690149888 B (119.7 GB)
Free Space: 1486848 B (1.5 MB)
|
+-< Physical Volume XXXXXYYY
| ----------------------------------------------------
| Index: 0
| Disk: disk3s2
| Status: Online
| Size: 119690149888 B (119.7 GB)
|
+-> Logical Volume Family XXXXXYYYYY
----------------------------------------------------------
Encryption Type: AES-XTS
Encryption Status: Unlocked
Conversion Status: Complete
High Level Queries: Fully Secure
| Passphrase Required
| Accepts New Users
| Has Visible Users
| Has Volume Key
|
+-> Logical Volume XXXXXYYYYYY
---------------------------------------------------
Disk: disk4
Status: Online
Size (Total): 119336337408 B (119.3 GB)
Revertible: No
LV Name: Passport
Volume Name: Passport
Content Hint: Apple_HFS
Remediation:
Use Disk Utility to erase a disk and format as macOS Extended (Journaled, Encrypted)
125 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
126 | P a g e
2.5.2 Firewall
macOS has a built-in firewall that has two main configuration aspects. Both the Application
Layer Firewall (ALF) and the Packet Filter Firewall (PF) can be used to secure running
ports and services on a Mac. The Application Firewall is the one accessible in System
Preferences under security. The PF firewall contains many more capabilities than ALF, but
also requires a greater understanding of firewall recipes and rule configurations. For
standard use cases on a Mac use of the PF firewall is not necessary. macOS may expose
server services that are reachable remotely but that is not the primary use case or design. If
custom use cases are required the PF firewall can provide additional security. Macs that are
used as mobile desktops do not need to use the PF firewall capabilities unless permanently
open ports need to be protected with more granular IP access controls.
Additional information
https://www.muo.com/tag/mac-really-need-firewall/
https://blog.neilsabol.site/post/quickly-easily-adding-pf-packet-filter-firewall-rules-
macos-osx/
http://marckerr.com/a-simple-guild-to-the-mac-pf-firewall/
https://blog.scottlowe.org/2013/05/15/using-pf-on-os-x-mountain-lion/
127 | P a g e
2.5.2.1 Ensure Gatekeeper is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
Rationale:
128 | P a g e
Audit:
or
Terminal Method:
Run the following command to verify that Gatekeeper is enabled:
assessments enabled
or
Run the following command to verify that a profile is installed that enables Gatekeeper:
AllowIdentifiedDevelopers = 1;
EnableAssessment = 1;
129 | P a g e
Remediation:
Terminal Method:
Run the following command to enable Gatekeeper to allow applications from App Store and
identified developers:
Profile Method:
130 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
131 | P a g e
2.5.2.2 Ensure Firewall Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
http://support.apple.com/en-us/HT201642
Rationale:
A firewall minimizes the threat of unauthorized users from gaining access to your system
while connected to a network or the Internet.
Impact:
The firewall may block legitimate traffic. Applications that are unsigned will require special
handling.
132 | P a g e
Audit:
or
Terminal Method:
Run the following command to verify that the firewall is enabled:
EnableFirewall = 1;
133 | P a g e
Remediation:
Terminal Method:
Run the following command to enable the firewall:
For the <value>, use either 1, specific services, or 2, essential services only.
Profile Method:
References:
1. https://support.apple.com/en-ca/guide/security/seca0e83763f/web
134 | P a g e
Additional Information:
Your organization might want to verify and limit specific applications that allow incoming
connectivity.
Graphical Method:
Terminal Method:
Run the following command to verify the what applications are allowing incoming
connections:
The output will show any applications, and their path, and their associated rule.
example:
1 : /System/Library/CoreServices/RemoteManagement/ARDAgent.app
( Allow incoming connections )
2 : /Applications/Chess.app
( Allow incoming connections )
3 : /Applications/Contacts.app
( Block incoming connections )
Perform the following to remove unnecessary firewall rules:
135 | P a g e
Terminal Method:
The </path/application name> is the one to be removed from the previous listing.
example:
1 : /System/Library/CoreServices/RemoteManagement/ARDAgent.app
( Allow incoming connections )
2 : /Applications/Chess.app
( Allow incoming connections )
3 : /Applications/Contacts.app
( Block incoming connections )
136 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
137 | P a g e
2.5.2.3 Ensure Firewall Stealth Mode Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
While in Stealth mode the computer will not respond to unsolicited probes, dropping that
traffic.
http://support.apple.com/en-us/HT201642
Rationale:
Stealth mode on the firewall minimizes the threat of system discovery tools while
connected to a network or the Internet.
Impact:
Traditional network discovery tools like ping will not succeed. Other network tools that
measure activity and approved applications will work as expected.
This control aligns with the primary macOS use case of a laptop that is often connected to
untrusted networks where host segregation may be non-existent. In that use case hiding
from the other inmates is likely more than desirable. In use cases where use is only on
trusted LANs with static IP addresses stealth mode may not be desirable.
138 | P a g e
Audit:
Perform the following to verify the firewall has stealth mode enabled:
Graphical Method:
or
Terminal Method:
Run the following command to verify that stealth mode is enabled:
or
Run the following command to verify that a profile is installed that enables firewall stealth
mode:
EnableStealthMode = 1;
139 | P a g e
Remediation:
Terminal Method:
Run the following command to enable stealth mode:
Profile Method:
Note: This key must be set in the same configuration profile with EnableFirewall set to
<true/>. If it is set in it's own configuration profile, it will fail.
Additional Information:
http://docs.info.apple.com/article.html?artnum=306938
140 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
141 | P a g e
2.5.3 Ensure Location Services Is Enabled (Automated)
Profile Applicability:
• Level 2
Description:
macOS uses location information gathered through local Wi-Fi networks to enable
applications to supply relevant information to users. With the operating system verifying
the location, users do not need to change the time or the time zone. The computer will
change them based on the user's location. They do not need to specify their location for
weather or travel times and even get alerts on travel times to meetings and appointment
where location information is supplied.
Location Services simplify some processes, for the purpose of asset management and time
and log management, with mobile computers.
There are some use cases where it is important that the computer not be able to report its
exact location. While the general use case is to enable Location Services, it should not be
allowed if the physical location of the computer and the user should not be public
knowledge.
Rationale:
Location Services are helpful in most use cases and can simplify log and time management
where computers change time zones.
Audit:
Terminal Method:
Run the following command to verify that Location Services are enabled:
142 | P a g e
Remediation:
Terminal Method:
Run the following command to enable Location Services
Note: In some use cases organizations may not want Location Services running. To disable
Location Services, System Integrity Protection must be disabled.
References:
1. https://support.apple.com/en-us/HT204690
143 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
144 | P a g e
2.5.4 Audit Location Services Access (Manual)
Profile Applicability:
• Level 2
Description:
macOS uses location information gathered through local Wi-Fi networks to enable
applications to supply relevant information to users. While Location Services may be very
useful, it may not be desirable to allow all applications that can use Location Services to use
your location for Internet queries to provide tailored content based on your current
location.
Ensure that the applications that can use Location Services are authorized to use that
information and provide that information where the application interacts with external
systems. Apple provides feedback within System Preferences and may be enabled to
provide information on the menu bar when Location Services are used.
Applications that support Location Services can be individually controlled in the Privacy
tab in Security & Privacy under System Preferences.
Rationale:
Impact:
Many macOS services rely on Location Services for tailored services. Users expect their
time zone and weather to be relevant to where they are without manual intervention. Find
my Mac does need to know where your Mac actually is. Where possible the tolerance
between location privacy and convenience may be best left to the user when the location
itself is not sensitive. If facility locations are not public location information should be
tightly controlled.
145 | P a g e
Audit:
Perform the following to verify what applications are enabled for Location Services:
Graphical Method:
Perform the following to verify what websites are enabled to ask for access to Location
Services:
Graphical Method:
1. Open Safari
2. Select Safari from the menu bar
3. Select Preferences
4. Select Websites
5. Select Location
6. Verify that When visiting other websites is set to Ask or Deny
Terminal Method:
Run the following command to evaluate the applications that are enabled to use Location
Services:
Ensure that all applications listed have been authorized to access location information.
146 | P a g e
Remediation:
Perform the following to set websites to ask for permission to access Location Services:
1. Open Safari
2. Select Safari from the menu bar
3. Select Preferences
4. Select Websites
5. Select Location
6. Set When visiting other websites to Ask or Deny
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
147 | P a g e
2.5.5 Ensure Sending Diagnostic and Usage Data to Apple Is Disabled
(Automated)
Profile Applicability:
• Level 2
Description:
Apple provides a mechanism to send diagnostic and analytics data back to Apple to help
them improve the platform. Information sent to Apple may contain internal organizational
information that should be controlled and not available for processing by Apple. Turn off all
Analytics and Improvements sharing.
Share Mac Analytics (Share with App Developers dependent on Mac Analytic sharing)
Rationale:
Organizations should have knowledge of what is shared with the vendor and the setting
automatically forwards information to Apple.
148 | P a g e
Audit:
Perform the following to verify that diagnostic data is not being send to Apple:
Graphical Method:
or
Terminal Method:
Run the following command to disable sending diagnostic and usage data to Apple:
or
Run the following command to verify that a profile is installed that disables sending
diagnostic and usage data to Apple:
allowDiagnosticSubmission = 0;
149 | P a g e
Remediation:
Terminal Method:
Profile Method:
150 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
151 | P a g e
2.5.6 Ensure Limit Ad Tracking Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
Apple provides a framework that allows advertisers to target Apple users and end-users
with advertisements. While many people prefer that when they see advertising it is
relevant to them and their interests, the detailed information that is data mining collected,
correlated, and available to advertisers in repositories is often disconcerting. This
information is valuable to both advertisers and attackers and has been used with other
metadata to reveal users' identities.
Organizations should manage advertising settings on computers rather than allow users to
configure the settings.
Apple Information
Rationale:
Organizations should manage user privacy settings on managed devices to align with
organizational policies and user data protection requirements.
Impact:
Uses will see generic advertising rather than targeted advertising. Apple warns that this
will reduce the number of relevant ads.
152 | P a g e
Audit:
or
Terminal Method:
For each user, run the following command to verify that ad tracking is limited:
153 | P a g e
example:
forceLimitAdTracking = 1;
allowApplePersonalizedAdvertising = 0;
154 | P a g e
Remediation:
Terminal Method:
For each needed user, run the following command to enable limited ad tracking:
example:
Profile Method:
155 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
156 | P a g e
2.5.7 Audit Camera Privacy and Confidentiality (Manual)
Profile Applicability:
• Level 2
Description:
If the computer is present in an area where there are privacy concerns or sensitive images
or actions are taking place the camera should be covered at those times. A permanent cover
or alteration may be required when the computer is always located in a confidential area.
Malware is continuously discovered that circumvents the privacy controls of the built-in
camera. No computer has perfect security and it seems likely that even if all the drivers are
disabled or removed that working drivers can be re-introduced by a determined attacker.
Rationale:
At this point video chatting and other uses of the built-in camera are standard uses for a
computer. In cases where the camera is not allowed to be used at all or when the computer
is located in private areas additional precautions are warranted. OS components used for
the built-in video camera can also be used for other connected cameras, whether USB or
Bluetooth. Removed OS components that enable a camera may be re-installed or re-
enabled.
The General rule should be that if the camera can capture images that could cause
embarrassment or an adverse impact the camera should be covered until it is appropriate
to use.
157 | P a g e
Audit:
or
Terminal Method:
Run the following command to verify that a profile is installed that sets connected cameras
to your organization's setting:
allowCamera = 0; disables the ability to use any connected cameras and allowCamera =
1; enables the ability to use any connected cameras.
Remediation:
Perform the following to set the camera settings to your organization's requirements:
Profile Method:
Additional Information:
There should be no hardware modifications done to the computers to remove any built-in
FaceTime cameras.
158 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
159 | P a g e
2.6 Apple ID
Apple is a hardware manufacturer that develops operating systems for the hardware it
creates. Apple is also a cloud service provider and those services include applications,
music, books, television, cloud storage etc. Apple simplifies the process to ensure that all
user devices are entitled to content where the user has purchased access, or is part of an
Apple basic level of entitlement (BLE) for purchasing an Apple device. The use of an Apple
ID allows for a consistent access and experience across all Apple devices. An Apple ID
functions as Single-Sign-On access to all Apple provided services. It is critical that each
user's account is protected appropriately so that unauthorized access risk is heavily
mitigated.
https://support.apple.com/en-us/HT203993
https://en.wikipedia.org/wiki/Apple_ID
https://www.lifewire.com/what-is-an-apple-id-1994330
https://support.apple.com/en-us/HT201303
160 | P a g e
2.6.1 iCloud
iCloud is Apple's service for synchronizing, storing and backing up data from Apple
applications in both macOS and iOS.
macOS controls for iCloud are part of the Apple ID settings in macOS. The configuration
options in macOS resemble the options in iOS.
161 | P a g e
2.6.1.1 Audit iCloud Configuration (Manual)
Profile Applicability:
• Level 2
Description:
Apple's iCloud is a consumer-oriented service that allows a user to store data as well as
find, control and backup devices that are associated with their Apple ID (Apple account).
The use of iCloud on Enterprise devices should align with the acceptable use policy for
devices that are managed as well as confidentiality requirements for data handled by the
user. If iCloud is allowed the data that is copied to Apple servers will likely be duplicated on
both personal as well as Enterprise devices.
For many users the Enterprise email system may replace many of the available features in
iCloud. If using either an Exchange or Google environment email, calendars, notes and
contacts can sync to the official Enterprise repository and be available through multiple
devices.
Apple's iCloud is just one of many cloud-based solutions being used for data
synchronization across multiple platforms and it should be controlled consistently with
other cloud services in your environment. Work with your employees and configure the
access to best enable data protection for your mission.
Rationale:
Organizations must make a risk decision on how their computers will interact with public
cloud services.
Impact:
iCloud services are integrated deeply into macOS and in many cases are expected to be
used by Mac users. iCloud is a public cloud and is not covered by an organizational security
plan. In many cases synchronizing user data from an organizational computer to an
uncontrolled location, no matter who is the data owner, is unacceptable.
162 | P a g e
Audit:
Terminal Method:
For each user, run this command to review enabled iCloud services:
The output will include all settings for the user's iCloud account.
example:
{
Accounts = (
{
AccountAlternateDSID = "000000-00-00a0aa00-0a00-0000-a000-
0aa0a0a0a000";
AccountDSID = 0000000000;
AccountDescription = iCloud;
AccountID = "[email protected]";
DisplayName = "Second User";
LoggedIn = 1;
Services = (
{
Name = CLOUDDESKTOP;
ServiceID = "com.apple.Dataclass.CloudDesktop";
status = active;
},
{
Name = FAMILY;
ServiceID = "com.apple.Dataclass.Family";
showManageFamily = 1;
},
{
Enabled = 1;
Name = "MOBILE_DOCUMENTS";
ServiceID = "com.apple.Dataclass.Ubiquity";
apsEnv = production;
authMechanism = token;
url = "https://p13-ubiquity.icloud.com:443";
wsUrl = "https://p13-ubiquityws.icloud.com:443";
},
163 | P a g e
{
Enabled = 1;
Name = "PHOTO_STREAM";
ServiceID = "com.apple.Dataclass.Photos";
},
{
Name = "MAIL_AND_NOTES";
ServiceID = "com.apple.Dataclass.Mail";
},
{
Enabled = 1;
Name = CONTACTS;
ServiceID = "com.apple.Dataclass.Contacts";
authMechanism = token;
beta = 0;
protocol = dav;
url = "https://p13-contacts.icloud.com:443";
},
{
Enabled = 1;
Name = CALENDAR;
ServiceID = "com.apple.Dataclass.Calendars";
authMechanism = token;
beta = 0;
protocol = dav;
url = "https://p13-caldav.icloud.com:443";
},
{
Enabled = 1;
Name = REMINDERS;
ServiceID = "com.apple.Dataclass.Reminders";
authMechanism = token;
beta = 0;
protocol = dav;
url = "https://p13-caldav.icloud.com:443";
},
{
Enabled = 1;
Name = BOOKMARKS;
ServiceID = "com.apple.Dataclass.Bookmarks";
apsEnv = production;
authMechanism = token;
beta = 0;
protocol = dav;
url = "https://p13-bookmarks.icloud.com:443";
},
{
Enabled = 1;
Name = NOTES;
ServiceID = "com.apple.Dataclass.Notes";
},
164 | P a g e
{
Name = SIRI;
ServiceID = "com.apple.Dataclass.Siri";
},
{
Enabled = 0;
Name = "KEYCHAIN_SYNC";
ServiceID = "com.apple.Dataclass.KeychainSync";
authMechanism = token;
escrowProxyUrl = "https://p13-
escrowproxy.icloud.com:443";
},
{
Name = "SHARED_STREAMS";
ServiceID = "com.apple.Dataclass.SharedStreams";
apsEnv = production;
authMechanism = token;
beta = 0;
url = "https://p13-sharedstreams.icloud.com:443";
},
{
Enabled = 1;
Name = "FIND_MY_MAC";
ServiceID = "com.apple.Dataclass.DeviceLocator";
apsEnv = Production;
authMechanism = token;
hostname = "p13-fmip.icloud.com";
url = "https://p13-fmip.icloud.com:443";
}
);
beta = 0;
firstName = Second;
isManagedAppleID = 0;
lastName = User;
primaryEmailVerified = 1;
}
);
}
Remediation:
165 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
166 | P a g e
2.6.1.2 Audit iCloud Keychain (Manual)
Profile Applicability:
• Level 2
Description:
The iCloud keychain is Apple's password manager that works with macOS and iOS. The
capability allows users to store passwords in either iOS or macOS for use in Safari on both
platforms and other iOS-integrated applications. The most pervasive use is driven by iOS
use rather than macOS. The passwords stored in a macOS keychain on an Enterprise-
managed computer could be stored in Apple's cloud and then be available on a personal
computer using the same account. The stored passwords could be for organizational as
well as for personal accounts.
If passwords are no longer being used as organizational tokens they are not in scope for
iCloud keychain storage.
Rationale:
Ensure that the iCloud keychain is used consistently with organizational requirements.
167 | P a g e
Audit:
or
Terminal Method:
For each user, run this command to verify the iCloud keychain sync services:
Enabled = <0,1>;
Name = "KEYCHAIN_SYNC";
The output will be either a 0, disabled, or 1, enabled. Verify if the setting meets your
organizations requirements
example:
or
Run the following command to verify that a profile is installed that sets iCloud Keychain
sync to your organizations settings:
168 | P a g e
Remediation:
Perform the following to set iCloud keychain sync based on your organization's
requirements:
Graphical Method:
Profile Method:
Note: iCloud Keychain and iCloud Drive must be set in a single configuration profile.
169 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
170 | P a g e
2.6.1.3 Audit iCloud Drive (Manual)
Profile Applicability:
• Level 2
Description:
iCloud Drive is Apple's storage solution for applications on both macOS and iOS to use the
same files that are resident in Apple's cloud storage. The iCloud Drive folder is available
much like Dropbox, Microsoft OneDrive or Google Drive.
One of the concerns in public cloud storage is that proprietary data may be inappropriately
stored in an end user's personal repository. Organizations that need specific controls on
information should ensure that this service is turned off or the user knows what
information must be stored on services that are approved for storage of controlled
information.
Rationale:
Organizations should review third party storage solutions pertaining to existing data
confidentiality and integrity requirements.
Impact:
Users will not be able to use continuity on macOS to resume the use of newly composed but
unsaved files
171 | P a g e
Audit:
or
Terminal Method:
Run the following command to verify that iCloud Drive is set to your organizations
specifications:
The output will include Enabled = and iCloud Drive is either enabled, 1, or disabled, 0.
Verify that the service is set to your organization's requirements.
example:
Enabled = 0;
Name = "MOBILE_DOCUMENTS";
or
Run the following command to verify that a profile is installed that sets iCloud Drive sync to
your organizations settings:
172 | P a g e
Remediation:
Profile Method:
Note: iCloud Keychain and iCloud Drive must be set in a single configuration profile.
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
173 | P a g e
2.6.1.4 Ensure iCloud Drive Document and Desktop Sync is Disabled
(Automated)
Profile Applicability:
• Level 2
Description:
With macOS 10.12 Apple introduced the capability to have a user's Desktop and Documents
folders automatically synchronize to the user's iCloud Drive, provided they have enough
room purchased through Apple on their iCloud drive. This capability mirrors what
Microsoft is doing with the use of OneDrive and Office 365. There are concerns with using
this capability.
The storage space that Apple provides for free is used by users with iCloud mail, all of a
user's Photo Library created with the ever larger Multi-Pixel iPhone cameras and all of the
iOS Backups. Adding a synchronization capability for users who have files going back a
decade or more and storage may be tight without much larger Apple charges than the free
5GB. Users with multiple computers running 10.12 and above with unique content on each
will have issues as well.
Enterprise users may not be allowed to store Enterprise information in a third-party public
cloud. In previous implementations iCloud Drive or even DropBox the user selected what
files were synchronized even if there were no other controls. The new feature synchronizes
all files in a folder widely used to put working files.
The automatic synchronization of all files in a user's Desktop and Documents folders
should be disabled.
https://derflounder.wordpress.com/2016/09/23/icloud-desktop-and-documents-in-
macos-sierra-the-good-the-bad-and-the-ugly/
Rationale:
Impact:
Users will not be able to use iCloud for the automatic sync of the Desktop and Documents
folders.
174 | P a g e
Audit:
Perform the following to verify if Desktop and Documents in iCloud Drive is enabled:
Graphical Method:
or
Terminal Method:
For each user, run the following command to verify that the Documents and Desktop
folders are not syncing to iCloud:
175 | P a g e
example:
total 8
allowCloudDesktopAndDocuments = 0;
Remediation:
Profile Method:
176 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
177 | P a g e
2.6.2 Audit App Store Password Settings (Manual)
Profile Applicability:
• Level 2
Description:
With OS X 10.11 Apple added settings for password storage for the App Store in macOS.
These settings parallel the settings in iOS. As with iOS the choices are a requirement to
provide a password after every purchase or to have a 15-minute grace period, and whether
to require a password for free purchases. The response to this setting is stored in a cookie
and processed by iCloud.
There is plenty of risk information on the wisdom of this setting for parents with children
buying games on iPhones and iPads. The most relevant information here is the likelihood
that users that are not authorized to download software may have physical access to an
unlocked computer where someone who is authorized recently made a purchase. If that is a
concern a password should be required at all times for App Store access in the Password
Settings controls.
Rationale:
Audit:
Perform the following to verify that App Store Passwords are set to your organization's
requirements:
Graphical Method:
178 | P a g e
Remediation:
Perform the following to set App Store Passwords to your organization's requirements:
Graphical Method:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
179 | P a g e
2.7 Time Machine
One of the most important IT Operational concerns is to ensure that information is
protected against loss or tampering. The purpose of the IT devices is to process the data
after all. At one time the cost of IT equipment and the volume of the data might make the
protection of the equipment itself more important. At this point the vast size of data
archives, and the lower cost of end-user equipment, makes data protection central to
operational planning. Backup strategies are generally focused on ensuring that there are
multiple copies of relevant versions of user files. The plan is that no single hardware or
software loss or failure will result in major data loss.
Apple does not provide a native remote logging capability that encrypts data in transit
(DIT). If no third party tool or agent is installed on organizational manned Macs it is even
more important to ensure that backup processes are implemented with log backups as part
of the architecture.
In recent years the criticality of information backup, protection of data and data backups
has become even more important with the rise of cybercriminals that not only commit
denial-of-service attacks using ransomware to encrypt your working data to make it
inaccessible, they also will encrypt the backups if reachable. Newer threats include
blackmail to compromise data confidentiality. A comprehensive plan to protect data from
compromise is even more vital with current threats. The Time Machine controls are only
recommended best practices to assist in ease of frequent backups and the encryption of
backup volumes.
Apple introduced Time Machine in 2007 as a simple-to-use built-in mechanism for users to
ensure that their machine was backed up and if there was a mistake or loss, information
could be easily recovered. There are other solutions to ensure information is protected
including several Enterprise solutions and simple drive or directory cloning.
180 | P a g e
The controls in this section are specifically about Time Machine. The general ideas are
applicable to any data backup solution. These controls are only pertinent to organizations
already using Time Machine as part of their backup solutions to ensure the included Apple
backup solution is being used effectively. We are not endorsing that Time Machine should
be used exclusively or as part of the Enterprise backup solution. The controls first check
that Time Machine is actually enabled.
• https://eclecticlight.co/tag/time-machine/
• https://www.pcmag.com/how-to/how-to-back-up-your-mac-with-time-machine
181 | P a g e
2.7.1 Ensure Backup Up Automatically is Enabled (Automated)
Profile Applicability:
• Level 2
Description:
Backup solutions are only effective if the backups run on a regular basis. The time to check
for backups is before the hard drive fails or the computer goes missing. In order to simplify
the user experience so that backups are more likely to occur Time Machine should be on
and set to Back Up Automatically whenever the target volume is available.
Operational staff should ensure that backups complete on a regular basis and the backups
are tested to ensure that file restoration from backup is possible when needed.
Backup dates are available even when the target volume is not available in the Time
Machine plist.
SnapshotDates = (
When the backup volume is connected to the computer more extensive information is
available through tmutil. See man tmutil
Rationale:
Impact:
The backup will run periodically in the background and could have user impact while
running.
182 | P a g e
Audit:
Perform the following to ensure that automatic backups are set if Time Machine is enabled:
Graphical Method:
or
Terminal Method:
Run the following command to verify that Time Machine is set to automatically backup if
Time Machine is enabled:
If Time Machine has never been used, and is not configured there will not be an
AutoBackup flag to check. If so, the machine will be in compliance.
Run the following command to check the snapshot dates to verify that the dates meet your
organization's approved backup frequency:
The output will contain all the Time Machine backups in the format "YYYY-MM-DD HH:MM:SS
+0000"
183 | P a g e
example:
{
AutoBackup = 1;
BackupAlias = {length = 270, bytes = 0x00000000 010e0002 00010654
65737454 ... 74544d00 ffff0000 };
Destinations = (
{
BackupAlias = {length = 270, bytes = 0x00000000 010e0002 00010654
65737454 ... 74544d00 ffff0000 };
BytesAvailable = 450998374400;
BytesUsed = 48765513728;
ConsistencyScanDate = "2020-08-07 12:23:26 +0000";
DestinationID = "C751EDAD-4E5F-4FA9-AF1B-AF34A00FF97F";
DestinationUUIDs = (
"24C6B473-A3C5-391F-8191-244A78D40E3C"
);
LastKnownEncryptionState = NotEncrypted;
RESULT = 0;
ReferenceLocalSnapshotDate = "2020-08-07 12:21:04 +0000";
RootVolumeUUID = "95953248-32FE-4B24-B546-91ED69B33A47";
SnapshotDates = (
"2020-08-06 19:54:13 +0000",
"2020-08-07 00:10:57 +0000",
"2020-08-07 10:45:58 +0000",
"2020-08-07 12:02:01 +0000",
"2020-08-07 12:03:00 +0000",
"2020-08-07 12:03:58 +0000",
"2020-08-07 12:06:22 +0000",
"2020-08-07 12:08:45 +0000",
"2020-08-07 12:09:42 +0000",
"2020-08-07 12:10:56 +0000",
"2020-08-07 12:11:56 +0000",
"2020-08-07 12:12:48 +0000",
"2020-08-07 12:13:41 +0000",
"2020-08-07 12:14:59 +0000",
"2020-08-07 12:16:27 +0000",
"2020-08-07 12:23:26 +0000"
);
UnencryptedBackupWarningDate = "2020-08-06 19:38:11 +0000";
}
);
HostUUIDs = (
"996981ED-1690-55E3-9486-1DD27D9E52D3"
);
184 | P a g e
LastConfigurationTraceDate = "2020-08-06 19:31:30 +0000";
LastDestinationID = "C751EDAD-4E5F-4FA9-AF1B-AF34A00FF97F";
LocalizedDiskImageVolumeName = "Time Machine Backups";
PreferencesVersion = 4;
SkipPaths = (
"~administrator/Applications",
);
SkipSystemFiles = 1;
SuspendHelperActivityTimeStamp = 618498798;
}
or
Run the following command to verify that a profile is installed that enables auto backup if
Time Machine enabled:
AutoBackup = 1;
185 | P a g e
Remediation:
Terminal Method:
Run the following command to enable automatic backups if Time Machine is enabled:
Profile Method:
<array>
<dict>
<key>mcx_preference_settings</key>
<dict>
<key>AutoBackup</key>
<true/>
</dict>
</dict>
</array>
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
186 | P a g e
2.7.2 Ensure Time Machine Volumes Are Encrypted (Automated)
Profile Applicability:
• Level 1
Description:
One of the most important security tools for data protection on macOS is FileVault. With
encryption in place it makes it difficult for an outside party to access your data if they get
physical possession of the computer. One very large weakness in data protection with
FileVault is the level of protection on backup volumes. If the internal drive is encrypted but
the external backup volume that goes home in the same laptop bag is not it is self-defeating.
Apple tries to make this mistake easily avoided by providing a checkbox to enable
encryption when setting-up a Time Machine backup. Using this option does require some
password management, particularly if a large drive is used with multiple computers. A
unique complex password to unlock the drive can be stored in keychains on multiple
systems for ease of use.
While some portable drives may contain non-sensitive data and encryption may make
interoperability with other systems difficult backup volumes should be protected just like
boot volumes.
Rationale:
187 | P a g e
Audit:
Perform the following to ensure the drive used for Time Machine is encrypted:
Graphical Method:
Terminal Method:
Run the following command to verify if the Time Machine disk encryption is enabled:
The output will be formatted as: 'Name : '. If there are more than one TimeMachine backup
disk the command will list all the disks.
Encrypted: Yes
example:
Name : TMbackup1
Name : TMbackup2
Encrypted: Yes
Encrypted: Yes
188 | P a g e
Remediation:
Note: You can set encryption through Disk Utility or diskutil in terminal.
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
189 | P a g e
2.8 Ensure Wake for Network Access Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
This feature allows the computer to take action when the user is not present and the
computer is in energy saving mode. These tools require FileVault to remain unlocked and
fully rejoin known networks. This macOS feature is meant to allow the computer to resume
activity as needed regardless of physical security controls.
This feature allows other users to be able to access your computer’s shared resources, such
as shared printers or iTunes playlists, even when your computer is in sleep mode. In a
closed network when only authorized devices could wake a computer it could be valuable
to wake computers in order to do management push activity. Where mobile workstations
and agents exist the device will more likely check in to receive updates when already
awake. Mobile devices should not be listening for signals on any unmanaged network or
where untrusted devices exist that could send wake signals.
Rationale:
Disabling this feature mitigates the risk of an attacker remotely waking the system and
gaining access.
Impact:
The control to prevent computer sleep has been retired for this version of the Benchmark.
Forcing the computer to stay on and use energy in case a management push is needed is
contrary to most current management processes. Only keep computers unslept if after
hours pushes are required on closed LANs.
190 | P a g e
Audit:
Perform the following to verify that Wake for network access or Power Nap are disabled:
Graphical Method:
Terminal Method:
Run the following command verify if Wake for network access is not enabled:
womp 0
Remediation:
Perform the following disable Wake for network access or Power Nap:
Graphical Method:
Terminal Method:
Run the following command to disable Wake for network access:
Additional Information:
man pmset
191 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
192 | P a g e
2.9 Ensure Power Nap Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
This feature allows the computer to take action when the user is not present and the
computer is in energy saving mode. These tools require FileVault to remain unlocked and
fully rejoin known networks. This macOS feature is meant to allow the computer to resume
activity as needed regardless of physical security controls.
Power Nap allows the system to stay in low power mode, especially while on battery power
and periodically connect to previously named networks with stored credentials for user
applications to phone home and get updates. This capability requires FileVault to remain
unlocked and the use of previously joined networks to be risk accepted based on the SSID
without user input.
This control has been updated to check the status on both battery and AC Power. The
presence of an electrical outlet does not completely correlate with logical and physical
security of the device or available networks.
Rationale:
Disabling this feature mitigates the risk of an attacker remotely waking the system and
gaining access.
The use of Power Nap adds to the risk of compromised physical and logical security. The
user should be able to decrypt FileVault and have the applications download what is
required when the computer is actively used.
The control to prevent computer sleep has been retired for this version of the Benchmark.
Forcing the computer to stay on and use energy in case a management push is needed is
contrary to most current management processes. Only keep computers unslept if after
hours pushes are required on closed LANs.
Impact:
Power Nap exists for unattended user application updates like email and social media
clients. With Power Nap disabled the computer will not wake and reconnect to known
wireless SSIDs intermittently when slept.
193 | P a g e
Audit:
Perform the following to verify that Wake for network access or Power Nap are disabled:
Graphical Method:
Terminal Method:
Run the following command to verify if Power Nap is not enabled:
Remediation:
Perform the following disable Wake for network access or Power Nap:
Graphical Method:
Terminal Method:
Run the following command to disable Power Nap:
Additional Information:
man pmset
194 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
195 | P a g e
2.10 Ensure Secure Keyboard Entry terminal.app is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
Secure Keyboard Entry prevents other applications on the system and/or network from
detecting and recording what is typed into Terminal.
Rationale:
Enabling Secure Keyboard Entry minimizes the risk of a key logger from detecting what is
entered in Terminal.
196 | P a g e
Audit:
Perform the following to ensure that keyboard entries are secure in Terminal:
Graphical Method:
1. Open Terminal
2. Select Terminal in the Menu Bar
3. Verify that Secure Keyboard Entry is set
or
Terminal Method:
For each user, run the following command to verify that keyboard entries in Terminal are
secured:
example:
In the above example the user seconduser is compliant, and the user firstuser is not
compliant.
or
Run the following command to verify that a profile is installed that enables secure
keyboard entry in Terminal:
SecureKeyboardEntry = 1;
197 | P a g e
Remediation:
1. Open Terminal
2. Select Terminal
3. Select Secure Keyboard Entry
Terminal Method:
example:
Profile Method:
References:
1. https://support.apple.com/en-ca/guide/terminal/trml109/2.11
198 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
199 | P a g e
2.11 Ensure EFI Version Is Valid and Checked Regularly (Automated)
Profile Applicability:
• Level 1
Description:
In order to mitigate firmware attacks Apple has created an automated Firmware check to
ensure that the EFI version running is a known good version from Apple. There is also an
automated process to check it every seven days.
Rationale:
If the Firmware of a computer has been compromised the Operating System that the
Firmware loads cannot be trusted either.
Audit:
The output should include Primary allowlist version match found. No changes
detected in primary hashes. as well as the model and version in this format
MBP133.xxx.xxxx.xxx.xxxxxxxxx.
If an Apple T2 Security Chip is present, the output will be:
ReadBinaryFromKernel: No matching services found. Either this system is not
supported by eficheck, or you need to re-load the kext IntegrityCheck:
couldn't get EFI contents from kext
Run this command to verify that the machine does have an Apple T2 Security Chip:
Result: - 0 com.apple.driver.eficheck
200 | P a g e
Remediation:
If EFI does not pass the integrity check you may send a report to Apple. Backing up files and
clean installing a known good Operating System and Firmware is recommended.
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
201 | P a g e
2.12 Audit Automatic Actions for Optical Media (Manual)
Profile Applicability:
• Level 1
Description:
Managing automatic actions, while useful in very few situations, is unlikely to increase
security on the computer and does complicate the user experience and add additional
complexity to the configuration. These settings are user controlled and can be changed
without Administrator privileges unless controlled through MCX settings or Parental
Controls. Unlike Windows, the Auto-run the optical media is accessed through Operating
System applications. Those same applications can open and access the media directly. If
optical media is not allowed in the environment the optical media drive should be disabled
in hardware and software.
Rationale:
Setting automatic actions for optical media can mitigate malicious code from running
automatically when optical media is inserted.
202 | P a g e
Audit:
Terminal Method:
For all users, run the following commands to verify the optical media actions:
{
"com.apple.digihub.blank.cd.appeared" = {
action = 1;
};
"com.apple.digihub.blank.dvd.appeared" = {
action = 100;
};
"com.apple.digihub.cd.music.appeared" = {
action = 101;
};
"com.apple.digihub.cd.picture.appeared" = {
action = 107;
};
"com.apple.digihub.dvd.video.appeared" = {
action = 105;
};
}
203 | P a g e
Remediation:
Terminal Method:
Run the following command to set the optical media action:
example:
204 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
205 | P a g e
2.13 Audit Siri Settings (Manual)
Profile Applicability:
• Level 1
Description:
With macOS 10.12 Sierra Apple has introduced Siri from iOS to macOS. While there are data
spillage concerns with the use of data gathering personal assistant software, the risk here
does not seem greater in sending queries to Apple through Siri than in sending search
terms in a browser to Google or Microsoft. While it is possible that Siri will be used for local
actions rather than Internet searches, Siri could, in theory, tell Apple about confidential
Programs and Projects that should not be revealed. This appears be a usage edge case.
In cases where sensitive and protected data is processed and Siri could help a user navigate
their machine and expose that information it should be disabled. Siri does need to phone
home to Apple so it should not be available from air-gapped networks as part of its
requirements.
Most of the use case data published has shown that Siri is a tremendous time saver on iOS
where multiple screens and menus need to be navigated through. Information like sports
scores, weather, movie times and simple to-do items on existing calendars can be easily
found with Siri. None of the standard use cases should be more risky than already
approved activity.
Rationale:
Where "normal" user activity is already limited, Siri use should be controlled as well.
206 | P a g e
Audit:
or
Terminal Method:
Run the following commands to verify the Siri settings:
The output will be either 0, disabled, or 1 for the following Siri options:
207 | P a g e
example:
{
LockscreenEnabled = 0;
StatusMenuVisible = 0;
VoiceTriggerUserEnabled = 0;
}
{
LockscreenEnabled = 0;
StatusMenuVisible = 1;
VoiceTriggerUserEnabled = 1;
}
{
LockscreenEnabled = 1;
StatusMenuVisible = 0;
VoiceTriggerUserEnabled = 1;
}
or
Run the following command to verify that a profile is installed that sets Siri to your
organization's setting:
allowAssistant = 0;
Note: Siri can only be enabled or disabled through configuration profiles. Any additional
settings need to be set through the GUI of CLI
208 | P a g e
Remediation:
Terminal Method:
Run the following commands to enable or disable Siri settings:
After running the default writes, the Windows Server needs to be restarted and the caches
cleared. Run the following commands to perform that action:
209 | P a g e
example:
Profile Method:
Note: Siri can only be enabled or disabled through configuration profiles. Any additional
settings need to be set through the GUI of CLI
References:
1. https://support.apple.com/en-us/HT210657
210 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
211 | P a g e
2.14 Audit Sidecar Settings (Manual)
Profile Applicability:
• Level 1
Description:
Apple introduced a technology called Sidecar with the release of mac OS 10.15 "Catalina"
that allows the use of an Apple iPad as an additional screen. There are no known security
issues with the use of Sidecar at the time of the publication of this Benchmark. There are
security concerns with some of the underlying technology that allows this feature to work.
The Apple support article below has the additional requirements that are reproduced
below. So while Sidecar may not have an explicit security concern some organizations may
have requirements that block the use of the features required to allow Sidecar to work.
https://support.apple.com/en-afri/HT210380
Additional requirements
• Both devices must be signed in to iCloud with the same Apple ID using two-factor
authentication.
• To use Sidecar wirelessly, both devices must be within 10 meters (30 feet) of each
other and have Bluetooth, Wi-Fi, and Handoff turned on. Also make sure that the
iPad is not sharing its cellular connection and the Mac is not sharing its Internet
connection.
• To use Sidecar over USB, make sure that your iPad is set to trust your Mac.
Organizations that do not allow the use of iCloud and more specifically Handoff will not be
able to use Sidecar.
Some organizations may not allow the use of mixed ownership for P2P wireless or USB
connections so that unless the organization controls both the Mac and the iPad connections
may not be approved and the use of a single Apple ID for distinctly managed devices may
be prohibited.
Rationale:
212 | P a g e
Audit:
or
Terminal Method:
Run the following commands to verify if Sidecar is enabled:
213 | P a g e
Remediation:
Terminal Method:
Run the following to enable or disable Sidecar settings:
Profile Method:
<dict>
<key>Forced</key>
<array>
<dict>
<key>mcx_preference_settings</key>
<dict>
<key>AllowAllDevices</key>
<<true/false>/>
<key>hasShownPref</key>
<<true/false>/>
</dict>
</dict>
</array>
</dict>
Note: Using the Terminal and Profile Methods will not display in System Preferences, but
will disable the underlying service.
References:
1. https://www.apple.com/macos/catalina/docs/Sidecar_Tech_Brief_Oct_2019.pdf
2. https://www.pocket-lint.com/laptops/news/apple/148262-apple-sidecar-macos-
ipados-features-explained
214 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
215 | P a g e
2.15 Audit Touch ID and Wallet & Apple Pay Settings (Manual)
Profile Applicability:
• Level 1
Description:
Apple has integrated Touch ID with macOS and allows fingerprint use for many common
operations. All use of Touch ID requires the presence of a password and the use of that
password after every reboot or where it has been more than 48 hours since the device was
last unlocked.
Touch ID is a pre-requisite for using Apple Pay and Wallet on macOS. Apple Pay allows an
Apple account holder to enroll their credit cards in Apple Pay and pay enrolled vendors
without using the physical card or number. Apple's service eliminates the requirement to
send the credit card number itself to the vendor. Apple Pay on a Mac allows the use of
credit cards the user has already enrolled and reduces user risk for credit card purchases.
Rationale:
Touch ID allows for an account enrolled fingerprint to access a key that uses a previously
provided password.
Some environments may have rules around purchases from organizationally managed
computers and may want to discourage shopping from them. It is difficult to block access to
websites that allow purchases and Apple Pay has additional controls for user protection
than the manually entry of credit card information
Impact:
Touch ID is more convenient for use with aggressive screen lock controls.
Audit:
216 | P a g e
Remediation:
References:
1. https://support.apple.com/guide/mac-help/use-wallet-apple-pay-on-mac-
mchl4773988b/mac
2. https://www.apple.com/apple-pay/
3. https://support.apple.com/guide/mac-help/touch-id-mchl16fbf90a/mac
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
217 | P a g e
2.16 Audit Notification System Preference Settings (Manual)
Profile Applicability:
• Level 1
Description:
Notification capabilities are designed to allow users to receive updates from applications
that are not currently in use, these can be background applications or even notices from
processes running on a computer that is not currently being actively used. Where the
screen of a computer is visible to others other than the logged-in user due to shared
working spaces or public spaces consideration should be made on the exposure of sensitive
data in notifications. Applications that use the system-wide application service may be
individually managed and applications that might expose confidential information to
unauthorized users should not expose notifications except to the current user, especially on
the locked screen when the computer may be unattended.
Rationale:
Impact:
Computer users are often juggling too much information through too many applications
that want their attention and are often designed to get attention and not ever let it go.
Notifications are a mechanism that can be used to cut through the deluge and allow
important issues to be resolved in a timely way. Global controls on limiting user
notifications, even for certain applications, could impact productivity and the timely
remediation of issues.
218 | P a g e
Audit:
Perform the following to verify that Notifications are set to your organization's
requirements:
Graphical Method:
Note: If the exposure of controlled information or data leakage is possible with application
notifications the acceptable notification level should be established through a risk analysis
of what unauthorized leaks may occur.
Remediation:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
219 | P a g e
2.17 Audit Passwords System Preference Setting (Manual)
Profile Applicability:
• Level 1
Description:
Apple has provided a new interface in macOS Monterey for managing passwords that
mirrors the interfaced capability already available in iOS. Password management in macOS
was previously available in both Safari Preferences and in Keychain Access. Apple is
attempting to simplify password management for macOS and make the user experience
more similar to iOS. Organizations are justifiably concerned about the risk of password
managers, particularly as a possible backdoor to improved credential management regimes
and greater use of Multi-Favor-Authentication (MFA).
Rationale:
Organizations should remove what passwords can be saved on user computes and the
ability of attackers rot potentially steal organizational credentials. Limits on password
storage must be evaluated based on both user risk and Enterprise risk.
Impact:
Audit:
220 | P a g e
Remediation:
Perform the following to set Password system settings to your organization's settings:
Graphical Method:
References:
1. https://support.apple.com/guide/security/password-monitoring-
sec78e79fc3b/1/web/1
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
221 | P a g e
3 Logging and Auditing
This section provide guidance on configuring the logging and auditing facilities available in
macOS. Starting with macOS 10.12 Apple introduced unified logging. This capability
replaces the previous logging methodology with centralized system wide common controls.
A full explanation of macOS logging behavior is beyond the scope of this Benchmark. These
changes impact previous logging controls from macOS Benchmarks. At this point many of
the syslog controls have been or are being removed since the old logging methods have
been deprecated. Controls that still appear useful will be retained. Some legacy controls
have been removed for this release.
222 | P a g e
3.1 Ensure Security Auditing Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
macOS's audit facility, auditd, receives notifications from the kernel when certain system
calls, such as open, fork, and exit, are made. These notifications are captured and written
to an audit log.
Rationale:
Logs generated by auditd may be useful when investigating a security incident as they may
help reveal the vulnerable application and the actions taken by a malicious actor.
Audit:
- 0 com.apple.auditd
Remediation:
223 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
224 | P a g e
3.2 Ensure Security Auditing Flags Are Configured Per Local
Organizational Requirements (Automated)
Profile Applicability:
• Level 2
Description:
Rationale:
Maintaining an audit trail of system activity logs can help identify configuration errors,
troubleshoot service disruptions, and analyze compromises or attacks that have occurred,
have begun, or are about to begin. Audit logs are necessary to provide a trail of evidence in
case the system or network is compromised.
Depending on the governing authority, organizations can have vastly different auditing
requirements. In this control we have selected a minimal set of audit flags that should be a
part of any organizational requirements. The flags selected below may not adequately meet
organizational requirements for users of this benchmark. The auditing checks for the flags
proposed here will not impact additional flags that are selected.
225 | P a g e
Audit:
The -all flag will capture all failed events across all audit classes and can be used to
supersede the individual flags for failed events.
Note: excluding potentially noisy audit events may be ideal, depending on your use-case.
Remediation:
References:
1. https://derflounder.wordpress.com/2012/01/30/openbsm-auditing-on-mac-os-x/
2. https://csrc.nist.gov/CSRC/media/Publications/sp/800-179/rev-
1/draft/documents/sp800-179r1-draft.pdf
3. https://meliot.me/2017/07/02/mac-os-real-time-auditing/
4. https://www.scip.ch/en/?labs.20150108
5. https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-171r2.pdf
6. https://www.whitehouse.gov/wp-content/uploads/2021/08/M-21-31-Improving-
the-Federal-Governments-Investigative-and-Remediation-Capabilities-Related-to-
Cybersecurity-Incidents.pdf
Additional Information:
Flag settings are currently based on the guidance provided by the NIST through the macOS
Security guidance they are providing in there GitHub repository. You can find that guidance
here.
226 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
227 | P a g e
3.3 Ensure install.log Is Retained for 365 or More Days and No
Maximum Size (Automated)
Profile Applicability:
• Level 1
Description:
The default value has an "all_max" file limitation, no reference to a minimum retention and
a less precise rotation argument.
The all_max flag control will remove old log entries based only on the size of the log files.
Log size can vary widely depending on how verbose installing applications are in their log
entries. The decision here is to ensure that logs go back a year and depending on the
applications a size restriction could compromise the ability to store a full year.
While this Benchmark is not scoring for a rotation flag the default rotation is sequential
rather than using a timestamp. Auditors may prefer timestamps in order to simply review
specific dates where event information is desired.
Please review the File Rotation section in the man page for more information.
man asl.conf
Rationale:
Archiving and retaining install.log for at least a year is beneficial in the event of an
incident as it will allow the user to view the various changes to the system along with the
date and time they occurred.
228 | P a g e
Impact:
Without log files system maintenance and security forensics cannot be properly performed.
Audit:
Perform the following to ensure that the install logs are retained for at least 365 days with
no maximum size:
Run the following command to verify how long install log files are retained and if there is a
maximum size:
Remediation:
Perform the following to ensure that install logs are retained for at least 365 days:
Edit the /etc/asl/com.apple.install file and add or modify the ttl value to 365 or
greater on the file line. Also, remove the all_max= setting and value from the file line.
229 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
230 | P a g e
3.4 Ensure Security Auditing Retention Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
Retention can be set to respect both size and longevity. To retain as much as possible under
a certain size the recommendation is to use the following:
expire-after:60d OR 1G
Rationale:
Impact:
The recommendation is that at least 60 days or 1 gigabyte of audit records are retained.
Systems that have very little remaining disk space may have issues retaining sufficient
data.
Audit:
Remediation:
231 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
232 | P a g e
3.5 Ensure Access to Audit Records Is Controlled (Automated)
Profile Applicability:
• Level 1
Description:
The audit system on macOS writes important operational and security information that can
be both useful for an attacker and a place for an attacker to attempt to obfuscate unwanted
changes that were recorded. As part of defense-in-depth the /etc/security/audit_control
configuration and the files in /var/audit should be owned only by root with group wheel
with read-only rights and no other access allowed. macOS ACLs should not be used for
these files.
Rationale:
Audit records should never be changed except by the system daemon posting events.
Records may be viewed or extracts manipulated, but the authoritative files should be
protected from unauthorized changes.
Impact:
This control is only checking the default configuration to ensure that unwanted access to
audit records is not available.
233 | P a g e
Audit:
The output should include the owner is root and the group is wheel or root and should not
be readable or writable by Other. Ex: -r--r----- not -r--r--r-- or -r--r---w-
The output should include the owner is root and the group is wheel or root and all entries
should not be readable or writable by Other (excluding the final current line). Ex: -r--r---
-- not -r--r--r-- or -r--r---w-
example:
Remediation:
Run the following to commands to set the audit records to the root user and wheel group:
Note: It is recommended to do a thorough verification process on why the audit logs have
been changed before following the remediation steps. If the system has different access
controls on the audit logs, and the changes cannot be traced, a new install may be prudent.
Check for signs of file tampering as well as unapproved OS changes.
234 | P a g e
Additional Information:
-e Print the Access Control List (ACL) associated with the file, if
More info:
https://www.techrepublic.com/blog/apple-in-the-enterprise/introduction-to-os-x-access-
control-lists-acls/
http://ahaack.net/technology/OS-X-Access-Control-Lists-ACL.html
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
235 | P a g e
3.6 Ensure Firewall Logging Is Enabled and Configured (Automated)
Profile Applicability:
• Level 1
Description:
The socketfilter firewall is what is used when the firewall is turned on in the Security
Preference Pane. In order to appropriately monitor what access is allowed and denied
logging must be enabled. The logging level must be set to "detailed" to be useful in
monitoring connection attempts that the firewall detects. Throttled login is not sufficient
for examine firewall connection attempts.
Rationale:
In order to troubleshoot the successes and failures of a firewall, detailed logging should be
enabled.
Impact:
236 | P a g e
Audit:
Terminal Method:
Run the following command to verify that the firewall log is enabled:
or
Run the following command to verify that a profile is installed that enables Firewall
Logging:
EnableLogging = 1;
LoggingOption = detail;
237 | P a g e
Remediation:
Profile Method:
Note: Firewall Logging must be enabled with this profile. It can either be set with the
Firewall and Stealth Mode (2.5.2.2 and 2.5.2.3) or as a separate profile. Setting logging with
its own profile will not cause a conflict.
Additional Information:
238 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
239 | P a g e
3.7 Audit Software Inventory (Manual)
Profile Applicability:
• Level 2
Description:
With the introduction of Mac OS X 10.6.6, Apple added a new application, App Store, which
resides in the Applications directory. This application allows a user with admin privileges
and an Apple ID to browse Apple's online App Store, purchase (including no cost
purchases), and install new applications, bypassing Enterprise software inventory controls.
Any admin user can install software in the /Applications directory whether from internet
downloads, thumb drives, optical media, cloud storage or even binaries through email.
Even standard users can run executables downloaded to their home folder by default. The
source of the software is not nearly as important as a consistent audit of all installed
software for patch compliance and appropriateness.
A single user desktop where the user, administrator and the person approving software are
all the same person probably does not need to audit software inventory to this extent. It is
helpful in the case of stability problems or malware however.
Scan systems on a monthly basis and determine the number of unauthorized pieces of
software that are installed. Verify that if an unauthorized piece of software is found one
month, it is removed from the system the next.
Export System Information through the built-in System Information Application or other
third-party tools on an organizationally defined timetable.
Rationale:
Part of comprehensive IT security involves device management and ensuring that all
software is authorized and patched. Checking for macOS updates and app updates are
relatively simple for the end user and can even be updated with minimal privileges from
trusted sources if enabled. Remote monitoring of the patch status for software maintained
through Apple is very well supported by management applications. Neither Apple
capabilities nor third-party patch management solutions will cover all mission necessary
software for most organizations. Full visibility into software present on the system enables
vulnerability and risk management.
240 | P a g e
Audit:
Perform the following to access System Information through the GUI or the command line:
Graphical Mode:
Terminal Method:
Run the following command to view all System Profiler details
$ sudo system_profiler
To find more detailed instructions on the use of the system_profiler command, run the
following:
Remediation:
Additional Information:
241 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
242 | P a g e
4 Network Configurations
This section contains guidance on configuring the networking-related aspects of macOS.
243 | P a g e
4.1 Ensure Bonjour Advertising Services Is Disabled (Automated)
Profile Applicability:
• Level 2
Description:
Bonjour is an auto-discovery mechanism for TCP/IP devices which enumerate devices and
services within a local subnet. DNS on macOS is integrated with Bonjour and should not be
turned off, but the Bonjour advertising service can be disabled.
Rationale:
Bonjour can simplify device discovery from an internal rogue or compromised host. An
attacker could use Bonjour's multicast DNS feature to discover a vulnerable or poorly-
configured service or additional information to aid a targeted attack. Implementing this
control disables the continuous broadcasting of "I'm here!" messages. Typical end-user
endpoints should not have to advertise services to other computers. This setting does not
stop the computer from sending out service discovery messages when looking for services
on an internal subnet, if the computer is looking for a printer or server and using service
discovery. To block all Bonjour traffic except to approved devices the pf or other firewall
would be needed.
Impact:
Some applications, like Final Cut Studio and AirPort Base Station management, may not
operate properly if the mDNSResponder is turned off.
244 | P a g e
Audit:
Terminal Method:
Run the following command to verify that Bonjour Advertising is not enabled:
Note: If the settings has not been changed from the default, then this audit will fail on the
command line. Follow the remediation instructions to verify that it is set to a disabled
status.
or
Run the following command to verify that a profile is installed that disables Bonjour
Advertising:
NoMulticastAdvertisements = 1;
Remediation:
Profile Method:
245 | P a g e
Additional Information:
Anything Bonjour discovers is already available on the network and probably discoverable
with network scanning tools. The security benefit of disabling Bonjour for that reason is
minimal.
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
246 | P a g e
4.2 Ensure Show Wi-Fi status in Menu Bar Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
The Wi-Fi status in the menu bar indicates if the system's wireless internet capabilities are
enabled. If so, the system will scan for available wireless networks to connect to. At the
time of this revision all computers Apple builds have wireless network capability, which
has not always been the case. This control only pertains to systems that have a wireless NIC
available. Operating systems running in a virtual environment may not score as expected
either.
Rationale:
Enabling "Show Wi-Fi status in menu bar" is a security awareness method that helps
mitigate public area wireless exploits by making the user aware of their wireless
connectivity status.
Impact:
The user of the system should have a quick check on their wireless network status
available.
247 | P a g e
Audit:
Perform the following to verify that the Wi-Fi status shows in the menu bar:
Graphical Method:
or
Terminal Method:
For each user, run the following command to verify that Wi-Fi status is enabled in the menu
bar:
18
Note: If the settings has not been changed from the default, then this audit will fail on the
command line. Follow the remediation instructions to verify that it is set to a disabled
status.
example:
18
or
Run the following command to verify that a profile is installed that enables Bluetooth to be
shown in the menu bar:
WiFi = 18;
248 | P a g e
Remediation:
Terminal Method:
For each user, run the following to turn the Wi-Fi status on in the menu bar
example:
Profile Method:
Additional Information:
AirPort is Apple’s marketing name for its 802.11b, g, and n wireless interfaces.
249 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
250 | P a g e
4.3 Audit Network Specific Locations (Manual)
Profile Applicability:
• Level 2
Description:
The network location feature of the Mac is a very powerful tool to manage network
security. By creating different network locations, a user can easily (and without
administrative privileges) change the network settings on the Mac. By only using the
network interfaces needed at any specific time, exposure to network attacks is limited.
A little understanding of how the Network System Preferences pane works is required.
Rationale:
Network locations allow the computer to have specific configurations ready for network
access when required. Locations can be used to manage which network interfaces are
available for specialized network access.
Impact:
Unneeded network interfaces increase the attack surface and could lead to a successful
exploit.
Audit:
Perform the following to verify that all network locations meet your organization's
requirements:
251 | P a g e
Remediation:
Perform the following actions to create and edit multiple network locations as needed:
Note: Delete the Automatic location for any device that does not use multiple network
services set for DHCP or dynamic addressing. If network services like FireWire, VPN,
AirPort or Ethernet are not used by a specific device class those services should be deleted.
Additional Information:
252 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
253 | P a g e
4.4 Ensure HTTP Server Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
macOS used to have a graphical front-end to the embedded Apache web server in the
Operating System. Personal web sharing could be enabled to allow someone on another
computer to download files or information from the user's computer. Personal web sharing
from a user endpoint has long been considered questionable, and Apple has removed that
capability from the GUI. Apache however is still part of the Operating System and can be
easily turned on to share files and provide remote connectivity to an end-user computer.
Web sharing should only be done through hardened web servers and appropriate cloud
services.
Rationale:
Web serving should not be done from a user desktop. Dedicated webservers or appropriate
cloud storage should be used. Open ports make it easier to exploit the computer.
Impact:
The web server is both a point of attack for the system and a means for unauthorized file
transfers.
Audit:
Run the following command to verify that the http server services are not currently
enabled. This check does not reflect any auto-start settings, only whether the web server is
currently enabled:
Note: If the setting has not been changed from the default, then this audit will fail on the
command line. Follow the remediation instructions to verify that it is set to a disabled
status.
254 | P a g e
Remediation:
References:
1. STIGID AOSX-12-001275
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
255 | P a g e
4.5 Ensure NFS Server Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
macOS can act as an NFS fileserver. NFS sharing could be enabled to allow someone on
another computer to mount shares and gain access to information from the user's
computer. File sharing from a user endpoint has long been considered questionable, and
Apple has removed that capability from the GUI. NFSD is still part of the Operating System
and can be easily turned on to export shares and provide remote connectivity to an end-
user computer.
Rationale:
File serving should not be done from a user desktop. Dedicated servers should be used.
Open ports make it easier to exploit the computer.
Impact:
The nfs server is both a point of attack for the system and a means for unauthorized file
transfers.
Audit:
Run the following commands to verify that the NFS fileserver service is not enabled:
Note: If the setting has not been changed from the default, then this audit will fail on the
command line. Follow the remediation instructions to verify that it is set to a disabled
status.
256 | P a g e
Remediation:
$ sudo rm /etc/exports
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
257 | P a g e
4.6 Audit Wi-Fi Settings (Manual)
Profile Applicability:
• Level 2
Description:
Some organizations have comprehensive rules that cover the use of wireless technologies
in order to implement operational security. There are specific policies governing the use of
both Bluetooth and Wi-Fi (802.11) that often include disabling the wireless capability in
either software or hardware or both.
Wireless access is part of the feature set required for mobile computers and is considered
essential for most users.
Rationale:
The general use case for macOS is to use wireless connectivity. In the current hardware
offering very few computers made by Apple provide a built-in wired network capability.
While it is possible to get an ethernet adapter for wired connectivity it is not the default.
The almost exclusive Apple use case is to support mobile connectivity for users of their
devices through wireless connections. For use cases that wireless connectivity is not
allowed an Apple model with built-in ethernet is the best option. Wireless can be turned off
in those situations in the network system preference pane.
258 | P a g e
Audit:
Terminal Method:
Run the following commands to verify the Airport settings:
The output will include Device: and the network device number. ex: Device: en0
Wireless disabled:
259 | P a g e
Remediation:
Terminal Method:
Run the following command to set Airport to the correct status:
Example:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
260 | P a g e
5 System Access, Authentication and Authorization
The controls in this section are a combination of hardening controls that are not specifically
in a System Preference pane. Many of these controls are only accessible using the
Command Line or a Device Profile and not available in the Graphical User Interface. The
Benchmaerk does contain simple, easy to follow instructions for technical staff to audit and
implement recommended controls.
261 | P a g e
5.1 File System Permissions and Access Controls
File system permissions have always been part of computer security. There are several
principles that are part of best practices for a POSIX-based system that are contained in this
section. This section does not contain a complete list of every permission on a macOS
System that might be problematic. Developers and use cases differ and what some admins
long in the profession might consider a travesty a risk assessor steeped in BYOD trends
may not give a second glance at. We are documenting here controls that should point out
truly bad practices or anomalies that should be looked at and considered closely. Many of
the controls are to mitigate the risk of privilege escalation attacks and data exposure to
unauthorized parties.
262 | P a g e
5.1.1 Ensure Home Folders Are Secure (Automated)
Profile Applicability:
• Level 1
Description:
By default, macOS allows all valid users into the top level of every other user's home folder
and restricts access to the Apple default folders within. Another user on the same system
can see you have a "Documents" folder but cannot see inside it. This configuration does
work for personal file sharing but can expose user files to standard accounts on the system.
The best parallel for Enterprise environments is that everyone who has a Dropbox account
can see everything that is at the top level but can't see your pictures. Similarly with macOS,
users can see into every new Directory that is created because of the default permissions.
Home folders should be restricted to access only by the user. Sharing should be used on
dedicated servers or cloud instances that are managing access controls. Some
environments may encounter problems if execute rights are removed as well as read and
write. Either no access or execute only for group or others is acceptable.
Rationale:
Allowing all users to view the top level of all networked users' home folder may not be
desirable since it may lead to the revelation of sensitive information.
Impact:
If implemented, users will not be able to use the "Public" folders in other users' home
folders. "Public" folders with appropriate permissions would need to be set up in the
/Shared folder.
263 | P a g e
Audit:
Run the following command to ensure that all home folders are secure:
The output for each home folder should be either drwx------ or drwx--x--x
example:
total 0
drwxr-xr-x+ 12 Guest _guest 384 24 Jul 13:42 Guest
drwxrwxrwt 4 root wheel 128 22 Jul 11:00 Shared
drwx--x--x+ 18 firstuser staff 576 10 Aug 14:36 firstuser
drwx--x--x+ 15 seconduser staff 480 10 Aug 09:16 seconduser
drwxrwxrwx+ 11 thirduser staff 352 10 Aug 14:53 thirduser
drwxrw-rw-+ 11 fourthuser staff 352 10 Aug 14:53 fourthuser
Remediation:
For each user, run the following command to secure all home folders:
Alternately, run the following command if there needs to be executable access for a home
folder:
example:
# /bin/ls -l /Users/
total 0
drwxr-xr-x+ 12 Guest _guest 384 24 Jul 13:42 Guest
drwxrwxrwt 4 root wheel 128 22 Jul 11:00 Shared
drwx--x--x+ 18 firstuser staff 576 10 Aug 14:36 firstuser
drwx--x--x+ 15 seconduser staff 480 10 Aug 09:16 seconduser
drwx--x--x+ 11 thirduser staff 352 10 Aug 14:53 thirduser
drwx------+ 11 fourthuser staff 352 10 Aug 14:53 fourthuser
264 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
265 | P a g e
5.1.2 Ensure System Integrity Protection Status (SIPS) Is Enabled
(Automated)
Profile Applicability:
• Level 1
Description:
Rationale:
Running without System Integrity Protection on a production system runs the risk of the
modification of system binaries or code injection of system processes that would otherwise
be protected by SIP.
Impact:
Audit:
Run the following command to verify that System Integrity Protection is enabled:
266 | P a g e
Remediation:
1. Reboot into the Recovery Partition (reboot and hold down Command (⌘) + R)
2. Select Utilities
3. Select Terminal
4. Run the following command:
Note: You cannot enable System Integrity Protection from the booted operating system. If
the remediation is attempted in the booted OS and not the Recovery Partition the output
will give the error csrutil: failed to modify system integrity configuration. This
tool needs to be executed from the Recovery OS.
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
267 | P a g e
5.1.3 Ensure Apple Mobile File Integrity Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
Apple Mobile File Integrity was first released in macOS 10.12, the daemon and service
block attempts to run unsigned code. AMFI uses lanchd, code signatures, certificates,
entitlements, and provisioning profiles to create a filtered entitlement dictionary for an
app. AMFI is the macOS kernel module that enforces code-signing and library validation.
Rationale:
Apple Mobile File Integrity (AMFI) validates that application code is validated.
Impact:
Audit:
Run the following command to verify that Apple Mobile File Integrity is enabled:
Remediation:
Run the following command to enable the Apple Mobile File Integrity service:
References:
1. https://eclecticlight.co/2018/12/29/amfi-checking-file-integrity-on-your-mac/
2. https://github.com/usnistgov/macos_security/issues/39
3. https://github.com/usnistgov/macos_security/issues/40
4. https://www.naut.ca/blog/2020/11/13/forbidden-commands-to-liberate-macos/
268 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
269 | P a g e
5.1.4 Ensure Library Validation Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
Rationale:
Running without Library Validation on a production system runs the risk of the
modification of system binaries or code injection of system processes that would otherwise
be protected by Library Validation.
Impact:
270 | P a g e
Audit:
Terminal Method:
Run the following command to verify that library validation is set:
Note: If the settings has not been changed from the default, then this audit will fail on the
command line. Follow the remediation instructions to verify that it is set to a disabled
status.
or
Run the following command to verify that a profile is installed that enables library
validation:
DisableLibraryValidation = 0;
271 | P a g e
Remediation:
Profile Method:
<array>
<dict>
<key>mcx_preference_settings</key>
<dict>
<key>DisableLibraryValidation</key>
<false/>
</dict>
</dict>
</array>
References:
1. https://github.com/Automattic/wp-desktop/issues/790
2. https://www.naut.ca/blog/2020/11/13/forbidden-commands-to-liberate-macos/
3. http://www.newosxbook.com/articles/CodeSigning.pdf
272 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
273 | P a g e
5.1.5 Ensure Sealed System Volume (SSV) Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
Sealed System Volume is a security feature introduced in macOS 11.0 Big Sur.
During system installation, a SHA-256 cryptographic hash is calculated for all immutable
system files and stored in a Merkle tree which itself is hashed as the Seal. Both are stored in
the metadata of the snapshot created of the System volume.
The seal is verified by the boot loader at startup. macOS will not boot if system files have
been tampered with. If validation fails, the user will be instructed to reinstall the operating
system.
During read operations for files located in the Sealed System Volume, a hash is calculated
and compared to the value stored in the Merkle tree.
Rationale:
Running without Sealed System Volume on a production system could run the risk of Apple
software, that integrates directly with macOS, being modified.
Impact:
Apple Software that integrates with the operating system could become compromised.
Audit:
Run the following command to verify that Sealed System Volume is enabled:
274 | P a g e
Remediation:
1. Reboot into the Recovery Partition (reboot and hold down Command (⌘) + R)
2. Select an administrator's account and enter that account's password
3. Select Utilities
4. Select Terminal
5. Run the following command:
Note: You cannot enable Sealed System Volume from the booted operating system. If the
remediation is attempted in the booted OS and not the Recovery Partition the output will
give the error csrutil: This tool needs to be executed from Recovery OS.
References:
1. https://developer.apple.com/news/?id=3xpv8r2m
2. https://eclecticlight.co/2020/11/30/is-big-surs-system-volume-sealed/
3. https://eclecticlight.co/2020/06/25/big-surs-signed-system-volume-added-
security-protection/
275 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
276 | P a g e
5.1.6 Ensure Appropriate Permissions Are Enabled for System Wide
Applications (Automated)
Profile Applicability:
• Level 1
Description:
Rationale:
Impact:
Audit:
Run the following command to verify that all applications have the correct permissions:
277 | P a g e
Remediation:
Run the following command to change the permissions for each application that does not
meet the requirements:
example:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
278 | P a g e
5.1.7 Ensure No World Writable Files Exist in the System Folder
(Automated)
Profile Applicability:
• Level 1
Description:
Rationale:
Audit:
Run the following command to check for directories in the /System folder that are world-
writable:
Remediation:
Run the following command to set permissions so that folders are not world-writable in the
/System folder:
example:
279 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
280 | P a g e
5.1.8 Ensure No World Writable Files Exist in the Library Folder
(Automated)
Profile Applicability:
• Level 2
Description:
Software sometimes insists on being installed in the /Library Directory and have
inappropriate world-writable permissions.
Rationale:
Audit:
example:
Remediation:
Run the following command to set permissions so that folders are not world-writable in the
/System/Volumes/Data/Library folder:
example:
281 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
282 | P a g e
5.2 Password Management
Password security is an important part of general IT security where passwords are in use.
For macOS passwords are still much more widely used than other methods for account
access. While there are other authentication and authorization methods for access from a
macOS computer to organizational services, console access to the Mac is probably done
using a password. This section contains password controls.
Length, threshold, and a yearly rotation requirement are the only scored controls below.
Other controls will remain as unscored options. Passwords used for macOS are likely to
also function as encryption keys for FileVault. Depending on the information confidentiality
on FileVault volumes, stronger passwords may be required than are necessary to pass the
controls in this Benchmark.
Apple supported solutions for managing local passwords on macOS are to use either an
XML file that contains password rules that are imported with pwpolicy or through the use
of a profile. In either case, the controls in this section can be implemented with an
organizationally-approved password policy.
https://pages.nist.gov/800-63-3/sp800-63b.html
283 | P a g e
5.2.1 Ensure Password Account Lockout Threshold Is Configured
(Automated)
Profile Applicability:
• Level 1
Description:
The account lockout threshold specifies the amount of times a user can enter an incorrect
password before a lockout will occur.
Ensure that a lockout threshold is part of the password policy on the computer.
Rationale:
The account lockout feature mitigates brute-force password attacks on the system.
Impact:
The number of incorrect log on attempts should be reasonably small to minimize the
possibility of a successful password attack, while allowing for honest errors made during a
normal user log on.
The locked account will auto-unlock after a few minutes when bad password attempts stop.
The computer will accept the still-valid password if remembered or recovered.
284 | P a g e
Audit:
Perform the following to ensure that the Password Account Threshold is set to less than or
equal to 5:
Graphical Method:
Terminal Method:
Run the following command to verify that the number of failed attempts is less than or
equal to 5:
285 | P a g e
Remediation:
Perform the following to enable Password Account Thresholds to less than or equal to 5:
Terminal Method:
Run the following command to set the maximum number of failed login attempts to less
than or equal to 5:
example:
Profile Method:
References:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
286 | P a g e
5.2.2 Ensure Password Minimum Length Is Configured (Automated)
Profile Applicability:
• Level 1
Description:
A minimum password length is the fewest number of characters a password can contain to
meet a system's requirements.
Ensure that a minimum of a 15-character password is part of the password policy on the
computer.
Rationale:
Information systems that are not protected with strong password schemes including
passwords of minimum length provide a greater opportunity for attackers to crack the
password and gain access to the system.
Impact:
287 | P a g e
Audit:
Perform the following to ensure that the Password Account Threshold is set to greater than
or equal to 15:
Graphical Method:
Terminal Method:
Run the following command to verify that the password length is greater than or equal to
15:
288 | P a g e
Remediation:
example:
Profile Method:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
289 | P a g e
5.2.3 Ensure Complex Password Must Contain Alphabetic Characters Is
Configured (Manual)
Profile Applicability:
• Level 2
Description:
Complex passwords contain one character from each of the following classes: English
uppercase letters, English lowercase letters, Westernized Arabic numerals, and non-
alphanumeric characters.
Ensure that an Alphabetic character is part of the password policy on the computer
Rationale:
The more complex a password the more resistant it will be against persons seeking
unauthorized access to a system.
Impact:
Password policy should be in effect to reduce the risk of exposed services being
compromised easily through dictionary attacks or other social engineering attempts.
290 | P a g e
Audit:
Perform the following to ensure that the passwords must contain at least 1 alphabetic
characters:
Graphical Method:
Terminal Method:
Run the following command to verify that the password requires at least one letter:
291 | P a g e
Remediation:
example:
Profile Method:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
292 | P a g e
5.2.4 Ensure Complex Password Must Contain Numeric Character Is
Configured (Manual)
Profile Applicability:
• Level 2
Description:
Complex passwords contain one character from each of the following classes: English
uppercase letters, English lowercase letters, Westernized Arabic numerals, and non-
alphanumeric characters.
Ensure that a number or numeric value is part of the password policy on the computer.
Rationale:
The more complex a password the more resistant it will be against persons seeking
unauthorized access to a system.
Impact:
Password policy should be in effect to reduce the risk of exposed services being
compromised easily through dictionary attacks or other social engineering attempts.
293 | P a g e
Audit:
Perform the following to ensure that the passwords must contain at least 1 numeric
characters:
Graphical Method:
Terminal Method:
Run the following command to verify that passwords require at least one number:
294 | P a g e
Remediation:
example:
Profile Method:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
295 | P a g e
5.2.5 Ensure Complex Password Must Contain Special Character Is
Configured (Manual)
Profile Applicability:
• Level 2
Description:
Complex passwords contain one character from each of the following classes: English
uppercase letters, English lowercase letters, Westernized Arabic numerals, and non-
alphanumeric characters. Ensure that a special character is part of the password policy on
the computer.
Rationale:
The more complex a password the more resistant it will be against persons seeking
unauthorized access to a system.
Impact:
Password policy should be in effect to reduce the risk of exposed services being
compromised easily through dictionary attacks or other social engineering attempts.
296 | P a g e
Audit:
Perform the following to ensure that the passwords must contain at least 1 special
characters:
Graphical Method:
Terminal Method:
Run the following command to set verify that the password requires at least one special
character:
297 | P a g e
Remediation:
example:
Profile Method:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
298 | P a g e
5.2.6 Ensure Complex Password Must Contain Uppercase and
Lowercase Characters Is Configured (Manual)
Profile Applicability:
• Level 2
Description:
Complex passwords contain one character from each of the following classes: English
uppercase letters, English lowercase letters, Westernized Arabic numerals, and non-
alphanumeric characters.
Ensure that both uppercase and lowercase letters are part of the password policy on the
computer.
Rationale:
The more complex a password the more resistant it will be against persons seeking
unauthorized access to a system.
Impact:
Password policy should be in effect to reduce the risk of exposed services being
compromised easily through dictionary attacks or other social engineering attempts.
Audit:
Run the following command to set verify that the password requires at upper and lower
case letter:
299 | P a g e
Remediation:
Run the following command to set passwords to require at upper and lower case letter:
example:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
300 | P a g e
5.2.7 Ensure Password Age Is Configured (Automated)
Profile Applicability:
• Level 1
Description:
Over time passwords can be captured by third-parties through mistakes, phishing attacks,
third party breaches or merely brute force attacks. To reduce the risk of exposure and to
decrease the incentives of password reuse (passwords that are not forced to be changed
periodically generally are not ever changed) users should reset passwords periodically.
This control uses 365 days as the acceptable value. Some organizations may be more or
less restrictive. This control mainly exists to mitigate against password reuse of the macOS
account password in other realms that may be more prone to compromise. Attackers take
advantage of exposed information to attack other accounts.
Rationale:
Impact:
Required password changes will lead to some locked computers requiring admin
assistance.
301 | P a g e
Audit:
Perform the following to ensure that the passwords expire after at most 365 days:
Graphical Method:
Terminal Method:
Run the following command to verify that the password expires after at most 365 days:
Remediation:
Perform the following to enable passwords expiring at no greater than 365 days:
Terminal Method:
Run the following command to require that passwords expire after at most 365 days:
example:
Profile Method:
302 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
303 | P a g e
5.2.8 Ensure Password History Is Configured (Automated)
Profile Applicability:
• Level 1
Description:
Over time passwords can be captured by third-parties through mistakes, phishing attacks,
third party breaches or merely brute force attacks. To reduce the risk of exposure and to
decrease the incentives of password reuse (passwords that are not forced to be changed
periodically generally are not ever changed) users must reset passwords periodically. This
control ensures that previous passwords are not reused immediately by keeping a history
of previous password hashes. Ensure that password history checks are part of the
password policy on the computer. This control checks whether a new password is different
than the previous 15. The latest NIST guidance based on exploit research referenced in this
section details how one of the greatest risks is password exposure rather than password
cracking. Passwords should be changed to a new unique value whenever a password might
have been exposed to anyone other than the account holder. Attackers have maintained
persistent control based on predictable password change patterns and substantially
different patterns should be used in case of a leak.
Rationale:
Impact:
Required password changes will lead to some locked computers requiring admin
assistance.
304 | P a g e
Audit:
Perform the following to ensure that the password is not the same as at least the last 15
passwords:
Graphical Method:
Terminal Method:
Run the following command to verify that the password is required to be different from at
least the last 15 passwords:
305 | P a g e
Remediation:
Perform the following to enable new passwords to be different than at least the last 15
passwords:
Terminal Method:
Run the following command to require that the password must to be different from at least
the last 15 passwords:
example:
Profile Method:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
306 | P a g e
5.3 Ensure the Sudo Timeout Period Is Set to Zero (Automated)
Profile Applicability:
• Level 1
Description:
The sudo command allows the user to run programs as the root user. Working as the root
user allows the user an extremely high level of configurability within the system. This
control along with the control to use a separate timestamp for each tty limits the window
where an unauthorized user, process or attacker could utilize legitimate credentials that
are valid for longer than required.
Rationale:
The sudo command stays logged in as the root user for five minutes before timing out and
re-requesting a password. This five-minute window should be eliminated since it leaves the
system extremely vulnerable. This is especially true if an exploit were to gain access to the
system, since they would be able to make changes as a root user.
Impact:
This control has a serious impact where users often have to use sudo. It is even more of an
impact where users have to use sudo multiple times in quick succession as part of normal
work processes. Organizations with that common use case will likely find this control too
onerous and are better to accept the risk of not requiring a 0 grace period.
In some ways the use of sudo -s, which is undesirable, is better than a long grace period
since that use does change the hash to show that it is a root shell rather than a normal shell
where sudo commands will be implemented without a password.
Audit:
Defaults timestamp_timeout=0
307 | P a g e
Remediation:
$ sudo /usr/sbin/visudo
Add the line Defaults timestamp_timeout=0 in the Override built-in defaults section.
Additional Information:
#
# Sample /etc/sudoers file.
#
# This file MUST be edited with the 'visudo' command as root.
#
# See the sudoers man page for the details on how to write a sudoers file.
##
# Override built-in defaults
##
Defaults env_reset
Defaults env_keep += "BLOCKSIZE"
Defaults env_keep += "COLORFGBG COLORTERM"
Defaults env_keep += "__CF_USER_TEXT_ENCODING"
Defaults env_keep += "CHARSET LANG LANGUAGE LC_ALL LC_COLLATE
LC_CTYPE"
Defaults env_keep += "LC_MESSAGES LC_MONETARY LC_NUMERIC LC_TIME"
Defaults env_keep += "LINES COLUMNS"
Defaults env_keep += "LSCOLORS"
Defaults env_keep += "SSH_AUTH_SOCK"
Defaults env_keep += "TZ"
Defaults env_keep += "DISPLAY XAUTHORIZATION XAUTHORITY"
Defaults env_keep += "EDITOR VISUAL"
Defaults env_keep += "HOME MAIL"
##
# User alias specification
##
# User_Alias FULLTIMERS = millert, mikef, dowdy
##
# Runas alias specification
##
# Runas_Alias OP = root, operator
308 | P a g e
##
# Host alias specification
##
# Host_Alias CUNETS = 128.138.0.0/255.255.0.0
# Host_Alias CSNETS = 128.138.243.0, 128.138.204.0/24, 128.138.242.0
# Host_Alias SERVERS = master, mail, www, ns
# Host_Alias CDROM = orion, perseus, hercules
##
# Cmnd alias specification
##
# Cmnd_Alias PAGERS = /usr/bin/more, /usr/bin/pg, /usr/bin/less
##
# User specification
##
# root and users in group wheel can run anything on any machine as any user
root ALL = (ALL) ALL
%admin ALL = (ALL) ALL
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
309 | P a g e
5.4 Ensure a Separate Timestamp Is Enabled for Each User/tty Combo
(Automated)
Profile Applicability:
• Level 1
Description:
Using tty tickets ensures that a user must enter the sudo password in each Terminal
session.
With sudo versions 1.8 and higher, introduced in 10.12, the default value is to have tty
tickets for each interface so that root access is limited to a specific terminal. The default
configuration can be overwritten or not configured correctly on earlier versions of macOS.
Rationale:
In combination with removing the sudo timeout grace period, a further mitigation should
be in place to reduce the possibility of a background process using elevated rights when a
user elevates to root in an explicit context or tty.
Impact:
This control should have no user impact. Developers or installers may have issues if
background processes are spawned with different interfaces than where sudo was
executed.
Audit:
Run the following commands to verify that the default sudoers controls are in place with
explicit tickets per tty:
Ensure that nothing is returned or that the output does not include timestamp_type=ppid
or timestamp_type=global
310 | P a g e
Remediation:
Edit the /etc/sudoers file with visudo and remove !tty_tickets from any Defaults line. If
there is a Default line of timestamp_type= with a value other than tty, change the value to
tty
If there is a file in the /etc/sudoers.d/ folder that contains Defaults !tty_tickets, edit
the file and remove !tty_tickets from any Defaults line. If there is a file /etc/sudoers.d/
folder that contains a Default line of timestamp_type= with a value other than tty, change
the value to tty
Default Value:
Additional Information:
https://github.com/jorangreef/sudo-prompt/issues/33
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
311 | P a g e
5.5 Ensure login keychain is locked when the computer sleeps (Manual)
Profile Applicability:
• Level 2
Description:
The login keychain is a secure database store for passwords and certificates and is created
for each user account on macOS. The system software itself uses keychains for secure
storage. Anyone with physical access to an unlocked keychain where the screen is also
unlocked can copy all passwords in that keychain. The approach recommended here is that
the login keychain be set to lock when the computer sleeps to reduce the risk of password
exposure. Organizations that use Firefox and Thunderbird will have a much different
tolerance than those organizations using keychain aware applications extensively.
Early guidance, including in this Benchmark, recommended the use of additional keychains
as needed to separate confidentiality levels or separate user domains (work, school,
volunteer groups...) At his point, particularly with the availability of iCloud Keychain key
segregation is a niche use case. Recent recommendations on distinct keychains is very rare.
Rationale:
While logged in, the keychain does not prompt the user for passwords for various systems
and/or programs. This can be exploited by unauthorized users to gain access to password-
protected programs and/or systems in the absence of the user.
Impact:
The user may experience multiple prompts to unlock the keychain when waking from
sleep.
312 | P a g e
Audit:
Perform the following to verify that the keychain locks when the computer sleeps:
Graphical Method:
Terminal Method:
For each user, run the following command to unlock the keychain and verify it locks on
sleep:
313 | P a g e
Remediation:
Terminal Method:
For each user, run the following command to set the login keychain to sleep on lock:
example:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
314 | P a g e
5.6 Ensure the "root" Account Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
The root account is a superuser account that has access privileges to perform any actions
and read/write to any file on the computer. With some Linux distros the system
administrator may commonly use the root account to perform administrative functions.
Rationale:
Enabling and using the root account puts the system at risk since any successful exploit or
mistake while the root account is in use could have unlimited access privileges within the
system. Using the sudo command allows users to perform functions as a root user while
limiting and password protecting the access privileges. By default the root account is not
enabled on a macOS computer. An administrator can escalate privileges using the sudo
command (use -s or -i to get a root shell).
Impact:
Audit:
Perform the following to ensure that the root user is not enabled:
Graphical Method:
Terminal Method:
Run the following command to verify the the root user has not been enabled:
315 | P a g e
Remediation:
Terminal Method:
Run the following command to disable the root user:
$ sudo /usr/sbin/dsenableroot -d
username = root
user password:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
316 | P a g e
5.7 Ensure Automatic Login Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
The automatic login feature saves a user's system access credentials and bypasses the login
screen. Instead, the system automatically loads to the user's desktop screen.
Rationale:
Impact:
If automatic login is not disabled an unauthorized user could gain access to the system
without supplying any credentials.
317 | P a g e
Audit:
or
Terminal Method:
Run the following command to verify that automatic login has not been enabled:
com.apple.login.mcx.DisableAutoLoginClient = 1;
318 | P a g e
Remediation:
Terminal Method:
Run the following command to disable automatic login:
Profile Method:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
319 | P a g e
5.8 Ensure a Password is Required to Wake the Computer From Sleep or
Screen Saver Is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
Sleep and screensaver modes are low power modes that reduce electrical consumption
while the system is not in use.
Rationale:
Prompting for a password when waking from sleep or screensaver mode mitigates the
threat of an unauthorized person gaining access to a system in the user's absence.
Impact:
Without a screenlock in place anyone with physical access to the computer would be
logged in and able to use the active user's session.
320 | P a g e
Audit:
Perform the following to verify that a password is required to wake from sleep or screen
saver:
Graphical Method:
or
Terminal Method:
Run the following command to verify that a profile is installed that requires a password to
wake the computer from sleep or from the screen saver:
askForPassword = 1;
askForPasswordDelay = <0,5>;
321 | P a g e
Remediation:
Perform the following to enable a password for unlock after a screen saver begins or after
sleep:
Graphical Method:
Profile Method:
Additional Information:
This only protects the system when the screen saver is running.
Note: The command line check in previous versions of the Benchmark does not work as
expected here. The use of a profile is recommended for both implementation and auditing
on a 10.13 system.
Issue https://blog.kolide.com/screensaver-security-on-macos-10-13-is-broken-
a385726e2ae2
322 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
323 | P a g e
5.9 Ensure system is set to hibernate (Automated)
Profile Applicability:
• Level 2
Description:
In order to use a computer with Full Disk Encryption (FDE) macOS must keep encryption
keys in memory to allow the use of the disk that has been FileVault protected. The storage
volume has been unlocked and acts as if it was not encrypted. When the system is not in
use the volume is protected through encryption. When the system is sleeping and available
to quickly resume the encryption keys remain in memory.
If an unauthorized party has possession of the computer and the computer is only slept
there are known attack vectors that can be attempted against the RAM that has the
encryption keys or the running operating system that is protected by a login screen.
Network attacks if network interfaces are on as well as USB or other open device ports are
possible. Most of these attacks require knowledge of unpatched vulnerabilities or a high
level of sophistication if all the other controls function as intended.
There is little impact on hibernating the system rather than sleeping after an appropriate
time period to remediate the risk of OS level attacks. Hibernation writes the keys to disk
and requires FileVault to be unlocked prior to the OS being available. In the case of
unauthorized personnel with access to the computer encryption would have to be broken
prior to attacking the operating system in order to recover data from the system.
https://www.helpnetsecurity.com/2018/08/20/laptop-sleep-security/
Mac systems should be set to hibernate after sleeping for a risk-acceptable time period. The
default value for "standbydelay" is three hours (10800 seconds). This value is likely
appropriate for most desktops. If Mac desktops are deployed in unmonitored, less
physically secure areas with confidential data this value might be adjusted. The desktop or
would have to retain power so that the running OS or physical RAM could be attacked
however.
324 | P a g e
MacBooks should be set so that the standbydelay is 15 minutes (900 seconds) or less. This
setting should allow laptop users in most cases to stay within physically secured areas
while going to a conference room, auditorium or other internal location without having to
unlock the encryption. When the user goes home at night the laptop will auto-hibernate
after 15 minutes and require the FileVault password to unlock prior to logging back into
system when it resumes.
MacBooks should also be set to a hibernate mode that removes power from the RAM. This
will stop the possibility of cold boot attacks on the system.
Rationale:
To mitigate the risk of data loss the system should power down and lock the encrypted
drive after a specified time. Laptops should hibernate 15 minutes or less after sleeping.
Impact:
The laptop will take additional time to resume normal operation then if only sleeping
rather than hibernating.
325 | P a g e
Audit:
Run the following command to verify the hibernation settings and that FileVault keys are
destroyed on standby:
If the output includes Model Name: MacBook, Model Name: MacBook Air, Model Name:
MacBook Pro run the following:
DestroyFVKeyOnStandby 1
hibernatemode 25
example:
standbydelaylow 600
standby 1
standbydelayhigh 600
highstandbythreshold 50
326 | P a g e
Remediation:
Run the following command to set the hibernate delays and to ensure the FileVault keys are
set to be destroyed on standby:
example:
Additional Information:
There are several good references to the concerns about ensuring hibernation rather than
sleep is in place. A selection below:
http://mattwashchuk.com/articles/2016/01/08/maximizing-filevault-security
https://www.zdziarski.com/blog/?p=6705
https://www.howtogeek.com/260478/how-to-choose-when-your-mac-hibernates-or-
enters-standby/
https://www.lifewire.com/change-mac-sleep-settings-2260804
https://www.zdziarski.com/blog/?p=6705
327 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
328 | P a g e
5.10 Require an administrator password to access system-wide
preferences (Automated)
Profile Applicability:
• Level 1
Description:
System Preferences controls system and user settings on a macOS Computer. System
Preferences allows the user to tailor their experience on the computer as well as allowing
the System Administrator to configure global security settings. Some of the settings should
only be altered by the person responsible for the computer.
Rationale:
Impact:
If Automatic login is not disabled an unauthorized user could login without supplying a
user password or credential.
329 | P a g e
Audit:
Terminal Method:
Run the following command to verify that accessing system-wide preferences requires an
administrator password:
<false/>
330 | P a g e
Remediation:
Terminal Method:
The authorizationdb settings cannot be written to directly, so the plist must be exported
out to temporary file. Changes can be made to the temporary plist, then imported back into
the authorizationdb settings.
Run the following commands to enable that an administrator password is required to
access system-wide preferences:
YES (0)
YES (0)
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
331 | P a g e
5.11 Ensure an administrator account cannot login to another user's
active and locked session (Automated)
Profile Applicability:
• Level 1
Description:
macOS has a privilege that can be granted to any user that will allow that user to unlock
active user's sessions.
Rationale:
Disabling the admins and/or user's ability to log into another user's active and locked
session prevents unauthorized persons from viewing potentially sensitive and/or personal
information.
Impact:
While Fast user switching is a workaround for some lab environments especially where
there is even less of an expectation of privacy this setting change may impact some
maintenance workflows.
Audit:
Run the following command to verify that a user cannot log into another user's active
and/or locked session:
Remediation:
Run the following command to disable a user logging into another user's active and/or
locked session:
YES (0)
332 | P a g e
References:
1. https://derflounder.wordpress.com/2014/02/16/managing-the-authorization-
database-in-os-x-mavericks/
2. https://www.jamf.com/jamf-nation/discussions/18195/system-login-screensaver
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
333 | P a g e
5.12 Ensure a Custom Message for the Login Screen Is Enabled
(Automated)
Profile Applicability:
• Level 1
Description:
An access warning informs the user that the system is reserved for authorized use only,
and that the use of the system may be monitored.
Rationale:
An access warning may reduce a casual attacker's tendency to target the system. Access
warnings may also aid in the prosecution of an attacker by evincing the attacker's
knowledge of the system's private status, acceptable use policy, and authorization
requirements.
Impact:
If users are not informed of their responsibilities, unapproved activities may occur. Users
that are not approved for access may take the lack of a warning banner as implied consent
to access.
334 | P a g e
Audit:
Terminal Method:
Run the following command to verify that a custom message on the login screen is
configured:
or
Run the following command to verify that a profile is installed that configures a login
banner:
The output should include LoginwindowText set to your organization's required text.
example:
335 | P a g e
Remediation:
Perform the following to enable a login banner set to your organization's required text:
Terminal Method:
Run the following command to enable a custom login screen message:
example:
Profile Method:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
336 | P a g e
5.13 Ensure a Login Window Banner Exists (Automated)
Profile Applicability:
• Level 2
Description:
A Login window banner warning informs the user that the system is reserved for
authorized use only. It enforces an acknowledgment by the user that they have been
informed of the use policy in the banner if required. The system recognizes either the .txt
and the .rtf formats.
Rationale:
An access warning may reduce a casual attacker's tendency to target the system. Access
warnings may also aid in the prosecution of an attacker by evincing the attacker's
knowledge of the system's private status, acceptable use policy, and authorization
requirements.
Impact:
Users will have to click on the window with the Login text before logging into the
computer.
337 | P a g e
Audit:
{\rtf1\ansi\ansicpg1252\cocoartf1561\cocoasubrtf610
{\fonttbl\f0\fswiss\fcharset0 Helvetica;}
{\colortbl;\red255\green255\blue255;}
{\*\expandedcolortbl;;}
\margl1440\margr1440\vieww10800\viewh8400\viewkind0
\pard\tx566\tx1133\tx1700\tx2267\tx2834\tx3401\tx3968\tx4535\tx5102\tx5669\tx
6236\tx6803\pardirnatural\partightenfactor0
{\rtf1\ansi\ansicpg1252\cocoartf1561\cocoasubrtf610
{\fonttbl\f0\fswiss\fcharset0 Helvetica;}
{\colortbl;\red255\green255\blue255;}
{\*\expandedcolortbl;;}
\margl1440\margr1440\vieww10800\viewh8400\viewkind0
\pard\tx566\tx1133\tx1700\tx2267\tx2834\tx3401\tx3968\tx4535\tx5102\tx5669\tx
6236\tx6803\pardirnatural\partightenfactor0
\f0\fs24 \cf0 Center for Internet Security Test Message}Center for Internet
Security Test Message
Remediation:
338 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
339 | P a g e
5.14 Ensure Users' Accounts Do Not Have a Password Hint (Automated)
Profile Applicability:
• Level 1
Description:
Password hints help the user recall their passwords for various systems and/or accounts.
In most cases, password hints are simple and closely related to the user's password.
Rationale:
Password hints that are closely related to the user's password are a security vulnerability,
especially in the social media age. Unauthorized users are more likely to guess a user's
password if there is a password hint. The password hint is very susceptible to social
engineering attacks and information exposure on social media networks.
Audit:
Run the following command to verify that no users hava a password hint:
The output will list all users. If there are any text listed with the user, then the machine is
not compliant.
example:
firstuser passwordhint
seconduser passwordhint2
thirduser
fourthuser
Guest
340 | P a g e
Remediation:
Terminal Method:
Run the following command to remove a user's password hint:
example:
Additional Information:
Organizations might consider entering an organizational help desk phone number or other
text (such as a warning to the user). A help desk number is only appropriate for
organizations with trained help desk personnel that are validating user identities for
password resets.
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
341 | P a g e
5.15 Ensure Fast User Switching Is Disabled (Manual)
Profile Applicability:
• Level 2
Description:
Fast user switching allows a person to quickly log in to the computer with a different
account. While only a minimal security risk, when a second user is logged in, that user
might be able to see what processes the first user is using, or possibly gain other
information about the first user. In a large directory environment where it is difficult to
limit log in access many valid users can login to other user's assigned computers.
Rationale:
Fast user switching allows multiple users to run applications simultaneously at console.
There can be information disclosed about processes running under a different user.
Without a specific configuration to save data and log out users can have unsaved data
running in a background session that is not obvious.
Impact:
When support staff visits a user's computer console, they will not be able to log in to their
own session if there is an active and locked session.
342 | P a g e
Audit:
Perform the following to ensure that fast user switching is not enabled:
Graphical Method:
or
Terminal Method:
Run the following command to verify that fast user switching is disabled:
MultipleSessionEnabled = 0;
343 | P a g e
Remediation:
Terminal Method:
Run the following command to turn fast user switching off:
Profile Method:
Additional Information:
macOS is a multi-user operating system, and there are other similar methods that might
provide the same kind of risk. The Remote Login service that can be turned on in the
Sharing System Preferences pane is another.
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
344 | P a g e
6 User Accounts and Environment
Account management is a central part of security for any computer system including
macOS. General practices should be followed to ensure that all accounts on a system are
still needed and that default accounts have been removed. Users with admin roles should
have distinct accounts for admin functions as well as day to day work where the passwords
are different and known only by the user assigned to the account. Accounts with elevated
privileges should not be easily discerned from the account name from standard accounts.
When any computer system is added to a directory system there are additional controls
available including user account management that are not available in a standalone
computer. One of the drawbacks is the local computer is no longer in control of the
accounts that can access or manage it if given permission. For macOS, if the computer is
connected to a directory, any standard user can now login to the computer at console
which by default may be desirable or not depending on the use case. If an admin group is
allowed to administer the local computer the membership of that group is controlled
completely in the directory.
345 | P a g e
6.1 Accounts Preferences Action Items
Proper account management is critical to computer security. Many options and settings in
the Account System Preference Pane can be used to increase the security of the Mac.
346 | P a g e
6.1.1 Ensure Login Window Displays as Name and Password Is Enabled
(Automated)
Profile Applicability:
• Level 1
Description:
The login window prompts a user for his/her credentials, verifies their authorization level
and then allows or denies the user access to the system.
Rationale:
Prompting the user to enter both their username and password makes it twice as hard for
unauthorized users to gain access to the system since they must discover two attributes.
347 | P a g e
Audit:
Perform the following to verify that the login window displays name and password:
Graphical Method:
or
Terminal Method:
Run the following command to verify the login window displays name and password:
SHOWFULLNAME = 1;
348 | P a g e
Remediation:
Perform the following to ensure the login window display name and password:
Graphical Method:
Terminal Method:
Run the following command to enable the login window to display name and password:
Note: The GUI will not display the updated setting until the current user(s) logs out.
Profile Method:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
349 | P a g e
6.1.2 Ensure Show Password Hints Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
Password hints are user-created text displayed when an incorrect password is used for an
account.
Rationale:
Password hints make it easier for unauthorized persons to gain access to systems by
providing information to anyone that the user provided to assist in remembering the
password. This info could include the password itself or other information that might be
readily discerned with basic knowledge of the end user.
Impact:
The user can set the hint to any value including the password itself or clues that allow
trivial social engineering attacks.
350 | P a g e
Audit:
or
Terminal Method:
Run the following command to verify that password hints are not displayed:
RetriesUntilHint = 0;
351 | P a g e
Remediation:
Terminal Method:
Run the following command to disable password hints:
Profile Method:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
352 | P a g e
6.1.3 Ensure Guest Account Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
The guest account allows users access to the system without having to create an account or
password. Guest users are unable to make setting changes cannot remotely login to the
system. All files, caches, and passwords created by the guest user are deleted upon logging
out.
Rationale:
Disabling the guest account mitigates the risk of an untrusted user doing basic
reconnaissance and possibly using privilege escalation attacks to take control of the
system.
Impact:
A guest user can use that access to find out additional information about the system and
might be able to use privilege escalation vulnerabilities to establish greater access.
353 | P a g e
Audit:
Perform the following to ensure that the guest account is not available:
Graphical Method:
or
Terminal Method:
Run the following command to verify if the guest account is enabled:
or
Run the following command to verify that the Guest account is disabled:
DisableGuestAccount = 1;
EnableGuestAccount = 0;
354 | P a g e
Remediation:
Terminal Method:
Run the following command to disable the guest account:
Profile Method:
Additional Information:
By default, the guest account is enabled for access to sharing services but is not allowed to
log in to the computer.
The guest account does not need a password when it is enabled to log in to the computer.
355 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
356 | P a g e
6.1.4 Ensure Guest Access to Shared Folders Is Disabled (Automated)
Profile Applicability:
• Level 1
Description:
Allowing guests to connect to shared folders enables users to access selected shared folders
and their contents from different computers on a network.
Rationale:
Not allowing guests to connect to shared folders mitigates the risk of an untrusted user
doing basic reconnaissance and possibly use privilege escalation attacks to take control of
the system.
Impact:
357 | P a g e
Audit:
Perform the following to ensure that guests cannot connect to shared folders:
Graphical Method:
or
Terminal Method:
Run the following commands to verify that shared folders are not accessible to guest users:
The computer is also compliant if the command outputs The domain/default pair of
(/Library/Preferences/SystemConfiguration/com.apple.smb.server,
AllowGuestAccess) does not exist.
or
Run the following command to verify that a profile is installed that disables the Guest
account to connect to shared folders:
AllowGuestAccess = 0;
358 | P a g e
Remediation:
Perform the following to no longer allow guest user access to shared folders:
Graphical Method:
Terminal Method:
Run the following commands to verify that shared folders are not accessible to guest users:
Profile Method:
<array>
<dict>
<key>mcx_preference_settings</key>
<dict>
<key>AllowGuestAccess</key>
<false/>
</dict>
</dict>
</array>
359 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
360 | P a g e
6.1.5 Ensure the Guest Home Folder Does Not Exist (Automated)
Profile Applicability:
• Level 1
Description:
In the previous two controls the guest account login has been disabled and sharing to
guests has been disabled as well. There is no need for the legacy Guest home folder to
remain in the file system. When normal user accounts are removed you have the option to
archive it, leave it in place or delete. In the case of the guest folder the folder remains in
place without a GUI option to remove it. If at some point in the future a Guest account is
needed it will be re-created. The presence of the Guest home folder can cause automated
audits to fail when looking for compliant settings within all User folders as well. Rather
than ignoring the folder's continued existence, it is best removed.
Rationale:
The Guest home folders are unneeded after the Guest account is disabled and could be used
inappropriately.
Impact:
The Guest account should not be necessary after it is disabled, and it will be automatically
re-created if the Guest account is re-enabled
Audit:
Run the following command to verify if the Guest user home folder exists:
Remediation:
Run the following command to remove the Guest user home folder:
361 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
362 | P a g e
6.2 Ensure Show All Filename Extensions Setting is Enabled (Automated)
Profile Applicability:
• Level 1
Description:
A filename extension is a suffix added to a base filename that indicates the base filename's
file format.
Rationale:
Visible filename extensions allow the user to identify the file type and the application it is
associated with which leads to quick identification of misrepresented malicious files.
Impact:
The user of the system can open files of unknown or unexpected filetypes if the extension is
not visible.
363 | P a g e
Audit:
1. Open Finder
2. Select Finder in the Menu Bar
3. Select Preferences
4. Select Advanced
5. Verify that Show all filename extensions is set
Terminal Method:
Run the following command to verify that displaying of file extensions is enabled:
example:
364 | P a g e
Remediation:
1. Open Finder
2. Select Finder in the Menu Bar
3. Select Preferences
4. Select Advanced
5. Set Show all filename extensions
Terminal Method:
Run the following command to enable displaying of file extensions:
example:
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
365 | P a g e
6.3 Ensure Automatic Opening of Safe Files in Safari Is Disabled
(Automated)
Profile Applicability:
• Level 1
Description:
Safari will automatically run or execute what it considers safe files. This can include
installers and other files that execute on the operating system. Safari evaluates file safety
by using a list of filetypes maintained by Apple. The list of files include text, image, video
and archive formats that would be run in the context of the OS rather than the browser.
Rationale:
Hackers have taken advantage of this setting via drive-by attacks. These attacks occur
when a user visits a legitimate website that has been corrupted. The user unknowingly
downloads a malicious file either by closing an infected pop-up or hovering over a
malicious banner. An attacker can create a malicious file that will fall within Safari's safe
file list that will download and execute without user input.
Impact:
Apple considers many files that the operating system itself auto-executes as "safe files."
Many of these files could be malicious and could execute locally without the user even
knowing that a file of a specific type had been downloaded.
366 | P a g e
Audit:
Perform the following to verify that safe files are not opened on download in Safari:
Graphical Method:
1. Open Safari
2. Select Safari from the menu bar
3. Select Preferences
4. Select General
5. Verify that Open "safe" files after downloading is not set
or
Terminal Method:
Run the following command to verify that opening safe files in Safari is disabled:
example:
Note: To run the Terminal commands, Terminal must be granted Full Disk Access in the
Security & Privacy pane in System Preferences.
or
Run the following command to verify that a profile is installed that disables safe files from
opening in Safari:
AutoOpenSafeDownloads = 0;
367 | P a g e
Remediation:
Perform the following to set safe files to not open after downloading in Safari:
Graphical Method:
1. Open Safari
2. Select Safari from the menu bar
3. Select Preferences
4. Select General
5. Uncheck Open "safe" files after downloading
Terminal Method:
Run the following command to disable safe files from not opening in Safari:
example:
Note: To run the Terminal commands, Terminal must be granted Full Disk Access in the
Security & Privacy pane in System Preferences.
Profile Method:
<array>
<dict>
<key>mcx_preference_settings</key>
<dict>
<key>AutoOpenSafeDownloads</key>
<false/>
</dict>
</dict>
</array>
368 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
369 | P a g e
7 Appendix: Additional Considerations
This section is for guidance on topics for which the Benchmark does not include a
prescribed state, and for security controls that were previously represented in macOS
security guides.
370 | P a g e
7.1 Extensible Firmware Interface (EFI) password (Manual)
Profile Applicability:
• Level 2
Description:
EFI is the software link between the motherboard hardware and the software operating
system. EFI determines which partition or disk to load macOS from, and it also determines
whether the user can enter single user mode. The main reasons to set a firmware password
have been protections against an alternative boot disk, protection against a passwordless
root shell through single user mode and protection against firewire DMA attacks. While it
was easier in the past to reset the firmware password by removing RAM, it did make
tampering slightly harder because having to remove RAM remediated memory scraping
attacks through DMA. It has always been difficult to manage the firmware password on
macOS computers, though some tools did make it much easier.
Apple patched OS X in 10.7 to mitigate the DMA attacks, and the use of FileVault 2 Full-Disk
Encryption mitigates the risk of damage to the boot volume if an unauthorized user uses a
different boot volume or uses single user mode. Apple's reliance on the recovery partition
and the additional features it provides make controls that do not allow the user to boot into
the recovery partition less attractive.
Starting in late 2010 with the MacBook Air Apple has slowly updated the requirements to
recover from a lost firmware password. Apple only supports taking the computer to an
Apple authorized service provider. This change makes managing the firmware password
effectively more critical if it is used.
Setting the firmware password may be a good practice in some environments. We cannot
recommend it as a standard security practice at this time.
http://support.apple.com/kb/ts3554
https://jamfnation.jamfsoftware.com/article.html?id=58
http://derflounder.wordpress.com/2012/02/05/protecting-yourself-against-firewire-
dma-attacks-on-10-7-x/
http://derflounder.wordpress.com/2013/04/26/booting-into-single-user-mode-on-a-
filevault-2-encrypted-mac/
371 | P a g e
Impact:
In environments where strict processes are mandated for change control, allowing the user
to boot to recovery and possibly change configurations on the boot volume will be
unacceptable. The risk analysis for this control is that the user of the computer already has
login rights, decryption rights, and access to user data. In most known use cases device
management controls will be sufficient to mitigate and discover insider threat control
circumvention. Some organizations will not accept the risk of even temporary control
changes on devices and may need set an EFI password to block unauthorized changes even
from trusted insiders.
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
372 | P a g e
7.2 FileVault and Local Account Password Reset using AppleID (Manual)
Profile Applicability:
• Level 2
Description:
Apple has provided services for several years that allowed a user to reset a local account
password on a computer using their Apple ID and a service to store the FileVault Master
Password with Apple that would be controlled by access to an Apple ID. These distinct
services have been more cleanly integrated starting in 10.12.
This service allows for organizational computer users to utilize AppleIDs for encryption
key escrow and user account management. The use of Apple's services rather than
enterprise services may be considered inappropriate.
https://support.apple.com/en-us/HT204837
References:
1. https://support.apple.com/en-us/HT211672
373 | P a g e
CIS Controls:
Controls
Control IG 1 IG 2 IG 3
Version
374 | P a g e
Appendix: Recommendation Summary
Table
Control Set
Correctly
Yes No
1 Install Updates, Patches and Additional Security Software
1.1 Ensure All Apple-provided Software Is Current (Automated) o o
1.2 Ensure Auto Update Is Enabled (Automated) o o
1.3 Ensure Download New Updates When Available is Enabled
o o
(Automated)
1.4 Ensure Installation of App Update Is Enabled (Automated) o o
1.5 Ensure System Data Files and Security Updates Are
o o
Downloaded Automatically Is Enabled (Automated)
1.6 Ensure Install of macOS Updates Is Enabled (Automated) o o
1.7 Audit Computer Name (Manual) o o
2 System Preferences
2.1 Bluetooth
2.1.1 Ensure Bluetooth Is Disabled If No Devices Are Paired
o o
(Automated)
2.1.2 Ensure Show Bluetooth Status in Menu Bar Is Enabled
o o
(Automated)
2.2 Date & Time
2.2.1 Ensure "Set time and date automatically" Is Enabled
o o
(Automated)
2.2.2 Ensure time set is within appropriate limits (Automated) o o
2.3 Desktop & Screen Saver
2.3.1 Ensure an Inactivity Interval of 20 Minutes Or Less for the
o o
Screen Saver Is Enabled (Automated)
2.3.2 Ensure Screen Saver Corners Are Secure (Automated) o o
2.3.3 Audit Lock Screen and Start Screen Saver Tools (Manual) o o
2.4 Sharing
2.4.1 Ensure Remote Apple Events Is Disabled (Automated) o o
2.4.2 Ensure Internet Sharing Is Disabled (Automated) o o
2.4.3 Ensure Screen Sharing Is Disabled (Automated) o o
2.4.4 Ensure Printer Sharing Is Disabled (Automated) o o
2.4.5 Ensure Remote Login Is Disabled (Automated) o o
2.4.6 Ensure DVD or CD Sharing Is Disabled (Automated) o o
2.4.7 Ensure Bluetooth Sharing Is Disabled (Automated) o o
2.4.8 Ensure File Sharing Is Disabled (Automated) o o
2.4.9 Ensure Remote Management Is Disabled (Automated) o o
375 | P a g e
2.4.10 Ensure Content Caching Is Disabled (Automated) o o
2.4.11 Ensure AirDrop Is Disabled (Automated) o o
2.4.12 Ensure Media Sharing Is Disabled (Automated) o o
2.4.13 Ensure AirPlay Receiver Is Disabled (Automated) o o
2.5 Security & Privacy
2.5.1 Encryption
2.5.1.1 Ensure FileVault Is Enabled (Automated) o o
2.5.1.2 Ensure all user storage APFS volumes are encrypted
o o
(Manual)
2.5.1.3 Ensure all user storage CoreStorage volumes are encrypted
o o
(Manual)
2.5.2 Firewall
2.5.2.1 Ensure Gatekeeper is Enabled (Automated) o o
2.5.2.2 Ensure Firewall Is Enabled (Automated) o o
2.5.2.3 Ensure Firewall Stealth Mode Is Enabled (Automated) o o
2.5.3 Ensure Location Services Is Enabled (Automated) o o
2.5.4 Audit Location Services Access (Manual) o o
2.5.5 Ensure Sending Diagnostic and Usage Data to Apple Is
o o
Disabled (Automated)
2.5.6 Ensure Limit Ad Tracking Is Enabled (Automated) o o
2.5.7 Audit Camera Privacy and Confidentiality (Manual) o o
2.6 Apple ID
2.6.1 iCloud
2.6.1.1 Audit iCloud Configuration (Manual) o o
2.6.1.2 Audit iCloud Keychain (Manual) o o
2.6.1.3 Audit iCloud Drive (Manual) o o
2.6.1.4 Ensure iCloud Drive Document and Desktop Sync is
o o
Disabled (Automated)
2.6.2 Audit App Store Password Settings (Manual) o o
2.7 Time Machine
2.7.1 Ensure Backup Up Automatically is Enabled (Automated) o o
2.7.2 Ensure Time Machine Volumes Are Encrypted (Automated) o o
2.8 Ensure Wake for Network Access Is Disabled (Automated) o o
2.9 Ensure Power Nap Is Disabled (Automated) o o
2.10 Ensure Secure Keyboard Entry terminal.app is Enabled
o o
(Automated)
2.11 Ensure EFI Version Is Valid and Checked Regularly
o o
(Automated)
2.12 Audit Automatic Actions for Optical Media (Manual) o o
2.13 Audit Siri Settings (Manual) o o
2.14 Audit Sidecar Settings (Manual) o o
2.15 Audit Touch ID and Wallet & Apple Pay Settings (Manual) o o
2.16 Audit Notification System Preference Settings (Manual) o o
376 | P a g e
2.17 Audit Passwords System Preference Setting (Manual) o o
3 Logging and Auditing
3.1 Ensure Security Auditing Is Enabled (Automated) o o
3.2 Ensure Security Auditing Flags Are Configured Per Local
o o
Organizational Requirements (Automated)
3.3 Ensure install.log Is Retained for 365 or More Days and No
o o
Maximum Size (Automated)
3.4 Ensure Security Auditing Retention Is Enabled (Automated) o o
3.5 Ensure Access to Audit Records Is Controlled (Automated) o o
3.6 Ensure Firewall Logging Is Enabled and Configured
o o
(Automated)
3.7 Audit Software Inventory (Manual) o o
4 Network Configurations
4.1 Ensure Bonjour Advertising Services Is Disabled
o o
(Automated)
4.2 Ensure Show Wi-Fi status in Menu Bar Is Enabled
o o
(Automated)
4.3 Audit Network Specific Locations (Manual) o o
4.4 Ensure HTTP Server Is Disabled (Automated) o o
4.5 Ensure NFS Server Is Disabled (Automated) o o
4.6 Audit Wi-Fi Settings (Manual) o o
5 System Access, Authentication and Authorization
5.1 File System Permissions and Access Controls
5.1.1 Ensure Home Folders Are Secure (Automated) o o
5.1.2 Ensure System Integrity Protection Status (SIPS) Is Enabled
o o
(Automated)
5.1.3 Ensure Apple Mobile File Integrity Is Enabled (Automated) o o
5.1.4 Ensure Library Validation Is Enabled (Automated) o o
5.1.5 Ensure Sealed System Volume (SSV) Is Enabled
o o
(Automated)
5.1.6 Ensure Appropriate Permissions Are Enabled for System
o o
Wide Applications (Automated)
5.1.7 Ensure No World Writable Files Exist in the System Folder
o o
(Automated)
5.1.8 Ensure No World Writable Files Exist in the Library Folder
o o
(Automated)
5.2 Password Management
5.2.1 Ensure Password Account Lockout Threshold Is Configured
o o
(Automated)
5.2.2 Ensure Password Minimum Length Is Configured
o o
(Automated)
5.2.3 Ensure Complex Password Must Contain Alphabetic
o o
Characters Is Configured (Manual)
377 | P a g e
5.2.4 Ensure Complex Password Must Contain Numeric Character
o o
Is Configured (Manual)
5.2.5 Ensure Complex Password Must Contain Special Character
o o
Is Configured (Manual)
5.2.6 Ensure Complex Password Must Contain Uppercase and
o o
Lowercase Characters Is Configured (Manual)
5.2.7 Ensure Password Age Is Configured (Automated) o o
5.2.8 Ensure Password History Is Configured (Automated) o o
5.3 Ensure the Sudo Timeout Period Is Set to Zero (Automated) o o
5.4 Ensure a Separate Timestamp Is Enabled for Each User/tty
o o
Combo (Automated)
5.5 Ensure login keychain is locked when the computer sleeps
o o
(Manual)
5.6 Ensure the "root" Account Is Disabled (Automated) o o
5.7 Ensure Automatic Login Is Disabled (Automated) o o
5.8 Ensure a Password is Required to Wake the Computer From
o o
Sleep or Screen Saver Is Enabled (Automated)
5.9 Ensure system is set to hibernate (Automated) o o
5.10 Require an administrator password to access system-wide
o o
preferences (Automated)
5.11 Ensure an administrator account cannot login to another
o o
user's active and locked session (Automated)
5.12 Ensure a Custom Message for the Login Screen Is Enabled
o o
(Automated)
5.13 Ensure a Login Window Banner Exists (Automated) o o
5.14 Ensure Users' Accounts Do Not Have a Password Hint
o o
(Automated)
5.15 Ensure Fast User Switching Is Disabled (Manual) o o
6 User Accounts and Environment
6.1 Accounts Preferences Action Items
6.1.1 Ensure Login Window Displays as Name and Password Is
o o
Enabled (Automated)
6.1.2 Ensure Show Password Hints Is Disabled (Automated) o o
6.1.3 Ensure Guest Account Is Disabled (Automated) o o
6.1.4 Ensure Guest Access to Shared Folders Is Disabled
o o
(Automated)
6.1.5 Ensure the Guest Home Folder Does Not Exist (Automated) o o
6.2 Ensure Show All Filename Extensions Setting is Enabled
o o
(Automated)
6.3 Ensure Automatic Opening of Safe Files in Safari Is Disabled
o o
(Automated)
7 Appendix: Additional Considerations
7.1 Extensible Firmware Interface (EFI) password (Manual) o o
378 | P a g e
7.2 FileVault and Local Account Password Reset using AppleID
o o
(Manual)
379 | P a g e
Appendix: CIS Controls v7 IG 1 Mapped
Recommendations
Recommendation Set
Correctly
Yes No
1.1 Ensure All Apple-provided Software Is Current o o
1.2 Ensure Auto Update Is Enabled o o
1.3 Ensure Download New Updates When Available is Enabled o o
1.4 Ensure Installation of App Update Is Enabled o o
1.5 Ensure System Data Files and Security Updates Are
o o
Downloaded Automatically Is Enabled
1.6 Ensure Install of macOS Updates Is Enabled o o
2.3.1 Ensure an Inactivity Interval of 20 Minutes Or Less for the
o o
Screen Saver Is Enabled
2.3.2 Ensure Screen Saver Corners Are Secure o o
2.3.3 Audit Lock Screen and Start Screen Saver Tools o o
2.4.1 Ensure Remote Apple Events Is Disabled o o
2.4.2 Ensure Internet Sharing Is Disabled o o
2.4.3 Ensure Screen Sharing Is Disabled o o
2.4.4 Ensure Printer Sharing Is Disabled o o
2.4.5 Ensure Remote Login Is Disabled o o
2.4.6 Ensure DVD or CD Sharing Is Disabled o o
2.4.7 Ensure Bluetooth Sharing Is Disabled o o
2.4.8 Ensure File Sharing Is Disabled o o
2.4.9 Ensure Remote Management Is Disabled o o
2.4.11 Ensure AirDrop Is Disabled o o
2.4.12 Ensure Media Sharing Is Disabled o o
2.4.13 Ensure AirPlay Receiver Is Disabled o o
2.5.1.1 Ensure FileVault Is Enabled o o
2.5.1.2 Ensure all user storage APFS volumes are encrypted o o
2.5.1.3 Ensure all user storage CoreStorage volumes are encrypted o o
2.5.2.1 Ensure Gatekeeper is Enabled o o
2.5.2.2 Ensure Firewall Is Enabled o o
2.5.2.3 Ensure Firewall Stealth Mode Is Enabled o o
2.5.3 Ensure Location Services Is Enabled o o
2.5.4 Audit Location Services Access o o
2.5.5 Ensure Sending Diagnostic and Usage Data to Apple Is
o o
Disabled
2.5.6 Ensure Limit Ad Tracking Is Enabled o o
380 | P a g e
2.5.7 Audit Camera Privacy and Confidentiality o o
2.6.1.1 Audit iCloud Configuration o o
2.6.1.2 Audit iCloud Keychain o o
2.6.1.3 Audit iCloud Drive o o
2.6.1.4 Ensure iCloud Drive Document and Desktop Sync is
o o
Disabled
2.6.2 Audit App Store Password Settings o o
2.7.1 Ensure Backup Up Automatically is Enabled o o
2.7.2 Ensure Time Machine Volumes Are Encrypted o o
2.9 Ensure Power Nap Is Disabled o o
2.10 Ensure Secure Keyboard Entry terminal.app is Enabled o o
2.11 Ensure EFI Version Is Valid and Checked Regularly o o
2.12 Audit Automatic Actions for Optical Media o o
2.13 Audit Siri Settings o o
2.14 Audit Sidecar Settings o o
2.15 Audit Touch ID and Wallet & Apple Pay Settings o o
2.16 Audit Notification System Preference Settings o o
3.1 Ensure Security Auditing Is Enabled o o
3.2 Ensure Security Auditing Flags Are Configured Per Local
o o
Organizational Requirements
3.5 Ensure Access to Audit Records Is Controlled o o
3.6 Ensure Firewall Logging Is Enabled and Configured o o
3.7 Audit Software Inventory o o
4.1 Ensure Bonjour Advertising Services Is Disabled o o
4.3 Audit Network Specific Locations o o
4.4 Ensure HTTP Server Is Disabled o o
4.5 Ensure NFS Server Is Disabled o o
5.1.1 Ensure Home Folders Are Secure o o
5.1.2 Ensure System Integrity Protection Status (SIPS) Is Enabled o o
5.1.3 Ensure Apple Mobile File Integrity Is Enabled o o
5.1.4 Ensure Library Validation Is Enabled o o
5.1.5 Ensure Sealed System Volume (SSV) Is Enabled o o
5.1.6 Ensure Appropriate Permissions Are Enabled for System
o o
Wide Applications
5.1.7 Ensure No World Writable Files Exist in the System Folder o o
5.1.8 Ensure No World Writable Files Exist in the Library Folder o o
5.2.7 Ensure Password Age Is Configured o o
5.3 Ensure the Sudo Timeout Period Is Set to Zero o o
5.4 Ensure a Separate Timestamp Is Enabled for Each User/tty
o o
Combo
5.5 Ensure login keychain is locked when the computer sleeps o o
5.6 Ensure the "root" Account Is Disabled o o
5.7 Ensure Automatic Login Is Disabled o o
381 | P a g e
5.8 Ensure a Password is Required to Wake the Computer From
o o
Sleep or Screen Saver Is Enabled
5.9 Ensure system is set to hibernate o o
5.10 Require an administrator password to access system-wide
o o
preferences
5.11 Ensure an administrator account cannot login to another
o o
user's active and locked session
5.12 Ensure a Custom Message for the Login Screen Is Enabled o o
5.13 Ensure a Login Window Banner Exists o o
5.15 Ensure Fast User Switching Is Disabled o o
6.1.1 Ensure Login Window Displays as Name and Password Is
o o
Enabled
6.1.2 Ensure Show Password Hints Is Disabled o o
6.1.4 Ensure Guest Access to Shared Folders Is Disabled o o
6.1.5 Ensure the Guest Home Folder Does Not Exist o o
6.2 Ensure Show All Filename Extensions Setting is Enabled o o
6.3 Ensure Automatic Opening of Safe Files in Safari Is Disabled o o
382 | P a g e
Appendix: CIS Controls v7 IG 2 Mapped
Recommendations
Recommendation Set
Correctly
Yes No
1.1 Ensure All Apple-provided Software Is Current o o
1.2 Ensure Auto Update Is Enabled o o
1.3 Ensure Download New Updates When Available is Enabled o o
1.4 Ensure Installation of App Update Is Enabled o o
1.5 Ensure System Data Files and Security Updates Are
o o
Downloaded Automatically Is Enabled
1.6 Ensure Install of macOS Updates Is Enabled o o
1.7 Audit Computer Name o o
2.1.1 Ensure Bluetooth Is Disabled If No Devices Are Paired o o
2.1.2 Ensure Show Bluetooth Status in Menu Bar Is Enabled o o
2.2.1 Ensure "Set time and date automatically" Is Enabled o o
2.2.2 Ensure time set is within appropriate limits o o
2.3.1 Ensure an Inactivity Interval of 20 Minutes Or Less for the
o o
Screen Saver Is Enabled
2.3.2 Ensure Screen Saver Corners Are Secure o o
2.3.3 Audit Lock Screen and Start Screen Saver Tools o o
2.4.1 Ensure Remote Apple Events Is Disabled o o
2.4.2 Ensure Internet Sharing Is Disabled o o
2.4.3 Ensure Screen Sharing Is Disabled o o
2.4.4 Ensure Printer Sharing Is Disabled o o
2.4.5 Ensure Remote Login Is Disabled o o
2.4.6 Ensure DVD or CD Sharing Is Disabled o o
2.4.7 Ensure Bluetooth Sharing Is Disabled o o
2.4.8 Ensure File Sharing Is Disabled o o
2.4.9 Ensure Remote Management Is Disabled o o
2.4.10 Ensure Content Caching Is Disabled o o
2.4.11 Ensure AirDrop Is Disabled o o
2.4.12 Ensure Media Sharing Is Disabled o o
2.4.13 Ensure AirPlay Receiver Is Disabled o o
2.5.1.1 Ensure FileVault Is Enabled o o
2.5.1.2 Ensure all user storage APFS volumes are encrypted o o
2.5.1.3 Ensure all user storage CoreStorage volumes are encrypted o o
2.5.2.1 Ensure Gatekeeper is Enabled o o
2.5.2.2 Ensure Firewall Is Enabled o o
383 | P a g e
2.5.2.3 Ensure Firewall Stealth Mode Is Enabled o o
2.5.3 Ensure Location Services Is Enabled o o
2.5.4 Audit Location Services Access o o
2.5.5 Ensure Sending Diagnostic and Usage Data to Apple Is
o o
Disabled
2.5.6 Ensure Limit Ad Tracking Is Enabled o o
2.5.7 Audit Camera Privacy and Confidentiality o o
2.6.1.1 Audit iCloud Configuration o o
2.6.1.2 Audit iCloud Keychain o o
2.6.1.3 Audit iCloud Drive o o
2.6.1.4 Ensure iCloud Drive Document and Desktop Sync is
o o
Disabled
2.6.2 Audit App Store Password Settings o o
2.7.1 Ensure Backup Up Automatically is Enabled o o
2.7.2 Ensure Time Machine Volumes Are Encrypted o o
2.8 Ensure Wake for Network Access Is Disabled o o
2.9 Ensure Power Nap Is Disabled o o
2.10 Ensure Secure Keyboard Entry terminal.app is Enabled o o
2.11 Ensure EFI Version Is Valid and Checked Regularly o o
2.12 Audit Automatic Actions for Optical Media o o
2.13 Audit Siri Settings o o
2.14 Audit Sidecar Settings o o
2.15 Audit Touch ID and Wallet & Apple Pay Settings o o
2.16 Audit Notification System Preference Settings o o
2.17 Audit Passwords System Preference Setting o o
3.1 Ensure Security Auditing Is Enabled o o
3.2 Ensure Security Auditing Flags Are Configured Per Local
o o
Organizational Requirements
3.3 Ensure install.log Is Retained for 365 or More Days and No
o o
Maximum Size
3.4 Ensure Security Auditing Retention Is Enabled o o
3.5 Ensure Access to Audit Records Is Controlled o o
3.6 Ensure Firewall Logging Is Enabled and Configured o o
3.7 Audit Software Inventory o o
4.1 Ensure Bonjour Advertising Services Is Disabled o o
4.3 Audit Network Specific Locations o o
4.4 Ensure HTTP Server Is Disabled o o
4.5 Ensure NFS Server Is Disabled o o
5.1.1 Ensure Home Folders Are Secure o o
5.1.2 Ensure System Integrity Protection Status (SIPS) Is Enabled o o
5.1.3 Ensure Apple Mobile File Integrity Is Enabled o o
5.1.4 Ensure Library Validation Is Enabled o o
5.1.5 Ensure Sealed System Volume (SSV) Is Enabled o o
384 | P a g e
5.1.6 Ensure Appropriate Permissions Are Enabled for System
o o
Wide Applications
5.1.7 Ensure No World Writable Files Exist in the System Folder o o
5.1.8 Ensure No World Writable Files Exist in the Library Folder o o
5.2.1 Ensure Password Account Lockout Threshold Is Configured o o
5.2.2 Ensure Password Minimum Length Is Configured o o
5.2.3 Ensure Complex Password Must Contain Alphabetic
o o
Characters Is Configured
5.2.4 Ensure Complex Password Must Contain Numeric Character
o o
Is Configured
5.2.5 Ensure Complex Password Must Contain Special Character
o o
Is Configured
5.2.6 Ensure Complex Password Must Contain Uppercase and
o o
Lowercase Characters Is Configured
5.2.7 Ensure Password Age Is Configured o o
5.2.8 Ensure Password History Is Configured o o
5.3 Ensure the Sudo Timeout Period Is Set to Zero o o
5.4 Ensure a Separate Timestamp Is Enabled for Each User/tty
o o
Combo
5.5 Ensure login keychain is locked when the computer sleeps o o
5.6 Ensure the "root" Account Is Disabled o o
5.7 Ensure Automatic Login Is Disabled o o
5.8 Ensure a Password is Required to Wake the Computer From
o o
Sleep or Screen Saver Is Enabled
5.9 Ensure system is set to hibernate o o
5.10 Require an administrator password to access system-wide
o o
preferences
5.11 Ensure an administrator account cannot login to another
o o
user's active and locked session
5.12 Ensure a Custom Message for the Login Screen Is Enabled o o
5.13 Ensure a Login Window Banner Exists o o
5.14 Ensure Users' Accounts Do Not Have a Password Hint o o
5.15 Ensure Fast User Switching Is Disabled o o
6.1.1 Ensure Login Window Displays as Name and Password Is
o o
Enabled
6.1.2 Ensure Show Password Hints Is Disabled o o
6.1.3 Ensure Guest Account Is Disabled o o
6.1.4 Ensure Guest Access to Shared Folders Is Disabled o o
6.1.5 Ensure the Guest Home Folder Does Not Exist o o
6.2 Ensure Show All Filename Extensions Setting is Enabled o o
6.3 Ensure Automatic Opening of Safe Files in Safari Is Disabled o o
385 | P a g e
386 | P a g e
Appendix: CIS Controls v7 IG 3 Mapped
Recommendations
Recommendation Set
Correctly
Yes No
1.1 Ensure All Apple-provided Software Is Current o o
1.2 Ensure Auto Update Is Enabled o o
1.3 Ensure Download New Updates When Available is Enabled o o
1.4 Ensure Installation of App Update Is Enabled o o
1.5 Ensure System Data Files and Security Updates Are
o o
Downloaded Automatically Is Enabled
1.6 Ensure Install of macOS Updates Is Enabled o o
1.7 Audit Computer Name o o
2.1.1 Ensure Bluetooth Is Disabled If No Devices Are Paired o o
2.1.2 Ensure Show Bluetooth Status in Menu Bar Is Enabled o o
2.2.1 Ensure "Set time and date automatically" Is Enabled o o
2.2.2 Ensure time set is within appropriate limits o o
2.3.1 Ensure an Inactivity Interval of 20 Minutes Or Less for the
o o
Screen Saver Is Enabled
2.3.2 Ensure Screen Saver Corners Are Secure o o
2.3.3 Audit Lock Screen and Start Screen Saver Tools o o
2.4.1 Ensure Remote Apple Events Is Disabled o o
2.4.2 Ensure Internet Sharing Is Disabled o o
2.4.3 Ensure Screen Sharing Is Disabled o o
2.4.4 Ensure Printer Sharing Is Disabled o o
2.4.5 Ensure Remote Login Is Disabled o o
2.4.6 Ensure DVD or CD Sharing Is Disabled o o
2.4.7 Ensure Bluetooth Sharing Is Disabled o o
2.4.8 Ensure File Sharing Is Disabled o o
2.4.9 Ensure Remote Management Is Disabled o o
2.4.10 Ensure Content Caching Is Disabled o o
2.4.11 Ensure AirDrop Is Disabled o o
2.4.12 Ensure Media Sharing Is Disabled o o
2.4.13 Ensure AirPlay Receiver Is Disabled o o
2.5.1.1 Ensure FileVault Is Enabled o o
2.5.1.2 Ensure all user storage APFS volumes are encrypted o o
2.5.1.3 Ensure all user storage CoreStorage volumes are encrypted o o
2.5.2.1 Ensure Gatekeeper is Enabled o o
2.5.2.2 Ensure Firewall Is Enabled o o
387 | P a g e
2.5.2.3 Ensure Firewall Stealth Mode Is Enabled o o
2.5.3 Ensure Location Services Is Enabled o o
2.5.4 Audit Location Services Access o o
2.5.5 Ensure Sending Diagnostic and Usage Data to Apple Is
o o
Disabled
2.5.6 Ensure Limit Ad Tracking Is Enabled o o
2.5.7 Audit Camera Privacy and Confidentiality o o
2.6.1.1 Audit iCloud Configuration o o
2.6.1.2 Audit iCloud Keychain o o
2.6.1.3 Audit iCloud Drive o o
2.6.1.4 Ensure iCloud Drive Document and Desktop Sync is
o o
Disabled
2.6.2 Audit App Store Password Settings o o
2.7.1 Ensure Backup Up Automatically is Enabled o o
2.7.2 Ensure Time Machine Volumes Are Encrypted o o
2.8 Ensure Wake for Network Access Is Disabled o o
2.9 Ensure Power Nap Is Disabled o o
2.10 Ensure Secure Keyboard Entry terminal.app is Enabled o o
2.11 Ensure EFI Version Is Valid and Checked Regularly o o
2.12 Audit Automatic Actions for Optical Media o o
2.13 Audit Siri Settings o o
2.14 Audit Sidecar Settings o o
2.15 Audit Touch ID and Wallet & Apple Pay Settings o o
2.16 Audit Notification System Preference Settings o o
2.17 Audit Passwords System Preference Setting o o
3.1 Ensure Security Auditing Is Enabled o o
3.2 Ensure Security Auditing Flags Are Configured Per Local
o o
Organizational Requirements
3.3 Ensure install.log Is Retained for 365 or More Days and No
o o
Maximum Size
3.4 Ensure Security Auditing Retention Is Enabled o o
3.5 Ensure Access to Audit Records Is Controlled o o
3.6 Ensure Firewall Logging Is Enabled and Configured o o
3.7 Audit Software Inventory o o
4.1 Ensure Bonjour Advertising Services Is Disabled o o
4.2 Ensure Show Wi-Fi status in Menu Bar Is Enabled o o
4.3 Audit Network Specific Locations o o
4.4 Ensure HTTP Server Is Disabled o o
4.5 Ensure NFS Server Is Disabled o o
4.6 Audit Wi-Fi Settings o o
5.1.1 Ensure Home Folders Are Secure o o
5.1.2 Ensure System Integrity Protection Status (SIPS) Is Enabled o o
5.1.3 Ensure Apple Mobile File Integrity Is Enabled o o
388 | P a g e
5.1.4 Ensure Library Validation Is Enabled o o
5.1.5 Ensure Sealed System Volume (SSV) Is Enabled o o
5.1.6 Ensure Appropriate Permissions Are Enabled for System
o o
Wide Applications
5.1.7 Ensure No World Writable Files Exist in the System Folder o o
5.1.8 Ensure No World Writable Files Exist in the Library Folder o o
5.2.1 Ensure Password Account Lockout Threshold Is Configured o o
5.2.2 Ensure Password Minimum Length Is Configured o o
5.2.3 Ensure Complex Password Must Contain Alphabetic
o o
Characters Is Configured
5.2.4 Ensure Complex Password Must Contain Numeric Character
o o
Is Configured
5.2.5 Ensure Complex Password Must Contain Special Character
o o
Is Configured
5.2.6 Ensure Complex Password Must Contain Uppercase and
o o
Lowercase Characters Is Configured
5.2.7 Ensure Password Age Is Configured o o
5.2.8 Ensure Password History Is Configured o o
5.3 Ensure the Sudo Timeout Period Is Set to Zero o o
5.4 Ensure a Separate Timestamp Is Enabled for Each User/tty
o o
Combo
5.5 Ensure login keychain is locked when the computer sleeps o o
5.6 Ensure the "root" Account Is Disabled o o
5.7 Ensure Automatic Login Is Disabled o o
5.8 Ensure a Password is Required to Wake the Computer From
o o
Sleep or Screen Saver Is Enabled
5.9 Ensure system is set to hibernate o o
5.10 Require an administrator password to access system-wide
o o
preferences
5.11 Ensure an administrator account cannot login to another
o o
user's active and locked session
5.12 Ensure a Custom Message for the Login Screen Is Enabled o o
5.13 Ensure a Login Window Banner Exists o o
5.14 Ensure Users' Accounts Do Not Have a Password Hint o o
5.15 Ensure Fast User Switching Is Disabled o o
6.1.1 Ensure Login Window Displays as Name and Password Is
o o
Enabled
6.1.2 Ensure Show Password Hints Is Disabled o o
6.1.3 Ensure Guest Account Is Disabled o o
6.1.4 Ensure Guest Access to Shared Folders Is Disabled o o
6.1.5 Ensure the Guest Home Folder Does Not Exist o o
6.2 Ensure Show All Filename Extensions Setting is Enabled o o
6.3 Ensure Automatic Opening of Safe Files in Safari Is Disabled o o
389 | P a g e
390 | P a g e
Appendix: CIS Controls v8 IG 1 Mapped
Recommendations
Recommendation Set
Correctly
Yes No
1.1 Ensure All Apple-provided Software Is Current o o
1.2 Ensure Auto Update Is Enabled o o
1.3 Ensure Download New Updates When Available is Enabled o o
1.4 Ensure Installation of App Update Is Enabled o o
1.5 Ensure System Data Files and Security Updates Are
o o
Downloaded Automatically Is Enabled
1.6 Ensure Install of macOS Updates Is Enabled o o
1.7 Audit Computer Name o o
2.3.1 Ensure an Inactivity Interval of 20 Minutes Or Less for the
o o
Screen Saver Is Enabled
2.3.2 Ensure Screen Saver Corners Are Secure o o
2.3.3 Audit Lock Screen and Start Screen Saver Tools o o
2.4.1 Ensure Remote Apple Events Is Disabled o o
2.4.2 Ensure Internet Sharing Is Disabled o o
2.4.3 Ensure Screen Sharing Is Disabled o o
2.4.4 Ensure Printer Sharing Is Disabled o o
2.4.5 Ensure Remote Login Is Disabled o o
2.4.6 Ensure DVD or CD Sharing Is Disabled o o
2.4.7 Ensure Bluetooth Sharing Is Disabled o o
2.4.8 Ensure File Sharing Is Disabled o o
2.4.9 Ensure Remote Management Is Disabled o o
2.4.11 Ensure AirDrop Is Disabled o o
2.4.12 Ensure Media Sharing Is Disabled o o
2.4.13 Ensure AirPlay Receiver Is Disabled o o
2.5.1.1 Ensure FileVault Is Enabled o o
2.5.1.2 Ensure all user storage APFS volumes are encrypted o o
2.5.2.1 Ensure Gatekeeper is Enabled o o
2.5.2.2 Ensure Firewall Is Enabled o o
2.5.2.3 Ensure Firewall Stealth Mode Is Enabled o o
2.5.3 Ensure Location Services Is Enabled o o
2.5.4 Audit Location Services Access o o
2.5.5 Ensure Sending Diagnostic and Usage Data to Apple Is
o o
Disabled
2.5.6 Ensure Limit Ad Tracking Is Enabled o o
391 | P a g e
2.5.7 Audit Camera Privacy and Confidentiality o o
2.6.1.1 Audit iCloud Configuration o o
2.6.1.2 Audit iCloud Keychain o o
2.6.1.3 Audit iCloud Drive o o
2.6.1.4 Ensure iCloud Drive Document and Desktop Sync is
o o
Disabled
2.6.2 Audit App Store Password Settings o o
2.7.1 Ensure Backup Up Automatically is Enabled o o
2.7.2 Ensure Time Machine Volumes Are Encrypted o o
2.9 Ensure Power Nap Is Disabled o o
2.11 Ensure EFI Version Is Valid and Checked Regularly o o
2.12 Audit Automatic Actions for Optical Media o o
2.13 Audit Siri Settings o o
2.14 Audit Sidecar Settings o o
2.15 Audit Touch ID and Wallet & Apple Pay Settings o o
2.16 Audit Notification System Preference Settings o o
2.17 Audit Passwords System Preference Setting o o
3.1 Ensure Security Auditing Is Enabled o o
3.2 Ensure Security Auditing Flags Are Configured Per Local
o o
Organizational Requirements
3.3 Ensure install.log Is Retained for 365 or More Days and No
o o
Maximum Size
3.4 Ensure Security Auditing Retention Is Enabled o o
3.5 Ensure Access to Audit Records Is Controlled o o
3.6 Ensure Firewall Logging Is Enabled and Configured o o
3.7 Audit Software Inventory o o
4.1 Ensure Bonjour Advertising Services Is Disabled o o
4.3 Audit Network Specific Locations o o
4.4 Ensure HTTP Server Is Disabled o o
4.5 Ensure NFS Server Is Disabled o o
5.1.1 Ensure Home Folders Are Secure o o
5.1.2 Ensure System Integrity Protection Status (SIPS) Is Enabled o o
5.1.3 Ensure Apple Mobile File Integrity Is Enabled o o
5.1.4 Ensure Library Validation Is Enabled o o
5.1.5 Ensure Sealed System Volume (SSV) Is Enabled o o
5.1.6 Ensure Appropriate Permissions Are Enabled for System
o o
Wide Applications
5.1.7 Ensure No World Writable Files Exist in the System Folder o o
5.1.8 Ensure No World Writable Files Exist in the Library Folder o o
5.2.1 Ensure Password Account Lockout Threshold Is Configured o o
5.2.2 Ensure Password Minimum Length Is Configured o o
5.2.3 Ensure Complex Password Must Contain Alphabetic
o o
Characters Is Configured
392 | P a g e
5.2.4 Ensure Complex Password Must Contain Numeric Character
o o
Is Configured
5.2.5 Ensure Complex Password Must Contain Special Character
o o
Is Configured
5.2.6 Ensure Complex Password Must Contain Uppercase and
o o
Lowercase Characters Is Configured
5.2.7 Ensure Password Age Is Configured o o
5.2.8 Ensure Password History Is Configured o o
5.3 Ensure the Sudo Timeout Period Is Set to Zero o o
5.4 Ensure a Separate Timestamp Is Enabled for Each User/tty
o o
Combo
5.5 Ensure login keychain is locked when the computer sleeps o o
5.6 Ensure the "root" Account Is Disabled o o
5.7 Ensure Automatic Login Is Disabled o o
5.8 Ensure a Password is Required to Wake the Computer From
o o
Sleep or Screen Saver Is Enabled
5.9 Ensure system is set to hibernate o o
5.10 Require an administrator password to access system-wide
o o
preferences
5.11 Ensure an administrator account cannot login to another
o o
user's active and locked session
5.12 Ensure a Custom Message for the Login Screen Is Enabled o o
5.13 Ensure a Login Window Banner Exists o o
5.14 Ensure Users' Accounts Do Not Have a Password Hint o o
5.15 Ensure Fast User Switching Is Disabled o o
6.1.1 Ensure Login Window Displays as Name and Password Is
o o
Enabled
6.1.2 Ensure Show Password Hints Is Disabled o o
6.1.3 Ensure Guest Account Is Disabled o o
6.1.4 Ensure Guest Access to Shared Folders Is Disabled o o
6.1.5 Ensure the Guest Home Folder Does Not Exist o o
6.2 Ensure Show All Filename Extensions Setting is Enabled o o
393 | P a g e
Appendix: CIS Controls v8 IG 2 Mapped
Recommendations
Recommendation Set
Correctly
Yes No
1.1 Ensure All Apple-provided Software Is Current o o
1.2 Ensure Auto Update Is Enabled o o
1.3 Ensure Download New Updates When Available is Enabled o o
1.4 Ensure Installation of App Update Is Enabled o o
1.5 Ensure System Data Files and Security Updates Are
o o
Downloaded Automatically Is Enabled
1.6 Ensure Install of macOS Updates Is Enabled o o
1.7 Audit Computer Name o o
2.1.1 Ensure Bluetooth Is Disabled If No Devices Are Paired o o
2.1.2 Ensure Show Bluetooth Status in Menu Bar Is Enabled o o
2.2.1 Ensure "Set time and date automatically" Is Enabled o o
2.2.2 Ensure time set is within appropriate limits o o
2.3.1 Ensure an Inactivity Interval of 20 Minutes Or Less for the
o o
Screen Saver Is Enabled
2.3.2 Ensure Screen Saver Corners Are Secure o o
2.3.3 Audit Lock Screen and Start Screen Saver Tools o o
2.4.1 Ensure Remote Apple Events Is Disabled o o
2.4.2 Ensure Internet Sharing Is Disabled o o
2.4.3 Ensure Screen Sharing Is Disabled o o
2.4.4 Ensure Printer Sharing Is Disabled o o
2.4.5 Ensure Remote Login Is Disabled o o
2.4.6 Ensure DVD or CD Sharing Is Disabled o o
2.4.7 Ensure Bluetooth Sharing Is Disabled o o
2.4.8 Ensure File Sharing Is Disabled o o
2.4.9 Ensure Remote Management Is Disabled o o
2.4.10 Ensure Content Caching Is Disabled o o
2.4.11 Ensure AirDrop Is Disabled o o
2.4.12 Ensure Media Sharing Is Disabled o o
2.4.13 Ensure AirPlay Receiver Is Disabled o o
2.5.1.1 Ensure FileVault Is Enabled o o
2.5.1.2 Ensure all user storage APFS volumes are encrypted o o
2.5.1.3 Ensure all user storage CoreStorage volumes are encrypted o o
2.5.2.1 Ensure Gatekeeper is Enabled o o
2.5.2.2 Ensure Firewall Is Enabled o o
394 | P a g e
2.5.2.3 Ensure Firewall Stealth Mode Is Enabled o o
2.5.3 Ensure Location Services Is Enabled o o
2.5.4 Audit Location Services Access o o
2.5.5 Ensure Sending Diagnostic and Usage Data to Apple Is
o o
Disabled
2.5.6 Ensure Limit Ad Tracking Is Enabled o o
2.5.7 Audit Camera Privacy and Confidentiality o o
2.6.1.1 Audit iCloud Configuration o o
2.6.1.2 Audit iCloud Keychain o o
2.6.1.3 Audit iCloud Drive o o
2.6.1.4 Ensure iCloud Drive Document and Desktop Sync is
o o
Disabled
2.6.2 Audit App Store Password Settings o o
2.7.1 Ensure Backup Up Automatically is Enabled o o
2.7.2 Ensure Time Machine Volumes Are Encrypted o o
2.8 Ensure Wake for Network Access Is Disabled o o
2.9 Ensure Power Nap Is Disabled o o
2.10 Ensure Secure Keyboard Entry terminal.app is Enabled o o
2.11 Ensure EFI Version Is Valid and Checked Regularly o o
2.12 Audit Automatic Actions for Optical Media o o
2.13 Audit Siri Settings o o
2.14 Audit Sidecar Settings o o
2.15 Audit Touch ID and Wallet & Apple Pay Settings o o
2.16 Audit Notification System Preference Settings o o
2.17 Audit Passwords System Preference Setting o o
3.1 Ensure Security Auditing Is Enabled o o
3.2 Ensure Security Auditing Flags Are Configured Per Local
o o
Organizational Requirements
3.3 Ensure install.log Is Retained for 365 or More Days and No
o o
Maximum Size
3.4 Ensure Security Auditing Retention Is Enabled o o
3.5 Ensure Access to Audit Records Is Controlled o o
3.6 Ensure Firewall Logging Is Enabled and Configured o o
3.7 Audit Software Inventory o o
4.1 Ensure Bonjour Advertising Services Is Disabled o o
4.2 Ensure Show Wi-Fi status in Menu Bar Is Enabled o o
4.3 Audit Network Specific Locations o o
4.4 Ensure HTTP Server Is Disabled o o
4.5 Ensure NFS Server Is Disabled o o
4.6 Audit Wi-Fi Settings o o
5.1.1 Ensure Home Folders Are Secure o o
5.1.2 Ensure System Integrity Protection Status (SIPS) Is Enabled o o
5.1.3 Ensure Apple Mobile File Integrity Is Enabled o o
395 | P a g e
5.1.4 Ensure Library Validation Is Enabled o o
5.1.5 Ensure Sealed System Volume (SSV) Is Enabled o o
5.1.6 Ensure Appropriate Permissions Are Enabled for System
o o
Wide Applications
5.1.7 Ensure No World Writable Files Exist in the System Folder o o
5.1.8 Ensure No World Writable Files Exist in the Library Folder o o
5.2.1 Ensure Password Account Lockout Threshold Is Configured o o
5.2.2 Ensure Password Minimum Length Is Configured o o
5.2.3 Ensure Complex Password Must Contain Alphabetic
o o
Characters Is Configured
5.2.4 Ensure Complex Password Must Contain Numeric Character
o o
Is Configured
5.2.5 Ensure Complex Password Must Contain Special Character
o o
Is Configured
5.2.6 Ensure Complex Password Must Contain Uppercase and
o o
Lowercase Characters Is Configured
5.2.7 Ensure Password Age Is Configured o o
5.2.8 Ensure Password History Is Configured o o
5.3 Ensure the Sudo Timeout Period Is Set to Zero o o
5.4 Ensure a Separate Timestamp Is Enabled for Each User/tty
o o
Combo
5.5 Ensure login keychain is locked when the computer sleeps o o
5.6 Ensure the "root" Account Is Disabled o o
5.7 Ensure Automatic Login Is Disabled o o
5.8 Ensure a Password is Required to Wake the Computer From
o o
Sleep or Screen Saver Is Enabled
5.9 Ensure system is set to hibernate o o
5.10 Require an administrator password to access system-wide
o o
preferences
5.11 Ensure an administrator account cannot login to another
o o
user's active and locked session
5.12 Ensure a Custom Message for the Login Screen Is Enabled o o
5.13 Ensure a Login Window Banner Exists o o
5.14 Ensure Users' Accounts Do Not Have a Password Hint o o
5.15 Ensure Fast User Switching Is Disabled o o
6.1.1 Ensure Login Window Displays as Name and Password Is
o o
Enabled
6.1.2 Ensure Show Password Hints Is Disabled o o
6.1.3 Ensure Guest Account Is Disabled o o
6.1.4 Ensure Guest Access to Shared Folders Is Disabled o o
6.1.5 Ensure the Guest Home Folder Does Not Exist o o
6.2 Ensure Show All Filename Extensions Setting is Enabled o o
7.2 FileVault and Local Account Password Reset using AppleID o o
396 | P a g e
397 | P a g e
Appendix: CIS Controls v8 IG 3 Mapped
Recommendations
Recommendation Set
Correctly
Yes No
1.1 Ensure All Apple-provided Software Is Current o o
1.2 Ensure Auto Update Is Enabled o o
1.3 Ensure Download New Updates When Available is Enabled o o
1.4 Ensure Installation of App Update Is Enabled o o
1.5 Ensure System Data Files and Security Updates Are
o o
Downloaded Automatically Is Enabled
1.6 Ensure Install of macOS Updates Is Enabled o o
1.7 Audit Computer Name o o
2.1.1 Ensure Bluetooth Is Disabled If No Devices Are Paired o o
2.1.2 Ensure Show Bluetooth Status in Menu Bar Is Enabled o o
2.2.1 Ensure "Set time and date automatically" Is Enabled o o
2.2.2 Ensure time set is within appropriate limits o o
2.3.1 Ensure an Inactivity Interval of 20 Minutes Or Less for the
o o
Screen Saver Is Enabled
2.3.2 Ensure Screen Saver Corners Are Secure o o
2.3.3 Audit Lock Screen and Start Screen Saver Tools o o
2.4.1 Ensure Remote Apple Events Is Disabled o o
2.4.2 Ensure Internet Sharing Is Disabled o o
2.4.3 Ensure Screen Sharing Is Disabled o o
2.4.4 Ensure Printer Sharing Is Disabled o o
2.4.5 Ensure Remote Login Is Disabled o o
2.4.6 Ensure DVD or CD Sharing Is Disabled o o
2.4.7 Ensure Bluetooth Sharing Is Disabled o o
2.4.8 Ensure File Sharing Is Disabled o o
2.4.9 Ensure Remote Management Is Disabled o o
2.4.10 Ensure Content Caching Is Disabled o o
2.4.11 Ensure AirDrop Is Disabled o o
2.4.12 Ensure Media Sharing Is Disabled o o
2.4.13 Ensure AirPlay Receiver Is Disabled o o
2.5.1.1 Ensure FileVault Is Enabled o o
2.5.1.2 Ensure all user storage APFS volumes are encrypted o o
2.5.1.3 Ensure all user storage CoreStorage volumes are encrypted o o
2.5.2.1 Ensure Gatekeeper is Enabled o o
2.5.2.2 Ensure Firewall Is Enabled o o
398 | P a g e
2.5.2.3 Ensure Firewall Stealth Mode Is Enabled o o
2.5.3 Ensure Location Services Is Enabled o o
2.5.4 Audit Location Services Access o o
2.5.5 Ensure Sending Diagnostic and Usage Data to Apple Is
o o
Disabled
2.5.6 Ensure Limit Ad Tracking Is Enabled o o
2.5.7 Audit Camera Privacy and Confidentiality o o
2.6.1.1 Audit iCloud Configuration o o
2.6.1.2 Audit iCloud Keychain o o
2.6.1.3 Audit iCloud Drive o o
2.6.1.4 Ensure iCloud Drive Document and Desktop Sync is
o o
Disabled
2.6.2 Audit App Store Password Settings o o
2.7.1 Ensure Backup Up Automatically is Enabled o o
2.7.2 Ensure Time Machine Volumes Are Encrypted o o
2.8 Ensure Wake for Network Access Is Disabled o o
2.9 Ensure Power Nap Is Disabled o o
2.10 Ensure Secure Keyboard Entry terminal.app is Enabled o o
2.11 Ensure EFI Version Is Valid and Checked Regularly o o
2.12 Audit Automatic Actions for Optical Media o o
2.13 Audit Siri Settings o o
2.14 Audit Sidecar Settings o o
2.15 Audit Touch ID and Wallet & Apple Pay Settings o o
2.16 Audit Notification System Preference Settings o o
2.17 Audit Passwords System Preference Setting o o
3.1 Ensure Security Auditing Is Enabled o o
3.2 Ensure Security Auditing Flags Are Configured Per Local
o o
Organizational Requirements
3.3 Ensure install.log Is Retained for 365 or More Days and No
o o
Maximum Size
3.4 Ensure Security Auditing Retention Is Enabled o o
3.5 Ensure Access to Audit Records Is Controlled o o
3.6 Ensure Firewall Logging Is Enabled and Configured o o
3.7 Audit Software Inventory o o
4.1 Ensure Bonjour Advertising Services Is Disabled o o
4.2 Ensure Show Wi-Fi status in Menu Bar Is Enabled o o
4.3 Audit Network Specific Locations o o
4.4 Ensure HTTP Server Is Disabled o o
4.5 Ensure NFS Server Is Disabled o o
4.6 Audit Wi-Fi Settings o o
5.1.1 Ensure Home Folders Are Secure o o
5.1.2 Ensure System Integrity Protection Status (SIPS) Is Enabled o o
5.1.3 Ensure Apple Mobile File Integrity Is Enabled o o
399 | P a g e
5.1.4 Ensure Library Validation Is Enabled o o
5.1.5 Ensure Sealed System Volume (SSV) Is Enabled o o
5.1.6 Ensure Appropriate Permissions Are Enabled for System
o o
Wide Applications
5.1.7 Ensure No World Writable Files Exist in the System Folder o o
5.1.8 Ensure No World Writable Files Exist in the Library Folder o o
5.2.1 Ensure Password Account Lockout Threshold Is Configured o o
5.2.2 Ensure Password Minimum Length Is Configured o o
5.2.3 Ensure Complex Password Must Contain Alphabetic
o o
Characters Is Configured
5.2.4 Ensure Complex Password Must Contain Numeric Character
o o
Is Configured
5.2.5 Ensure Complex Password Must Contain Special Character
o o
Is Configured
5.2.6 Ensure Complex Password Must Contain Uppercase and
o o
Lowercase Characters Is Configured
5.2.7 Ensure Password Age Is Configured o o
5.2.8 Ensure Password History Is Configured o o
5.3 Ensure the Sudo Timeout Period Is Set to Zero o o
5.4 Ensure a Separate Timestamp Is Enabled for Each User/tty
o o
Combo
5.5 Ensure login keychain is locked when the computer sleeps o o
5.6 Ensure the "root" Account Is Disabled o o
5.7 Ensure Automatic Login Is Disabled o o
5.8 Ensure a Password is Required to Wake the Computer From
o o
Sleep or Screen Saver Is Enabled
5.9 Ensure system is set to hibernate o o
5.10 Require an administrator password to access system-wide
o o
preferences
5.11 Ensure an administrator account cannot login to another
o o
user's active and locked session
5.12 Ensure a Custom Message for the Login Screen Is Enabled o o
5.13 Ensure a Login Window Banner Exists o o
5.14 Ensure Users' Accounts Do Not Have a Password Hint o o
5.15 Ensure Fast User Switching Is Disabled o o
6.1.1 Ensure Login Window Displays as Name and Password Is
o o
Enabled
6.1.2 Ensure Show Password Hints Is Disabled o o
6.1.3 Ensure Guest Account Is Disabled o o
6.1.4 Ensure Guest Access to Shared Folders Is Disabled o o
6.1.5 Ensure the Guest Home Folder Does Not Exist o o
6.2 Ensure Show All Filename Extensions Setting is Enabled o o
7.2 FileVault and Local Account Password Reset using AppleID o o
400 | P a g e
401 | P a g e
Appendix: Change History
Date Version Changes for this version
402 | P a g e