Skip to content
Software development
ASD ISMISM-1755

ASD ISM 1755 Develop and maintain a vulnerability disclosure policy

What it says

A vulnerability disclosure policy is developed, implemented and maintained.

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

What it means

In plain English

Organisations create and sustain a policy for reporting software vulnerabilities securely.

A vulnerability disclosure policy is like an invitation for people to let you know about weaknesses in your software in a safe and organised way. This is crucial because if these vulnerabilities are not reported and fixed, they could be exploited by malicious people, potentially leading to data breaches or system failures.

Why it matters

Without a vulnerability disclosure policy, external researchers may not report flaws, leaving vulnerabilities unaddressed and increasing likelihood of compromise or data breach.

How to implement

  1. The organisation's management team should establish a clear policy for disclosing software vulnerabilities.

    This policy should outline what information to collect, how to protect the privacy of the reporters, and who in the organisation will handle these reports. Make sure the policy is written in clear language and is easily accessible to everyone involved.

  2. The communications or IT team should set up a dedicated channel, such as a specific email address, for receiving vulnerability reports.

    This ensures that people know where to send their findings, and the organisation can track reports efficiently. Advertise this contact information on your website and any relevant documentation.

  3. Appoint a responsible team or individual within the IT department to handle incoming vulnerability reports.

    This person or team should review each report, assess its validity, and coordinate any required response or remediation within the organisation. Regularly train this team on best practices for handling sensitive information.

  4. The IT team should work on a step-by-step process for verifying and resolving reported vulnerabilities.

    This process might include verifying the existence of a vulnerability, evaluating its impact, and prioritising fixes accordingly. Document each step to ensure consistent handling of each report.

  5. The management team should communicate policy updates and changes with all staff involved periodically.

    Hosting regular training sessions around this policy helps ensure everyone understands their role and responsibilities. This keeps the team ready and informed when vulnerabilities are reported.

Keep it running

Publish a clear disclosure policy with reporting channels, triage/response timeframes and safe-harbour; review and update it regularly as systems and contacts change.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The official vulnerability disclosure policy document: Check if it clearly explains the process of vulnerability reporting and management.

    Look at

    Detailed procedures and contact information.

    Good evidence

    A document that is dated, includes an official version number, and has been reviewed and approved by management.

  2. Check 2 of 5What an auditor asks for

    Ask for

    Records of communication channels: Request evidence of how the dedicated vulnerability report channels are publicised.

    Look at

    Relevant website pages or official communiqués.

    Good evidence

    Shows clear and consistent communication of contact information in a public and easy-to-find manner.

  3. Check 3 of 5What an auditor asks for

    Ask for

    A list of vulnerability reports received: Inspect the list for details such as dates, vulnerability descriptions, and actions taken. Good means seeing recent entries that show active report handling with response timelines and status updates.

  4. Check 4 of 5What an auditor asks for

    Ask for

    To see the documented process for verifying and resolving vulnerabilities.

    Look at

    Step-by-step procedures and responsible persons or teams. Good means seeing a consistently followed, documented process with roles clearly defined and actions traceable.

  5. Check 5 of 5What an auditor asks for

    Ask for

    About recent training sessions on the vulnerability disclosure policy.

    Look at

    Training materials and attendance records. Good is evidenced by regular, documented training sessions with participant lists and feedback forms, indicating staff are up-to-date with the policy.

Mappings

Closest match in ISO/IEC 27001: A.8.8, Management of technical vulnerabilities, which this control partially meets.

ISO 27001

ISO/IEC 27001: 1 mapping

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