We’ve made a number of updates to the RunSafe Security Platform and RunSafe Identify in May and June, expanding language and source control support, giving teams more control over vulnerability tracking, and cleaning up how SBOMs are generated and documented.
Here’s what’s new:
RunSafe Security Platform
- SBOM generation support for .NET and C# projects
- Connections to self-hosted GitHub Enterprise instances
- Automated email alerts when scans detect new vulnerabilities
- Ability to rename organizations directly in the platform
RunSafe Identify
- Improved deduplication of Windows application and library components
- Error reporting when a generated SBOM has zero components
- Configurable root path for the mask_paths setting
- Beta support for Solaris 10 SBOM generation
- Overhauled config file documentation with new examples
Generate SBOMs for .NET and C# Projects
RunSafe now generates SBOMs for .NET projects, including C# codebases, extending coverage to teams building on the .NET platform.
Connect to Self-Hosted GitHub Enterprise Instances
The RunSafe Security Platform now connects to self-hosted GitHub Enterprise instances, not just GitHub.com. This applies to both the SaaS platform and the on-prem platform, so teams running their own GitHub instance can connect it the same way they would connect GitHub.com.
Get Notified When New Vulnerabilities Are Detected
Organization admins can now configure a new Vulnerability Alerting settings page to add user emails and turn alerting on or off. Once enabled, any automated scan that detects new vulnerabilities triggers an email to the configured recipients, summarizing what was found with direct links to view the details in the platform.
Rename Organizations Anytime
Organizations can now be renamed directly in the platform, making it easier to clean up placeholder names created during trials or setup.
Cleaner, More Accurate SBOMs for Windows Builds
SBOMs generated on Windows previously treated components missing hashes as independent, which inflated component counts and made it harder to identify what mattered. RunSafe now hashes these components so they can be properly deduplicated, significantly reducing noise in Windows SBOMs and ensuring each component is represented distinctly.
Get Alerted When an SBOM Has Zero Components
If a scan results in zero detected components, for example, when everything identified is a build tool or filtered out, RunSafe now returns an error instead of producing an empty SBOM, ensuring users are alerted when attention is needed.
Gain More Control Over Path Masking in SBOMs
The mask_paths configuration option previously worked as a true/false toggle that auto-detected a root path and made all paths in the SBOM relative to it. Teams can now specify their own root path directly for more accurate results, while the true/false option remains available for backward compatibility.
Generate SBOMs on Solaris 10 (Beta)
RunSafe now offers beta support for Solaris 10, giving teams running Solaris environments the ability to generate and analyze SBOMs on the platform.
View Our Config File Documentation Overhaul
The config file documentation has been substantially rewritten for clarity, with expanded examples and a complete sample config file to make it easier to set up and configure the platform.
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.
