Control and Manage Physical Access Devices – NIST SP 800-171 & CMMC 2.0
How do you meet the security requirement 3.10.5 “Control and manage physical access devices”?

A physical access device refers to objects such as traditional keys used to unlock doors, and RFID key cards/fobs. Physical access devices grant access to locked doors. Something like a YubiKey or a DoD Common Access Card (CAC) may also be a physical access device even though they also provide access to computer systems. The key concept to grasp is that anything that unlocks a door or provides access to a location is a physical access device.
When personnel no longer require extended access to your facility then you should take or disable their physical access device. As part of your onboarding process, have terminated personnel return their keys or RFID cards.
If someone loses their RFID card you should disable it. If they lose a traditional key, you should change the lock to the doors where the key is used.
To manage physical access devices, you should first create an inventory of them. RFID cards and traditional keys often have serial numbers associated with them. Document these serial numbers and the personnel the keys were assigned to. You should also document what areas of your facility these keys grant access to. It is also a clever idea to document when you provided the physical access device to the person and when they turned it back in.
In summary a physical access device is any device used to provide access to your facility. This can include traditional keys and key fobs. You should only give physical access devices to personnel who are authorized to have extended access to your facility. You should take back physical access devices from terminated personnel and maintain an inventory of them.
Keep reading
More on NIST SP 800-171 & CMMC Level 2.

IA.L2-3.5.7: Technical How-To: Configure Password Policies on Windows, Linux, and macOS to Enforce Complexity and Character Changes
Step-by-step guidance to configure password complexity and character-change controls on Windows, Linux, and macOS to meet NIST SP 800-171 Rev.2 / CMMC 2.0 Level 2 IA.L2-3.5.7.

AU.L2-3.3.7: Validate and Test Clock Synchronization
Step-by-step guidance to validate, test, and collect audit-ready evidence for clock synchronization to meet NIST SP 800-171 Rev.2 / CMMC 2.0 Level 2 AU.L2-3.3.7 compliance.

CM.L2-3.4.3: Use Version Control and Configuration Management
Practical steps, tools, and small-business examples to track, review, approve, and audit configuration changes to meet NIST SP 800-171 Rev.2 / CMMC 2.0 CM.L2-3.4.3.
See LakeRidge in action.
Talk with our team about your framework, your gaps, and the right plan.
Get a demo