AI agents should not have risky HTTP configurations
Part of Maester · Copilot Studio · Agents · All checks
Invoke-Maester -TestId MT.1115Overview
Section titled “Overview”AI agents should not use risky HTTP configurations.
Agents with HTTP request nodes in topics connecting to non-standard ports or using plain HTTP (instead of HTTPS) may be misconfigured or could indicate data exfiltration or command-and-control communication channels.
How to fix
Section titled “How to fix”Review the HTTP request nodes in each flagged agent’s topics. Ensure all HTTP requests use HTTPS on standard port 443. Replace direct HTTP calls with Power Platform connectors where possible, as connectors provide built-in governance and DLP policy enforcement.
Learn more: Configure data policies for agents
Details
Section titled “Details”Every attribute of this check
| Field | Value |
|---|---|
| Test ID | MT.1115 |
| Severity | Medium |
| Suite | Maester |
| Product | Copilot Studio |
| Feature | Agents |
| Area | AI and agents |
| Resource type | Agent |
| User impact | Low |
| Implementation cost | Medium |
| MITRE ATT&CK | T1571 Non-Standard Port, T1048 Exfiltration Over Alternative Protocol, T1071.001 Web Protocols |
| Supports controls | nist-800-53-r5:SC-7 |
| PowerShell test | Test-MtAIAgentRiskyHttpConfig |
| Services | Graph |
Source
Section titled “Source”About this check
- Severity
- Medium
- Effort to fix
- Medium
- Impact on users
- Low
- Product
- Copilot Studio
- Feature
- Agents
- Area
- AI and agents
- Suite
- Maester