Rego is the declarative policy language used by Open Policy Agent (OPA). This tile covers writing and testing Rego policies for Kubernetes admission control, Terraform and infrastructure-as-code plan validation, Docker container authorization, HTTP API authorization, RBAC and role-based access control, data filtering, metadata annotations with opa inspect, and OPA policy testing with opa test.
96
94%
Does it follow best practices?
Impact
97%
1.18xAverage score across 32 eval scenarios
Low
Low-risk findings worth noting
Write a Rego policy in the package api.limits that returns a max_requests value based on the user's subscription tier stored in data.user_tiers. Use a default declaration for the fallback value (10 requests). Override for "standard" tier (100 requests) and "premium" tier (1000 requests). The default must be declared at the top of the rule group, not at the bottom.
{"user_id": "alice"}{
"user_tiers": {
"alice": "premium",
"bob": "standard"
}
}alice (premium) → max_requests = 1000bob (standard) → max_requests = 100carol (no tier / unknown) → max_requests = 10 (default).tessl-plugin
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
skills
rego-domain-reference
references