-
Notifications
You must be signed in to change notification settings - Fork 13
docs: Add blog post about Conforma demo from Red Hat Summit 2026 #548
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+53
−1
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| --- | ||
| title: "Red Hat Summit 2026: From SBOM to Enforcement — Writing License Policies with Conforma" | ||
| date: 2026-08-19T10:00:00+01:00 | ||
| author: "Luiz Carvalho" | ||
| --- | ||
|
|
||
| We're excited to share that Conforma was featured at Red Hat Summit 2026. The talk demonstrates writing a Conforma policy rule from scratch to solve a real-world license compliance challenge. | ||
|
|
||
| <!--more--> | ||
|
|
||
| ## The Challenge: License Compliance at Scale | ||
|
|
||
| Your legal team mandates "no AGPL" in container images. With hundreds of packages per image, manual checking doesn't scale across multiple teams, constant updates, and the inevitable special cases where specific packages have been individually approved. Organizations need automated enforcement — not just data collection. | ||
|
|
||
| ## From First Rule to Production-Ready | ||
|
|
||
| The demo walks through writing a license policy rule using Rego, starting with a straightforward rule and evolving it commit by commit. Violation messages become more specific. Exceptions handle approved packages. The policy extends to work with SBOMs from multiple sources. Each change is small and purposeful, showing how Conforma and Rego turn requirements into enforceable rules. | ||
|
|
||
| ## Watch the Demo | ||
|
|
||
| Watch a license policy evolve from a simple rule to production-ready enforcement. The demo recording and presentation slides are now available on our Resources page. | ||
|
|
||
| **[Watch "From SBOM to Enforcement: Writing License Policies with Conforma"](/resources/#from-sbom-to-enforcement-writing-license-policies-with-conforma)** | ||
|
|
||
|
Acepresso marked this conversation as resolved.
|
||
| While you're there, explore our collection of other conference presentations, demos, and educational content about securing software supply chains with Conforma. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.