February brought meaningful enhancements across the RunSafe Security Platform, with new compliance controls for GitLab, expanded architecture support in Protect, and continued improvements to SBOM accuracy and package detection in Identify. As always, our focus remains on giving security teams deeper visibility, stronger protection, and more flexible workflows.

Here’s what’s new in February:

• RunSafe Platform: GitLab pipeline enforcement for high, critical, and known-exploited vulnerabilities
• RunSafe Platform: Configurable GitLab remediation workflows
• RunSafe Platform: Multi-organization support with segmented data and access controls
• RunSafe Identify: Expanded package detection for Windows (vcpkg) and VxWorks environments
• RunSafe Identify: Improved license authentication and validation workflow
• RunSafe Protect: MIPS architecture support

Fail GitLab Pipelines on High-Risk Vulnerabilities

We’ve added new vulnerability compliance capabilities for GitLab projects. Customers can now configure pipelines to automatically fail when:

• High or Critical vulnerabilities are detected
• Known Exploited Vulnerabilities (KEV) are identified

Teams can enforce stronger security gates directly within their CI/CD workflows, ensuring that high-risk vulnerabilities are addressed before code progresses further down the pipeline.

Choose How Automated Remediation Works for You

Customers now have full control over how RunSafe applies protection changes to GitLab repos. 

Options now include:

• Opening a Merge Request
• Pushing changes directly to a branch
• No automatic changes (opt-out)

Teams can align RunSafe’s automation with their existing development and approval workflows, whether they prefer formal review processes or fully automated updates.

Multi-Org Support: Segregate Access and Scale Across Teams

We’ve introduced multi-org support within the RunSafe platform.

Users can now:

• Be members of multiple organizations
• Create and manage separate organizations (e.g., by business unit or team)
• Segregate data and access between organizations

Organizations continue to maintain their own data and access boundaries, while executives or responders can span all orgs for cross-team oversight.

SBOM Package Layout Enabled by Default

Package layout is now turned on by default in RunSafe SBOMs. Package layout groups detected files under their corresponding packages whenever possible. This makes Software Bill of Material (SBOM) outputs more intuitive and easier to consume, improving clarity and improving SBOM readability for security and compliance teams.

Improved Package Detection for VxWorks Environments

We’ve enhanced package detection for VxWorks environments, improving visibility into components within embedded and real-time operating systems. These improvements increase SBOM completeness and strengthen vulnerability analysis for teams building on VxWorks.

vcpkg Support for Better Windows Package Detection

With support for vcpkg, RunSafe now leverages metadata from this common Windows package manager to enrich package detection during SBOM generation, improving coverage and vulnerability mapping for Windows-native builds.

Improved License Checking Workflow

We’ve made the license-checking experience in RunSafe Identify more user-friendly. A new login command and refined workflow now make it easier to verify both online and offline license keys, reduce ambiguity around invalid or missing licenses, and simplify onboarding.

RunSafe Protect Adds MIPS Architecture Support

RunSafe Protect now supports MIPS processors, extending runtime protections to a broader set of embedded platforms and use cases. Whether you’re building on specialized hardware or legacy systems, you can now embed memory safety protections across an even wider range of targets.

Interested in Learning More?

If you have questions or would like a demo of these new capabilities, please reach out to your RunSafe Security contact or request a consultation.