Skip to content
Software development
ASD ISMISM-2037

ASD ISM 2037 Train software developers lacking cyber security skills

What it says

Software developers that lack sufficient cyber security knowledge and skills required for their projects or tasks undertake suitable training or upskilling on secure software development and programming practices.

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

What it means

In plain English

Developers without cyber security skills need training in secure software practices.

This control ensures that developers who don't know much about cyber security get the training they need to build secure software. If they don't, software could be vulnerable to cyber attacks, which can lead to data breaches and financial loss.

Why it matters

Without proper training, developers might write insecure code, potentially leading to vulnerabilities and cyber breaches in the software.

How to implement

  1. Training coordinator should identify which developers lack cyber security skills and set up a training plan for them.

    Look for courses that cover secure coding practices and common vulnerabilities.

  2. IT manager should partner with a reputable provider to deliver cyber security training to developers.

    Prioritise hands-on workshops where developers can practice secure coding.

  3. Development team leaders should hold regular review sessions where developers can discuss what they've learned and ask questions.

    Use real-world examples to make the learning more relatable.

  4. HR should incorporate cyber security skill assessments into the hiring process for developers.

    Use these assessments to determine ongoing training needs as part of professional development.

  5. IT security lead should provide developers with resources like coding standards and guides that focus on secure software development.

    Ensure these are easily accessible and updated regularly.

Keep it running

Regularly update training content to keep pace with emerging threats and involve developers in security discussions to reinforce learning.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    copies of the training schedule and curriculum: Check whether the content covers essential secure coding practices.

    Good evidence

    a well-documented calendar and detailed syllabus reflecting cyber security topics.

  2. Check 2 of 5What an auditor asks for

    Good evidence

    signed attendance sheets showing the participants' names and dates.

  3. Check 3 of 5What an auditor asks for

    Look at

    course completion certificates or credentials: Ensure developers completed the training satisfactorily.

    Good evidence

    valid certificates for all developers needing training.

  4. Check 4 of 5What an auditor asks for

    Ask for

    to review internal communications regarding training opportunities: See if these were clearly communicated.

    Good evidence

    emails or notices showing details and encouragement for attendance.

  5. Check 5 of 5What an auditor asks for

    Look at

    participant feedback or test results to evaluate training effectiveness.

    Good evidence

    records showing improvement or satisfaction ratings.

Mappings

Closest match in ISO/IEC 27001: A.6.3, Information security awareness, education and training program, which this control partially meets.

ISO 27001

ISO/IEC 27001: 2 mappings

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