Skip to content
System access
ASD ISMISM-0434

ASD ISM 0434 Ensure personnel employment screening and security clearance

What it says

Personnel undergo appropriate employment screening and, where necessary, hold an appropriate security clearance before being granted access to systems and their resources.

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

What it means

In plain English

Staff need job screening and security clearance for system access.

This control is about making sure that people who need access to important or sensitive systems go through proper background checks and, if needed, have a security clearance. This is crucial because if someone not properly vetted gets access, they could misuse sensitive information, leading to data breaches, financial losses, or harm to your organisation's reputation.

Why it matters

Without employment screening and required security clearances, unsuitable staff may gain access, increasing insider threat, data breaches and loss of trust.

How to implement

  1. HR should perform thorough background checks: Before hiring, the HR team should verify employment history, qualifications, and conduct reference checks to ensure candidates are trustworthy.

    This can be done by contacting previous employers and using professional screening services.

  2. Managers should identify roles needing security clearance: Managers must determine which positions involve access to sensitive systems and require a security clearance.

    They should list these roles and ensure candidates are informed about the need for clearance before hiring.

  3. Assign a security officer to handle clearances: A security officer should be responsible for coordinating the security clearance process for new hires.

    This involves understanding the levels of clearance required and liaising with the relevant authority to process applications.

  4. IT should manage access rights carefully: The IT team needs to ensure that system access is only granted once the required checks and clearances are complete.

    They should use an access management system to track and manage permissions.

  5. Conduct regular reviews: Management should periodically review current employees' clearances and background checks to ensure they are still valid and appropriate for their roles.

    This can be done annually or in response to changes in job functions.

Keep it running

Before granting access, verify HR screening completion and required clearance level; revalidate clearances and keep a current register mapped to roles and systems.

Evidence and audit

  1. Check 1 of 4What an auditor asks for

    Ask for

    A list of positions requiring security clearance: Request documentation that details which roles need clearance and why.

    Look at

    A clear rationale for each position and a list of positions. Good documentation will clearly define roles and associated clearance requirements.

    Good evidence

    Record includes contact details of referees and dates of checks.

  2. Check 2 of 4What an auditor asks for

    Ask for

    How employees are screened before being given system access.

    Look at

    A consistent and comprehensive explanation of steps taken.

    Good evidence

    Includes a detailed, step-by-step process of checks performed.

  3. Check 3 of 4What an auditor asks for

    Look at

    Details on how the clearances are processed and reviewed.

    Good evidence

    Document includes steps, responsible individuals, and review intervals.

  4. Check 4 of 4What an auditor asks for

    Ask for

    To see logs or records showing access was only granted after clearances.

    Look at

    Timestamps and approval signatures to ensure compliance.

    Good evidence

    Log shows a clear linkage between clearance approval and access granted date.

Mappings

Closest match in ISO/IEC 27001: A.6.1, Personnel background verification, which partially overlaps with this control.

ISO 27001

ISO/IEC 27001: 2 mappings

  • A.6.1Personnel background verificationPartially overlaps

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