CtrlK
BlogDocsLog inGet started
Tessl Logo

nicholasjackson/opa-rego-language

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.

99

1.19x

Quality

Pending

Does it follow best practices?

Impact

99%

1.19x

Average score across 31 eval scenarios

SecuritybySnyk

Pending

The risk profile of this skill

Overview
Eval results
Files

task.mdevals/scenario-30/

Regal: Naming Conventions — RBAC Policy

Write a Rego policy in the package rbac.authz that implements role-based access control for API endpoints. Users have roles stored in data.user_roles. Roles have permissions stored in data.role_permissions. Allow access when the user's role grants the required permission for the requested endpoint and method.

Input

{
  "user": "alice",
  "method": "GET",
  "path": "/api/reports"
}

Data

{
  "user_roles": {"alice": "engineer", "bob": "admin"},
  "role_permissions": {
    "engineer": ["reports:read"],
    "admin": ["reports:read", "reports:write", "users:read", "users:write"]
  }
}

Expected behaviour

  • Alice (engineer) can GET /api/reports (has reports:read) — allow
  • Alice (engineer) cannot POST /api/reports (no reports:write) — deny
  • Bob (admin) can POST /api/reports — allow
  • Unknown user with no role — deny

README.md

rules.md

tile.json