AI runtime security vs guardrails vs red teaming
Guardrails are policies on what a model may say or do. Runtime security enforces policies and more while a system runs. Red teaming tests before launch and finds gaps. Sources read on 16 Nov 2026 show guardrails often sit inside runtime tools, and red teaming feeds both.
Facts read on .
Are guardrails the same as runtime security?
Guardrails are one mechanism that runtime security uses, so they overlap but are not the same. A guardrail checks a prompt or response against a policy. Runtime security also covers agent tool calls, machine actions, logging and response.
NVIDIA's NeMo Guardrails names five rail types: input, dialog, retrieval, execution and output. Input rails can reject or alter user input, and output rails can reject or alter what the model returns. Execution rails apply to the inputs and outputs of tools the model calls.
Sources: NVIDIA NeMo Guardrails.
Where does red teaming fit?
Red teaming fits before release and on a schedule, because it tests a system and reports what got through. It does not stop anything at runtime.
Cisco shows the split in its own offer: AI Defense includes a free Explorer Edition described as red teaming, while the paid runtime protection places guardrails in the network. Findings from testing become runtime policy.
Sources: Cisco AI Defense.
What does each one produce?
Guardrails produce policy decisions per request. Runtime security produces decisions plus a log of allowed and blocked actions. Red teaming produces a report of attack paths that succeeded.
MITRE ATLAS gives a shared vocabulary of adversary tactics against AI systems, useful for mapping red team findings to runtime rules. Zenity says its detections map to OWASP LLM and MITRE ATLAS.
Sources: MITRE ATLAS; Zenity AI detection and response.
Who is responsible for each control?
Guardrails often sit with the application team, runtime security with the security team and red teaming with either. Pick one accountable team per control, because a guardrail changed by an application release can silently weaken a security rule.
A cloud provider's guardrail, such as Amazon Bedrock Guardrails, can be applied to a model call or called on its own through an API without invoking a model, which lets security review the policy separately.
Sources: Amazon Bedrock Guardrails.
How should you sequence them?
Start with red teaming to learn what your system is exposed to, put guardrails on the model path, then add runtime enforcement where actions have side effects.
NIST AI 600-1, the AI risk profile, treats these as risk management actions across the lifecycle, not one product. Re-test after each policy change.
Sources: NIST AI 600-1, AI Risk Management Framework profile.
What do the three miss alone?
Guardrails alone miss agent actions, because a text policy cannot see a shell command that runs on a machine. Runtime security alone has no view of weaknesses nobody has tried yet. Red teaming alone gives a snapshot that ages with each model or prompt change.
Treat them as a loop: test, set policy, enforce, log, then test again with what the logs showed.
Sources: NVIDIA NeMo Guardrails; Cisco AI Defense.
What should you ask a vendor about each?
Ask what policies come built in, what you can write yourself, and whether findings from testing can be loaded as runtime rules. Ask whether the product only detects or also blocks.
Where the answer is not public, expect the score to reflect that: a claim without a public source is capped by this site's method.
How do you keep them consistent?
Keep one written policy that all three read: what the system may say, what it may do and what it may touch. Guardrail rules, runtime rules and red team test cases should each trace to a line in that policy.
When a red team finds a gap, change the policy first, then the rules, then re-test. A fix made only in a guardrail can leave the agent action path open.
Sources
- NVIDIA NeMo Guardrails (github.com), read
- Cisco AI Defense (cisco.com), read
- MITRE ATLAS (atlas.mitre.org), read
- Zenity AI detection and response (zenity.io), read
- Amazon Bedrock Guardrails (docs.aws.amazon.com), read
- NIST AI 600-1, AI Risk Management Framework profile (nvlpubs.nist.gov), read