Back to Threat Intel
sourcearticleAgent: unspecified

Microsoft introduces RAMPART and Clarity for agent development safety

Microsoft says agentic AI has shifted from generating text to taking actions across connected systems, and introduces RAMPART for CI-friendly agent safety tests plus Clarity for documenting design assumptions and failure analysis.

openclawagentic-aiprompt-injectionred-teamingcidetection

Date

May 20, 2026

First Seen

May 20, 2026

Last Reviewed

May 21, 2026

Publisher

Microsoft Security Blog

Source Type

article

View source

Get email updates

Get reviewed Armorer threat-intel updates when new findings are published.

Source Summary

What It Contains

Microsoft says agentic AI has shifted from generating text to taking actions across connected systems, and introduces RAMPART for CI-friendly agent safety tests plus Clarity for documenting design assumptions and failure analysis.

Extracted Claims

  • Microsoft frames modern enterprise AI agents as systems that may access email, retrieve CRM records, write and execute code, and take actions across connected systems.
  • RAMPART is an open-source, Pytest-native framework for encoding adversarial and benign agent safety scenarios as repeatable tests that can run in CI.
  • RAMPART's mature coverage focuses on cross-prompt injection, where untrusted data from documents, email, tickets, web pages, or other sources indirectly manipulates agent behavior.
  • RAMPART evaluators are intended to inspect what the agent does, including tool invocation, side effects, and action boundaries.
  • Microsoft says incident response should become reproducible and mitigations verifiable by turning failures and red-team findings into runnable engineering assets.
  • Clarity records problem statements, solution rationale, failure analysis, and decisions in repo-local markdown artifacts for review and later reassessment.

Evidence Quality

Primary Microsoft Security Blog announcement from Microsoft's AI Red Team. Strong evidence for a control pattern and open-source tooling direction, but it is not a vulnerability advisory or proof that the tools prevent all agent failures.

Follow-Up

  • Track adoption experience and limitations for Microsoft RAMPART in real OpenClaw-style local agent workflows.
  • Consider adding a separate repository source for RAMPART if the project publishes security test packs, releases, or implementation guidance useful to operators.