Philipp Krenn - Open Policy Agent: security for cloud natives and everyone else

Learn how Open Policy Agent (OPA) enables secure cloud-native applications and traditional systems with rego rules for infrastructure and security policies, automated testing, and deployment.

Key takeaways
  • Rego rules can be used to encode infrastructure and security policies, and OPA (Open Policy Agent) provides a platform for testing and deploying these rules.
  • Rego rules can be used to check against different types of data, including infrastructure configuration and application state.
  • OPA provides a way to test and deploy Rego rules, allowing for automated enforcement of security and infrastructure policies.
  • Rego rules can be used to express complex policies, such as checking the origin of a Docker image or the cost center label of a Kubernetes resource.
  • OPA provides a way to test Rego rules against a given input, and to debug and fix any errors that are found.
  • Rego rules can be used to check against a variety of different data sources, including Kubernetes, Elasticsearch, and Prometheus.
  • OPA provides a way to integrate Rego rules with existing tooling and workflows, such as Ansible and Terraform.
  • Rego rules can be used to encode security policies that are more flexible and expressive than traditional rule-based systems.
  • OPA provides a way to test and deploy Rego rules, allowing for automated enforcement of security and infrastructure policies.
  • Rego rules can be used to check against different types of data, including infrastructure configuration and application state.
  • OPA provides a way to debug and fix any errors that are found in Rego rules, making it easier to use Rego rules in production environments.
  • Rego rules can be used to express complex policies, such as checking the origin of a Docker image or the cost center label of a Kubernetes resource.
  • OPA provides a way to integrate Rego rules with existing tooling and workflows, such as Ansible and Terraform.