Skip to content

3.1.12 — Eyes on Remote Access

Monitor and control remote access sessions.

Remote access isn’t just VPN to headquarters. It includes:

  • VPN connections
  • Remote desktop sessions
  • Cloud email access from outside the office
  • Cloud file storage access
  • AWS/Azure/GCP console access
  • Any connection from outside your physical environment to systems containing CUI

For every remote session, you need to know: who’s connected, from where, using what method, and what they’re accessing. You need the ability to terminate any session immediately.

Don’t forget cloud services — if someone accesses M365 or AWS from home, that’s remote access.


Your assessor needs a “yes” to every row:

#QuestionWhat “yes” looks like
1Is remote access permitted and defined?A policy stating when, how, and by whom
2Are permitted methods identified?VPN, RDP, cloud — each one documented
3Are remote sessions controlled?You can manage, restrict, and terminate them
4Are remote sessions monitored?You can see who’s connected and what they’re doing

Documents they’ll review: Access control policy, remote access procedures, configuration management plan, system security plan, system config, remote access authorizations, audit logs

People they’ll talk to: Remote access managers, sysadmins, information security staff

Live demos they’ll ask for: “Show me who is connected remotely right now. Show me you can terminate a session.”


These are the actual questions. Have answers ready.

  • “What policies identify when remote access is permitted and what methods must be used?”
  • “Are systems configured to only permit approved remote access sessions?”
  • “Are automated or manual mechanisms used for monitoring remote connections?”
  • “Can you show me who is currently connected remotely?”

No remote access policy. People connect however they want with no defined rules.

Cloud access is invisible. VPN is monitored but M365, AWS Console, and other cloud access isn’t tracked.

Can’t terminate sessions. You can see who’s connected but can’t force-disconnect them.

Personal devices with no controls. Remote access from unmanaged devices with no visibility.



RequirementWhy it matters here
3.1.13 — Encrypt Remote SessionsEncrypting the sessions you monitor here
3.1.14 — One Front DoorRouting through managed access points
3.5.3 — Multifactor AuthMFA required for remote access

🔒

Step-by-step guides for Microsoft 365, AWS, Azure, and GCP are available to Ancitus clients.

Start a conversation →

CMMC Practice ID: AC.L2-3.1.12 | SPRS Weight: 5 points | POA&M Eligible: No