ASD ISM 2071 Training on managing social engineering threats
What it says
Personnel dealing with user account details are advised of what social engineering attacks are, how to manage such situations and how to report them.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishStaff handling user accounts learn to identify and handle social engineering threats.
This control is about teaching the people who manage user accounts how to recognise and deal with social engineering threats, like phishing emails or fake phone calls. It's important because if these threats aren't managed correctly, bad actors could trick someone into giving away confidential information, potentially leading to data breaches or financial loss.
Free. Save your status, tasks and notes.
Why it matters
Without training on social engineering, staff handling account details may be tricked by phishing or impersonation, leading to credential compromise and unauthorised access to sensitive information.
How to implement
Managers should organise regular training sessions for staff who handle user accounts.
These sessions should cover examples of social engineering attacks, such as phishing emails or deceptive phone calls, and provide strategies to recognise and avoid them. Use role-playing scenarios and real-life examples to make the training engaging and memorable.
HR should update onboarding processes to include social engineering awareness.
Introduce new hires to basic concepts of social engineering during their first week, ensuring they know how to report any suspicious encounters or requests. Provide a user-friendly guide they can refer back to as needed.
The IT team should develop a simple guide on identifying social engineering threats, tailored to the organisation's specific risks.
This guide should be easily accessible on the intranet and include contact information for reporting incidents. Regularly update the guide with new tactics that attackers might be using.
Department heads should establish a clear reporting procedure for any suspected social engineering attempts.
Encourage staff to report without fear of blame. Ensure they know who to contact and how to escalate the issue if needed. Follow up on incidents to assess and improve response measures.
Communications teams should regularly remind staff about the risks of social engineering through newsletters or bulletins.
Highlight recent examples of attempted attacks and successful interventions by staff. This keeps the topic top-of-mind and encourages vigilance across the organisation.
Keep it running
Run annual training for staff handling account details; include phishing/impersonation examples and clear reporting steps. Refresh quarterly with updated scenarios and periodic mock-phishing drills.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
Training attendance records: Request lists of employees who have completed training sessions on social engineering threats.
Look at
The names, dates, and course content covered in these sessions.
Good evidence
Includes comprehensive records showing regular training for all relevant staff.
- Check 2 of 5What an auditor asks for
Ask for
The onboarding training materials: Review the content for social engineering awareness included in new employee induction.
Look at
Clear, concise information about identifying and reporting threats.
Good evidence
Shows a dedicated section on social engineering with up-to-date examples.
- Check 3 of 5What an auditor asks for
Ask for
The incident reporting procedure document: Request the official process for reporting suspected social engineering incidents.
Look at
Step-by-step instructions and contact information.
Good evidence
Includes a straightforward, easy-to-follow process that all staff can access.
- Check 4 of 5What an auditor asks for
Ask for
To see communication samples: Request copies of newsletters or bulletins that mention social engineering.
Look at
Frequency and clarity of messages about vigilance and recent incidents.
Good evidence
Shows regular, engaging communications that keep the topic front and centre.
- Check 5 of 5What an auditor asks for
Ask for
The incident response log: Request logs of any reported social engineering incidents.
Look at
Columns detailing the nature of the incident, how it was handled, and any outcomes.
Good evidence
Demonstrates prompt action and reflection to improve future responses.
Mappings
Closest match in ISO/IEC 27001: A.6.3, Information security awareness, education and training program, which this control partially meets.
ISO/IEC 27001: 2 mappings
This control partially meets A.6.3.
Annex A 6.3 requires the organisation to provide role-relevant information security awareness, education, and training with regular policy/procedure updates. ISM-2071 fits within this by requiring targeted training for personnel handling user account details on recognising, managing, and reporting social engineering attacks. ISM-2071 is topic-specific, while Annex A 6.3 is an overarching program requirement spanning many topics and roles.
This control partially overlaps A.6.8.
ISM-2071 requires personnel who deal with user account details to be trained to recognise social engineering, manage attempted manipulation, and report it. Annex A 6.8 requires the organisation to provide defined channels and mechanisms for reporting information security events and suspected weaknesses promptly. This aligns with the reporting aspect of ISM-2071, making this an overlapping relationship as Annex A 6.8 focuses on establishing reporting mechanisms, while ISM-2071 focuses on situational training.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




