Servers, appliances and logs in your own data centres are worked the same way as cloud and SaaS tools. Analysts investigate, hunt, manage rules and respond across both from one place, and nobody has to consolidate anything first.
A small connector runs inside your network and opens a scoped, read-only path to the on-prem systems you choose. During each task Mitigate pulls from those systems and from your connected cloud and SaaS tools at once, joins the evidence, and runs any approved response through the tool that owns it. Write access is granted per action. Logs stay where they are, in the format they are already in.
A proof of concept with Mitigate is scored on these measures, against your own alerts and your own tools.
| No. | Measure | Definition |
|---|---|---|
| 01 | Hours to first query | Median time from installing the connector to a validated query against each on-prem source. |
| 02 | Sources reached | Sources on the required list, whether on-prem, cloud or SaaS, that answered queries. |
| 03 | Hybrid cases | Investigations that closed using evidence from both on-prem and cloud systems. |
| 04 | Actions completed | Approved responses that finished successfully in each connected environment. |
| 05 | Engineering hours | Total engineer time spent connecting and checking every source. |
| 06 | Alert to verdict | Median time between an alert firing and a verdict backed by evidence. |
Install the connector, choose what it may read, and run a case that spans server racks and cloud accounts.