STIGViewer Support

164.312(a)(2)(i)

paragraph (action item)

Unique user identification (Required). Assign a unique name and/or number for identifying and tracking user identity.

164.312 Technical safeguards.

Related Frameworks

2 mappings across 5 frameworks
SCF2 mappings
IAC-02Identification & Authentication for Organizational Users
1.00
IAC-09Identifier Management (User Names)
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (71) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-1Policy and Procedures
1.00
AC-10Concurrent Session Control
1.00
AC-12Session Termination
1.00
AC-14Permitted Actions Without Identification or Authentication
1.00
AC-16Security and Privacy Attributes
1.00
AC-17Remote Access
1.00
AC-18Wireless Access
1.00
AC-19Access Control for Mobile Devices
1.00
AC-2Account Management
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00

+61 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (13) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.1.1
1.00
3.1.11
1.00
3.1.16
1.00
3.1.18
1.00
3.1.2
1.00
3.1.4
1.00
3.1.5
1.00
3.1.8
1.00
3.5.1
1.00
3.5.11
1.00

+3 more (top 10 by confidence shown)

CCI0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (100) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

+90 more (top 10 by confidence shown)

STIG0 mappings

No source states a mapping between these directly.

Also reachable in 4 hops (100) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

SV-104233r1_ruleSymantec ProxySG must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
1.00
SV-104235r1_ruleSymantec ProxySG must be configured with a pre-established trust relationship and mechanisms with appropriate authorities that validate user account access authorizations and privileges.
1.00
SV-104237r1_ruleSymantec ProxySG providing user authentication intermediary services must restrict user authentication traffic to specific authentication servers.
1.00
SV-205699r958482_ruleWindows Server 2019 shared user accounts must not be permitted.
1.00
SV-205700r958482_ruleWindows Server 2019 accounts must require passwords.
1.00
SV-207208r608988_ruleThe VPN Gateway must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
1.00
SV-207386r958482_ruleThe VMM must uniquely identify and must authenticate organizational users (or processes acting on behalf of organizational users).
1.00
SV-216189r958482_ruleDuplicate User IDs (UIDs) must not exist for users within the organization.
1.00
SV-216426r958482_ruleDuplicate User IDs (UIDs) must not exist for users within the organization.
1.00
SV-217163r958482_ruleThe SUSE operating system must not have duplicate User IDs (UIDs) for interactive users.
1.00

+90 more (top 10 by confidence shown)

Department of Health and Human Services, HIPAA Security and Privacy Rules (45 CFR Part 164). Edition dated 2026-01-01. Read the publication.