“Our reports say your software is not secure and has critical and high vulnerabilities. Our delivery pipeline is not working. We can’t upgrade applications in production environments!”. You see Slack messages and Salesforce escalation tickets. It doesn’t look good.
You know that no application, Docker image, virtual machine or operating system is free of issues. Flaws are sooner or later exploited, classified as security vulnerabilities, and added to the CVE database. This is the reality.
In December 2024, the Go team announced two security bugs and assigned two CVEs to the golang.org/x/net and golang.org/x/crypto packages.
If you work on large Go projects, you must apply security patches, as both packages are likely imported as direct or indirect dependencies.
The process starts in your mind, attitude, and awareness of cybersecurity. You build your knowledge about secure programming practices and study daily Common Software Weaknesses examples and ways to bullet-proof your software products.