Entity

User Identity and Access Profile

The managed record of each user's digital identity — containing authentication credentials, role assignments, group memberships, application entitlements, access request history, last login timestamps, and the privilege escalation audit trail maintained by identity and access management (IAM) systems.

Last updated: February 2026Data current as of: February 2026

Why This Object Matters for AI

AI cannot detect access anomalies, enforce least-privilege principles, or automate provisioning without structured identity data; without it, 'who has access to what and should they' requires manual access reviews that take weeks and miss dormant privileged accounts.

Information Technology & Infrastructure Capacity Profile

Typical CMC levels for information technology & infrastructure in Manufacturing organizations.

Formality
L2
Capture
L2
Structure
L2
Accessibility
L2
Maintenance
L2
Integration
L2

CMC Dimension Scenarios

What each CMC level looks like specifically for User Identity and Access Profile. Baseline level is highlighted.

L0

User access is managed informally — new employees get whatever access their manager requests verbally, and nobody maintains a record of who has access to what.

None — AI has no identity or access information to reason about.

Create a basic user access register documenting which employees have accounts in which systems with their role or access level.

L1

A spreadsheet lists user accounts and system access, but it's maintained manually by IT and drifts from reality — terminated employees still appear, new access grants are missed.

Can list documented user accounts but cannot verify whether the spreadsheet reflects actual access state or identify dormant accounts.

Implement an identity management system with structured user profiles containing role assignments, group memberships, and application entitlements.

L2Current Baseline

An IAM system manages user profiles with role assignments and group memberships, but entitlements are granted on request without consistent documentation of why access was approved.

Can query IAM for current role assignments and group memberships but cannot assess whether access levels are appropriate without business justification records.

Enforce documented business justification for every access grant and maintain an audit trail linking each entitlement to an approved access request.

L3

Every user identity profile contains structured role assignments, group memberships, application entitlements, access request history with business justification, and last-login timestamps.

Can perform access reviews, detect dormant accounts, and flag entitlements that exceed documented job requirements.

Implement a validated identity schema with enforced attribute types, privilege escalation audit trails, and automated consistency checks across all systems.

L4

A validated identity schema enforces attribute types, links every entitlement to approved requests, maintains privilege escalation audit trails, and validates consistency across all connected systems.

Can detect access anomalies, enforce least-privilege by comparing entitlements to usage patterns, and automate access certification workflows.

Deploy continuous identity governance that auto-adjusts access based on role changes, behavioral analytics, and real-time risk scoring.

L5

Continuous identity governance auto-adjusts access based on role changes, behavioral analytics, and risk scoring — entitlements granted and revoked in real time as job functions evolve.

Can autonomously manage identity lifecycle — provisioning, adjusting, and deprovisioning access in real time based on behavioral and organizational signals.

Ceiling of the CMC framework for this dimension.

Capabilities That Depend on User Identity and Access Profile

Other Objects in Information Technology & Infrastructure

Related business objects in the same function area.

IT Asset Inventory

Entity

The comprehensive registry of all IT assets — servers, workstations, network devices, cloud instances, and installed software including hardware specifications, operating system versions, patch levels, warranty status, assigned owner, and the relationships between assets that form the configuration management database (CMDB).

IT Service Ticket

Entity

The transactional record for each IT incident or service request — containing the reported issue, affected system, priority, category, assigned technician, resolution steps taken, time to resolution, root cause code, and user satisfaction rating tracked through the ITSM lifecycle.

Network and Infrastructure Topology

Entity

The structured map of how IT systems interconnect — defining network segments, VLANs, firewall zones, cloud VPCs, load balancer configurations, DNS records, and the dependency chains that show which applications rely on which infrastructure components.

Software License Portfolio

Entity

The managed inventory of software entitlements — containing license types (perpetual, subscription, usage-based), quantities purchased, quantities deployed, renewal dates, cost per license, vendor contract references, and the compliance position showing over- or under-deployment per product.

Security Threat Intelligence

Entity

The curated collection of known threat indicators, attack patterns, and vulnerability data — containing indicators of compromise (IOCs), Common Vulnerabilities and Exposures (CVEs), threat actor profiles, attack technique mappings (MITRE ATT&CK), and the risk scores that contextualize threats to the organization's specific environment.

Patch Deployment Priority Decision

Decision

The recurring judgment point where IT operations evaluates which patches to deploy and in what order — weighing vulnerability severity (CVSS score), exploit availability, asset criticality, production impact risk, maintenance window constraints, and testing completion status.

Security Incident Response Decision

Decision

The recurring judgment point where the security team determines the appropriate response to a detected threat — evaluating threat severity, confidence level, affected systems, containment options (isolate, block, quarantine), business impact of each response action, and the escalation criteria for invoking incident response plans.

Configuration Baseline Rule

Rule

The codified standard configurations for each asset class — defining approved OS versions, required security settings, mandatory agents, network configurations, and hardening standards (CIS benchmarks, STIG) that every system must comply with, along with the exception process for justified deviations.

Access Control Policy Rule

Rule

The codified rules governing who may access which systems under what conditions — defining role-based access templates, separation-of-duties constraints, privileged access requirements (MFA, just-in-time), periodic review schedules, and the automatic deprovisioning triggers for terminated or transferred employees.

IT Incident Management Process

Process

The end-to-end workflow governing how IT incidents are detected, triaged, escalated, resolved, and reviewed — defining severity classification criteria, response time SLAs per severity, escalation paths, communication templates, post-incident review requirements, and the knowledge base update triggers that capture resolution patterns.

What Can Your Organization Deploy?

Enter your context profile or request an assessment to see which capabilities your infrastructure supports.