The following section details the basics of accessing and using the Carbon Black Cloud. If you are familiar with the Carbon Black Cloud you may skip the informational section one. For more a more in-depth walkthrough of the CBC please see the “Endpoint Standard Hands-On Lab” located here: https://labs.hol.vmware.com/HOL/catalogs/lab/10096
2.1 Accessing the Carbon Black Cloud
The Carbon Black Cloud console is web-based with one lightweight agent deployed to endpoints. The single agent allows for consolidation across AV, EDR, vulnerability, and security auditing technologies. No stand-up or maintenance of on-premises servers is required – offloading work from infrastructure and security teams.
The console is accessed through a supported web browser:
- Windows: Chrome, Edge, Firefox
- MacOS: Chrome, Firefox, Safari
Login to Carbon Black Cloud:
- URL: https://defense-prod05.conferdeploy.net/
- User: (listed in text file Carbon_Black_Cloud_Malware_Credentials.txt on the Carbon Black Malware desktop)
- Password: (listed in text file Carbon_Black_Cloud_Malware_Credentials.txt on the Carbon Black Malware desktop)
For purposes of this lab use Google Chrome to access the console. On login you will land on the CBC Dashboard. The main navigation menu is located on the left-hand side of the web console.
CBC Dashboard | The dashboard gives a high-level overview of your environment with interactive widgets.
Before continuing you must switch orgs. The TestDrive Carbon Black console is separated based on experience. Navigate to the correct org by clicking the org name in the upper right. Then, click Switch Orgs.
Finally, select vmweng-standard.com from the dropdown and click select.
2.2 Alert Walkthrough
The Alerts page displays events of known threats or potential risks to your environment. To navigate to the Alerts page, select Alerts from the left-hand menu.
Regularly review alerts to determine whether action needs to be taken or policies need to be modified. Alert notifications can be setup to email designated administrators when an alert occurs. Alerts can also be forward to a SIEM with the Carbon Black open API (https://developer.carbonblack.com/reference/carbon-black-cloud/cb-defense/latest/rest-api/).
An alert will show:
Status – Run status and policy status
- Run Status: process ran/did not run
- Policy status: policy applied/no policy applied
- First Seen – What time the events of alerts first occurred
- Reason – High level overview of the reason the alert occurred
- S(everity) – Numerical score from 1 to 10, 1 being lowest severity and 10 being highest
- T(arget Value) – Acts as a multiplier for the severity score; target value can be assigned per policy group
- Device – Device that was alerted upon
Alert severity indicates the relative importance of an alert and acts as a prioritization assistant (one being lowest severity and ten being highest, mission critical). The following describe the ranges of severity:
- Severity 1-2: Activities such as port scans, malware drops, changes to system configuration files, persistence, etc.
- Severity 3-5: Activities such as malware running, generic virus-like behavior, monitoring user input, potential memory scraping, password theft, etc.
- Severity 6-10: Activities such as reverse command shells, process hollowing, ransomware, destructive malware, hidden processes and tool sets, applications that talk on the network but should not, etc.
Filters are available on the left-hand. This can be used to filter into alerts of interest by device, severity, etc.
To view additional information about an alert, click the chevron to expand. The Alert Details show additional information about the processes, behaviors (or TTP’s – Tactics, Techniques, and Procedures), recommended steps for remediation, and notes/tags.
CBC Alerts – Alert Details | Alert Details show additional information for further investigation into malicious/suspicious events.
The Techniques section in Alert Details shows what behaviors, or TTPs (tactics, techniques, and procedures), were exhibited by the specified process. TTP’s are color coded, with red being a higher severity. TTP’s can be clicked into to view further information about the TTP and what it means. Carbon Black also correlates MITRE techniques to TTPs which are also displayed. Clicking a MITRE technique will take you directly to the MITRE page correlating to that technique.
An alert visualization is generated for all alerts that occur. The visualization provides an easy to understand and digest view of what occurred during the attack sequence. To view an alert visualization, called the Alert Triage, click the tree icon) in the upper right of alert details.
CBC Alerts | You can quickly pivot to the Alert Triage (tree icon), Investigate, or additional actions with the linked buttons.
The Alert Triage displays a tree containing events associated with the alert. A node represents an individual process or event. You can click a node to view additional process details on the right including reputation, TTPs (behaviors), command line used, and other information. The Alert Triage provides actionable information about the events that occurred during an alert: including where prevention was applied, source, and what the attacker may have been attempting.
CBC Alerts – Alert Triage| Alert Triage shows alert in visual format; each node can be clicked into for more details about the selected process on the right.
The alert can be viewed in a log level format as well for more rich, process level behavioral information such as: command line, parent command line, if the device was on or off-premise at the time of the event, etc. These logs can be viewed in the Enriched Events section, which you can find by scrolling down to the bottom of the Alert Triage page.
CBC Alerts – Enriched Events| Click the chevron next to an enriched event to view additional details.
2.3 Policies Walkthrough
The CBC next-gen AV and EDR solution offers flexible Policies. Policies determine preventative rules as well as sensor functionality. Carbon Black gives administrators control and visibility into how prevention works in your environment.
Each endpoint with a sensor installed will belong to a single policy. A policy defines how the sensor should behave on the endpoint, blocking/preventative rules, exclusions and allowances, and other configurations.
In this lab we have put the Horizon TestDrive endpoints into the ‘Virtual Desktops’ policy group that copies settings from 'Standard' with some adjustments for VDI. The Standard policy group comes OOTB (alongside the Monitored and Advanced policies) and is meant to act as a day-one, production viable policy that gives additional preventative layers beyond a traditional AV.
To view information about Policies and the Standard Policy Rules, navigate using the main left-hand menu to Enforce -> Policies. On the ‘Prevention’ tab you can see rules associated with the selected policy group.
CBC Policies – Prevention Rules| Carbon Black offers OOTB production viable policies for day-one use while giving admins visibility and customizability into what is prevented and allowed.
Review the rules within the Standard policy before proceeding. In this lab the attacks ran will be prevented by rules within this policy, including rules for:
- Process: Known Malware
- Process (At Path): Excel, Invokes a command interpreter
- Process: Not Listed, Performs ransomware-like behavior