Skip to main content
MuonPartners
Services
Architecture

Solution design and technology roadmapping

Solution AssessmentTechnology RoadmapsIntegration DesignSolution ArchitectureTechnical Design
Cyber Security

Security assessments, IAM, and compliance

AssessmentsIAMComplianceSecurity BaselineCyber Innovation
Network and Platform

Network architecture and cloud platforms

Network DesignCloud StrategyModernisation
Enterprise Architecture

Business-technology alignment

Business AlignmentPortfolio AnalysisGovernance
View all services
ProjectsCase StudiesInsightsToolsAbout
Contact Us

Services

Architecture
Solution AssessmentTechnology RoadmapsIntegration DesignSolution ArchitectureTechnical Design
Cyber Security
AssessmentsIAMComplianceSecurity BaselineCyber Innovation
Network and Platform
Network DesignCloud StrategyModernisation
Enterprise Architecture
Business AlignmentPortfolio AnalysisGovernance
ProjectsCase StudiesInsightsToolsAboutContact
Get in Touch
MuonPartners

Strategic technology consulting for Australian organisations navigating complexity.

Services

  • Architecture
  • Cyber Security
  • Network and Platform
  • Enterprise Architecture

Company

  • About
  • Products
  • Frameworks
  • Cross-Framework Mapping
  • Projects
  • Case Studies
  • Insights
  • Contact

Contact

  • [email protected]
  • Australia
  • LinkedIn

© 2026 Muon Partners. All rights reserved.

ABN 50 669 022 315 · A Muon Group company.

Privacy PolicyTerms of Service
  1. Frameworks
  2. >C2M2
  3. >Identity And Access Management
  4. >Identity And Access Management - Objective 2
  5. >C2M2-ACCESS-2G
C2M2-ACCESS-2GActive

Logical access privileges that pose higher risk to the function receive additional scrutiny and monitoring

Statement

Logical access privileges that pose higher risk to the function receive additional scrutiny and monitoring

Location

Domain
Identity and Access Management
Objective
Identity and Access Management - Objective 2

Practice Details

Identifier
C2M2-ACCESS-2G
Domain
Identity and Access Management
Objective
Objective 2
Maturity Level
MIL-2

Help Text

Privileged access, service accounts, shared accounts, and remote access should be subject to stricter control than routine user access. Additional scrutiny might require that access requests are approved by more than one person or an individual with a higher level of authority than standard user access requests. Additional monitoring might entail logging the use of elevated privileges. As an example, in a mature organization, privileged access to shared accounts may be implemented through provisioned credentials that are valid only for the time needed to perform an approved change. Additionally, staff may be monitored through closed-circuit television and screen captures while those credentials are in use. These are specific examples of access that may pose higher risk to the function: · privileged accounts · service accounts · shared accounts · remote access · administrative accounts · emergency access · access to sensitive assets · access to cloud or virtual asset management systems · cryptographic key management accounts · backup accounts Additionally, it is important to note that the word risk is being used in this practice in the general sense of the word and not intended to refer to any specific risks identified in the Risk Management domain of the C2M2. However, organizations should consider access to IT and OT assets and the sufficiency of controls to manage access as potential sources of risk that should be considered in the risk identification, analysis and response activities discussed in the Risk Management domain.

Related Practices · Input From: Implementing ARCHITECTURE-3a provides input that may be useful for implementing this practice. · Progression: This practice is part of a practice progression. Practice progressions are groups of related practices that represent increasingly complete or more advanced implementations of an activity. The practices in this progression include: ACCESS-2b, ACCESS-2g, ACCESS-2h.

AESCSF
AESCSF-ACCESS-2gequivalentvia derived-shared-practice-structure
View in graphReport an issue
← Back to Identity and Access Management - Objective 2
Identity and Access Management - Objective 29 controls
C2M2-ACCESS-2ALogical access controls are implemented, at least in an ad hoc mannerC2M2-ACCESS-2BLogical access privileges are revoked when no longer needed, at least in an ad hoc mannerC2M2-ACCESS-2CLogical access requirements are established and maintained (for example, rules for which types of entities are allowed to access an asset, limits of allowed access, constraints on remote access, authentication parameters)C2M2-ACCESS-2DLogical access requirements incorporate the principle of least privilegeC2M2-ACCESS-2ELogical access requirements incorporate the principle of separation of dutiesC2M2-ACCESS-2FLogical access requests are reviewed and approved by the asset ownerC2M2-ACCESS-2GLogical access privileges that pose higher risk to the function receive additional scrutiny and monitoringC2M2-ACCESS-2HLogical access privileges are reviewed and updated to ensure conformance with access requirements periodically and according to defined triggers, such as changes to organizational structure, and after any temporary elevation of privilegesC2M2-ACCESS-2IAnomalous logical access attempts are monitored as indicators of cybersecurity events