Notifications
Clear all
Topic starter
11/08/2026 3:16 pm
TL;DR: Microsoft’s July 27, 2026 security portfolio update centers on agentic harnesses, including MAI-Cyber-1-Flash, MDASH, and Project Perception, which let models execute multi-step work with tools and loops rather than only answer questions, according to Noma Security. The governance gap is that prompt-layer safety is not enough when agents can issue repeated tool calls before humans can review them.
NHIMG editorial — based on content published by Noma Security: Microsoft’s agentic security harness and what it means for defenders
By the numbers:
- 100 agents work in parallel and in sequence, n sequence inside MDASH, each handling part of a scanning workload with a specialized model doing the reasoning at each step.
- Project Perception enters public preview on August 3, 2026, after being announced on July 27, 2026.
Questions worth separating out
Q: How should security teams implement agentic security without losing control?
A: Start in observe mode, limit the agent to investigation support, and gate any response action behind human approval.
Q: Why do agentic harnesses create more risk than a single LLM prompt?
A: A single prompt returns text, but an agentic harness can choose tools, repeat actions, and continue until a goal is met.
Q: What breaks when remediation and detection sit inside the same agent workflow?
A: When detection and remediation are merged, the same workflow can identify a problem and immediately change the environment without a separate control gate.
Practitioner guidance
- Define harness-level approval gates Require explicit human approval before any agent can modify configuration, trigger remediation, or open new execution paths in production.
- Scope each agent to a minimal tool set Assign only the APIs, scanners, and data sources required for one task, then validate those permissions at runtime rather than only at configuration time.
- Log every tool call and action chain Capture the full sequence of queries, commands, retries, and responses so operators can reconstruct agent behaviour after the fact.
What's in the full article
Noma Security's full article covers the operational detail this post intentionally leaves for the source:
- A deeper explanation of how Microsoft’s agentic security harness works across MDASH and Project Perception.
- The article’s own breakdown of MAI-Cyber-1-Flash and the CyberGym benchmark context.
- Additional commentary on what defenders should evaluate when agentic tooling runs inside existing security platforms.
- The source piece also expands on how Noma Security interprets the supervision problem for agent behavior.
👉 Read Noma Security’s analysis of Microsoft’s agentic security harness →
Agentic security harnesses: are your controls keeping up?
Explore further
11/08/2026 3:29 pm
Agentic security harnesses collapse the assumption that models only generate output. Security programmes built around prompt governance assume the model stops after responding, but a harness gives it tools, timing, and repetition. That changes the governance problem from content safety to runtime authority. Practitioners need to treat the harness as an identity-bearing execution layer, not just an interface.
A few things that frame the scale:
- 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, according to The State of Non-Human Identity Security.
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, compared to nearly 1 in 4 for securing human identities.
A question worth separating out:
Q: How can organisations tell whether an agent has exceeded its intended scope?
A: Organisations should look for cross-system action chains, unusual delegation hops, and high-impact actions that were never intended by the originating request. If an agent can move from read access to configuration change to deployment or export without a separate control point, its effective scope has expanded beyond what the initial entitlement suggested.
👉 Read our full editorial: Microsoft’s agentic security harness raises new governance gaps
