Agentic Security Could Strengthen Platforms—If They Remain Open
6 companies named across 9 categories, one of 337 articles referencing Microsoft. Previous coverage: Xage Security expands Critical Asset Protection to cover digital assets (Aug 2026).
Companies mentioned
Best suited for
- Seniority
- EVP / SVP / VP / AVP
- Job function
- Chief Information Security Officer
- Persona
- Security Architect
- Buyer role
- Decision Maker / Budget Holder
- Decision stage
- How to start
- Adoption curve
- Early Adopters
- Technology maturity
- Market Correction
- Industry
- Information Technology / Software & Services / IT Services / Cloud Services
Our classification, not the publisher's statement. Best suited for, not only for.
Microsoft’s agentic security push centers on coordinating security context, models, and enforcement across its estate, while highlighting the tension between higher automation and tighter vendor platform alignment for enterprise customers.
Technology shown at the launch
Microsoft described Perception as a system that coordinates security context, models, specialized agents, and enforcement mechanisms across its security portfolio, with red agents testing environments, blue agents investigating threats, and green agents recommending or executing remediation.
Microsoft also outlined MDASH to extend discovery into source-code vulnerability work and developer workflows, plus MAI-Cyber-1-Flash for part of that work and Security FORGE Labs for more autonomous vulnerability discovery and remediation.
Control-plane integration and automation workflow
The report frames Microsoft’s advantage as the number of enterprise control planes it can connect, citing Defender for endpoint and security-operations context, Entra for identity information, and Azure for cloud context and enforcement.
It adds that GitHub and Azure DevOps connect to source code and development workflows, enabling an agent to move from threat-intelligence questions to investigation, identify exposed identities and assets, apply temporary controls, and propose code fixes.
Enforcement points and temporary controls
The article links temporary controls to network security enforcement points, including firewalls, web application firewalls, workload controls, and other enforcement locations that could provide machine-generated shielding as application teams develop and validate permanent fixes.
Microsoft’s demonstration included custom detections, posture changes, application protections, and proposed code remediation tied to this control workflow.
Vendor competition and ecosystem reach
The note says other vendors pursue similar strategies by connecting security operations to other parts of the stack, including network enforcement and application or cloud security, with examples cited as Palo Alto Networks, CrowdStrike, and Google.
It argues that each vendor benefits when agents use the vendor’s platform for context, decisions, and coordination, which can increase pressure for security platform consolidation.
Limits for multivendor enterprises
The article states that most large enterprises will remain multivendor and may use different vendors across identity, endpoints, cloud, application security, and data security.
It warns that an agent that reasons accurately only inside its own vendor environment can create an incomplete view of risk, and it notes that cross-environment normalization and coordination remain required.
Openness requirements for data and interoperability
Microsoft acknowledged that third-party data quality, normalization, permissions, and enforcement remain difficult, and it said it is exploring approaches such as data federation for Perception.
The note says Perception’s practical openness needs demonstration in customer environments, and it also says connectors or open agent protocols do not ensure reliable interoperability because vendors must show correct interpretation of external evidence, attribution, permission handling, and safe action execution.
Model certification and configuration constraints
The article says Microsoft expects to certify supported configurations in a multi-model architecture rather than permit unrestricted model substitution.
It adds that customers may require different models for reasons such as sovereignty, cost, availability, or organizational policy, and that platforms need to balance customer model choice with risks from untested combinations.
Analyst outlook
The report frames the market as a contest between integrated performance and ecosystem reach, stating broad platforms may benefit when their native products dominate customer environments.
It concludes that openness matters more when agents depend on external data sources and attempt actions across competing control planes, and it emphasizes the neutrality requirement that agentic security cannot become an enterprise operating layer unless it works across the enterprise that exists.
This Analyst Signals brief reflects a neutral, fact-based summary of the original research note.
Blog post, originally published at delloro.com.