CMMC Navigatorby Foxx Cyber Bedrock CMMC

↑↓ to move, Enter to open, Esc to close. Try 3.5.3, AC.L2-3.1.1, MFA or unmarked.

3.1.1Know who and what is allowed on your systems

Keep a real list of the people, service accounts, and devices allowed on your systems, and let nothing else on.

The requirement, verbatim

NIST SP 800-171 Rev. 2 · 3.1.1

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

Requirement 3.1.1, practice name in the CMMC assessment guide: Authorized Access Control.

NIST's discussion

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 verses [sic] non-privileged) are addressed in requirement 3.1.2 (AC.L2-3.1.2).

NIST SP 800-171 Rev. 2, discussion under 3.1.1. Whitespace normalised; wording unchanged.

Assessment objectives

An assessor decides each of these separately. The requirement is met only when every objective is.

  1. [a] authorized users are identified
  2. [b] processes acting on behalf of authorized users are identified
  3. [c] devices (and other systems) authorized to connect to the system are identified
  4. [d] system access is limited to authorized users
  5. [e] system access is limited to processes acting on behalf of authorized users
  6. [f] system access is limited to authorized devices (including other systems)

NIST SP 800-171A, determination statements for 3.1.1.

For assessors: examine, interview, test

NIST SP 800-171A names what an assessor may examine, whom they may interview, and what they may test for this requirement. Assessors select from these lists; they are not a checklist of everything you must produce.

Examine
  • Access control policy
  • procedures addressing account management
  • system security plan
  • system design documentation
  • system configuration settings and associated documentation
  • list of active system accounts and the name of the individual associated with each account
  • notifications or records of recently transferred, separated, or terminated employees
  • list of conditions for group and role membership
  • list of recently disabled system accounts along with the name of the individual associated with each account
  • access authorization records
  • account management compliance reviews
  • system audit logs and records
  • other relevant documents or records
Interview
  • Personnel with account management responsibilities
  • system or network administrators
  • personnel with information security responsibilities
Test
  • Organizational processes for managing system accounts
  • mechanisms for implementing account management

NIST SP 800-171A, potential assessment methods and objects for 3.1.1.

Evidence

No evidence examples are published for this requirement yet. The objectives above are what an assessor checks; evidence is whatever shows each one is true in your environment, dated and kept with your system security plan.

Scoring weight

Worth 5 points. Not meeting this requirement subtracts 5 from your 110-point SPRS score. These are the requirements with the largest effect on your posture.

DoD NIST SP 800-171 Assessment Methodology v1.2.1 weighting, as carried in the Bedrock scoring table. The score starts at 110 and subtracts the weight of every requirement not met.

In Rev. 3

Rev. 2 is what your contract requires today. A standing DoD class deviation keeps Rev. 2 in force; NIST has published Rev. 3, but it is not adopted for contracts. In Rev. 3 this requirement is reworded: 03.01.01 Account Management. It gains organization-defined parameters.

See the Rev. 2 and Rev. 3 wording word by word, or start with the status page.

Where this page's facts come from
Requirement text
bedrock-cmmc-api@89b8e8e:migrations/004_reference_requirements.sql#Requirement.basicRequirement@rev2
Discussion
bedrock-cmmc-api@89b8e8e:migrations/004_reference_requirements.sql#Requirement.discussion@rev2
Practice name
bedrock-cmmc-api@89b8e8e:migrations/004_reference_requirements.sql#Requirement.title@rev2 (CMMC Assessment Guide practice name)
Objectives
bedrock-cmmc-api@89b8e8e:migrations/005_reference_objectives.sql#AssessmentObjective.description@rev2
Examine, interview, test
bedrock-cmmc-api@89b8e8e:migrations/005_reference_objectives.sql#AssessmentObjective.description@rev2 ({examineGuidance, interviewGuidance, testGuidance})
Level
bedrock-cmmc-api@89b8e8e:migrations/021_fix_level1_requirements.sql#Requirement.cmmcLevel@rev2
Weight
bedrock-cmmc-api@89b8e8e:internal/cmmc/requirement_values.go#requirementValues (DoD AM v1.2.1 / eMASS L2 template v3.8)
Rev. 3 mapping
bedrock-cmmc-api@89b8e8e:docs/reference/nist-800-171-rev3/normalized/r2_r3_transition_map.json#r2_to_r3
Plain-language title and summary
editorial/CMMC Navigator.dc.html#RAW (Foxx Cyber editorial)