RunSafe Security Inc.

Are your products secure enough to avoid CISA’s “bad practices” pitfalls? Joe Saunders, Founder & CEO of RunSafe Security, explains how outdated software, default passwords, and unprotected memory can jeopardize critical systems. Rather than avoiding C and C++, he shares how RunSafe empowers manufacturers to secure their code and build resilience. Watch the video for more insights: https://runsafe.ly/3B2PjrW #ProductManufacturers #Cybersecurity

Nation-state actors are using generative AI to engage in digital warfare, but can AI also be used to defend critical infrastructure? RunSafe Security CEO and Founder Joe Saunders weighs in alongside industry experts in Techstrong.ai. Read here: https://runsafe.ly/3ZgnKF0

Transportation systems are highly interconnected. A successful cyber attack on one supplier can cause major disruptions with implications around the globe. Legacy OT infrastructure puts these systems at risk of ransomware, memory safety vulnerabilities, and other forms of attack. By leveraging SBOMs to identify vulnerabilities and advanced memory relocation techniques, it's possible to secure transportation systems from both known and unknown vulnerabilities, building resilience and keeping economies and commerce running.

What does a Volt Typhoon cyber kill chain look like? Dave Salwen, VP of Embedded Systems at RunSafe Security, takes a look at the typical pattern of attack involving Volt Typhoon and what can be done today to prevent the group's future success. Read more here: https://runsafe.ly/3V4M8a3 #cybersecurity #nationstatethreat #volttyphoon #criticalinfrastructure

Malicious actors exploit memory safety vulnerabilities to execute arbitrary code, compromise sensitive data, and cause system crashes. When we think about these attacks in the context of the energy grid, defense systems, and transportation, it’s clear that it’s time to address the memory safety crisis once and for all. Learn more in our guide: "Safeguarding Code: A Comprehensive Guide to Addressing the Memory Safety Crisis" https://runsafe.ly/3V37SmH #memorysafety #softwaresecurity

November is Critical Infrastructure Security and Resilience Month and we have one question for you: How are you addressing memory safety in legacy systems? Scanning, patching, and rewriting code are options, but in long-standing critical systems, traditional scanning and patching methods often fall short and code rewrites could take decades. We need to protect critical infrastructure today, and that is what RunSafe is here to do! Our solution enables you to achieve memory safety without requiring code rewrites, no matter how old your systems are. Eliminating memory-based vulnerabilities means more resilient critical infrastructure. Let's continue working toward that day together. #BeResilient

Memory safety vulnerabilities in C/C++ often go undetected by scanning tools—why is that? In this week’s RunSafe Security Minute, Salim explains the challenges of detecting subtle memory safety bugs in C/C++ and shares how to improve software security: ? Use SBOMs to monitor vulnerabilities ? Harden your C/C++ software to guard against unknown threats Watch now to strengthen your defenses: https://runsafe.ly/3CrldPc

Catch RunSafe Founder & CEO Joe Saunders on the Claroty Nexus Podcast! Thank you to Michael Mimoso for hosting the conversation. Critical infrastructure needs protection. RunSafe is here to do so, helping to keep the world a safer place.

Who says you have to rewrite the book to secure your systems? Reducing your attack surface without rewriting existing code is a revolutionary approach in cybersecurity. With advanced security solutions that seamlessly integrate with your current systems, you can shield against vulnerabilities while maintaining your development momentum. This approach not only boosts security but also lets your developers focus on what they do best. So, why not secure your systems efficiently and keep the productivity flowing? Let's chat to discuss how we can simplify and enhance your cybersecurity strategy. [https://runsafe.ly/3UT34Am] #CyberSecurity #CyberResilience #SecureByDesign

One of the first major cyber incidents, the infamous Morris Worm of 1988, started with a memory safety vulnerability. Over 30 years later, we are still dealing with memory safety vulnerabilities in the present day. Why does this problem persist and what can be done to safeguard the code behind our critical infrastructure? With the right strategies and automated tools, software developers, product managers, and security professionals can tackle the memory safety crisis once and for all. We dig into how and why in our latest RunSafe Security guide: https://runsafe.ly/3UQ8Sux