Knowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search courses, individual lessons, wiki entries, books, podcasts, magazine articles, Daily Cyber News, and Darwin.

Cross-Framework Defense Map

AC-19 — Access Control for Mobile Devices

Trace this SP 800-53 control to NIST CSF outcomes, CUI requirements, D3FEND defensive techniques, ATT&CK relationships, and related learning resources.

AC — Access Control · NIST SP 800-53 Release 5.2.0

Open the complete control page →
NIST SP 800-53 control context

AC-19 — Access Control for Mobile Devices

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

Read the official statement, discussion, parameters, enhancements, and assessment methods →

Outcome layer

NIST CSF 2.0 informative references

These CSF Subcategories list this base control or one of its enhancements in the imported NIST informative reference.

CUI protection layer

NIST SP 800-171 and SP 800-172

SP 800-171 requirements sourcing this control

SP 800-172 enhanced requirements sourcing this control

No relationship is present in the currently imported source datasets.
Defensive engineering layer

MITRE D3FEND techniques

No relationship is present in the currently imported source datasets.
Adversary layer

MITRE ATT&CK relationships

Curated mitigation mappings

No relationship is present in the currently imported source datasets.

Inferred behavior relationships

Experimental: These relationships are inferred through D3FEND and must be validated against architecture, telemetry, and threat context.

No relationship is present in the currently imported source datasets.
Relationship boundaries

Use the map without overclaiming.

A CSF informative reference is not an equivalence statement. A source-control relationship is not proof of implementation. A D3FEND semantic relationship is not a product claim. An inferred ATT&CK link is a hypothesis for engineering analysis.

Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST or MITRE. Informative references and cross-framework relationships support navigation and analysis; they do not establish compliance, applicability, equivalence, control inheritance, or guaranteed mitigation effectiveness.