This post gives a practical, testable approach for validating IA.L1-B.1.V — the requirement to verify identification of users, processes, and devices — under FAR 52.204-21 and CMMC 2.0 Level 1, with step-by-step test procedures, example commands/logs, small-business scenarios, and recommended evidence artifacts to produce during an assessment.
Understanding the control and what auditors expect
At its core IA.L1-B.1.V requires the organization to ensure that actions on its information systems can be attributed to an individual user, an authorized process, or an identified device. For a Compliance Framework assessment this means demonstrating: unique user identities (no shared human accounts), service/process identities for automated tasks, and device identity for endpoints accessing work resources. Auditors will look for documented policies, enforcement mechanisms (e.g., unique accounts, certificates, MDM enrollment, 802.1X/NAC), and concrete evidence (log entries, access requests, configuration screenshots, exported reports).
Practical testing strategy (high level)
Design tests to cover all three identity domains: user, process, and device. Each test should include: a triggering action (e.g., login, service start, device connect), capture of relevant logs or artifacts, verification steps to ensure the identity is recorded and non-repudiable, and mapping to a policy control. Tests should be repeatable (document test steps), minimally invasive (use test accounts/devices), and scheduled (periodic and after changes). For small businesses this can be run quarterly or aligned with contract audits.
Test 1 — User identification: how to verify unique human identities
Steps: 1) Create or use a dedicated test user in your identity store (AD/Azure AD/local accounts). 2) Perform an authentication action: remote RDP/SSH login, web app sign-in, or VPN connection. 3) Collect logs from the system (Windows Security events, Linux auth/syslog, VPN/RADIUS logs) and your identity provider (Azure AD sign-in logs, IdP audit). Commands and checks: on Windows run PowerShell: Get-WinEvent -FilterHashtable @{LogName='Security'; ID=4624} | Where-Object {$_.Properties[5].Value -eq 'TESTUSER'} | Select TimeCreated,Message; on Linux grep 'sshd' /var/log/auth.log or use ausearch -m USER_LOGIN -ts today. Expected result: logs contain the test user's unique username, timestamp, source IP, and authentication method; evidence artifacts: exported log lines, screenshots of IdP sign-in record, ticket linking account creation to HR/req. Also test that shared/hardcoded accounts cannot be used for interactive login (search for common account names and verify policy prohibits interactive use).
Test 2 — Process identification: validating service and automated identities
Steps: identify critical services (backup, scheduler, CI/CD runners) and verify they run under named service accounts or container service identities. On Windows inspect services: Get-Service -Name 'YourService' | Select Name,Status; and check the Log On As account. Collect process start logs (Windows Event ID 4688 with Sysmon enabled; on Linux enable auditd execve/audit rules: auditctl -a exit,always -F arch=b64 -S execve -k exec_log) and look up entries for the process start. For containers, verify Kubernetes service account names and bound RBAC: kubectl get sa -n namespace; kubectl get rolebinding -n namespace. Expected result: each automated action is attributable to a named service account or process identity, with log entries showing process name, PID, parent PID, and the service account or token used. Evidence: exported Sysmon or auditd records, service account definitions, and configuration files showing credentials are not embedded in scripts (sample grep -R "password" /opt/app).
Test 3 — Device identification: proving endpoints are identified before access
Steps: demonstrate that devices are enrolled and identifiable before accessing CUI or sensitive services. For MDM-managed endpoints (Intune/Workspace ONE), export the device inventory and pick a device to authenticate to a cloud service; capture the device ID and certificate ID in the authentication log. For network access, show RADIUS/NAC logs during 802.1X authentication (e.g., grep 'Accepted' /var/log/radius/radius.log) and confirm the NAS returned the device MAC and certificate thumbprint. For certificate-based device ID, run openssl x509 -in device-cert.pem -noout -fingerprint and match the fingerprint to the auth log. Expected result: logs and inventory show a one-to-one mapping between device identifier (hostname/MAC/device ID/cert thumbprint) and network/session event; evidence: device inventory export CSV, RADIUS/NAC auth log excerpt, certificate fingerprint match screenshot.
Implementation notes specific to Compliance Framework
For Compliance Framework implementations, tie each test back to your documented control objective and acceptance criteria. Maintain a test matrix that maps: control statement → test case → evidence file name → tester initials/date. Store artifacts in a secure evidence repository (versioned, access-controlled) with retention that meets your policy. Small businesses should use built-in platform capabilities first (Windows Event Viewer, auditd, Azure AD sign-in logs) and consolidate into a lightweight SIEM (Wazuh or Splunk Free) to simplify evidence collection and querying during an assessment.
Small-business real-world scenarios and examples
Scenario A: 25-person contractor using Microsoft 365 and company-managed laptops. Practical steps include enforcing Azure AD join for devices, enabling Intune enrollment, enabling sign-in logs and conditional access, and running these tests: create a test user, perform cloud sign-in, export Azure sign-in logs (CSV) and show deviceId/deviceDetail fields. Scenario B: Hybrid shop with on-prem file server and OpenSSH VPN. Test by creating a test SSH key, authenticate via RADIUS-backed VPN while recording RADIUS accounting entries, then verify the OpenSSH logs include the username and source IP and the RADIUS log includes the device MAC passed by the VPN endpoint.
Compliance tips, evidence artifacts, and best practices
Best practices: 1) Eliminate shared human accounts; where shared access is necessary, require jump hosts or temporary privileged elevation with audit. 2) Use unique service accounts for each automated function and rotate credentials or use managed identities. 3) Enforce device enrollment and use certificate-based device ID where possible. 4) Centralize logs in a SIEM and retain at least 90 days (or your policy-required retention) for user/process/device events. Evidence items to collect: account creation tickets, exported log queries (with filters & timestamps), screenshots of MDM/NAC device details, configuration files showing service account names, and your test matrix with pass/fail annotations. For small teams, script log exports (PowerShell, awk/sed) to produce reproducible artifacts for auditors.
Risks of failing to implement and test the control
Without verifiable identification you face increased risk of unauthorized access, inability to perform forensic investigations, and contract penalties under FAR 52.204-21 or lost DoD work under CMMC. Practically, an un-attributable action can allow insider misuse, malware to blend into legitimate processes, or rogue devices to exfiltrate data undetected. Failure to provide clear audit evidence during an assessment can result in findings, remediation orders, or contract suspension.
Summary — implement measurable tests, collect reproducible evidence, and automate where possible: build a small test suite that covers login flows, service/process starts, and device enrollments, export the supporting logs (with timestamps and identifiers), and keep a documented mapping from tests to policy. These steps will make demonstrating IA.L1-B.1.V concrete, repeatable, and audit-ready for Compliance Framework assessments.
