Memory Safety after Salt Typhoon

Bronto-WatchingTwisterA brontosaurus watching a twister over the desert. [Generated by Google Gemini]

Most folks have heard about the massive Salt Typhoon Cyberattack that compromised at least 8 telecoms, but this is just the tip of the proverbial iceberg.  In the past, companies could afford a reactive stance to cybersecurity, but those days have ended.  Forward looking “memory safety strategies” are considered fundamental practices on par with following CVE procedures and updating dependencies to avoid known vulnerabilities.

Google is leading the charge here, creating a sophisticated memory safety strategy and publicly reporting about its progress.  But all critical infrastructure is under the microscope.  After the Salt Typhoon attacks, telecoms will be required to “Create, update, and implement cybersecurity risk management plans”.  Plans that must include a memory safety strategy.  As cybersecurity threads continue to expand, so too will the requirements for and importance of having a forward looking strategy across all industries.

Fortunately, BrontoSource can help your company develop and deploy a memory safety strategy.  Our tools can automate the migration from memory unsafe languages, update your third-party dependencies, and turn your legacy code from a compliance and security risk to a first mover advantage.