CMMCpedia Download

Requirements / Access Control (AC)

AC.L2-3.1.15

Privileged Remote Access

Official Source Material

Authorize remote execution of privileged commands and remote access to security-relevant information.

Determine if:

  1. [a] privileged commands authorized for remote execution are identified;
  2. [b] security-relevant information authorized to be accessed remotely is identified;
  3. [c] the execution of the identified privileged commands via remote access is authorized; and
  4. [d] access to the identified security-relevant information via remote access is authorized.

Source: CMMC Assessment Guide - Level 2, Version 2.13, September 2024

Practitioner Guidance

How to meet it

This requirement governs remote administration, and it is answered with authorization lists.

Identify which privileged commands may be executed remotely [a] and which security-relevant information may be reached remotely [b], then show both are authorized [c] and [d]. If administrators can do administrative work from outside the boundary, write down what they may do, from where, and under whose approval. Avoiding remote privilege entirely is the strongest position. Where the business needs it, the documentation is the control.

Authorize by role, not by command inventory.

Enumerating individual commands produces a list nobody can maintain. State instead that the commands granted by your named administrator roles in Microsoft Entra ID or Active Directory are authorized for remote execution by the people holding those roles. An assessor who wants the command list gets the role definitions that bound it, a better answer than a stale spreadsheet.

If privilege requires being inside the boundary first, say exactly that.

A clean posture for VPN-centric environments: no privileged commands are authorized for remote execution. Administrators must first establish an approved remote access session under AC.L2-3.1.12 and AC.L2-3.1.14, and administration then happens inside the controlled boundary. Write it that way in the system security plan and enforce it. The statement converts four objectives into one architectural fact.

Inventory your remote execution vectors.

Intune script deployment, remote monitoring and management (RMM) agents, PowerShell remoting, SSH, and patch management platforms all execute privileged commands on machines the operator is not sitting at. Each belongs under [a] with its authorized operators under [c]. These vectors are easy to forget precisely because they are routine.

Security-relevant information is yours to define.

Audit log configuration, security tool settings, firewall rule sets, and access control configuration are the core of it. Name what qualifies in your environment and who may reach it remotely, and [b] and [d] are complete. Browsing an admin portal from home is remote access to security-relevant information, so cover it with the same role-based authorization and conditional access controls.

Edge cases

  • In a fully cloud environment every administrative action crosses the internet, so there is no non-remote administration to retreat to. The role-based authorization statement, enforced by conditional access from managed devices, is the fitting answer for [c] and [d].
  • Solve AC.L2-3.1.12 through AC.L2-3.1.15 as one design rather than four documents. They describe the same remote access architecture from four angles, and a system security plan that tells one coherent story assesses better than four disconnected answers.

CMMCpedia is independently maintained and is not affiliated with the U.S. Department of Defense. The content is educational. It is not legal advice, and it does not guarantee certification.