Skip to content
System access
ASD ISMISM-2078

ASD ISM 2078 Ensure passwords are not common or compromised

What it says

Passwords appearing in lists of commonly used passwords or lists of compromised passwords are not used.

Quoted as published. Everything else on this page is written by Control Stack.

What it means

In plain English

Make sure passwords aren't from known compromised or common password lists to enhance security.

When we talk about ensuring passwords aren't from known compromised or common lists, it's like making sure you aren't using the same old rusty key everyone else has. If you use a weak or already stolen password, it's much easier for someone to break in and steal your information or mess with your systems.

Why it matters

Using common or compromised passwords invites unauthorised access, increasing the risk of data breaches and reputational damage.

How to implement

  1. IT team should implement password management tools: Use software that checks if passwords are on lists of known compromised or commonly used passwords.

    This involves integrating with online services that maintain these lists, to automatically flag or prevent unsafe passwords.

  2. System administrators should set up password policies: Develop and enforce rules that require employees to create complex passwords.

    This can be done through settings in your systems that demand a mix of letters, numbers, and special characters.

  3. HR should educate staff on password importance: Organise regular training sessions to explain why secure passwords matter and how to create them.

    Use examples of breaches caused by weak passwords to make it relatable.

  4. IT support should perform regular audits of user passwords: Conduct checks to ensure passwords haven't been compromised by using tools that compare them to known databases of breached passwords.

    Schedule audits at regular intervals and report findings.

  5. Management should ensure usage of multi-factor authentication: Require all staff to not only use passwords but also verify their identity through another method, such as a code sent to their phone.

    This adds an extra layer of security even if a password gets compromised.

Keep it running

Block passwords found in common/compromised lists by checking proposed passwords against breach datasets (e.g. Have I Been Pwned) and refresh the lists routinely.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The password policy document: Check that it describes requirements against using common or compromised passwords.

    Good evidence

    Includes explicit statements about checking passwords against known breach lists and updating these lists regularly.

  2. Check 2 of 5What an auditor asks for

    Ask for

    To see reports from password audit tools.

    Look at

    How frequently these audits are performed and what the results are.

    Good evidence

    Includes dated records showing audits performed regularly with documented follow-ups on any issues found.

  3. Check 3 of 5What an auditor asks for

    Good evidence

    Shows recent training dates and attendee lists, indicating regular educational efforts.

  4. Check 4 of 5What an auditor asks for

    Ask for

    Logs showing attempted password changes: Check if the system is automatically flagging or blocking weak passwords.

    Good evidence

    Provides logs where attempts to use weak or compromised passwords are promptly rejected.

  5. Check 5 of 5What an auditor asks for

    Good evidence

    Demonstrates integration with existing login systems and shows records of successful multifactor verification.

Mappings

Closest match in ISO/IEC 27001: A.5.17, Management of authentication information, which partially overlaps with this control.

ISO 27001

ISO/IEC 27001: 1 mapping

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.