For communication to flow between the Nebula console and endpoints, you must adjust your firewall. This article lists internal network recommendations and our external access requirements.
File and Printer Sharing
We recommend using Administrator shared folders to perform network tasks, such as installations. To use them, you must enable File and Printer Sharing on your endpoints.
The location of File and Printer Sharing options depends on which operating system your endpoint uses. Consult your operating system guide for additional information.
External Access Requirements
Allow the following addresses through your firewall or other security software. Endpoint Agents use the sites below to reach Nebula services.
You must allow or exclude all addresses on port 443, outbound.
|https://ark.mwbsys.com||Used to deliver updates to products.|
|https://blitz.mb-cosmos.com||Used to upload files for research and analysis.|
|https://cdn.mwbsys.com||Used to deliver updates to products.|
|https://cloud.malwarebytes.com||Used to access the Nebula admin console.|
|http://cosmos-shuriken-samples-mb-prod.s3.amazonaws.com/||Used to process samples sent from the endpoint agent.|
|https://data-cdn.mbamupdates.com||Used to deliver updates to products.|
|https://data-cdn-static.mbamupdates.com||Used to deliver updates to products.|
|https://detect-remediate.cloud.malwarebytes.com||Used to provide Endpoint Detection and Response capabilities.|
Used to validate threats against our servers for better protection and reduce false positives.
|https://keystone-akamai.mwbsys.com||Used to validate product licensing.|
|https://keystone.mwbsys.com||Used to validate product licensing.|
|https://nebula-agent-installers-mb-prod.s3.amazonaws.com||Used to download the endpoint agent installer and component package updates.|
|https://nebula-diagnostics-mb-prod.s3.amazonaws.com||Used to provide diagnostic data from the endpoint agent to Nebula.|
|https://nebula-helix-syslog-mb-prod.s3.amazonaws.com||Used to provide syslog functionality between the endpoint and Nebula.|
|https://sirius.mwbsys.com||Used to check for updates for both the product version and the protection database.|
|https://socket.cloud.malwarebytes.com||Used to provide real-time communication between the endpoint agent and Nebula|
|https://storage.gra.cloud.ovh.net||Used to upload suspicious files for sandbox analysis for Endpoint Detection and Response.|
|https://downloads.malwarebytes.com||Used to download packages and unmanaged remediation utilities|
|https://links.malwarebytes.com||Used to access product documentation through Nebula.|
Used to validate the Ransomware Extinction Prevention system in Nebula.
Used to allow access for Active Response Shell.
Used to allow websocket connection for Active Response Shell.
Used to communicate with our Public APIs.
Used for the DNS Filtering module.
- The endpoint agent does not allow packet-inspection, as this interferes with the service protocols.
- Bypass inspection is required to bypass packet-inspection on the endpoint agent.
- Proxy configurations are supported using built-in functions.
- Pass-through proxy configuration is recommended.
- Dynamic proxy configuration is not supported.
- To test the Endpoint Agent connection, see: Use the Endpoint Agent Command-line tool with Nebula.
Exclude Nebula from other applications
We recommend adding specific software exclusions if you use additional security software with Nebula. For more information, see Exclusions for using Nebula with other security applications.