kriterion 0.0.1

data/standards/stig_apple_os_x_10.11.json

@@ -0,0 +1,725 @@
+{
+  "name": "stig_apple_os_x_10.11",
+  "date": "2018-01-04",
+  "description": "This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.",
+  "title": "Apple OS X 10.11 Security Technical Implementation Guide",
+  "version": "1",
+  "item_syntax": "^\\w-\\d+$",
+  "section_separator": null,
+  "items": [
+    {
+      "id": "V-67461",
+      "title": "The operating system must conceal, via the session lock, information previously visible on the display with a publicly viewable image.",
+      "description": "A default screensaver must be configured for all users, as the screensaver will act as a session time-out lock for the system and must be one that conceals the contents of the screen from unauthorized users. The screensaver must not display any sensitive information or reveal the contents of the locked session screen. Publicly viewable images can include static or dynamic images such as patterns used with screen savers, photographic images, solid colors, a clock, a battery life indicator, or a blank screen.",
+      "severity": "low"
+    },
+    {
+      "id": "V-67463",
+      "title": "The operating system must initiate a session lock after a 15-minute period of inactivity.",
+      "description": "A screensaver must be enabled and set to require a password to unlock. The timeout should be set to fifteen minutes of inactivity. This mitigates the risk that a user might forget to manually lock the screen before stepping away from the computer.\n\nA session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system, but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67465",
+      "title": "The operating system must retain the session lock until the user reestablishes access using established identification and authentication procedures.",
+      "description": "Users must be prompted to enter their passwords when unlocking the screensaver. The screensaver acts as a session lock and prevents unauthorized users from accessing the current user's account.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67467",
+      "title": "The operating system must monitor remote access methods.",
+      "description": "Remote access services, such as those providing remote access to network devices and information systems, increase risk and expose those systems to possible cyber attacks, so all remote access should be closely monitored and audited. Only authorized users should be permitted to remotely access DoD non-public information systems. An attacker might attempt to log in as an authorized user, through stolen credentials, unpatched exploits of the remote access service, or brute force attempts to guess a valid username and password. If a user is attempting to log in to a system from an unusual location or at an unusual time, or if there are many failed attempts, there is a possibility that the system is the target of a cyber attack. Auditing logon events mitigates this risk by recording all logon attempts, successful and unsuccessful, to the system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67469",
+      "title": "The operating system must, for networked systems, compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).",
+      "description": "Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside of the configured acceptable allowance (drift) may be inaccurate.\n\nSynchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. \n\nOrganizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67471",
+      "title": "Audit log files must be owned by root.",
+      "description": "The audit service must be configured to create log files with the correct ownership to prevent normal users from reading audit logs. Audit logs contain sensitive data about the system and about users. If log files are set to only be readable and writable by root or administrative users with sudo, the risk is mitigated.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67473",
+      "title": "Audit log folders must be owned by root.",
+      "description": "The audit service must be configured to create log files with the correct ownership to prevent normal users from reading audit logs. Audit logs contain sensitive data about the system and about users. If log files are set to only be readable and writable by root or administrative users with sudo, the risk is mitigated.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67475",
+      "title": "Audit log files must be group-owned by wheel.",
+      "description": "The audit service must be configured to create log files with the correct group-ownership to prevent normal users from reading audit logs. Audit logs contain sensitive data about the system and about users. If log files are set to only be readable and writable by root or administrative users with sudo, the risk is mitigated.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67477",
+      "title": "Audit log folders must be group-owned by wheel.",
+      "description": "The audit service must be configured to create log files with the correct group-ownership to prevent normal users from reading audit logs. Audit logs contain sensitive data about the system and about users. If log files are set to only be readable and writable by root or administrative users with sudo, the risk is mitigated.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67479",
+      "title": "Audit log files must be mode 440 or less permissive.",
+      "description": "The audit service must be configured to create log files with the correct permissions to prevent normal users from reading audit logs. Audit logs contain sensitive data about the system and about users. If log files are set to only be readable and writable by root or administrative users with sudo, the risk is mitigated.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67481",
+      "title": "Audit log folders must have mode 700 or less permissive.",
+      "description": "The audit service must be configured to create log folders with the correct permissions to prevent normal users from reading audit logs. Audit logs contain sensitive data about the system and about users. If log folders are set to only be readable and writable by root or administrative users with sudo, the risk is mitigated.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67483",
+      "title": "Log files must not contain ACLs.",
+      "description": "The audit service must be configured to create log files with the correct permissions to prevent normal users from reading audit logs. Audit logs contain sensitive data about the system and about users. If log files are set to only be readable and writable by root or administrative users with sudo, the risk is mitigated.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67485",
+      "title": "Log folders must not contain ACLs.",
+      "description": "The audit service must be configured to create log folders with the correct permissions to prevent normal users from reading audit logs. Audit logs contain sensitive data about the system and about users. If log folders are set to only be readable and writable by root or administrative users with sudo, the risk is mitigated.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67487",
+      "title": "The operating system must implement DoD-approved encryption to protect the confidentiality of remote access sessions.",
+      "description": "The rexec service must be disabled. The rexec service does not implement crypto and has had several security vulnerabilities in the past. It is disabled by default; enabling it would increase the attack surface of the system.\n\nWithout confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. \n\nRemote access is access to DoD non-public information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.\n\nEncryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection (e.g., RDP) thereby providing a degree of confidentiality. The encryption strength of mechanism is selected based on the security categorization of the information.",
+      "severity": "high"
+    },
+    {
+      "id": "V-67491",
+      "title": "The rshd service must be disabled.",
+      "description": "It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled.\n\nThe \"rshd\" service must be disabled.",
+      "severity": "high"
+    },
+    {
+      "id": "V-67493",
+      "title": "The operating system must enforce requirements for remote connections to the information system.",
+      "description": "The Screen Sharing feature allows remote users to view or control the desktop of the current user. A malicious user can take advantage of screen sharing to gain full access to the system remotely, either with stolen credentials or by guessing the username and password. Disabling Screen Sharing mitigates this risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67495",
+      "title": "The Bluetooth software driver must be disabled.",
+      "description": "The Bluetooth kernel extension must be disabled, as wireless access introduces unnecessary security risks. Disabling Bluetooth support with a configuration profile mitigates this risk.",
+      "severity": "low"
+    },
+    {
+      "id": "V-67497",
+      "title": "Wi-Fi support software must be disabled.",
+      "description": "Use of Wi-Fi to connect to unauthorized networks may facilitate the exfiltration of mission data.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67499",
+      "title": "Infrared [IR] support must be disabled.",
+      "description": "Infrared [IR] kernel support must be disabled to prevent users from controlling the system with IR devices. By default, if IR is enabled, the system will accept IR control from any remote.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67501",
+      "title": "Automatic actions must be disabled for blank CDs.",
+      "description": "Applications should not be configured to launch automatically when a disk is inserted. This potentially circumvents anti-virus software and allows malicious users to craft disks that can exploit user applications. Disabling Automatic Actions for blank CDs mitigates this risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67503",
+      "title": "Automatic actions must be disabled for blank DVDs.",
+      "description": "Applications should not be configured to launch automatically when a disk is inserted. This potentially circumvents anti-virus software and allows malicious users to craft disks that can exploit user applications. Disabling Automatic Actions for blank DVDs mitigates this risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67505",
+      "title": "Automatic actions must be disabled for music CDs.",
+      "description": "Applications should not be configured to launch automatically when a disk is inserted. This potentially circumvents anti-virus software and allows malicious users to craft disks that can exploit user applications. Disabling Automatic Actions for music CDs mitigates this risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67507",
+      "title": "Automatic actions must be disabled for picture CDs.",
+      "description": "Applications should not be configured to launch automatically when a disk is inserted. This potentially circumvents anti-virus software and allows malicious users to craft disks that can exploit user applications. Disabling Automatic Actions for picture CDs mitigates this risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67509",
+      "title": "Automatic actions must be disabled for video DVDs.",
+      "description": "Applications should not be configured to launch automatically when a disk is inserted. This potentially circumvents anti-virus software and allows malicious users to craft disks that can exploit user applications. Disabling Automatic Actions for video DVDs mitigates this risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67511",
+      "title": "The operating system must automatically remove or disable temporary user accounts after 72 hours.",
+      "description": "If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be targeted by attackers to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation.\n\nTemporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation.\n\nIf temporary accounts are used, the operating system must be configured to automatically terminate these types of accounts after a DoD-defined time period of 72 hours.\n\nTo address access requirements, many operating systems may be integrated with enterprise level authentication/access mechanisms that meet or exceed access control policy requirements.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67513",
+      "title": "The operating system must provide an immediate real-time alert to the SA and ISSO, at a minimum, of all audit failure events requiring real-time alerts.",
+      "description": "The audit service should be configured to immediately print messages to the console or email administrator users when an auditing failure occurs. It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an impending failure of the audit capability and system operation may be adversely affected.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67515",
+      "title": "The operating system must provide an immediate warning to the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of repository maximum audit record storage capacity.",
+      "description": "The audit service must be configured to require a minimum percentage of free disk space in order to run. This ensures that audit will notify the administrator that action is required to free up more disk space for audit logs.\n\nWhen minfree is set to 25%, security personnel are notified immediately when the storage volume is 75% full and are able to plan for audit record storage capacity expansion.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67517",
+      "title": "The operating system must allocate audit record storage capacity to store at least one weeks worth of audit records, when audit records are not immediately sent to a central audit record storage facility.",
+      "description": "The audit service must be configured to require that records are kept for 7 days or longer before deletion when there is no central audit record storage facility. When \"expire-after\" is set to \"7d\", the audit service will not delete audit logs until the log data is at least 7 days old.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67521",
+      "title": "The operating system must be configured such that emergency administrator accounts are never automatically disabled.",
+      "description": "Emergency administrator accounts are privileged accounts which are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability.\n\nEmergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts also remain available and are not subject to automatic termination dates. However, an emergency administrator account is normally a different account which is created for use by vendors or system maintainers.\n\nTo address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67523",
+      "title": "The operating system must generate audit records for all account creations, modifications, disabling, and termination events, for privileged activities or other system-level access, all kernel module load, unload, and restart actions, all program initiations, and organizationally defined events for all non-local maintenance and diagnostic sessions.",
+      "description": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter).\n\nSatisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000327-GPOS-00127, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000476-GPOS-00221, SRG-OS-000477-GPOS-00222",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67531",
+      "title": "SMB File Sharing must be disabled unless required.",
+      "description": "File Sharing is usually non-essential and must be disabled if not required. Enabling any service increases the attack surface for an intruder. By disabling unnecessary services, the attack surface is minimized.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67533",
+      "title": "Apple File (AFP) Sharing must be disabled.",
+      "description": "File Sharing is non-essential and must be disabled. Enabling any service increases the attack surface for an intruder. By disabling unnecessary services, the attack surface is minimized.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67535",
+      "title": "The NFS daemon must be disabled unless required.",
+      "description": "If the system does not require access to NFS (Network File System) file shares or is not acting as an NFS server, then support for NFS is non-essential and NFS services must be disabled. NFS is a network file system protocol supported by Unix-like operating systems. Enabling any service increases the attack surface for an intruder. By disabling unnecessary services, the attack surface is minimized.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67537",
+      "title": "The NFS lock daemon must be disabled unless required.",
+      "description": "If the system does not require access to NFS (Network File System) file shares or is not acting as an NFS server, then support for NFS is non-essential and NFS services must be disabled. NFS is a network file system protocol supported by Unix-like operating systems. Enabling any service increases the attack surface for an intruder. By disabling unnecessary services, the attack surface is minimized.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67539",
+      "title": "The NFS stat daemon must be disabled unless required.",
+      "description": "If the system does not require access to NFS (Network File System) file shares or is not acting as an NFS server, then support for NFS is non-essential and NFS services must be disabled. NFS is a network file system protocol supported by Unix-like operating systems. Enabling any service increases the attack surface for an intruder. By disabling unnecessary services, the attack surface is minimized.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67541",
+      "title": "The system firewall must be configured with a default-deny policy.",
+      "description": "An approved firewall must be installed and enabled to work in concert with the OS X Application Firewall. When configured correctly, firewalls protect computers from network attacks by blocking or limiting access to open network ports.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67547",
+      "title": "The SSH banner must contain the Standard Mandatory DoD Notice and Consent Banner.",
+      "description": "Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n\nSystem use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.\n\nThe banner must be formatted in accordance with DTM-08-060.",
+      "severity": "low"
+    },
+    {
+      "id": "V-67551",
+      "title": "The operating system must initiate session audits at system startup.",
+      "description": "If auditing is enabled late in the startup process, the actions of some start-up processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67553",
+      "title": "The operating system must generate audit records for DoD defined events such as: successful/unsuccessful logon attempts, successful/unsuccessful direct access attempts, starting and ending time for user access, and concurrent logons to the same account from different sources.",
+      "description": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.\nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\n\nSatisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67555",
+      "title": "Any connection to the operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.",
+      "description": "Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n\nSystem use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.\n\nThe banner must be formatted in accordance with DTM-08-060.\n\nSatisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67557",
+      "title": "The operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system via SSH.",
+      "description": "Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n\nSystem use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.\n\nThe banner must be formatted in accordance with DTM-08-060.",
+      "severity": "low"
+    },
+    {
+      "id": "V-67559",
+      "title": "The Security assessment policy subsystem must be enabled.",
+      "description": "Any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have significant effects on the overall security of the system.\n\nAccordingly, software defined by the organization as critical software must be signed with a certificate that is recognized and approved by the organization.",
+      "severity": "high"
+    },
+    {
+      "id": "V-67561",
+      "title": "The operating system must limit privileges to change software resident within software libraries.",
+      "description": "File permissions should be compared against the default set of permissions that were set at the time of the initial install. Changes to default file permissions can make the system less secure and disrupt the functionality of installed applications. Unless changes are required to harden a system, the default permissions should be kept. If the operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. Verifying that permissions remain unchanged mitigates this risk.\n\nThis requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67563",
+      "title": "A configuration profile must be installed.",
+      "description": "Configuration settings must be verified by a centrally managed system such as an MDM to ensure that they have not been changed. Configuration settings are the configurable security-related parameters of information technology products that are part of the information system. Security-related parameters are those parameters impacting the security state of the system including parameters related to meeting other security control requirements. Rather than visiting each and every system when verifying configuration changes, organizations will employ automated tools that can make changes across all systems.  This greatly increases efficiency and manageability of applications in a large scale environment.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67565",
+      "title": "The operating system must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.",
+      "description": "Application Restrictions must be enabled for user accounts and configured to only allow users to execute approved applications. Utilizing a whitelist such as Application Restrictions provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities.\n\nThe organization must identify authorized software programs and permit execution of authorized software. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67567",
+      "title": "The application FaceTime must be disabled.",
+      "description": "It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled.\n\nThe application FaceTime establishes connections to Apple's iCloud, despite using security controls to disable iCloud access.",
+      "severity": "low"
+    },
+    {
+      "id": "V-67569",
+      "title": "The application Game Center must be disabled.",
+      "description": "It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled.\n\nThe application Game Center establishes connections to Apple's iCloud, despite using security controls to disable iCloud access.",
+      "severity": "low"
+    },
+    {
+      "id": "V-67571",
+      "title": "The application Messages must be disabled.",
+      "description": "It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled.\n\nThe application Messages establishes connections to Apple's iCloud, despite using security controls to disable iCloud access.",
+      "severity": "low"
+    },
+    {
+      "id": "V-67573",
+      "title": "The application Calendar must be disabled.",
+      "description": "It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled.\n\nThe application Calendar establishes connections to Apple's iCloud, despite using security controls to disable iCloud access.",
+      "severity": "low"
+    },
+    {
+      "id": "V-67575",
+      "title": "The application Reminders must be disabled.",
+      "description": "It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled.\n\nThe application Reminders establishes connections to Apple's iCloud, despite using security controls to disable iCloud access.",
+      "severity": "low"
+    },
+    {
+      "id": "V-67577",
+      "title": "The application Contacts must be disabled.",
+      "description": "It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled.\n\nThe application Contacts establishes connections to Apple's iCloud, despite using security controls to disable iCloud access.",
+      "severity": "low"
+    },
+    {
+      "id": "V-67579",
+      "title": "The application Mail must be disabled.",
+      "description": "It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled.\n\nThe application Mail establishes connections to Apple's iCloud, despite using security controls to disable iCloud access.",
+      "severity": "low"
+    },
+    {
+      "id": "V-67581",
+      "title": "The application Notes must be disabled.",
+      "description": "It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled.\n\nThe application Notes establishes connections to Apple's iCloud, despite using security controls to disable iCloud access.",
+      "severity": "low"
+    },
+    {
+      "id": "V-67583",
+      "title": "The system preference panels iCloud and Internet Accounts must be disabled.",
+      "description": "It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled.\n\nThe system preference panel's iCloud and Internet Accounts must be disabled.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67585",
+      "title": "Sending diagnostic and usage data to Apple must be disabled.",
+      "description": "In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. \n\nTo support the requirements and principles of least functionality, the operating system must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.\n\nSending diagnostic and usage data to Apple must be disabled.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67587",
+      "title": "Find My Mac must be disabled.",
+      "description": "In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. \n\nTo support the requirements and principles of least functionality, the operating system must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.\n\nFind My Mac must be disabled.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67589",
+      "title": "Find My Mac messenger must be disabled.",
+      "description": "In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. \n\nTo support the requirements and principles of least functionality, the operating system must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.\n\nFind My Mac messenger must be disabled.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67591",
+      "title": "Location Services must be disabled.",
+      "description": "In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. \n\nTo support the requirements and principles of least functionality, the operating system must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.\n\nLocation Services must be disabled.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67593",
+      "title": "Bonjour multicast advertising must be disabled on the system.",
+      "description": "In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. \n\nTo support the requirements and principles of least functionality, the operating system must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.\n\nBonjour multicast advertising must be disabled on the system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67595",
+      "title": "The UUCP service must be disabled.",
+      "description": "It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled.\n\nThe system must not have the UUCP service active.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67597",
+      "title": "The operating system must require individuals to be authenticated with an individual authenticator prior to using a group authenticator.",
+      "description": "Administrator users must never log in directly as root. To assure individual accountability and prevent unauthorized access, logging in as root over a remote connection must be disabled. Administrators should only run commands as root after first authenticating with their individual user names and passwords.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67599",
+      "title": "The operating system must implement replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.",
+      "description": "The SSH Version should be explicitly set to Version 2. Version 2 supports strong crypto and was rewritten from scratch to resolve several weaknesses in Version 1 that make it extremely vulnerable to attackers. The weaker crypto in Version 1 is potentially susceptible to certain forms of replay attacks. The system default is to only enable Version 2.\n\nA replay attack may enable an unauthorized user to gain access to the operating system. Authentication sessions between the authenticator and the operating system validating the user credentials must not be vulnerable to a replay attack. An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message.\n\nSatisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67603",
+      "title": "Operating systems must enforce password complexity by requiring that at least one numeric character be used.",
+      "description": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.\n\nPassword complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67605",
+      "title": "The operating system must enforce password complexity by requiring that at least one special character be used.",
+      "description": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity or strength is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor in determining how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Special characters are those characters that are not alphanumeric. Examples include: ~ ! @ # $ % ^ *.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67607",
+      "title": "The operating system must enforce a minimum 15-character password length.",
+      "description": "The minimum password length must be set to 15 characters. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. The use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67609",
+      "title": "The operating system must implement cryptography to protect the integrity and confidentiality of data during transmission of remote access sessions, non-local maintenance sessions, and diagnostic communications.\n",
+      "description": "The \"telnet\" service must be disabled as it sends all data in a clear text form that can be easily intercepted and read. The data needs to be protected at all times during transmission and encryption is the standard method for protecting data in transit. If the data is not encrypted during transmission, it can be plainly read (i.e., clear text) and easily compromised. Disabling telnet is one way to mitigate this risk. Administrators should be instructed to use an alternate service for remote access sessions, non-local maintenance sessions, and diagnostic communications that uses encryption, such as SSH.\n\nSatisfies: SRG-OS-000074-GPOS-00042, SRG-OS-000125-GPOS-00065, SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174",
+      "severity": "high"
+    },
+    {
+      "id": "V-67617",
+      "title": "The system must allow only applications downloaded from the App Store to run.",
+      "description": "Gatekeeper settings must be configured correctly to only allow the system to run applications downloaded from the Mac App Store or applications signed with a valid Apple Developer ID code. Administrator users will still have the option to override these settings on a per app basis. Gatekeeper is a security feature that ensures that applications must be digitally signed by an Apple issued certificate in order to run. Digital signatures allow the OS X to verify that the application has not been modified by a malicious third-party.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67619",
+      "title": "End users must not be able to override Gatekeeper settings.",
+      "description": "\"Gatekeeper\" must be configured with a configuration profile in order to prevent normal users from overriding its setting. If users are allowed to disable Gatekeeper or set it to a less restrictive setting, then it is possible that malware could be introduced into the system. Gatekeeper is a security feature that ensures that applications must be digitally signed by an Apple issued certificate in order to run. Digital signatures allow Mac OS X to verify that the application has not been modified by a malicious third-party.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67621",
+      "title": "The SSH daemon ClientAliveInterval option must be set correctly.",
+      "description": "SSH should be configured to log users out after a \"15\" minute interval of inactivity and to only wait \"30\" seconds before timing out login attempts. Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session or an incomplete login attempt will also free up resources committed by the managed network element.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67623",
+      "title": "The SSH daemon ClientAliveCountMax option must be set correctly.",
+      "description": "SSH should be configured to log users out after a \"15\" minute interval of inactivity and to only wait \"30\" seconds before timing out login attempts. Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session or an incomplete login attempt will also free up resources committed by the managed network element.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67649",
+      "title": "The operating system must audit the enforcement actions used to restrict access associated with changes to the system.",
+      "description": "By auditing access restriction enforcement, changes to application and OS configuration files can be audited. Without auditing the enforcement of access restrictions, it will be difficult to identify attempted attacks and an audit trail will not be available for forensic investigation.\n\nEnforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67651",
+      "title": "ACLs for system log files must be set correctly.",
+      "description": "System logs should only be readable by root or admin users. System logs frequently contain sensitive information that could be used by an attacker. Setting the correct ACLs mitigates this risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67653",
+      "title": "System log files must be mode 640 or less permissive.",
+      "description": "System logs should only be readable by root or admin users. System logs frequently contain sensitive information that could be used by an attacker. Setting the correct permissions mitigates this risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67655",
+      "title": "System log files must be owned by root and group-owned by wheel or admin.",
+      "description": "System logs should only be readable by root or admin users. System logs frequently contain sensitive information that could be used by an attacker. Setting the correct owner mitigates this risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67657",
+      "title": "The operating system must generate audit records when successful/unsuccessful attempts to access/modify privileges occur.",
+      "description": "Frequently, an attacker that successfully gains access to a system has only gained access to an account with limited privileges, such as a guest account or a service account. The attacker must attempt to change to another user account with normal or elevated privileges in order to proceed. Auditing successful and unsuccessful attempts to switch to another user account and the escalation of privileges mitigates this risk.\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67661",
+      "title": "The operating system must prohibit password reuse for a minimum of five generations.",
+      "description": "Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed as per policy requirements.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67663",
+      "title": "Operating systems must enforce a 60-day maximum password lifetime restriction.",
+      "description": "Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically.\n\nOne method of minimizing this risk is to use complex passwords and periodically change them. If the operating system does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the operating system passwords could be compromised.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67671",
+      "title": "The system must be integrated into a directory services infrastructure.",
+      "description": "Distinct user account databases on each separate system cause problems with username and password policy enforcement. Most approved directory services infrastructure solutions allow centralized management of users and passwords.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67673",
+      "title": "All users must use PKI authentication for login and privileged access.",
+      "description": "Password-based authentication has become a prime target for malicious actors. Multifactor authentication using PKI technologies mitigates most, if not all, risks associated with traditional password use. (Use of username and password for last-resort emergency access to a system for maintenance is acceptable, however.)",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67675",
+      "title": "AirDrop must be disabled.",
+      "description": "In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. \n\nTo support the requirements and principles of least functionality, the operating system must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.\n\nAirDrop must be disabled.",
+      "severity": "low"
+    },
+    {
+      "id": "V-67677",
+      "title": "The SSH daemon LoginGraceTime must be set correctly.",
+      "description": "SSH should be configured to log users out after a 15 minute interval of inactivity and to only wait 30 seconds before timing out login attempts. Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session or an incomplete login attempt will also free up resources committed by the managed network element.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67679",
+      "title": "The operating system must issue or obtain public key certificates under an appropriate certificate policy from an approved service provider.",
+      "description": "DoD-approved certificates must be installed to the System Keychain so that they will be available to all users.\n\nFor user certificates, each organization attains certificates from an approved, shared service provider, as required by OMB policy. For federal agencies operating a legacy public key infrastructure cross-certified with the Federal Bridge Certification Authority at medium assurance or higher, this Certification Authority will suffice. This control focuses on certificates with a visibility external to the information system and does not include certificates related to internal system operations, for example, application-specific time services.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67681",
+      "title": "The operating system must implement cryptographic mechanisms to protect the confidentiality and integrity of all information at rest.",
+      "description": "Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive) within an organizational information system. Mobile devices, laptops, desktops, and storage devices can be either lost or stolen, and the contents of their data storage (e.g., hard drives and non-volatile memory) can be read, copied, or altered. By encrypting the system hard drive, the confidentiality and integrity of any data stored on the system is ensured. FileVault Disk Encryption mitigates this risk. \n\nSatisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67687",
+      "title": "The operating system must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where HBSS is used; 30 days, for any additional internal network scans not covered by HBSS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP).",
+      "description": "An approved tool for continuous network scanning must be installed and configured to run.\n\nWithout the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws.\n\nTo support this requirement, the operating system may have an integrated solution incorporating continuous scanning using HBSS and periodic scanning using other tools, as specified in the requirement.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67689",
+      "title": "The operating system must restrict the ability of individuals to use USB storage devices.",
+      "description": "External hard drives, such as USB, must be disabled for users. USB hard drives are a potential vector for malware and can be used to exfiltrate sensitive data, if an approved data-loss prevention (DLP) solution is not installed.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67691",
+      "title": "The usbmuxd daemon must be disabled.",
+      "description": "Connections to unauthorized iOS devices (iPhones, iPods, and iPads) open the system to possible compromise via exfiltration of system data. Disabling the usbmuxd daemon blocks connections to iOS devices.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67693",
+      "title": "The operating system must automatically lock the account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are exceeded.",
+      "description": "By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account. Setting a lockout expiration of 15 minutes is an effective deterrent against brute forcing that also makes allowances for legitimate mistakes by users.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67695",
+      "title": "The operating system must shut down by default upon audit failure (unless availability is an overriding concern).",
+      "description": "The audit service should shut down the computer if it is unable to audit system events. Once audit failure occurs, user and system activity is no longer recorded and malicious activity could go undetected. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.\n\nWhen availability is an overriding concern, other approved actions in response to an audit failure are as follows: \n\n(i) If the failure was caused by the lack of audit record storage capacity, the operating system must continue generating audit records if possible (automatically restarting the audit service if necessary), overwriting the oldest audit records in a first-in-first-out manner. \n\n(ii) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, the operating system must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67697",
+      "title": "The operating system must not allow an unattended or automatic logon to the system.",
+      "description": "When automatic logins are enabled, the default user account is automatically logged in at boot time without prompting the user for a password. Even if the screen is later locked, a malicious user would be able to reboot the computer in order to log in. Disabling automatic logins mitigates this risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67699",
+      "title": "The login window must be configured to prompt for username and password, rather than show a list of users.",
+      "description": "The login window must be configured to prompt all users for both a username and a password. By default, the system displays a list of known users at the login screen. This gives an advantage to an attacker with physical access to the system, as the attacker would only have to guess the password for one of the listed accounts.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67701",
+      "title": "The OS X firewall must have logging enabled.",
+      "description": "Firewall logging must be enabled. This ensures that malicious network activity will be logged to the system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67703",
+      "title": "Bluetooth devices must not be allowed to wake the computer.",
+      "description": "Bluetooth devices must not be allowed to wake the computer. If Bluetooth is not required, turn it off. If Bluetooth is necessary, disable allowing Bluetooth devices to wake the computer.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67705",
+      "title": "Bluetooth Sharing must be disabled.",
+      "description": "Bluetooth sharing allows users to wirelessly transmit files between the OS X and Bluetooth-enabled devices, including personally owned cell phones and tablets. A malicious user might introduce viruses or malware onto the system or extract sensitive files. Disabling Bluetooth Sharing mitigates this risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67707",
+      "title": "Remote Apple Events must be disabled.",
+      "description": "It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).\n\nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled.\n\nRemote Apple Events must be disabled.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67709",
+      "title": "The sudoers file must be configured to authenticate users on a per-tty basis.",
+      "description": "The sudo command must be configured to prompt for the administrator user's password at least once in each newly opened Terminal window or remote login session, as this prevents a malicious user from taking advantage of an unlocked computer or an abandoned login session to bypass the normal password prompt requirement. Without the tty_tickets option, all open local and remote logon sessions would be authenticated to use sudo without a password for the duration of the configured password timeout window.",
+      "severity": "high"
+    },
+    {
+      "id": "V-67711",
+      "title": "The application firewall must be enabled.",
+      "description": "The Application Firewall is the built-in firewall that comes with the OS X and must be enabled. Firewalls protect computers from network attacks by blocking or limiting access to open network ports. Application firewalls limit which applications are allowed to communicate over the network.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67713",
+      "title": "All public directories must be owned by root or an application account.",
+      "description": "All public directories must be owned by root, the local admin user, or an application account. Directory owners have permission to delete any files contained in that directory, even if the files are owned by other user accounts. By setting the owner to an administrator or application account, regular users will not be permitted to delete each other's files.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67715",
+      "title": "The finger service must be disabled.",
+      "description": "The finger service has had several security vulnerabilities in the past and is not a necessary service. It is disabled by default; enabling it would increase the attack surface of the system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67717",
+      "title": "The sticky bit must be set on all public directories.",
+      "description": "The sticky bit must be set on all public directories, as it prevents users with write access to the directory from deleting or renaming files that belong to other users inside it.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67719",
+      "title": "The prompt for Apple ID and iCloud must be disabled.",
+      "description": "The prompt for Apple ID and iCloud must be disabled, as it might mislead new users into creating unwanted Apple IDs and iCloud storage accounts upon their first log on.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67721",
+      "title": "Users must not have Apple IDs signed into iCloud.",
+      "description": "Users should not sign into iCloud, as this leads to the possibility that sensitive data could be saved to iCloud storage or that users could inadvertently introduce viruses or malware previously saved to iCloud from other systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67723",
+      "title": "iTunes Music Sharing must be disabled.",
+      "description": "When iTunes Music Sharing is enabled, the computer starts a network listening service that shares the contents of the user's music collection with other users in the same subnet. Unnecessary network services should always be disabled because they increase the attack surface of the system. Disabling iTunes Music Sharing mitigates this risk.",
+      "severity": "low"
+    },
+    {
+      "id": "V-67725",
+      "title": "All setuid executables on the system must be vendor-supplied.",
+      "description": "Very few of the executables that come preinstalled on the OS X have the setuid bit set, and administrators should never add the setuid bit to any executable that does not already have it set by the vendor. Executables with the setuid bit set allow anyone that executes them to be temporarily assigned the UID of the file owner. In practice, this almost always is the root account. While some vendors depend on this file attribute for proper operation, security problems can result if setuid is assigned to programs allowing reading and writing of files, or shell escapes, as this could lead to unprivileged users gaining privileged access to files and directories on the system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67727",
+      "title": "The system must not accept source-routed IPv4 packets.",
+      "description": "A source-routed packet attempts to specify the network path the packet should take. If the system is not configured to block the incoming source-routed packets, an attacker can redirect the system's network traffic. Configuring the system to drop incoming source-routed IPv4 packets mitigates this risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67729",
+      "title": "The system must ignore IPv4 ICMP redirect messages.",
+      "description": "ICMP redirects are broadcast in order to reshape network traffic. A malicious user could craft fake redirect packets and try to force all network traffic to pass through a network sniffer. If the system is not configured to ignore these packets, it could be susceptible to this kind of attack.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67731",
+      "title": "IP forwarding for IPv4 must not be enabled.",
+      "description": "IP forwarding for IPv4 must not be enabled, as only authorized systems should be permitted to operate as routers.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67733",
+      "title": "IP forwarding for IPv6 must not be enabled.",
+      "description": "IP forwarding for IPv6 must not be enabled, as only authorized systems should be permitted to operate as routers.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67735",
+      "title": "The operating system must enforce account lockout after the limit of three consecutive invalid logon attempts by a user during a 15 minute time period.",
+      "description": "By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67737",
+      "title": "The operating system must enforce an account lockout time period of 15 minutes in which three consecutive invalid logon attempts by a user are made.",
+      "description": "Setting a lockout time period of 15 minutes is an effective deterrent against brute forcing that also makes allowances for legitimate mistakes by users. When three invalid logon attempts are made, the account will be locked.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67739",
+      "title": "Web Sharing must be disabled.",
+      "description": "Web Sharing is non-essential and must be disabled. Enabling any service increases the attack surface for an intruder. By disabling unnecessary services, the attack surface is minimized.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67741",
+      "title": "Internet Sharing must be disabled.",
+      "description": "In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.\n\nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. \n\nTo support the requirements and principles of least functionality, the operating system must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.\n\nInternet Sharing must be disabled.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67745",
+      "title": "The system must not send IPv4 ICMP redirects by default.",
+      "description": "ICMP redirects are broadcast in order to reshape network traffic. A malicious user could use the system to send fake redirect packets and try to force all network traffic to pass through a network sniffer. Disabling ICMP redirect broadcasts mitigates this risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67747",
+      "title": "The system must not send IPv6 ICMP redirects by default.",
+      "description": "ICMP redirects are broadcast in order to reshape network traffic. A malicious user could use the system to send fake redirect packets and try to force all network traffic to pass through a network sniffer. Disabling ICMP redirect broadcasts mitigates this risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67749",
+      "title": "The system must prevent local applications from generating source-routed packets.",
+      "description": "A source-routed packet attempts to specify the network path that the system should take. If the system is not configured to block the sending of source-routed packets, an attacker can redirect the system's network traffic.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67751",
+      "title": "The operating system must employ automated mechanisms to detect the presence of unauthorized software on organizational information systems and notify designated organizational officials in accordance with the organization-defined frequency.",
+      "description": "An approved anti-virus product must be installed and configured to run.\n\nMalicious software can establish a base on individual desktops and servers.  Employing an automated mechanism to detect this type of software will aid in elimination of the software from the operating system.",
+      "severity": "high"
+    },
+    {
+      "id": "V-67753",
+      "title": "The system must not process Internet Control Message Protocol [ICMP] timestamp requests.",
+      "description": "ICMP Timestamp requests reveal information about the system and can be used to determine which operating system is installed. Precise time data can also be used to launch time based attacks against the system. Configuring the system to drop incoming ICMPv4 timestamp requests mitigates these risks.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-67755",
+      "title": "Unused network devices must be disabled.",
+      "description": "If an unused network device is left enabled, a user might be able to activate it at a later time. Unused network devices should be disabled.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-68155",
+      "title": "The operating system must generate audit records when successful/unsuccessful attempts to access/modify/delete objects, access/modify categories of information (e.g., classification levels), and delete privileges occur.",
+      "description": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.\n\nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\nSatisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209, SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00211, SRG-OS-000468-GPOS-00212, SRG-OS-000474-GPOS-00219",
+      "severity": "medium"
+    },
+    {
+      "id": "V-79059",
+      "title": "The OS X system must not use unencrypted FTP.",
+      "description": null,
+      "severity": "high"
+    }
+  ]
+}