policy as code
AI security interview questions tagged policy as code, across every topic.
5 questions · 0 unlocked for you
Concepts behind "policy as code"
Explanations of the mechanisms these questions rely on.
Foundational
Access-Control Models: RBAC, ABAC and ReBAC in DepthEvery authorization model answers one question: may this subject perform this action on this resource, in this context? RBAC answers with roles and is easy to review but explodes when roles start encoding objects or context. ABAC evaluates attributes and is expressive but hard to audit. ReBAC follows relationships such as owner, member and parent folder, as Google's Zanzibar does at millions of checks per second. Real systems combine them, and the hard parts are deny semantics, list filtering, stale permissions and agents acting for users. Identity & Access
Foundational
Agent and MCP Gateways ExplainedAn agent or MCP gateway sits between agent runtimes and the tools or MCP servers they call. Because each call passes through it, it can authenticate the agent, apply default-deny policy to the tool name and arguments, swap in a credential issued for that tool, pin approved tool definitions, enforce budgets, route high-impact calls for approval and log every decision. It cannot control traffic that does not pass through it, cannot tell whether an allowed call serves the user's goal, and cannot clean instructions out of the data it relays. It works only alongside per-agent identity, sandboxing, egress control and authorisation inside the tools. Agent & MCP Security