CMMC Practice AC.L1-3.1.1

Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).

Monarch ISC Guidance

The very first practice is to control access to your network by assigning all users unique usernames and passwords and having a user provisioning and deprovisioning process. The ensures only authorized personnel are allowed access to the network and services. While user access is the focus of this control, the practice and examples also mention controlling device access. You should distribute a statement to all staff that you will disable and remove unauthorized devices from the network, and that IT must authorize all devices before they can be connected.
Security Catapult

Be prepared for CMMC

Our Q&A assessment tool is designed by security advisors for MSPs and DoD contractors of all sizes.

Try now for free

Understand your gaps
Security Catapult

Understand your gaps

See compliance gaps, compliance scores and proactive security tasks in a single interface.

Try now for free

Validate NIST SP 800-171
Security Catapult

Validate NIST SP 800-171

Based on your CMMC answers, we let you know where you stand on NIST.

Try now for free

Build a plan of action
Security Catapult

Build a plan of action

Track your burn down and stay on top of security needs.

Try now for free

Build your policy
Security Catapult

Build your policy

Say goodbye to maintaining a security policy. We do it for you.

Try now for free

Discussion From Source

DISCUSSION FROM SOURCE: DRAFT NIST SP 800-171 R2 Access control policies (e.g., identity or role-based policies, control matrices, and cryptography) control access between active entities or subjects (i.e., users or processes acting on behalf of users) and passive entities or objects (e.g., devices, files, records, and domains) in systems. Access enforcement mechanisms can be employed at the application and service level to provide increased information security. Other systems include systems internal and external to the organization. This requirement focuses on account management for systems and applications. The definition of and enforcement of access authorizations, other than those determined by account type (e.g., privileged vs non-privileged) are addressed in requirement 3.1.2.

References