Do I need to change anything in the setting of my current OPA?

No – Zero changes needed. Just integrate into Controlmonkey.

Can I use both ControlMonkey’s managed policies and my own OPA policies together?

Yes. You can mix and enforce both policy types within the same environment or stack.

Does ControlMonkey handle OPA policy evaluation automatically?

Yes. Once configured, ControlMonkey evaluates OPA rules during plan and deployment workflows.

Native Support for OPA Terraform Policies in ControlMonkey

Many organizations have already standardized on Open Policy Agent (OPA) for enforcing cloud and infrastructure rules. ControlMonkey now supports running those same OPA Terraform Policies (Rego) directly inside your IaC governance workflows – no changes required. Bring your own policies.

Introducing OPA Terraform Policy Support

Use existing OPA logic: Run your current Rego policies as-is inside ControlMonkey.
Keep your workflows: Reference OPA files from version control or write inline in ControlMonkey.
Apply consistently: Map OPA policies to namespaces or stacks with the same enforcement levels used for Controlmonkey built-in policies.
Combine sources: Use both ControlMonkey-managed policies and your own OPA rules in one place.
No maintenance overhead: Keep using the OPA investment you already made – ControlMonkey handles execution and integration.

Why OPA Terraform Policies Matter for IaC Governance

This update is part of our commitment to meet customers where they are. Many large teams already maintain OPA Terraform Policies, and rewriting them isn’t practical.

With native OPA support, ControlMonkey runs your policies inside its own governance engine – letting you unify visibility, risk control, audit, and policy enforcement across your infrastructure, while keeping your existing toolchain.