RunSafe Security

@RunSafeSecurity

Protect embedded systems across critical infrastructure. Generate build-time SBOMs for C/C++, identify vulns, and defend devices at runtime.

McLean, VA

Joined September 2015

RunSafe Security
@RunSafeSecurity
17h
What do the supplier fields in a #CycloneDX #SBOM represent? ▸ metadata.supplier: the issuing org ▸ metadata.component.supplier: the vendor of the product it describes ▸ runsafe.ly/45ouH97.compon…: the tool that generated it Keep this graphic handy!
RunSafe Security
@RunSafeSecurity
Aug 20
RunSafe’s C/C++ SBOM checklist helps teams evaluate whether their SBOM is a basic inventory or a release-ready, build-attested record. Evaluate yours: runsafe.ly/4pGe4iB
RunSafe Security
@RunSafeSecurity
Aug 19
How are embedded teams using AI? Testing and validation lead at 27.5%. Code generation follows at 19%, with deployment automation close behind at 18.5%. See the full 2025 AI in Embedded Systems Report: runsafe.ly/4fAH5aG
RunSafe Security
@RunSafeSecurity
Aug 17
The #CRA deadline is approaching, and embedded teams are searching for #SBOM tools. Can the tool see static libraries, vendored code, conditional builds, and the exact components in a released artifact? Learn more:
Questions to Ask When Evaluating C/C++ SBOM Tools
From runsafesecurity.com
RunSafe Security
@RunSafeSecurity
Aug 14
CRA readiness has to work beyond the checklist. Leaders from Schneider Electric, May Mobility, GE Healthcare, and RunSafe share practical lessons on SBOMs, supplier risk, secure updates, and long-term product support. Watch now: runsafe.ly/3TRE1Qk