# AC-19 Access Control for Mobile Devices

NIST SP 800-53 control. Family: AC Access Control. Function: preventative. Baselines: low, moderate, high. Mapping licence: CC BY-SA 4.0.

Statement: a. Establish configuration requirements, connection requirements, and implementation guidance for organization-controlled mobile devices, to include when such devices are outside of controlled areas; and b. Authorize the connection of mobile devices to organizational systems.
Guidance: A mobile device is a computing device that has a small form factor such that it can easily be carried by a single individual; is designed to operate without a physical connection; possesses local, non-removable or removable data storage; and includes a self-contained power source. Mobile device functionality may also include voice communication capabilities, on-board sensors that allow the device to capture information, and/or built-in features for synchronizing local data with remote locations. Examples include smart phones and tablets. Mobile devices are typically associated with a single individual. The processing, storage, and transmission capability of the mobile device may be comparable to or merely a subset of notebook/desktop systems, depending on the nature and intended purpose of the device. Protection and control of mobile devices is behavior or policy-based and requires users to take physical action to protect and control such devices when outside of controlled areas. Controlled areas are spaces for which organizations provide physical or procedural controls to meet the requirements established for protecting information and systems. Due to the large variety of mobile devices with different characteristics and capabilities, organizational restrictions may vary for the different classes or types of such devices. Usage restrictions and specific implementation guidance for mobile devices include configuration management, device identification and authentication, implementation of mandatory protective software, scanning devices for malicious code, updating virus protection software, scanning for critical software updates and patches, conducting primary operating system (and possibly other resident software) integrity checks, and disabling unnecessary hardware. Usage restrictions and authorization to connect may vary among organizational systems. For example, the organization may authorize the connection of mobile devices to its network and impose a set of usage restrictions, while a system owner may withhold authorization for mobile device connection to specific applications or impose additional usage restrictions before allowing mobile device connections to a system. Adequate security for mobile devices goes beyond the requirements specified in AC-19. Many safeguards for mobile devices are reflected in other controls. AC-20 addresses mobile devices that are not organization-controlled.

## Enhancements (2)
- AC-19(04) Restrictions for Classified Information
- AC-19(05) Full Device or Container-based Encryption. Baselines: moderate, high
Withdrawn by NIST: AC-19(01) (now in MP-07); AC-19(02) (now in MP-07); AC-19(03) (now in MP-07).
Each enhancement's statement: /api/v1/controls/AC-19?fields=enhancements

## Patterns that use it (6)
- Critical (2): SP-007 Wireless- Public Hotspot Pattern; SP-015 Secure Remote Working
- Important (2): SP-006 Wireless- Private Network Pattern; SP-052 Decentralised Identity & Verifiable Credentials (draft)
- Standard (2): SP-001 Client Module; SP-026 PCI Full Environment

## Clauses by framework (47 frameworks)
- iso_27001_2022: A.5.14, A.7.9, A.8.1
- iso_27002_2022: 7.9, 8.1
- cobit_2019: DSS05
- pci_dss_v4: 1.5
- nist_csf_2: PR.AA-05
- cis_controls_v8: CIS 4.11, CIS 4.12
- nis2: Art. 21(2)(i)
- mas_trm: 9
- bsi_grundschutz: CON.7, ORP.4
- anssi: Hygiene.19, SecNumCloud.10.6
- osfi_b13: B-13.3.2
- finma_circular: IV.B.d(59), IV.C(64)
- gdpr: Art.32(1)(a), Art.32(1)(b)
- dora: Art.9(4)(a), Art.9(4)(c)
- bio2: 7.9, 8.1
- rbi_csf: Annex1.8, Annex1.12
- fisc: FISC.T10
- hkma_tme1: TME1.8.5, TME1.10.2
- mlps_2: 8.3
- cbb_tm: TM-6
- cbuae: CR-4
- nca_ecc: 2-6
- qatar_nia: AC
- sama_csf: 3.1, 3.3, 3.8
- uae_ia: T9
- bog_cisd: CISD-VIII
- bom_ctrm: 3.12
- cbe_csf: CTO-1, CTO-7
- cbn_csf: Part3.2
- sa_js2: JS2-7.1
- bot_cyber: Ch2.6, Ch9.1
- cpmi_pfmi: CG.PR
- ecb_croe: CROE.2.3.5
- ffiec_is: II.C.15(c)
- nydfs_500: 500.7
- sebi_cscrf: PR.ES
- cmmc_2: AC
- fca_sysc_13: SYSC 13.7.3
- fda_21_cfr_11: §11.10(h)
- hitrust_csf: 01.b, 01.d, 05.c
- iso_27799: 6.3, 11.2
- lloyds_ms: MS8.3
- naic_ds: 4-access
- nhs_dspt: NDG-9.7
- solvency_ii: EIOPA-ICT-4.6
- csa_ccm_v4: UEM-01, UEM-13
- csa_aicm: UEM-01, UEM-13
OSA's mapping for iso_27001_2022 and nist_csf_2 takes NIST's published crosswalk as its base. A clause not marked as OSA's own is in that crosswalk.

## More
- This control as JSON, with guidance and ATT&CK techniques: /api/v1/controls/AC-19
- Clauses only: /api/v1/controls/AC-19?fields=mappings
- Page for people: /controls/ac-19/