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. >AESCSF
  3. >ACCESS
  4. >Control Logical Access
  5. >AESCSF-ACCESS-2i
AESCSF-ACCESS-2iActive

Anomalous logical access attempts are monitored as indicators of cybersecurity events

Statement

Anomalous logical access attempts are monitored as indicators of cybersecurity events

Context and Guidance: Monitoring is done on logical access attempts, and any anomalies detected (such as an attempted login with a user name that doesn’t exist within the system) are tagged as requiring further review to determine whether they are indicators of cybersecurity events (rather than user error, for example).

Related Practices • Input From: Implementing ARCHITECTURE-3a provides input that may be useful for implementing this practice.

Location

Domain
ACCESS
Objective
Control Logical Access

Practice Details

Identifier
AESCSF-ACCESS-2i
Type
Practice
Domain
ACCESS
Objective
Control Logical Access

Maturity Level

MIL-1MIL-2MIL-3

Security Profile

SP-1SP-2SP-3
ISM
ISM-1714relatedvia aescsf-reference
ISM-1651relatedvia aescsf-reference
ISM-1652relatedvia aescsf-reference
ISM-1715relatedvia aescsf-reference
C2M2
C2M2-ACCESS-2Iequivalentvia derived-shared-practice-structure
View in graphReport an issue
← Back to Control Logical Access
Control Logical Access9 controls
AESCSF-ACCESS-2aLogical access controls are implemented, at least in an ad hoc mannerAESCSF-ACCESS-2bLogical access privileges are revoked when no longer needed, at least in an ad hoc mannerAESCSF-ACCESS-2cLogical access requirements are established and maintained (for example, rules for which types of entities are allowe...AESCSF-ACCESS-2dLogical access requirements incorporate the principle of least privilegeAESCSF-ACCESS-2eLogical access requirements incorporate the principle of separation of dutiesAESCSF-ACCESS-2fLogical access requests are reviewed and approved by the asset ownerAESCSF-ACCESS-2gLogical access privileges that pose higher risk to the function receive additional scrutiny and monitoringAESCSF-ACCESS-2hLogical access privileges are reviewed and updated to ensure conformance with access requirements periodically and ac...AESCSF-ACCESS-2iAnomalous logical access attempts are monitored as indicators of cybersecurity events