Guidance
Machine learning principles
These principles help developers, engineers, decision makers and risk owners make informed decisions about the design, development, deployment and operation of their machine learning (ML) systems.
Our advice & guidance covers a broad range of topics
Resources for individuals and organisations in the UK who have experienced an online scam or cyber attack.
Find a range of products & services from NCSC and certified 3rd party suppliers
Working with industry, government and academia to support the next generation of researchers, students and cyber security professionals
All the latest information to help you keep track of what's happening
Page 18 of 22
You have a process in place for securely sharing information about incidents with the appropriate authorities.
Following security considerations, you participate in information-sharing communities, collaborating with industry, academia and governments to share best practice.
You have mechanisms in place so that anyone discovering a vulnerability in your model is able to report it back to you.
You provide consent to security researchers to publish and report vulnerabilities.
Like any other software, ML systems will contain vulnerabilities, and having proper vulnerability management processes will help address the risks associated with using them. The fast-developing nature of ML, and the increasing integration of ML components into critical systems, mean that sharing knowledge about vulnerabilities and incidents is particularly important.
Your ability to receive information from users about possible vulnerabilities in your own ML products will allow you to address security issues. In some sectors this may also help you comply with requirements or legislation linked to secure data handling.
Vulnerabilities are discovered all the time, and security specialists want to be able to report them directly to the organisation responsible. These reports can provide you with valuable information that you can use to improve the security of your systems.
By providing a clear process, organisations can receive the information directly so the vulnerability can be addressed, and the risk of compromise reduced. This process also reduces the reputational damage of public disclosure by providing a way to report, and a defined policy of how the organisation will respond. The NCSC's Vulnerability Disclosure Toolkit contains the main components required to set up your own vulnerability disclosure process.
The NIST Guide to Threat Information Sharing provides guidance on establishing and participating in cyber threat information sharing relationships. Identify and share your knowledge at appropriate forums such as industry specific conferences, blogs and journals.
Note that a real-life adversarial attack can be used to create a case study through MITRE ATLAS - Contribute. Principle 1.3 discusses benefits and risks of publishing specific detail about your systems. Nevertheless, there are likely to be various ways to share enough information to support others in developing secure ML, even if key sensitivities are removed.
Follow the NCSC's advice for reporting and managing incidents and if appropriate report the incident to the NCSC. Where possible, share details about the incident to help build knowledge across the ML development community. One way to do this would be to create a case study in MITRE ATLAS, as discussed above.


