We’ve made a number of updates to the RunSafe Security Platform and RunSafe Identify in July and August, adding enterprise authentication, improving the accuracy of Software Bill of Materials (SBOM) data through enrichment, expanding the SBOM formats the platform accepts, giving teams more granular control over compliance policies, and improving SBOM generation on Windows.

Here’s what’s new:

RunSafe Security Platform

• SBOM enrichment in the platform
• SPDX SBOM ingest support
• Single sign-on (SSO) support
• Project-level vulnerability and license compliance settings

RunSafe Identify

• Windows standalone (non-admin) mode
• Improved Windows path support
• More complete SBOM generation on Windows
• SBOM manufacturer and build lifecycle fields
• New --foundation flag for generating foundation reports
• exclude alias for the
  exclude-directories option
• Improved logging

SBOM Enrichment for More Accurate Vulnerability Data

RunSafe now enriches your SBOMs directly in the platform, applying improvements to existing SBOMs as new data becomes available. This includes all SBOMs, regardless of where the SBOM originated. For example, SBOMs that were uploaded to the platform. All SBOMs benefit as new enrichment data comes in. Your view of a build keeps improving over time rather than staying fixed to what was known when the SBOM was first created.

Enrichment starts with version information. More precise version data lets the platform match vulnerabilities to the exact versions in your build, so teams spend less time triaging vulnerabilities that do not apply and get a clearer picture of their real risk.

Ingest SBOMs in the SPDX Format

The platform now supports ingesting SBOMs in the SPDX (Software Package Data Exchange) format, one of the two widely adopted SBOM standards alongside CycloneDX. Teams can bring existing SPDX SBOMs into the RunSafe Security Platform to manage and analyze them alongside SBOMs generated by RunSafe.

Single Sign-On (SSO) Support

The RunSafe Security Platform now supports single sign-on (SSO), allowing users to authenticate through their organization’s identity provider instead of maintaining separate platform credentials.

Project-Level Vulnerability and License Compliance Settings

Vulnerability and license compliance settings can be defined at the organization level, and individual projects can now override those organization defaults with their own settings. This lets teams apply stricter vulnerability and license policies to a specific project without changing the organization-wide configuration.

Generate SBOMs on Windows Without Admin Rights

RunSafe Identify now offers a standalone, non-admin mode for Windows. This installation method runs the SBOM generator in a non-privileged context, so teams can generate SBOMs on Windows without administrator rights. This enables SBOM generation in environments where elevated privileges aren’t available.

More Complete SBOM Generation on Windows

We improved how RunSafe Identify handles Windows file paths for more reliable SBOM generation. We also updated the hooks RunSafe uses on Windows to capture more information during generation, improving the completeness of component data in Windows SBOMs.

More Complete SBOM Metadata

RunSafe Identify now populates additional metadata in generated SBOMs, including manufacturer and build lifecycle fields. This gives teams more complete SBOM data that better aligns with common SBOM standards and reporting requirements.

Command-Line Updates for SBOM Generation

RunSafe Identify added two new options to its command-line interface (CLI). The new --foundation flag generates a foundation report that bundles an SBOM with supporting material, making it easier to integrate RunSafe and evaluate potential configuration improvements. We also added an exclude alias for the existing exclude-directories option, giving teams a shorter way to specify directories to leave out of SBOM generation.

Improved Logging for Hard-to-Access Compilers

RunSafe Identify now produces more detailed logging, which is especially useful when it works with compilers it has limited or no direct access to. This is common in C and C++ environments, and the added detail makes it easier to diagnose and resolve issues during SBOM generation.

If you’d like to learn more about these updates or see them in action, reach out to your RunSafe Security contact. Schedule time with our team here.