Google Android 13 BYOAD STIG Y24 M04 Checklist Details (Checklist Revisions)
Supporting Resources:
-
Download Standalone XCCDF 1.1.4 - Google Android 13 BYOAD STIG
- Defense Information Systems Agency
Target:
Target | CPE Name |
---|---|
Google Android 13 | cpe:/o:google:android:13.0 (View CVEs) |
Checklist Highlights
- Checklist Name:
- Google Android 13 BYOAD STIG
- Checklist ID:
- 1071
- Version:
- Y24 M04
- Type:
- Compliance
- Review Status:
- Final
- Authority:
- Governmental Authority: Defense Information Systems Agency
- Original Publication Date:
- 09/22/2023
Checklist Summary:
The Red Hat Enterprise Linux 9 (RHEL 9) Security Technical Implementation Guide (STIG) is published as a tool to improve the security of the Department of Defense (DOD) information systems. The requirements were developed from the General Purpose Operating System Security Requirements Guide (GPOS SRG). The vulnerabilities discussed in this document are applicable to RHEL 9 Desktop and Server installations. This document is meant for use in conjunction with the Enclave, Network Infrastructure, Secure Remote Computing, and appropriate application STIGs.
Checklist Role:
- Operating System
Known Issues:
Not provided.
Target Audience:
Parties within the DOD and federal government’s computing environments can obtain the applicable STIG from the DOD Cyber Exchange website at https://cyber.mil/. This site contains the latest copies of STIGs, SRGs, and other related security information. Those without a Common Access Card (CAC) that has DOD Certificates can obtain the STIG from https://public.cyber.mil/.
Target Operational Environment:
- Managed
- Specialized Security-Limited Functionality (SSLF)
Testing Information:
Not provided.
Regulatory Compliance:
This document is provided under the authority of DODI 8500.01.
Comments/Warnings/Miscellaneous:
Not provided.
Disclaimer:
DISA accepts no liability for the consequences of applying specific configuration settings made on the basis of the SRGs/STIGs. It must be noted that the configuration settings specified should be evaluated in a local, representative test environment before implementation in a production environment, especially within large user populations. The extensive variety of environments makes it impossible to test these configuration settings for all potential software configurations. For some production environments, failure to test before implementation may lead to a loss of required functionality. Evaluating the risks and benefits to a system’s particular circumstances and requirements is the system owner’s responsibility. The evaluated risks resulting from not applying specified configuration settings must be approved by the responsible AO. Furthermore, DISA implies no warranty that the application of all specified configurations will make a system 100 percent secure. Security guidance is provided for the DOD. While other agencies and organizations are free to use it, care must be given to ensure that all applicable security guidance is applied at both the device hardening level and the architectural level due to the fact that some settings may not be configurable in environments outside the DOD architecture.
Product Support:
Not provided.
Point of Contact:
Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
Sponsor:
Not provided.
Licensing:
Not provided.
Change History:
NEW checklist - 10/12/23 updated to final - 11/13/2023 Update Version and Resources - 06/10/2024
Dependency/Requirements:
URL | Description |
---|
References:
Reference URL | Description |
---|