{"title": "Exabeam Fusion XDR setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002718921-Exabeam-Fusion-XDR-setup-for-Workbench", "date": "2021-02-17T20:44:50Z", "contents": "This article explains how to connect Exabeam Fusion XDR to Workbench.\n\n####  In this article\n\n  * Step 1: Enable console access\n\n  * Step 2: Generate API credentials\n\n  * Step 3: Configure the technology in Workbench\n\n  * Step 4: Edit the device to add console access\n\n##  Step 1: Enable console access\n\nHaving read-only access to the interface of your technology allows Expel to\ndig deeper during incident investigations. Our device health team uses this\naccess to investigate potential health issues with your tech.\n\nThe Exabeam Security Management Platform uniquely combines a data lake for\nunlimited data collection, machine learning for advanced analytics, and\nautomated incident response into an integrated set of products. The SOC\nanalysts require a dedicated user account, which allows us to respond to\nsecurity alerts and leverage the data available in Exabeam Fusion XDR.\n\n###  Note\n\nExpel secures all login information our SOC analysts need about your devices\nin a MFA password product. Access to this login information is protected using\nour internal MFA processes. To learn more about the IP addresses all Expel\ntraffic comes from, go here.\n\n  1. From the menu at the top right, click Settings.\n\n  2. In the Exabeam User Management section, select Users.\n\n  3. Select Add User. Type the following information for the fields:\n\n**Field name**\n\n|\n\n**What to put in it**  \n  \n---|---  \n  \nUser Type\n\n|\n\nLocal  \n  \nUsername\n\n|\n\nexpel  \n  \nFull Name\n\n|\n\nExpel SOC  \n  \nEmail\n\n|\n\nOptional field can be left blank  \n  \nPassword\n\n|\n\nEnter a password. **Save the password to enter later in Workbench.**  \n  \n  4. For Role, select Tier 3 Analyst. If a custom role is preferred, complete the next 2 steps. Note the permission requirements. If you don't need a custom role, skip to Step 2 below.\n\n  5. For a custom role, type Expel for Role Name and Expel Custom Role for Description.\n\n  6. Select Advanced Analytics, and select the following permissions:\n\n**View**\n\n|  \n---|---  \n  \nView Activities\n\n|\n\nRequired  \n  \nView Executive Info\n\n|\n\nRequired  \n  \nView Global Insights\n\n|\n\nRequired  \n  \nView Infographics\n\n|\n\nRequired  \n  \nView Insights\n\n|\n\nRequired  \n  \nView Rules\n\n|\n\nRequired  \n  \n**Edit and Approve**\n\n|  \n  \nApprove Lockouts\n\n|\n\nOptional but recommended  \n  \nAccept Sessions\n\n|\n\nOptional but recommended  \n  \nManage Rules\n\n|\n\nOptional but recommended  \n  \nManage Watchlist\n\n|\n\nOptional but recommended  \n  \n**Search**\n\n|  \n  \nManage Search Library\n\n|\n\nOptional but recommended  \n  \nBasic Search\n\n|\n\nRequired  \n  \nThreat Hunting\n\n|\n\nRequired  \n  \nView Search Library\n\n|\n\nRequired  \n  \n\n##  Step 2: Generate API credentials\n\nHaving read-only access to the interface of your technology allows Expel to\ndig deeper during incident investigations. Our device health team uses this\naccess to investigate potential health issues with your tech.\n\n  1. Navigate to Settings > Admin Operations > Cluster Authentication Token.\n\n  2. On the Cluster Authentication Token menu, click + to add a new token.\n\n  3. In the Setup Token dialog box, fill in the Token Name, set Expiry Date to Permanent, and set the Permission Level as Tier 3 Analyst.\n\n  4. Click Save.\n\n  5. Copy the generated token for use in the next step.\n\n##  Step 3: Configure the technology in Workbench\n\nNow that we have the correct access configured and noted the credentials, we\ncan integrate your tech with Workbench.\n\n  1. Go to https://workbench.expel.io/settings/security-devices?setupIntegration=exabeam_fusion_xdr.\n\n  2. Complete the fields using the credentials and information you collected in Step 1 and Step 2.\n\n![ExabeamFusionXDR_AddSecDev.png](https://support.expel.io/hc/article_attachments/13874991886611/uuid-\ndea420f1-5b85-5425-f8f9-b74edc4cf0b1.png)\n\n    * (On-prem only) Select an Assembler from the list. If you have an assembler, select the assembler you set up in Getting connected to googleWorkbench\n\n    * For Name, type a name that's meaningful to you.\n\n    * Type the city or site where your Exabeam installation is located for Location.\n\n    * Under Connection Settings, for Token type the token you generated in Step 2 and for Server Address type the IP address for Exabeam.\n\n    * For Username and Password, type the information you created in Step 1.\n\n  3. Click Save.\n\n  4. You can provide console access now or set it up later. Use the instructions below to set it up later.\n\nYou can see if the device is healthy on the Security Devices page. It may take\na few minutes to see the device listed as healthy.\n\nTo check if alerts are coming through, navigate to the Alerts Analysis page.\nScroll to the device you want to check and click View alerts. Switch to grid\nview, then check the list for device alerts. It can take 36 to 72 hours for\nalerts to appear after setup, as we tune your device.\n\n##  Step 4: Edit the device to add console access\n\nExpel needs console access to your device to allow our SOC analysts to dig\ndeeper during incident investigations. Additionally, our engineering teams use\nthis access to investigate potential health issues, including proper alert\ningestion.\n\n### Note\n\nExpel secures all login information our SOC analysts need about your devices\nin a MFA password product. Access to this login information is protected using\nour internal MFA processes. To learn more about the IP addresses all Expel\ntraffic comes from, go here.\n\n  1. Open Workbench. Go to Organization Settings > Security Devices. Next to the device you just connected, click the down arrow and click Edit.\n\n  2. In the Console Login area, type these details:\n\n    * Console URL: type the console URL from the Server address in the Connection Settings area above. At the end of the URL, type **/login**.\n\n    * Username: type the user name you created above.\n\n    * Password: type the password you created above.\n\n    * Two-factor secret key (32-character code): depending on how your organization enforces log-ins, this field may not apply to you. In these cases, you can leave it blank. This field is optional and if you have questions or concerns, reach out to your engagement manager or to support.\n\n  3. Click Save.\n\n###  Tip\n\nThis article was accurate at the time of writing, but changes happen. If you\nfind the instructions are outdated, leave a description in the comment field\nbelow and let us know!\n\n"}