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.
Editorial analysis by NHI Mgmt Group, based on content published by Noma Security: “What Microsoft MDASH and Project Perception Mean for Defenders”.
Key questions
Q: What breaks when agentic security systems are governed like chatbots?
A: The control model breaks at runtime.
Q: Why do agentic harnesses create governance gaps in enterprise environments?
A: Harnesses solve runtime execution, not enterprise governance.
Q: How do security teams know if a workflow is behaving outside its intended boundary?
A: They compare observed behaviour against a known baseline for the workflow, including destinations, processes, and registration activity.
Practitioner guidance
- Define tool-scoped agent permissions Limit each agent to the smallest set of tools, datasets, and actions needed for its task.
- Insert human approval gates for high-consequence actions Require approval before configuration changes, remediation steps, or any action that can alter production systems.
- Log every agent action and tool call Capture the full sequence of queries, API calls, and outputs so operators can reconstruct what happened and why.
Bottom line: Agentic security harnesses change the problem from content safety to runtime governance, because the system can now act through tools rather than only answer questions.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/08/2026 3:29 pm
Agentic security harnesses shift the control problem from model output to runtime authority. A model that only answers questions can be governed like a content system. A harness that can call tools, loop, and coordinate action has to be governed like an executing identity with scope, traceability, and stop conditions. The practical implication is that security teams must treat agent runtime as a privileged control plane, not a chatbot wrapper.
A question worth separating out:
Q: What should teams do after a defensive agent changes production systems?
A: Treat it as a governance event first and a technical event second. Reconstruct the full action chain, verify which permissions enabled the change, and determine whether the agent role had authority to act without explicit approval. The aim is to contain the authority path, not just the technical symptom.
👉 Read our full editorial: Microsoft’s agentic security harness raises new governance gaps