# rego Published articles for rego. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Policy as Code in 2026: OPA, Kyverno, Cedar and What's Next DevFeed: [Policy as Code in 2026: OPA, Kyverno, Cedar and What's Next]() Original publisher: [Read original article]() Author: Abhijit Pujare Eric Minick Published: 2026-09-11T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [policy-as-code](), [Open Policy Agent](), [rego](), [Kyverno](), [Software Engineering](), [Kubernetes](), [JSON](), [YAML](), [AI Agent]() Tags: [ai-agent](), [compliance](), [json](), [kyverno](), [opa](), [open-policy-agent](), [policies](), [policy-as-code](), [rego](), [security](), [software-engineering](), [yaml]() ### AI overview This article surveys the 2026 Policy as Code ecosystem, comparing general-purpose Open Policy Agent and Rego with specialized approaches such as Kyverno, Cedar, and agent-oriented governance. It discusses the shift toward automated, machine-readable governance, the separation of policy from business logic, and the challenges of authoring and maintaining Rego as schemas evolve. ### Source excerpt | Blog ## Accelerate teams with platform engineering and policy-as-code DevFeed: [Accelerate teams with platform engineering and policy-as-code]() Original publisher: [Read original article]() Author: Rafael Ferreira Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [DevOps](), [Security](), [Code](), [Deployment](), [opa](), [JSON](), [rego](), [YAML](), [Git]() Tags: [best-practices](), [deployment](), [developer](), [devops](), [engineering](), [git](), [json](), [kyverno](), [platform](), [platform-engineering](), [policy](), [rego](), [security]() ### AI overview This article explains how platform engineering uses internal platforms, golden paths, automation, and self-service to reduce developer cognitive load while improving security, compliance, cost control, and delivery speed. It also presents Policy-as-Code as a way to encode rules in versioned, testable definitions and validate them continuously before deployment, with tools such as OPA and Kyverno providing immediate feedback and audit trails. ### Source excerpt Move from DevOps to platform engineering. Learn golden paths, platform thinking, and why demand is rising for skilled platform engineers ## Automated DevOps Compliance with Harness Rego Policy Packs DevFeed: [Automated DevOps Compliance with Harness Rego Policy Packs]() Original publisher: [Read original article]() Author: Abhijit Pujare Vishal Vishwaroop Published: 2026-07-14T00:00:00Z Content type: release Language: en Sources: [Harness Blog]() Topics: [DevOps](), [rego](), [sdlc](), [opa](), [Security]() Tags: [audit](), [compliance](), [devops](), [governance](), [opa](), [policy](), [policy-as-code](), [rego](), [sdlc]() ### AI overview Harness announces Policy Packs, a curated library of pre-written Rego policies that helps teams align software delivery lifecycles with compliance frameworks. The packs provide out-of-the-box governance controls covering frameworks including SOC 2, NIST, PCI DSS, HIPAA, and HITRUST. ### Source excerpt Shift governance left with out-of-the-box Policy-as-Code. Simplify compliance and achieve continuous audit readiness across your entire SDLC. | Blog ## Optimizing OPA performance: From arrays to objects DevFeed: [Optimizing OPA performance: From arrays to objects]() Original publisher: [Read original article]() Author: Capital One Tech Published: 2026-07-07T14:25:30Z Content type: tutorial Language: en Sources: [Capital One Tech]() Topics: [opa](), [Open Policy Agent](), [rego](), [Data structures](), [Optimization](), [Algorithms, Complexity]() Tags: [algorithms](), [cloud-native](), [data-structures](), [kubernetes](), [opa](), [open-policy-agent](), [optimization](), [performance-tuning](), [rego](), [software-development](), [software-engineering](), [software-supply-chain]() ### AI overview This article explains how to improve Open Policy Agent performance by choosing appropriate data structures for Rego policies. It focuses on replacing nested arrays with keyed objects to avoid inefficient array traversal when evaluating large datasets. ### Source excerpt Achieve 99% faster Rego policy execution through optimization. Note: This post focuses on one aspect of performance tuning Rego policies and datasets evaluated by OPA-arrays vs. objects. The Rego Style Guide and Regal Rego linter are very helpful resources for learning Rego best practices and avoiding code smells in Rego policies. There is also the OPA performance tuning documentation. In 2018, I started using open policy agent (OPA) as a solution for controlling and preventing unwanted behaviors in our Kubernetes Clusters. OPA, along with Kubernetes Dynamic Admission Control, provided a means to build preventive controls. Since then, I have worked with several PaC solutions. I have always stayed close to the OPA tool set because of how well it supports multiple use cases. OPA is domain agnostic and can be used with virtually any use case, as long as you supply the correct data and policies. To that end, OPA use cases have expanded throughout several technical disciplines, such as cloud-native computing and software supply chain management. OPA performance engineering OPA enables us to unify PaC solutions across multiple use cases and systems, using the same languages and tools. However, there is always room for improvement and performance engineering policies and the execution thereof. In addition, optimizing data that policies evaluate and mutate should be part of our focus when we deliver OPA-based solutions. Recently I was asked to help with OPA performance issues. I made several recommendations, but I overlooked one simple and glaring issue: the poor performing policy was processing a large data set using nested-arrays, instead of the best practice of using keyed-objects. Later, something was bothering me about my interaction and I realized that while I gave decent architectural level advice, I completely missed the best engineering advice. Rego policies and data should be optimized just like other algorithms and relative data, and part of that optimization is ## Security Benchmarking Authorization Policy Engines: Rego, Cedar, OpenFGA & Teleport ACD DevFeed: [Security Benchmarking Authorization Policy Engines: Rego, Cedar, OpenFGA & Teleport ACD]() Original publisher: [Read original article]() Author: info@goteleport.com (Mohamed Ouad, Doyensec) Published: 2025-06-04T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [benchmarking](), [Authorization](), [Security](), [rego](), [Open Policy Agent](), [Vulnerabilities]() Tags: [authorization](), [benchmarking](), [opa](), [open-policy-agent](), [performance](), [rego](), [security](), [vulnerabilities]() ### AI overview This article introduces the Security Policy Evaluation Framework (SPEF), an automated testing and benchmarking system for evaluating authorization policy engines. It describes how SPEF assesses robustness, correctness, and performance across Rego, Cedar, OpenFGA, and Teleport ACD. ### Source excerpt Explore how the Security Policy Evaluation Framework (SPEF) benchmarks Rego, Cedar, OpenFGA, and Teleport ACD for vulnerabilities, correctness, and performance. ## Ep. 9: Go Package Design: Authorization and API Structures DevFeed: [Ep. 9: Go Package Design: Authorization and API Structures]() Original publisher: [Read original article]() Published: 2024-07-17T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Authorization](), [rego](), [Software Engineering]() Tags: [access-control](), [api-structures-in-go](), [authentication](), [authorization](), [clean-code-go](), [context-in-go-middleware](), [efficient-go-code](), [error-handling-patterns-go](), [exported-and-unexported-apis-go](), [go](), [go-api-best-practices](), [go-api-readability](), [go-authorization](), [go-authorization-logic](), [go-development-practices](), [go-error-management](), [go-middleware-handlers](), [go-package-design](), [go-package-organization](), [go-package-tutorials](), [go-software-architecture](), [go-software-tips](), [intuitive-go-codebase](), [maintainable-go-code](), [rego](), [rego-scripts-for-go](), [role-based-authorization-in-go](), [scalable-go-software-design](), [secure-access-control-go](), [software-design](), [user-claims-context-go]() ### AI overview This episode explains how to design Go packages that support role-based authorization with Rego, clearly separate exported and unexported APIs, manage errors consistently, and pass information through context between middleware and handlers. ### Source excerpt Introduction: Welcome to Episode 9 of our Ultimate Software Design series! In this episode, Bill delves into the intricacies of implementing robust authorization and API structure within Go packages, offering invaluable insights for developers aiming to build scalable and maintainable software systems. Implement role-based authorization logic for secure and precise access control using Rego scripts. Learn best practices for structuring exported and unexported APIs to maintain a clean, intuitive, and maintainable codebase. ## Automatic source locations with Rego DevFeed: [Automatic source locations with Rego]() Original publisher: [Read original article]() Author: Jasper Van der Jeugt Published: 2024-02-12T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [opa](), [snyk-iac](), [Infrastructure as code](), [Open Policy Agent](), [AWS CloudFormation](), [Terraform]() Tags: [blog](), [blog-post](), [cloud-security](), [cloudformation](), [developer](), [devops](), [engineering](), [iac](), [opa](), [rego](), [snyk](), [snyk-iac](), [technical]() ### AI overview This technical Snyk article explains automatic source code locations for Rego policy violations in Snyk IaC. The feature reports accurate file, line, and column information, including for custom rules. A simplified proof of concept uses CloudFormation YAML, Rego policies, and YAML tree traversal to infer attribute paths and retrieve source locations. ### Source excerpt We recently released a series of improvements to Snyk IaC, and in this blog post, we're taking a technical dive into a particularly interesting feature -- automatic source code locations for rule violations. ## Rego 103: Types of values and rules DevFeed: [Rego 103: Types of values and rules]() Original publisher: [Read original article]() Author: Jasper Van der Jeugt; Becki Lee Published: 2023-11-16T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [rego](), [opa](), [Open Policy Agent](), [Infrastructure as code](), [Programming]() Tags: [beginner](), [blog](), [blog-post](), [cloud-security](), [code](), [developer](), [devrel](), [enablement](), [iac-security](), [infrastructure-as-code](), [learn](), [opa](), [policy](), [programming](), [rego](), [snyk-cloud](), [snyk-iac](), [types]() ### AI overview This beginner-focused article is the third part of a Rego introduction series. It explains scalar and composite value types, including strings, numbers, booleans, null, arrays, objects, and sets, and introduces set rules, object rules, functions, and iteration for writing policies evaluated by OPA. ### Source excerpt Learn about the different types of Values and Rules you can use to build policies in OPA & Rego. ## Rego 102: Combining queries with AND/OR and custom messages DevFeed: [Rego 102: Combining queries with AND/OR and custom messages]() Original publisher: [Read original article]() Author: Jasper Van der Jeugt; Becki Lee Published: 2023-11-09T06:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [rego](), [opa](), [Programming](), [Cloud](), [Infrastructure as code](), [JSON](), [YAML]() Tags: [beginner](), [blog](), [blog-post](), [cloud-security](), [code](), [developer](), [devrel](), [enablement](), [guide](), [how-to](), [iac-security](), [opa](), [policy](), [programming](), [rego](), [snyk-cloud](), [snyk-iac]() ### AI overview A beginner-focused guide to intermediate Rego syntax, explaining how to combine queries with AND and OR and introduce custom messages. It describes how OPA evaluates Rego policies against JSON or YAML input documents. ### Source excerpt Learn how to use AND and OR rules and custom messages using OPA and Rego in the second part of our beginner's guide to Rego. ## Rego 101: Introduction to Rego DevFeed: [Rego 101: Introduction to Rego]() Original publisher: [Read original article]() Author: Becki Lee Published: 2023-11-02T05:00:00Z Content type: tutorial Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [rego](), [opa](), [Open Policy Agent](), [Infrastructure as code](), [Security](), [Programming]() Tags: [blog](), [blog-post](), [cloud-security](), [developer](), [devrel](), [enablement](), [how-to](), [iac-security](), [infrastructure-as-code](), [infrastructure-as-code-iac](), [learn](), [opa](), [policy](), [rego](), [security](), [snyk-cloud](), [snyk-iac](), [tutorial]() ### AI overview A beginner-focused introduction to Rego, the declarative policy language used with Open Policy Agent (OPA). It explains policy as code, how OPA evaluates Rego policies, and how these policies can be applied to cloud and infrastructure-as-code resources. ### Source excerpt Learn how to write your first policy as code rules in Rego. This Rego tutorial for beginners covers the basics of Rego syntax and using OPA. ## Conquering your Build Horizon DevFeed: [Conquering your Build Horizon]() Original publisher: [Read original article]() Published: 2023-10-10T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Automation](), [rego](), [CI/CD](), [Security](), [Vulnerabilities](), [GitHub Copilot]() Tags: [architecture](), [automation](), [base-images](), [build-horizon](), [chainguard-images](), [config](), [container-images](), [defense-in-depth](), [dependencies](), [github-action](), [rego](), [security](), [vulnerability]() ### AI overview The article presents Build Horizon, a policy that limits how long build artifacts such as binaries and container images may remain in production before being rebuilt. It explains how freshness controls, dependency automation, and policy checks can reduce risks from outdated software and long-lived builds. ### Source excerpt "Build Horizon" is a practice that imposes a maximum age on build artifacts. Learn more about how it works and see an example in action! ## Chainguard open sources new policy catalog for Sigstore policy-controller DevFeed: [Chainguard open sources new policy catalog for Sigstore policy-controller]() Original publisher: [Read original article]() Published: 2023-04-18T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [sigstore policy controller](), [sigstore](), [chainguard](), [supply-chain-security](), [Security](), [Kubernetes](), [rego](), [YAML]() Tags: [chainguard](), [kubernetes](), [kubernetes-security](), [rego](), [secure-software](), [security](), [sigstore](), [sigstore-policy-controller](), [supply-chain](), [supply-chain-security](), [trust](), [verification](), [yaml]() ### AI overview Chainguard open sources a policy catalog for Sigstore policy-controller. The catalog provides policies that organizations and open source projects can adopt incrementally to improve software supply-chain security, with community contributions supported. ### Source excerpt To help unlock benefits of the Sigstore policy-controller, Chainguard open sources a policy catalog that can be adopted to improve your supply chain security.