Upload 155 files

article_10012579141523.json

@@ -0,0 +1 @@
+{"title": "Organization notifications default list", "url": "https://support.expel.io/hc/en-us/articles/10012579141523-Organization-notifications-default-list", "date": "2022-09-30T20:48:39Z", "contents": "These organization notifications are provided by default:\n\n  1. When an incident is created.\n\n  2. When an incident is assigned to my org.\n\n  3. When an investigation is assigned to my org.\n\n  4. When a remediation action is assigned to my org.\n\n  5. When a verify action is assigned to my org.\n\n  6. When an investigative action is assigned to my org.\n\n  7. When a notify action is assigned to my org.\n\n  8. When an assembler has a health status change.\n\n  9. When a security device has a health status change.\n\nFor the list of default user notifications that are added for each new user,\nsee the User notifications default list. To learn more about what the\nnotifications mean, see the Notifications definitions guide.\n\n"}

article_10853659813395.json

@@ -0,0 +1 @@
+{"title": "GitLab (SaaS) Setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/10853659813395-GitLab-SaaS-Setup-for-Workbench", "date": "2022-10-31T17:50:22Z", "contents": "This article explains how to connect GitLab to Expel Workbench.\n\n####  In this article\n\n  * Before you start\n\n  * Step 1: Enable console access\n\n  * Step 2: Configure the technology in Workbench\n\n##  Before you start\n\nYou must have:\n\n  * A GitLab SaaS installation. Reach out to your engagement manager if you’re using the self-managed version.\n\n  * A user account with owner permissions on the top-level group.\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\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. Login to GitLab and navigate to a top-level group.\n\n  2. Copy the Group ID.\n\n  3. Open your Profile menu and select Preferences.\n\n  4. Click Access Tokens.\n\n  5. Generate a Personal Access Token with a 1-year expiry date and a read_api permission level.\n\n##  Step 2: 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. In a new browser tab, log into Workbench. The link opens the Add Security Device screen directly.\n\n  2. Fill in the fields like this:\n\n![GitLab_AddSecDev.jpg](https://support.expel.io/hc/article_attachments/10853730922131/uuid-7762994e-3cdc-d0bf-\ndba9-771bee1baff4.jpg)\n\n    * Add a Name and Location that are meaningful to you.\n\n    * For API token, use the Personal Access Token created in Step 1.5.\n\n    * For On-prem URL, if the server is self-managed, use the GitLab server URL.\n\n    * For Group IDs, type the Group ID copied in Step 1.2.\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###  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"}

article_11455980950035.json

@@ -0,0 +1 @@
+{"title": "Check Point via SIEM setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/11455980950035-Check-Point-via-SIEM-setup-for-Workbench", "date": "2022-11-21T21:23:01Z", "contents": "This procedure helps you to connect your Check Point via SIEM to the Expel\nWorkbench. The procedure is to port in logs by creating a new Syslog source,\nconfiguring that source in Workbench, then your Check Point via SIEM device in\nWorkbench.\n\n###  Note\n\nSome steps in this procedure vary greatly depending upon the SIEM-based\ntechnology you use.\n\n####  In this article\n\n  * Step 1: Logging Check Point to a desired SIEM\n\n  * Step 2: Configure the SIEM in Workbench\n\n  * Step 3: Configure Check Point via SIEM in Workbench\n\n##  Step 1: Logging Check Point to a desired SIEM\n\nRefer to your SIEM documentation or work with your SIEM representative to port\nin Check Point logs. You can also refer to the following web references for\ncreating a new Syslog source:\n\n  * Sumo Logic\n\n##  Step 2: Configure the SIEM in Workbench\n\nThis link opens the Expel Knowledge Base section for connecting SIEM-based\ntechnology to Workbench. Follow the applicable article to configure your SIEM-\nbased tech and confirm that Check Point logs are flowing through and\navailable.\n\n##  Step 3: Configure Check Point via SIEM in Workbench\n\nNow that we have the correct access configured and noted the credentials, we\ncan integrate your tech with Workbench.\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. In a new browser tab, go to https://workbench.expel.io/settings/security-devices?setupIntegration=checkpoint.\n\n![image5.png](https://support.expel.io/hc/article_attachments/11455982033427/uuid-620734c6-3e67-2eb9-7f6e-8fc0b0ab24a5.png)  \n---  \n  \n  2. Fill in the device fields like this:\n\n    1. For SIEM select the SIEM that was onboarded in Step 2.\n\n    2. For Name type the host name of the Check Point device.\n\n    3. For Location type the geographic location of the device.\n\n  3. Fill in the Connection Settings fields based on the SIEM selected:\n\n    1. For Source category, type in the Sumo Logic source category for this device.\n\n  4. Click Save.\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###  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"}

article_11455981103379.json

@@ -0,0 +1 @@
+{"title": "Cisco FirePower via SIEM setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/11455981103379-Cisco-FirePower-via-SIEM-setup-for-Workbench", "date": "2022-11-21T21:23:03Z", "contents": "This procedure helps you to connect your Cisco FirePower via SIEM to the Expel\nWorkbench. The procedure is to port in logs by creating a new Syslog source,\nconfiguring that source in Workbench, then configure your Cisco FirePower via\nSIEM device in Workbench.\n\n###  Note\n\nSome steps in this procedure vary greatly depending upon the SIEM-based\ntechnology you use.\n\n####  In this article\n\n  * Step 1: Logging Cisco FirePower to a desired SIEM\n\n  * Step 2: Configure the SIEM in Workbench\n\n  * Step 3: Configure Cisco FirePower via SIEM in Workbench\n\n##  Step 1: Logging Cisco FirePower to a desired SIEM\n\nRefer to your SIEM documentation or work with your SIEM representative to port\nin Cisco FirePower logs. You can also refer to the following web references\nfor creating a new Syslog source:\n\n  * Sumo Logic\n\n  * Splunk\n\n  * Microsoft Sentinel\n\n##  Step 2: Configure the SIEM in Workbench\n\nThis link opens the Expel Knowledge Base section for connecting SIEM-based\ntechnology to Workbench. Follow the applicable article to configure your SIEM-\nbased tech and confirm that Cisco FirePower logs are flowing through and\navailable.\n\n##  Step 3: Configure Cisco FirePower via SIEM in Workbench\n\nNow that we have the correct access configured and noted the credentials, we\ncan integrate your tech with Workbench.\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. In a new browser tab, go to https://workbench.expel.io/settings/security-devices?setupIntegration=cisco_firepower.\n\n![image10.png](https://support.expel.io/hc/article_attachments/13874953488531/uuid-a6774976-0ade-5585-f1ec-a9093827d3bc.png)  \n---  \n  \n  2. Fill in the device fields like this:\n\n    * For SIEM, select the SIEM that was onboarded in Step 2.\n\n    * For Name, type the host name of the Cisco FirePower device.\n\n    * For Location, type the geographic location of the device.\n\n  3. Fill in the Connection Settings fields based on the SIEM you selected:\n\n    * For Index, type in the SIEM index.\n\n    * For Source type, type the Splunk source type for this device.\n\n  4. Click Save.\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###  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"}

article_11455981226003.json

@@ -0,0 +1 @@
+{"title": "Cisco Meraki via SIEM setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/11455981226003-Cisco-Meraki-via-SIEM-setup-for-Workbench", "date": "2022-11-21T21:23:04Z", "contents": "This procedure helps you to connect your Cisco Meraki via SIEM to the Expel\nWorkbench. The procedure is to port in logs by creating a new Syslog source,\nconfiguring that source in Workbench, then configure your Cisco Meraki via\nSIEM device in Workbench.\n\n###  Note\n\nSome steps in this procedure vary greatly depending upon the SIEM-based\ntechnology you use.\n\n####  In this article\n\n  * Step 1: Logging Cisco Meraki to a desired SIEM\n\n  * Step 2: Configure the SIEM in Workbench\n\n  * Step 3: Configure Cisco Meraki via SIEM in Workbench\n\n##  Step 1: Logging Cisco Meraki to a desired SIEM\n\nRefer to your SIEM documentation or work with your SIEM representative to port\nin Cisco Meraki logs. You can also refer to the following web references for\ncreating a new Syslog source:\n\n  * Sumo Logic\n\n  * Splunk\n\n##  Step 2: Configure the SIEM in Workbench\n\nThis link opens the Expel Knowledge Base section for connecting SIEM-based\ntechnology to Workbench. Follow the applicable article to configure your SIEM-\nbased tech and confirm that Cisco Meraki logs are flowing through and\navailable.\n\n##  Step 3: Configure Cisco Meraki via SIEM in Workbench\n\nNow that we have the correct access configured and noted the credentials, we\ncan integrate your tech with Workbench.\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. In a new browser tab, go to https://workbench.expel.io/settings/security-devices?setupIntegration=cisco_meraki.\n\n![image6.png](https://support.expel.io/hc/article_attachments/11455993539347/uuid-2ba5b47e-d9d4-d739-061c-6b4bad6c962d.png)\n\n  2. Fill in the device fields like this:\n\n    * For SIEM, select the SIEM that was onboarded in Step 2.\n\n    * For Name, type the host name of the Cisco Meraki device.\n\n    * For Location, type the geographic location of the device.\n\n  3. Fill in the Connection Settings fields based on the SIEM you selected:\n\n    * For Source category, type the Sumo Logic source category for this device.\n\n    * For Source type, type the Splunk source type for this device.\n\n  4. Click Save.\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###  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"}

article_11455981281299.json

@@ -0,0 +1 @@
+{"title": "CyberArk via SIEM setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/11455981281299-CyberArk-via-SIEM-setup-for-Workbench", "date": "2022-11-21T21:23:05Z", "contents": "This procedure helps you to connect your CyberArk via SIEM to the Expel\nWorkbench. The procedure is to port in logs by creating a new Syslog source,\nconfiguring that source in Workbench, then configure your CyberArk via SIEM\ndevice in Workbench.\n\n###  Note\n\nSome steps in this procedure vary greatly depending upon the SIEM-based\ntechnology you use.\n\n####  In this article\n\n  * Step 1: Logging CyberArk to a desired SIEM\n\n  * Step 2: Configure the SIEM in Workbench\n\n  * Step 3: Configure CyberArk via SIEM in Workbench\n\n##  Step 1: Logging CyberArk to a desired SIEM\n\nRefer to your SIEM documentation or work with your SIEM representative to port\nin CyberArk logs. You can also refer to the following web references for\ncreating a new Syslog source:\n\n  * Splunk\n\n##  Step 2: Configure the SIEM in Workbench\n\nThis link opens the Expel Knowledge Base section for connecting SIEM-based\ntechnology to Workbench. Follow the applicable article to configure your SIEM-\nbased tech and confirm that CyberArk logs are flowing through and available.\n\n##  Step 3: Configure CyberArk via SIEM 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. In a new browser tab, go to https://workbench.expel.io/settings/security-devices?setupIntegration=cyberark_siem.\n\n![image8.png](https://support.expel.io/hc/article_attachments/11455993631123/uuid-568dbe69-7e10-27fa-2ffe-5259b84c1315.png)  \n---  \n  \n  2. Fill in the device fields like this:\n\n    * For SIEM, select the SIEM that was onboarded in Step 2.\n\n    * For Name, type the host name of the CyberArk device.\n\n    * For Location, type the geographic location of the device.\n\n  3. Fill in the Connection Settings field based on the Splunk SIEM selected:\n\n    * For Index, type in the Splunk index where the logs are located.\n\n  4. Click Save.\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"}

article_11455981555603.json

@@ -0,0 +1 @@
+{"title": "Palo Alto Networks via SIEM setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/11455981555603-Palo-Alto-Networks-via-SIEM-setup-for-Workbench", "date": "2022-11-21T21:23:08Z", "contents": "This article helps you to connect your Palo Alto Networks via SIEM to the\nExpel Workbench. The procedure is to port in logs by creating a new Syslog\nsource, configuring that source in Workbench, then configure your Palo Alto\nNetworks via SIEM device in Workbench.\n\n###  Note\n\nSome steps in this procedure vary greatly depending upon the SIEM-based\ntechnology you use.\n\n####  In this article\n\n  * Step 1: Logging Palo Alto Networks to a desired SIEM\n\n  * Step 2: Configure the SIEM in Workbench\n\n  * Step 3: Configure Palo Alto Networks via SIEM in Workbench\n\n##  Step 1: Logging Palo Alto Networks to a desired SIEM\n\nRefer to your SIEM documentation or work with your SIEM representative to port\nin Palo Alto Networks logs. You can also refer to the following web references\nfor creating a new Syslog source:\n\n  * Sumo Logic\n\n  * Splunk\n\n##  Step 2: Configure the SIEM in Workbench\n\nThis link opens the Expel Knowledge Base section for connecting SIEM-based\ntechnology to Workbench. Follow the applicable article to configure your SIEM-\nbased tech and confirm that Palo Alto Networks logs are flowing through and\navailable.\n\n##  Step 3: Configure Palo Alto Networks via SIEM in Workbench\n\nNow that we have the correct access configured and noted the credentials, we\ncan integrate your tech with Workbench.\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. In a new browser tab, go to https://workbench.expel.io/settings/security-devices?setupIntegration=palo_alto_networks_siem.\n\n![image2.png](https://support.expel.io/hc/article_attachments/11455994709139/uuid-35a8793a-3ec7-f37a-5aa3-b778f7901938.png)\n\n  2. Fill in the device fields like this:\n\n    * For SIEM, select the SIEM that was onboarded in Step 2.\n\n    * For Name, type the host name of the Palo Alto Networks device.\n\n    * For Location, type the geographic location of the device.\n\n  3. Fill in the Connection Settings fields based on the SIEM you selected:\n\n    * For Source category, type the Sumo Logic source category for this device.\n\n    * For Source type, type the Splunk source type for this device.\n\n    * For Index, type in the Splunk index where the logs are located\n\n  4. Click Save.\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###  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"}

article_11455992258323.json

@@ -0,0 +1 @@
+{"title": "Cisco ASA via SIEM setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/11455992258323-Cisco-ASA-via-SIEM-setup-for-Workbench", "date": "2022-11-21T21:23:02Z", "contents": "This procedure helps you to connect your Cisco ASA via SIEM to the Expel\nWorkbench. The procedure is to port in logs by creating a new Syslog source,\nconfiguring that source in Workbench, then your Cisco ASA through SIEM device\nin Workbench.\n\n###  Note\n\nSome steps in this procedure vary greatly depending upon the SIEM-based\ntechnology you use.\n\n####  In this article\n\n  * Step 1: Logging Cisco ASA to a desired SIEM\n\n  * Step 2: Configure the SIEM in Workbench\n\n  * Step 3: Configure Cisco ASA via SIEM in Workbench\n\n##  Step 1: Logging Cisco ASA to a desired SIEM\n\nRefer to your SIEM documentation or work with your SIEM representative to port\nin Cisco ASA logs. You can also refer to the following web references for\ncreating a new Syslog source:\n\n  * Sumo Logic\n\n  * Splunk\n\n##  Step 2: Configure the SIEM in Workbench\n\nThis link opens the Expel Knowledge Base section for connecting SIEM-based\ntechnology to Workbench. Follow the applicable article to configure your SIEM-\nbased tech and confirm that Cisco ASA logs are flowing through and available.\n\n##  Step 3: Configure Cisco ASA via SIEM in Workbench\n\nNow that we have the correct access configured and noted the credentials, we\ncan integrate your tech with Workbench.\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. In a new browser tab, go to https://workbench.expel.io/settings/security-devices?setupIntegration=cisco_asa.\n\n![CISCO_ASA_Workbench.png](https://support.expel.io/hc/article_attachments/11455993341075/uuid-f429bf40-14c0-1c0e-4359-4cdb0e06a598.png)\n\n  2. Fill in the device fields like this:\n\n    * For SIEM, select the SIEM that was onboarded in Step 2.\n\n    * For Name, type the host name of the Cisco ASA device.\n\n    * For Location, type the geographic location of the device.\n\n  3. Fill in the Connection Settings fields based on the SIEM you selected:\n\n    * For Source type, type the Splunk source type for this device.\n\n    * For Source category, type the Sumo Logic source category for this device.\n\n    * For Index, type in the Splunk index where the logs are located. By default this is filled in with a wildcard (*).\n\n  4. Click Save.\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###  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"}

article_11455992575379.json

@@ -0,0 +1 @@
+{"title": "CylancePROTECT via SIEM setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/11455992575379-CylancePROTECT-via-SIEM-setup-for-Workbench", "date": "2022-11-21T21:23:06Z", "contents": "This procedure helps you to connect your CylancePROTECT via SIEM to the Expel\nWorkbench. The procedure is to port in logs by creating a new Syslog source,\nconfiguring that source in Workbench, then configure your CylancePROTECT\ndevice in Workbench.\n\n###  Note\n\nSome steps in this procedure vary greatly depending upon the SIEM-based\ntechnology you use.\n\n####  In this article\n\n  * Step 1: Logging CylancePROTECT to a desired SIEM\n\n  * Step 2: Configure the SIEM in Workbench\n\n  * Step 3: Configure CylancePROTECT via SIEM in Workbench\n\n##  Step 1: Logging CylancePROTECT to a desired SIEM\n\nRefer to your SIEM documentation or work with your SIEM representative to port\nin CylancePROTECT logs. You can also refer to the following web references for\ncreating a new Syslog source:\n\n  * Sumo Logic\n\n##  Step 2: Configure the SIEM in Workbench\n\nThis link opens the Expel Knowledge Base section for connecting SIEM-based\ntechnology to Workbench. Follow the applicable article to configure your SIEM-\nbased tech and confirm that CylancePROTECT logs are flowing through and\navailable.\n\n##  Step 3: Configure CylancePROTECT via SIEM 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. In a new browser tab, go to https://workbench.expel.io/settings/security-devices?setupIntegration=cylance.\n\n![image11.png](https://support.expel.io/hc/article_attachments/11455993724435/uuid-3ddaf712-c1fb-f4c1-7970-80e80857b1d4.png)  \n---  \n  \n  2. Fill in the device fields like this:\n\n    * SIEM, select the SIEM that was onboarded in Step 2.\n\n    * For Name, type the host name of the CylancePROTECT device.\n\n    * For Location, type the geographic location of the device\n\n  3. Fill in the Connection Settings field based on the Sumo Logic SIEM you selected:\n\n    * For Source category, type the Sumo Logic source category for this device.\n\n  4. Click Save.\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###  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"}

article_11455992644371.json

@@ -0,0 +1 @@
+{"title": "Forcepoint via SIEM setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/11455992644371-Forcepoint-via-SIEM-setup-for-Workbench", "date": "2022-11-21T21:23:07Z", "contents": "This article helps you to connect your Forcepoint via SIEM to the Expel\nWorkbench. The procedure is to port in logs by creating a new Syslog source,\nconfiguring that source in Workbench, then configure your Forcepoint via SIEM\ndevice in Workbench.\n\n###  Note\n\nSome steps in this procedure vary greatly depending upon the SIEM-based\ntechnology you use.\n\n####  In this article\n\n  * Step 1: Logging Forcepoint to a desired SIEM\n\n  * Step 2: Configure the SIEM in Workbench\n\n  * Step 3: Configure Forcepoint in Workbench\n\n##  Step 1: Logging Forcepoint to a desired SIEM\n\nRefer to your SIEM documentation or work with your SIEM representative to port\nin Forcepoint Web Filter logs. You can also refer to the following web\nreferences for creating a new Syslog source:\n\n  * Exabeam Fusion SIEM\n\n##  Step 2: Configure the SIEM in Workbench\n\nThis link opens the Expel Knowledge Base section for connecting SIEM-based\ntechnology to Workbench. Follow the applicable article to configure your SIEM-\nbased tech and confirm that Forcepoint logs are flowing through and available.\n\n##  Step 3: Configure Forcepoint in Workbench\n\nNow that we have the correct access configured and noted the credentials, we\ncan integrate your tech with Workbench.\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. In a new browser tab, go to https://workbench.expel.io/settings/security-devices?setupIntegration=forcepoint_siem.![image1.png](https://support.expel.io/hc/article_attachments/11455983387155/uuid-679a6a45-6cf9-c9dd-e5db-510aa0631da7.png)\n\n  2. Fill in the device fields like this:\n\n    * For SIEM, select the SIEM that was onboarded in Step 2.\n\n    * For Name, type the host name of the Forcepoint device.\n\n    * For Location, type the geographic location of the device.\n\n  3. Click Save.\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###  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"}

article_11455992832403.json

@@ -0,0 +1 @@
+{"title": "Proofpoint via SIEM setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/11455992832403-Proofpoint-via-SIEM-setup-for-Workbench", "date": "2022-11-21T21:23:08Z", "contents": "This article helps you to connect your Proofpoint via SIEM to the Expel\nWorkbench. The procedure is to port in logs by creating a new Syslog source,\nconfiguring that source in Workbench, then configure your Proofpoint via SIEM\ndevice in Workbench.\n\n###  Note\n\nSome steps in this procedure vary greatly depending upon the SIEM-based\ntechnology you use.\n\n####  In this article\n\n  * Step 1: Logging Proofpoint to a desired SIEM\n\n  * Step 2: Configure the SIEM in Workbench\n\n  * Step 3: Configure Proofpoint via SIEM in Workbench\n\n##  Step 1: Logging Proofpoint to a desired SIEM\n\nRefer to your SIEM documentation or work with your SIEM representative to port\nin Proofpoint logs. You can also refer to the following web references for\ncreating a new Syslog source:\n\n  * Sumo Logic\n\n##  Step 2: Configure the SIEM in Workbench\n\nThis link opens the Expel Knowledge Base section for connecting SIEM-based\ntechnology to Workbench. Follow the applicable article to configure your SIEM-\nbased tech and confirm that Proofpoint logs are flowing through and available.\n\n##  Step 3: Configure Proofpoint via SIEM in Workbench\n\nNow that we have the correct access configured and noted the credentials, we\ncan integrate your tech with Workbench.\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. In a new browser tab, go to https://workbench.expel.io/settings/security-devices?setupIntegration=observeit_siem.\n\n![image7.png](https://support.expel.io/hc/article_attachments/13874992013459/uuid-4013c40e-ec36-9f22-ac79-3853d71ff2ed.png)\n\n  2. Fill in the device fields like this:\n\n    * For SIEM, select the SIEM that was onboarded in Step 2.\n\n    * For Name, type the host name of the Proofpoint device.\n\n    * For Location, type the geographic location of the device.\n\n  3. Fill in the Connection Settings fields based on the Sumo Logic SIEM you selected:\n\n    * For Source category, type the Sumo Logic source category for this device.\n\n  4. Click Save.\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###  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"}

article_11455992924563.json

@@ -0,0 +1 @@
+{"title": "Symantec Endpoint Protection via SIEM setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/11455992924563-Symantec-Endpoint-Protection-via-SIEM-setup-for-Workbench", "date": "2022-11-21T21:23:09Z", "contents": "This procedure helps you to connect your Symantec Endpoint Protection via SIEM\nto the Expel Workbench. The procedure is to port in logs by creating a new\nSyslog source, configuring that source in Workbench, then configure your\nSymantec Endpoint Protection via SIEM device in Workbench.\n\n###  Note\n\nSome steps in this procedure vary greatly depending upon the SIEM-based\ntechnology you use.\n\n####  In this article\n\n  * Step 1: Logging Symantec Endpoint Protection to a desired SIEM\n\n  * Step 2: Configure the SIEM in Workbench\n\n  * Step 3: Configure Symantec Endpoint Protection in Workbench\n\n##  Step 1: Logging Symantec Endpoint Protection to a desired SIEM\n\nRefer to your SIEM documentation or work with your SIEM representative to port\nin Symantec Endpoint Protection logs. You can also refer to the following web\nreferences for creating a new Syslog source:\n\n  * Sumo Logic\n\n  * Splunk\n\n  * Exabeam Fusion SIEM\n\n##  Step 2: Configure the SIEM in Workbench\n\nThis link opens the Expel Knowledge Base section for connecting SIEM-based\ntechnology to Workbench. Follow the applicable article to configure your SIEM-\nbased tech and confirm that Symantec Endpoint Protection logs are flowing\nthrough and available.\n\n####  Step 3: Configure Symantec Endpoint Protection 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. In a new browser tab, go to https://workbench.expel.io/settings/security-devices?setupIntegration=symantec_endpoint_protection.\n\n![image3.png](https://support.expel.io/hc/article_attachments/13874948580883/uuid-d97036ea-f10e-05e9-62db-f051a0a27514.png)  \n---  \n  \n  2. Fill in the device fields like this:\n\n    1. For SIEM, select the SIEM that was onboarded in Step 2.\n\n    2. For Name, type the host name of the Symantec Endpoint Protection device.\n\n    3. For Location, type the geographic location of the device.\n\n  3. Fill in the Connection Settings fields based on the SIEM you selected:\n\n    1. For Source category, type the Sumo Logic source category for this device.\n\n    2. For Source type, type the Splunk source type for this device.\n\n  4. Click Save.\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###  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"}

article_11742313688595.json

@@ -0,0 +1 @@
+{"title": "Google Kubernetes Engine (GKE) setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/11742313688595-Google-Kubernetes-Engine-GKE-setup-for-Workbench", "date": "2022-12-01T15:04:58Z", "contents": "The Expel Google Kubernetes Engine (GKE) offering consumes audit logs from the\nGCP platform through a log sink and pub/sub. This visibility allows Workbench\nto identify activity of interest in GKE, investigate, and notify organizations\nif action is recommended.\n\n![Kub_Google_1_Overview.png](https://support.expel.io/hc/article_attachments/11742327507731/uuid-131e1763-9ff6-024d-91c5-c9b69271a05a.png)\n\n####  In this article\n\n  * Onboarding with terraform\n\n  * Manual onboarding instructions\n\n  * Before you start\n\n  * Enable control plane logging for GKE clusters\n\n  * Enable Cloud Resource Manager API for monitored projects\n\n  * Enable data access auditing for GKE\n\n  * Send GKE logs to a pub/sub topic\n\n    * Step 1: Create a new pub/sub queue\n\n    * Step 2: Create a log sink to route logs to pub/sub\n\n    * If you are onboarding a specific project\n\n    * Create IAM Role for required permissions\n\n    * Create GCP service account for Workbench\n\n    * Download GCP service account key\n\n  * Onboarding to Expel Workbench\n\n##  Onboarding with terraform\n\nExpel maintains a terraform module to help organizations easily onboard GKE\nwith Expel. Contact your engagement manager with any questions about this\nonboarding method. Otherwise, follow the manual instructions below.\n\n##  Manual onboarding instructions\n\nComplete the steps below for each GCP project to be monitored by Workbench.\n\n##  Before you start\n\nTo complete this procedure you need:\n\n  * Administrative access to the GCP environment.\n\n  * User privileges to create a service account, IAM role, log sink, a pub/sub topic, and a pub/sub subscription.\n\n##  Enable control plane logging for GKE clusters\n\nAt a minimum, Workbench requires logging of the Kubernetes control plane audit\nevents for each cluster. This provides visibility into activity affecting\nresources in the cluster (the “who”, “what”, and “when” we need to detect and\nrespond). By default, GKE clusters are configured to send Kubernetes audit\nevents to Cloud Logging, so no additional configuration is required for\nclusters.\n\n####  Enable Cloud Resource Manager API for monitored projects\n\nFor Expel to discover GKE clusters in the environment, the Cloud Resource\nManager API needs to be enabled in monitored projects. To enable the Cloud\nResource Manager API, navigate to APIs & Services library in the Google Cloud\nconsole.\n\nFrom the library, select Cloud Resources Manager, and enable this API for all\nmonitored projects.\n\n##  Enable data access auditing for GKE\n\nGoogle Kubernetes Engine (GKE) separates the Kubernetes control plane logs\ninto 2 log types in Cloud Logging: Admin Activity and Data Access logs. In\ngeneral, write operations (like get, update, or delete) are captured in the\nAdmin Activity log while read operations (like get or list) are captured in\nthe optional Data Access logs (see the documentation for more specifics).\n\nAdmin Activity logging is enabled by default, but it can be necessary to\nenable Data Access logging to increase logging visibility to include read\noperations. To do so, go to the IAM > Audit Logs page and search for\n_Kubernetes Engine API_.\n\nSelect all 3 boxes as below:\n\n![Kub_Google_2_EnableDataAccessAuditing.png](https://support.expel.io/hc/article_attachments/11742327582867/uuid-\ncc173ca9-1a12-cce1-ad1f-0b1fbbf9653c.png)\n\nThis can be done at a project, folder, or organization level.\n\n### Note\n\nEnabling additional logging can increase costs for Cloud Logging. For more\ninformation on how this is priced, see the documentation.\n\n##  Send GKE logs to a pub/sub topic\n\nGKE begins routing Kubernetes logs to Cloud Logging automatically. Next, we\ncreate a pub/sub queue and a log sink to route logs to Workbench.\n\n###  Step 1: Create a new pub/sub queue\n\nWorkbench collects GKE logs through a pub/sub subscription. Navigate to\nPub/Sub > Topics and create a new topic and default subscription.\n\n### Note\n\nWe don't recommend enabling retention duration because of additional cost.\nOptionally, configure a Customer-managed encryption key if needed.\n\n###  Step 2: Create a log sink to route logs to pub/sub\n\nNext, we need to create a log sink to route logs to the Pub/Sub topic. To\ncreate a sink at the organization level we need to use the gcloud command line\nutility.\n\n  1. Login to GCP.\n\n`$ gcloud auth login`\n\n  2. List the organizations and take note of the org ID.\n\n`$ gcloud organizations list`\n\n  3. Create the pub/sub org sink. Use this command to create the sink:\n    \n        $ gcloud logging sinks create [name of log sink] pubsub.googleapis.com/projects/[project-id]/topics/[topic-id] --include-children --organization=[org-id] --log-filter=\"(resource.type=gke_cluster OR resource.type=k8s_cluster)\\n-proto_payload.method_name=\\\"io.k8s.core.v1.nodes.proxy.get\\\"\\n-proto_payload.method_name=\\\"io.k8s.coordination.v1.leases.update\\\"\\n-proto_payload.method_name=\\\"io.k8s.core.v1.limitranges.update\\\"\\n-proto_payload.method_name=\\\"io.k8s.autoscaling\\\"\"\n\nThis automatically creates a new service account which must be granted Pub/Sub\nPublisher permissions on the integration’s topic.\n\n  4. Grant Pub/Sub Publisher role to log sink’s writer identity.\n\nObtain the sink's writer identity—an email address—from the new sink. Go to\nthe Log Router page, and select View sink details. The writer identity appears\nin the Sink details panel.\n\nFrom the console, navigate to PubSub > Topics > [topic-id]. On the Permissions\ntab, grant the service account created above the Publisher role.\n\n###  If you are onboarding a specific project\n\nNext, we need to create a log sink to route logs to the pub/sub topic.\nNavigate to Cloud Logging > Logs Router and create a new sink.\n\nType the following information:\n\n  1. A name for the sink.\n\n  2. A description for the sink.\n\n  3. Select the Cloud Pub/Sub topic we created earlier as the destination.\n\n  4. Type the filter below as an inclusion filter.\n\n**Filter**\n\n![Kub_Google_6_CreateLogSink.png](https://support.expel.io/hc/article_attachments/11742327930643/uuid-63cc2378-7ab3-f5f2-2e53-5f12643c6ded.png)\n\n###  Create IAM Role for required permissions\n\nNext, we create a new custom IAM role to capture the required permissions for\nWorkbench. Navigate to IAM > Roles and create a new role.\n\nClick the ADD PERMISSIONS button and add the below permissions to this role:\n\n  * compute.instanceGroupManagers.get\n\n  * container.apiServices.get\n\n  * container.apiServices.getStatus\n\n  * container.apiServices.list\n\n  * container.auditSinks.get\n\n  * container.auditSinks.list\n\n  * container.backendConfigs.get\n\n  * container.backendConfigs.list\n\n  * container.bindings.get\n\n  * container.bindings.list\n\n  * container.certificateSigningRequests.get\n\n  * container.certificateSigningRequests.getStatus\n\n  * container.certificateSigningRequests.list\n\n  * container.clusterRoleBindings.get\n\n  * container.clusterRoleBindings.list\n\n  * container.clusterRoles.get\n\n  * container.clusterRoles.list\n\n  * container.clusters.get\n\n  * container.clusters.list\n\n  * container.componentStatuses.get\n\n  * container.componentStatuses.list\n\n  * container.controllerRevisions.get\n\n  * container.controllerRevisions.list\n\n  * container.cronJobs.get\n\n  * container.cronJobs.getStatus\n\n  * container.cronJobs.list\n\n  * container.csiDrivers.get\n\n  * container.csiDrivers.list\n\n  * container.csiNodeInfos.get\n\n  * container.csiNodeInfos.list\n\n  * container.csiNodes.get\n\n  * container.csiNodes.list\n\n  * container.customResourceDefinitions.get\n\n  * container.customResourceDefinitions.getStatus\n\n  * container.customResourceDefinitions.list\n\n  * container.daemonSets.get\n\n  * container.daemonSets.getStatus\n\n  * container.daemonSets.list\n\n  * container.deployments.get\n\n  * container.deployments.getScale\n\n  * container.deployments.getStatus\n\n  * container.deployments.list\n\n  * container.endpointSlices.get\n\n  * container.endpointSlices.list\n\n  * container.endpoints.get\n\n  * container.endpoints.list\n\n  * container.events.get\n\n  * container.events.list\n\n  * container.frontendConfigs.get\n\n  * container.frontendConfigs.list\n\n  * container.horizontalPodAutoscalers.get\n\n  * container.horizontalPodAutoscalers.getStatus\n\n  * container.horizontalPodAutoscalers.list\n\n  * container.ingresses.get\n\n  * container.ingresses.getStatus\n\n  * container.ingresses.list\n\n  * container.initializerConfigurations.get\n\n  * container.initializerConfigurations.list\n\n  * container.jobs.get\n\n  * container.jobs.getStatus\n\n  * container.jobs.list\n\n  * container.mutatingWebhookConfigurations.get\n\n  * container.mutatingWebhookConfigurations.list\n\n  * container.namespaces.get\n\n  * container.namespaces.getStatus\n\n  * container.namespaces.list\n\n  * container.networkPolicies.get\n\n  * container.networkPolicies.list\n\n  * container.nodes.get\n\n  * container.nodes.getStatus\n\n  * container.nodes.list\n\n  * container.operations.get\n\n  * container.operations.list\n\n  * container.persistentVolumeClaims.get\n\n  * container.persistentVolumeClaims.getStatus\n\n  * container.persistentVolumeClaims.list\n\n  * container.persistentVolumes.get\n\n  * container.persistentVolumes.getStatus\n\n  * container.persistentVolumes.list\n\n  * container.petSets.get\n\n  * container.petSets.list\n\n  * container.podDisruptionBudgets.get\n\n  * container.podDisruptionBudgets.getStatus\n\n  * container.podDisruptionBudgets.list\n\n  * container.podPresets.get\n\n  * container.podPresets.list\n\n  * container.podSecurityPolicies.get\n\n  * container.podSecurityPolicies.list\n\n  * container.podTemplates.get\n\n  * container.podTemplates.list\n\n  * container.pods.get\n\n  * container.pods.getStatus\n\n  * container.pods.list\n\n  * container.priorityClasses.get\n\n  * container.priorityClasses.list\n\n  * container.replicaSets.get\n\n  * container.replicaSets.getScale\n\n  * container.replicaSets.getStatus\n\n  * container.replicaSets.list\n\n  * container.replicationControllers.get\n\n  * container.replicationControllers.getScale\n\n  * container.replicationControllers.getStatus\n\n  * container.replicationControllers.list\n\n  * container.resourceQuotas.get\n\n  * container.resourceQuotas.getStatus\n\n  * container.resourceQuotas.list\n\n  * container.roleBindings.get\n\n  * container.roleBindings.list\n\n  * container.roles.get\n\n  * container.roles.list\n\n  * container.runtimeClasses.get\n\n  * container.runtimeClasses.list\n\n  * container.scheduledJobs.get\n\n  * container.scheduledJobs.list\n\n  * container.serviceAccounts.get\n\n  * container.serviceAccounts.list\n\n  * container.services.get\n\n  * container.services.getStatus\n\n  * container.services.list\n\n  * container.statefulSets.get\n\n  * container.statefulSets.getScale\n\n  * container.statefulSets.getStatus\n\n  * container.statefulSets.list\n\n  * container.storageClasses.get\n\n  * container.storageClasses.list\n\n  * container.storageStates.get\n\n  * container.storageStates.getStatus\n\n  * container.storageStates.list\n\n  * container.storageVersionMigrations.get\n\n  * container.storageVersionMigrations.getStatus\n\n  * container.storageVersionMigrations.list\n\n  * container.thirdPartyObjects.get\n\n  * container.thirdPartyObjects.list\n\n  * container.thirdPartyResources.get\n\n  * container.thirdPartyResources.list\n\n  * container.tokenReviews.create\n\n  * container.updateInfos.get\n\n  * container.updateInfos.list\n\n  * container.validatingWebhookConfigurations.get\n\n  * container.validatingWebhookConfigurations.list\n\n  * container.volumeAttachments.get\n\n  * container.volumeAttachments.getStatus\n\n  * container.volumeAttachments.list\n\n  * container.volumeSnapshotClasses.get\n\n  * container.volumeSnapshotClasses.list\n\n  * container.volumeSnapshotContents.get\n\n  * container.volumeSnapshotContents.getStatus\n\n  * container.volumeSnapshotContents.list\n\n  * container.volumeSnapshots.get\n\n  * container.volumeSnapshots.list\n\n###  Create GCP service account for Workbench\n\nNext, we create a service account for Workbench to collect GKE logs and\nmonitor GKE clusters. Navigate to IAM > Service Accounts and create a new\nservice account.\n\nUnder service account details, type a Name, ID and Description and click\nCreate and Continue.\n\nNext, add 3 roles to the service account:\n\n  1. The “Browser” role. This allows Workbench to discover GKE clusters in the environment.\n\n  2. The custom Workbench role we created earlier.\n\n  3. The “Pub/Sub” subscriber role.\n\n### Note\n\nWe recommend adding a condition to limit this role to the pub/resource created\nearlier.\n\nFinally, for the last section, leave the blank defaults and click Done.\n\n###  Download GCP service account key\n\nWorkbench requires a service account key to authenticate to your GCP\nenvironment. To generate a key, navigate to IAM > Service Accounts. Locate the\nservice account you created earlier for Workbench, and select Manage Keys from\nthe Actions menu for that account.\n\nCreate a new key, and download the key in the default JSON format. We use this\nkey later in Workbench to onboard the GKE integration.\n\n###  Onboarding to Expel Workbench\n\nThe steps below outline how to finish onboarding in Workbench.\n\n  1. Log in to Workbench at https://workbench.expel.io.\n\n  2. Navigate to Settings > Security devices.\n\n  3. Click \\+ Add security device.\n\n  4. Select Google Kubernetes Engine.\n\n![Kub_Google_12_AddSecDev.png](https://support.expel.io/hc/article_attachments/11742328473747/uuid-c74391db-0e15-fab6-ec99-c5463afac7cf.png)\n\n  5. Name the device, provide a description, and fill in the Service Account auth JSON, and the pubsub subscription name.\n\n  6. 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"}

article_11742327047827.json

@@ -0,0 +1 @@
+{"title": "Amazon Elastic Kubernetes Service (EKS) setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/11742327047827-Amazon-Elastic-Kubernetes-Service-EKS-setup-for-Workbench", "date": "2022-12-01T15:04:57Z", "contents": "The Expel Amazon Elastic Kubernetes Service (EKS) consumes audit logs from the\nAWS platform through Kinesis. This visibility allows Workbench to identify\nactivity of interest in EKS, investigate, and notify organizations if action\nis recommended.\n\n![Kub_Amazon_1_Overview.png](https://support.expel.io/hc/article_attachments/11742313846547/uuid-63054dbd-f784-8502-1004-aed43158f216.png)\n\nComplete the steps below for each EKS cluster in each AWS account to be\nmonitored by Workbench.\n\n####  In this article\n\n  * Before you start\n\n  * Enable control plane logging for each EKS cluster\n\n  * Send EKS logs to a Kinesis stream\n\n  * Step 1: Create a new Kinesis data stream\n\n  * Step 2: Create an IAM role for CloudWatch log delivery\n\n  * Step 3: Route logs from CloudWatch to Kinesis stream\n\n    * Create IAM Role for Workbench\n\n    * Grant Workbench IAM Role required permissions\n\n    * Grant Workbench read-only cluster permissions\n\n  * Step 4: Connecting to Workbench\n\n  * Put these IP addresses in your allow list\n\n##  Before you start\n\nTo complete this procedure you need:\n\n  * Administrative access to Amazon Web Services (AWS).\n\n  * User privileges to create a Kinesis stream, CloudWatch log subscription, IAM role, and IAM policy.\n\n##  Enable control plane logging for each EKS cluster\n\nAt a minimum, Workbench requires logging of the **audit** events for each\ncluster. This provides visibility into activity affecting resources in the\ncluster (the “who, what, and when” we need to detect and respond to).\n\nUpdate logging configuration with the AWS CLI like this:\n\n    \n    \n    aws eks update-cluster-config \\\n    _--region_ **_< your-cluster-region>_** \\\n        _--name_ **_< your-cluster-name>_** _\\_ \n       _--logging '{\"clusterLogging\":[{\"types\":[\"audit\"],\"enabled\":true}]}'_\n    \n\nFor more information on configuring control plane logging, see the Amazon\nreference guide.\n\n##  Send EKS logs to a Kinesis stream\n\nAfter control plane logging is enabled, EKS begins sending logs to CloudWatch.\nNext, the logs must be routed from CloudWatch to a Kinesis data stream so that\nWorkbench can consume the logs in real time. Complete the steps below to route\nEKS logs to a Kinesis data stream.\n\n##  Step 1: Create a new Kinesis data stream\n\nCreate a stream with the AWS CLI like this:\n\n    \n    \n    _aws kinesis create-stream \\_\n    _--region_ **_< your-cluster-region>_** _\\_\n    _--stream-name_ **_< your-stream-name>_** _\\_\n    _--stream-mode-details '{\"StreamMode\": \"ON_DEMAND\"}'_\n\nWe recommend creating an `“ON_DEMAND”` stream to allow the stream to adjust\ncapacity based on demand.\n\n##  Step 2: Create an IAM role for CloudWatch log delivery\n\nAn IAM role is required to allow CloudWatch to deliver logs to your Kinesis\nstream.\n\nTo start, create a trust policy document that allows the CloudWatch service to\nassume the role:\n\n    \n    \n          _{_\n       \n        \n          _\"Statement\": {_\n        \n    \n          _\"Effect\": \"Allow\",_\n        \n        _\"Principal\": { \"Service\": \"logs._ **_< your-region>_** _.amazonaws.com\" },_\n        \n          _\"Action\": \"sts:AssumeRole\",_\n        \n        \n          _\"Condition\": {_\n        \n        _\"StringLike\": { \"aws:SourceArn\": \"arn:aws:logs:_ **_< your-region>_** _:_ **_< your-account-id>_** _:*\" }_\n        \n          _}_\n        \n        \n          _}_\n        \n        \n          _}_\n        \n    \n\nThen, create the IAM role supplying this trust document:\n\n    \n    \n        \n          _aws iam create-role \\_\n        \n    _--role-name_ **_< your-cloudwatch-role-name>_**\n        _--assume-role-policy-document file://_ **_< your-trust-document-file-path>_**\n    \n\nNext, create an IAM policy document that grants this role permissions to put\nrecords into your Kinesis stream:\n\n    \n    \n        \n          _{_\n        \n        \n          _\"Statement\": [_\n        \n        \n          _{_\n        \n        \n          _\"Effect\": \"Allow\",_\n        \n    \n          _\"Action\": \"kinesis:PutRecord\",_\n        \n        _\"Resource\": \"_ **_< your-kinesis-arn>_** _\"_\n        \n          _}_\n        \n        \n          _]_\n        \n        \n          _}_\n        \n    \n\nFinally, apply this IAM policy to the CloudWatch role:\n\n    \n    \n    aws iam put-role-policy \\\n         --role-name **< your-cloudwatch-role-name>** \\\n         --policy-name “ **< your-policy-name>**” \\\n        --policy-document file:// **< your-policy-document-path>**\n\n##  Step 3: Route logs from CloudWatch to Kinesis stream\n\nLogs can be routed to Kinesis with a CloudWatch log group subscription filter.\nCreate this filter with the AWS CLI like this:\n\n    \n    \n    aws logs put-subscription-filter \\\n    _--region_ **_< your-cluster-region>_** _\\_\n    _–log-group-name_ **_< your-cluster-log-group-name>_** _\\_\n         –filter-name “AllEKSLogs” \\\n         –filter-pattern “”\n    _–destination-arn_ **_< your-kinesis-stream-arn>_**\n    _--role-arn_ **_< your-cloudwatch-role>_**\n\n###  Create IAM Role for Workbench\n\nTo authenticate to your AWS account and retrieve logs, Workbench requires an\nIAM role. If you already have an Workbench IAM role for another Workbench\nintegration (like CloudWatch or AWS GuardDuty), this existing role can be\nreused and you can go to: **Grant Expel IAM Role required permissions**.\n\nTo start, create a trust policy document that allows Workbench to assume the\nrole:\n\n    \n    \n          \n          _{_\n        \n          \n          _\"Statement\":_\n        \n          \n          _[_\n        \n        \n          _{_\n        \n        \n          _\"Effect\": \"Allow\",_\n        \n        \n          _\"Principal\":_\n        \n        \n          _{_\n        \n        \n          _\"AWS\": \"arn:aws:iam::012205512454:user/ExpelCloudService\"_\n        \n        \n          _},_\n        \n        \n          _\"Action\": \"sts:AssumeRole\",_\n        \n        \n          _\"Condition\":_\n        \n        \n          _{_\n        \n        \n          _\"StringEquals\":_\n        \n        \n          _{_\n        \n        _\"sts:ExternalId\": \"_ **_< your-customer-guid>_** _\"_\n        \n          _}_\n        \n        \n          _}_\n        \n        \n          _}_\n        \n        \n          _]_\n        \n        \n          _}_\n        \n    \n\nThen, create the IAM role supplying this trust document:\n\n    \n    \n          _aws iam create-role \\_\n        \n        _--role-name_ **_< your-expel-role-name>_**\n        _--assume-role-policy-document file://_ **_< your-trust-document-file-path>_**\n\n###  Grant Workbench IAM Role required permissions\n\nWorkbench requires IAM permissions to retrieve logs from Kinesis, as well as\ninvestigate activity of interest affecting your EKS clusters.\n\nFirst, create an IAM policy document granting Workbench required permissions\nfor Kinesis and EKS:\n\n    \n    \n        \n          _{_\n        \n        \n          _\"Version\": \"2012-10-17\",_\n        \n        \n          _\"Statement\": [_\n        \n        _{_\n        \n          _\"Effect\": \"Allow\",_\n        \n        \n          _\"Action\": [_\n        \n        \n          _\"kinesis:DescribeLimits\",_\n         \n        \n          _\"kinesis:DescribeStream\",_\n        \n        \n          _\"kinesis:DescribeStreamSummary\",_\n        \n        \n          _\"kinesis:GetRecords\",_\n        \n        \n          _\"kinesis:GetShardIterator\",_\n        \n        \n          _\"kinesis:ListShards\"_\n        \n        \n          _],_\n        \n        _\"Resource\": \"_ **_< your kinesis stream arn>_** _\"_\n         \n          _},_\n        \n        \n          _{_\n        \n         \n          _\"Effect\": \"Allow\",_\n        \n        \n          _\"Action\": [_\n        \n        \n          _\"eks:AccessKubernetesApi\",_\n        \n        \n          _\"eks:DescribeCluster\",_\n        \n        \n          _\"eks:DescribeNodegroup\",_\n        \n        \n          _\"eks:ListClusters\",_\n         \n        \n          _\"eks:ListNodegroups\",_\n        \n        \n          _\"eks:ListUpdates\",_\n        \n        \n          _\"sts:GetCallerIdentity\",_\n        \n        \n          _\"ec2:DescribeRegions\",_\n        \n        \n          _\"autoscaling:DescribeAutoScalingGroups\"_\n         \n                      ],\n        \n        \n          _\"Resource\": \"*\"_\n        \n        \n          _}_\n        \n        \n          _]_\n        \n        \n          _}_\n        \n    \n\nThen, apply this policy to the Expel IAM role:\n\n    \n    \n    aws iam put-role-policy \\\n              --role-name **< your-expel-role-name>** \\ \n            --policy-name “ **< your-policy-name>**” \\\n            --policy-document file:// **< your-policy-document-path>**\n    \n\n###  Grant Workbench read-only cluster permissions\n\nExpel suggests providing limited read-only access to your EKS clusters to\nenable deep investigation of interesting activity. These permissions can be\nfine-tuned based on your needs. Workbench can deliver service without this\naccess, but it significantly limits our ability to thoroughly investigate\nactivity in your clusters.\n\nFirst, create an Expel ClusterRole manifest to grant limited, read-only\npermissions:\n\n    \n    \n        \n          _apiVersion: rbac.authorization.k8s.io/v1_\n        \n        \n          _kind: ClusterRole_\n        \n        \n          _metadata:_\n        \n        \n          _name: expel-reader-clusterrole_\n            \n          _rules:_\n        \n        \n          _- apiGroups:_\n        \n        \n          _- \"\"_\n        \n        \n          _- admissionregistration.k8s.io_\n        \n        \n          _- apps_\n        \n        \n          _- networking.k8s.io_\n        \n        \n          _- rbac.authorization.k8s.io_\n        \n        \n          _resources:_\n        \n        \n          _- apiservices_\n        \n        \n          _- clusterrolebindings_\n        \n        \n          _- clusterroles_\n        \n        \n          _- cronjobs_\n        \n        \n          _- daemonsets_\n        \n        \n          _- deployments_\n        \n        \n          _- events_\n        \n        \n          _- flowschemas_\n        \n        \n          _- horizontalpodautoscalers_\n        \n        \n          _- ingressclasses_\n        \n        \n          _- ingresses_\n        \n        \n          _- jobs_\n        \n        \n          _- localsubjectaccessreviews_\n        \n        \n          _- mutatingwebhookconfigurations_\n        \n        \n          _- namespaces_\n        \n        \n          _- networkpolicies_\n        \n        \n          _- nodes_\n        \n        \n          _- persistentvolumes_\n        \n        \n          _- poddisruptionbudgets_\n        \n        \n          _- pods_\n        \n        \n          _- podsecuritypolicies_\n        \n        \n          _- podtemplates_\n        \n        \n          _- replicasets_\n        \n        \n          _- rolebindings_\n        \n        \n          _- roles_\n        \n        \n          _- selfsubjectaccessreviews_\n        \n        \n          _- selfsubjectrulesreviews_\n        \n        \n          _- serviceaccounts_\n        \n        \n          _- services_\n        \n        \n          _- statefulsets_\n        \n        \n          _- subjectaccessreviews_\n        \n        \n          _- tokenreviews_\n        \n        \n          _- validatingwebhookconfigurations_\n        \n        \n          _- volumeattachments_\n        \n        \n          _verbs:_\n        \n        \n          _- get_\n         \n       \n          _- list_\n        \n\nUse kubectl to apply this role:\n\n    \n    \n        = _kubectl apply -f_ **_< your-expel-role-manifest>_**  \n\nNext, bind this role to a Workbench user with a ClusterRoleBinding. Create a\nClusterRoleBinding manifest:\n\n    \n    \n        \n          _kind: ClusterRoleBinding_\n        \n        \n          _apiVersion: rbac.authorization.k8s.io/v1_\n        \n        \n          _metadata:_\n        \n        \n          _name: expel-reader-clusterrolebinding_\n        \n        \n          _subjects:_\n        \n        \n          _- kind: User_\n        \n        \n          _name: expel-user_\n        \n        \n          _roleRef:_\n        \n        \n          _kind: ClusterRole_\n        \n        \n          _name: expel-reader-clusterrole_\n        \n        \n          _apiGroup: rbac.authorization.k8s.io_\n        \n\nUse kubectl to apply this role:\n\n    \n    \n    _kubectl apply -f_ **_< your-expel-role-binding-manifest>_**\n\nFinally, map the Workbench IAM role to the in-cluster user “expel-user”. This\nrequires editing the “aws-auth” configMap with **EKS ctl**.\n\n    \n    \n     \n          _eksctl create iamidentitymapping \\_\n        \n        _--cluster_ **_< your-cluster-name>_** _\\_\n        _--region_ **_< your-region>_** _\\_\n        _--arn_ **_< your-expel-role-arn>_** _\\_\n        \n          _--username expel-user_\n        \n    \n\nYou can confirm the mapping is created by running:\n\n    \n    \n    _eksctl get iamidentitymapping --cluster_ **_< your-cluster-name>_** _--region_ **_< your-region>_**\n\n##  Step 4: Connecting to Workbench\n\nThe steps below outline how to finish connecting to Workbench.\n\n  1. Log in to Workbench at https://workbench.expel.io.\n\n  2. Navigate to Settings > Security devices.\n\n  3. Click +Add security device.\n\n  4. Select Amazon Elastic Kubernetes Service (EKS).\n\n![Kub_Amazon_2_AddSecDev.png](https://support.expel.io/hc/article_attachments/11742327407123/uuid-84d48493-7573-0adb-802a-3aa552fe62ae.png)\n\n  5. Name the device, provide a description, and fill in the Role ARN, Role Session Name, Region, External ID, and Kinesis Stream Name.\n\n  6. Click Save.\n\n##  Put these IP addresses in your allow list\n\n  * 34.75.13.114\n\n  * 34.75.152.7\n\n  * 35.243.190.98\n\n  * 104.196.158.205\n\n  * 34.75.81.28\n\n  * 34.75.210.18\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"}

article_12116548434067.json

@@ -0,0 +1 @@
+{"title": "AWS CloudTrail setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/12116548434067-AWS-CloudTrail-setup-for-Workbench", "date": "2022-12-13T18:50:35Z", "contents": "This article contains links to all the ways you can connect your new or\nexisting AWS CloudTrail to the Expel Workbench.\n\n####  In this article\n\n  * Onboarding a new CloudTrail\n\n  * Onboarding an existing AWS CloudTrail\n\n##  Onboarding a new CloudTrail\n\nYou can onboard new CloudTrails in 1 of 2 ways:\n\n  * Use our AWS onboarding wizard.\n\n![AWS_Cloudtrail_Wizard_set_1.png](https://support.expel.io/hc/article_attachments/12116522023443/uuid-2648e29f-ce8c-fe52-d459-4f2c0c93cc10.jpg)\n\n  * Connect manually.\n\nIf you want Expel to create new CloudTrails on your behalf, use our AWS\nOnboarding Wizard in Workbench.\n\n### Note\n\nCreating duplicate CloudTrails can result in additional AWS costs. Do not use\nthe wizard if you want to connect an existing CloudTrail.\n\nOur wizard supports creating new CloudTrails using:\n\n  * CloudFormation Templates: You can use AWS CloudFormation templates to perform the necessary configuration for an individual account or organization. If you’re onboarding an AWS organization, it creates a CloudFormation StackSet to configure the permissions on each account within the organization. It can even automatically run on accounts you create in the future under the organization. Don’t worry, we won’t run anything in your AWS account. We instead populate CloudFormation with the right steps; you review it and decide to execute.\n\n  * Terraform: We present an open source, fully transparent Terraform module which creates necessary AWS resources used to securely transfer CloudTrail logs to Workbench. All of the resources that we allocate are listed here: https://registry.terraform.io/modules/expel-io/cloudtrail/aws/latest?tab=resources. By default, all methods of communication between these resources and AWS and Workbench are secured by encryption. All means of data storage (S3) follow AWS best practices—access logging enabled, bucket versioning enabled, zero public access.\n\nIf you're...\n\n|\n\nuse this...  \n  \n---|---  \n  \nusing the wizard, setting up new AWS CloudTrails\n\n|\n\ngo to the wizard  \n  \nusing the wizard, setting up new AWS CloudTrails with Terraform\n\n|\n\ngo to the wizard and select Terraform  \n  \n##  Onboarding an existing AWS CloudTrail\n\nTo onboard an existing CloudTrail, the instructions vary depending upon your\nuse of AWS Control Tower:\n\nIf you're...\n\n|\n\nuse this...  \n  \n---|---  \n  \nmanually setting up new AWS CloudTrails\n\n|\n\nthe new AWS CloudTrail steps  \n  \nconnecting an existing CloudTrail\n\n|\n\nthe existing installation steps  \n  \nconnecting an existing CloudTrail that includes Control Tower\n\n|\n\nthe Control Tower connection steps  \n  \nOur Product team is developing a process for onboarding an existing CloudTrail\nusing the AWS wizard. We will update this article when the procedure is ready.\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"}

article_12391858961171.json

@@ -0,0 +1 @@
+{"title": "AWS CloudTrail: Existing CloudTrail with Control Towersetup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/12391858961171-AWS-CloudTrail-Existing-CloudTrail-with-Control-Towersetup-for-Workbench", "date": "2022-12-22T16:21:16Z", "contents": "This article describes how to connect your existing AWS CloudTrail with AWS\nControl Tower to the Expel Workbench.\n\nIf you're...\n\n|\n\nuse...\n\n|\n\nNotes  \n  \n---|---|---  \n  \nconnecting an existing CloudTrail that includes Control Tower,\n\n|\n\nthis article\n\n|\n\nYou need the following to integrate a Control Tower environment with\nWorkbench.\n\n  * An AWS Control Tower with Landing Zone.\n\n  * Administrator privileges in the AWS Control Tower management and Log Archive accounts.\n\n  \n  \nsetting up new AWS CloudTrails\n\n|\n\nthe onboarding wizard\n\n|\n\nYou can also use the manual connection procedure.  \n  \nconnecting an existing CloudTrail\n\n|\n\nthe existing installation steps\n\n|  \n  \n####  In this article\n\n  * About connecting your device\n\n  * Before you start\n\n  * About console permissions in your devices\n\n  * Permissions description and explanation\n\n  * Step 1: Setup ExpelIAM role and policy\n\n  * Step 2: Update CloudTrail CMK policy if applicable\n\n  * Step 3: Confirm S3 log bucket ACL settings\n\n  * Step 4: Setup SNS topic for S3 notifications\n\n    * Option 1: Using CloudFormation (recommended)\n\n    * Option 2: Manual setup\n\n  * Step 5: Setup SQS queue for SNS notification\n\n  * Step 6: Subscribe SQS to SNS topic\n\n  * Step 7: Setup KMS encryption for SNS and SQS\n\n  * Step 8: Enable S3 event notifications to SNS topic\n\n  * Step 9: Grant ExpelIAM Role necessary access\n\n  * Step 10: Complete Workbench setup\n\n##  About connecting your device\n\nConnecting your device to Workbench allows Workbench to ingest the logs. AWS\nlogs include a great deal of information that can take hours to manually\nreview. And not all AWS alerts need attention.\n\nExpel collects data through direct API integrations with the AWS platform.\nExpel supports authentication with an IAM Role (recommended) or IAM User with\na set of read-only permissions. To collect data, Expel communicates directly\nwith AWS APIs (like AWS GuardDuty and Inspector) and pulls in CloudTrail data\nfrom S3.\n\nExpel processes all product alerts with a library of Expel created rules\nfocused on the MITRE attack framework. This makes it possible for a product\nalert that wouldn't be reviewed to be elevated to an Expel alert.\n\n##  Before you start\n\n**This process requires you to download the attachment, found at the end of\nthis article. The attachment includes the code blocks you need to complete\nthis process.**\n\n### Note\n\nThis article assumes the default service control policies are in play. If you\nrun into any issues during setup, contact your engagement manager for help.\n\n##  About console permissions in your devices\n\nAs you connect your devices to Workbench, you provide Workbench access to\nthose devices through permissions in the devices. These permissions vary from\n1 device technology to another, but we typically need at least Read access to\nyour devices to pull in any logs from those devices into Workbench.\n\nWithout minimum permissions to your devices, the SOC analysts are limited in\ntheir insight into your technology. This can mean they surface more benign\nalerts to your team for further investigation, resulting in increasing the\nworkload for your team, and resulting in alert fatigue.\n\nIf you grant Read access to your devices, we can investigate the device and\nthe logs more deeply and surface relevant alerts to you in Workbench. Allowing\nExpel visibility into the console of your security devices helps our SOC\nanalysts make better decisions on whether an alert is benign or malicious. It\nalso allows our SOC analysts to perform health checks to make sure Workbench\nis not missing alerts from your security devices. Depending on what your\norganization purchased from Expel, the SOC analysts may even be able to\ncontain and/or remediate the issues on your behalf.\n\nUltimately, the more permissions you can grant Workbench, the better and\nfaster the SOC analysts can find and investigate alerts in your environment.\n\n###  Permissions description and explanation\n\nExpel requires these permissions when connecting to AWS CloudTrail. These\npermissions are set to **Read** , except as shown below.\n\n**This permission...**\n\n|\n\n**does this...**\n\n|\n\n**Notes**  \n  \n---|---|---  \n  \nec2:DescribeRegions\n\n|\n\nDynamically list all enabled regions for a customer account\n\n|  \n  \nec2:DescribeInstances\n\n|\n\nCloud investigative actions and inventory\n\n|\n\nAllows SOC analysts to triage issues and get additional content for the\nenvironment.  \n  \nec2:DescribeSecurityGroups  \n  \niam:List*  \n  \niam:Get*  \n  \nlambda:GetFunction  \n  \nrds:DescribeDBInstances  \n  \nrds:ListTagsForResource  \n  \neks:DescribeCluster  \n  \neks:ListClusters  \n  \necs:ListContainerInstances  \n  \necs:DescribeContainerInstances  \n  \necs:DescribeClusters  \n  \necs:ListClusters  \n  \ns3:GetBucketNotification  \n  \ns3:GetEncryptionConfiguration  \n  \ncloudtrail:GetTrail  \n  \ncloudtrail:DescribeTrails  \n  \ncloudtrail:GetTrailStatus  \n  \ncloudtrail:ListTrails  \n  \norganizations:ListAccounts\n\n|\n\nEnumerate accounts in an org\n\n|  \n  \nsqs:DeleteMessage\n\n|\n\nRemove Processed messages from the queue\n\n|\n\nRequires **Write** permission.  \n  \nsqs:ReceiveMessage\n\n|\n\nRead messages\n\n|  \n  \ns3:GetObject\n\n|\n\nDownload cloudtrail log files\n\n|  \n  \nec2:DescribeVolumes\n\n|\n\nCloud investigative actions and inventory\n\n|\n\nAllows SOC analysts to triage issues and get additional content for the\nenvironment.  \n  \necs:DescribeTaskDefinition\n\n|\n\nInventory\n\n|  \n  \necs:ListTaskDefinitions  \n  \nconfig:ListDiscoveredResources  \n  \nconfig:GetDiscoveredResourceCounts  \n  \nlambda:ListFunctions\n\n|\n\nCloud investigative actions and inventory\n\n|\n\nAllows SOC analysts to triage issues and get additional content for the\nenvironment.  \n  \nlightsail:GetInstances  \n  \nlightsail:GetRegions  \n  \ns3:ListAllMyBuckets  \n  \nkms:Decrypt\n\n|\n\nDecrypt S3 buckets\n\n|  \n  \norganizations:DescribeOrganization\n\n|\n\nOrganization information\n\n|\n\nRetrieves information about the organization the user's account belongs to.  \n  \n##  Step 1: Setup ExpelIAM role and policy\n\nIn this step we create a permissions policy to assign to the IAM Role.\n\n### Important\n\nFor AWS Control Tower the primary Expel role is created within the\norganization’s Log Archive account where the CloudTrail S3 Log Bucket exists.\n\nThe role and policy must be replicated across all the other accounts in the\norganization to allow Expel to perform investigative actions within your AWS\nenvironment. The policy replicated to the other non-Log Archive sub-accounts\ncan be modified to exclude the policy elements providing access permissions to\nthe S3 resources if necessary.\n\n  1. Create IAM Role and Policy in management account.\n\n    * Navigate to the CloudFormation > Stacks service portal.\n\n    * Click Create Stack (with new resources) and select Upload a template file as the source.\n\n    * Upload a json file containing the stack template. You can find that code in the attachment for this article in the Step 1 area.\n\n    * Provide a relevant name to the stack, such as ExpelIAMStack.\n\n    * In the WorkbenchExternalID parameter field, type in your Workbench GUID, then click Next.\n\n### Note\n\nYou can find this GUID by logging into Workbench and then navigating to\nhttps://workbench.expel.io/settings/organizations. The redirected URL contains\nthe value to be used for this parameter.\n\n![image4.jpg](https://support.expel.io/hc/article_attachments/12391877518227/uuid-a9d74a89-4757-81b0-a78f-a5d899eb69f9.jpg)  \n---  \n  \n    * You can leave all defaults for configuring the stack options and click Next.\n\n    * Verify the stack details, then check the acknowledgement and click Submit.\n\n    * The new IAM role and attached policy should exist for Expel within the management account on completion of the stack.\n\n  2. Create IAM Role and Policy in all sub accounts.\n\n    * Navigate to the CloudFormation > Stacksets service portal.\n\n    * Click Create StackSet and select Upload a template file as the source.\n\n    * Follow the same process to fill out the stackset details as was done in deploying the stack above (Step 1.1).\n\n##  Step 2: Update CloudTrail CMK policy if applicable\n\n### Note\n\nYou can skip this step if your CloudTrail is not configured to encrypt the S3\nlogs using CMK. Otherwise, we need to update the key policy to provide\nWorkbench with the kms:Decrypt permission so that we can properly get objects\nfrom the S3 bucket containing the CloudTrail logs.\n\nYou can determine if this step applies to you by navigating to Services >\nCloudTrail > Trails and then selecting the trail created by Control Tower in\nyour management account. In the General details section you see a value under\nLog file SSE-KMS encryption and an associated AWS KMS key populated as well.\n\n  1. Navigate to the CMK key used to encrypt the CloudTrail logs.\n\n    * You can find the specific key arn by looking for AWS KMS Key in the General details section of the CloudTrail.\n\n  2. Select the Key policy tab and then click Edit to change it.\n\n  3. Add the decrypt permission to the existing list of policy statements. You can find that code in the attachment for this article in the Step 2 area.\n\n### Note\n\nMake sure to update the principal value with the correct arn path to the Expel\nRole created in the Log Archive account as a result of Step 1.2 via the\nStackSet.\n\n  4. Click Save changes.\n\n### Important\n\nThe following steps (Steps 3 - 8) must be performed from within your AWS\nControl Tower Log Archive account. See the AWSdocumentation for any\nclarification on what that is.\n\n##  Step 3: Confirm S3 log bucket ACL settings\n\n### Note\n\nAmazon S3 access control lists allow you to manage access to buckets and any\nobjects contained within. We want to confirm that the S3 bucket created in\nyour log archive account allows the bucket owner (Log Archive) and Expel by\nextension through the deployed role read permissions for the objects within.\n\n  1. Navigate to Services > S3 > Buckets > [Your S3 Log Bucket] (usually follows the naming scheme “aws-controltower-logs-”.\n\n  2. Select the Permissions tab, then look at the Object Ownership section to confirm the current ACL setting.\n\n  3. If you keep ACLs enabled on the bucket then confirm the current Object Ownership is set to Bucket owner preferred.\n\n### Important\n\nAWS recommends that you disable ACLs on S3 for a majority of modern use-cases\nwhich then delegate ownership to the bucket owner account (source).\n\n##  Step 4: Setup SNS topic for S3 notifications\n\n###  Option 1: Using CloudFormation (recommended)\n\n### Important\n\nIf you choose this option, then you can skip to Step 8 when you’re done.\n\n  1. Navigate to Services > CloudFormation > Stacks and click Create stack (with new resources).\n\n  2. In the Specify template section select Upload a template file. Then upload a json file containing the stack template. Then click Next. You can find that code in the attachment for this article in the Step 4, Option 1 area.\n\n  3. Fill in a name for the stack.\n\n  4. Fill in the following required parameters.\n\n    * S3LogBucketARN: the ARN associated with the S3 Bucket in your Log Archive account that retains the CloudTrail logs.\n\n    * CloudTrailKeyARN: the ARN for the customer-managed kms key configured on your CloudTrail (in your management account).\n\n  5. Proceed through the rest of the wizard keeping the defaults, then click Submit to initiate the stack.\n\n  6. After the stack creation completes, make note of all values returned in the Outputs tab of the stack console. You need these returned values to complete setup in Workbench.\n\n    * RoleARN: the IAM Role created in the log archive account needed to complete setup in Workbench.\n\n    * SqsURL: the SQS url path needed to complete setup of in Workbench.\n\n### Important\n\nYou can now skip directly to Step 8.\n\n####  Option 2: Manual setup\n\n### Caution\n\nMake sure to create the SNS topic in the same region as the S3 bucket\nCloudTrail events are being sent to!\n\n  1. Navigate to Services > Simple Notification Service > Topics and click Create Topic.\n\n  2. On the next screen, select Standard as the Type and create a Topic Name.\n\n  3. Under Access Policy, select Advanced.\n\nIn the JSON editor, paste the below policy substituting the YOUR_TOPIC_ARN and\nYOUR_S3_ARN fields with your values. This policy allows S3 to publish\nnotifications to the topic for your CloudTrail bucket. You can find that code\nin the attachment for this article in the Step 4, Option 2 area.\n\n  4. Click Create Topic.\n\n##  Step 5: Setup SQS queue for SNS notification\n\nIn this step, we create a new SQS queue for S3 notifications. Workbench polls\nnotifications from this queue to know when new CloudTrail data is added.\n\n### Caution\n\nMake sure you create the SQS queue in the same region as the SNS topic and S3\nbucket!\n\n  1. Navigate to Services > Simple Queue Service > Queues and click Create queue.\n\n  2. On the next screen, select Standard Queue and name the new queue.\n\n    * Visibility timeout: 30 Seconds.\n\n    * Message retention period: 7 days.\n\n    * Delivery delay: 0 Seconds.\n\n    * Maximum message size: 256 KB.\n\n    * Receive message wait time: 0 Seconds.\n\n  3. Under Access Policy, select Advanced.\n\n  4. In the JSON editor, paste the policy substituting the YOUR_SQS_QUEUE_ARN and YOUR_SNS_TOPIC_ARN fields with your values. You can find that code in the attachment for this article in the Step 5 area.\n\n##  Step 6: Subscribe SQS to SNS topic\n\nNow that we created an SNS topic and SQS queue, we need to configure SNS to\nsend events to the SQS queue.\n\n  1. Navigate to Services > Simple Notification Service > Subscriptions and click Create subscription.\n\n  2. On the next screen, configure the required fields to complete the subscription.\n\nField\n\n|\n\nValue  \n  \n---|---  \n  \nTopic ARN\n\n|\n\nYour SNS Topic ARN  \n  \nProtocol\n\n|\n\nSelect Amazon SQS  \n  \nEndpoint\n\n|\n\nYour SNS Queue ARN  \n  \nEnable raw message delivery\n\n|\n\n###  Important\n\nSelecting enable raw message delivery makes sure SNS doesn’t add extra\nmetadata headers to the message when it sends to SQS. Make sure you select\nthis!  \n  \n  3. Click Create subscription to finish this step.\n\n##  Step 7: Setup KMS encryption for SNS and SQS\n\n  1. Navigate to Services > Key Management Service (KMS) > Customer managed keys and click Create Key.\n\n  2. Retain the default configuration values as shown below, then click Next.\n\n  3. Fill in values for the alias and description for the key, then click Next.\n\n  4. Select any additional key administrators for the new key, then click Next until you get to the Review page.\n\n  5. Look for the Key policy generated for this key in the Review page and add the policies to the statement list to give S3 & SNS the right perms they need to decrypt with this key. You can find that code in the attachment for this article in the Step 7 area.\n\n  6. Click Finish to complete the creation of the new key.\n\n  7. Enable Encryption on the SNS topic you created in Step 3 using the new key.\n\n    * Navigate to Services > Simple Notification Service > Topics > YourTopic.\n\n    * Click Edit, then click Encryption on.\n\n    * In the Customer master key (CMK) selection, click the KMS key you created above.\n\n    * Click Save changes.\n\n  8. Enable Encryption on the SQS topic you created in Step 4 using the new key.\n\n    * Navigate to Services > Simple Queue Service > Queues > YourQueue.\n\n    * Click Edit, then toggle the Encryption option on.\n\n    * Set the Server-side encryption option to Enabled.\n\n    * Set the Encryption key type to SSE-KMS.\n\n    * In the Customer master key selection, click the KMS key you created above.\n\n    * Click Save.\n\n##  Step 8: Enable S3 event notifications to SNS topic\n\nIn this step, we configure the CloudTrail S3 bucket to send SNS notifications\nwhen CloudTrail adds logs to the bucket.\n\n  1. Navigate to Services > S3 > Your S3 CloudTrail Bucket.\n\n  2. Open Properties for your S3 bucket and navigate to Event notifications. Click Create event notification.\n\n  3. On the next screen:\n\n    * Create a name for your notification rule.\n\n    * Select All object create events from the Event types section.\n\n    * Select SNS topic from the Destination section.\n\n    * Select your SNS topic created in Step 3.\n\n  4. Click Save changes.\n\n##  Step 9: Grant ExpelIAM Role necessary access\n\n### Tip\n\nSkip this step if you onboarded the Expel resources with CloudFormation using\nStep 4, Option 1. You can go to Step 10.\n\nAt this point we configured S3 notifications → SNS topic → SQS queue. The\nfinal step involves granting the existing ExpelIAM Role the necessary access\nto poll events from the SQS queue and the S3 bucket.\n\n  1. Navigate to Services > IAM > Roles.\n\n  2. Create and add a new inline policy to the Expel Role that was propagated to the Log Archive account as part of Step 1.\n\n### Tip\n\nName it ExpelAssumeRole if you used the provided StackSet template. The policy\ngrants the permissions. You can find that code in the attachment for this\narticle in the Step 9 area.\n\n##  Step 10: Complete Workbench setup\n\nCongratulations! You configured S3 notifications to an SQS queue through SNS.\nGo through Step 8: Register AWS in Workbench of the AWS CloudTrail: New\nCloudTrail setup for Workbench complete setup to register the integration in\nWorkbench. Make sure to select Manual Connection for the connection type.\n\nYou require the following details to complete this step:\n\n  * Role ARN: Expel Role ARN created in Step 1 specific to the Log Archive account.\n\n  * SQS URL: the full URL path of the SQS created in Step 4.\n\n  * Organization Management Account: the account ID of your AWS organization’s management account.\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"}

article_12871722483347.json

@@ -0,0 +1 @@
+{"title": "About console permissions in your devices", "url": "https://support.expel.io/hc/en-us/articles/12871722483347-About-console-permissions-in-your-devices", "date": "2023-01-09T15:29:41Z", "contents": "As you connect your devices to Workbench, you provide Workbench access to\nthose devices through permissions in the devices. These permissions vary from\n1 device technology to another, but we typically need at least Read access to\nyour devices to pull in any logs from those devices into Workbench.\n\nWithout minimum permissions to your devices, the SOC analysts are limited in\ntheir insight into your technology. This can mean they surface more benign\nalerts to your team for further investigation, resulting in increasing the\nworkload for your team, and resulting in alert fatigue.\n\nIf you grant Read access to your devices, we can investigate the device and\nthe logs more deeply and surface relevant alerts to you in Workbench. Allowing\nExpel visibility into the console of your security devices helps our SOC\nanalysts make better decisions on whether an alert is benign or malicious. It\nalso allows our SOC analysts to perform health checks to make sure Workbench\nis not missing alerts from your security devices. Depending on what your\norganization purchased from Expel, the SOC analysts may even be able to\ncontain and/or remediate the issues on your behalf.\n\nUltimately, the more permissions you can grant Workbench, the better and\nfaster the SOC analysts can find and investigate alerts in your environment.\n\n"}

article_12925742896787.json

@@ -0,0 +1 @@
+{"title": "What are Expel alerts?", "url": "https://support.expel.io/hc/en-us/articles/12925742896787-What-are-Expel-alerts-", "date": "2023-01-10T21:54:24Z", "contents": "Expel alerts are vendor alerts that appear in Workbench for analysts to\ntriage, investigate, and respond to. An Expel alert is created when one or\nmore vendor alerts satisfy the rule logic in our detection engines. You can\nview Expel alerts on the Alerts analysis dashboard.\n\nEach Expel alert is assigned a severity, which may not always match the\nseverity of the originating vendor alert(s). Expel alerts are _de facto_ tier\n1 when mapping back to the traditional security operations center (SOC)\nprocess. New Expel alerts trigger Ruxie, our automated workflow bot. Ruxie\ncreates new investigative actions, looks for similar Expel alerts, and even\ncloses the alert in certain circumstances.\n\nAs our SOC analysts and Ruxie triage Expel alerts, they can end up proceeding\nin 3 different ways:\n\n  * **Closed** : Expel alerts are closed if the vendor alert is benign or doesn’t fall into a category we can investigate further. For example, potentially unwanted programs (PUP) or potentially unwanted applications (PUA).\n\n  * **Escalated to investigation** : if there’s a potential of malicious behavior or our SOC analysts need more information, we create an investigation from that Expel alert.\n\n  * **Escalated to incident** : if an Expel alert is explicitly malicious, it is immediately escalated to an incident.\n\nIn the case of phishing Expel alerts, instead of a vendor alert being both the\nsource/cause of the Expel alert, it’s a phishing submission.\n\nIn the Expel alert/triage phase Ruxie may contact your organization to ask\n“did you expect this?”.\n\nIn both cases, Expel alerts are closed with a reason and a comment if they are\ndetermined to be benign in nature.\n\n"}

article_12925743005331.json

@@ -0,0 +1 @@
+{"title": "What are incidents?", "url": "https://support.expel.io/hc/en-us/articles/12925743005331-What-are-incidents-", "date": "2023-01-10T21:54:25Z", "contents": "If the SOC analysts determine there's a threat in an organization’s\nenvironment, an incident is created or an investigation is promoted to an\nIncident.\n\nIncidents are similar to investigations in that they include investigative\nactions and have a similar look and feel. Incidents, however, include\nfindings. These are the details to the common questions:\n\n  * What is it?\n\n  * Where is it?\n\n  * When did it get here?\n\n  * How did it get here?\n\nIncidents can also include remediation and resilience actions.\n\n"}

article_12925743051411.json

@@ -0,0 +1 @@
+{"title": "What are investigations?", "url": "https://support.expel.io/hc/en-us/articles/12925743051411-What-are-investigations-", "date": "2023-01-10T21:54:26Z", "contents": "An Expel alert becomes an investigation if the SOC analysts think a more in-\ndepth analysis of the activity is needed. In this case, the Expel alert that\nraised suspicion is called the lead Expel alert.\n\nInvestigations are where the SOC analysts can perform additional actions\n(investigative actions) to uncover more information to help determine the\nscope and nature of the activity that occurred proximate to the time of the\nExpel alert.\n\nIn an investigation, you and the SOC analysts can collaborate and share\ninformation in Workbench to reach a conclusion through comments, findings, and\ninvestigative actions.\n\nIf the activity is determined to be benign, the investigation is closed with\nan explanation. If not, the investigation is promoted to an incident.\n\n"}

article_12925743290387.json

@@ -0,0 +1 @@
+{"title": "What are vendor alerts?", "url": "https://support.expel.io/hc/en-us/articles/12925743290387-What-are-vendor-alerts-", "date": "2023-01-10T21:54:29Z", "contents": "Vendor alerts are the Expel-normalized representation of signal coming from\nintegrations you connected to Workbench. Vendor alerts are signal in the form\nof alerts from security technologies such as endpoint detection and response\n(EDR) providers, next-gen firewalls (NGFW), or security information and event\nmanagement (SIEM) systems. Vendor alerts can also include audit events\nproduced by software Expel monitors. For example, AssumeRole events from AWS\nCloudTrail, or login events from Microsoft Azure AD, and so on.\n\nEvery vendor alert is associated with a specific security device in Workbench.\nVendor alerts don’t have a status and we don’t assign them. Our detection\nengines evaluate vendor alerts to produce Expel alerts if they rise to the\nlevel of requiring additional attention.\n\n"}

article_12925746962195.json

@@ -0,0 +1 @@
+{"title": "What are findings?", "url": "https://support.expel.io/hc/en-us/articles/12925746962195-What-are-findings-", "date": "2023-01-10T21:54:25Z", "contents": "Findings are where security analysts document, in detail, the answers to\nquestions such as: What is it? Where is it? When did it get here? How did it\nget here?\n\n### Tip\n\nIn the cases of commodity malware, business email compromise and red team\nactivity, the findings are even more optimized to directly address those\nspecific classes of activity.\n\nLastly, on every incident you find an alert-to-fix timeline in the findings\nsection in Workbench that describes the activity involved in answering the\nabove questions.\n\n"}

article_12925747081875.json

@@ -0,0 +1 @@
+{"title": "What are investigative actions?", "url": "https://support.expel.io/hc/en-us/articles/12925747081875-What-are-investigative-actions-", "date": "2023-01-10T21:54:27Z", "contents": "Investigative actions are steps an analyst and/or automation take to aid in\nthe investigation. Most commonly used investigative actions are steps that a\ngiven security technology supports. For example,\n\n  * acquiring a file can be accomplished by asking Workbench to retrieve it.\n\n  * Workbench navigates for the SOC analysts, indicating how to acquire the file from any number of EDRs.\n\nInvestigative actions can also describe manual steps. This is less common, but\nan investigative action can be created, for example, tasking you to upload a\nfile that Expel doesn’t have access to but needs to complete the\ninvestigation.\n\nInvestigative actions come in many forms, but can be grouped into 2\ncategories: _triage support_ and _communications_.\n\n  * Triage support consists of gathering additional data from customer devices, enriching data from external data sources, and fetching data sources from multiple locations.\n\n  * Communications involves sending out verify actions or notifications.\n\n"}

article_12925747142803.json

@@ -0,0 +1 @@
+{"title": "What is a Phishing submission?", "url": "https://support.expel.io/hc/en-us/articles/12925747142803-What-is-a-Phishing-submission-", "date": "2023-01-10T21:54:27Z", "contents": "The phishing submission model object represents some email metadata related to\nan Expel alert. It can further link to other metadata in the form of\nattachments/URLs/headers for that submission record. It's roughly analogous to\na vendor alert, but can also exist in tandem with a vendor alert. For example,\na Proofpoint TAP-based Expel alert has a vendor alert containing threat\ninformation and a phishing submission record containing the email information\nfrom the Proofpoint TAP alert.\n\n"}

article_12925747196051.json

@@ -0,0 +1 @@
+{"title": "What are remediation actions?", "url": "https://support.expel.io/hc/en-us/articles/12925747196051-What-are-remediation-actions-", "date": "2023-01-10T21:54:28Z", "contents": "A remediation action is a recommended action that should be performed by the\ncustomer organization, an analyst, or another automated process to ensure that\nthe bad actor(s) involved in an incident are stopped. Expel can automate some\nremediation steps, removing the customer from the loop if they choose.\n\n"}

article_13017623221779.json

@@ -0,0 +1 @@
+{"title": "Expel alert categorization by alert fidelity and impact", "url": "https://support.expel.io/hc/en-us/articles/13017623221779-Expel-alert-categorization-by-alert-fidelity-and-impact", "date": "2023-01-13T17:15:27Z", "contents": "Expel uses the following matrix to map an alert's fidelity and impact to an\nExpel alert severity.\n\n![Matrix_Alert_Fidelity.png](https://support.expel.io/hc/article_attachments/13017669036307/uuid-086f9131-d1fa-3466-5f93-00eedafdce66.png)\n\nExpel considers the following when assigning severities of Critical, High,\nMedium, or Low for Expel created rule content, and when reclassifying certain\nsecurity product alerts:\n\n  1. How likely can the underlying logic that generated the alert identify what it was designed to identify? This is also known as the _alert fidelity_.\n\n    * High Fidelity: the alert maintains a true positive rate of **50%** or greater.\n\n    * Medium Fidelity: the alert maintains a true positive rate between **5% to 50%**.\n\n    * Low Fidelity: the alert maintains a true positive rate between **0% to 5%**.\n\n  2. If the alerts are a true positive, what is the impact to the organization?\n\n    * High Impact: there's a high or absolute likelihood of consequences, including but not limited to:\n\n      * Business operation outage to critical systems\n\n      * Large reputational damage\n\n      * Large amount of regulated data exposed\n\n      * Catastrophic exposure of trade secrets\n\n      * Large financial loss\n\n    * Medium Impact: there's a high or absolute likelihood of consequences, including but not limited to:\n\n      * Business operation outage to non-critical systems\n\n      * Limited reputational damage\n\n      * Limited amount of regulated data exposed\n\n      * Limited exposure of trade secrets\n\n      * Limited financial loss\n\n    * Low Impact\n\n      * No business operation outage\n\n      * No reputational damage\n\n      * No amount of regulated data exposed\n\n      * No exposure of trade secrets\n\n      * No financial loss\n\n"}

article_13017623282195.json

@@ -0,0 +1 @@
+{"title": "Expel alert severity descriptions", "url": "https://support.expel.io/hc/en-us/articles/13017623282195-Expel-alert-severity-descriptions", "date": "2023-01-13T17:15:28Z", "contents": "Expel processes 2 types of data from security technologies we integrate with:\nalerts and events. Alerts are security events generated by a security\ntechnology based on events it observed. Events are atomic elements like log\nmessages. Expel uses 2 combined approaches for mapping alerts to our alert\nseverity of Critical, High, Medium or Low:\n\n  * Categorization by alert fidelity and impact\n\n  * Categorization by security product fidelity\n\n"}

article_13017623557267.json

@@ -0,0 +1 @@
+{"title": "SIEM products fidelity and impact", "url": "https://support.expel.io/hc/en-us/articles/13017623557267-SIEM-products-fidelity-and-impact", "date": "2023-01-13T17:15:31Z", "contents": "|\n\n**Expel severity**  \n  \n---|---  \n  \n**Product**\n\n|\n\n**Critical**\n\n|\n\n**High**\n\n|\n\n**Medium**\n\n|\n\n**Low**\n\n|\n\n**Not reviewed**  \n  \nAzure Log Analytics\n\n|  |\n\nSee Azure Active Directory Identity Protection and Microsoft Defender for\nCloud (formerly Azure Security Cloud)\n\n|\n\nSee Azure Active Directory Identity Protection and Microsoft Defender for\nCloud (formerly Azure Security Cloud)\n\n|\n\nSee Azure Active Directory Identity Protection and Microsoft Defender for\nCloud (formerly Azure Security Cloud)\n\n|\n\nSee Azure Active Directory Identity Protection and Microsoft Defender for\nCloud (formerly Azure Security Cloud)  \n  \nDEVO\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A  \n  \nExabeam UBA\n\n|  |  |\n\nScore of 200 or greater\n\n|\n\nScore of 100 to 199\n\n|\n\nScore less than 100  \n  \niBoss\n\n|  |  |  |  |\n\nAll alerts  \n  \nLogRhythm\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A  \n  \nSplunk\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A  \n  \nSplunk Enterprise Security\n\n|  |  |\n\nNotable events categorized as High or Critical\n\n|  |\n\nNotable events categorized as a lesser severity than High  \n  \nQRadar Offenses\n\n|  |  |  |\n\nMagnitude 7 or greater\n\n|\n\nMagnitude less than 7\n\n"}

article_13017668722707.json

@@ -0,0 +1 @@
+{"title": "Cloud products fidelity and impact", "url": "https://support.expel.io/hc/en-us/articles/13017668722707-Cloud-products-fidelity-and-impact", "date": "2023-01-13T17:15:31Z", "contents": "|\n\n**Expel severity**  \n  \n---|---  \n  \n**Product**\n\n|\n\n**Critical**\n\n|\n\n**High**\n\n|\n\n**Medium**\n\n|\n\n**Low**\n\n|\n\n**Not reviewed**  \n  \nAWS GuardDuty\n\n|  |  |\n\nSeverity 7 or greater\n\n|  |\n\nSeverity less than 7  \n  \nAWS Inspector\n\n|  |  |\n\nHigh risk “Network Reachability” alerts\n\n|  |\n\nAll other alerts  \n  \nAWS MACIE\n\n|  |  |\n\nAll alerts\n\n|  |\n\nN/A  \n  \nAWS Trusted Advisor\n\n|  |  |  |  |\n\nAll alerts  \n  \nDUO\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A  \n  \nAzure Active Directory Identity Protection\n\n|  |\n\nAuthentications from suspicious countries and leaked credential events\n\n|  |  |\n\nAll other events  \n  \nDefender for Cloud (formerly Azure Security Cloud)\n\n|  |  |\n\nSeverity High and Critical\n\n|  |\n\nSeverity less than High  \n  \nMicrosoft Cloud App Security\n\n|  |  |\n\nSeverity of 2 or greater\n\n|  |\n\nSeverity less than 2  \n  \nMicrosoft 365\n\n|  |\n\nSee Azure Active Directory Identity Protection and Microsoft Cloud App\nSecurity\n\n|\n\nSee Azure Active Directory Identity Protection and Microsoft Cloud App\nSecurity\n\n|\n\nSee Azure Active Directory Identity Protection and Microsoft Cloud App\nSecurity\n\n|\n\nSee Azure Active Directory Identity Protection and Microsoft Cloud App\nSecurity  \n  \nOkta\n\n|  |  |  |  |\n\nSecurity Threats  \n  \nOneLogin\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A\n\n|\n\nN/A\n\n"}

article_13511503596179.json

@@ -0,0 +1 @@
+{"title": "Usage Metrics overview", "url": "https://support.expel.io/hc/en-us/articles/13511503596179-Usage-Metrics-overview", "date": "2023-01-30T17:25:04Z", "contents": "When your organization purchased Workbench, a certain number of attack\nsurfaces, or endpoints, were purchased. These endpoints are all the devices,\nusers, and other places threats can come from in your environment. In\nWorkbench you can see how many endpoints you're actually using in your\nenvironment.\n\n####  In this article\n\n  * Viewing the overall counts\n\n  * Viewing specific device counts\n\n##  Viewing the overall counts\n\nTo see the total counts for your environment, click Settings > Counts.\n\n![metering2_screen.png](https://support.expel.io/hc/article_attachments/13511523687827/uuid-c3b8d0dd-1461-2ce7-0613-3d49ed4aff65.png)\n\nOn this screen, you see:\n\n  * **Calculated counts** : these are the categories and the general numbers for each area listed.\n\n  * **Counts detail area** : these are the more detailed counts for the endpoints listed above.\n\nFor what the specific counts are and what they mean, go to What's counted in\nyour Expel usage\n\n##  Viewing specific device counts\n\nYou can also view the counts for a specific device. This view also shows you\nthe inventory for the selected device.\n\nTo see the specific device counts, click Settings > Counts > locate the device\nto view > down arrow > View details > Counts.\n\n![Metering_Screen.png](https://support.expel.io/hc/article_attachments/13511504156563/uuid-\ndfd001c8-dd2e-f762-ca99-6aec17fb5e67.png)\n\nWhat you specifically see listed varies, based on the type of selected device.\nTo read an explanation of what you're seeing, expand Count explanations.\n\n"}

article_13511503709587.json

@@ -0,0 +1 @@
+{"title": "What's counted in your Expel usage", "url": "https://support.expel.io/hc/en-us/articles/13511503709587-What-s-counted-in-your-Expel-usage", "date": "2023-01-30T17:25:05Z", "contents": "As you view your usage in Workbench, you see specific information for each\narea. This article details that information for each type of technology.\n\n####  In this article\n\n  * Kubernetes\n\n  * SaaS apps\n\n    * Duo\n\n    * Google Workspace\n\n    * Microsoft 365\n\n    * Okta\n\n    * Onelogin\n\n  * Cloud infrastructure\n\n    * AWS\n\n    * Azure\n\n    * Google Cloud Platform (GCP)\n\n  * Endpoints\n\n    * CrowdStrike\n\n    * Microsoft defender\n\n    * Palo Alto Networks Cortex\n\n    * SentinelOne\n\n    * Carbon Black\n\n  * Product not listed here?\n\n**Kubernetes**\n\nWe count the median number of nodes over the past 30 days. Kubernetes Services\nand Pods are informational only and are not factored into your usage.\n\nWhat we're counting\n\n|\n\nResource type\n\n|\n\nDescription  \n  \n---|---|---  \n  \nNodes\n\n|\n\nNodes\n\n|\n\nThe number of nodes across all clusters.  \n  \n##  SaaS apps\n\nWe count the most recent number of the IdP SaaS app with the maximum number of\nusers. If there is no IdP connected, we take the most recent number of the\nSaaS app with the highest number of users.\n\n**Duo**\n\nWhat we're counting\n\n|\n\nResource type\n\n|\n\nDescription\n\n|\n\nNotes  \n  \n---|---|---|---  \n  \nUsers\n\n|\n\nUser count\n\n|\n\nThe number of users that are not pending deletion in the organization's DUO\naccount.\n\n|\n\nNote: We filter for users where the account status is not \"pending deletion\".\nSee DUO admin users API.  \n  \n**Google Workspace**\n\nWhat we're counting\n\n|\n\nResource type\n\n|\n\nDescription\n\n|\n\nNote  \n  \n---|---|---|---  \n  \nUsers\n\n|\n\nUser count\n\n|\n\nThe number of users that are not marked deleted in the organization's Google\nWorkspace account.\n\n|\n\nNote: We filter for users that are not deleted by setting showDeleted as\nfalse. See Google workspace users list API.  \n  \n**Microsoft 365**\n\nWhat we're counting\n\n|\n\nResource type\n\n|\n\nDescription\n\n|\n\nNote  \n  \n---|---|---|---  \n  \nUsers\n\n|\n\nUser count\n\n|\n\nThe number of users that can sign in.\n\n|\n\nNote: We filter for users where the field accountEnabled is true. See\nMicrosoft user properties.  \n  \n**Okta**\n\nWhat we're counting\n\n|\n\nResource type\n\n|\n\nDescription\n\n|\n\nNotes  \n  \n---|---|---|---  \n  \nUsers\n\n|\n\nUser count\n\n|\n\nThe number of active users in the organization's Okta account.\n\n|\n\nNote: We filter for users where the account status is not deprovisioned\n(deactivated). See Okta user statuses.  \n  \n**Onelogin**\n\nWhat we're counting\n\n|\n\nResource type\n\n|\n\nDescription\n\n|\n\nNotes  \n  \n---|---|---|---  \n  \nUsers\n\n|\n\nUser count\n\n|\n\nThe number of activated users in the organization's Onelogin account.\n\n|\n\nNote: We filter for users where status is not 0 (unactivated). See Onelogin\nuser resource.  \n  \n##  Cloud infrastructure\n\nWe apply a weighting factor to count the number of cloud resources we protect.\nWe count the median data point from the past 30 days, which prevents the data\nfrom being skewed by outliers.\n\n  * We weight storage resources at 25%.\n\n  * We weight compute resources at 100%.\n\n**AWS**\n\nWhat we're counting\n\n|\n\nResource type\n\n|\n\nDescription\n\n|\n\nNote  \n  \n---|---|---|---  \n  \nEC2\n\n|\n\nCompute\n\n|\n\nThe number of running AWS EC2 instances for this account. This includes EC2\ninstances created by other AWS services, for example, Elastic Kubernetes\nService (EKS).\n\n|  \n  \nLambda\n\n|\n\nCompute\n\n|\n\nThe number of unique lambdas for this account. This count is grouped by\naccount, region, and lambda name.\n\n|\n\nNote: We're treating lambdas with the same name but different regions or\naccounts as separate lambdas because there can be differences in the security\nconfigurations and access to services in each region or account.  \n  \nS3\n\n|\n\nStorage\n\n|\n\nThe number of S3 buckets for this account.\n\n|  \n  \nRDS\n\n|\n\nStorage\n\n|\n\nThe number of provisioned RDS instances for this account.\n\n|  \n  \n**Azure**\n\nWhat we're counting\n\n|\n\nResource type\n\n|\n\nDescription  \n  \n---|---|---  \n  \nVirtual machines\n\n|\n\nCompute\n\n|\n\nThe number of virtual machines and virtual machine scale sets in this Azure\nsubscription.  \n  \nSites\n\n|\n\nStorage\n\n|\n\nThe number of static sites in this Azure subscription.  \n  \nStorage accounts\n\n|\n\nStorage\n\n|\n\nThe number of storage accounts and compute disks for this Azure subscription.  \n  \nSQL servers\n\n|\n\nStorage\n\n|\n\nThe number of SQL virtual machines, SQL servers, and SQL databases in this\nAzure subscription.  \n  \nFunctions and App Services\n\n|\n\nCompute\n\n|\n\nThe number of Functions and App Service Apps in this subscription.  \n  \n**Google Cloud Platform (GCP)**\n\nWhat we're counting\n\n|\n\nResource type\n\n|\n\nDescription\n\n|\n\nNote  \n  \n---|---|---|---  \n  \nApp Engine\n\n|\n\nCompute\n\n|\n\nThe number of App Engine applications in all projects.\n\n|  \n  \nCloud function\n\n|\n\nCompute\n\n|\n\nThe number of unique cloud functions when grouped by project ID, region, and\nfunction name.\n\n|\n\nNote: We're grouping functions with the same name that may be in a different\nregion or account because there can be differences in the security\nconfigurations and access to services.  \n  \nCompute instance\n\n|\n\nCompute\n\n|\n\nThe number of compute instances in all projects and regions.\n\n|  \n  \nSQL admin\n\n|\n\nStorage\n\n|\n\nThe number of Cloud SQL instances in all projects.\n\n|  \n  \nStorage\n\n|\n\nStorage\n\n|\n\nThe number of Cloud Storage buckets in all projects.\n\n|  \n  \n##  Endpoints\n\nWe count on-prem endpoint resources and don't count cloud resources. We take\nthe most recent number of endpoint resources. We’re not including mobile\ndevices or devices like printers, thermostats and other things with an IP\naddress in the usage data.\n\n**CrowdStrike**\n\nWhat we're counting\n\n|\n\nResource type\n\n|\n\nDescription  \n  \n---|---|---  \n  \nOn-prem resources\n\n|\n\nEndpoint\n\n|\n\nThe number of hosts with a non-null Service Provider in CrowdStrike. The\nnumber of endpoints that have been last seen within 30 days.  \n  \n**Microsoft defender**\n\nWhat we're counting\n\n|\n\nResource type\n\n|\n\nDescription\n\n|\n\nNotes  \n  \n---|---|---|---  \n  \nMachines\n\n|\n\nEndpoint\n\n|\n\nThe number of endpoints that have been last seen within 30 days.\n\n|\n\nNote: We filter for machines where the onboardingStatus is “onboarded”. See\nmachine resources API.  \n  \n**Palo Alto Networks Cortex**\n\nWhat we're counting\n\n|\n\nResource type\n\n|\n\nDescription  \n  \n---|---|---  \n  \nEndpoints\n\n|\n\nEndpoint\n\n|\n\nThe number of endpoints that have been last seen within 30 days.  \n  \n**SentinelOne**\n\nWhat we're counting\n\n|\n\nResource type\n\n|\n\nDescription  \n  \n---|---|---  \n  \nAgents\n\n|\n\nEndpoint\n\n|\n\nThe number of agents that don't have a Cloud Provider of AWS, CDP, or Azure in\nSentinelOne. The number of endpoints that have been last seen within 30 days.  \n  \n**Carbon Black**\n\nWhat we're counting\n\n|\n\nResource type\n\n|\n\nDescription  \n  \n---|---|---  \n  \nSensors\n\n|\n\nEndpoint\n\n|\n\nThe number of endpoints that have been last seen within 30 days.  \n  \n##  Product not listed here?\n\nThe products listed here are the primary ones we use for determining your\nusage for each product. There are many more products we integrate with. If you\nonly have products not listed here integrated with Workbench, your account\nteam can work with you to determine the correct quantity of Expel to purchase.\n\n"}

article_13612714001171.json

@@ -0,0 +1 @@
+{"title": "Connecting your devices securely to Workbench", "url": "https://support.expel.io/hc/en-us/articles/13612714001171-Connecting-your-devices-securely-to-Workbench", "date": "2023-02-02T15:59:46Z", "contents": "All traffic from Expel to your security devices come from 1 of these 6 IP\naddresses, which are available in DNS under the hostname\negress.opsv2.expel.io. If your security tech supports an IP allow list,\nconfigure it to restrict access to these IP addresses.\n\n  * 34.75.13.114\n\n  * 34.75.152.7\n\n  * 35.243.190.98\n\n  * 104.196.158.205\n\n  * 34.75.81.28\n\n  * 34.75.210.18\n\n"}

article_13807470251027.json

@@ -0,0 +1 @@
+{"title": "Slack setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/13807470251027-Slack-setup-for-Workbench", "date": "2023-02-08T21:52:49Z", "contents": "This article helps you integrate your Slack installation with the Expel\nWorkbench.\n\n####  In this article\n\n  * Before you start\n\n  * Step 1: Enable API access\n\n  * Step 2: Configure Slack in Expel Workbench\n\n##  Before you start\n\n  * **Slack Enterprise Grid is required.**\n\n  * The Slack app must be installed by the **Owner** of the Enterprise Grid organization.\n\n  * The Slack app must be installed on the organization, not just a workspace within the organization.\n\n##  Step 1: Enable API 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\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. Create a new slack app https://api.slack.com/apps.\n\n  2. In the settings for the new app, select OAuth > Permissions from the left navigation. Scroll to the section titled Scopes, then click Add an OAuth Scope under User Token Scopes. Add the `auditlogs:read` scope. Use https://localhost for the redirect URL.\n\n  3. In the settings for the new app, select Manage Distribution from the left navigation. Under the section titled Share Your App with Other Workspaces, make sure all four sections have the green checkmark. Then click the green Activate Public Distribution button.\n\n  4. Under the Share Your App with Your Workspace section, copy the Sharable URL and paste it into a browser to start the OAuth handshake that installs the app on your organization. You must be logged in as the Owner of your Enterprise Grid organization to install the app.\n\n  5. Check the list in the upper right of the installation screen to make sure you are installing the app on the Enterprise Grid organization, not an individual workspace within the organization (see image below).\n\n  6. After the app is authorized, you are redirected to the localhost URL that contains a temporary code. Use that code to manually exchange it with an access token. Click here for instructions. Save the access token for later use.\n\n##  Step 2: Configure Slack in Expel Workbench\n\nNow that we have the correct access configured and noted the credentials, we\ncan integrate your tech with Workbench.\n\n  1. In a new browser tab, click this link to open the Add Security Device screen in Workbench.\n\n![Slack_AddSecDev_v2.png](https://support.expel.io/hc/article_attachments/13807501313043/uuid-3744c9c2-8596-6771-b482-85720e22b989.png)\n\n  2. Fill in the fields like this:\n\nField name\n\n|\n\nWhat to put in it  \n  \n---|---  \n  \nName\n\n|\n\nWhat you want to name the security device.  \n  \nLocation\n\n|\n\nGeographic location of the server.  \n  \nAPI Token\n\n|\n\nThe access token created in Step 1.  \n  \n  3. Click Save.\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###  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"}

article_14012946928659.json

@@ -0,0 +1 @@
+{"title": "Microsoft Intune setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/14012946928659-Microsoft-Intune-setup-for-Workbench", "date": "2023-02-15T18:34:05Z", "contents": "This article helps you provide the provisioning of the Azure App needed to\nperform the graph API queries for the deviceManagement endpoint, which allows\nthe Expel Workbench to collect logs for Microsoft Intune.\n\n####  In this article\n\n  * Step 1: Enable console access\n\n  * Step 2: Configure Slack in Expel Workbench\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\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. Sign into Azure and search for app registrations.\n\n  2. In the App registrations pane, select New registration.\n\n  3. Give the application a name, choose the supported account type that can access the API, assign a redirect URL if needed, and click Register to create the app.\n\n  4. After you load into the app, select API permissions to begin selecting the necessary permissions for the integration.\n\n  5. Choose to add permissions to the app and select Microsoft Graph > Application permissions, and then scroll down to DeviceManagementApps. Select DeviceManagementApps.Read.All and click Add permissions to prepare the grant permissions request.\n\n  6. Create a Client secret to enter into Workbench to facilitate API authentication for alert polling. Save this for later use.\n\n  7. As an Administrator, navigate to the Expel Admin Consent Page.\n\n  8. Review and accept the requested permissions.\n\n  9. The Expel Intune Integration app now appears under Enterprise Applications. Review properties and make sure that all permissions were properly granted.\n\n####  Step 2: Configure Slack in Expel Workbench\n\nNow that we have the correct access configured and noted the credentials, we\ncan integrate your tech with Workbench.\n\n  1. In a new browser tab, click this link to open the Add Security Device screen in Workbench.\n\n![Intune_AddSecDev.png](https://support.expel.io/hc/article_attachments/14013003430547/uuid-\nfbf965ab-17bb-edd3-0a00-a87c67f0142e.png)\n\n  2. Fill in the fields like this:\n\nField name\n\n|\n\nWhat to put in it  \n  \n---|---  \n  \nName\n\n|\n\nWhat you want to name the security device.  \n  \nLocation\n\n|\n\nGeographic location of the server.  \n  \nIntune (tenant) ID\n\n|  \n  \nApplication (client) ID\n\n|  \n  \nApplication (client) secret\n\n|\n\nThe client secret created in Step 1.  \n  \n  3. Click Save.\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###  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"}

article_14012947037715.json

@@ -0,0 +1 @@
+{"title": "ExtraHop Setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/14012947037715-ExtraHop-Setup-for-Workbench", "date": "2023-02-15T18:34:06Z", "contents": "This guide helps you connect your ExtraHop installation to the Expel\nWorkbench.\n\n####  In this article\n\n  * Before you start\n\n  * Step 1: Enable console access\n\n  * Step 2: Configure the technology in Workbench\n\n##  Before you start\n\nYou must have:\n\n  * **ExtraHop Reveal(x) Enterprise. Expel does not support ExtraHop Reveal(x) 360.**\n\n  * An ExtraHop user account with admin-level permissions to create another account.\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\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. Login to the ExtraHop console using the admin account.\n\n  2. Create a new user account named Expel-Integration with these permissions:\n\n    * Full Read-only permissions.\n\n    * `\"write\" : \"personal\"` This is required for API key generation.\n\n  3. Login to the ExtraHop console using the Expel-Integration account.\n\n  4. Click the user bubble to open a list with an API access option, then select API access. If you need instructions on creating an API key in ExtraHop, click here.\n\n  5. Type a description for the API key, then click Generate. Make a note of the key for later use.\n\n##  Step 2: 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. Click this link to open Workbench. The link opens the Add Security Device screen directly. You may need to log in first.\n\n![ExtraHop_AddSecDev.png](https://support.expel.io/hc/article_attachments/14013037161235/uuid-27ae074e-c588-da93-85ec-8460f8595d96.png)\n\n  2. Fill in the Connection Settings fields like this:\n\n    * Add a Name and Location that are meaningful to you.\n\n    * For Server address, use the ExtraHop server URL.\n\n    * For API key, use the key generated in Step 1.\n\n  3. (Optional) To grant console access, fill in the Console Login fields like this:\n\n    * For Console URL, use the ExtraHop console URL.\n\n    * For Username and Password, use the username and password created for the Expel-Integrations account.\n\n  4. Click Save.\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###  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"}

article_14049611141779.json

@@ -0,0 +1 @@
+{"title": "GitHub self-hosted (on-prem) setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/14049611141779-GitHub-self-hosted-on-prem-setup-for-Workbench", "date": "2023-02-16T18:36:02Z", "contents": "This article explains how to connect GitHub to Workbench.\n\n####  In this article\n\n  * Before you start\n\n  * Step 1: Install the self-hosted GitHub App\n\n  * Step 2: Configure the technology in Workbench\n\n##  Before you start\n\nYou must have:\n\n  * A GitHub Enterprise account license. For more information, see GitHub products.\n\n### Note\n\nThis procedure is specifically for self-hosted GitHub deployments. For cloud-\nhosted, use the GitHub cloud-hosted Workbench setup guide.\n\n##  Step 1: Install the self-hosted GitHub App\n\nWorkbench uses a GitHub App as part of the onboarding process. During\ninstallation, the Expel GitHub App receives the following organization-level\nprivileges:\n\n  * Members: Read+Write\n\n  * Administration: Read-only\n\n### Note\n\nGitHub doesn't log user identities, making it difficult to track suspicious\nactivity at the user level. To solve this problem, Expel uses Write\nPermissions to map GitHub data to a user's identity.\n\n  1. Use the Create a GitHub App instructions to create a custom application in the organization you want monitored. Fill in the required fields like this:\n\n    * GitHub app name: ExpelGitHubIntegration\n\n    * https://github.com/apps/expelgithubintegration\n\n    * Permissions:\n\n      * Members: Read+Write\n\n      * Administration: Read-Only\n\n    * Leave all other fields blank.\n\n  2. Navigate to the organization's Apps Settings page. Example URL: https://github.*****/organizations/*****/settings/apps/ExpelGitHubIntegration.\n\n  3. Write down the App ID.\n\n  4. Use the Authenticating with GitHub Apps instructions to generate a private key and store it for later use. This is your PEM key and you need it in the next section.\n\n    * ### Note\n\nIf you have multiple organizations, create a separate Security Device in\nWorkbench for each organization.\n\n  5. If you are using an Expel Assembler within your network, use the Managing allowed IP addresses for a GitHub App instructions to add the assembler's internal IP to the allow list. Otherwise, add the Expel egress IPs to the allow list:\n\n    * 34.75.13.114\n\n    * 34.75.152.7\n\n    * 35.243.190.98\n\n    * 104.196.158.205\n\n    * 34.75.81.28\n\n    * 34.75.210.18\n\n##  Step 2: 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###  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. In a new browser tab, login to https://workbench.expel.io/settings/security-devices?setupIntegration=github.\n\n![mceclip2.png](https://support.expel.io/hc/article_attachments/14049613619987/uuid-18f1e774-583c-2ff0-dd49-4b9c0a69dd08.png)\n\n  2. For Where is your device? select:\n\n    1. If you decided to allowlist the Expel egress IPs, select Cloud.\n\n    2. If you are using an Assembler, select On-prem.\n\n  3. For Assembler select the Assembler from the list. N/A for Cloud.\n\n  4. Complete these fields using the credentials and information from Step 1.\n\n    * For Name type the name of your GitHub organization.\n\n    * For Location type Cloud.\n\n    * For Organization name, type the name of your GitHub organization.\n\n    * For Enterprise slug type the Enterprise name.\n\n    * For the Application installation ID type the installation ID from Step 1.\n\n    * For Application ID type the application ID from Step 1.\n\n    * For Application Private PEM, copy and paste the PEM file contents from Step 1.\n\n  5. Click Save.\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###  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"}

article_1500002718861.json

@@ -0,0 +1 @@
+{"title": "How to provision Expel Assembler", "url": "https://support.expel.io/hc/en-us/articles/1500002718861-How-to-provision-Expel-Assembler", "date": "2021-02-17T20:44:46Z", "contents": "The Expel Assembler enables you to create a secure VPN connection so that we\ncan access your security devices. We’ve packaged it as a virtual machine. If\nyou install virtual machine images regularly, this should be pretty\nstraightforward.\n\n####  In this article\n\n  * Do you need an Assembler?\n\n  * Download the Assembler image\n\n  * Register the Assembler in the Expel Workbench\n\n  * Deploy the Assembler virtual machine in your network\n\n  * Activate the Assembler through the virtual machine console\n\n  * Authorize the Assembler in the Expel Portal\n\n##  Do you need an Assembler?\n\nThe Expel Assembler is only needed if a security device you want to connect to\nWorkbench is on an internal network to your company. If Workbench can connect\ndirectly to the security device, you don’t need an Assembler at all! Just go\nright to adding the security device in Workbench.\n\n##  Before you start\n\nBefore you get started, you need 2 things.\n\n  1. A place to run the Expel Assembler virtual machine. We work with VMWare or Hyper V for on-prem environments and AWS or Microsoft Azure for cloud environments. The Assembler needs the following resources available:\n\n    * 4 virtual CPUs\n\n    * 8 GB RAM\n\n    * 100 GB disk space\n\n  2. Connect the Assembler virtual machine to the following network resources:\n\n    * Our VPN servers:\n\n**Host**\n\n|\n\n**Ports**  \n  \n---|---  \n  \nprovisionvpn.opsv2.expel.io\n\n|\n\nTCP 443 or TCP 8099  \n  \nservicevpn.opsv2.expel.io  \n  \n    * The security devices you want to connect to the Expel Assembler. Search this knowledge base for documentation on each security device.\n\n    * Your DHCP server, unless you decide to assign a static IP to the Assembler.\n\n    * Your DNS server.\n\nIf your network is segmented, you may need to deploy multiple Assemblers. If\nyou have any questions about how many Assemblers to install, let us know and\nwe’ll recommend the best approach for your environment.\n\n##  Download the Assembler image\n\n### Note\n\nIf you are deploying the assembler image in Amazon Web Services (AWS), then\nskip this section and go to Register the Assembler in the Expel Workbench.\n\n  1. In Expel Workbench, click Settings in the top navigation bar.\n\n  2. Click Assemblers in the left navigation panel.\n\n  3. Click Download installer.\n\n![Download_Assembler_Installer.png](https://support.expel.io/hc/article_attachments/6758698390931/uuid-2f797b2d-6a96-6a41-8780-42cbfda1b2f1.png)  \n---  \n  \n  4. Click the installer link for your virtualization technology.\n\n![Download_VM_Installer_Box1.png](https://support.expel.io/hc/article_attachments/6758683508499/uuid-162e9ad3-d382-7569-8b87-a3fbd91beee0.png)  \n---  \n  \n  5. Note the hash of the file downloaded for error checking in Step 7.\n\n![Download_VM_Installer_Box2.png](https://support.expel.io/hc/article_attachments/6758581344915/uuid-39c0d132-0d48-dde7-13b4-726a474019f5.png)  \n---  \n  \n  6. Now’s a good time to grab a cup of coffee because it’ll take a few minutes to download.\n\n    * If the hash matches, continue to Register the Assembler in Expel Workbench.\n\n    * If the hash doesn't match, download it again and re-check the hash.\n\n    * If the hash still doesn’t match after the second time, something’s not right. In that case, contact your engagement manager or customer success engineer in Slack or by email, or you can email [email protected].\n\n  7. After the download completes, verify that a hash of the file downloaded matches the data shown in Expel Workbench. The table below shows how you can do this for the 3 main operating systems.\n\n### Caution\n\nThis is an important step because it confirms that your download is complete\nand that no one tampered with the image.\n\n**Operating system**\n\n|\n\n**Hash to verify**\n\n|\n\n**Command**  \n  \n---|---|---  \n  \nWindows\n\n|\n\nSHA256\n\n|\n\nSearch for cmd, and select cmd.exe or “Command Prompt” from the results. Run\nthese commands in the window that opens:\n\n    \n    \n    cd <your download folder>\n    \n    certutil -hashfile expel-assembler-vmware- <version>.ova sha256  \n  \nMac OS\n\n|\n\nSHA256\n\n|\n\nIn Spotlight Search, search for the Terminal program and run it. In the\nterminal window, run this command:\n\n    \n    \n    shasum -a 256 ~/Downloads/expel-assembler-vmware- <version>.ova  \n  \nLinux\n\n|\n\nSHA256\n\n|\n\nIn a terminal program, run:\n\n    \n    \n    sha256sum ~/Downloads/expel-assembler-vmware- <version>.ova  \n  \n##  Register the Assembler in the Expel Workbench\n\n  1. In Workbench, click Settings in the top navigation bar, then Assemblers on the left navigation panel. You see a box with the Assembler Name and Location fields. If not, click the Add Assembler button.\n\n  2. Type the Assembler Name and Location for the Assembler. It’s best to select names that are meaningful to both you and to Expel so you can easily identify the Assembler in the user interface. For example: ACME HQ.\n\n  3. Click Save.\n\n  4. Note the Install Code for the newly registered Assembler. You need this later to activate the Assembler.\n\n  5. To add another Assembler, click the Add Assembler button and repeat these steps.\n\n####  Deploy the Assembler virtual machine in your network\n\nClick a link for instructions on deploying the Assembler virtual machine in\nyour network:\n\n  * Deploying the Expel Assembler in AWS.\n\n  * Deploying the Expel Assembler On VMWare.\n\n  * Deploying the Expel Assembler on Hyper-V.\n\n  * Deploying the Expel Assembler on Microsoft Azure.\n\n##  Activate the Assembler through the virtual machine console\n\n  1. Select the newly deployed Virtual Machine for the Assembler.\n\n  2. Open the console of the Assembler.\n\n  3. Log in with username expel and password expel.\n\n  4. Set a unique and secure password for the expel account. First type the existing password (expel), then type the new password 2 more times. Securely store the new password per your organization's policies. You need it to log in to the Assembler again.\n\nNote: Your password must be at least 8 characters and not a word found in the\ndictionary.\n\n    \n        You are required to change your password immediately (root enforced)\n    Changing password for expel.\n    (current) UNIX password: expel\n    New password: <enter new password>\n    Retype new password: <enter new password again>  \n  \n---  \n  \n  5. Azure users only: delete the users you created during VM creation by running:\n    \n                  sudo userdel temp\n            \n\n  6. Determine the network interface to use by running:\n    \n                  sudo expelmanage --list-interfaces\n            \n\n  7. The Assembler uses DHCP by default. To use DHCP, skip to the next step. To use a static network configuration, run:\n    \n        sudo expelmanage --net --interface <interface name> --type static --ip  <IP address> --netmask <subnet mask> --gateway <gateway IP> --dns  <nameserver IP>\n\n<interface name> is determined in the previous step.  \n  \n---  \n  \n### Note\n\nGet the IP address, subnet mask, gateway IP, and nameserver IP to input the\nabove command from your virtualization administrator.  \n  \n  8. Activate the Assembler by supplying the 8-character install code created in Register the Assembler:\n    \n        sudo expelmanage --activate <eight-character install code>\n\nYou see output like this:\n\n    \n        [expel@hostname ~]$ sudo expelmanage --activate abcd1234\n    Activation code set\n    Regenerating SSH keys\n    Activated\n    [expel@hostname ~]$  \n  \n---  \n  \n  9. Run exit to log out of the console.\n\n##  Authorize the Assembler in the Expel Portal\n\nWithin 30 seconds of activating the Assembler with a matching install code,\nthe Assembler you registered at https://workbench.expel.io/settings/assemblers\nchanges status from Not Yet Connected to Connected, and an Authorize button\nappears for the Assembler. Click the Authorize button.\n\nWorkbench now automatically configures the Assembler. This process takes about\n10 minutes but can take longer if you have a slow network connection. After\ncomplete, the status changes to Active.\n\nIf any errors occur along the way, leave everything as it is and file a\nsupport case. We can often fix any issues without any further involvement from\nyou after it's connected to our VPN.\n\nYou can now begin to turn on your security devices. Follow the instructions in\nthe Getting connected to Expel Workbench.\n\n"}

article_1500002718881.json

@@ -0,0 +1 @@
+{"title": "Lacework setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002718881-Lacework-setup-for-Workbench", "date": "2021-02-17T20:44:47Z", "contents": "This article explains how to connect Lacework 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\nCreate a user in Lacework for Workbench or create an SSO user for Workbench\nwith access to Lacework.\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##  Step 2: Generate API credentials\n\nTo integrate the technology with Workbench, we need to create secure\ncredentials to the API.\n\nLacework provides a combination of API Access keys and tokens to be used by\nclients and client applications to access the Lacework API. API access key IDs\nand secret access keys are created using the Lacework Console. Temporary\naccess (bearer) tokens, used by clients, are created using the Lacework API.\n\nOnly administrators can create API access keys with a limit of 2 per user. An\nAPI access key doesn't expire but can be disabled or deleted. After creation,\nadministrators can download and securely store the secret key.\n\n  1. To create an API key, navigate to Settings > API Keys and click \\+ Create New.\n\n  2. Type a name for the key and an optional description and click Save.\n\n  3. To get the secret key, download the generated API key file and open it in an editor.\n\nDocs reference: https://support.lacework.com/hc/en-\nus/articles/360011403853-Generate-API-Access-Keys-and-Tokens\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###  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. In a new browser tab, login to https://workbench.expel.io.\n\n  2. On the console page, navigate to Settings and click Security Devices.\n\n  3. At the top of the page, click Add Security Device.\n\n  4. Search for and select your technology.\n\n![Screen Shot 2021-03-05 at 12.29.16\nPM.png](https://support.expel.io/hc/article_attachments/13874829904915/uuid-24abe14f-605b-3cc1-2107-d11fa3e19f19.png)  \n---  \n  \n  5. Complete all fields using the credentials and information you collected in Step 1 and Step 2.\n\n    * For Name type the host name of the Lacework device.\n\n    * For Location type the geographic location of the appliance.\n\n    * For URL type the host name or IP address of the Lacework management interface. Device IP can be found in the Lacework console under Dashboard > General Information > MGT IP Address.\n\n    * For API key type the API generated in Step 2.\n\n    * For API secret, type the secret generated in Step 2.\n\n  6. Click Save.\n\n  7. 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"}

article_1500002718901.json

@@ -0,0 +1 @@
+{"title": "Configuring your Okta SSO provider with Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002718901-Configuring-your-Okta-SSO-provider-with-Workbench", "date": "2021-02-17T20:44:47Z", "contents": "This article explains setting up your Okta SSO provider with Expel Workbench\n\n### Tip\n\nWorkbench logins don't support SCIM. We only support SAML and local logins.\n\n  1. Log into your Okta console.\n\n  2. Navigate to Applications in the main top navigation.\n\n  3. Click Add Application > Create New App.\n\n  4. The settings should be as follows:\n\n    * Platform: Web\n\n    * Sign on method: SAML 2.0\n\n    * Click Create.\n\n### Note\n\nThis screen can look slightly different depending on your Okta account.\n\n  5. Under General Settings:\n\n    * App name: Expel Workbench.\n\n    * Upload our logo and click Save. You can right-click this image and save it locally.\n\n![Expel\nLogo](https://support.expel.io/hc/article_attachments/6789150377363/uuid-8179e3c1-15ce-4bba-d03f-152aaefde479.png)\n\n    * Click Next.\n\n  6. You are now on the Configure SAML step in Okta. Copy information from Expel Workbench to complete the integration. Open a new tab or window and log into Expel Workbench (https://workbench.expel.io)\n\n  7. Navigate to Organization Settings > My Organizations and select the organization. Click Integrations > Configure SSO.\n\n  8. Next, copy and paste the following from Expel Workbench into Okta:\n\n    * ACS URL or Single Sign-on URL → Single sign on URL\n\n    * Audience URI or Audience → Audience URI (SP Entity ID)\n\n    * Leave Yes, allow users to log in locally OR via SSO selected for local logins. This selection makes initial SSO setup easier. You can change this later.\n\n  9. In Okta under (A) SAML Settings, Attribute Statements (Optional):\n\n    * Type the word email under Name, and select user.email from the Value list.\n\n### Tip\n\nThese are case sensitive.\n\n    * Click Next.\n\n  10. For the Okta feedback form, select I’m an Okta customer adding an internal app and fill in the following optional information as you see fit. Or This is an internal app that we have created. Then click Finish.\n\n  11. In Okta under Sign On, Settings > View Setup Instructions.\n\n  12. In Expel Workbench, click Next 2 times, until you see Step 3 of 3.\n\n  13. Copy and paste the following from Okta into Expel Workbench.\n\n    * Identity Provider Single-Sign-On URL → Single Sign-On URL or SAML 2.0 Endpoint\n\n    * Identity Provider Issuer → Issuer or Issuer ID\n\n    * X.509 Certificate → Certificate\n\n  14. Click Save in Expel Workbench.\n\n### Important\n\nBefore signing in with SSO, make sure that:\n\n  * In your SSO provider, Workbench is assigned to all intended users.\n\n  * The user email addresses in your SSO provider match the email that's configured for the users in Workbench. The emails are case sensitive.\n\n  * New members of your organization that need access to Workbench have user accounts created in Workbench and have Workbench assigned to them in your Identity Provider.\n\n  * After you finish testing and setting up, in Workbench, you can disable local logins by going to the Integrations area in Settings. Click Edit from the list, and click No, users can ONLY log in via SSO. Then click Next > Next > Save to save.\n\n"}

article_1500002718921.json

@@ -0,0 +1 @@
+{"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"}

article_1500002718961.json

@@ -0,0 +1 @@
+{"title": "VMware Carbon Black EDR setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002718961-VMware-Carbon-Black-EDR-setup-for-Workbench", "date": "2021-02-17T20:44:52Z", "contents": "This article explains how to connect VMware Carbon Black EDR to Workbench.\n\nVMWare VMware Carbon Black EDR was formerly called Carbon Black Response.\n\n####  In this article\n\n  * Step 1: Enable console access\n\n    * Create an admin account\n\n    * Verify VMware Carbon Black Live EDR is enabled\n\n  * Step 2: Generate API credentials\n\n    * Obtain the API key for the Expel account\n\n  * Step 3: Enable threat feeds\n\n  * Step 4: Configure the technology in Workbench\n\n  * Step 5: Edit the device to add console access\n\n##  Step 1: Enable console access\n\nThis procedure creates a user account for Expel that keeps the Expel activity\nseparate from other activity on the VMware Carbon Black EDR console.\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###  Create an admin account\n\n  1. Navigate to the Users icon on left and click +Add User.\n\n    * For Username type expel.\n\n    * For First Name type Expel.\n\n    * For Last Name type User.\n\n    * For Email Address type [email protected].\n\n    * Type a Password.\n\n    * Assign to: Administrators.\n\n    * Select Global administrator. Global administrator is required to perform the necessary functions within VMware Carbon Black EDR for pulling process listings, and so on.\n\n  2. Click Save changes.\n\n###  Verify VMware Carbon Black Live EDR is enabled\n\nThis step allows Expel to interact with your endpoints, for example, pull\nprocess listings, and so on.\n\n  1. Click on the Sensors icon on the left side panel and click any host name.\n\n  2. In the upper right corner, the button Go Live is active if VMware Carbon Black Live EDR is enabled. If it's active, you are DONE!\n\n  3. If VMware Carbon Black Live EDR isn't enabled and is hosted on-prem:\n\n    * SSH into the CB appliance and perform the command `vi /etc/cb/cb.conf`.\n\n    * Search for `CbLREnabled=False` and change the value from False to True.\n\n    * Restart services for the change to take effect: `service cb-enterprise restart`.\n\n  4. If VMware Carbon Black Live EDR is not enabled and cloud-hosted:\n\n    * Submit a request to the Carbon Black Cloud Support team requesting this feature be enabled. You can simply send the request with the following: “Please enable Live EDR and VDI Behavior”.\n\n##  Step 2: Generate API credentials\n\nTo integrate the technology with Workbench, we need to create secure\ncredentials to the API.\n\nThis step creates an authentication token that allows the Expel Assembler to\naccess the VMware Carbon Black EDR API.\n\n###  Obtain the API key for the Expel account\n\n  1. Log out of the VMware Carbon Black EDR Console.\n\n  2. Log back into the VMware Carbon Black EDR Console as the newly-created Expel User.\n\n  3. Click Expel User on the upper right, then My Profile, then API Token.\n\n  4. Make note of the API token. It's used next for registration within Workbench.\n\n##  Step 3: Enable threat feeds\n\nExpel recommends enabling the following Carbon Black threat feeds at a\nminimum:\n\n  * \\+ CB Advanced Threat\n\n  * \\+ CB Community\n\n  * \\+ CB Suspicious Feed\n\n  * \\+ CB Tamper Detection\n\n  * \\+ CB Early Access\n\n  * \\+ SANS Feed\n\n  * \\+ Expel (this feed is added and enabled by Expel)\n\n  1. Navigate to the Threat Intelligence icon.\n\n  2. Select Enable and the Create Alert options for each of the feeds.\n\n##  Step 4: 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. Login to https://workbench.expel.io/settings/security-devices?setupIntegration=carbon_black.\n\n  2. Enter the following information:\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/13874984471059/uuid-\ncd551474-a2f2-a52e-7e35-f85216a4b1dc.png)\n\n    * Select Cloud or On-Prem (on premises) installation.\n\n    * For On-Prem installations only, select an Assembler from the list. Select the assembler you set up in Getting connected to Expel Workbench.\n\n    * For Name type the hostname of the VMware Carbon Black EDR device.\n\n    * For Location type the geographic location of the appliance.\n\n    * For Server address type the VMware Carbon Black EDR device IP or hostname in the following format: `https://10.0.0.10 or https://mycbraddress.com`\n\n    * For API key type the API generated in Step 2.\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 5: 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"}

article_1500002719001.json

@@ -0,0 +1 @@
+{"title": "Attivo through SIEM setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002719001-Attivo-through-SIEM-setup-for-Workbench", "date": "2021-02-17T20:44:59Z", "contents": "This article explains how to connect Attivo to Workbench.\n\n####  In this article\n\n  * Step 1: Enable console access\n\n  * Step 2: Logging Attivo using Sumo Logic and Splunk\n\n  * Step 3: Configure Attivo 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\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. Administration > User Accounts > Configure.\n\n  2. Select +Add from the Users List.\n\n    * For User Type select local.\n\n    * Select Privileges checkbox for Admin.\n\n    * For Username type expelsoc.\n\n    * For First Name type Expel.\n\n    * For Last Name type SOC.\n\n    * Type a Password.\n\n  3. Click Save.\n\n### Note\n\nAfter console access is established, the remaining onboarding steps for this\ntechnology can also be performed by Expel. Reach out to your engagement\nmanager and we're happy to complete the integration!\n\n##  Step 2: Logging Attivo using Sumo Logic and Splunk\n\nRefer to your SIEM documentation or work with your SIEM representative to port\nin Attivo logs. You can also refer to the following web references for\ncreating a new Syslog source:\n\nSumo Logic: https://help.sumologic.com/docs/send-data/installed-\ncollectors/sources/syslog-source/\n\nSplunk:\nhttps://docs.splunk.com/Documentation/Splunk/7.0.2/Data/Monitornetworkports\n\n##  Step 3: Configure Attivo 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. In a new browser tab, go to https://workbench.expel.io/settings/security-devices?setupIntegration=attivo.\n\n  2. Select the Assembler with network connectivity to the Attivo device. Select the SIEM you created earlier.\n\n![Screen Shot 2021-03-05 at 7.36.20\nAM.png](https://support.expel.io/hc/article_attachments/13874953185811/uuid-d35c1569-de05-6058-3783-569dccdef35d.png)\n\n    * For Name type the host name of the Attivo device.\n\n    * For Location type the geographic location of the appliance.\n\n    * For Source Category, type the Sumo Logic source category for this device.\n\n    * For Source Type (SIEM that contains the data) type the Splunk source type for this device.\n\n    * For Server address type the address of the server for console access.\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"}

article_1500002872602.json

@@ -0,0 +1 @@
+{"title": "Getting connected to Expel Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002872602-Getting-connected-to-Expel-Workbench", "date": "2021-02-17T20:44:43Z", "contents": "Welcome to Expel. We’re excited to be working with you! We’ve put a lot of\neffort into making it as easy as possible to get going. You have 3 basic steps\nand this article walks you through each of them.\n\n  * Step 1: Get your account set up in Expel Workbench.\n\n  * Step 2: Complete configuration steps on your technologies.\n\n  * Step 3: Connect your technologies to Expel Workbench.\n\nThree steps. That’s it and you’re ready to go! We’re always looking to make\nthings easier, so if you see anything along the way that'd make this process\nsmoother, don’t be shy—let us know!\n\n#####  Step 1: Set up your Expel Workbench account\n\nThe Expel Workbench is what you use to see everything Expel is doing for you.\nHere’s how you get your account set up:\n\n  1. Check your inbox. You received a Welcome to Expel email. It includes a link to activate your Expel Workbench account. If you haven’t received the email (or just can’t find it) don’t worry. Just let us know and we’ll send another one over to you right away.\n\n  2. Click the Activation button in your welcome email and follow the directions to configure your password and multifactor authentication. You need a multifactor authentication app on your phone or computer to complete creating your account.\n\n### Tip\n\nBookmark https://workbench.expel.io so you have quick access to Expel\nWorkbench in the future.\n\n#####  Step 2: Configure your technologies\n\n  1. In the knowledge base, search for and find the Getting Started Guide for your technology.\n\n  2. Complete the steps in the articles.\n\n### Note\n\nSome on-prem technologies require the deployment of an Expel Assembler. For\ninformation on the Expel Assembler, search the knowledge base for the\nassembler you're interested in.\n\n#####  Step 3: Add your security devices\n\nFollow this procedure on https://workbench.expel.io for each technology to\nconnect to Expel Workbench:\n\n  1. Click the Dashboards link in the upper left. The Welcome to Expel Workbench screen appears. The technology your organization purchased is listed.\n\n  2. Click the technology you want to set up.\n\n  3. Follow the instructions on the screen.\n\n  4. Continue until all your technology is set up.\n\nIf your organization purchased additional technology and you want to add it to\nExpel Workbench, use the instructions below.\n\n  1. Click Organization Settings.\n\n  2. Click Security Devices in the left panel.\n\n  3. Click the \\+ Add Security Device button.\n\n  4. Select the type of security device you want to connect.\n\n  5. Type a Name and Location that's meaningful to both you and to Expel.\n\n  6. Type additional information specific to the security device type.\n\n  7. Click Save.\n\n"}

article_1500002872642.json

@@ -0,0 +1 @@
+{"title": "Trellix HX Series setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002872642-Trellix-HX-Series-setup-for-Workbench", "date": "2021-02-17T20:44:46Z", "contents": "This article explains how to connect Trellix HX 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\nThis procedure creates a user account for Expel that keeps the Expel activity\nseparate from other activity on the Trellix HX console.\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###  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. Navigate to Admin > Appliance Settings.\n\n  2. Click User Accounts on the left.\n\n    * For Username add Expel.\n\n    * Ensure the Role is set to Admin.\n\n    * Type a Password.\n\n  3. Click Add User.\n\n##  Step 2: Generate API credentials\n\nTo integrate the technology with Workbench, we need to create secure\ncredentials to the API.\n\nThis procedure creates an authentication token that allows the Expel Assembler\nto access the Trellix HX API.\n\n  1. Go to the User Accounts section.\n\n  2. For Username add expelapi.\n\n  3. Make sure the Role is set to API Admin.\n\n  4. Type a Password.\n\n  5. Click Add User.\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. In a new browser tab, log into https://workbench.expel.io.\n\n  2. On the console page, navigate to Settings and click Security Devices.\n\n  3. At the top of the page, click Add Security Device.\n\n  4. Search for and select Trellix HX.\n\n  5. Make the following selections.\n\n![Screen Shot 2021-03-05 at 12.14.06\nPM.png](https://support.expel.io/hc/article_attachments/13874947051283/uuid-b0d55ac2-3c33-1bc9-fced-247a69c9e8c8.png)\n\n    * (On-prem only) Select an Assembler from the list with network connectivity to the Trellix HX device. Select the assembler you set up in Getting connected to Expel Workbench.\n\n    * For Name type the host name of the Trellix HX device.\n\n    * For Location type the geographic location of the appliance.\n\n    * For Server address type the Trellix HX device IP and communications port in the following format: `https://<serverip>:3000`. Find the Device IP in the Trellix HX console > Admin > Appliance Settings > Network.\n\n    * For API Password and API Username type the API Admin credentials previously created in the Trellix HX console in Step 2.\n\n  6. Click Save.\n\n  7. 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####  Related terms\n\nFireEye, FireEye HX, Fire Eye\n\n"}

article_1500002872662.json

@@ -0,0 +1 @@
+{"title": "Okta setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002872662-Okta-setup-for-Workbench", "date": "2021-02-17T20:44:46Z", "contents": "This article explains how to connect Okta 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 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\n  1. Create a user in Okta for Expel.\n\n    * Select Directory and People.\n\n    * Under People select Add person.\n\n      * User type: User\n\n      * First name: Expel\n\n      * Last name: SOC\n\n      * Username: soc+<Your_Organization_Name>@expel.io\n\n###  Tip\n\nYes, the \"+\" sign is part of the email address, and it's important. Click here\nto find out why.\n\n      * Primary email: same as username\n\n      * Password: set by user\n\n      * Select Send user activation email now.\n\n      * Click Save.\n\n  2. Notify your customer success engineer that the registration email is sent.\n\n##  Step 2: Generate API credentials\n\nTo integrate the technology with Workbench, we need to create secure\ncredentials to the API.\n\n  1. Sign into your Okta organization as a user with Read-Only Admin privileges. API tokens have the same permissions as the user who creates them, and if the user permissions change, the API token permissions also change.\n\n    * Okta permissions table:\n\nhttps://help.okta.com/oie/en-us/Content/Topics/Security/administrators-admin-\ncomparison.htm\n\n  2. Open the API page.\n\n    * If you use the Developer Console, select Tokens from the API menu.\n\n    * If you use the Administrator Console (Classic UI), select API from the Security menu, and then select Tokens.\n\n  3. Click Create Token.\n\n  4. Name your token ExpelAPI and click Create Token.\n\n### Note\n\nMake note of your API token, as you only see it 1 time.\n\n  5. Collect your Okta URL (also called an Okta domain).\n\n    * Sign in to your Okta organization with your administrator account.\n\n    * Look for the Okta domain in the upper right corner of the dashboard.\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. Log into https://workbench.expel.io.\n\n  2. Navigate to Settings > Security Devices.\n\n  3. At the top of the page, click Add New Device.\n\n  4. Search for and select Okta.\n\n![Screen Shot 2021-07-16 at 6.18.35\nPM.png](https://support.expel.io/hc/article_attachments/13874872663699/uuid-7adcac13-7d2e-2755-68ec-f04a2c05a797.png)\n\n    * Complete all fields using the credentials and information you collected in Step 1 and Step 2.\n\n  5. Click Save.\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###  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"}

article_1500002872682.json

@@ -0,0 +1 @@
+{"title": "Configuring your OneLogin SSO provider with Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002872682-Configuring-your-OneLogin-SSO-provider-with-Workbench", "date": "2021-02-17T20:44:48Z", "contents": "This article explains setting up your OneLogin SSO provider with Expel\nWorkbench\n\n### Tip\n\nWorkbench logins don't support SCIM. We only support SAML and local logins.\n\n  1. Log into your OneLogin Console and navigate to Administration in the top right corner.\n\n  2. Navigate to Applications > Add App.\n\n  3. Search for SAML and select SAML Test Connector (IdP w/attr w/ sign response).\n\n  4. Under Portal:\n\n    * Display Name: Expel Workbench.\n\n    * Upload our logo and click Save. You can right-click this image and save it locally.\n\n![Expel\nLogo](https://support.expel.io/hc/article_attachments/6789206117395/uuid-8179e3c1-15ce-4bba-d03f-152aaefde479.png)\n\n    * Click Save.\n\n  5. Select Configuration in the left navigation.\n\n  6. Copy information from Expel Workbench to complete the integration. Open a new tab or window and log in to Expel Workbench (https://workbench.expel.io).\n\n  7. Navigate to Organization Settings > My Organizations and select the organization. Then click Integrations > Configure SSO.\n\n  8. Copy and paste the following from Expel Workbench into OneLogin.\n\n    * ACS URL or Single Sign-on URL → ACS (Consumer) URL.\n\n    * Audience URI or Audience → Audience.\n\n    * ACS URI Validator → ACS (Consumer) URI Validator.\n\n    * Leave Yes, allow users to log in locally OR via SSO selected for local logins. This makes initial SSO setup easier. You can change this later.\n\n  9. In Expel Workbench, click Next.\n\n    * Select Parameters from the left navigation.\n\n    * Click the “+” button on the left to add a new parameter.\n\n    * For Field name type the word email and select Include SAML assertion. Click Save.\n\n  10. In OneLogin, click Save in the upper right corner.\n\n    * For Value, select Email from the list and click Save.\n\n  11. Navigate to SSO in the left navigation.\n\n  12. Right-click and open in a new tab or window View Details under the X.509 Certificate.\n\n  13. Copy and paste the X.509 Certificate from OneLogin into Expel Workbench.\n\n  14. Back in the SSO window, copy and paste the following from OneLogin into Expel Workbench.\n\n    * SAML 2.0 Endpoint (HTTP)→ Single Sign-On URL or SAML 2.0 Endpoint.\n\n    * Issuer URL → Issuer or Issuer ID.\n\n  15. Click Save in Expel Workbench.\n\n  16. Click Save in OneLogin.\n\n### Important\n\nBefore signing in with SSO, make sure that:\n\n  * In your SSO provider, Workbench is assigned to all intended users.\n\n  * The user email addresses in your SSO provider match the email that's configured for the users in Workbench. The emails are case sensitive.\n\n  * New members of your organization that need access to Workbench have user accounts created in Workbench and have Workbench assigned to them in your Identity Provider.\n\n  * After you finish testing and setting up, in Workbench, you can disable local logins by going to the Integrations area in Settings. Click Edit from the list, and click No, users can ONLY log in via SSO. Then click Next > Next > Save to save.\n\n"}

article_1500002872702.json

@@ -0,0 +1 @@
+{"title": "Splunk setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002872702-Splunk-setup-for-Workbench", "date": "2021-02-17T20:44:48Z", "contents": "By following these steps, you create a user account for Expel that keeps the\nExpel activity separate from other activity on the Splunk console.\n\n### Note\n\nExpel needs access to the Splunk device or instance through port 8000 (UI) and\n8089 (API). For cloud instances, follow the Splunk Configure IP Allow List\ninstructions to grant Expel these access privileges:\n\n  * Search head API access\n\n  * Search head UI access\n\nExpel has 6 egress IP addresses. All requests to rest API come from 1 of 6 IP\naddresses. We’ve designed this so it can scale significantly without Expel\nneeding to add new IP addresses to the list.\n\n  * 34.75.13.114/32\n\n  * 34.75.152.7/32\n\n  * 35.243.190.98/32\n\n  * 104.196.158.205/32\n\n  * 34.75.81.28/32\n\n  * 34.75.210.18/32\n\n####  In this article\n\n  * Step 1: Enable console access\n\n  * Step 2: Configure the technology in Workbench\n\n  * Step 3: 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\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. Log into Splunk.\n\n  2. Navigate to Settings > Access Controls > Users.\n\n  3. Click the +Add new button.\n\n  4. Fill in the following information:\n\n    * For Name type Expel.\n\n    * For Full name type Expel SOC.\n\n    * For Email address type [email protected].\n\n    * Set the Password.\n\n    * For Time Zone select GMT (or UTC).\n\n    * For Assign roles select User.\n\n    * Clear Require password change on first login.\n\n  5. Click Save.\n\n### Tip\n\nAfter console access is established for Expel, the remaining onboarding steps\nfor this technology can also be performed by Expel. Reach out to your\nengagement manager if this is needed and we're happy to complete the\nintegration!\n\n##  Step 2: 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=splunk.\n\n  2. If your installation is on premises ( **On-prem** ), then select the Assembler connected to the Splunk device. This is the assembler you set up in How to provision Expel Assembler.\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/6758580851987/uuid-1d7afaa0-708c-fc08-e069-46708fc1fe20.png)\n\n  3. Fill in the following information:\n\n![mceclip2.png](https://support.expel.io/hc/article_attachments/6758682390675/uuid-9683d0bc-8faa-9a5a-d373-c47b87f27c83.png)\n\n    * Name: the hostname of the Splunk device.\n\n    * Location: the geographic location of the appliance.\n\n    * Username: the username created in Step 1.\n\n    * Password: the password created in Step 1.\n\n    * Leave the Splunk Enterprise Security instance? field blank.\n\n### Note\n\nIntegration_Vendors: Splunk Enterprise Security alerts require review by Expel\nbefore enabling. Reach out to your engagement manager for details.\n\n    * Server address:\n\n      * Cloud: type the Splunk server address and port 8089. For example: https://<domainname>.splunkcloud.com:8089.\n\n      * On-prem: type the Splunk console IP address and port 8089. For example: https://10.10.10.10:8089/.\n\n  4. Click Save.\n\n  5. 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 3: 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"}

article_1500002872722.json

@@ -0,0 +1 @@
+{"title": "Elastic Endpoint Security (formerly Endgame) setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002872722-Elastic-Endpoint-Security-formerly-Endgame-setup-for-Workbench", "date": "2021-02-17T20:44:50Z", "contents": "This article explains how to connect Elastic Endpoint Security to Workbench.\n\n####  In this article\n\n  * Step 1: Enable console access\n\n  * Step 2: Configure the technology in Workbench\n\n  * Step 3: 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\nThis procedure creates a user account for Expel that keeps the Expel activity\nseparate from other activity on the Elastic Endpoint Security console.\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. Navigate to Administration icon on the left, click Users tab, and click Create New User.\n\n  2. For First name add Expel.\n\n    * For Last name type Admin.\n\n    * For Username type Expel.\n\n    * For User Role select Admin.\n\n### Note\n\nYou can select LEVEL 3 access here, although Expel can't view security\npolicies for the device to advise on best practices and configuration.\nDetection remains unaffected.\n\n    * Create a Password for Expel.\n\n  3. Click Create User.\n\n###  Tip\n\nAfter console access is established for Workbench, the remaining onboarding\nsteps for this technology can also be performed by Expel. Reach out to your\nengagement manager if you want us to help.\n\n##  Step 2: 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. In a new browser tab, log into https://workbench.expel.io.\n\n  2. On the console page, navigate to Settings and click Security Devices.\n\n  3. At the upper right of the page, select Add Security Device.\n\n  4. Search for and select Endgame.\n\n![Screen Shot 2021-03-05 at 10.45.12\nAM.png](https://support.expel.io/hc/article_attachments/6760515566995/uuid-7fb81e1d-d5ad-1519-a94d-452866373c22.png)  \n---  \n  \n  5. Select Cloud or On-prem.\n\n![Screen Shot 2021-07-16 at 5.13.06\nPM.png](https://support.expel.io/hc/article_attachments/13874946501011/uuid-417f9f0c-290b-51cd-c67b-e5075b74e893.png)\n\n    * Select the assembler from the list. (On-prem only)\n\n    * For Name, type the host name of the Elastic Endpoint Security device.\n\n    * For Location, type the geographic location of the appliance.\n\n    * For Username, type Expel from Step 1.\n\n    * For Password, type the password used in Step 1.\n\n    * For Server address, type the management/console IP address of the device to be connected through https. For example: https://127.0.0.1.\n\n    * For File unzip password, type the password to unzip the acquired file. If you don't type a password here, the default Endgame password is used.\n\n    * For Acknowledge alerts, select yes to mark Endgame alerts as _viewed_ after Workbench processes them.\n\n    * For Dismiss alerts, select yes to mark Endgame alerts as _dismissed_ after Workbench processes them.\n\n  6. Click Save.\n\n  7. 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 3: 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####  Related terms\n\nendgame\n\n"}

article_1500002872742.json

@@ -0,0 +1 @@
+{"title": "Darktrace direct setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002872742-Darktrace-direct-setup-for-Workbench", "date": "2021-02-17T20:44:51Z", "contents": "Darktrace is an Intrusion Detection Device (IDS) that leverages machine\nlearning to detect emerging threats, including insider threats, low-and-slow\nattacks, and automated viruses.\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\nExpel requires a Darktrace user account to review Alerts and Models within the\nconsole.\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###  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 located at the top left, select Add New User.\n\n  2. Username: Expel.\n\n  3. Password: set a temporary password — this is changed on initial login.\n\n  4. Account Permissions: select all available permissions, except User Admin or Group Admin. These can be left cleared.\n\n  5. Click OK.\n\n##  Step 2: Generate API credentials\n\nTo integrate the technology with Workbench, we need to create secure\ncredentials to the API.\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. Log into the Darktrace console.\n\n  2. Navigate to Admin > System Config.\n\n  3. Near the bottom of the page, under API Token, click New.\n\n  4. The Darktrace system generates a Token and a Private Token. The Private Token can only be seen 1 time after the token pair is initially generated. Make note of the tokens for onboarding in Workbench. The system can only have 1 token pair, so if one already exists and you don't have a record of this, you must generate another token pair.\n\n### Caution\n\nIf a replacement Token pair is generated, other clients using the API must be\nreconfigured with the new credentials.\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. In a new browser tab, login to https://workbench.expel.io.\n\n  2. On the console page, click Settings and click Security Devices.\n\n  3. At the top of the page, click Add Security Device.\n\n  4. Search for and select your technology.\n\n![Screen Shot 2021-03-05 at 10.31.45\nAM.png](https://support.expel.io/hc/article_attachments/6758676746643/uuid-469986b1-ba69-b1d8-b6b7-747ce4a54525.png)\n\n  5. Select an Assembler from the list. Select the assembler you set up in Getting connected to Expel Workbench.\n\n![Screen Shot 2021-07-16 at 5.29.17\nPM.png](https://support.expel.io/hc/article_attachments/6758578718995/uuid-40a79b52-f7e6-1c45-e276-d202160e9db1.png)\n\n    * Type Name and Location.\n\n    * For Server address, type the server address of the vendor’s server, which must include the port. For example: https://127.0.0.1:443 or myvendordevice.acme.com:443.\n\n    * For Public key, type the API token used to authenticate to the device from Step 2.\n\n    * For Private key, type the private token used to authenticate to the device from Step 2.\n\n  6. Click Save.\n\n  7. 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"}

article_1500002872762.json

@@ -0,0 +1 @@
+{"title": "Azure Log Analytics setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002872762-Azure-Log-Analytics-setup-for-Workbench", "date": "2021-02-17T20:44:51Z", "contents": "Azure Log Analytics aggregates and provides search capabilities over data in\nan Azure deployment. Azure Log Analytics functions as a data store for Azure\napplications, but can also be queried manually.\n\nDepending on policy and configuration, Azure Log Analytics can contain all\nkinds of data relevant to a security team. Most notably, after security audit\npolicies are enabled on Azure VMs, they feed log data to Azure Log Analytics\nwhere it can be queried in the Analytics Portal.\n\n####  In this article\n\n  * About connecting your device\n\n  * About console permissions in your devices\n\n  * Step 1: Enable console access\n\n  * Step 2: Enable Azure application access\n\n  * Step 3: Configure Azure Log Analytics in Workbench\n\n##  About connecting your device\n\nConnecting your device to Workbench allows Workbench to ingest the data. Azure\nLog Analytics data include a great deal of information that can take hours to\nmanually review.\n\n##  About console permissions in your devices\n\nAs you connect your devices to Workbench, you provide Workbench access to\nthose devices through permissions in the devices. These permissions vary from\n1 device technology to another, but we typically need at least Read access to\nyour devices to pull in any logs from those devices into Workbench.\n\nWithout minimum permissions to your devices, the SOC analysts are limited in\ntheir insight into your technology. This can mean they surface more benign\nalerts to your team for further investigation, resulting in increasing the\nworkload for your team, and resulting in alert fatigue.\n\nIf you grant Read access to your devices, we can investigate the device and\nthe logs more deeply and surface relevant alerts to you in Workbench. Allowing\nExpel visibility into the console of your security devices helps our SOC\nanalysts make better decisions on whether an alert is benign or malicious. It\nalso allows our SOC analysts to perform health checks to make sure Workbench\nis not missing alerts from your security devices. Depending on what your\norganization purchased from Expel, the SOC analysts may even be able to\ncontain and/or remediate the issues on your behalf.\n\nUltimately, the more permissions you can grant Workbench, the better and\nfaster the SOC analysts can find and investigate alerts in your environment.\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\n  1. Sign into the Azure portal as a user who is assigned a limited administrator directory role or the Guest Inviter role.\n\n  2. In the navigation pane, click Azure Active Directory.\n\n  3. Under Manage, select Users.\n\n  4. Select New guest user.\n\n  5. On the New user page, click Invite user, fill out the email address ([email protected]), and optionally include a message.\n\n  6. Under roles, add the role Global Reader role.\n\n  7. Click Invite to automatically send the invitation to the guest user. After you send the invitation, the user account is automatically added to the directory as a guest.\n\n##  Step 2: Enable Azure application access\n\n  1. As an Azure administrator, log in to the Azure portal.\n\n  2. Navigate to Azure Active Directory > App registrations and click +New registration.\n\n  3. Fill in the application details. You can fill these in however you want, but we recommend this:\n\n    * Name: Expel \\- Log Analytics API\n\n    * Supported account types: Accounts in this organizational directory only (1st option).\n\n  4. After you fill out the fields, click Register to create the new application.\n\n  5. You should be navigated automatically to the settings page for the Expel Cloud Service app you just created. If not, navigate to Azure Active Directory > App Registrations > View all applications (if you don’t see the new app) > Expel \\- Log Analytics API.\n\n  6. Make a note of the Application (client) ID, Application secret, and the Directory (tenant) ID for use in later steps.\n\n  7. Open API permissions. Click \\+ Add a permission.\n\n  8. Head over to Log Analytic Workspace > Access Control (IAM) > \\+ Add and assign the Log Analytics Reader role to the application and user created in above steps.\n\n##  Step 3: Configure Azure Log Analytics 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. In a new browser tab, login to https://workbench.expel.io/settings/security-devices?setupIntegration=azure_log_analytics.\n\n  2. Fill in the fields like this:\n\n![Screen Shot 2021-03-05 at 8.00.07\nAM.png](https://support.expel.io/hc/article_attachments/13874955961491/uuid-8a5a236e-a81e-c9b0-5b50-efcee117f28f.png)\n\n    * For Name type the host name of the Azure Log Analytics device.\n\n    * For Location type Cloud.\n\n    * For Directory ID, type the ID of the AzureActive Directory (tenant) in the cloud instance.\n\n    * For Application ID, type the ID of the application with access to Azure Log Analytics.\n\n    * For Application secret, type the key used to authenticate the application.\n\n    * For Workspace ID, type the ID of the workspace within Azure Log Analytics.\n\n  3. Click Save.\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###  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"}