<?xml version="1.0" encoding="UTF-8"?>
<CHECKLIST>
  <ASSET>
    <ROLE>None</ROLE>
    <ASSET_TYPE>Computing</ASSET_TYPE>
    <HOST_NAME></HOST_NAME>
    <HOST_IP></HOST_IP>
  </ASSET>
  <STIGS>
    <iSTIG>
      <STIG_INFO>
        <SI_DATA>
          <SID_NAME>title</SID_NAME>
          <SID_DATA>Apple visionOS 2 Security Technical Implementation Guide</SID_DATA>
        </SI_DATA>
        <SI_DATA>
          <SID_NAME>version</SID_NAME>
          <SID_DATA>1</SID_DATA>
        </SI_DATA>
        <SI_DATA>
          <SID_NAME>releaseinfo</SID_NAME>
          <SID_DATA>Release: 1</SID_DATA>
        </SI_DATA>
      </STIG_INFO>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276374</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276374r1146618_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>low</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must allow the administrator (MDM) to perform the following management function: enable/disable VPN protection across the device and [selection: on a per-app basis, on a per-group of applications processes basis].</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The system administrator must have the capability to configure VPN access to meet organization-specific policies based on mission needs. Otherwise, a user could inadvertently or maliciously set up a VPN and connect to a network that poses an unacceptable risk to DOD information systems. An adversary could exploit vulnerabilities created by the weaker configuration to compromise DOD sensitive information.

SFR ID: FMT_SMF.1.1 #3</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review the list of unmanaged apps installed on the Vision Pro and determine if any unmanaged third-party VPN clients are installed. If so, verify the VPN app is not configured with a DOD network (work) VPN profile. 

This validation procedure is performed on the visionOS device only.

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap the &quot;VPN and Device Management&quot; line and determine if any &quot;Personal VPN&quot; exists.
4. If not, the requirement has been met.
5. If there are personal VPNs, open each VPN app. Review the list of VPN profiles configured on the VPN client.
6. Verify no DOD network VPN profiles are configured on the VPN client.

If any third-party unmanaged VPN apps are installed (personal VPN) and they have a DOD network VPN profile configured on the client, this is a finding.

Note: This setting cannot be managed by the MDM administrator and is a User-Based Enforcement (UBE) requirement.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>If a third-party unmanaged VPN app is installed on the visionOS 2 device, do not configure the VPN app with a DOD network VPN profile.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276375</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276375r1146621_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must not allow backup to remote systems (iCloud).</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>If a user can configure the security setting, the user could inadvertently or maliciously set it to a value that poses unacceptable risk to DOD information systems. An adversary could exploit vulnerabilities created by the weaker configuration to compromise DOD sensitive information.

SFR ID: FMT_MOF_EXT.1.2 #40</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Note: This requirement is not applicable if the authorizing official (AO) has approved users&apos; full access to the Apple App Store for downloading unmanaged (personal) apps and syncing personal data on the device with personal cloud data storage accounts. The site must have an AO-signed document showing the AO has assumed the risk for users&apos; full access to the Apple App Store.

Review configuration settings to confirm iCloud Backup is disabled.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Apple visionOS management tool, verify &quot;Allow iCloud backup&quot; is unchecked.

Alternatively, verify the text &quot;&lt;key&gt;allowCloudBackup&lt;/key&gt; &lt;false/&gt;&quot; appears in the configuration profile (.mobileconfig file).

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;iCloud backup not allowed&quot;.

If &quot;Allow iCloud backup&quot; is checked in the Apple visionOS management tool, &quot;&lt;key&gt;allowCloudBackup&lt;/key&gt;&lt;true/&gt;&quot; appears in the configuration profile, or the restrictions policy on the Vision Pro does not list &quot;iCloud backup not allowed&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable iCloud backup.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276376</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276376r1146624_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must not allow backup to remote systems (iCloud document and data synchronization).</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>If a user can configure the security setting, they could inadvertently or maliciously set it to a value that poses unacceptable risk to DOD information systems. An adversary could exploit vulnerabilities created by the weaker configuration to compromise DOD sensitive information.

SFR ID: FMT_MOF_EXT.1.2 #40</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Note: This requirement is not applicable if the authorizing official (AO) has approved users&apos; full access to the Apple App Store for downloading unmanaged (personal) apps and syncing personal data on the device with personal cloud data storage accounts. The site must have an AO-signed document showing the AO has assumed the risk for users&apos; full access to the Apple App Store. 

This is a supervised-only control. If the Vision Pro being reviewed is not supervised by the MDM, this control is automatically a finding.

If the Vision Pro being reviewed is supervised by the MDM, review configuration settings to confirm &quot;Allow iCloud documents &amp; data&quot; is disabled.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review.

In the Apple visionOS management tool, verify &quot;Allow iCloud documents &amp; data&quot; is unchecked.

Alternatively, verify the text &quot;&lt;key&gt;allowCloudDocumentSync&lt;/key&gt; &lt;false/&gt;&quot; appears in the configuration profile (.mobileconfig file).

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Documents in the Cloud not allowed&quot; is listed.

Note: This also verifies that iCloud Drive and iCloud Photo Library are disabled.

If &quot;Allow iCloud documents &amp; data&quot; is checked in the Apple visionOS management tool, &quot;&lt;key&gt;allowCloudDocumentSync&lt;/key&gt; &lt;true/&gt;&quot; appears in the configuration profile, or the restrictions policy on the Vision Pro does not list &quot;Documents in the Cloud not allowed&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable iCloud documents and data. This is a supervised-only control.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276377</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276377r1146627_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must not allow backup to remote systems (iCloud Keychain).</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>If a user can configure the security setting, the user could inadvertently or maliciously set it to a value that poses unacceptable risk to DOD information systems. An adversary could exploit vulnerabilities created by the weaker configuration to compromise DOD sensitive information.

SFR ID: FMT_MOF_EXT.1.2 #40</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Note: This requirement is not applicable if the authorizing official (AO) has approved users&apos; full access to the Apple App Store for downloading unmanaged (personal) apps and syncing personal data on the device with personal cloud data storage accounts. The site must have an AO-signed document showing the AO has assumed the risk for users&apos; full access to the Apple App Store. 

This is a supervised-only control. If the Vision Pro being reviewed is not supervised by the MDM, this control is automatically a finding.

If the Vision Pro being reviewed is supervised by the MDM, review configuration settings to confirm iCloud keychain is disabled.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro. 

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review.

In the Apple visionOS management tool, verify &quot;Allow iCloud keychain&quot; is unchecked.

Alternatively, verify the text &quot;&lt;key&gt;allowCloudKeychainSync&lt;/key&gt;&lt;false/&gt;&quot; appears in the configuration profile (.mobileconfig file).

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the management policy.
5. Verify &quot;iCloud Keychain not allowed&quot; is listed.

If &quot;Allow iCloud keychain&quot; is checked in the Apple visionOS management tool, &quot;&lt;key&gt;allowCloudKeychainSync&lt;/key&gt;&lt;true/&gt;&quot; appears in the configuration profile, or &quot;iCloud Keychain not allowed&quot; is not listed on the Vision Pro, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable iCloud keychain. This is a supervised-only control.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276378</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276378r1146630_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must not allow backup to remote systems (Cloud Photo Library).</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>If a user can configure the security setting, the user could inadvertently or maliciously set it to a value that poses unacceptable risk to DOD information systems. An adversary could exploit vulnerabilities created by the weaker configuration to compromise DOD sensitive information.

SFR ID: FMT_MOF_EXT.1.2 #40</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Note: This requirement is not applicable if the authorizing official (AO) has approved users&apos; full access to the Apple App Store for downloading unmanaged (personal) apps and syncing personal data on the device with personal cloud data storage accounts. The site must have an AO-signed document showing the AO has assumed the risk for users&apos; full access to the Apple App Store. 

This is a supervised-only control. If the Vision Pro being reviewed is not supervised by the MDM, this control is automatically a finding.

If the Vision Pro being reviewed is supervised by the MDM, review configuration settings to confirm &quot;Allow Cloud Photo Library&quot; is disabled.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro. 

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Apple visionOS management tool, verify &quot;Allow Cloud Photo Library&quot; is unchecked.

Alternatively, verify the text &quot;&lt;key&gt;allowCloudPhotoLibrary&lt;/key&gt;&lt;false/&gt;&quot; appears in the configuration profile (.mobileconfig file).

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the Apple visionOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;iCloud Photos not allowed&quot; is listed.

If &quot;Allow Cloud Photo Library&quot; is checked in the Apple visionOS management tool, &quot;&lt;key&gt;allowCloudPhotoLibrary&lt;/key&gt; &lt;true/&gt;&quot; appears in the configuration profile, or the restrictions policy on the Vision Pro does not list &quot;iCloud Photos not allowed&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable Cloud Photo Library. This is a supervised-only control.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276379</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276379r1146633_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must not allow backup to remote systems (managed applications data stored in iCloud).</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>If a user can configure the security setting, the user could inadvertently or maliciously set it to a value that poses unacceptable risk to DOD information systems. An adversary could exploit vulnerabilities created by the weaker configuration to compromise DOD sensitive information.

SFR ID: FMT_MOF_EXT.1.2 #40</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm &quot;Allow managed apps to store data in iCloud&quot; is disabled.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Apple visionOS management tool, verify &quot;Allow managed apps to store data in iCloud&quot; is unchecked.

Alternatively, verify the text &quot;&lt;key&gt;allowManagedAppsCloudSync&lt;/key&gt; &lt;false/&gt;&quot; appears in the configuration profile (.mobileconfig file).

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the Apple visionOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Managed apps cloud sync not allowed&quot; is listed.

If &quot;Allow managed apps to store data in iCloud&quot; is checked in the Apple visionOS management tool, &quot;&lt;key&gt;allowManagedAppsCloudSync&lt;/key&gt; &lt;true/&gt;&quot; appears in the configuration profile, or the restrictions policy on the Vision Pro does not list &quot;Managed apps cloud sync not allowed&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to prevent DOD applications from storing data in iCloud.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276380</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276380r1146636_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must be configured to enforce a minimum password length of six characters.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Password strength is a measure of the effectiveness of a password in resisting guessing and brute force attacks. The ability to crack a password is a function of how many attempts an adversary is permitted, how quickly an adversary can do each attempt, and the size of the password space. The longer the minimum length of the password is, the larger the password space. Having a too-short minimum password length significantly reduces password strength, increasing the chance of password compromise and resulting device and data compromise.

SFR ID: FMT_SMF.1.1 #1</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm the minimum passcode length is six or more characters.

This procedure is performed in the Apple visionOS management tool and on the Vision Pro. 

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Management tool, verify the &quot;Minimum passcode length&quot; value is set to six or greater.

Alternatively, verify the text &quot;&lt;key&gt;minLength&lt;/key&gt; &lt;integer&gt;6&lt;/integer&gt;&quot; appears in the configuration profile (.mobileconfig file). It also is acceptable for the integer value to be greater than six.

On the Vision Pro:
1. Open the Settings app. 
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the Apple visionOS management tool containing the password policy.
5. Tap &quot;Restrictions&quot;.
6. Tap &quot;Passcode&quot;.
7. Verify &quot;Minimum length&quot; is listed as &quot;six or greater&quot;.

If the &quot;Minimum passcode length&quot; is fewer than six characters in the visionOS management tool, &quot;&lt;key&gt;minLength&lt;/key&gt; &quot; has an integer value of fewer than six, or the password policy on the Vision Pro from the Apple visionOS management tool does not list &quot;Minimum length&quot; of six or more, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to enforce a minimum passcode length value of six or greater.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276381</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276381r1146639_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must be configured to not allow passwords that include more than four repeating or sequential characters.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Password strength is a measure of the effectiveness of a password in resisting guessing and brute force attacks. Passwords that contain repeating or sequential characters are significantly easier to guess than those that do not contain repeating or sequential characters. Therefore, disallowing repeating or sequential characters increases password strength and decreases risk.

SFR ID: FMT_SMF.1.1 #1</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm simple passcodes are not allowed.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro. 

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Apple visionOS management tool, verify &quot;Allow simple value&quot; is unchecked. Alternatively, verify the text &quot;&lt;key&gt;allowSimple&lt;/key&gt; &lt;false/&gt;&quot; appears in the configuration profile (.mobileconfig file).

On the Vision Pro: 
1. Open the Settings app. 
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;. 
4. Tap the configuration profile from the visionOS management tool containing the password policy.
5. Tap &quot;Restrictions&quot;.
6. Tap &quot;Passcode&quot;.
7. Verify &quot;Simple passcodes allowed&quot; is set to &quot;No&quot;.

If &quot;Allow simple value&quot; is checked in the Apple visionOS management tool, &quot;&lt;key&gt;allowSimple&lt;/key&gt; &lt;true/&gt;&quot; appears in the Configuration Profile, or the password policy on the Vision Pro does not have &quot;Simple passcodes allowed&quot; set to &quot;No&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disallow more than four sequential or repeating numbers or letters in the device unlock password.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276382</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276382r1146642_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must be configured to lock the display after 15 minutes (or fewer) of inactivity.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The screen lock timeout must be set to a value that helps protect the device from unauthorized access. Having a too-long timeout would increase the window of opportunity for adversaries who gain physical access to the mobile device through loss, theft, etc. Such devices are much more likely to be in an unlocked state when acquired by an adversary, thus granting immediate access to the data on the mobile device. The maximum timeout period of 15 minutes has been selected to balance functionality and security; shorter timeout periods may be appropriate depending on the risks posed to the mobile device.

SFR ID: FMT_SMF.1.1 #2</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm the screen lock timeout is set to 15 minutes or fewer.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review.

In the management tool, verify the sum of the values assigned to &quot;Maximum Auto-Lock time&quot; and &quot;Grace period for device lock&quot; is between 1 and 15 minutes. 

Alternatively, locate the text &quot;&lt;key&gt;maxGracePeriod&lt;/key&gt;&quot; and &quot;&lt;key&gt;maxInactivity&lt;/key&gt;&quot; and ensure the sum of their integer value is between 1 and 15 in the configuration profile (.mobileconfig file). For example:

&quot;&lt;key&gt;maxGracePeriod&lt;/key&gt;
&lt;integer&gt;5&lt;/integer&gt;
&lt;key&gt;maxInactivity&lt;/key&gt;
&lt;integer&gt;5&lt;/integer&gt;&quot;

Here, 5 + 5 = 10; this meets the requirement.

On the Vision Pro: 
1. Open the Settings app. 
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the password policy.
5. Tap &quot;Restrictions&quot;.
6. Tap &quot;Passcode&quot;.
7. Verify the sum of the &quot;Max grace period&quot; and &quot;Max inactivity&quot; values is fewer than 15 minutes.

Note: On some visionOS devices, it is not possible to have a sum of exactly 15. In these cases, the sum must be fewer than 15. A sum of 16 does not meet the requirement.

On the management server, if the sum of the &quot;Max grace period&quot; and &quot;Max inactivity&quot; values is not between 1 and 15 minutes in the visionOS management tool or the sum of the values assigned to &quot;&lt;key&gt;maxGracePeriod&lt;/key&gt;&quot; and &quot;&lt;key&gt;maxInactivity&lt;/key&gt;&quot; is not between 1 and 15 minutes in the configuration profile, or if on the Vision Pro, the sum of the values assigned to &quot;Max grace period&quot; and &quot;Max inactivity&quot; is not between 1 and 15 minutes, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to lock the device display after 15 minutes (or fewer) of inactivity. This is done by setting &quot;Maximum Auto-Lock time&quot; and &quot;Grace Period for device lock&quot; so the sum of their values is between 1 and 15 minutes.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276383</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276383r1146645_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must be configured to not allow more than 10 consecutive failed authentication attempts.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The more attempts an adversary has to guess a password, the more likely the adversary will enter the correct password and gain access to resources on the device. Setting a limit on the number of attempts mitigates this risk. Setting the limit at 10 or fewer gives authorized users the ability to make a few mistakes when entering the password but still provides adequate protection against dictionary or brute force attacks on the password.

SFR ID: FMT_SMF.1.1 #2, FIA_AFL_EXT.1.5</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm that consecutive failed authentication attempts is set to 10 or fewer.

This procedure is performed in the Apple visionOS management tool and on the Vision Pro. 

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Management tool, verify the &quot;Maximum number of failed attempts&quot; value is set to 10 or fewer.

Alternatively, verify the text &quot;&lt;key&gt;maxFailedAttempts&lt;/key&gt; &lt;integer&gt;10&lt;/integer&gt;&quot; appears in the configuration profile (.mobileconfig file). It also is acceptable for the integer value to be fewer than 10.

On the Vision Pro: 
1. Open the Settings app. 
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the password policy.
5. Tap &quot;Restrictions&quot;.
6. Tap &quot;Passcode&quot;.
7. Verify &quot;Max failed attempts&quot; is listed as &quot;10&quot; or fewer.

If the &quot;Maximum number of failed attempts&quot; is more than 10 in the visionOS management tool, &quot;&lt;key&gt;maxFailedAttempts&lt;/key&gt; &quot; has an integer value of more than 10, or the password policy on the Vision Pro does not list &quot;Max failed attempts&quot; of 10 or fewer, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to allow only 10 or fewer consecutive failed authentication attempts.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276384</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276384r1146648_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>high</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must be configured to enforce a passcode reuse prohibition of at least two generations.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>visionOS/iPadOS 17 and later versions include a feature that allows the previous passcode to be valid for 72 hours after a passcode change. If the previous passcode has been compromised and the attacker has access to it and the Apple device, enterprise data and the enterprise network can be compromised. Currently there is no MDM control to force the old passcode to expire immediately after passcode change. The previous passcode will expire immediately after a passcode change if the MDM password history control is implemented.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm the Apple visionOS device has a passcode reuse prohibition of at least two generations.

This procedure is performed in the Apple visionOS management tool and on the Vision Pro. 

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Management tool, verify the &quot;Passcode History&quot; value is set to two or greater.

On the Vision Pro:
1. Open the Settings app. 
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the Apple visionOS management tool containing the password policy.
5. Tap &quot;Restrictions&quot;.
6. Tap &quot;Passcode&quot;.
7. Verify &quot;Number of unique recent passcodes required&quot; is listed as &quot;two&quot; or greater.

If the Apple visionOS device does not enforce a passcode reuse prohibition of at least two generations, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to enforce a passcode reuse prohibition of at least two generations (passcode history).</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276385</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276385r1146651_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must be configured to enforce an application installation policy by specifying one or more authorized application repositories, including [selection: DOD-approved commercial app repository, MDM server, mobile application store].</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Forcing all applications to be installed from authorized application repositories can prevent unauthorized and malicious applications from being installed and executed on mobile devices. Allowing such installations and executions could cause a compromise of DOD data accessible by these unauthorized/malicious applications.

SFR ID: FMT_SMF.1.1 #8</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm &quot;Allow Trusting New Enterprise App Authors&quot; is disabled.

This procedure is performed in the Apple visionOS management tool and on the Vision Pro. 

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Management tool, verify &quot;Allow Trusting New Enterprise App Authors&quot; is disabled.

On the Vision Pro: 
1. Open the Settings app. 
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the Apple visionOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Trusting enterprise apps not allowed&quot; is listed.

If &quot;Allow Trusting New Enterprise App Authors&quot; is not disabled in the visionOS management tool or on the Vision Pro, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable &quot;Allow Trusting New Enterprise App Authors&quot;.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276386</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276386r1146654_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must be configured to not display notifications when the device is locked.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Many mobile devices display notifications on the lock screen so users can obtain relevant information in a timely manner without having to frequently unlock the phone. However, in many cases, these notifications can contain sensitive information. When they are available on the lock screen, an adversary can view them merely by being in close physical proximity to the device. Configuring the mobile operating system not to send notifications to the lock screen mitigates this risk.

SFR ID: FMT_SMF.1.1 #18</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm the display of notifications when the device is locked has been disabled. 

This check procedure is performed on the Apple visionOS management tool and mobile device. 

In the Apple visionOS management tool, for each managed app, verify the app is configured to disable Notifications preview.

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the management policy.
5. Tap &quot;Apps&quot;.
6. Tap an app and verify &quot;Disallow notification view in locked screen&quot; is listed.

Repeat steps 5 and 6 for each managed app in the list.

If one or more managed apps are not set to disable showing notification view on locked screen, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable the display of notifications when the device is locked.

Install a configuration profile to disable Notification Center from the device Lock screen.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276387</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276387r1146657_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>low</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must be configured to display the DOD advisory warning message at startup or each time the user unlocks the device.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Before granting access to the system, the mobile operating system is required to display the DOD-approved system use notification message or banner that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. Required banners help ensure that DOD can audit and monitor the activities of mobile device users without legal restriction.

System use notification messages can be displayed when individuals first access or unlock the mobile device. The banner must be implemented as a &quot;click-through&quot; banner at device unlock (to the extent permitted by the operating system). A &quot;click-through&quot; banner prevents further activity on the information system unless and until the user executes a positive action to manifest agreement by clicking on a box indicating &quot;OK&quot;.

The approved DOD text must be used exactly as required in the Knowledge Service referenced in DODI 8500.01. For devices accommodating banners of 1300 characters, the banner text is: 

You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. 
By using this IS (which includes any device attached to this IS), you consent to the following conditions: 
-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. 
-At any time, the USG may inspect and seize data stored on this IS. 
-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. 
-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. 
-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.

For devices with severe character limitations, the banner text is: 

I&apos;ve read &amp; consent to terms in IS user agreem&apos;t.

The administrator must configure the banner text exactly as written without any changes.

SFR ID: FMT_SMF.1.1 #36</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The DOD warning banner can be displayed by the following method (required text is found in the Vulnerability Discussion):

1. By placing the DOD warning banner text in the user agreement signed by each Vision Pro user. 

Validation Procedure for Method #1:
Review the signed user agreements for several visionOS device users and verify the agreement includes the required DOD warning banner text.

If, the required warning banner text is not on all signed user agreements reviewed, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Configure the DOD warning banner by the following method (required text is found in the Vulnerability Discussion):

1. By placing the DOD warning banner text in the user agreement signed by each visionOS device user.

Note, Vision Pro does not support the LockScreenFootnote key.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276388</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276388r1146660_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must not allow non-DOD applications to access DOD data.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>App data sharing gives apps the ability to access the data of other apps for enhanced user functionality. However, sharing also poses a significant risk that unauthorized users or apps will obtain access to sensitive DOD information. To mitigate this risk, there are data sharing restrictions. If a user is allowed to make exceptions to the data sharing restriction policy, the user could enable unauthorized sharing of data, leaving it vulnerable to breach. Limiting the granting of exceptions to either the administrator or common application developer mitigates this risk.

Copy/paste of data between applications in different application processes or groups of application processes is considered an exception to the access control policy; therefore, the administrator must be able to enable/disable the feature. Other exceptions include allowing any data or application sharing between process groups.

SFR ID: FMT_SMF.1.1 #42, FDP_ACF_EXT.1.2</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm &quot;Allow documents from managed apps in unmanaged apps&quot; is disabled.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review.

In the visionOS management tool, verify &quot;Allow documents from managed apps in unmanaged apps&quot; is unchecked.

Alternatively, verify the text &quot;&lt;key&gt;allowOpenFromManagedToUnmanaged&lt;/key&gt;&lt;false/&gt;&quot; appears in the configuration profile (.mobileconfig file).

On the visionOS device:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Opening documents from managed to unmanaged apps not allowed&quot; is listed.

If &quot;Allow documents from managed apps in unmanaged apps&quot; is checked in the visionOS management tool, &quot;&lt;key&gt;allowOpenFromManagedToUnmanaged&lt;/key&gt;&lt;true/&gt;&quot; appears in the configuration profile, or the restrictions policy on the Vision Pro does not list &quot;Opening documents from managed to unmanaged apps not allowed&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to prevent non-DOD applications from accessing DOD data.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276389</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276389r1146663_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must be configured to [selection: wipe protected data, wipe sensitive data] upon unenrollment from MDM.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>When a mobile device is no longer managed by MDM technologies, its protected/sensitive data must be sanitized because it will no longer be protected by the MDM software, putting it at much greater risk of unauthorized access and disclosure. At least one of the two options must be selected.

SFR ID: FMT_SMF_EXT.2.1</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Note: Not all Apple visionOS deployments involve MDM. If the site uses an authorized alternative to MDM for distribution of configuration profiles (Apple Configurator), this check procedure is not applicable.

This check procedure is performed on the Apple visionOS management tool or on the visionOS device.

In the Apple visionOS management tool, for each managed app, verify the app is configured to be removed when the MDM profile is removed.

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the management policy.
5. Tap &quot;Apps&quot;.
6. Tap an app and verify &quot;App and data will be removed when device is no longer managed&quot; is listed.

Repeat steps 5 and 6 for each managed app in the list.

If one or more managed apps are not set to be removed upon device MDM unenrollment, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to delete all managed apps upon device unenrollment.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276390</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276390r1146666_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must be configured to [selection: remove Enterprise applications, remove all noncore applications (any nonfactory-installed application)] upon unenrollment from MDM.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>When a mobile device is no longer managed by MDM technologies, its protected/sensitive data must be sanitized because it will no longer be protected by the MDM software, putting it at much greater risk of unauthorized access and disclosure. At least one of the two options must be selected.

SFR ID: FMT_SMF_EXT.2.1</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Note: Not all Apple visionOS deployments involve MDM. If the site uses an authorized alternative to MDM for distribution of configuration profiles (Apple Configurator), this check procedure is not applicable.

This check procedure is performed on the Apple visionOS management tool or on the visionOS device.

In the Apple visionOS management tool, for each managed app, verify the app is configured to be removed when the MDM profile is removed.

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the management policy.
5. Tap &quot;Apps&quot;.
6. Tap an app and verify &quot;App and data will be removed when device is no longer managed&quot; is listed.

Repeat steps 5 and 6 for each managed app in the list.

If one or more managed apps are not set to be removed upon device MDM unenrollment, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to delete all managed apps upon device unenrollment.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276391</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276391r1146669_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must be configured to disable ad hoc wireless client-to-client connection capability.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Ad hoc wireless client-to-client connections allow mobile devices to communicate with each other directly, circumventing network security policies and making the traffic invisible. This could allow the exposure of sensitive DOD data and increase the risk of downloading and installing malware on the DOD mobile device.

SFR ID: FMT_SMF_EXT.1.1/WLAN</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm it is disabled. If AirDrop is approved, this requirement is not applicable.

This is a supervised-only control. If the Vision Pro being reviewed is not supervised by the MDM, this control is automatically a finding.

If the Vision Pro being reviewed is supervised by the MDM, follow these procedures:

This check procedure is performed on both the device management tool and the Vision Pro device.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the visionOS management tool, verify &quot;Allow AirDrop&quot; is unchecked.

On the Vision Pro device:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;. 
4. Tap the configuration profile from the visionOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;AirDrop not allowed&quot; is listed.

If &quot;AirDrop not allowed&quot; is not listed in the management tool and on the Apple device, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable the AllowAirDrop control in the management tool. This is a supervised-only control.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276392</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276392r1146672_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>high</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must require a valid password be successfully entered before the mobile device data is unencrypted.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Passwords provide a form of access control that prevents unauthorized individuals from accessing computing resources and sensitive data. Passwords may also be a source of entropy for generation of key encryption or data encryption keys. If a password is not required to access data, this data is accessible to any adversary who obtains physical possession of the device. Requiring that a password be successfully entered before the mobile device data is unencrypted mitigates this risk.

Note: MDF PP requires a Password Authentication Factor and requires management of its length and complexity. It leaves open whether the existence of a password is subject to management. This requirement addresses the configuration to require a password, which is critical to the cybersecurity posture of the device.

SFR ID: FIA_UAU_EXT.1.1</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm the device is set to require a passcode before use.

This procedure is performed on the visionOS device.

On the Vision Pro: 
1. Open the Settings app. 
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the password policy.
5. Tap &quot;Restrictions&quot;.
6. Tap &quot;Passcode&quot;.
7. Verify &quot;Passcode required&quot; is set to &quot;Yes&quot;.

If &quot;Passcode required&quot; is not set to &quot;Yes&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to require a password to unlock the device.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276393</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276393r1146675_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>low</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must implement the management setting: not allow automatic completion of Safari browser passcodes.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The AutoFill functionality in the Safari web browser allows the user to complete a form that contains sensitive information, such as PII, without previous knowledge of the information. By allowing using the AutoFill functionality, an adversary who learns a user&apos;s Vision Pro passcode, or who otherwise can unlock the device, may be able to further breach other systems by relying on the AutoFill feature to provide information unknown to the adversary. By disabling the AutoFill functionality, the risk of an adversary gaining additional information about the device&apos;s user or compromising other systems is significantly mitigated.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm &quot;Enable autofill&quot; is unchecked.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review.

In the Apple visionOS management tool, verify &quot;Enable autofill&quot; is unchecked.

Alternatively, verify the text &quot;&lt;key&gt;safariAllowAutoFill&lt;/key&gt;&lt;false&gt;&quot; appears in the configuration profile (.mobileconfig file).

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the management policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Auto-fill in Safari not allowed&quot; is present.

If &quot;Enable autofill&quot; is checked in the Apple visionOS management tool, &quot;&lt;key&gt;safariAllowAutoFill&lt;/key&gt;&lt;true&gt;&quot; appears in the configuration profile, or the restrictions policy on the Vision Pro does not list &quot;Auto-fill in Safari not allowed&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable the AutoFill capability in the Safari app.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276394</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276394r1146678_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>low</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must implement the management setting: not allow use of Handoff.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Handoff permits a user of a Vision Pro to transition user activities from one device to another. Handoff passes sufficient information between the devices to describe the activity, but app data synchronization associated with the activity is handled though iCloud, which should be disabled on a compliant Vision Pro. If a user associates both DOD and personal devices to the same Apple ID, the user may improperly reveal information about the nature of the user&apos;s activities on an unprotected device. Disabling Handoff mitigates this risk.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>This is a supervised-only control. If the Vision Pro being reviewed is not supervised by the MDM, this control is automatically a finding.

If the Vision Pro being reviewed is supervised by the MDM, review configuration settings to confirm &quot;Allow Handoff&quot; is disabled.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Apple visionOS management tool, verify &quot;Allow Handoff&quot; is unchecked.

Alternatively, verify the text &quot;&lt;key&gt;allowActivityContinuation&lt;/key&gt; &lt;false/&gt;&quot; appears in the configuration profile (.mobileconfig file).

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the Apple visionOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Handoff not allowed&quot; is listed.

If &quot;Allow Handoff&quot; is checked in the Apple visionOS management tool, &quot;&lt;key&gt;allowActivityContinuation&lt;/key&gt; &lt;true/&gt;&quot; appears in the configuration profile, or the restrictions policy on the Vision Pro does not list &quot;Handoff not allowed&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable continuation of activities among devices and workstations. This is a supervised-only control.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276395</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276395r1146681_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must implement the management setting: disable Allow MailDrop.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>MailDrop allows users to send large attachments (up to 5 GB) via iCloud. Storing data with a non-DOD cloud provider may leave the data vulnerable to breach. Disabling non-DOD cloud services mitigates this risk.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm &quot;Allow MailDrop&quot; is disabled.

This validation procedure is performed on both the Apple visionOS management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Apple visionOS management tool, verify &quot;Allow MailDrop&quot; is not checked.

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the Apple visionOS management tool containing the restrictions policy.
5. Tap &quot;Mail&quot;.
6. Tap the mail account.
7. Verify &quot;Mail Drop Enabled&quot; is set to &quot;No&quot;.

If &quot;Allow MailDrop&quot; is not disabled in the Apple visionOS management tool or the restrictions policy on the Vision Pro lists &quot;Mail Drop Enabled&quot; as &quot;Yes&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Configure the Apple visionOS configuration profile to disable &quot;Allow MailDrop&quot;.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276396</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276396r1146684_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>high</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Vision Pro must have the latest available visionOS operating system installed.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Required security features are not available in earlier OS versions. In addition, earlier versions may have known vulnerabilities.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm the most recently released version of visionOS is installed.

This validation procedure is performed on both the Apple visionOS management tool and the Vision Pro. Go to https://www.apple.com and determine the most current version of visionOS released by Apple.

In the MDM management console, review the version of visionOS installed on a sample of managed devices. This procedure will vary depending on the MDM product.

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;About&quot; and view the installed version of visionOS. 
4. Go back to the &quot;General&quot; screen. Tap &quot;Software Update&quot; and verify the following message is shown on the screen: &quot;Your software is up to date.&quot;

If the installed version of visionOS on any reviewed visionOS devices is not the latest released by Apple, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install the latest release version of Apple visionOS on all managed visionOS devices.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276397</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276397r1146687_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must implement the management setting: use Secure Sockets Layer (SSL) for Exchange ActiveSync.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Exchange email messages are a form of data in transit and thus are vulnerable to eavesdropping and man-in-the-middle attacks. SSL, also referred to as Transport Layer Security (TLS), provides encryption and authentication services that mitigate the risk of breach.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm &quot;Use SSL&quot; for the Exchange account is enabled for incoming mail.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro. 

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Apple visionOS management tool, verify &quot;Use SSL for incoming mail&quot; is checked under the Exchange payload.

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the Apple visionOS management tool containing the Exchange policy.
5. Tap &quot;Mail&quot;.
6. Tap the name of the Exchange account. 
7. Verify &quot;SSL for incoming mail&quot; is set to &quot;Yes&quot;.

If &quot;Use SSL for incoming mail&quot; is unchecked in the Apple visionOS management tool or the Exchange policy on the Vision Pro has &quot;SSL for incoming mail&quot; set to &quot;No&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to use SSL for Exchange ActiveSync incoming mail.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276398</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276398r1146690_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must implement the management setting: not allow messages in an ActiveSync Exchange account to be forwarded or moved to other accounts in the Apple visionOS 2 Mail app.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The Apple visionOS Mail app can be configured to support multiple email accounts concurrently. These email accounts are likely to involve content of varying degrees of sensitivity (e.g., both personal and enterprise messages). To prevent the unauthorized and undetected forwarding or moving of messages from one account to another, Mail ActiveSync Exchange accounts can be configured to block such behavior. While users may still send a message from the Exchange account to another account, these transactions must involve an Exchange server, enabling audit records of the transaction, filtering of mail content, and subsequent forensic analysis.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm &quot;Allow messages to be moved&quot; is disabled.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Apple visionOS management tool, verify &quot;Allow messages to be moved&quot; is unchecked under the Exchange payload.

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the Apple visionOS management tool containing the Exchange policy.
5. Tap &quot;Mail&quot;.
6. Tap the name of the Exchange account.
7. Verify &quot;Prevent Move&quot; is set to &quot;Yes&quot;.

If &quot;Allow messages to be moved&quot; is checked in the Apple visionOS management tool or the Exchange policy on the Vision Pro has &quot;Prevent Move&quot; set to &quot;No&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to prevent Exchange messages from being moved or forwarded between email accounts.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276399</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276399r1146693_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must implement the management setting: treat AirDrop as an unmanaged destination.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>AirDrop is a way to send contact information or photos to other users with AirDrop enabled. This feature enables a possible attack vector for adversaries to exploit. Once the attacker has gained access to the information broadcast by this feature, the attacker may distribute this sensitive information very quickly and without DOD&apos;s control or awareness. By disabling this feature, the risk of mass data exfiltration will be mitigated.

Note: If the site uses Apple&apos;s optional Automatic Device Enrollment, this control is available as a supervised MDM control.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm &quot;Treat AirDrop as an unmanaged destination&quot; is enabled.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro. 

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Apple visionOS management tool, verify &quot;Treat AirDrop as unmanaged destination&quot; is checked.

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the c0onfiguration management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Sharing managed documents using AirDrop not allowed&quot; is listed.

If &quot;Treat AirDrop as unmanaged destination&quot; is disabled in the Apple visionOS management tool or the restrictions policy on the Vision Pro does not list &quot;Sharing managed documents using AirDrop not allowed&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to treat AirDrop as an unmanaged destination.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276400</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276400r1148316_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 users must complete required training.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The security posture on visionOS devices requires the device user to configure several required policy rules on their device. User-Based Enforcement (UBE) is required for these controls. In addition, if the authorizing official (AO) has approved users&apos; full access to the Apple App Store, users must receive training on risks. If a user is not aware of their responsibilities and does not comply with UBE requirements, the security posture of the visionOS mobile device and DOD sensitive data may become compromised.

SFR ID: NA</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review a sample of site User Agreements for visionOS device users or similar training records and training course content. Verify Vision Pro users have completed required training.

If any Vision Pro user has not completed required training, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Have all Vision Pro users complete training on the following topics. Users must acknowledge receipt of training via a signed User Agreement or similar written record.

Training topics:
- Operational security concerns introduced by unmanaged applications, including applications using global positioning system (GPS) tracking.
- Must ensure no DOD data is saved in an unmanaged app or transmitted from a personal app (for example, from personal email). 
- If the Purebred key management app is used, users are responsible for always maintaining positive control of their credentialed device. The DOD PKI certificate policy requires subscribers to maintain positive control of the devices that contain private keys and report any loss of control so the credentials can be revoked. Upon device retirement, turn in, or reassignment, ensure a factory data reset is performed prior to device handoff. Follow mobility service provider decommissioning procedures as applicable. 
- How to configure the following UBE controls (users must configure the control) and other controls on the Vision Pro:
** Never enable Guest User Mode. Use is prohibited.
** Never enable Developer Mode. Use is prohibited.
- AO guidance on acceptable use and restrictions, if any, on downloading and installing personal apps and data (music, photos, etc.).
- The Developer Strap must not be used with a DOD Vision Pro device without the explicit approval of the AO.
- How to disable Bluetooth when Bluetooth use is not approved by the AO.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276401</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276401r1146699_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>A managed photo app must be used to take and store work-related photos.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The visionOS Photos app is unmanaged and may sync photos with a device or user&apos;s personal iCloud account. Therefore, work-related photos must not be taken via the visionOS camera app or stored in the Photos app. A managed photo app must be used to take and manage work-related photos.

SFR ID: NA</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm a managed photos app is installed on the visionOS device.

This check procedure is performed on the Vision Pro.

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the DOD Configuration Profile from the Apple visionOS management tool.
5. Tap &quot;Apps&quot;.
6. Verify a photo capture and management app is listed.

If a managed photo capture and management app is not installed on the Vision Pro, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a managed photos app to take and manage work-related photos.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276402</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276402r1146702_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>low</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must not allow managed apps to write contacts to unmanaged contacts accounts.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Managed apps have been approved for the handling of DOD sensitive information. Unmanaged apps are provided for productivity and morale purposes but are not approved to handle DOD sensitive information. Examples of unmanaged apps include those for news services, travel guides, maps, and social networking. If a document were to be viewed in a managed app and the user had the ability to open this same document in an unmanaged app, this could lead to the compromise of sensitive DOD data. In some cases, the unmanaged apps are connected to cloud backup or social networks that would permit dissemination of DOD sensitive information to unauthorized individuals. Not allowing data to be opened within unmanaged apps mitigates the risk of compromising sensitive data.

SFR ID: FMT_SMF.1.1 #42, FDP_ACF_EXT.1.2</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm &quot;Allow managed apps to write contacts to unmanaged contacts accounts&quot; is disabled.

This check procedure is performed on both the Apple visionOS management tool and the Apple visionOS device.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the visionOS management tool, verify &quot;Allow managed apps to write contacts to unmanaged contacts accounts&quot; is unchecked.

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;. 
4. Tap the configuration profile from the visionOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Allow managed apps to write contacts to unmanaged contacts accounts&quot; is not listed.

If &quot;Allow managed apps to write contacts to unmanaged contacts accounts&quot; is checked in the visionOS management tool or the restrictions policy on the Vision Pro lists &quot;Allow managed apps to write contacts to unmanaged contacts accounts&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to prevent managed apps from writing contacts to unmanaged contacts accounts.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276403</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276403r1146705_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>low</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must not allow unmanaged apps to read contacts from managed contacts accounts.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Managed apps have been approved for the handling of DOD sensitive information. Unmanaged apps are provided for productivity and morale purposes but are not approved to handle DOD sensitive information. Examples of unmanaged apps include those for news services, travel guides, maps, and social networking. If a document were to be viewed in a managed app and the user had the ability to open this same document in an unmanaged app, this could lead to the compromise of sensitive DOD data. In some cases, the unmanaged apps are connected to cloud backup or social networks that would permit dissemination of DOD sensitive information to unauthorized individuals. Not allowing data to be opened within unmanaged apps mitigates the risk of compromising sensitive data.

SFR ID: FMT_SMF.1.1 #42, FDP_ACF_EXT.1.2</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm &quot;Allow unmanaged apps to read contacts from managed contacts accounts&quot; is disabled.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review.

In the visionOS management tool, verify &quot;Allow unmanaged apps to read contacts from managed contacts accounts&quot; is unchecked.

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Allow unmanaged apps to read contacts from managed contacts accounts&quot; is not listed.

If &quot;Allow unmanaged apps to read contacts from managed contacts accounts&quot; is checked in the visionOS management tool or the restrictions policy on the Vision Pro lists &quot;Allow unmanaged apps to read contacts from managed contacts accounts&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to prevent unmanaged apps from reading contacts from managed contacts accounts.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276404</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276404r1146708_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must implement the management setting: disable AirDrop.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>AirDrop is a way to send contact information or photos to other users with this same feature enabled. This feature enables a possible attack vector for adversaries to exploit. Once the attacker has gained access to the information broadcast by this feature, the attacker may distribute this sensitive information very quickly and without DOD&apos;s control or awareness. By disabling this feature, the risk of mass data exfiltration will be mitigated. 

Note: If the site uses Apple&apos;s optional Automatic Device Enrollment, this control is available as a supervised MDM control.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm it is disabled. 

This is a supervised-only control. If the Vision Pro being reviewed is not supervised by the MDM, this control is automatically a finding.

If the Vision Pro being reviewed is supervised by the MDM, follow these procedures:

This check procedure is performed on both the device management tool and the Vision Pro device.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Vision Pro management tool, verify &quot;Allow AirDrop&quot; is unchecked.

On the Vision Pro device:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;. 
4. Tap the configuration profile from the iOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;AirDrop not allowed&quot; is listed.

If &quot;AirDrop not allowed&quot; is not listed in the management tool and on the Apple device, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable the AllowAirDrop control in the management tool. This is a supervised-only control.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276405</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276405r1146711_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must disable &quot;Password AutoFill&quot; in browsers and applications.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The AutoFill functionality in browsers and applications allows the user to complete a form that contains sensitive information, such as PII, without previous knowledge of the information. By allowing using the AutoFill functionality, an adversary who learns a user&apos;s Vision Pro passcode, or who otherwise can unlock the device, may be able to further breach other systems by relying on the AutoFill feature to provide information unknown to the adversary. By disabling the AutoFill functionality, the risk of an adversary gaining further information about the device&apos;s user or compromising other systems is significantly mitigated.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>This is a supervised-only control. If the Vision Pro being reviewed is not supervised by the MDM, this control is automatically a finding.

If the Vision Pro being reviewed is supervised by the MDM, review configuration settings to confirm &quot;Password AutoFill is not allowed&quot; is disabled.

This check procedure is performed on both the visionOS device management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review.

In the visionOS management tool, verify &quot;Password AutoFill is not allowed&quot; is unchecked.

On the Vision Pro:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Password AutoFill is not allowed&quot; is listed.

If &quot;Password AutoFill is not allowed&quot; is not enabled in the visionOS management tool and on the Apple device, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable allow Password AutoFill in the management tool. This is a supervised-only control.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276406</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276406r1146714_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must disable password sharing.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>This control allows sharing passwords between Apple devices using AirDrop. This could lead to a compromise of the device password with an unauthorized person or device. DOD Apple device passwords must not be shared.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>This is a supervised-only control. If the Vision Pro being reviewed is not supervised by the MDM, this control is automatically a finding.

If the Vision Pro being reviewed is supervised by the MDM, review configuration settings to confirm &quot;Password Sharing is not allowed&quot; is enabled.

This check procedure is performed on both the device management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review.

In the visionOS management tool, verify &quot;Password Sharing is not allowed&quot; is checked.

On the visionOS:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Password Sharing is not allowed&quot; is listed.

If &quot;Password Sharing is not allowed&quot; is not enabled in the management tool and on the Apple device, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable allow password proximity sharing in the management tool. This is a supervised-only control.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276407</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276407r1146717_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The Apple visionOS 2 must be supervised by the MDM.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>When visionOS is not supervised, the DOD mobile service provider cannot control when new visionOS updates are installed on site-managed devices. Most updates should be installed immediately to mitigate new security vulnerabilities, while some sites need to test each update prior to installation to ensure critical missions are not adversely impacted by the update.

Several password and data protection controls can be implemented only when an Apple device is supervised.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm site-managed visionOS devices are supervised.

This check procedure is performed on both the Apple visionOS management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review.

In the visionOS management tool, verify all managed Apple devices are supervised (verification procedure will vary by MDM product).

Note: If the Apple device is not managed by an MDM and supervision is set up via Apple Configurator, this procedure is not applicable.

On the Vision Pro:
1. Open the Settings app.
2. Verify a message similar to the following appears on the screen: &quot;This AVP is supervised by (name of site DOD mobile service provider).&quot; 

If site-managed visionOS devices are not supervised, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Use one of the following methods to supervise visionOS devices managed by the DOD mobile service provider.

Method 1:
- Register all current and new visionOS devices in the DOD mobile service provider&apos;s Automated Device Management/Apple Business Manager (ABM) account.
- Enable supervision of managed visionOS devices in the MDM.

Method 2: 
- Configure each visionOS device using the Apple Configurator tool for Supervision.
- This method is usually only appropriate when MDM management of the DOD Apple device is not appropriate or an older device cannot be registered in ABM.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276408</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276408r1146720_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>low</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The Apple visionOS must be configured to disable automatic transfer of diagnostic data to an external device other than an MDM service with which the device has enrolled.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Many software systems automatically send diagnostic data to the manufacturer or a third-party. This data enables the developers to understand real-world field behavior and improve the product based on that information. Unfortunately, it can also reveal information about what DOD users are doing with the systems and what causes them to fail. An adversary embedded within the software development team or elsewhere could use the information acquired to breach mobile operating system security. Disabling automatic transfer of such information mitigates this risk.

SFR ID: FMT_SMF.1.1 #47a</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm &quot;Allow sending diagnostic and usage data to Apple&quot; is disabled.

This check procedure is performed on both the visionOS management tool and the visionOS device.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the visionOS management tool, verify &quot;Allow sending diagnostic and usage data to Apple&quot; is unchecked.

Alternatively, verify the text &quot;&lt;key&gt;allowDiagnosticSubmission&lt;/key&gt;&lt;false/&gt;&quot; appears in the configuration profile (.mobileconfig file).

On the Apple visionOS device: 
1. Open the Settings app. 
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the management policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Diagnostic submission not allowed&quot;.

Note: This setting also disables &quot;Share With App Developers&quot;.

If &quot;Allow sending diagnostic and usage data to Apple&quot; is checked in the visionOS management tool, &quot;&lt;key&gt;allowDiagnosticSubmission&lt;/key&gt;&lt;true/&gt;&quot; appears in the configuration profile, or the restrictions policy on the Apple visionOS device from the Apple visionOS management tool does not list &quot;Diagnostic submission not allowed&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable sending diagnostic data to an organization other than DOD.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276409</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276409r1146723_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS must implement the management setting: not allow a user to remove Apple visionOS configuration profiles that enforce DOD security requirements.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Configuration profiles define security policies on Apple visionOS devices. If a user can remove a configuration profile, the user can then change the configuration that had been enforced by that policy. Relaxing security policies may introduce vulnerabilities the profiles had mitigated. Configuring a profile to never be removed mitigates this risk.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm configuration profiles are not removable.

This check procedure is performed on both the Apple visionOS management tool and the Apple visionOS device. The procedures below assume the site is not enrolled in Apple&apos;s Automatic Device Enrollment and are not applicable to devices under MDM management.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Apple visionOS management tool, verify &quot;Security&quot; is set to &quot;Never&quot; and &quot;Automatically Remove Profile&quot; is set to &quot;Never&quot;.

On the Apple visionOS device:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;. 
4. Tap each Configuration Profile from the Apple visionOS management tool that contains the restrictions for the device.
5. Verify the &quot;Remove Profile&quot; button is not present.

If on the Apple visionOS management tool or the visionOS device the &quot;Remove Profile&quot; button is available on the configuration profile, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Configure the Apple visionOS configuration profile so that it can never be removed.

The procedure for implementing this control will vary depending on the MDM/EMM used by the mobile service provider.

When using Apple Configurator, under &quot;General Security&quot;, configure &quot;Security&quot; to &quot;Never&quot; and &quot;Automatically Remove Profile&quot; to &quot;Never&quot;.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276410</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276410r1146726_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must disable &quot;Allow network drive access in Files access&quot;.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Allowing network drive access by the Files app could lead to the introduction of malware or unauthorized software into the DOD IT infrastructure and compromise of sensitive DOD information and systems.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>This is a supervised-only control. If the Vision Pro being reviewed is not supervised by the MDM, this control is automatically a finding.

This check procedure is performed on both the device management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review.

In the visionOS management tool, verify &quot;Allow network drive access in Files access&quot; is unchecked.

On the Vision Pro device:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Network drives not accessible in Files app&quot; is listed.

If &quot;Allow network drive access in Files access&quot; is not disabled in the management tool and &quot;Network drives not accessible in Files app&quot; is not listed in Profile Restrictions on the Apple device, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable &quot;Allow network drive access in Files access&quot;.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276411</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276411r1146729_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must disable connections to Siri servers for the purpose of dictation.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>If a user can configure the security setting, the user could inadvertently or maliciously set it to a value that poses unacceptable risk to DOD information systems. An adversary could exploit vulnerabilities created by the weaker configuration to compromise DOD sensitive information. Dictation information could contain sensitive DOD information; therefore, should not leave the DOD control.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>If the Vision Pro being reviewed is supervised by the MDM, review configuration settings to confirm &quot;Disable connections to Siri servers for the purpose of dictation&quot; is disabled.

This check procedure is performed on the device management tool.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review.

In the visionOS management tool, verify &quot;Disable connections to Siri servers for the purpose of dictation&quot; is checked.

If connections to Siri servers are not disabled for dictation, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Configure the Apple visionOS configuration profile to disable connections to Siri servers for the purpose of dictation. This is a supervised-only control.

The procedure for implementing this control will vary depending on the MDM/EMM used by the mobile service provider.

In the MDM console, select &quot;disable connections to Siri servers for the purpose of dictation&quot;.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276412</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276412r1146732_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must disable copy/paste of data from managed to unmanaged applications.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>If a user can configure the security setting, the user could inadvertently or maliciously set it to a value that poses unacceptable risk to DOD information systems. An adversary could exploit vulnerabilities created by the weaker configuration to compromise DOD sensitive information.

SFR ID: FMT_SMF.1.1 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review.

In the visionOS management tool, verify &quot;Require managed pasteboard&quot; is set to &quot;True&quot;.

If &quot;Require managed pasteboard&quot; is not set to &quot;True&quot;, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Configure the Apple visionOS configuration profile to disable copy/paste of data from managed to unmanaged applications.

The procedure for implementing this control will vary depending on the MDM/EMM used by the mobile service provider.

In the MDM console, set &quot;Require managed pasteboard&quot; to &quot;True&quot;.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276413</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276413r1146735_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must have DOD root and intermediate PKI certificates installed.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>DOD root and intermediate PKI certificates are used to verify the authenticity of PKI certificates of users and web services. If the user is allowed to remove root and intermediate certificates, the user could allow an adversary to falsely sign a certificate in such a way that it could not be detected. Restricting the ability to remove DOD root and intermediate PKI certificates to the administrator mitigates this risk.

SFR ID: FMT_MOF_EXT.1.2 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Verify DOD intermediate and root certificates have been installed on Apple devices.

In the visionOS management tool, verify the DOD intermediate and root certificates are installed on the Apple device.

On the Vision Pro device:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Tap &quot;More Details&quot;.
7. Verify the DOD intermediate and root certificates are listed.

If DOD intermediate and root certificates are not installed on the Apple device, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install DOD intermediate and root certificates on managed mobile devices using the MDM.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276414</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276414r1147116_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must disable ChatGPT connection for Apple Intelligence.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The ChatGPT feature of Apple Intelligence allows DOD information to be downloaded from the DOD Vision Pro and processed by the ChatGPT application in the cloud. The ChatGPT feature of Apple Intelligence increases the risk of compromise of sensitive DOD information.

SFR ID: FMT_MOF_EXT.1.2 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>This check procedure is performed on the device management tool and the device.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review.

In the visionOS management tool, verify the following controls are set to Disable (the text may vary, depending on the UEM/MDM product): 
-Allow External Intelligence Integrations.
-Allow External Intelligence Integrations Sign In.

On the Vision Pro (Apple Intelligence capable device only):
1. Settings &gt;&gt; Apple Intelligence &amp; Siri &gt;&gt; ChatGPT.
2. Verify &quot;ChatGPT&quot; is grayed out and disabled.

If ChatGPT and other external AI app connections are not disabled in the management tool or are not grayed out and disabled on the Vision Pro, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable ChatGPT and other external AI app connections for Apple Intelligence.

-Set &quot;allowExternalIntelligenceIntegrations&quot; to &quot;False&quot;.
-Set &quot;allowExternalIntelligenceIntegrationsSignIn&quot; to &quot;False&quot;.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276415</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276415r1146741_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must disable the download of visionOS beta updates.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Beta operating system updates may contain features that could lead to the compromise of sensitive DOD information or provide a vector for the attack on the DOD network. The current STIG will not normally provide controls to disable these unsecure features.

SFR ID: FMT_MOF_EXT.1.2 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>This is a supervised-only control. If the Vision Pro being reviewed is not supervised by the MDM, this control is automatically a finding.

This check procedure is performed on both the device management tool and the Vision Pro.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review.

In the visionOS management tool, verify &quot;Allow installing configuration profiles (supervised only)&quot; is unchecked.

On the Vision Pro device:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;.
4. Tap the configuration profile from the visionOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Installing configuration profiles not allowed&quot; is listed.

If &quot;Allow installing configuration profiles&quot; is not disabled in the management tool, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable the installation of new configuration profiles. This will block the download and installation of beta visionOS updates. This is a supervised-only control.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276416</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276416r1146744_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>low</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple Vision Pro hardware must not be modified to use the Developer Strap unless use is approved on a case-by-case basis by the authorizing official (AO).</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The Apple Developer Strap provides a USB connector on the AVP and is used to download content on the AVP from a Mac. Using the Developer Strap without authorization is considered an unauthorized modification to the DOD owned AVP. The Developer Strap is sold by Apple only to registered Apple developers but can also be bought online. Data cannot be downloaded from the AVP to a connected Mac and does not currently provide access to an AVP enterprise network to the connected Mac. Only unmanaged apps can be uploaded to an AVP via the Developer Strap. Unauthorized unmanaged apps can be downloaded to the AVP from the connected Mac.

SFR ID: FMT_MOF_EXT.1.2 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Interview the site information system security officer (ISSO) and AVP users. Determine if the AVP Developer Strap is used at the site. If yes, verify the AO has approved its use by reviewing approval documentation. Verify AVP users are trained to not use the AVP developer Strap without AO approval (AVOS-02-011900).

If the AVP Developer Strap is used at the site without AO approval, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Train AVP users to not connect and use the Developer Strap unless the AO has approved its use for a specific use case (refer to AVOS-02-011900). AO use approval must be documented and must detail specific use cases for which its use is approved.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276417</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276417r1146747_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must disable the ability of the user to wipe the device.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>This feature must be disabled to comply with DOD electronic records retention requirements for mobile devices. Otherwise, mobile device users could wipe the device, which would violate DOD policy.

SFR ID: FMT_MOF_EXT.1.2 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm it is disabled. 

This is a supervised-only control. If the Vision Pro being reviewed is not supervised by the MDM, this control is automatically a finding.

If the Vision Pro being reviewed is supervised by the MDM, follow these procedures:

This check procedure is performed on both the device management tool and the Vision Pro device.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Vision Pro management tool, verify &quot;Allow erase all content and settings&quot; is unchecked.

On the Vision Pro device:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;. 
4. Tap the configuration profile from the Vision Pro management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Erase content and settings not allowed&quot; is listed.

If &quot;Allow erase all content and settings&quot; is not disabled in the management tool and on the Apple device, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable &quot;Allow Erase All Content and Settings&quot;. This is a supervised-only control.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276418</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276418r1146750_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>low</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must disable the use voice assistant (Siri) unless required to meet Section 508 compliance requirements.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Using voice assistants could expose sensitive DOD data to cloud-based servers during the processing of assistant requests.

SFR ID: FMT_MOF_EXT.1.2 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm it is disabled. Exception - Siri is allowed to meet Section 508 compliance requirements.

This check procedure is performed on both the device management tool and the Vision Pro device.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Vision Pro management tool, verify &quot;Allow Siri&quot; is unchecked.

On the Vision Pro device:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;. 
4. Tap the configuration profile from the Vision Pro management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Siri not allowed&quot; is listed.

If &quot;Allow Siri&quot; is not disabled in the management tool and on the Apple device, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable &quot;Allow Siri&quot;, unless required to meet Section 508 compliance requirements.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276419</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276419r1146753_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>low</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must disable Apple Intelligence feature: Image Generation.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The security of the Apple Intelligence system has not been vetted by the DOD and the risk to DOD sensitive information is not known at this time. Therefore, Apple intelligence features will be disabled until more information is available.

SFR ID: FMT_MOF_EXT.1.2 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm it is disabled. Note: this control is only applicable to Apple Intelligence capable Vision Pros.

This is a supervised-only control. If the Vision Pro being reviewed is not supervised by the MDM, this control is automatically a finding.

If the Vision Pro being reviewed is supervised by the MDM, follow these procedures:

This check procedure is performed on both the device management tool and the Vision Pro device.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Vision Pro management tool, verify the Apple Intelligence feature: Image Generation is unchecked.

On the Vision Pro device:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;. 
4. Tap the configuration profile from the Vision Pro management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Image Playground not allowed&quot; is listed.

If Image Generation is not disabled in the management tool and on the Apple device, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable Apple Intelligence feature: Image Generation. This is a supervised-only control.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276420</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276420r1146756_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>low</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must disable Apple Intelligence feature: generate new Genmoji.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>The security of the Apple Intelligence system has not been vetted by the DOD and the risk to DOD sensitive information is not known at this time. Therefore, Apple intelligence features will be disabled until more information is available.

SFR ID: FMT_MOF_EXT.1.2 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm it is disabled. Note: this control is only applicable to Apple Intelligence capable Vision Pro.

This is a supervised-only control. If the Vision Pro being reviewed is not supervised by the MDM, this control is automatically a finding.

If the Vision Pro being reviewed is supervised by the MDM, follow these procedures:

This check procedure is performed on both the device management tool and the Vision Pro device.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Vision Pro management tool, verify the Apple Intelligence feature: generate new Genmoji is unchecked.

On the Vision Pro device:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;. 
4. Tap the configuration profile from the visionOS management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Genmoji not allowed&quot; is listed.

If generate new Genmoji is not disabled in the management tool and on the Apple device, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable Apple Intelligence feature: generate new Genmoji. This is a supervised-only control.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276421</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276421r1147110_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>DOD Apple visionOS 2 devices must have a Mobile Threat Detection (MTD) app installed.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>DOD mobile devices are in constant risk of cyber threats. Mobile Threat Detection (MTD) apps mitigate these risks by providing real-time threat detection, malware prevention, and vulnerability analysis.

SFR ID: FMT_MOF_EXT.1.2 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Confirm an MTD app is installed on managed Vision Pro.

This check procedure is performed on both the device management tool and the Vision Pro device.

In the Vision Pro management tool, verify an MTD app is listed as a managed app being deployed to site managed devices.

On the Vision Pro device:
1. Open the Settings app.
2. Tap &quot;Apps&quot;.
3. Verify an MTD app is listed.

If an MTD app is not installed on the device, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Deploy a site approved MTD app via the MDM server to manage Vision Pro.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-276422</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-276422r1148317_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>low</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>DOD Apple visionOS 2 devices must disable screenshots and screen recordings.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>A screenshot or screen recording of sensitive DOD information could lead to the inadvertent exposure of that information.

SFR ID: FMT_MOF_EXT.1.2 #47</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Review configuration settings to confirm screenshot and screen recording is disabled.

This check procedure is performed on both the device management tool and the Vision Pro device.

Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. 

In the Vision Pro management tool, verify &quot;Allow screenshot and screen recording&quot; is unchecked.

On the Vision Pro device:
1. Open the Settings app.
2. Tap &quot;General&quot;.
3. Tap &quot;VPN &amp; Device Management&quot;. 
4. Tap the configuration profile from the Vision Pro management tool containing the restrictions policy.
5. Tap &quot;Restrictions&quot;.
6. Verify &quot;Screen capture not allowed&quot; is listed.

If &quot;Allow screenshot and screen recording&quot; is listed in the management tool or &quot;Screen capture not allowed&quot; is not listed on the Apple device, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Install a configuration profile to disable the screenshot and screen recording.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    <VULN>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Num</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>V-279327</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_ID</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>SV-279327r1148314_rule</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Severity</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>medium</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Rule_Title</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Apple visionOS 2 must implement the management setting: disable the Bluetooth radio.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Vuln_Discuss</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Authorizing Official (AO) approval is required before the Apple device Bluetooth radio can be enabled. All AO approvals should be documented and based on critical mission need.  Use of Bluetooth may lead to the exposure of sensitive DOD information in some operational environments.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Check_Content</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>Determine if the site AO has approved the use of Apple device Bluetooth radios. Look for a document showing AO approval. All AO approvals should be documented and based on critical mission need. 

If not approved, review configuration settings on the Vision Pro to confirm Bluetooth is disabled. If approved, this requirement is not applicable.

If the AO has not approved the use Bluetooth and Bluetooth is not disabled on the Vision Pro device, this is a finding.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STIG_DATA>
        <VULN_ATTRIBUTE>Fix_Text</VULN_ATTRIBUTE>
        <ATTRIBUTE_DATA>If the AO has not approved the use of the Apple device Bluetooth radio, disable Bluetooth use. This requirement is Not Applicable if the AO has approved Bluetooth use.

There are two steps to this procedure:
1. MDM sends a device command to site-managed Apple devices to disable Bluetooth during initial setup of device.
2. User is trained to always keep Bluetooth disabled. This requirement is covered in AVOS-02-011900. This is a User-Based Enforcement (UBE) requirement.</ATTRIBUTE_DATA>
      </STIG_DATA>
      <STATUS>Not_Reviewed</STATUS>
      <FINDING_DETAILS></FINDING_DETAILS>
      <COMMENTS></COMMENTS>
    </VULN>
    </iSTIG>
  </STIGS>
</CHECKLIST>