mirror of
https://github.com/open-policy-agent/opa.git
synced 2026-08-12 19:32:48 -06:00
cb79e2eefb
Signed-off-by: David Wertenteil <dwertent@armosec.io>
1989 lines
66 KiB
YAML
1989 lines
66 KiB
YAML
# This file is used to generate the OPA ecosystem page: https://www.openpolicyagent.org/docs/latest/ecosystem/
|
||
# For instructions on how to add an entry, see https://github.com/open-policy-agent/opa/tree/main/docs#integration-index
|
||
integrations:
|
||
styra-das:
|
||
title: Styra Declarative Authorization Service
|
||
description: Styra DAS provides a single pane of glass for authorization and policy across the cloud-native ecosystem of software systems. Beyond a simple control plane, Styra DAS pushes OPA’s potential, providing powerful impact analysis, policy authoring, and decision logging.
|
||
software:
|
||
- styra-das
|
||
- kubernetes
|
||
- envoy
|
||
- terraform
|
||
labels:
|
||
category: authorization
|
||
type: poweredbyopa
|
||
tutorials:
|
||
- https://docs.styra.com/getting-started
|
||
- https://docs.styra.com/tutorials/kubernetes/introduction
|
||
- https://docs.styra.com/tutorials/envoy/introduction
|
||
- https://docs.styra.com/tutorials/ssh/introduction
|
||
- https://docs.styra.com/tutorials/terraform/introduction
|
||
- https://docs.styra.com/tutorials/entitlements/introduction
|
||
- https://academy.styra.com/courses/opa-rego
|
||
code:
|
||
- https://github.com/StyraInc/das-opa-samples
|
||
- https://github.com/StyraInc/example-policy-management
|
||
- https://github.com/StyraInc/entitlements-samples
|
||
inventors:
|
||
- styra
|
||
blogs:
|
||
- https://blog.styra.com/blog/six-of-my-favorite-styra-declarative-authorization-service-das-features
|
||
- https://blog.styra.com/blog/styra-declarative-authorization-service-expands-service-mesh-use-case
|
||
- https://blog.styra.com/blog/opa-styra-terraform-protect-your-cloud-investment
|
||
- https://www.styra.com/blog/how-to-write-your-first-rules-in-rego-the-policy-language-for-opa
|
||
videos:
|
||
- title: "Securing Microservices-Based Apps with Dynamic Traffic Authz"
|
||
speakers:
|
||
- name: Kurt Roekle
|
||
organization: styra
|
||
venue: online
|
||
link: https://www.youtube.com/watch?v=9F-Zyn9j25g
|
||
- title: "Policy Management Across the Cloud-Native Stack: Styra DAS for Terraform"
|
||
speakers:
|
||
- name: Kurt Roekle
|
||
organization: styra
|
||
venue: online
|
||
link: https://www.youtube.com/watch?v=3K0RqIvNfAc
|
||
|
||
circleci:
|
||
title: CircleCI
|
||
description: Use config policy management to create organization-level policies to impose rules and scopes around which configuration elements are required, allowed, not allowed etc.
|
||
software:
|
||
- circleci
|
||
labels:
|
||
category: tooling
|
||
layer: cicd
|
||
type: poweredbyopa
|
||
tutorials:
|
||
- https://circleci.com/docs/config-policy-management-overview/
|
||
inventors:
|
||
- circleci
|
||
|
||
aws-cloudformation-hook:
|
||
title: AWS CloudFormation Hook
|
||
description: AWS CloudFormation Hook that uses OPA to make policy decisions on infrastructure provisioned via AWS CloudFormation
|
||
software:
|
||
- aws
|
||
- cloudformation
|
||
labels:
|
||
type: poweredbyopa
|
||
tutorials:
|
||
- https://www.openpolicyagent.org/docs/latest/aws-cloudformation-hooks/
|
||
code:
|
||
- https://github.com/StyraInc/opa-aws-cloudformation-hook
|
||
blogs:
|
||
- https://blog.styra.com/blog/the-opa-aws-cloudformation-hook
|
||
inventors:
|
||
- styra
|
||
|
||
oauth2:
|
||
title: OAuth2
|
||
description: Integrating OAuth2 with Open Policy Agent
|
||
software:
|
||
- oauth
|
||
labels:
|
||
category: security
|
||
tutorials:
|
||
- https://www.openpolicyagent.org/docs/latest/oauth-oidc/
|
||
blogs:
|
||
- https://blog.styra.com/blog/integrating-identity-oauth2-and-openid-connect-in-open-policy-agent
|
||
|
||
oidc:
|
||
title: OpenID Connect (OIDC)
|
||
description: Integrating OpenID Connect (OIDC) with Open Policy Agent
|
||
software:
|
||
- oauth
|
||
- oidc
|
||
labels:
|
||
category: security
|
||
tutorials:
|
||
- https://www.openpolicyagent.org/docs/latest/oauth-oidc/
|
||
blogs:
|
||
- https://blog.styra.com/blog/integrating-identity-oauth2-and-openid-connect-in-open-policy-agent
|
||
|
||
google-kubernetes-engine:
|
||
title: Google Kubernetes Engine (GKE)
|
||
description: OPA related tools and policy libraries for Kubernetes in the Google Cloud Platform
|
||
software:
|
||
- kubernetes
|
||
- google-kubernetes-engine
|
||
labels:
|
||
category: containers
|
||
layer: orchestration
|
||
code:
|
||
- https://github.com/google/gke-policy-automation
|
||
tutorials:
|
||
- https://github.com/google/gke-policy-automation/tree/main/gke-policies
|
||
inventors:
|
||
- google
|
||
|
||
apache-apisix:
|
||
title: Authorization Integration with Apache APISIX
|
||
description: Apache APISIX provides a plugin for delegating fine-grained authorization decisions to OPA.
|
||
software:
|
||
- apache-apisix
|
||
labels:
|
||
category: gateway
|
||
layer: network
|
||
code:
|
||
- https://github.com/apache/apisix
|
||
inventors:
|
||
- apache-apisix
|
||
blogs:
|
||
- https://apisix.apache.org/blog/2021/12/24/open-policy-agent
|
||
- https://medium.com/@ApacheAPISIX/apache-apisix-integrates-with-open-policy-agent-to-enrich-its-ecosystem-15569fe3ab9c
|
||
|
||
dapr:
|
||
title: Dapr
|
||
description: Middleware to apply Open Policy Agent policies on incoming requests
|
||
software:
|
||
- dapr
|
||
labels:
|
||
category: application
|
||
layer: network
|
||
tutorials:
|
||
- https://docs.dapr.io/reference/components-reference/supported-middleware/middleware-opa/
|
||
code:
|
||
- https://github.com/dapr/dapr
|
||
|
||
fig:
|
||
title: fig
|
||
description: Beautiful shell autocompletion for OPA and many other commands, for Mac OS
|
||
software:
|
||
- fig
|
||
labels:
|
||
category: utilities
|
||
layer: shell
|
||
code:
|
||
- https://github.com/open-policy-agent/contrib/tree/main/opa_fig_autocomplete
|
||
- https://github.com/withfig/autocomplete/blob/master/src/opa.ts
|
||
inventors:
|
||
- fig
|
||
|
||
fiber:
|
||
title: fiber
|
||
description: |
|
||
Fiber is an Express inspired web framework built on top of Fasthttp, the fastest HTTP engine for Go.
|
||
Designed to ease things up for fast development with zero memory allocation and performance in mind.
|
||
With Open Policy Agent integration, you can run your Rego policies as part of the request lifecycle in the middleware.
|
||
labels:
|
||
category: application
|
||
layer: library
|
||
software:
|
||
- golang
|
||
- fiber
|
||
code:
|
||
- https://github.com/gofiber/contrib/tree/main/opafiber
|
||
|
||
sphinx-rego:
|
||
title: Automatically document Rego policies
|
||
description: Sphinx extension that automatically documents Open Policy Agent Rego policies using meta properties.
|
||
software:
|
||
- sphinx-doc
|
||
code:
|
||
- https://github.com/zenitysec/sphinx-rego
|
||
inventors:
|
||
- zenity
|
||
labels:
|
||
category: tooling
|
||
layer: cicd
|
||
|
||
kubernetes-validating-admission:
|
||
title: Kubernetes Admission Control
|
||
description: Kubernetes automates deployment, scaling, and management of containerized applications. OPA provides fine-grained, context-aware authorization for which application component configuration.
|
||
software:
|
||
- kubernetes
|
||
labels:
|
||
category: containers
|
||
layer: orchestration
|
||
tutorials:
|
||
- https://www.openpolicyagent.org/docs/kubernetes-admission-control.html
|
||
- https://katacoda.com/austinheiman/scenarios/open-policy-agent-gatekeeper
|
||
code:
|
||
- https://github.com/open-policy-agent/kube-mgmt
|
||
- https://github.com/open-policy-agent/gatekeeper
|
||
inventors:
|
||
- styra
|
||
- microsoft
|
||
- google
|
||
videos:
|
||
- title: Securing Kubernetes With Admission Controllers
|
||
speakers:
|
||
- name: Dave Strebel
|
||
organization: microsoft
|
||
venue: Kubecon Seattle 2018
|
||
link: https://sched.co/GrZQ
|
||
- title: Using OPA for Admission Control in Production
|
||
speakers:
|
||
- name: Zach Abrahamson
|
||
organization: Capital One
|
||
- name: Todd Ekenstam
|
||
organization: Intuit
|
||
venue: Kubecon Seattle 2018
|
||
link: https://sched.co/Grbn
|
||
- title: Liz Rice Keynote
|
||
speakers:
|
||
- name: Liz Rice
|
||
organization: AquaSecurity
|
||
venue: Kubecon Seattle 2018
|
||
link: https://youtu.be/McDzaTnUVWs?t=418
|
||
- title: Intro to Open Policy Agent Gatekeeper
|
||
speakers:
|
||
- name: Rita Zhang
|
||
organization: microsoft
|
||
- name: Max Smythe
|
||
organization: google
|
||
venue: Kubecon Barcelona 2019
|
||
link: https://kccnceu19.sched.com/event/MPiM/intro-open-policy-agent-rita-zhang-microsoft-max-smythe-google
|
||
- title: Policy Enabled Kubernetes and CICD
|
||
speakers:
|
||
- name: Jimmy Ray
|
||
organization: capitalone
|
||
venue: OPA Summit at Kubecon San Diego 2019
|
||
link: https://www.youtube.com/watch?v=vkvWZuqSk5M
|
||
- title: "TripAdvisor: Building a Testing Framework for Integrating OPA into K8s"
|
||
speakers:
|
||
- name: Luke Massa
|
||
organization: tripadvisor
|
||
venue: OPA Summit at Kubecon San Diego 2019
|
||
link: https://www.youtube.com/watch?v=X09c1eXvCFM
|
||
- title: Enforcing automatic mTLS with Linkerd and OPA Gatekeeper
|
||
speakers:
|
||
- name: Ivan Sim
|
||
organization: buoyant
|
||
- name: Rita Zhang
|
||
organization: microsoft
|
||
venue: Kubecon San Diego 2019
|
||
link: https://www.youtube.com/watch?v=gMaGVHnvNfs
|
||
- title: Enforcing Service Mesh Structure using OPA Gatekeeper
|
||
speakers:
|
||
- name: Sandeep Parikh
|
||
organization: google
|
||
venue: Kubecon San Diego 2019
|
||
link: https://www.youtube.com/watch?v=90RHTBinAFU
|
||
- title: "TGIK: Exploring the Open Policy Agent"
|
||
speakers:
|
||
- name: Joe Beda
|
||
organization: VMware
|
||
link: https://www.youtube.com/watch?v=QU9BGPf0hBw
|
||
blogs:
|
||
- https://medium.com/@sbueringer/kubernetes-authorization-via-open-policy-agent-a9455d9d5ceb
|
||
- https://medium.com/@jimmy.ray/policy-enabled-kubernetes-with-open-policy-agent-3b612b3f0203
|
||
- https://blog.openpolicyagent.org/securing-the-kubernetes-api-with-open-policy-agent-ce93af0552c3
|
||
- https://itnext.io/kubernetes-authorization-via-open-policy-agent-a9455d9d5ceb
|
||
- https://medium.com/capital-one-tech/policy-enabled-kubernetes-with-open-policy-agent-3b612b3f0203
|
||
- https://blog.openshift.com/fine-grained-policy-enforcement-in-openshift-with-open-policy-agent/
|
||
|
||
kubernetes-authorization:
|
||
title: Kubernetes Authorization
|
||
description: |
|
||
Kubernetes Authorization is a pluggable mechanism that lets administrators control which users can run which APIs and
|
||
is often handled by builtin RBAC. OPA's policy language is more flexible than the RBAC, for example,
|
||
writing policy using a prohibited list of APIs instead of the usual RBAC style of listing the permitted APIs.
|
||
code:
|
||
- https://github.com/open-policy-agent/contrib/tree/main/k8s_authorization
|
||
blogs:
|
||
- https://blog.styra.com/blog/kubernetes-authorization-webhook
|
||
- https://itnext.io/kubernetes-authorization-via-open-policy-agent-a9455d9d5ceb
|
||
- https://itnext.io/optimizing-open-policy-agent-based-kubernetes-authorization-via-go-execution-tracer-7b439bb5dc5b
|
||
inventors:
|
||
- styra
|
||
|
||
kubernetes-provisioning:
|
||
title: Kubernetes Provisioning
|
||
description: Kubernetes automates deployment, scaling, and management of containerized applications. OPA decides which resources need to be created on k8s in response to a namespace being created.
|
||
software:
|
||
- kubernetes
|
||
labels:
|
||
category: containers
|
||
layer: orchestration
|
||
inventors:
|
||
- goldmansachs
|
||
videos:
|
||
- title: Kubernetes Policy Enforcement Using OPA at Goldman Sachs
|
||
speakers:
|
||
- name: Miguel Uzcategui
|
||
organization: goldmansachs
|
||
- name: Tim Hinrichs
|
||
organization: styra
|
||
venue: Kubecon San Diego 2019
|
||
link: https://www.youtube.com/watch?v=lYHr_UaHsYQ&list=PLj6h78yzYM2NDs-iu8WU5fMxINxHXlien&index=140&t=0s
|
||
|
||
google-calendar:
|
||
title: Google Calendar
|
||
description: Using the Google Calendar API with OPA for calendar powered policy decisions
|
||
labels:
|
||
category: data
|
||
layer: rego
|
||
software:
|
||
- google-calendar
|
||
inventors:
|
||
- styra
|
||
code:
|
||
- https://github.com/anderseknert/opa-google-calendar
|
||
blogs:
|
||
- https://blog.styra.com/blog/the-power-of-data-calendar-based-policy-enforcement
|
||
|
||
gcp-forseti:
|
||
title: GCP audit with Forseti
|
||
description: |
|
||
Google cloud provides a plethora of software as a service.
|
||
Forseti, built using OPA, lets you run policy checks against the software resources on Google cloud and remediate violations.
|
||
labels:
|
||
category: publiccloud
|
||
inventors:
|
||
- google
|
||
code:
|
||
- https://forsetisecurity.org
|
||
videos:
|
||
- title: Repeatable GCP Environments at Scale with Cloud Build Infra-as-Code Pipelines
|
||
speakers:
|
||
- name: Morgante Pell
|
||
organization: google
|
||
- name: Andrew Phillips
|
||
organization: google
|
||
venue: Cloud Next 2019
|
||
link: https://www.youtube.com/watch?v=3vfXQxWJazM&feature=youtu.be&t=2054
|
||
|
||
aws-api-gateway:
|
||
title: AWS API Gateway
|
||
description: The AWS API Gateway controls API traffic for your application running on AWS. OPA can be configured as an external authorizer for that Gateway to implement authorization policies on APIs.
|
||
labels:
|
||
category: servicemesh
|
||
layer: gateway
|
||
code:
|
||
- https://github.com/zotoio/sls-lambda-opa
|
||
|
||
antlr:
|
||
title: ANTLR Grammar
|
||
description: ANTLR4 grammar for Rego.
|
||
labels:
|
||
category: utilities
|
||
layer: rego
|
||
code:
|
||
- https://github.com/antlr/grammars-v4
|
||
inventors:
|
||
- independent
|
||
|
||
traefik-api-gateway:
|
||
title: Traefik API Gateway
|
||
description: |
|
||
The Traefik API Gateway is open-source software that controls API traffic into your application.
|
||
OPA can be configured as a plugin to implement authorization policies for those APIs.
|
||
labels:
|
||
category: servicemesh
|
||
layer: gateway
|
||
blogs:
|
||
- https://engineering.etermax.com/api-authorization-with-kubernetes-traefik-and-open-policy-agent-23647fc384a1
|
||
|
||
nodejs-express:
|
||
title: NodeJS express
|
||
description: |
|
||
Express is a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications.
|
||
OPA can be used to implement authorization policies for APIs used in the express framework.
|
||
labels:
|
||
category: application
|
||
layer: network
|
||
code:
|
||
- https://github.com/build-security/opa-express-middleware
|
||
inventors:
|
||
- build.security
|
||
|
||
nginx:
|
||
title: Nginx
|
||
description: OPA Authorization for Nginx
|
||
labels:
|
||
category: gateway
|
||
layer: network
|
||
software:
|
||
- nginx
|
||
code:
|
||
- https://github.com/summerwind/opa-nginx-rbac
|
||
|
||
asp-dotnet-core:
|
||
title: ASP.NET Core
|
||
description: |
|
||
Use ASP.NET Core to create web apps and services that are fast, secure, cross-platform, and cloud-based.
|
||
OPA can be used to implement authorization policies for APIs used in the ASP.NET Core framework.
|
||
labels:
|
||
category: application
|
||
layer: network
|
||
code:
|
||
- https://github.com/build-security/OPA-AspDotNetCore-Middleware
|
||
inventors:
|
||
- build.security
|
||
|
||
gloo-api-gateway:
|
||
title: Gloo API Gateway
|
||
description: |
|
||
Gloo is an open-source Kubernetes-native ingress controller, and next-generation API gateway.
|
||
OPA can be used to implement authorization policies for those APIs.
|
||
labels:
|
||
category: servicemesh
|
||
layer: gateway
|
||
blogs:
|
||
- https://medium.com/solo-io/5-min-with-gloo-api-gateway-configuration-with-open-policy-agent-53da276a6534
|
||
- https://docs.solo.io/gloo/latest/security/auth/opa/
|
||
|
||
envoy-authorization:
|
||
title: Container Network Authorization with Envoy
|
||
description: Envoy is a networking abstraction for cloud-native applications. OPA hooks into Envoy’s external authorization filter to provide fine-grained, context-aware authorization for network or HTTP requests.
|
||
labels:
|
||
category: servicemesh
|
||
layer: network
|
||
software:
|
||
- envoy
|
||
tutorials:
|
||
- https://github.com/tsandall/minimal-opa-envoy-example/blob/master/README.md
|
||
- https://www.openpolicyagent.org/docs/latest/envoy-introduction/
|
||
code:
|
||
- https://github.com/open-policy-agent/opa-istio-plugin
|
||
- https://github.com/tsandall/minimal-opa-envoy-example
|
||
inventors:
|
||
- styra
|
||
blogs:
|
||
- https://blog.openpolicyagent.org/envoy-external-authorization-with-opa-578213ed567c
|
||
videos:
|
||
- title: "OPA at Scale: How Pinterest Manages Policy Distribution"
|
||
speakers:
|
||
- name: Will Fu
|
||
organization: pinterest
|
||
- name: Jeremy Krach
|
||
organization: pinterest
|
||
venue: OPA Summit at Kubecon San Diego 2019
|
||
link: https://www.youtube.com/watch?v=LhgxFICWsA8
|
||
- title: "Deploying Open Policy Agent at Atlassian"
|
||
speakers:
|
||
- name: Chris Stivers
|
||
organization: atlassian
|
||
- name: Nicholas Higgins
|
||
organization: atlassian
|
||
venue: OPA Summit at Kubecon San Diego 2019
|
||
link: https://www.youtube.com/watch?v=nvRTO8xjmrg
|
||
- title: How Yelp Moved Security From the App to the Mesh with Envoy and OPA
|
||
speakers:
|
||
- name: Daniel Popescu
|
||
organization: yelp
|
||
- name: Ben Plotnick
|
||
organization: yelp
|
||
venue: Kubecon San Diego 2019
|
||
link: https://www.youtube.com/watch?v=Z6aN3Smt-9M
|
||
|
||
custom-library-microservice-authorization:
|
||
title: Library-based Microservice Authorization
|
||
description: Microservice authorization can be enforced through a network proxy like Envoy/Istio/Linkerd/...
|
||
or can be enforced by modifying the microservice code to use a common library. In both cases
|
||
OPA makes the authorization decision that the network proxy or the library enforce.
|
||
labels:
|
||
category: servicemesh
|
||
layer: library
|
||
videos:
|
||
- title: How Netflix is Solving Authorization Across Their Cloud
|
||
speakers:
|
||
- name: Manish Mehta
|
||
organization: netflix
|
||
- name: Torin Sandall
|
||
organization: styra
|
||
venue: Kubecon Austin 2017
|
||
link: https://www.youtube.com/watch?v=R6tUNpRpdnY
|
||
|
||
istio-authorization-edge:
|
||
title: Container Network Authorization with Istio (at the Edge)
|
||
description: Istio is a networking abstraction for cloud-native applications that uses Envoy at the edge. OPA hooks into Envoy’s external authorization filter to provide fine-grained, context-aware authorization for network or HTTP requests.
|
||
labels:
|
||
category: servicemesh
|
||
layer: network
|
||
software:
|
||
- istio
|
||
- envoy
|
||
- spire
|
||
tutorials:
|
||
- https://github.com/open-policy-agent/opa-istio-plugin/blob/master/README.md
|
||
code:
|
||
- https://github.com/open-policy-agent/opa-istio-plugin
|
||
- https://github.com/tsandall/minimal-opa-envoy-example
|
||
- https://github.com/open-policy-agent/opa-envoy-spire-ext-authz
|
||
blogs:
|
||
- https://blog.openpolicyagent.org/envoy-external-authorization-with-opa-578213ed567c
|
||
inventors:
|
||
- styra
|
||
|
||
istio-authorization-mixer:
|
||
title: Container Network Authorization with Istio (as part of Mixer)
|
||
description: Istio is a networking abstraction for cloud-native applications. In this Istio integration OPA hooks into the centralized Mixer component of Istio, to provide fine-grained, context-aware authorization for network or HTTP requests.
|
||
labels:
|
||
category: servicemesh
|
||
layer: network
|
||
software:
|
||
- istio
|
||
tutorials:
|
||
- https://istio.io/docs/reference/config/policy-and-telemetry/adapters/opa/
|
||
code:
|
||
- https://github.com/istio/istio/tree/master/mixer/adapter/opa
|
||
inventors:
|
||
- google
|
||
|
||
openfaas-function-authorization:
|
||
title: OpenFaaS Serverless Function Authorization
|
||
description: OpenFaaS is a serverless function framework that runs on Docker Swarm and Kubernetes. OPA makes it possible to provide fine-grained context-aware authorization on a per-function basis.
|
||
labels:
|
||
layer: application
|
||
category: serverless
|
||
software:
|
||
- openfaas
|
||
code:
|
||
- https://github.com/adaptant-labs/openfaas-function-auth-opa
|
||
tutorials:
|
||
- https://github.com/adaptant-labs/openfaas-function-auth-opa/blob/master/README.md
|
||
inventors:
|
||
- adaptant
|
||
|
||
kong-authorization:
|
||
title: API Gateway Authorization with Kong
|
||
description: Kong is a microservice API Gateway. OPA provides fine-grained, context-aware control over the requests that Kong receives.
|
||
labels:
|
||
layer: network
|
||
category: gateway
|
||
software:
|
||
- kong
|
||
code:
|
||
- https://github.com/TravelNest/kong-authorization-opa
|
||
- https://github.com/open-policy-agent/contrib/tree/master/kong_api_authz
|
||
inventors:
|
||
- travelnest
|
||
- wada-ama
|
||
|
||
linux-pam:
|
||
title: SSH and Sudo Authorization with Linux
|
||
description: Host-level access controls are an important part of every organization's security strategy. OPA provides fine-grained, context-aware controls for SSH and sudo using Linux-PAM.
|
||
software:
|
||
- linuxpam
|
||
labels:
|
||
layer: server
|
||
tutorials:
|
||
- https://www.openpolicyagent.org/docs/ssh-and-sudo-authorization.html
|
||
code:
|
||
- https://github.com/open-policy-agent/contrib/tree/master/pam_opa
|
||
inventors:
|
||
- styra
|
||
|
||
kafka-authorization:
|
||
title: Kafka Topic Authorization
|
||
description: Apache Kafka is a high-performance distributed streaming platform deployed by thousands of companies. OPA provides fine-grained, context-aware access control of which users can read/write which Kafka topics to enforce important requirements around confidentiality and integrity.
|
||
software:
|
||
- kafka
|
||
labels:
|
||
category: streaming
|
||
layer: data
|
||
blogs:
|
||
- https://opencredo.com/blogs/controlling-kafka-data-flows-using-open-policy-agent/
|
||
tutorials:
|
||
- https://www.openpolicyagent.org/docs/latest/kafka-authorization/
|
||
code:
|
||
- https://github.com/StyraInc/opa-kafka-plugin
|
||
- https://github.com/llofberg/kafka-authorizer-opa
|
||
- https://github.com/opencredo/opa-single-message-transformer
|
||
inventors:
|
||
- ticketmaster
|
||
- styra
|
||
videos:
|
||
- title: "OPA at Scale: How Pinterest Manages Policy Distribution"
|
||
speakers:
|
||
- name: Will Fu
|
||
organization: pinterest
|
||
- name: Jeremy Krach
|
||
organization: pinterest
|
||
venue: OPA Summit at Kubecon San Diego 2019
|
||
link: https://www.youtube.com/watch?v=LhgxFICWsA8
|
||
|
||
strimzi:
|
||
title: Strimzi (Apache Kafka on Kubernetes)
|
||
description: Strimzi provides a way to run an Apache Kafka cluster on Kubernetes in various deployment configurations. Strimzi ships with the OPA authorizer plugin right out of the box, and supports OPA as an option for Kafka authorization.
|
||
software:
|
||
- kafka
|
||
- strimzi
|
||
labels:
|
||
category: streaming
|
||
layer: data
|
||
blogs:
|
||
- https://strimzi.io/blog/2020/08/05/using-open-policy-agent-with-strimzi-and-apache-kafka/
|
||
- https://strimzi.io/blog/2020/09/01/enforce-custom-resource-policies-with-opa-gatekeeper/
|
||
code:
|
||
- https://github.com/strimzi/strimzi-kafka-operator
|
||
- https://github.com/scholzj/demo-opa-kafka-authorization
|
||
- https://github.com/StyraInc/opa-kafka-plugin
|
||
inventors:
|
||
- redhat
|
||
|
||
ceph:
|
||
title: Ceph Object Storage Authorization
|
||
description: Ceph is a highly scalable distributed storage solution that uniquely delivers object, block, and file storage in one unified system. OPA provides fine-grained, context-aware authorization of the information stored within Ceph.
|
||
software:
|
||
- ceph
|
||
labels:
|
||
category: object
|
||
layer: data
|
||
tutorials:
|
||
- https://docs.ceph.com/docs/master/radosgw/opa/
|
||
- https://www.katacoda.com/styra/scenarios/opa-ceph
|
||
inventors:
|
||
- styra
|
||
- redhat
|
||
videos:
|
||
- https://www.youtube.com/watch?v=9m4FymEvOqM&feature=share
|
||
|
||
clojure:
|
||
title: App authorization for Clojure
|
||
description: Authorization middleware for Ring based apps and other utilities for working with OPA in Clojure.
|
||
software:
|
||
- clojure
|
||
labels:
|
||
layer: network
|
||
category: application
|
||
code:
|
||
- https://github.com/anderseknert/clj-opa
|
||
inventors:
|
||
- styra
|
||
|
||
open-service-mesh:
|
||
title: Open Service Mesh (OSM)
|
||
description: Open Service Mesh is a lightweight and extensible cloud native service mesh.
|
||
software:
|
||
- osm
|
||
labels:
|
||
category: servicemesh
|
||
layer: network
|
||
code:
|
||
- https://github.com/openservicemesh/osm/blob/main/docs/example/manifests/opa/deploy-opa-envoy.yaml
|
||
tutorials:
|
||
- https://release-v0-11.docs.openservicemesh.io/docs/guides/integrations/external_auth_opa/#osm-with-opa-plugin-external-authorization-walkthrough
|
||
|
||
minio:
|
||
title: Minio API Authorization
|
||
description: Minio is an open source, on-premise object database compatible with the Amazon S3 API. This integration lets OPA enforce policies on Minio's API.
|
||
software:
|
||
- minio
|
||
labels:
|
||
layer: data
|
||
category: authorization
|
||
tutorials:
|
||
- https://github.com/minio/minio/blob/master/docs/iam/opa.md
|
||
inventors:
|
||
- minio
|
||
- styra
|
||
|
||
terraform:
|
||
title: Terraform Policy
|
||
description: Terraform lets you describe the infrastructure you want and automatically creates, deletes, and modifies your existing infrastructure to match. OPA makes it possible to write policies that test the changes Terraform is about to make before it makes them.
|
||
software:
|
||
- terraform
|
||
- aws
|
||
- gcp
|
||
- azure
|
||
labels:
|
||
category: publiccloud
|
||
layer: orchestration
|
||
tutorials:
|
||
- https://www.openpolicyagent.org/docs/terraform.html
|
||
- https://github.com/instrumenta/conftest/blob/master/README.md
|
||
code:
|
||
- https://github.com/instrumenta/conftest
|
||
- https://github.com/fugue/regula
|
||
- https://github.com/accurics/terrascan
|
||
- https://github.com/Checkmarx/kics
|
||
- https://github.com/open-policy-agent/library/tree/master/terraform
|
||
- https://github.com/accurics/terrascan/tree/master/pkg/policies/opa/rego
|
||
- https://github.com/Checkmarx/kics/tree/master/assets/queries/terraform
|
||
blogs:
|
||
- https://blog.styra.com/blog/policy-based-infrastructure-guardrails-with-terraform-and-opa
|
||
inventors:
|
||
- fugue
|
||
- accurics
|
||
- checkmarx
|
||
- medallia
|
||
- styra
|
||
- docker
|
||
- snyk
|
||
|
||
terraform-cloud:
|
||
title: Terraform Cloud
|
||
description: Policies are rules that Terraform Cloud enforces on runs. You use the Rego policy language to write policies for the Open Policy Agent (OPA) framework.
|
||
software:
|
||
- terraform
|
||
- terraform-cloud
|
||
- aws
|
||
- gcp
|
||
- azure
|
||
labels:
|
||
category: publiccloud
|
||
layer: orchestration
|
||
tutorials:
|
||
- https://developer.hashicorp.com/terraform/cloud-docs/policy-enforcement/opa
|
||
- https://developer.hashicorp.com/terraform/tutorials/cloud/drift-and-opa
|
||
- https://developer.hashicorp.com/terraform/cloud-docs/policy-enforcement/opa/vcs
|
||
videos:
|
||
- title: "Terraform Cloud Learn Lab: Validate Infrastructure and Enforce OPA Policies"
|
||
speakers:
|
||
- name: Rita Sokolova
|
||
organization: HashiCorp
|
||
- name: Cole Morrison
|
||
organization: HashiCorp
|
||
venue: HashiConf Europe 2022
|
||
link: https://www.youtube.com/watch?v=jO2CiYMPxFE
|
||
inventors:
|
||
- hashicorp
|
||
|
||
pulumi:
|
||
title: Pulumi
|
||
description: Build infrastructure as code in familiar languages. CrossGuard is Pulumi's policy as code offering, providing OPA as one of the options to use for defining policy.
|
||
software:
|
||
- pulumi
|
||
- aws
|
||
- gcp
|
||
- azure
|
||
labels:
|
||
category: publiccloud
|
||
layer: orchestration
|
||
code:
|
||
- https://github.com/pulumi/pulumi-policy-opa
|
||
blogs:
|
||
- https://www.pulumi.com/blog/opa-support-for-crossguard/
|
||
videos:
|
||
- title: "Testing Configuration with Open Policy Agent"
|
||
speakers:
|
||
- name: Gareth Rushgrove
|
||
organization: snyk
|
||
venue: Cloud Engineering Summit 2020
|
||
link: https://www.pulumi.com/resources/testing-configuration-with-open-policy-agent/
|
||
inventors:
|
||
- pulumi
|
||
|
||
iptables:
|
||
title: IPTables
|
||
description: IPTables is a useful tool available to Linux kernel for filtering network packets. OPA makes it possible to manage IPTables rules using context-aware policy.
|
||
labels:
|
||
layer: network
|
||
category: linux
|
||
software:
|
||
- linux
|
||
tutorials:
|
||
- https://github.com/open-policy-agent/contrib/blob/master/opa-iptables/docs/tutorial.md
|
||
code:
|
||
- https://github.com/open-policy-agent/contrib/tree/master/opa-iptables
|
||
inventors:
|
||
- gsoc
|
||
- cisco
|
||
- styra
|
||
|
||
dart-authorization:
|
||
title: HTTP API Authorization in Dart
|
||
description: This integration demonstrates how to leverage OPA to perform basic HTTP API authorization in a simple Dart microservice. OPA makes it possible to provide fine-grained context-aware authorization for each REST endpoint and access method.
|
||
labels:
|
||
layer: network
|
||
category: application
|
||
software:
|
||
- dart
|
||
tutorials:
|
||
- https://github.com/adaptant-labs/opa-api-authz-dart/README.md
|
||
code:
|
||
- https://github.com/adaptant-labs/opa-api-authz-dart
|
||
inventors:
|
||
- adaptant
|
||
|
||
springsecurity-api:
|
||
title: Authorization for Java Spring Security
|
||
description: Spring Security provides a framework for securing Java applications. These integrations provide simple implementations for Spring Security that use OPA for making API authorization decisions. They provide support for both traditional Spring Security (MVC), as well as an implementation for Spring Reactive (Web Flux).
|
||
labels:
|
||
layer: network
|
||
category: application
|
||
software:
|
||
- javaspringsecurity
|
||
code:
|
||
- https://github.com/open-policy-agent/contrib/tree/master/spring_authz
|
||
- https://github.com/Bisnode/opa-spring-security
|
||
- https://github.com/build-security/opa-java-spring-client
|
||
- https://github.com/massenz/jwt-opa
|
||
- https://github.com/eugenp/tutorials/tree/master/spring-security-modules/spring-security-opa
|
||
|
||
tutorials:
|
||
- https://github.com/open-policy-agent/contrib/blob/master/spring_authz/README.md
|
||
- https://github.com/massenz/jwt-opa#web-server-demo-app
|
||
- https://www.baeldung.com/spring-security-authorization-opa
|
||
inventors:
|
||
- styra
|
||
- build.security
|
||
- bisnode
|
||
- alertavert
|
||
|
||
spinnaker-pipeline:
|
||
title: Spinnaker Pipeline Policy Enforcment
|
||
description: Spinnaker is a Continuous Delivery and Deployment tool started by Netflix. OPA lets you configure policies that dictate what kinds of Spinnaker pipelines developers can create.
|
||
labels:
|
||
layer: cicd
|
||
software:
|
||
- spinnaker
|
||
blogs:
|
||
- https://blog.armory.io/deployment-policies-with-spinnaker/
|
||
tutorials:
|
||
- https://docs.armory.io/spinnaker/policy_engine/
|
||
inventors:
|
||
- armory
|
||
|
||
java:
|
||
title: Authorization for Java
|
||
description: Integrations for interacting with OPA from Java
|
||
labels:
|
||
layer: network
|
||
category: application
|
||
software:
|
||
- java
|
||
code:
|
||
- https://github.com/Bisnode/opa-java-client
|
||
inventors:
|
||
- bisnode
|
||
|
||
jenkins-job-authorization:
|
||
title: Jenkins Job Trigger Policy Enforcement
|
||
description: Jenkins automates software development processes. OPA lets you control which people and which machines can run which Jenkins jobs.
|
||
labels:
|
||
layer: cicd
|
||
software:
|
||
- jenkins
|
||
inventors:
|
||
- pinterest
|
||
videos:
|
||
- title: "OPA at Scale: How Pinterest Manages Policy Distribution"
|
||
speakers:
|
||
- name: Will Fu
|
||
organization: pinterest
|
||
- name: Jeremy Krach
|
||
organization: pinterest
|
||
venue: OPA Summit at Kubecon San Diego 2019
|
||
link: https://www.youtube.com/watch?v=LhgxFICWsA8
|
||
|
||
|
||
elasticsearch-datafiltering:
|
||
title: Elasticsearch Data Filtering
|
||
description: Elasticsearch is a distributed, open source search and analytics engine. This OPA integration lets an elasticsearch client construct queries so that the data returned by elasticsearch obeys OPA-defined policies.
|
||
labels:
|
||
layer: data
|
||
category: filtering
|
||
software:
|
||
- elasticsearch
|
||
code:
|
||
- https://github.com/open-policy-agent/contrib/tree/master/data_filter_elasticsearch
|
||
tutorials:
|
||
- https://github.com/open-policy-agent/contrib/blob/master/data_filter_elasticsearch/README.md
|
||
inventors:
|
||
- styra
|
||
|
||
sql-datafiltering:
|
||
title: SQL Database Data Filtering
|
||
description: This integration enables the client of a SQL database to enhance a SQL query so that the results obey an OPA-defined policy.
|
||
labels:
|
||
layer: data
|
||
category: filtering
|
||
software:
|
||
- sqlite
|
||
code:
|
||
- https://github.com/open-policy-agent/contrib/tree/master/data_filter_example
|
||
blogs:
|
||
- https://blog.openpolicyagent.org/write-policy-in-opa-enforce-policy-in-sql-d9d24db93bf4
|
||
inventors:
|
||
- styra
|
||
|
||
clair-datasource:
|
||
title: Kubernetes Admission Control using Vulnerability Scanning
|
||
description: Admission control policies in Kubernetes can be augmented with vulnerability scanning results to make more informed decisions. This integration demonstrates how to integrate Clair with OPA and run it as an admission controller.
|
||
software:
|
||
- kubernetes
|
||
- clair
|
||
labels:
|
||
layer: orchestration
|
||
category: containers
|
||
datasource: clair
|
||
code:
|
||
- https://github.com/open-policy-agent/contrib/tree/master/image_enforcer
|
||
tutorials:
|
||
- https://github.com/open-policy-agent/contrib/blob/master/image_enforcer/README.md
|
||
|
||
cloudflare-worker:
|
||
title: Cloudflare Worker Enforcement of OPA Policies Using WASM
|
||
description: Cloudflare Workers are a serverless platform that supports WASM. This integration uses OPA's WASM compiler to generate code enforced at the edge of Cloudflare's network.
|
||
software:
|
||
- cloudflare
|
||
labels:
|
||
layer: application
|
||
category: serverless
|
||
code:
|
||
- https://github.com/open-policy-agent/contrib/tree/master/wasm/cloudflare-worker
|
||
tutorials:
|
||
- https://github.com/open-policy-agent/contrib/blob/master/wasm/cloudflare-worker/README.md
|
||
|
||
docker-machine:
|
||
title: Docker controls via OPA Policies
|
||
description: Docker's out of the box authorization model is all or nothing. This integration demonstrates how to use OPA's context-aware policies to exert fine-grained control over Docker.
|
||
software:
|
||
- docker
|
||
labels:
|
||
layer: server
|
||
category: container
|
||
code:
|
||
- https://github.com/open-policy-agent/opa-docker-authz
|
||
tutorials:
|
||
- https://www.openpolicyagent.org/docs/latest/docker-authorization/
|
||
inventors:
|
||
- styra
|
||
|
||
conftest:
|
||
title: Conftest -- Configuration checking
|
||
description: Conftest is a utility built on top of OPA to help you write tests against structured configuration data.
|
||
labels:
|
||
type: poweredbyopa
|
||
layer: configuration
|
||
code:
|
||
- https://github.com/instrumenta/conftest
|
||
software:
|
||
- kustomize
|
||
- terraform
|
||
- aws
|
||
- toml
|
||
- docker
|
||
videos:
|
||
- title: "Applying Policy Throughout the Application Lifecycle with Open Policy Agent"
|
||
speakers:
|
||
- name: Gareth Rushgrove
|
||
organization: snyk
|
||
venue: Kubecon San Diego 2019
|
||
link: https://www.youtube.com/watch?v=cXfsaE6RKfc
|
||
|
||
boomerang-bosun:
|
||
title: Boomerang Bosun Policy Gating
|
||
description: Boomerang Bosun is a policy-based gating system that combines Policy Templates with Rules and data to validate Gates.
|
||
labels:
|
||
type: poweredbyopa
|
||
layer: application
|
||
code:
|
||
- https://www.useboomerang.io/
|
||
- https://github.com/boomerang-io
|
||
inventors:
|
||
- ibm
|
||
- boomerang
|
||
software:
|
||
- bosun
|
||
|
||
kubeshield:
|
||
title: Secure Kubernetes using eBPF & Open Policy Agent
|
||
description: Ensure runtime security in any linux machine by combining Extended Berkeley Packet Filter(eBPF) and Open Policy Agent.
|
||
software:
|
||
- linux
|
||
- kubernetes
|
||
- ebpf
|
||
labels:
|
||
layer: application
|
||
catagory: filtering
|
||
code:
|
||
- https://github.com/kubeshield/bpf-opa-demo
|
||
blogs:
|
||
- https://blog.byte.builders/post/bpf-opa/
|
||
|
||
php-authorization:
|
||
title: HTTP API Authorization in PHP
|
||
description: These integrations demonstrate using OPA to perform API authorization in PSR-15 and Symfony compliant frameworks.
|
||
labels:
|
||
layer: network
|
||
category: application
|
||
software:
|
||
- php
|
||
tutorials:
|
||
- https://coil.com/p/segra/OPA-for-API-Authorization-with-Slim-PHP/H-7YsQL2m
|
||
code:
|
||
- https://github.com/segrax/opa-php-examples
|
||
- https://github.com/segrax/openpolicyagent
|
||
- https://github.com/build-security/opa-symfony-middleware
|
||
inventors:
|
||
- build.security
|
||
|
||
gradle-plugin:
|
||
title: Gradle Build Plugin
|
||
description: Build plugin adding various tasks to support using OPA as part of Gradle builds
|
||
labels:
|
||
layer: cicd
|
||
category: cicdplugin
|
||
type: poweredbyopa
|
||
software:
|
||
- gradle
|
||
- java
|
||
- groovy
|
||
- kotlin
|
||
code:
|
||
- https://github.com/Bisnode/opa-gradle-plugin
|
||
- https://plugins.gradle.org/plugin/com.bisnode.opa
|
||
inventors:
|
||
- bisnode
|
||
|
||
custom-application:
|
||
title: Custom Application Authorization
|
||
description: |
|
||
Application require authorization decisions made at the API gateway, frontend, backend, and database.
|
||
OPA helps developers decouple authorization logic from application code, define a custom authorization model
|
||
that enables end-users to control tenant permissions, and enforce that policy across the different components of the
|
||
application (gateway, frontend, backend, database).
|
||
tutorials:
|
||
- https://github.com/chef/automate/tree/master/components/authz-service#authz-with-opa
|
||
blogs:
|
||
- https://blog.verygoodsecurity.com/posts/building-a-fine-grained-permission-system-in-a-distributed-environment/
|
||
- https://choria.io/blog/post/2020/02/14/rego_policies_opa/
|
||
videos:
|
||
- title: "OPA in Practice: From Angular to OPA in Chef Automate"
|
||
speakers:
|
||
- name: Michael Sorens
|
||
organization: chef
|
||
venue: OPA Summit at Kubecon San Diego 2019
|
||
link: https://www.youtube.com/watch?v=jrrW855xL3s
|
||
|
||
sysdig-image-scanner:
|
||
title: Kubernetes Sysdig Image Scanner Admission Controller
|
||
description: Sysdig’s OPA Image Scanner combines Sysdig Secure image scanner with OPA policy-based rego language to evaluate the scan results and the admission context, providing great flexibility on the admission decision.
|
||
software:
|
||
- kubernetes
|
||
- sysdigsecure
|
||
labels:
|
||
category: containers
|
||
layer: orchestration
|
||
code:
|
||
- https://github.com/sysdiglabs/opa-image-scanner
|
||
inventors:
|
||
- sysdig
|
||
|
||
pomerium-authz:
|
||
title: Pomerium Access Proxy
|
||
description: Pomerium is an identity-aware proxy that enables secure access to internal applications. OPA implements authorization under the hood.
|
||
labels:
|
||
layer: network
|
||
category: proxy
|
||
software:
|
||
- pomerium
|
||
blogs:
|
||
- https://www.pomerium.io/posts/2020/04/16/release-0-7/
|
||
code:
|
||
- https://github.com/pomerium/pomerium
|
||
|
||
coredns-authz:
|
||
title: CoreDNS Authorization
|
||
description: CoreDNS is a cloud-native DNS server written in Go. OPA can be used as a plugin to filter queries and responses.
|
||
labels:
|
||
layer: network
|
||
category: dns
|
||
software:
|
||
- coredns
|
||
code:
|
||
- https://github.com/coredns/policy
|
||
inventors:
|
||
- infoblox
|
||
|
||
gluu-gateway-authz:
|
||
title: Gluu Gateway Authorization
|
||
description: Gluu Gateway provides API authentication and authorization for websites built on Kong. Gluu provides an OPA plugin to handle API authorization.
|
||
labels:
|
||
layer: network
|
||
category: gateway
|
||
software:
|
||
- gluu
|
||
- kong
|
||
code:
|
||
- https://github.com/GluuFederation/gluu-gateway
|
||
|
||
pre-commit-hooks:
|
||
title: Pre-commit hooks
|
||
description: Pre-commit git hooks for OPA and Rego development
|
||
labels:
|
||
category: tooling
|
||
layer: cicd
|
||
software:
|
||
- git
|
||
- pre-commit
|
||
code:
|
||
- https://github.com/anderseknert/pre-commit-opa
|
||
blogs:
|
||
- https://www.eknert.com/tech/2020/08/31/pre-commit-hooks-for-opa
|
||
inventors:
|
||
- independent
|
||
|
||
scalr-iacp:
|
||
title: Scalr - Policy enforcement for Terraform
|
||
description: Scalr allows teams to easily collaborate on Terraform through its pipeline that runs all Terraform operations, policy checks, and stores state. Scalr uses OPA to check the auto-generated Terraform JSON plan to ensure that it meets your organization standards prior to an apply.
|
||
labels:
|
||
category: Infrastructure as Code
|
||
layer: cicd
|
||
software:
|
||
- terraform
|
||
tutorials:
|
||
- https://iacp.docs.scalr.com/en/latest/working-with-iacp/opa.html#creating-the-opa-policy
|
||
code:
|
||
- https://github.com/Scalr/sample-tf-opa-policies
|
||
inventors:
|
||
- scalr
|
||
blogs:
|
||
- https://www.scalr.com/blog/opa-is-to-policy-automation-as-terraform-is-to-iac/
|
||
|
||
spire:
|
||
title: SPIRE
|
||
description: SPIRE is a production-ready implementation of the SPIFFE APIs that performs node and workload attestation in order to securely issue SPIFFE Verifiable Identity Documents (SVIDs) to workloads, and verify the SVIDs of other workloads, based on a predefined set of conditions.
|
||
labels:
|
||
layer: network
|
||
category: application
|
||
software:
|
||
- spiffe
|
||
- spire
|
||
blogs:
|
||
- https://blog.styra.com/blog/zero-trust-with-envoy-spire-and-open-policy-agent-opa
|
||
code:
|
||
- https://github.com/spiffe/spire/blob/v1.0.2/doc/authorization_policy_engine.md
|
||
tutorials:
|
||
- https://spiffe.io/docs/latest/microservices/envoy-opa/readme/
|
||
- https://spiffe.io/docs/latest/microservices/envoy-jwt-opa/readme/
|
||
|
||
fairwinds-insights:
|
||
title: Fairwinds Insights Configuration Validation Software
|
||
description: Automate, monitor and enforce OPA policies with visibility across multiple clusters and multiple teams. It ensures the same policies are applied across all your clusters and gives some flexibility if you want certain policies to apply to only certain workloads. Run the same policies in CI/CD, Admission Control, and In-cluster scanning to apply policy consistently throughout the development and deployment process.
|
||
labels:
|
||
category: kubernetes
|
||
layer: cicd
|
||
inventors:
|
||
- fairwinds
|
||
software:
|
||
- kubernetes
|
||
- docker
|
||
- helm
|
||
tutorials:
|
||
- https://insights.docs.fairwinds.com/features/policy/
|
||
- https://insights.docs.fairwinds.com/reports/opa/
|
||
- https://insights.docs.fairwinds.com/features/admission-controller/
|
||
- https://insights.docs.fairwinds.com/features/continuous-integration/
|
||
videos:
|
||
- https://youtu.be/kmvPYjx1bpU
|
||
- https://youtu.be/gxE_Tkj6d40
|
||
blogs:
|
||
- https://www.fairwinds.com/blog/managing-opa-policies-with-fairwinds-insights
|
||
- https://www.fairwinds.com/blog/manage-open-policy-agent-opa-consistently
|
||
- https://www.fairwinds.com/blog/kubernetes-multi-cluster-visibility-why-how-to-get-it
|
||
- https://www.fairwinds.com/blog/what-is-kubernetes-policy-as-code
|
||
- https://www.fairwinds.com/blog/why-kubernetes-policy-enforcement
|
||
- https://www.fairwinds.com/blog/an-interview-with-flatfile-on-why-fairwinds-insights-kubernetes-configuration-validation
|
||
|
||
flask-opa:
|
||
title: Flask-OPA
|
||
description: Simple to use Flask extension that lets you secure your projects with OPA. It allows HTTP API Authorization and Policy Enforcement Point (AOP using decorators on methods).
|
||
labels:
|
||
category: flask
|
||
layer: library
|
||
code:
|
||
- https://github.com/EliuX/flask-opa
|
||
blogs:
|
||
- https://github.com/EliuX/flask-opa/tree/master/examples
|
||
|
||
permit:
|
||
title: Permit.io
|
||
description: |
|
||
Permit.io empowers developers to bake in permissions and access-control into any product in minutes and takes away the pain of constantly rebuilding them.
|
||
Permit is based on OPA.
|
||
labels:
|
||
category: authorization
|
||
layer: application
|
||
inventors:
|
||
- permitio
|
||
code:
|
||
- https://github.com/permitio
|
||
tutorials:
|
||
- https://docs.permit.io/
|
||
videos:
|
||
- https://docs.permit.io/tutorials/onboarding_demo
|
||
blogs:
|
||
- https://www.permit.io/blog/introduction-to-opa
|
||
- https://www.permit.io/blog/implement-abac-using-opa
|
||
- https://www.permit.io/blog/implement-rbac-using-opa
|
||
|
||
opal:
|
||
title: OPAL (Open Policy Administration Layer)
|
||
description: |
|
||
OPAL is an administration layer for Open Policy Agent (OPA), detecting changes in realtime to both policy and policy data and pushing live updates to your agents.
|
||
OPAL brings open-policy up to the speed needed by live applications. As your application state changes (whether it's via your APIs, DBs, git, S3 or 3rd-party SaaS services), OPAL will make sure your services are always in sync with the authorization data and policy they need (and only those they need).
|
||
labels:
|
||
category: updates
|
||
layer: application
|
||
inventors:
|
||
- permitio
|
||
software:
|
||
- opal
|
||
code:
|
||
- https://github.com/permitio/opal
|
||
tutorials:
|
||
- https://github.com/permitio/opal/blob/master/docs/index.md
|
||
videos:
|
||
- https://www.youtube.com/watch?v=K1Zm2FPfrh8
|
||
|
||
optoggles:
|
||
title: OPToggles (Open Policy Toggles)
|
||
description: |
|
||
OPToggles uses OPA and OPAL to sync open-policy to your frontend with the help of feature flag solutions.
|
||
OPToggles creates user-targeted feature flags based on the policy rules you defined in OPA and keeps the users updated in real-time with OPAL's real-time policy and policy-data change detection.
|
||
OPToggles already supports launchdarkly.com and a generic REST API.
|
||
labels:
|
||
category: updates
|
||
layer: application
|
||
inventors:
|
||
- permitio
|
||
code:
|
||
- https://github.com/permitio/OPToggles
|
||
tutorials:
|
||
- https://optoggles.opal.ac/tutorials/demo
|
||
|
||
bottle:
|
||
title: Custom Bottle Application Authorization
|
||
description: |
|
||
This integration demonstrates using Open Policy Agent to perform API authorization for a Python application backed by Bottle.
|
||
Bottle is a fast, simple and lightweight WSGI micro web-framework for Python.
|
||
labels:
|
||
layer: network
|
||
category: application
|
||
software:
|
||
- bottle
|
||
code:
|
||
- https://github.com/dolevf/bottle-acl-openpolicyagent
|
||
blogs:
|
||
- https://blog.lethalbit.com/open-policy-agent-for-bottle-web-framework/
|
||
|
||
kubescape:
|
||
title: Kubescape Kubernetes security posture scanner
|
||
description: |
|
||
This integration uses OPA for defining security controls over Kubernetes clusters. Kubescape is a simple extensible tool
|
||
finding security problems in your environment. OPA enables Kubescape to implement and extend very fast to answer new problems.
|
||
labels:
|
||
category: security
|
||
layer: application
|
||
software:
|
||
- kubescape
|
||
code:
|
||
- https://github.com/kubescape/kubescape
|
||
- https://github.com/kubescape/regolibrary
|
||
inventors:
|
||
- armo
|
||
tutorials:
|
||
- https://hub.armosec.io/docs
|
||
|
||
i2scim:
|
||
title: i2scim.io SCIM Restful User/Group Provisioning API
|
||
description: |
|
||
i2scim.io is an open source, Apache 2 Licensed, implementation of SCIM (System for Cross-domain Identity Management RFC7643/7644) for use
|
||
cloud-native kubernetes platforms. i2scim supports externalized access control decisions through OPA. SCIM is a RESTful HTTP API that can be
|
||
used to provide a standardized way to provision accounts from Azure, Okta, PingIdentity and other providers and tools. SCIM can also be used
|
||
as a backing identity store for OAuth and other authentication services.
|
||
labels:
|
||
category: security
|
||
layer: application
|
||
software:
|
||
- i2scim
|
||
code:
|
||
- https://github.com/i2-open/i2scim
|
||
- https://i2scim.io
|
||
inventors:
|
||
- i2
|
||
tutorials:
|
||
- https://i2scim.io/OPA_AccessControl.html
|
||
|
||
graphene-graphql:
|
||
title: Custom Application with Field-level Authorization in Graphene GraphQL
|
||
description: |
|
||
This integration demonstrates using Open Policy Agent to perform field-level Authorization with GraphQL for a custom Python application backed by Graphene.
|
||
labels:
|
||
layer: network
|
||
category: application
|
||
software:
|
||
- graphene-graphql
|
||
code:
|
||
- https://github.com/dolevf/graphql-open-policy-agent
|
||
|
||
rekor:
|
||
title: Rekor transparency log monitoring and alerting
|
||
description: |
|
||
Rekor Sidekick monitors a Rekor signature transparency log and forwards events of interest where ever you like.
|
||
Alert policies written in Rego determine if an event is of interest.
|
||
labels:
|
||
category: security
|
||
layer: application
|
||
software:
|
||
- rekor
|
||
inventors:
|
||
- sigstore
|
||
code:
|
||
- https://github.com/nsmith5/rekor-sidekick
|
||
videos:
|
||
- https://www.youtube.com/watch?v=lHSLPIo1pz8
|
||
|
||
cosign:
|
||
title: Container Signing, Verification and Storage in an OCI registry
|
||
description: |
|
||
Cosign is a tool for container image signing and verifying maintained under the Project Sigstore
|
||
in collaboration with the Linux Foundation. Among other features, Cosign supports KMS signing,
|
||
built-in binary transparency, and timestamping service with Rekor and Kubernetes policy enforcement.
|
||
labels:
|
||
category: security
|
||
layer: application
|
||
software:
|
||
- cosign
|
||
inventors:
|
||
- sigstore
|
||
code:
|
||
- https://docs.sigstore.dev/cosign/attestation#validate-in-toto-attestations
|
||
- https://github.com/sigstore/cosign-gatekeeper-provider
|
||
vides:
|
||
- https://www.youtube.com/watch?v=gCi9_4NYyR0
|
||
|
||
alfred:
|
||
title: Self-hosted Alternative to OPA Playground
|
||
description: |
|
||
Alfred introduces a local graphical user interface to interact with Open Policy Agent and acts as an alternative to OPA's playground, allowing the user to keep information related to policy testing locally.
|
||
labels:
|
||
layer: network
|
||
category: application
|
||
software:
|
||
- alfred
|
||
code:
|
||
- https://github.com/dolevf/Open-Policy-Agent-Alfred
|
||
|
||
open-policy-registry:
|
||
title: Open Policy Registry
|
||
description: |
|
||
The Open Policy Registry project provides a docker workflow for OPA policies. The policy CLI can be used to build, tag, sign, push, and pull OPA policies as OCIv2 container images,
|
||
in conjunction with any container registry. The Open Policy Registry (OPCR) is a reference implementation of a policy registry, built and hosted on GCP.
|
||
labels:
|
||
category: containers
|
||
layer: application
|
||
inventors:
|
||
- aserto
|
||
software:
|
||
- open-policy-registry
|
||
code:
|
||
- https://github.com/opcr-io/policy
|
||
tutorials:
|
||
- https://www.openpolicyregistry.io/docs/tutorial
|
||
blogs:
|
||
- https://www.openpolicyregistry.io/blog/docker-workflow-for-opa
|
||
|
||
aserto:
|
||
title: Aserto
|
||
description: |
|
||
Aserto is a cloud-native authorization service that makes it easy to add permissions and RBAC to your SaaS applications and APIs.
|
||
Aserto is based on the Open Policy Agent.
|
||
labels:
|
||
category: authorization
|
||
layer: application
|
||
type: poweredbyopa
|
||
inventors:
|
||
- aserto
|
||
software:
|
||
- aserto
|
||
code:
|
||
- https://github.com/aserto-dev
|
||
- https://github.com/opcr-io
|
||
tutorials:
|
||
- https://docs.aserto.com/docs
|
||
blogs:
|
||
- https://www.aserto.com/blog/how-do-aserto-rego-policies-work
|
||
- https://www.aserto.com/blog/testing-rego-policies
|
||
- https://www.aserto.com/blog/aserto-on-aserto-an-opa-authorization-policy-for-aserto-tenants
|
||
- https://www.aserto.com/blog/rego-getting-started
|
||
videos:
|
||
- https://www.youtube.com/watch?v=RJkgmdjJn_w
|
||
|
||
topaz:
|
||
title: Topaz
|
||
description: |
|
||
Topaz is an open source authorization service providing fine grained, real-time, policy based access control for applications and APIs.
|
||
Topaz uses OPA as its decision engine, and includes an embedded database that stores subjects, relations, and objects, inspired by the Google Zanzibar data model.
|
||
Topaz can be deployed as a sidecar or microservice in your cloud.
|
||
labels:
|
||
category: authorization
|
||
layer: application
|
||
type: poweredbyopa
|
||
inventors:
|
||
- aserto
|
||
software:
|
||
- topaz
|
||
code:
|
||
- https://github.com/aserto-dev/topaz
|
||
tutorials:
|
||
- https://www.topaz.sh
|
||
- https://github.com/aserto-dev/topaz#quickstart
|
||
blogs:
|
||
- https://www.aserto.com/blog/topaz-oss-cloud-native-authorization-combines-opa-zanzibar
|
||
|
||
emissary-ingress:
|
||
title: Emissary-Ingress
|
||
description: |
|
||
Emissary-Ingress is an open-source Kubernetes-native API Gateway, Layer 7 load balancer and Kubernetes Ingress built on Envoy Proxy.
|
||
OPA can be integrated with Emissary as an external authorization service to enforce authorization policies over APIs.
|
||
labels:
|
||
category: network
|
||
layer: gateway
|
||
software:
|
||
- emissary-ingress
|
||
blogs:
|
||
- https://www.infracloud.io/blogs/emissary-ingress-opa-integration/
|
||
|
||
magda:
|
||
title: Magda
|
||
description: |
|
||
Magda is a federated, Kubernetes-based, open-source data catalog system.
|
||
Working as Magda's central authorisation policy engine, OPA helps not only the API endpoint authorisation.
|
||
Magda also uses its partial evaluation feature to translate datasets authorisation decisions to other database-specific DSLs (e.g. SQL or Elasticsearch DSL) and use them for dataset authorisation enforcement in different databases.
|
||
labels:
|
||
type: poweredbyopa
|
||
category: application
|
||
layer: application
|
||
software:
|
||
- magda
|
||
code:
|
||
- https://github.com/magda-io/magda
|
||
blogs:
|
||
- https://github.com/magda-io/magda/blob/master/docs/docs/architecture/Guide%20to%20Magda%20Internals.md#authorization-authz
|
||
|
||
sansshell:
|
||
title: Sansshell
|
||
description: A non-interactive daemon for host management
|
||
software:
|
||
- sansshell
|
||
labels:
|
||
category: management
|
||
layer: server
|
||
type: poweredbyopa
|
||
code:
|
||
- https://github.com/Snowflake-Labs/sansshell
|
||
blogs:
|
||
- https://www.snowflake.com/blog/sansshell-local-host-agent/
|
||
inventors:
|
||
- snowflake
|
||
|
||
rond:
|
||
title: Rönd
|
||
description: |
|
||
Rönd is a lightweight container that distributes security policy enforcement throughout your application.
|
||
software:
|
||
- rond
|
||
labels:
|
||
category: authorization
|
||
layer: application
|
||
code:
|
||
- https://github.com/rond-authz/rond
|
||
tutorials:
|
||
- https://github.com/rond-authz/example
|
||
videos:
|
||
- title: "Rönd - The Open Source K8s sidecar that defines security policies over your APIs"
|
||
speakers:
|
||
- name: Federico Maggi
|
||
organization: mia-platform
|
||
link: https://youtu.be/ubT31NtHV8w
|
||
inventors:
|
||
- mia-platform
|
||
blogs:
|
||
- https://blog.mia-platform.eu/en/announcing-rond-new-open-source-security-enforcement-over-your-apis
|
||
- https://blog.mia-platform.eu/en/how-why-adopted-role-based-access-control-rbac
|
||
|
||
waltid:
|
||
title: walt.id
|
||
description: |
|
||
Verifying W3C Verifiable Credentials for building SSI (Self-Sovereign Identity) use cases.
|
||
labels:
|
||
category: authorization
|
||
layer: application
|
||
type: poweredbyopa
|
||
inventors:
|
||
- waltid
|
||
- blockchainlabum
|
||
- netis
|
||
software:
|
||
- ssikit
|
||
code:
|
||
- https://github.com/walt-id/waltid-ssikit
|
||
tutorials:
|
||
- https://docs.walt.id/v/ssikit/ssi-kit/open-policy-agent
|
||
- https://docs.walt.id/v/ssikit/concepts/verification-policies/dynamic-policies
|
||
videos:
|
||
- title: "Verifying W3C Verifiable Credentials with the SSI Kit using OPA (Open Policy Agent)"
|
||
speakers:
|
||
- name: Severin Stampler
|
||
organization: waltid
|
||
link: https://youtu.be/mue4UjzOZ3Q
|
||
|
||
graphql:
|
||
title: GraphQL
|
||
description: |
|
||
GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data.
|
||
labels:
|
||
category: network
|
||
layer: application
|
||
software:
|
||
- graphql
|
||
code:
|
||
- https://github.com/StyraInc/graphql-apollo-example
|
||
tutorials:
|
||
- https://www.openpolicyagent.org/docs/graphql-api-authorization/
|
||
|
||
spacelift:
|
||
title: Spacelift
|
||
description: Spacelift is a sophisticated CI/CD platform for Infrastructure as Code including Terraform, Pulumi, CloudFormation, Kubernetes, and Ansible. Spacelift utilizes Open Policy Agent to support a variety of policy types within the platform and Policy as Code for secure and compliance Infrastructure as Code.
|
||
labels:
|
||
category: Infrastructure as Code
|
||
layer: cicd
|
||
software:
|
||
- terraform
|
||
- pulumi
|
||
- cloudformation
|
||
- kubernetes
|
||
- ansible
|
||
- aws
|
||
- gcp
|
||
- azure
|
||
tutorials:
|
||
- https://docs.spacelift.io/concepts/policy
|
||
code:
|
||
- https://github.com/spacelift-io/spacelift-policies-example-library
|
||
inventors:
|
||
- spacelift
|
||
blogs:
|
||
- https://spacelift.io/blog/what-is-open-policy-agent-and-how-it-works
|
||
|
||
easegress:
|
||
title: Easegress
|
||
description: |
|
||
Easegress is a Cloud Native API orchestration system.
|
||
OPA can be configured as a filter(plugin) to implement authorization policies for the APIs.
|
||
labels:
|
||
category: gateway
|
||
layer: network
|
||
code:
|
||
- https://github.com/megaease/easegress
|
||
inventors:
|
||
- megaease
|
||
|
||
organizations:
|
||
styra:
|
||
name: Styra
|
||
link: https://styra.com
|
||
microsoft:
|
||
name: Microsoft
|
||
link: https://microsoft.com
|
||
google:
|
||
name: Google
|
||
link: https://google.com
|
||
travelnest:
|
||
name: TravelNest
|
||
link: https://travelnest.com
|
||
ticketmaster:
|
||
name: TicketMaster
|
||
link: https://www.ticketmaster.com/
|
||
docker:
|
||
name: Docker
|
||
link: https://www.docker.com/
|
||
snyk:
|
||
name: Snyk
|
||
link: https://snyk.io/
|
||
ceph:
|
||
name: Ceph
|
||
link: https://ceph.io/
|
||
fig:
|
||
name: fig
|
||
link: https://fig.io
|
||
redhat:
|
||
name: RedHat
|
||
link: https://www.redhat.com
|
||
medallia:
|
||
name: Medallia
|
||
link: https://www.medallia.com/
|
||
gsoc:
|
||
name: Google Summer of Code
|
||
link: https://summerofcode.withgoogle.com/
|
||
cisco:
|
||
name: Cisco
|
||
link: https://www.cisco.com/
|
||
adaptant:
|
||
name: Adaptant
|
||
link: https://www.adaptant.io/
|
||
armory:
|
||
name: Armory
|
||
link: https://www.armory.io/
|
||
minio:
|
||
name: Minio
|
||
link: https://min.io/
|
||
ibm:
|
||
name: IBM
|
||
link: https://developer.ibm.com/open
|
||
boomerang:
|
||
name: Boomerang
|
||
link: https://www.useboomerang.io/
|
||
bisnode:
|
||
name: Bisnode
|
||
link: https://www.bisnode.com
|
||
goldmansachs:
|
||
name: Goldman Sachs
|
||
link: https://www.goldmansachs.com/
|
||
pinterest:
|
||
name: Pinterest
|
||
link: https://www.pinterest.com/
|
||
atlassian:
|
||
name: Atlassian
|
||
link: https://www.atlassian.com/
|
||
tripadvisor:
|
||
name: TripAdvisor
|
||
link: https://www.tripadvisor.com/
|
||
chef:
|
||
name: Chef
|
||
link: https://www.chef.io/
|
||
buoyant:
|
||
name: Buoyant
|
||
link: https://buoyant.io/
|
||
netflix:
|
||
name: Netflix
|
||
link: https://www.netflix.com/
|
||
capitalone:
|
||
name: CapitalOne
|
||
link: https://www.capitalone.com/
|
||
yelp:
|
||
name: Yelp
|
||
link: https://www.yelp.com/
|
||
sysdig:
|
||
name: Sysdig
|
||
link: https://sysdig.com/
|
||
wada-ama:
|
||
name: World Anti-Doping Agency
|
||
link: https://www.wada-ama.org
|
||
infoblox:
|
||
name: InfoBlox
|
||
link: https://www.infoblox.com/
|
||
independent:
|
||
name: Independent developer
|
||
link: https://www.openpolicyagent.org
|
||
scalr:
|
||
name: Scalr
|
||
link: https://www.scalr.com/
|
||
sigstore:
|
||
name: Sigstore
|
||
link: https://sigstore.dev/
|
||
build.security:
|
||
name: build.security
|
||
link: https://build.security
|
||
fugue:
|
||
name: Fugue
|
||
link: https://www.fugue.co
|
||
accurics:
|
||
name: Accurics
|
||
link: https://www.accurics.com/
|
||
checkmarx:
|
||
name: Checkmarx
|
||
link: https://www.checkmarx.com
|
||
fairwinds:
|
||
name: Fairwinds
|
||
link: https://fairwinds.com
|
||
permitio:
|
||
name: Permit.io
|
||
link: https://permit.io
|
||
alertavert:
|
||
name: AlertAVert.com
|
||
link: https://www.alertavert.com/
|
||
zenity:
|
||
name: Zenity
|
||
link: https://www.zenity.io
|
||
apache-apisix:
|
||
name: Apache APISIX
|
||
link: https://apisix.apache.org/
|
||
armo:
|
||
name: ARMO
|
||
link: https://armosec.io
|
||
i2:
|
||
name: Independent Identity
|
||
link: https://www.independentid.com
|
||
aserto:
|
||
name: Aserto
|
||
link: https://www.aserto.com
|
||
snowflake:
|
||
name: Snowflake
|
||
link: https://www.snowflake.com/
|
||
pulumi:
|
||
name: Pulumi
|
||
link: https://www.pulumi.com/
|
||
mia-platform:
|
||
name: Mia-Platform
|
||
link: https://mia-platform.eu/
|
||
waltid:
|
||
name: walt.id
|
||
link: https://walt.id
|
||
blockchainlabum:
|
||
name: Blockchain Lab:UM
|
||
link: https://blockchain-lab.um.si
|
||
netis:
|
||
name: Netis
|
||
link: http://netis.si/en/
|
||
spacelift:
|
||
name: Spacelift
|
||
link: https://spacelift.io
|
||
circleci:
|
||
name: CircleCI
|
||
link: https://circleci.com
|
||
hashicorp:
|
||
name: HashiCorp
|
||
link: https://www.hashicorp.com/
|
||
megaease:
|
||
name: MegaEase
|
||
link: https://www.megaease.com/
|
||
|
||
software:
|
||
oauth:
|
||
name: OAuth
|
||
link: https://oauth.net/
|
||
oidc:
|
||
name: OpenID Connect (OIDC)
|
||
link: https://openid.net/connect/
|
||
dapr:
|
||
name: Dapr
|
||
link: https://dapr.io/
|
||
fig:
|
||
name: fig
|
||
link: https://fig.io
|
||
kubernetes:
|
||
name: Kubernetes
|
||
link: https://kubernetes.io
|
||
envoy:
|
||
name: Envoy
|
||
link: https://envoyproxy.io
|
||
istio:
|
||
name: Istio
|
||
link: https://istio.io
|
||
kong:
|
||
name: Kong
|
||
link: https://konghq.com/
|
||
linuxpam:
|
||
name: Linux PAM
|
||
link: http://www.linux-pam.org/
|
||
terraform:
|
||
name: Terraform
|
||
link: https://www.terraform.io/
|
||
kafka:
|
||
name: Kafka
|
||
link: https://kafka.apache.org/
|
||
ceph:
|
||
name: Ceph
|
||
link: https://ceph.io/
|
||
clojure:
|
||
name: Clojure
|
||
link: https://clojure.org
|
||
cosign:
|
||
name: Cosign
|
||
link: https://github.com/sigstore/cosign
|
||
aws:
|
||
name: Amazon Public Cloud
|
||
link: https://aws.com
|
||
gcp:
|
||
name: Google Public Cloud
|
||
link: https://cloud.google.com/
|
||
azure:
|
||
name: Microsoft Public Cloud
|
||
link: https://azure.microsoft.com/
|
||
cloudformation:
|
||
name: AWS CloudFormation
|
||
link: https://aws.amazon.com/cloudformation/
|
||
fiber:
|
||
name: Fiber
|
||
link: https://docs.gofiber.io
|
||
golang:
|
||
name: golang
|
||
link: https://golang.org/
|
||
java:
|
||
name: Java
|
||
link: https://www.java.com/
|
||
javaspringsecurity:
|
||
name: Spring Security
|
||
link: https://spring.io/projects/spring-security
|
||
osm:
|
||
name: Open Service Mesh
|
||
link: https://openservicemesh.io/
|
||
spinnaker:
|
||
name: Spinnaker
|
||
link: https://www.spinnaker.io/
|
||
strimzi:
|
||
name: Strimzi
|
||
link: https://strimzi.io/
|
||
elasticsearch:
|
||
name: Elastic Search
|
||
link: https://www.elastic.co/
|
||
azurecosmos:
|
||
name: Azure Cosmos
|
||
link: https://docs.microsoft.com/en-us/azure/cosmos-db/introduction
|
||
azuretablestorage:
|
||
name: Azure Table Storage
|
||
link: https://docs.microsoft.com/en-us/azure/cosmos-db/table-storage-overview
|
||
sqlite:
|
||
name: SQLite
|
||
link: https://www.sqlite.org/index.html
|
||
clair:
|
||
name: Clair
|
||
link: https://github.com/coreos/clair
|
||
cloudflare:
|
||
name: Cloudflare
|
||
link: https://www.cloudflare.com
|
||
openfaas:
|
||
name: OpenFaaS
|
||
link: https://www.openfaas.com/
|
||
minio:
|
||
name: Minio
|
||
link: https://min.io/
|
||
dart:
|
||
name: dart
|
||
link: https://dart.dev/
|
||
docker:
|
||
name: Docker
|
||
link: https://www.docker.com/
|
||
bosun:
|
||
name: Boomerang Bosun
|
||
link: https://www.useboomerang.io/
|
||
php:
|
||
name: PHP
|
||
link: https://www.php.net/
|
||
gradle:
|
||
name: Gradle
|
||
link: https://gradle.org/
|
||
jenkins:
|
||
name: Jenkins
|
||
link: https://jenkins.io/
|
||
sysdigsecure:
|
||
name: Sysdig Secure
|
||
link: https://sysdig.com/products/kubernetes-security/
|
||
pomerium:
|
||
name: Pomerium
|
||
link: https://www.pomerium.io/
|
||
coredns:
|
||
name: CoreDNS
|
||
link: https://coredns.io/
|
||
gluu:
|
||
name: Gluu Gateway
|
||
link: https://www.gluu.org/
|
||
nodejsexpress:
|
||
name: Node.JS express
|
||
link: https://expressjs.com/
|
||
aspdotnetcore:
|
||
name: ASP .NET core
|
||
link: https://docs.microsoft.com/en-us/aspnet/core/
|
||
helm:
|
||
name: Helm
|
||
link: https://helm.sh/
|
||
flask:
|
||
name: Flask
|
||
link: https://flask.palletsprojects.com/
|
||
opal:
|
||
name: OPAL
|
||
link: https://opal.ac
|
||
sphinx-doc:
|
||
name: Sphinx
|
||
link: https://www.sphinx-doc.org
|
||
bottle:
|
||
name: Bottle
|
||
link: https://bottlepy.org
|
||
spiffe:
|
||
name: SPIFFE
|
||
link: https://spiffe.io
|
||
spire:
|
||
name: SPIRE
|
||
link: https://spiffe.io
|
||
google-calendar:
|
||
name: Google Calendar
|
||
link: https://calendar.google.com/
|
||
apache-apisix:
|
||
name: Apache APISIX
|
||
link: https://apisix.apache.org/
|
||
kubescape:
|
||
name: Kubescape
|
||
link: https://github.com/kubescape/kubescape
|
||
i2scim:
|
||
name: i2 SCIM Server
|
||
link: https://i2scim.io
|
||
graphene-graphql:
|
||
name: Graphene GraphQL
|
||
link: https://graphene-python.org
|
||
styra-das:
|
||
name: Styra DAS
|
||
link: https://www.styra.com
|
||
kustomize:
|
||
name: Kustomize
|
||
link: https://kustomize.io
|
||
toml:
|
||
name: TOML
|
||
link: https://toml.io
|
||
groovy:
|
||
name: Groovy
|
||
link: https://groovy-lang.org
|
||
kotlin:
|
||
name: Kotlin
|
||
link: https://kotlinlang.org
|
||
linux:
|
||
name: Linux
|
||
link: https://www.kernel.org
|
||
ebpf:
|
||
name: eBPF
|
||
link: https://ebpf.io
|
||
git:
|
||
name: Git
|
||
link: https://git-scm.com
|
||
pre-commit:
|
||
name: pre-commit
|
||
link: https://pre-commit.com
|
||
rekor:
|
||
name: rekor
|
||
link: https://github.com/sigstore/rekor
|
||
open-policy-registry:
|
||
name: Open Policy Registry
|
||
link: https://www.openpolicyregistry.io
|
||
aserto:
|
||
name: Aserto
|
||
link: https://www.aserto.com
|
||
topaz:
|
||
name: Topaz
|
||
link: https://www.topaz.sh
|
||
emissary-ingress:
|
||
name: Emissary-Ingress
|
||
link: https://github.com/emissary-ingress/emissary
|
||
magda:
|
||
name: Magda
|
||
link: https://github.com/magda-io/magda
|
||
google-kubernetes-engine:
|
||
name: Google Kubernetes Engine
|
||
link: https://cloud.google.com/kubernetes-engine/
|
||
sansshell:
|
||
name: Sansshell
|
||
link: https://github.com/Snowflake-Labs/sansshell
|
||
nginx:
|
||
name: Nginx
|
||
link: https://nginx.org/
|
||
pulumi:
|
||
name: Pulumi
|
||
link: https://www.pulumi.com/
|
||
alfred:
|
||
name: alfred
|
||
link: https://github.com/dolevf/Open-Policy-Agent-Alfred
|
||
rond:
|
||
name: Rönd
|
||
link: https://rond-authz.io/
|
||
ssikit:
|
||
name: ssikit
|
||
link: https://walt.id/ssi-kit
|
||
graphql:
|
||
name: graphql
|
||
link: https://graphql.org/
|
||
ansible:
|
||
name: Ansible
|
||
link: https://www.ansible.com
|
||
circleci:
|
||
name: CircleCI
|
||
link: https://circleci.com
|
||
terraform-cloud:
|
||
name: Terraform Cloud
|
||
link: https://cloud.hashicorp.com/products/terraform |