This month, we’re excited to announce three major enhancements to the RunSafe Security Platform that expand coverage, improve developer experience, and provide greater accuracy in SBOM generation.

Here’s what’s new in August:

• Protect: 100% VxWorks Coverage
• Identify: Reworked SBOM CLI for better developer experience
• Identify: Improved proprietary component enrichment in RunSafe-generated SBOMs

RunSafe Protect Expands Coverage for VxWorks Environments

RunSafe Protect now provides 100% coverage across the VXWorks environment, securing both kernel and application layers from the earliest point of execution. Organizations running VxWorks can now rely on RunSafe’s runtime code protection to defend embedded systems against exploitation attempts.

The expanded coverage underscores our commitment to delivering the most complete runtime protection across Linux, VxWorks, and beyond, where reliability and resilience are critical.

Learn more about RunSafe Protect.

RunSafe Identify SBOM CLI Rework Creates a Better Developer Experience

We’re rolling out a major rework of the RunSafe Identify SBOM CLI designed to deliver a smoother, more intuitive experience for developers.

The redesigned command structure makes it simpler to interact with the service responsible for data collection and enrichment.

For example, we’ve added new commands to interact directly with the RunSafe service, including:

• Service Start / Stop: Quickly bring the SBOM service up or down without manual workarounds.
• Service Status: Get a detailed view of the service state with more verbose logging, helping to diagnose issues faster.

The update is particularly beneficial for Windows users, where installation and service management previously required multiple steps. Customers can monitor and control SBOM services more easily, identify errors, and access richer logs, leading to a faster and more reliable development workflow.

Enrich SBOMs with Proprietary Components with RunSafe’s Improved Config File

We’ve expanded the flexibility of RunSafe’s SBOM configuration file to make it easier than ever to accurately represent your proprietary components in every SBOM you generate.

While our tooling automatically detects proprietary dependencies, companies often have greater clarity into their unique components, including licensing, authorship, or supplier information. The updated config file addresses this by allowing you to:

• Define proprietary components once: Create a single configuration file with details of your custom libraries or binaries.
• Enrich SBOMs automatically: Add critical data such as license, supplier, version, CPEs, or PURLs, and have it included in every SBOM moving forward.
• Reuse across builds: Pass the same config file into your build pipeline and reuse it across builds without extra manual effort.

The config file gives your team full control over how proprietary components are represented, while keeping SBOM generation accurate, repeatable, and efficient. 

By combining automation with configurable enrichment, you get the best of both worlds: streamlined detection for open-source dependencies and precise handling of the custom components unique to your products.

Learn more about RunSafe Identify.