Skip to content
Software development
ASD ISMISM-1616

ASD ISM 1616 Implementing a vulnerability disclosure program

What it says

A vulnerability disclosure program is implemented to assist with the secure development and maintenance of products and services.

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

In plain English

Have a working vulnerability disclosure program that takes reports of vulnerabilities in the organisation's products and services and feeds them into secure development and maintenance.

A vulnerability disclosure program must be implemented to help develop and maintain the organisation's products and services securely. The program is how staff, customers, security researchers and others report vulnerabilities, and how each report is checked, fixed and disclosed. The ISM applies this control to software development, so products here are software. Implemented means working, not just written down, so reports arrive, someone handles them and valid ones lead to fixes in development and maintenance. Related controls require its policy (ISM-1755), processes and procedures (ISM-1756) and security.txt files (ISM-1717).

Why it matters

Customers, researchers and staff can find vulnerabilities the developers missed, but without a clear way to report them, they may give up or publish details before a fix exists. A working program turns their reports into fixes, and into advice consumers can act on.

How to implement

  1. List the products and services the program covers.

    Include software you build or ship, websites, mobile apps, APIs and online services, including any a provider hosts for you. For hosted services, agree with the provider how reports about its platform are passed on.

  2. Set up a monitored reporting channel.

    Use a dedicated security email address or web form that reaches a named team, not one person's inbox, and sends an automatic acknowledgement. Publish it in the disclosure policy (ISM-1755) and in security.txt (ISM-1717).

  3. Connect reports to development and maintenance.

    Log each report in the issue tracker (ISM-2025), and pass valid ones to the team that fixes the product. Resolve them in a timely manner (ISM-1754), analyse root causes (ISM-1909) and disclose them as ISM-1908 requires. For a supplier's product, agree how reports reach them and how you track the fix.

  4. Send a test report through the public channel.

    Before launch and after any change to the channel, send a realistic test report and check it is acknowledged, logged and routed to the right team. Fix any step where it stalls.

Keep it running

Add each new product, service or website domain to the program when it launches, and remove retired ones. A change of team, contact address or supplier, or a report that went unanswered, should trigger a test of the reporting channel.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    The products and services the program covers, and an independent list of the software, websites and online services the organisation develops, maintains or offers, such as the application register and DNS records.

    Look at

    Whether any product or service on the independent list is outside the program.

    Good evidence

    Every product and service on the independent list is covered by the program, including those a provider hosts.

  2. Check 2 of 3What an auditor asks for

    Ask for

    A test report sent unannounced through the published reporting channel.

    Look at

    Whether it is acknowledged, logged and passed to the team responsible for that product, and how long each step takes.

    Good evidence

    The test report is acknowledged, logged and reaches the responsible development or maintenance team within the times the disclosure policy states.

  3. Check 3 of 3What an auditor asks for

    Ask for

    The reporting channel's inbox or form log for the period, compared with the issue tracker.

    Look at

    Whether every vulnerability report received was logged, and whether valid ones led to work in development or maintenance.

    Good evidence

    Every vulnerability report in the inbox or form log appears in the issue tracker, and each valid one is linked to a released fix or an open issue in development or maintenance.

Mappings

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

ISO 27001

ISO/IEC 27001: 2 mappings

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