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. >Establish Identities And Manage Authentication
  5. >AESCSF-ACCESS-1j
AESCSF-ACCESS-1jActive

Identities are disabled after a defined period of inactivity, where feasible

Statement

Identities are disabled after a defined period of inactivity, where feasible

Context and Guidance: Enforcement of identity deprovisioning based on periods of inactivity can reduce the risk of a dormant account being misused or subject to malicious activity. The period of inactivity must be established by the organisation commensurate with potential risk. For example, temporary identities supplied to contractors might be appropriately disabled after a period of 30 days or less. An organisation may implement this control by first monitoring last logon timestamp or other attributes to identify potential periods of inactivity. Using this information, identities that have been inactive for a defined period of time can be identified and disabled or removed if no longer needed. The efficiency of this activity may be improved by developing a list of accounts that by nature have long periods of dormancy but are also still necessary to meet operational requirements. While this practice may be enforced by automated means, it is important to carefully consider the impacts to operations prior to implementing automated deprovisioning.

Related Practices • 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-1a, ACCESS-1c, ACCESS-1e, ACCESS-1f, ACCESS-1j.

Location

Domain
ACCESS
Objective
Establish Identities and Manage Authentication

Practice Details

Identifier
AESCSF-ACCESS-1j
Type
Practice
Domain
ACCESS
Objective
Establish Identities and Manage Authentication

Maturity Level

MIL-1MIL-2MIL-3

Security Profile

SP-1SP-2SP-3
ISM
ISM-0430relatedvia aescsf-reference
ISM-1591relatedvia aescsf-reference
ISM-1404relatedvia aescsf-reference
ISM-1648relatedvia aescsf-reference
ISM-1716relatedvia aescsf-reference
View in graphReport an issue
← Back to Establish Identities and Manage Authentication
Establish Identities and Manage Authentication10 controls
AESCSF-ACCESS-1aIdentities are provisioned, at least in an ad hoc manner, for personnel and other entities such as services and devic...AESCSF-ACCESS-1bCredentials (such as passwords, smartcards, certificates, and keys) are issued for personnel and other entities that ...AESCSF-ACCESS-1cIdentities are deprovisioned, at least in an ad hoc manner, when no longer requiredAESCSF-ACCESS-1dPassword strength and reuse restrictions are defined and enforcedAESCSF-ACCESS-1eIdentity repositories are reviewed and updated periodically and according to defined triggers, such as system changes...AESCSF-ACCESS-1fIdentities are deprovisioned within organisation-defined time thresholds when no longer requiredAESCSF-ACCESS-1gThe use of privileged credentials is limited to processes for which they are requiredAESCSF-ACCESS-1hStronger credentials, multifactor authentication, or single use credentials are required for higher risk access (such...AESCSF-ACCESS-1iMultifactor authentication is required for all access, where feasibleAESCSF-ACCESS-1jIdentities are disabled after a defined period of inactivity, where feasible