CMMC Practice AC.1.001

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


CMMC Version 1.02, pg. 50

Bold Coast Security 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. At level 1 you can 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. At Level 2, you will create a policy to this effect, and at level 3 a plan to ensure it is complied with, such as scheduling walk-throughs of the company. You can also disconnect unused network ports. At level 4 you can record the outcome of those walkthroughs, and if there are continued issues, you may need to put technical controls in place such as Network Access Control (NAC) as mentioned in AC.3.012.

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 (AC.1.002).