Malwarebytes Endpoint Detection and Response includes Endpoint Isolation, which temporarily stops threats from spreading between endpoints by restricting their communication or access. An isolated endpoint can still communicate with the console and run Malwarebytes processes. Super Admins and Administrators can isolate endpoints protected by policies with the Endpoint Isolation feature enabled. For Endpoint Isolation usage […]
Administrators can delete endpoints using the console, which removes them from the Malwarebytes Nebula platform. After a period of time, the deleted endpoint is also removed from the Malwarebytes database. Malwarebytes then uninstalls the agent from from the endpoint. This article explains what happens when you mark endpoints for deletion, and how to perform this action. Alternatively, you can automate […]
Malwarebytes Nebula allows you to create a new name, or alias, for your managed endpoints. You may want to rename endpoints with complex device names to something easier to remember or identify. The new endpoint name is only visible in the Nebula console. Users at the endpoint do not see any changes. This article details […]
Malwarebytes Nebula allows you to control the maximum amount of processing power used during a manual or scheduled system scan on Mac endpoints. To follow the steps in this article, enable the New policies experience switch in the Policies page. If you have the new policies experience disabled, locate these policy settings by referring to: Malwarebytes Nebula policy […]
The Inactive endpoint option in Malwarebytes Nebula allows you to remove endpoints from your Nebula console that have been inactive for a set period of time. When enabled in a policy, endpoints that have not checked in with the console within the specified time frame are automatically removed. This feature is useful for automating the […]
Policies define how Malwarebytes behaves when running a scheduled scan, using Real-Time Protection, or monitoring Suspicious Activity. Policies are applied at the group level, and all endpoints in a group use the same policy. By default, endpoints added to the console belong to the Default Group which uses the Default Policy. To follow the steps […]
After installing the Linux Endpoint Agent, you can execute many operations by Command Line Interface (CLI), including start a scan, update databases, or configure exclusions. Some tasks are easier to use via the Malwarebytes Nebula console interface, like update database, create exclusions, or check quarantine. See this article for the available commands for Linux endpoints. […]
Policies define how Malwarebytes behaves when using Endpoint Detection and Response features. Policies are applied at the group level, and all endpoints in a group use the same policy. By default, endpoints added to the console belong to the Default Group, and the Default Policy. To follow the steps in this article, enable the New policies […]
The Malwarebytes Endpoint Protection agent needs to be allowed through any proxy in order to communicate with the Management Server. This can be done during a manual install, or via the command line after install. Set proxy information during manual install Proxy settings can be set during Malwarebytes Endpoint Protection installation if done manually with […]
When creating a base image with a Malwarebytes Endpoint Protection installation, the Malwarebytes installer should be prevented from connecting to the internet before the image is generalized by Sysprep. This may be easier to accomplish if the Malwarebytes installation is saved for the last step when configuring an image. If the endpoint agent is allowed to […]