Microsoft open-sources RAMPART, Clarity

Microsoft released two open-source tools for AI agent safety this week, adding developer-facing software to a broader push to secure systems that can take actions across email, code, records and other enterprise workflows. The tools, RAMPART and Clarity, were introduced in a Microsoft Security Blog post dated May 20 and were made available through public GitHub repositories. The release is aimed at a specific problem Microsoft described in its post: enterprise AI systems are moving beyond question answering into retrieving data, writing code and acting on a user’s behalf across connected systems. Microsoft said that shift creates a different development and security workflow, one that needs testing before deployment and controls that can be repeated as code changes. (microsoft.com) ### What, exactly, is RAMPART? RAMPART stands for Risk Assessment and Measurement Platform for Agentic Red Teaming, according to Microsoft’s GitHub repository and Microsoft’s launch post. The company describes it as a pytest-native safety and security testing framework for agentic AI applications. The GitHub documentation says developers write tests that attack or probe an agent, while RAMPART orchestrates the interaction, evaluates the outcome and reports the results. (microsoft.com) Microsoft said the framework is meant to cover adversarial attacks, benign failures and a range of harm categories, with evaluation-driven assertions that fit into existing pytest workflows and CI pipelines. (github.com) The Register, which reported the release on May 21, said RAMPART is built on Microsoft’s earlier open-source PyRIT tooling. Microsoft’s own post presents RAMPART as part of an effort to turn red-team findings into repeatable engineering checks rather than one-off exercises. ### What is Clarity supposed to do before code gets written? (github.com) Clarity is positioned earlier in the workflow. Microsoft’s blog says the tool is designed to help teams check software-engineering assumptions before implementation by asking structured questions that product managers, architects and safety engineers would ask. (theregister.com) The `microsoft/clarity-agent` repository says Clarity helps “distill intent,” “surface failure modes,” and “keep the plan current.” It creates a `.clarity-protocol/` directory inside a project repository with human-readable files that capture the problem, proposed solution, failure analysis and decisions, according to the GitHub materials. Microsoft said that protocol can become a shared artifact for a team and can also be exported into review documents. (microsoft.com) In one GitHub evaluation case, the project is framed around pushing back on vague requests to “add AI” by probing for the user problem, data, affected users and whether non-AI approaches might work. (github.com) ### Why is Microsoft pairing these two tools? Microsoft presented the two projects as covering different points in the agent development cycle. The company said Clarity is intended to sharpen intent and expose assumptions before implementation, while RAMPART is intended to test the resulting system continuously once teams are building and changing it. (microsoft.com) InfoWorld, describing the release, said Microsoft was trying to make agent safety a continuous engineering practice. That matches Microsoft’s own wording that incident response and red teaming should become repeatable parts of development rather than ad hoc scrambles after deployment. ### Where can developers find them now? (microsoft.com) GitHub repositories for `microsoft/RAMPART` and `microsoft/clarity-agent` are already public, with documentation, source code and setup instructions available. Microsoft’s May 20 blog post says both tools are available now, and third-party reports from The Register and others followed on May 21. Microsoft’s next visible step is likely to play out in those repositories. (infoworld.com) The RAMPART project already shows active documentation updates, and the Clarity repository includes evaluation cases, protocol tooling and developer utilities that Microsoft says teams can use and extend from GitHub today. (github.com 1) (github.com 2)