canonical: https://jentic.com/apis/mitigant.io/mitigant # Mitigant Cloud Security API Jentic publishes the only available OpenAPI specification for Mitigant Cloud Security API, keeping it validated and agent-ready. Mitigant (formerly Resility) is a cloud infrastructure security platform that runs attack surface management, cloud security posture assessment, and chaos-style attack simulations across AWS, Azure, and GCP environments. The API exposes 20 endpoints for managing cloud accounts, scans, findings, assets, attack simulations, dashboard metrics, and compliance reports - designed for embedding cloud security checks into automation pipelines. ## For AI agents Manage cloud accounts, run security scans, list findings and assets, and trigger attack simulations across AWS, Azure, and GCP through the Mitigant cloud security platform. ## Scope Does not handle endpoint detection, application code scanning, or SIEM event ingestion - use for cloud account posture, findings, assets, and attack simulation only. ## Capabilities - Connect AWS, Azure, and GCP accounts for posture scanning - Trigger and monitor cloud security scans on demand - List and filter findings by severity, asset, or compliance control - Inventory cloud assets discovered during scans - Run attack simulations against connected cloud environments - Generate compliance reports against frameworks like CIS and SOC 2 - Pull dashboard metrics for security posture trending ## Use cases ### Continuous Cloud Posture Monitoring Integrate Mitigant into a security operations workflow that triggers scans on a schedule and pulls new findings into the SOC ticketing system. The API exposes scan creation, status, and findings retrieval so a script can run nightly, route critical findings to engineers, and close out resolved items based on subsequent scan results. Example prompt: Trigger a scan on cloud account {accountId} via POST /scans, poll status, and post any critical findings to the SOC channel ### Attack Surface Discovery Use the assets endpoints to enumerate the publicly exposed surface of a multi-cloud estate after an account is connected. The discovered assets are correlated with findings so security teams can see which exposed resources have outstanding misconfigurations or vulnerabilities, prioritising remediation by blast radius rather than raw severity. Example prompt: Call GET /assets filtered by exposed=true and intersect with /findings to list public assets carrying critical findings ### Chaos-Style Attack Simulation Run controlled attack simulations against staging cloud environments to validate detection and response controls. The simulation endpoints orchestrate techniques like over-permissive IAM policy abuse or storage exfiltration patterns and report whether existing alarms or guardrails fired, so red-team and detection-engineering exercises can be automated rather than manual. Example prompt: Trigger an attack simulation on staging account {accountId} and capture the simulation result for the detection-engineering report ### Agent-Driven Cloud Security Triage An agent discovered through Jentic queries Mitigant findings, opens tickets in the engineering tracker for unresolved critical items, and re-checks the next day to confirm closure. Jentic isolates the bearer token in its credential vault so the agent only invokes scoped operations rather than handling raw secrets. Example prompt: Use Jentic to find Mitigant's findings list operation, retrieve open critical findings, and open a tracker ticket for each one not already triaged ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/cloud-accounts` | List connected cloud accounts | | POST | `/scans` | Trigger a security scan | | GET | `/findings` | List security findings | | GET | `/assets` | List discovered cloud assets | | GET | `/scans/{scanId}` | Get scan status | | GET | `/findings/{findingId}` | Get details for a specific finding | ## Key resources - **Cloud Accounts** — Connected AWS, Azure, and GCP accounts - **Scans** — Posture and vulnerability scan jobs - **Findings** — Misconfigurations and vulnerabilities discovered - **Assets** — Inventory of discovered cloud resources - **Attack Simulations** — Controlled adversary simulation jobs - **Compliance** — Compliance benchmark scoring and reports - **Dashboard** — Aggregated security posture metrics ## Why Jentic - **Setup:** Wiring the Mitigant Cloud Security API by hand means handling its bearer auth, tracking scan and finding ids across calls, and plumbing posture and asset reads yourself. Through Jentic you install once, import the Mitigant Cloud Security API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Mitigant puts the scan and finding ids in the URL path (`/scans/{scanId}`, `/findings/{findingId}`), so a rule can pin your agent to read-only posture work: it can list cloud accounts, assets, and findings and inspect one scan. You choose the operations it may call, so starting an attack simulation with a new scan is not included unless you add it. - **Credential handling:** Your Mitigant token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list cloud security findings' or 'check an account's posture', and Jentic returns the matching Mitigant operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Snyk API** — Application and cloud security scanning - **Prisma Cloud CSPM API** — Cloud security posture management from Palo Alto Networks - **Rapid7 InsightVM API** — Vulnerability management for endpoint and on-premise assets ## FAQ ### Why is there no official OpenAPI spec for Mitigant Cloud Security API? Mitigant does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mitigant Cloud Security API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Mitigant Cloud Security API use? The API uses bearer token authentication. The token is generated from the Mitigant console and passed in the Authorization header. Through Jentic the bearer is held in the credential vault and injected at execution time so agent code never sees the raw token. ### Can I trigger a scan and retrieve findings with the Mitigant API? Yes. Call POST /scans with the cloud account identifier to start a scan, poll GET `/scans/{scanId}` for status, then call GET /findings filtered by the resulting scan to retrieve the security findings. ### What are the rate limits for the Mitigant Cloud Security API? Mitigant applies per-tenant rate limits that depend on your subscription tier. Scan creation and attack simulation calls are stricter than findings reads. Check your Mitigant console for current numeric limits before automating large batches. ### How do I list open critical findings through Jentic? Search Jentic for list mitigant findings, load the schema for GET /findings, and execute with the severity filter set to critical. The structured response can be passed directly to a ticketing integration. ### Does the Mitigant API support attack simulation? Yes. The Attack Simulations endpoints orchestrate controlled adversary techniques against connected cloud accounts and report whether expected detections fired. Use them on staging accounts to validate detection and response controls. ### Can I limit what my agent is allowed to do with the Mitigant Cloud Security API? Yes. Because you run Jentic One yourself, your own rules decide which Mitigant operations the agent may call and which credentials it may use. Since Mitigant carries scan and finding ids in the URL path (GET `/scans/{scanId}`, GET `/findings/{findingId}`), you can pin the agent to read-only posture work, letting it list cloud accounts, list assets, list findings, and inspect a single scan. Write actions such as triggering a new scan via POST /scans or starting an attack simulation are excluded unless you explicitly add them.