Skip to main content

Running tasks

Running tasks on computers

Malware scan

IOC scan

Risk scan

Exchange scan

Install agent

Uninstall agent

Update agent

Upgrade agent

This task is available only when Endpoint Security agent is installed and detected in the network. Bitdefender recommends upgrading from Endpoint Security to Bitdefender Endpoint Security Tools Bitdefender Endpoint Security Tools, for a last-generation endpoint protection.

To easily find the security agents that are not upgraded, you can generate an upgrade status report. For details about how to create reports, refer to Creating reports.

Reconfigure agent

Repair agent

Restart endpoint

Isolate endpoint

Remove from isolation

Suspend endpoint protection

In the Network section, you can manage endpoint security efficiently while maintaining full control over the suspension process.

Note

These actions are supported starting with Windows product version 7.9.20.x, macOS product version 7.20.x, and Linux product version 7.5.0.x.

To suspend endpoint protection follow these steps:

  1. Locate the endpoint for which you want to suspend protection in the Network grid.

  2. Select the corresponding checkbox.

  3. Open the Actions menu at the top of the grid and select Suspend protection.

    Suspend_protection_action_menu_network.png
  4. On the configuration page:

    1. Create a task name.

    2. Select the modules that will be suspended.

    3. Select the time interval for the suspend action.

    4. Click Suspend to initiate the task.

    Suspend_protection_FPP.png

    Important

    The selected endpoint will be unprotected for the specified time interval, therefore we recommend starting a full malware scan on the unprotected endpoint immediately after the selected time interval ends.

    On iOS devices, Web Traffic Scan relies on the Antimalware module to function. If Antimalware protection is suspended, Web Traffic Scan will also be disabled automatically until protection is resumed.

    When troubleshooting, some protection modules cannot be deactivated. These modules are necessary for system integrity and security but do not affect user work.

    The following modules are grayed out and cannot be disabled:

    • Device Control: manages access to external devices like USB drives and external storage. Since it does not interfere with regular operations, disabling it is unnecessary for troubleshooting.

    • Power User: ensures that only authorized administrators can modify security configurations. Disabling it would not aid in troubleshooting and could compromise security policies.

    • Full Disk Encryption: protects sensitive data at rest. Turning this off could lead to security risks, and it does not impact normal troubleshooting tasks.

    • Patch Management: ensures that critical security updates and patches are applied. Since patching runs in the background without disrupting user workflows, it remains enabled.

Resume endpoint protection

To resume endpoint protection follow these steps:

  1. Locate the endpoint for which you want to resume protection in the Network grid.

  2. Select the corresponding checkbox.

  3. Open the Actions menu at the top of the grid and select Resume protection.

    resume_protection_action_menu_network.png
  4. Click Resume to initiate the task.

    Resume_endpoint_protection.png

    Important

    We recommend starting a full malware scan on the unprotected endpoint when resuming endpoint protection.

Submit to Sandbox Analyzer

At any time, you can remotely send samples to Sandbox Analyzer from any managed endpoint running Windows OS.

You can only submit samples from a single endpoint at once.

Note

To submit samples that you store locally on the machine where you access GravityZone Control Center, use the options on the Manual submission page.

Creating the task

To submit a sample from an endpoint in your network, follow these steps:

  1. Log in to GravityZone Control Center.

  2. Go to the Network page in the GravityZone main menu.

  3. Browse your network and select the target endpoint.

  4. Click the Actions menu and select Submit to Sandbox Analyzer.

  5. In the configuration window, fill in the following details:

    • Task name. By default, the task name is Submit to Sandbox Analyzer followed by date. If needed, you can change the name to find it easier on the Network > Tasks page.

      The task name supports up to 512 characters.

    • Path. Specify the full path to the sample you want detonated. For example, D:\temp\test.exe

      You can add up to 5 samples per submission. Each sample must be up to 100 MB. After each path, click the Add.png Add button.

      The path requires Windows format and supports up to 1024 characters.

      Sandbox Analyzer supports archives with two levels of nesting.

      Note

      An easy way to get the full path is to access the Security tab in the Properties window of the sample, on the target endpoint, and copy it from there.

    • Command line. Optionally, add command lines to be executed when the detonation starts.

      Command lines may include parameters. Executable files, such as interpreters, must include the full path. For example, C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe C:\script.ps1

      If nothing is specified, Sandbox Analyzer will automatically choose how to detonate the samples.

      You can add up to 10 command lines per submission. After each command line, click the Add.png Add button.

      Each command line supports up to 4096 characters.

    • Click Save.

      tasks_submit_to_sandbox_analyzer_904121_en.png

You can monitor the progress of the created task on the Network > Tasks page, under Submit to Sandbox Analyzer type.

Note

Sandbox Analyzer supports any Unicode characters.

Viewing the results

Sample detonation may take several minutes. When done, you can view the results on the Sandbox Analyzer page in the GravityZone main menu.

Each detonation has dedicated submission card, with the following details:

  • Submission type: manual.

  • Verdict: clean, infected, unsupported.

  • Sample path, as you provided it when creating the task.

  • Severity score, which indicates the threat level posed by the sample.

  • Files and process involved, indicated by a number.

  • Endpoint name, as displayed in your network.

  • Environment where the detonation had taken place, which is identified as Cloud Sandbox.

  • MD5 hash.

  • ATT&CK techniques identified during detonation.

For a more detailed report, click the View button on the right side of the card.

tasks_sandbox_analyzer_results_904121_en.png

User activity

You can review the tasks on the Accounts > User activity page, under Area: Tasks.

Run network discovery

Update Security Server