ASD ISM 1387 Use jump servers for administrative activities
What it says
Administrative activities are conducted through jump servers.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishEnsure all admin tasks are done through safer, intermediary servers to enhance security.
A jump server is like an extra secure bridge that your IT team uses to safely access the main systems they need to manage. By making sure all admin tasks go through these special servers, you're adding a strong layer of protection against cyber criminals. Without this, hackers could more easily access the sensitive parts of your business systems, leading to data breaches or disruptions.
Free. Save your status, tasks and notes.
Why it matters
Without jump servers, admin credentials traverse many hosts, increasing exposure to credential theft and enabling attacker lateral movement.
How to implement
The IT team should set up dedicated jump servers.
They should be configured to only allow access from authorised personnel using strong passwords or passphrases. This could involve setting up secure connections like VPNs or specific network rules that route admin traffic through the jump server.
System administrators should conduct training sessions for all relevant staff on how to use the jump servers.
The training should include login procedures and why using these servers is essential for security. Use clear guides and practical demonstrations so everyone understands.
Managers should enforce policies requiring all administrative activities to go through the designated jump servers.
Clearly communicate this policy through company emails and include it in any relevant staff training materials. Compliance can be tracked by monitoring system logs.
IT security specialists should regularly monitor and audit the use of jump servers to ensure they are used correctly.
This includes reviewing access logs to check for any suspicious activity, and confirming that all admin traffic is correctly routed through the jump servers.
Once set up, the cyber security officer should periodically review the jump server setup against the latest Australian Cyber Security Centre (ACSC) guidelines to ensure they remain compliant with best practices.
Updates might be needed to reflect changes in the threat landscape or organisational structure.
Keep it running
Monitor jump server access logs for unauthorised use, restrict admin tools to the jump host, and enforce MFA for all privileged sessions.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
The network architecture diagram showing jump server placement: Request a diagram that illustrates where jump servers are positioned in relation to other systems.
Look at
How the traffic flows and ensure all admin channels pass through these servers.
Good evidence
Is a clear diagram showing all admin access is routed exclusively via jump servers.
- Check 2 of 5What an auditor asks for
Ask for
Access logs from the jump server: Request logs that detail who has accessed the jump server and when.
Look at
Multiple entries that correspond to legitimate admin activities.
Good evidence
Is logs that show consistent use by authorised admin staff only, without unexplained gaps or anomalies.
- Check 3 of 5What an auditor asks for
Ask for
The server configuration policy document: Request documentation that outlines the configuration and security settings of the jump servers.
Look at
The security measures implemented like firewalls and VPN settings.
Good evidence
Includes completed checklists or certificates from recent hardening assessments.
- Check 4 of 5What an auditor asks for
Ask for
Staff training records related to jump server use: Request evidence of training sessions held for admin staff on using jump servers.
Look at
Session dates, attendance lists, and training content.
Good evidence
Includes dated records showing recent and regular training sessions with all relevant staff listed as attendees.
- Check 5 of 5What an auditor asks for
Ask for
A policy document that mandates the use of jump servers for admin tasks: Request to see the official company policy document.
Look at
The scope and detail of the policy and who it applies to.
Good evidence
Is a well-documented, easily accessible policy that includes a clear requirement for all admin activities to use jump servers.
Mappings
Closest match in ASD Essential Eight: E8-RA-ML2.4, Conduct administrative activities through jump servers, which asks for the same thing.
ASD Essential Eight: 3 mappings
This control is equivalent to E8-RA-ML2.4.
ISM-1387 requires that administrative activities are conducted through jump servers. E8-RA-ML2.4 states the same requirement with effectively identical scope and intent, mandating jump servers for administrative work. Implementing either control would largely satisfy the other as both focus on routing admin actions via an intermediary to reduce exposure.
This control partially overlaps E8-RA-ML3.2.
ISM-1387 requires that administrative activities are conducted through jump servers. E8-RA-ML3.2 requires administrative tasks be performed from Secure Admin Workstations, which can be the endpoint used to access a jump server and reduces the likelihood of admin credential compromise. The candidate focuses on the security posture of the admin workstation, while ISM-1387 focuses on the network/architecture pattern of brokering admin access via a jump server.
This control supports E8-RA-ML1.5.
E8-RA-ML1.5 requires privileged users to use separate privileged and unprivileged operating environments to reduce exposure of admin activity and credentials. ISM-1387 supports this by requiring administrative activities to be conducted through jump servers, which can serve as the controlled privileged environment and reduce direct admin actions from user workstations. Jump servers are one implementation pattern, but E8-RA-ML1.5 can also be met via other dedicated admin workstations or isolated admin environments.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.