Introduction
Field Effect prioritizes Field Effect-hosted virtual MDR SIEM devices. Field Effect hosts these virtual MDR SIEMs in a number of Azure regions worldwide, including:
- For clients in the USA: eastus2, centralus, westus2
- For clients in Canada: canadaeast, canadacentral
- For clients in the UK: uksouth
- For clients in Asia: eastasia
- For clients in Oceania: ustraliaeast
In some situations, you may require a physical MDR SIEM device on-site in your network; you can discuss these with your Sales representative. On relatively rare occasions, clients need an on-site MDR SIEM device but cannot host a physical one. In such cases, it is possible for a client to self-host an MDR SIEM. More commonly, clients may need to self-host virtual network sensors.
The following table provides the minimum system requirements for self-hosted MDR SIEMs or network sensors. MDR SIEM devices receive and analyze all traffic from the network they're deployed in, along with traffic that network sensors and endpoint agents send. For more on this, see How Field Effect Works.
| Virtual MDR SIEM device | Virtual Network Sensors | |
|---|---|---|
| Storage | 1TB + 512GB, capable of providing at least 1024 IOPS/TB | 1TB, capable of providing at least 256 IOPS/TB |
| Memory | 32 GB | 8 GB |
| CPU | 4 vCPUs | 2 vCPUs |
| Distribution | 1 Field Effect VM per physical ESXi host (depending on capture configuration) | |
Requesting a Virtual MDR SIEM device or network sensor
Direct clients will have the opportunity to make this selection while our Sales team scopes your organization's requirements. Partners will be able to scope a client's appliance requirements while onboarding them. Based on your needs, we’ll deliver the appropriate assets including welcome content and deployment guides for your virtual application.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article