PARTNERS

Viewing endpoint details

Viewing endpoint details

You can obtain detailed information about each endpoint within the Network page, as follows:

Checking the Network page

To find out details about an endpoint, check the information available in the right-side pane table from the Network page.

You can add or remove columns with endpoint information by clicking the columns.pngColumns button at the upper-right side of the pane.

  1. Go to the Network page.

  2. Select the group that you want from the left-side pane.

    All endpoints available in the selected group are displayed in the right-side pane table.

  3. You can easily identify the endpoint status by checking the corresponding icon. For detailed information, refer to Checking the endpoints status.

  4. Check the information displayed on columns for each endpoint.

    Use the header row to search as you type for specific endpoints, according to the available criteria:

    • Name: endpoint name.

    • FQDN: fully qualified domain name.

    • OS version: the version of the operating system installed on the endpoint.

    • OS type: the type of the operating system installed on the endpoint.

    • IP: endpoint's IP address.

    • Last Seen: date and time when the endpoint has last been seen online.

      Note

      It is important to monitor the Last Seen field as long inactivity periods might indicate a communication issue or a disconnected computer.

    • Label: a custom string with additional information about the endpoint. You can add a label in the endpoint's Information window and then use it in searches.

    • Policy: the policy applied to the endpoint, with a link for viewing or changing the policy settings.

    • Endpoint type: the type of the machine, server or workstation.

    • Company: the company where the endpoint is located.

    • Users: the logged in users. For only one logged in user, their name will be displayed. Otherwise, the grid displays the number of users.

      Tip

      Users column contains links to pages with further details on the topic.

Checking the Information window

In the right-side pane of the Network page, click the name of the endpoint you are interested in to display the Information window. This window displays only the data available for the selected endpoint, grouped under several tabs.

Find hereafter the exhaustive list of information you may find in the Information window, according to the endpoint type and its specific security information.

General tab
  • General endpoint information, such as name, instance ID, IP address, Amazon region and availability zone (if the endpoint is an Amazon instance), instance type, operating system, infrastructure, security groups and current connection status.

    In this section, you can assign the endpoint with a label. You will be able to quickly find endpoints with the same label and take actions on them, no matter where they are located in the network. For more information about filtering endpoints, refer to sorting, filtering and searching for endpoints.

  • Protection layers information, including the list of security technologies acquired with your GravityZone solution and their license status, which can be:

    • Not Licensed - the GravityZone partner does not have a license key for this protection layer.

    • Available / Active – the license key for this protection layer is active on the endpoint.

    • Expired – the license key for this protection layer is expired.

    • Pending – the license key is not confirmed yet.

      Note

      Additional information on the protection layers is available in the Protection tab.

  • Relay Connection: the name, IP and label of the relay to which the endpoint is connected, if the case.

details-eps-general.png
Protection tab

This tab contains details about each protection layer licensed on the endpoint. Details refer to:

  • Security agent information like product name, version, update status, and update locations as well as scanning engines configuration and security content versions. For Exchange Protection, antispam engine version is also available.

  • Security status for each protection layer. This status appears at the right side of the protection layer's name:

    • Secure, when there are no security issues reported on the endpoints applied with the protection layer.

    • Vulnerable, when there are security issues reported on the endpoints applied with the protection layer. For more details, refer to Security Status.

  • Associated Security Server. Each assigned Security Server is displayed in case of agentless deployments or when scanning engines of the security agents are set to use remote scan. Security Server information helps you identify the virtual appliance and get its update status.

  • The protection modules status. You can easily view which protection modules have been installed on the endpoint and also the status of available modules (On / Off) set via the applied policy.

  • A quick overview regarding the modules activity and malware reporting in the current day.

    Click the report_inline.pngView link to access the report options and then generate the report. For more information, refer to Creating reports

  • Information regarding the Sandbox Analyzer protection layer:

    • Sandbox Analyzer usage status on the endpoint, displayed at the right side of the window:

      • Active: Sandbox Analyzer is licensed (available) and enabled via policy on the endpoint.

      • Inactive: Sandbox Analyzer is licensed (available) but not enabled via policy on the endpoint.

    • Name of the agent that acts as feeding sensor.

    • Module status on the endpoint:

      • On - Sandbox Analyzer is enabled on the endpoint via policy.

      • Off - Sandbox Analyzer is not enabled on the endpoint via policy.

    • Threat detections in the last week by clicking the report_inline.pngView link to access the report.

  • Information regarding the Encryption module, such as:

    • Detected volumes (mentioning the boot drive).

    • Encryption status for each volume (which can be Encrypted, Encryption in progress, Decryption in progress, Unencrypted, Locked or Paused).

      Click the Recovery link to retrieve the recovery key for the associated encrypted volume. For details about retrieving the recovery keys, refer to Using Recovery manager for encrypted volumes.

  • Information on the Storage Protection module, in case the endpoint is a Security Server. Details refer to:

    • Service status:

      • N/A – Storage Protection is licensed, but the service is not configured yet.

      • Enabled – the service is enabled in the policy and functioning.

      • Disabled – the service is not functioning either because it has been disabled from the policy or the license key has expired.

    • List of the storage devices that have been scanned during the past month, with these details:

      • Storage device name

      • Storage device IP

      • Storage device type

      • The date and time of the last communication between the storage device and Security Server.

  • Information on Security Analytics, as part of EDR:

    • Specific Agent Information indicates:

      • Events Provider - BEST reports endpoint and application behavior to the Security Analytics component.

      • Communication Status - BEST connects to Security Analytics.

      • Last Status Update - The most recent status.

    • Overview information on the EDR Sensor activation status.

details-eps-protection.png
Investigation tab

In the Investigation tab you can collect forensic data from the endpoint to analyze and investigate possible threats to your environment.

  1. In the Network page, select the managed endpoint you want to collect forensic data from and open its details page.

  2. Go to the Investigation tab, and click Collect Investigation Package to start compiling an archive with forensic data.

    InvPackageEPDetailsFullCollect.png

    Note

    If the button is inactive, a tooltip will be displayed, with the reason why the action is unavailable. For more details see Investigation package prerequisites

    A toast message will inform you that the data collection request was successfully created.

    You can track its progress in the Investigation Files Activity grid.

  3. You can view the current collection process (the status of the activity in progress is set to Pending), along with other data gathering activities performed in the past 24 hours.

    InvFilesActivityProgress.png

    Note

    Collection activities that were canceled by user or could not be completed for various reasons have the status set to Failed .

    When the data collection process has completed successfully, the action status changes to Finished, and the archive with collected forensic artefacts is available for download.

  4. Click Download file in the Actions column to download the archive locally and analyze the collected data.

Note

To find out more details about the type of data collected as part of an investigation package see Investigation Package data.

Policy tab

An endpoint can be applied with one or more policies, but only one policy can be active at a time. The Policy tab displays information about all policies that apply to the endpoint.

  • The active policy name. Click the policy name to open the policy template and view its settings.

  • The active policy type, which can be:

    • Device: when the policy is manually assigned to the endpoint by the network administrator.

    • Location: a rule-based policy automatically assigned to the endpoint if the endpoint's network settings match the given conditions of an existing assignment rule.

      For example, a laptop has assigned two location-aware policies: one named Office, which is active when it connects to the company's LAN, and Roaming, which becomes active when the user works remotely and connects to other networks.

    • User: a rule-based policy automatically assigned to the endpoint if it matches the Active Directory target specified in an existing assignment rule.

    • External (NSX): when the policy is defined in the VMware NSX environment.

  • The active policy assignment type, which can be:

    • Direct: when the policy is directly applied to the endpoint.

    • Inherited: when the endpoint inherits the policy from a parent group.

  • Applicable policies: displays the list of policies linked to existing assignment rules. These policies may apply to the endpoint when it matches the given conditions of the linked assignment rules.

details-eps-policy.png

For more information regarding policies, refer to Changing Policy Settings

Connected Endpoints tab

The Connected Endpoints tab is available only for endpoints with relay roles. This tab displays information about the endpoints connected to the current relay, such as name, IP, and label.

Information window - Connected Endpoints Tab
Repository details tab

The Repository details tab is available only for endpoints with relay roles and displays information about the security agent updates and security content.

The tab includes details about the product and signatures versions stored on the relay and the ones available in the official repository, update rings, the date and time of the update, and last check for new versions.

Note

  • The product versions are not available for Security Servers.

Scan Logs tab

The Scan logs tab displays detailed information about all scan tasks performed on the endpoint.

Logs are grouped by protection layer and you can choose from the drop-down menu for which layer to display logs.

Click the scan task you are interested in and the log will open in a new page of the browser.

When many scan logs are available, they may span through several pages. To move through the pages, use the navigation options at the bottom of the table. If there are too many entries, you can use the filter options available at the top of the table.

details-eps-relay_2.png
Troubleshooting tab

This section is dedicated to agent troubleshooting activity. You can gather general or specific logs from the endpoint check or take action on current troubleshooting events and view previous activity.

Important

Troubleshooting is available for Windows, Linux, macOS, and all Security Server types.

details-eps-troubleshooting.PNG
  • Gather endpoint logs

    This option helps you gather a set of logs and general information necessary for troubleshooting such as endpoint settings, active modules, or applied policy specific to the target machine. All the generated data is saved in an archive.

    It is recommended to use the option when the cause of the issue is unclear.

    To start the troubleshooting process:

    1. Click the Gather logs button. A configuration window is displayed.

    2. In the Logs Storage section, choose a storage location.

      • Target machine: the logs archive is saved to the provided local path. The path is not configurable for Security Servers.

      • Network share: the logs archive is saved to the provided path from the shared location.

      • Bitdefender Cloud: the logs archive is saved to a Bitdefender Cloud storage location where the Enterprise Support team can access the files.

      You can use the option Save logs also on target machine to save a copy of the logs archive on the affected machine as a backup.

    3. Fill in with the necessary information (local path, credentials for the network share, path to the shared location) depending on the selected location.

    4. Click the Gather logs button.

    Note

    If you choose Bitdefender Cloud as a storage option, consider the following:

    • The logs archive is saved with identical names both to Bitdefender Cloud and on the target machine. Click the troubleshooting event to view the archive’s name in the details window.

    • After the archive is uploaded please provide Bitdefender Enterprise Support with the necessary information (name of the target machine, the archive name), on the opened case. Open a new case if none exists.

  • Debug session

    With Debug session, you can activate advanced logging on the endpoint to gather specific logs while reproducing the issue.

    You should use this option when you have discovered which module is causing issues or at the recommendation of Bitdefender Enterprise Support. All the generated data is saved in an archive.

    To start the troubleshooting process:

    1. Click the Begin session button. A configuration window is displayed.

    2. In the Issue type section, select the issue you consider is affecting the endpoint:

      Issue type

      Use case

      Antimalware (on-access and on-demand scanning)

      • Endpoint general slowdown

      • A program or system resource takes too long to respond

      • A scanning process takes longer than usual

      • No connection to host security service error

      Update errors

      • Error messages received during product or security content updates.

      Content Control and Firewall

      • The website does not load

      • Elements of the web page are not displayed properly

      • Firewall communication issues

      • Firewall rules do not apply properly

      • Firewall blocks applications

      • Firewall is not working properly

      Cloud Services connectivity

      • The endpoint does not have connectivity with Bitdefender

      Product general issues (high verbosity logging)

      • Reproduce a generic reported issue with verbose logging.

      Endpoint Detection and Response (EDR)

      • Incidents are not created

      • Incidents are false positive

      • Incidents are false negative

      • Incidents are missing data

      • Incidents contain incorrect data

    3. For Debug session duration, choose the time interval after which the debug session automatically ends.

      Note

      It is recommended to manually stop the session using the Finish session option, right after you reproduce the issue.

    4. In the Logs Storage section, choose one or both storage locations.

      You can use the option Save logs also on target endpoint to save a copy of the logs archive on the affected endpoint as a backup.

    5. Fill in the necessary information (local path, credentials for the network share, path to the shared location) depending on the selected location.

    6. Click the Begin session button.

    Important

    You can run only one troubleshooting process at a time (Gather endpoint logs / Debug session) on the affected endpoint.

  • Troubleshooting history

    The Last activity section presents the troubleshooting activity on the affected computer. The grid displays only the latest 10 troubleshooting events in reverse chronological order and automatically deletes activity older than 30 days.

    The grid displays the details for every troubleshooting process.

    The process has main and intermediary statuses. Depending on the customized settings, you can have the following status, where you are required to take action:

    • In progress (Ready to reproduce the issue) – access the affected endpoint manually or remotely and reproduce the issue.

    You have several options to stop a troubleshooting process, as follows:

    • Finish session: ends the debug session and the gathering process on the endpoint while saving all the collected data to the specified storage location.

      It is recommended to use this option right after you reproduced the issue.

    • Cancel: this option cancels the process and no logs are collected.

      Use this option when you do not want to collect any logs from the endpoint.

    • Force Stop: forcefully stops the troubleshooting process.

      Use this option when cancelling the session takes too long or the endpoint is unresponsive and you will be able to start a new session in a few minutes.

    Important

    • To make sure the console displays the latest information use the refresh.png Refresh button at the upper right side of the Troubleshooting page.

    • For more details about a specific event, click the event name from the grid.

Users tab

This tab displays information about the users who logged into the computer, and contains the following elements:

  • Last update: shows when the information in this tab was last updated.

  • Refresh button: refreshes the data on the page.

  • A list that shows the following information:

    • Username: a list of the users who logged into the computer.

    • Last login method: shows whether the user logged in locally or remotely (via an RDP or SSH connection).

    • Last login time: shows the last time the user logged in.

Tip

You can use the filters available in each column header to search and refine the information displayed. For Last login time, use the two calendars to mark the beginning and the end of the time frame you are interested in.

Note

Each property in this window which is generating security issues is marked with the critical.png icon. Check the icon's tooltip to find out more details. Further local investigations may be needed.

Viewing container details

You can obtain detailed information about each container from the Network page, as follows:

Checking the Network page

To find out details about a container or a container host, check the information available in the right-side pane table from the Network page.

You can add or remove columns with container information by clicking the columns.png Columns button at the upper-right side of the pane.

  1. Go to the Network page.

  2. Select the group that you want from the left-side pane.

    All container hosts available in the selected group are displayed in the right-side pane table.

    Click on a specific container host to display all available containers managed by that specific host.

  3. You can easily identify the container and container host status by checking the corresponding icon. For detailed information, refer to Checking the container status.

  4. Check the information displayed on table columns for each container. To filter out which columns are displayed, click the columns.png Columns button at the upper right side of the screen.

    Use the header row to search for specific containers or container hosts. referred to collectively as endpoints, according to the available criteria:

    • Name: endpoint name.

    • FQDN: fully qualified domain name.

    • OS version: operating system version installed on the endpoint.

    • OS type: operating system type installed on the endpoint.

    • IP: endpoint's IP address.

    • Last Seen: date and time when the endpoint has last been seen online.

      Note

      It is important to monitor the Last Seen field as long inactivity periods might indicate a communication issue or a disconnected container.

    • Label: a custom string with additional information about the endpoint. You can add a label in the container's Information window and then use it in searches.

    • Policy: the policy applied to the endpoint, with a link for viewing or changing the policy settings.

    • Endpoint type: the type of endpoint (computer, virtual machine, container or mobile device).

    • Users - last user that accessed the device.

      Note

      Applies only to end-user devices.

    • Company: the company where the endpoint is located.

    • Container ID - the ID of the container.

    • Container image name - name of the container image.

Checking the Information window

In the right-side pane of the Network page, click the name of the container you are interested in to display the Information window. This window displays only the data available for the selected container, grouped under several tabs.

Find hereafter the exhaustive list of information you may find in the Information window, according to the machine type and its specific security information.

General tab
106300_1.png
  • General container information, such as name, FQDN information, IP address, operating system, infrastructure, parent group and current connection status.

    In this section you can assign the container with a label. You will be able to quickly find containers with the same label and take actions on them, no matter where they are located in the network. For more information about filtering containers, refer to Sorting, filtering, and searching for containers.

  • Protection layers information, including the list of security technologies acquired with your GravityZone solution and their license status, which can be:

    • Available / Active – the license key for this protection layer is active on the container.

    • Expired – the license key for this protection layer is expired.

    • Pending – the license key is not confirmed yet.

      Note

      Additional information on the protection layers is available in the Protection tab.

Protection tab
106300_2.png

This tab contains details about each protection layer licensed on the endpoint. Details refer to:

  • Security agent information, including protection type, product version, update related information, engine version, security content details and scan engine information.

  • Security status for each protection layer. This status appears at the right side of the protection layer's name:

    • Secure, when there are no security issues reported on the endpoints applied with the protection layer.

    • Vulnerable, when there are security issues reported on the endpoints applied with the protection layer. For more details, refer to Security Status.

  • NSX related information, such as virus tag status and the security group to which the container belongs. If a security tag has been applied, it informs you that the machine is infected. Otherwise, either the machine is clean or security tags are not being used.

  • The protection modules status. You can easily view which protection modules have been installed on the endpoint and also the status of available modules (On / Off) set via the applied policy.

  • A quick overview regarding the modules activity and malware reporting in the current day.

    Click the report_inline.png View link to access the report options and then generate the report. For more information, refer to Creating Reports

Policy tab
106300_3.png

A container can be applied with one or more policies, but only one policy can be active at a time. The Policy tab displays information about all policies that apply to the container.

  • The active policy name. Click the policy name to open the policy template and view its settings.

  • The active policy type, which can be:

    • Device: when the policy is manually assigned to the container by the network administrator.

    • Location: a rule-based policy automatically assigned to the container if the container's network settings match the given conditions of an existing assignment rule.

    • User: a rule-based policy automatically assigned to the endpoint if it matches the Active Directory target specified in an existing assignment rule.

      For example, a machine can have assigned two user-aware policies, one for administrators and one for other employees. Each policy becomes active when the user with the appropriate privileges logs in.

    • External (NSX): when the policy is defined in the VMware NSX environment.

  • The active policy assignment type, which can be:

    • Direct: when the policy is directly applied to the container.

    • Inherited: when the container inherits the policy from a parent group.

  • Applicable policies: displays the list of policies linked to existing assignment rules. These policies may apply to the container when it matches the given conditions of the linked assignment rules.

For more information regarding policies, refer to Managing Policies