Answer yes if your organisation has processes or tools in place to regularly monitor software components for newly disclosed vulnerabilities throughout the software lifecycle. This includes identifying relevant vulnerabilities, understanding the potential impact to you, and assessing any necessary actions.
Regular vulnerability scanning is a security best practice that helps organisations maintain an awareness of newly disclosed vulnerabilities and assess whether they are relevant to any software developed by the organisation. By continuously identifying known vulnerabilities across all software components, organisations can prioritise and deploy patches or other mitigations in a timely manner. This decreases the window of opportunity for a malicious actor to exploit the vulnerability, and trigger a supply chain incident.
Your policies and processes around your software development life cycle (SDLC) should include a requirement for continuous monitoring of vulnerabilities throughout the lifespan of the application. This monitoring should be fed by up to date feeds from global vulnerability databases such as the Common Vulnerabilities and Exposures (CVE) and the National Vulnerability Database (NVD) to ensure that newly disclosed vulnerabilities are checked against your applications.
There are numerous consultancies or individual consultants that will be able to assist in crafting a policy and implementing an SDLC that includes continuous vulnerability scanning in a way that meets your business and technical requirements.
If you would like to contribute to this article or provide feedback, please email knowledge@riskledger.com. Contributors will be recognised on our contributors page.