ASD ISM 1247 Disable or remove unneeded server features
What it says
Unneeded user accounts, components, services and functionality of server applications are disabled or removed.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishRemove unnecessary accounts and features from servers to enhance security.
This control is about making sure you only keep what you really need on your servers. If servers have unnecessary accounts and features, they can be weak spots for hackers to exploit, which could lead to data breaches or service disruptions. It's like only keeping the doors and windows you use open and securely locked, while closing ones you don't need to stop burglars from getting in.
Free. Save your status, tasks and notes.
Why it matters
Excess server features expand the attack surface; unnecessary services/components can be exploited to gain unauthorised access, leading to compromise or data breach.
How to implement
System owners should take an inventory of all user accounts on each server to identify which ones are unnecessary.
This can be done by reviewing account lists and comparing them against current staff and service needs; any accounts not in use should be flagged for removal.
The IT team should review all installed server components and services to identify any that are not required for daily operations.
This involves checking each server's configuration and disabling or uninstalling anything unnecessary to reduce potential entry points for attackers.
Managers should ensure that there is a regular schedule for reviewing server configurations to add or remove features as business needs change.
This means setting a recurring calendar event every few months to reassess server requirements and adjust configurations accordingly.
IT teams should establish a protocol for immediately disabling unused accounts and features when employees leave or services are discontinued.
This can include checklists for account closure and service deactivation as part of the employee exit or service shutdown process.
Procurement teams should be tasked with ensuring that new server systems or software purchases are only for features that are necessary.
This involves careful review of user needs and liaising with IT specialists to avoid acquiring products with extra, potentially vulnerable, features.
Keep it running
Maintain a hardened baseline: regularly review installed server roles/features, disable or remove anything not required, and verify services/accounts are not left enabled by default.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
A list of all server user accounts: The list should include information on the role associated with each account and when it was last used.
Look at
Whether any accounts are redundant or have not been accessed in a significant period.
Good evidence
Shows regular updates and justification for all active accounts.
- Check 2 of 5What an auditor asks for
Look at
A clear record of decisions on which components are necessary and which have been removed. Good documentation outlines reasons for keeping each component and details of any recent removals.
- Check 3 of 5What an auditor asks for
Ask for
A record of recent configuration review meetings: These documents should show who attended, what was reviewed, and what changes were agreed upon.
Look at
Minutes showing comprehensive discussion about server needs and security implications.
Good evidence
Record shows regular and robust review processes.
- Check 4 of 5What an auditor asks for
Ask for
Procedures on disabling accounts and services: This should include checklists or guidelines used when an employee exits or when a service is retired.
Look at
Thorough procedures that ensure quick removal of access. Procedures should reflect best practices and show ample evidence of recent activity.
- Check 5 of 5What an auditor asks for
Look at
Evidence that all purchases align with operational needs and security requirements.
Good evidence
Includes evaluation reports and notes on the necessity of each feature purchased.
Mappings
Closest match in ASD Essential Eight: E8-AH-ML3.2, Ensure Windows PowerShell 2.0 is disabled or removed, which this control covers in full and more.
ASD Essential Eight: 2 mappings
This control is broader than E8-AH-ML3.2.
E8-AH-ML3.2 requires organisations to disable or remove Windows PowerShell 2.0. ISM-1247 focuses on disabling or removing unneeded server features, including components, services and functionality of server applications. Where PowerShell 2.0 is present as an enabled legacy feature on servers, E8-AH-ML3.2 acts as a specific hardening action that fits within ISM-1247's broader requirement.
This control partially overlaps E8-PA-ML1.9.
ISM-1247 requires unneeded user accounts, components, services and functionality of server applications to be disabled or removed. E8-PA-ML1.9 relates by removing no-longer-supported applications, which often reduces unnecessary functionality and attack surface on servers and endpoints. However, E8-PA-ML1.9 focuses on vendor support status and specific software categories, while ISM-1247 focuses on disabling/removing unneeded features regardless of support status.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




