RunSafe Security today announced the addition of a new license compliance feature to its RunSafe Security Platform. The rollout of this critical new feature underscores RunSafe Security’s unwavering commitment to remaining the leader in software supply chain security for embedded systems, from generating build-time Software Bill of Materials (SBOMs) to identifying vulnerabilities and preventing exploitation of embedded software at runtime.
The license compliance feature in the RunSafe Security Platform is designed to give embedded teams control over open source licenses and set policies based on their organization’s risk profile. The feature is aimed at companies needing to prevent “copyleft” licenses, which can legally require companies to open-source proprietary code if they inadvertently distribute code with licenses that are not permissive. With this feature enhancement, RunSafe customers can easily decide which licenses are safe, which licenses are off-limits, and how they want their build pipelines to react if an undesirable license is included in a software product.
Additionally, the feature allows customers to configure organization-wide rules to stop the delivery of code licensed under restrictive licensing terms, automatically enforcing license policy within the CI/CD pipeline to prevent the distribution of disallowed licenses in a software release. Unlike complex alternatives that require extensive manual configuration, RunSafe’s approach offers a balanced mix of control and simplicity. Whether a customer wants to automatically fail pipelines that include restricted licenses or allow by default, the settings are configurable to each customer’s business rules. If an organization’s team is using RunSafe’s SBOM generator and adds new dependencies, RunSafe automatically tracks any new or “unset” licenses.
For more information about RunSafe’s approach to licence compliance, vulnerability identification, and protecting embedded software systems, please visit https://runsafesecurity.com.
Like this:
Like Loading...
Related
This entry was posted on November 5, 2025 at 11:27 am and is filed under Commentary with tags RunSafe Security. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
RunSafe Security Releases New License Compliance Feature on the Company’s RunSafe Security Platform
RunSafe Security today announced the addition of a new license compliance feature to its RunSafe Security Platform. The rollout of this critical new feature underscores RunSafe Security’s unwavering commitment to remaining the leader in software supply chain security for embedded systems, from generating build-time Software Bill of Materials (SBOMs) to identifying vulnerabilities and preventing exploitation of embedded software at runtime.
The license compliance feature in the RunSafe Security Platform is designed to give embedded teams control over open source licenses and set policies based on their organization’s risk profile. The feature is aimed at companies needing to prevent “copyleft” licenses, which can legally require companies to open-source proprietary code if they inadvertently distribute code with licenses that are not permissive. With this feature enhancement, RunSafe customers can easily decide which licenses are safe, which licenses are off-limits, and how they want their build pipelines to react if an undesirable license is included in a software product.
Additionally, the feature allows customers to configure organization-wide rules to stop the delivery of code licensed under restrictive licensing terms, automatically enforcing license policy within the CI/CD pipeline to prevent the distribution of disallowed licenses in a software release. Unlike complex alternatives that require extensive manual configuration, RunSafe’s approach offers a balanced mix of control and simplicity. Whether a customer wants to automatically fail pipelines that include restricted licenses or allow by default, the settings are configurable to each customer’s business rules. If an organization’s team is using RunSafe’s SBOM generator and adds new dependencies, RunSafe automatically tracks any new or “unset” licenses.
For more information about RunSafe’s approach to licence compliance, vulnerability identification, and protecting embedded software systems, please visit https://runsafesecurity.com.
Share this:
Like this:
Related
This entry was posted on November 5, 2025 at 11:27 am and is filed under Commentary with tags RunSafe Security. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.