diff --git a/article_10012579141523.json b/article_10012579141523.json new file mode 100644 index 0000000000000000000000000000000000000000..edf4cec8ddf7507c19ea4f4813c3c55dbc3fc8b8 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_10853659813395.json b/article_10853659813395.json new file mode 100644 index 0000000000000000000000000000000000000000..cff5773a25c493b54ba15663ff46fe03eebe5063 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_11455980950035.json b/article_11455980950035.json new file mode 100644 index 0000000000000000000000000000000000000000..635df3a99a584f90714e03127ee74106e9e768b9 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_11455981103379.json b/article_11455981103379.json new file mode 100644 index 0000000000000000000000000000000000000000..2b16e2e8520338244e621964ccc621e5336218d2 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_11455981226003.json b/article_11455981226003.json new file mode 100644 index 0000000000000000000000000000000000000000..2285ec7a3218a5dec2c7cd32fca26a4fb91b55ba --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_11455981281299.json b/article_11455981281299.json new file mode 100644 index 0000000000000000000000000000000000000000..ada52f425dbce4403271d1b30c54b72a91143483 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_11455981555603.json b/article_11455981555603.json new file mode 100644 index 0000000000000000000000000000000000000000..fb3578776283c8fe5f89ab764081b56393d645f9 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_11455992258323.json b/article_11455992258323.json new file mode 100644 index 0000000000000000000000000000000000000000..2a6eabfb8e1c84468c93e1a0e1ae0aa41fcb804b --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_11455992575379.json b/article_11455992575379.json new file mode 100644 index 0000000000000000000000000000000000000000..4c9ef4d396246e064949b8522b03a7a75a4e1bfe --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_11455992644371.json b/article_11455992644371.json new file mode 100644 index 0000000000000000000000000000000000000000..e37b48e06b85769bb8d0e5ecfe6ae159ea684251 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_11455992832403.json b/article_11455992832403.json new file mode 100644 index 0000000000000000000000000000000000000000..c4bc73218f2e423668a1ae37d3b1ffd4ac024330 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_11455992924563.json b/article_11455992924563.json new file mode 100644 index 0000000000000000000000000000000000000000..f92d85b84bc21016209fae7ea9c117a3d5dfe16c --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_11742313688595.json b/article_11742313688595.json new file mode 100644 index 0000000000000000000000000000000000000000..ff8075acbea90b049ba26d414de5f742620f2551 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_11742327047827.json b/article_11742327047827.json new file mode 100644 index 0000000000000000000000000000000000000000..fb5783ae306cf6b6ab870a916f1ae7e6066a76da --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_12116548434067.json b/article_12116548434067.json new file mode 100644 index 0000000000000000000000000000000000000000..058c13a4ffef67a300083477ac93a94668178c69 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_12391858961171.json b/article_12391858961171.json new file mode 100644 index 0000000000000000000000000000000000000000..eff8b2da123440bdf758ba9a70b4d0e066355f3f --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_12871722483347.json b/article_12871722483347.json new file mode 100644 index 0000000000000000000000000000000000000000..5b4440e1edb71b243fdc24fb0a1d03743f692381 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_12925742896787.json b/article_12925742896787.json new file mode 100644 index 0000000000000000000000000000000000000000..7196c07e6101e4d62aaf2658973060fc628aaee7 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_12925743005331.json b/article_12925743005331.json new file mode 100644 index 0000000000000000000000000000000000000000..ab7354e100574d275de3b9c054b415644ffd29cc --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_12925743051411.json b/article_12925743051411.json new file mode 100644 index 0000000000000000000000000000000000000000..a3cf18bb830040bc00b61e2dff6225ed8d467b1a --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_12925743290387.json b/article_12925743290387.json new file mode 100644 index 0000000000000000000000000000000000000000..197f3c3c8925f9db8becc6560385a22fb0d7e314 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_12925746962195.json b/article_12925746962195.json new file mode 100644 index 0000000000000000000000000000000000000000..f3a6dd76c9c0d499d7793893e2be8da184f8f9af --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_12925747081875.json b/article_12925747081875.json new file mode 100644 index 0000000000000000000000000000000000000000..de894c754cbd7331b430f22958a74b2cccb219d2 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_12925747142803.json b/article_12925747142803.json new file mode 100644 index 0000000000000000000000000000000000000000..96a40adec8ca38bbf5e0a2302708978ed0722394 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_12925747196051.json b/article_12925747196051.json new file mode 100644 index 0000000000000000000000000000000000000000..e40da09240601cfa64d561954d8f08fcafcc4d12 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_13017623221779.json b/article_13017623221779.json new file mode 100644 index 0000000000000000000000000000000000000000..2a69ce925a69475542594e2fffb3d8d1a0774c26 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_13017623282195.json b/article_13017623282195.json new file mode 100644 index 0000000000000000000000000000000000000000..779b0abf67c91564405ba5c252bca48651bd3c69 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_13017623557267.json b/article_13017623557267.json new file mode 100644 index 0000000000000000000000000000000000000000..9dbc4a081758f5be26fc48ba1726e4d6b50db4ae --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_13017668722707.json b/article_13017668722707.json new file mode 100644 index 0000000000000000000000000000000000000000..3da439ee4f17ee7cfee4c6e0c62d88401c4a35a0 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_13511503596179.json b/article_13511503596179.json new file mode 100644 index 0000000000000000000000000000000000000000..2dde4bcc7fbead753d0ab90a8ed064eb4af49768 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_13511503709587.json b/article_13511503709587.json new file mode 100644 index 0000000000000000000000000000000000000000..2391a76e9ed11e01159f3f59303c3955ccc95008 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_13612714001171.json b/article_13612714001171.json new file mode 100644 index 0000000000000000000000000000000000000000..3eab83ff8d8b276c0f554933b5dd99259844bb33 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_13807470251027.json b/article_13807470251027.json new file mode 100644 index 0000000000000000000000000000000000000000..e10769f6ebb88703790744602df8eaa239866e43 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_14012946928659.json b/article_14012946928659.json new file mode 100644 index 0000000000000000000000000000000000000000..4ef83abc9b5134d87a5063a79d084cf6ee741166 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_14012947037715.json b/article_14012947037715.json new file mode 100644 index 0000000000000000000000000000000000000000..028e3a757e0ee9d2ce6f68d96f266ebdccf57103 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_14049611141779.json b/article_14049611141779.json new file mode 100644 index 0000000000000000000000000000000000000000..8a5d33dff1b658535789daab6a77975a3bfcf1b7 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_1500002718861.json b/article_1500002718861.json new file mode 100644 index 0000000000000000000000000000000000000000..566c48a56f496a350afe83d91ff1a4e9eb3e8589 --- /dev/null +++ b/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 devicehealth@expel.io.\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 \n \n certutil -hashfile expel-assembler-vmware- .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- .ova \n \nLinux\n\n|\n\nSHA256\n\n|\n\nIn a terminal program, run:\n\n \n \n sha256sum ~/Downloads/expel-assembler-vmware- .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: \n Retype new password: \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 --type static --ip --netmask --gateway --dns \n\n 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 \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"} \ No newline at end of file diff --git a/article_1500002718881.json b/article_1500002718881.json new file mode 100644 index 0000000000000000000000000000000000000000..c69133f67cab1b93d203c581f145757ee48f4667 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_1500002718901.json b/article_1500002718901.json new file mode 100644 index 0000000000000000000000000000000000000000..7effef946684895a45e56fad494a9c60b813db98 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_1500002718921.json b/article_1500002718921.json new file mode 100644 index 0000000000000000000000000000000000000000..50225fa2c3282db87ee52bb87c9b068fd7d574b3 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_1500002718961.json b/article_1500002718961.json new file mode 100644 index 0000000000000000000000000000000000000000..c478d33ddda9c828773bc87dd715c17437b82fea --- /dev/null +++ b/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 soc@expel.io.\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"} \ No newline at end of file diff --git a/article_1500002719001.json b/article_1500002719001.json new file mode 100644 index 0000000000000000000000000000000000000000..4c82dda10f15493338dc8cfc2d349b9121ff45c0 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_1500002872602.json b/article_1500002872602.json new file mode 100644 index 0000000000000000000000000000000000000000..0b17022418daa31b9022f9398a067b77d4b89e95 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_1500002872642.json b/article_1500002872642.json new file mode 100644 index 0000000000000000000000000000000000000000..354b242cc7c608f49d4a2f70e41a0312da6db5ea --- /dev/null +++ b/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://: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"} \ No newline at end of file diff --git a/article_1500002872662.json b/article_1500002872662.json new file mode 100644 index 0000000000000000000000000000000000000000..877f4e512cb2081847c182368b25d3f66849f34d --- /dev/null +++ b/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+@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"} \ No newline at end of file diff --git a/article_1500002872682.json b/article_1500002872682.json new file mode 100644 index 0000000000000000000000000000000000000000..1937234ba3473fb1254a2371ff669b154ba09daa --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_1500002872702.json b/article_1500002872702.json new file mode 100644 index 0000000000000000000000000000000000000000..f10824e02dd8420cc53cfa5cbfb0b6d6df63ee57 --- /dev/null +++ b/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 soc@expel.io.\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://.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"} \ No newline at end of file diff --git a/article_1500002872722.json b/article_1500002872722.json new file mode 100644 index 0000000000000000000000000000000000000000..4cc92076117adb0d32b86e88f0d296df77b204b5 --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_1500002872742.json b/article_1500002872742.json new file mode 100644 index 0000000000000000000000000000000000000000..0b1637c31f4f406fa96ed9694e2276496bac7daa --- /dev/null +++ b/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"} \ No newline at end of file diff --git a/article_1500002872762.json b/article_1500002872762.json new file mode 100644 index 0000000000000000000000000000000000000000..6ac67dcd7abb6f6b19af781ec4c123ba634d1c92 --- /dev/null +++ b/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 (expel_analyst@expel.io), 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"} \ No newline at end of file diff --git a/article_1500002872822.json b/article_1500002872822.json new file mode 100644 index 0000000000000000000000000000000000000000..dce1f75b760bb493bf282079473dce51ef95c6a2 --- /dev/null +++ b/article_1500002872822.json @@ -0,0 +1 @@ +{"title": "Cisco AMP setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002872822-Cisco-AMP-setup-for-Workbench", "date": "2021-02-17T20:44:53Z", "contents": "This article explains how to connect Cisco AMP 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\nThis procedure creates a user account for Expel that keeps the Expel activity\nseparate from other activity on the Cisco AMP 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 Accounts > Users.\n\n 2. Click \\+ New User.\n\n 3. Add the user.\n\n * For First Name add Expel.\n\n * For Last Name add SOC.\n\n * For Login Email add soc+@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 * Select Administrator checkbox.\n\n 4. Click Create.\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 Accounts > API Credentials.\n\n 2. Click +New API Credential.\n\n 3. For Application name enter **expelapi**.\n\n 4. For Scope select Read-Only.\n\n 5. Click Create.\n\n 6. A new page opens with your API Key Details. Save these items as they are not easily accessible later in the process and are needed for onboarding in Workbench.\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, 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 Cisco.\n\n 5. For Name type the host name of the Cisco AMP device.\n\n![Screen Shot 2021-07-16 at 4.55.13\nPM.png](https://support.expel.io/hc/article_attachments/13874927500435/uuid-642448ba-c609-eb95-20d1-46ca9bfeab92.png)\n\n * For Location type the geographic location of the device.\n\n * For API key and Client ID, type the API credentials generated in Step 2.\n\n * For Username and Password type credentials previously created in the Cisco AMP console.\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"} \ No newline at end of file diff --git a/article_1500002872902.json b/article_1500002872902.json new file mode 100644 index 0000000000000000000000000000000000000000..26bf33820fd489de12a71cbe284b04b01680119e --- /dev/null +++ b/article_1500002872902.json @@ -0,0 +1 @@ +{"title": "VMware Carbon Black Cloud setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002872902-VMware-Carbon-Black-Cloud-setup-for-Workbench", "date": "2021-02-17T20:44:54Z", "contents": "This article explains how to connect VMware Carbon Black Cloud 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 VMware Carbon Black Cloud 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 gear icon on left side and click Users. Then click Add User on the top right of the screen.\n\n 2. For First name type Expel.\n\n * For Last name type SOC.\n\n * For Email, type soc+@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 * For Role select Level 2 Analyst.\n\n 3. Click Save.\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### Generate an API key with view all permissions\n\n 1. In the VMware Carbon Black Cloud console, navigate to Settings > Roles.\n\n 2. Navigate to Settings > API Keys.\n\n 3. Create a new API key by selecting Add API Key in the upper right corner.\n\n 4. Type a name for the new key. We suggest Expel SOC.\n\n 5. From the Access Level list, select Custom.\n\n 6. From the Custom Access Level list, select either the View All role or the role you created above.\n\n 7. Complete the rest of the information and click Save to create the new key.\n\n 8. Make a record of the API ID and API Secret Key for later.\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/settings/security-devices?setupIntegration=carbon_black_threat_hunter.\n\n 2. Type these details:\n\n![mceclip2.png](https://support.expel.io/hc/article_attachments/13874950327059/uuid-e4a3041c-ad7d-2890-19ae-\ncbe54c84bcd7.png)\n\n * For Name type the host name of the device.\n\n * For Location type the geographic location of the appliance.\n\n * For Server Address, type the VMware Carbon Black Cloud server address, usually https://defense-prod05. conferdeploy.net/\n\n * For Org ID, type your CB Organization ID.\n\n * For Org Key, type the Org Key.\n\n * For API ID, type the API ID created in Step 2.\n\n * For API Key, type the API Secret Key created 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 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\nCB ThreatHunter, CB Defense\n\n"} \ No newline at end of file diff --git a/article_1500002872922.json b/article_1500002872922.json new file mode 100644 index 0000000000000000000000000000000000000000..d3717f85beb80500a295660afc0b17f67ef23c48 --- /dev/null +++ b/article_1500002872922.json @@ -0,0 +1 @@ +{"title": "AWS CloudTrail: Existing CloudTrail setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002872922-AWS-CloudTrail-Existing-CloudTrail-setup-for-Workbench", "date": "2021-02-17T20:44:55Z", "contents": "This article describes how to connect your existing AWS CloudTrail to the\nExpel Workbench.\n\nIf you're...\n\n|\n\nuse...\n\n|\n\nNotes \n \n---|---|--- \n \nconnecting an existing CloudTrail\n\n|\n\nthis article\n\n|\n\nYou must already have a trail configured to send CloudTrail events to a S3\nbucket.\n\nYou must already have an IAM (Identity and Access Management) Role for\nWorkbench to authenticate with. To set this up, follow Step 6 of the AWS\nCloudTrail - New CloudTrail setup for Workbench article. \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 that includes Control Tower\n\n|\n\nthe Control Tower connection steps\n\n| \n \nAmazon S3 notifications can only be configured for 1 Simple Queue Service\n(SQS) queue per bucket. This poses a problem if you want to hook up Workbench\nto your CloudTrail bucket if you're already sending notifications to an SQS\nqueue for internal reasons.\n\nIn this article, we show how you can route S3 notifications through SNS\n(simple notification service) to a different SQS queue that Workbench can poll\nfrom.\n\n#### In this article\n\n * About connecting your device\n\n * Before you start\n\n * Information to record\n\n * About connecting your device\n\n * Permissions description and explanation\n\n * Step 1: Create a new SNS topic\n\n * Step 2: Create an SQS queue for S3 notifications\n\n * Step 3: Subscribe SQS queue to SNS topic\n\n * Step 4: Enable S3 event notifications to SNS topic\n\n * Step 5: Grant ExpelIAM Role access to SQS queue\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### Information to record\n\n**Field**\n\n|\n\n**Description** \n \n---|--- \n \nS3 bucket ARN (Amazon Resource Name)\n\n|\n\nThe unique identifier for the S3 bucket where CloudTrail events are being\nsent. \n \nSQS queue ARN\n\n|\n\nThe unique identifier for the SQS queue that Workbench uses to consume S3\nnotifications. \n \nSQS queue URL\n\n|\n\nThe URL for the SQS queue that Workbench uses to consume S3 notifications. \n \nSNS topic ARN\n\n|\n\nThe unique identifier for the SNS topic that routes S3 notifications to the\nSQS queue. \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: Create a new SNS topic\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\n 4. In the JSON editor, paste the below policy substituting the YOUR_TOPIC_ARN and YOUR_S3_ARN fields with your values. This policy allows S3 to publish notifications to the topic for your CloudTrail bucket.\n \n {\n \"Version\": \"2008-10-17\",\n \"Id\": \"expel-topic-policy-ID\",\n \"Statement\": [\n {\n \"Sid\": \"expel-statement-ID\",\n \"Effect\": \"Allow\",\n \"Principal\": {\n \"AWS\":\"*\"\n },\n \"Action\": [\n \"SNS:Publish\"\n ],\n \"Resource\": \"YOUR_TOPIC_ARN\",\n \"Condition\": {\n \"ArnLike\": { \n \"aws:SourceArn\": \"YOUR_S3_ARN\"\n }\n }\n }\n ]\n } \n \n--- \n \n 5. Click Create Topic.\n\n## Step 2: Create an SQS queue for S3 notifications\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 below policy substituting the YOUR_SQS_QUEUE_ARN and YOUR_SNS_TOPIC_ARN fields with your values.\n \n {\n \"Version\": \"2012-10-17\",\n \"Id\": \"YOUR_QUEUE_ARN/SQSDefaultPolicy\",\n \"Statement\": [\n {\n \"Sid\": \"Sid1572965666162\",\n \"Effect\": \"Allow\",\n \"Principal\": {\n \"AWS\": \"*\"\n },\n \"Action\": \"SQS:SendMessage\",\n \"Resource\": \"YOUR_SQS_QUEUE_ARN\",\n \"Condition\": {\n \"StringEquals\": {\n \"aws:SourceArn\": \"YOUR_SNS_TOPIC_ARN\"\n }\n }\n }\n ]\n }\n\n## Step 3: Subscribe SQS queue to SNS topic\n\nNow that we’ve 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, type the required fields to configure the subscription.\n\n**Field**\n\n|\n\n**Value** \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 4: 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.\n\n * Send to SNS topic.\n\n * Select your SNS topic we created earlier.\n\n 4. Click Save changes.\n\n## Step 5: Grant ExpelIAM Role access to SQS queue\n\nAt this point we configured S3 notifications → SNS topic → SQS queue. The\nfinal step involves granting the existing ExpelIAM Role access to poll events\nfrom the SQS queue and the S3 bucket.\n\n 1. Navigate to Services > IAM > Expel Role.\n\n 2. Create and add a new inline policy to the Expel Role. Grant the policy these permissions:\n\n * SQS Permissions\n\n * DeleteMessage\n\n * DeleteMessageBatch\n\n * ReceiveMessage\n\n * S3 Permissions\n\n * GetObject\n\n * Expel Permissions\n \n {\n “Version”: “2012-10-17”,\n “Statement”: [\n {\n “Action”: [\n “sqs:DeleteMessage”,\n “sqs:DeleteMessageBatch”,\n “sqs:ReceiveMessage”\n ],\n “Effect”: “Allow”,\n “Resource”: “YOUR_SQS_QUEUE_ARN”\n },\n {\n “Action”: [\n “s3:GetObject”\n ],\n “Effect”: “Allow”,\n “Resource”: “YOUR_S3_BUCKET_ARN/*”\n }\n ]\n } \n \n--- \n \n 3. Congratulations! You configured S3 notifications to an SQS queue through SNS. Contact your engagement manager for details on how to finish onboarding.\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"} \ No newline at end of file diff --git a/article_1500002872982.json b/article_1500002872982.json new file mode 100644 index 0000000000000000000000000000000000000000..5226213c81de457af63540467691a9d81f1218ff --- /dev/null +++ b/article_1500002872982.json @@ -0,0 +1 @@ +{"title": "Configuring your Azure SSO Provider with Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002872982-Configuring-your-Azure-SSO-Provider-with-Workbench", "date": "2021-02-17T20:45:00Z", "contents": "This article explains setting up your Azure 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 Azure console.\n\n 2. In the search bar at the top, search for Enterprise Applications and navigate to it.\n\n 3. On the page, select New Application.\n\n 4. On the Add your own application page, provide a name for the application and click Add.\n\n 5. On the newly created application page, click Properties on the left menu bar under Manage.\n\n 6. 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/6789210867987/uuid-8179e3c1-15ce-4bba-d03f-152aaefde479.png)\n\n 7. Click Overview on the left menu bar to navigate to the application’s overview page.\n\n 8. Click Set up single sign-on.\n\n 9. For Select a single sign-on method, click SAML.\n\n 10. You are now on the SAML-based Sign-on page in Azure. Edit section 1- Basic SAML Configuration.\n\n 11. In Expel Workbench copy the field Audience URI and paste it in Identifier (Entity ID) in Section 1 in Azure.\n\n### Note\n\nYou can put anything in this field. We recommend this value, but if your value\nnaming standards are different, follow your standards. However, on step 17, be\nconsistent and use this exact value or URI there, too.\n\n 12. In Expel Workbench, copy information to complete the integration. Open a new tab or window and log into Expel Workbench (https://workbench.expel.io).\n\n 13. Navigate to Organization Settings > My Organizations and select the organization. Then select the Integrations tab and click Configure SSO > Single Sign-on.\n\n 14. Copy and paste the following from Expel Workbench into Azure:\n\n * ACS URL or Single Sign-on URL → Reply URL (Assertion Consumer Service URL).\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![Screen Shot 2021-03-05 at 10.12.34\nAM.png](https://support.expel.io/hc/article_attachments/6760304974099/uuid-e05f0420-d511-849c-c630-822d6f67b5ef.png)\n\n 15. In Azure, edit Single sign-on section 2 User Attributes & Claims, click Add new claim.\n\n 16. In the Manage Claim view:\n\n![Screen Shot 2021-03-05 at 10.13.05\nAM.png](https://support.expel.io/hc/article_attachments/6760305026195/uuid-4dfcc69f-7dc5-6061-8f6e-b5d2af78e9f9.png)\n\n * Type the word **email** (case-sensitive) under Name.\n\n * Leave the Namespace empty.\n\n * Select Attribute for Source.\n\n * Select the appropriate value for your organization for Source attribute. This field populates each user’s email address, and can be different from the example shown.\n\n * Click Next.\n\n 17. In Azure, navigate back to Single sign-on on the left menu bar. Copy the following values from Azure into Expel Workbench.\n\n * Login URL → Single Sign-on URL or SAML 2.0 Endpoint.\n\n * Default Entity ID → Issuer or Issuer ID or if you chose a different value in step 11, use that exact value or URI here.\n\n * Certificate (Base64) → Certificate.\n\n 18. In Expel Workbench, click Save.\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"} \ No newline at end of file diff --git a/article_1500002873002.json b/article_1500002873002.json new file mode 100644 index 0000000000000000000000000000000000000000..0f1142f5a7a6922d2a1899205384d225729f7512 --- /dev/null +++ b/article_1500002873002.json @@ -0,0 +1 @@ +{"title": "Azure Cloud (direct) setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002873002-Azure-Cloud-direct-setup-for-Workbench", "date": "2021-02-17T20:45:00Z", "contents": "This article provides prerequisites and onboarding steps for Azure Cloud\n(direct).\n\n## Wizard vs. Manual Onboarding\n\nWe’ve made onboarding easier! You can use our Azure Wizard, which uses Azure\ntemplates, to programmatically connect your Azure instance.\n\nYou can easily deploy RBAC subscription roles in Azure, allowing you to decide\nwhether Expel should monitor 1 or more subscriptions. Expel can also connect\nto existing log storage accounts, or create new ones on your behalf.\n\n### Important\n\nCreating and maintaining additional storage logs can result in additional fees\nfrom Microsoft Azure. If you enable storage logging, it's applied to all\nstorage accounts deployed in your subscription.\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 * Azure RBAC permissions and roles\n\n * Step 1: Enable console access\n\n * Step 2: Enable Azure Application access\n\n * Option 1: Enable Azure Enterprise Application\n\n * Option 2: Create custom Azure AD application\n\n * Step 3: Enable roles within Azure subscriptions\n\n * Step 4: Enable Azure resource logs\n\n * Enable Azure storage logs\n\n * Enable Azure storage logs: classic\n\n * Step 5: Configure Azure in Workbench\n\n## About connecting your device\n\nConnecting your device to Workbench allows Workbench to ingest the logs. Azure\nlogs include a great deal of information that can take hours to manually\nreview. And not all Azure alerts need attention.\n\nExpel uses API integrations to connect directly to the Microsoft Azure\nplatform. We support authentication through an AzureActive Directory app. To\ncollect data, Workbench communicates directly with APIs, including the\nMicrosoft Security Graph API to poll alerts from Microsoft Sentinel. Workbench\nalso queries Azure Log Analytics to enrich Sentinel alerts with the Azure Log\nAnalytics context that originally generated that alert.\n\n## Before you start\n\n 1. Have an AzureActive Directory (AD) admin on hand to grant permissions.\n\n 2. Install Microsoft 365 to monitor AD activity logs.\n\nMicrosoft allows using the Microsoft 365 Management Activity API to retrieve\ninformation about various user, admin, system, and policy actions and events\nfrom Microsoft 365 AND AzureActive Directory activity logs. For example, this\nis how Expel pulls Azure sign-in logs. If you want us to monitor this type of\ndata for your environment, enable audit logging and onboard Microsoft 365 into\nWorkbench.\n\n 3. Enabling Azure Defender is strongly recommended by Expel to monitor Azure infrastructure. Azure Defender can be enabled on a per resource basis or for resource groups. The following Azure Defender services are currently monitored by Expel:\n\n * Azure Storage\n\n * Azure KeyVault\n\n * Azure Resource Manager\n\n * Azure App Service\n\n * Azure SQL Service\n\n * Azure Cosmos DB Service\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## Azure RBAC permissions and roles\n\nExpel Workbench needs access to the following roles and operations in Azure.\n\nMicrosoft Azure Integration Application Permissions\n\nThis permission...\n\n|\n\ndoes this... \n \n---|--- \n \nSecurityEvents.Read.All\n\n|\n\nIngests VendorAlerts from a direct poller. \n \nUser.Read\n\n|\n\nCreates an application. \n \nThese RBAC operations are needed to read Activity Logs:\n\nThis operation...\n\n|\n\ndoes this... \n \n---|--- \n \nAction - Microsoft.Insights/eventtypes/values/read\n\n|\n\nList Activity log events (management events) in a subscription. This\npermission applies to both programmatic and portal access to the Activity log. \n \nThese RBAC operations are needed to read Storage Logs using Azure AD Auth:\n\nThis operation...\n\n|\n\ndoes this... \n \n---|--- \n \nAction - Microsoft.Storage/storageAccounts/read\n\n|\n\nReturns the list of storage accounts or gets the properties for the specified\nstorage account. \n \nAction - Microsoft.Storage/storageAccounts/blobServices/containers/read\n\n|\n\nReturns list of containers. \n \nDataAction -\nMicrosoft.Storage/storageAccounts/blobServices/containers/blobs/read\n\n|\n\nReturns a blob or a list of blobs. \n \nThese RBAC operations are needed to read Storage Logs using Shared Key Auth:\n\nThis operation...\n\n|\n\ndoes this... \n \n---|--- \n \nAction - Microsoft.Storage/storageAccounts/read\n\n|\n\nReturns the list of storage accounts or gets the properties for the specified\nstorage account. \n \nAction - Microsoft.Storage/storageAccounts/blobServices/containers/read\n\n|\n\nReturns list of containers. \n \nAction - Microsoft.Storage/storageAccounts/listKeys/action\n\n|\n\nReturns the access keys for the specified storage account. \n \nThese RBAC operations are needed to query Azure Log Analytics\n\nThis operation...\n\n|\n\ndoes this... \n \n---|--- \n \nAction - Microsoft.OperationalInsights/workspaces/analytics/query/action\n\n|\n\nSearch using new engine. \n \nThese roles roll up under the following built-in RBAC roles:\n\nThis role...\n\n|\n\ndoes this... \n \n---|--- \n \nGlobal Reader\n\n|\n\nRead everything that a Global Administrator can, but not update anything.\nRequired role to ingest logs. \n \nLog Analytics Reader\n\n|\n\nView and search all monitoring data as well as view monitoring settings,\nincluding viewing the configuration of Azure diagnostics on all Azure\nresources. Required role to ingest logs. \n \nStorage Blob Data Reader or Storage Account Contributor (only if using shared\nkey auth)\n\n|\n\nStorage Blob Data Reader: read and list Azure Storage containers and blobs.\nRequired role to ingest logs.\n\nStorage Account Contributor: allows management of storage accounts. Provides\naccess to the account key, which can be used to access data via Shared Key\nauthorization. Required role to ingest logs. \n \n### Remediation capabilities\n\nThis permission...\n\n|\n\ndoes this... \n \n---|--- \n \nDisable user account\n\n|\n\nAllows the app to enable and disable users' accounts, on behalf of the signed-\nin user. \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 AzureActive 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 (expel_analyst@expel.io), 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.\n\n 8. 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\nTo integrate the technology with Expel, we need to create secure credentials\nto the API. You have 2 options for enabling API access:\n\n * Option 1: Enable the ExpelAzure Integration Enterprise Application within Azure.\n\n * Option 2: Create a custom AzureActive Directory (AD) Application.\n\nEnabling the Enterprise Application is the recommended approach. However,\nbecause Enterprise Application supports access for multiple Microsoft\nintegrations (Sentinel, Azure Log Analytics, and so on), it may be that the\npermissions granted to the Enterprise Application are more than the minimum\nrequired for the Azure integration specifically.\n\nThe second option is offered for if the absolute minimum permissions are\nrequired. In either case, the table below lists the required items to be\nobtained during this step:\n\n**We need this...**\n\n|\n\n**and it's...** \n \n---|--- \n \nDirectory (tenant) ID\n\n|\n\nUnique identifier for your Azure AD instance. Expel needs this information to\nroute our API requests to the right place. Required in all cases. \n \nApplication (client) ID (Option 2 only)\n\n|\n\nUnique identifier for the application you create that grants Expel the access\nit needs to your Azure instance. Required if you are manually onboarding. \n \nApplication (client) Secret (Option 2 only)\n\n|\n\nAPI secret that allows Expel to authenticate as the created application to\nyour Azure instance. Required if you are manually onboarding. \n \n### Option 1: Enable Azure Enterprise Application\n\n 1. As an Administrator, navigate to the Expel Admin Consent Page.\n\n 2. Review and accept requested permissions.\n\n 3. The ExpelAzure Integration app appears under Enterprise Applications. Review properties and make sure that all permissions are properly granted. These permissions are:\n\nThis permission...\n\n|\n\nallows this... \n \n---|--- \n \nUser.Read\n\n|\n\nUsers to sign in to the app and allows the app to read the profile of signed-\nin users. It also allows the app to read basic company information of signed-\nin users. \n \nSecurityEvents.Read.All\n\n|\n\nThe app to read your organization’s security events without a signed-in user. \n \nUser.ReadWrite.All\n\n|\n\nThe app to read and update user profiles without assigned in user. \n \nUser.ReadAll\n\n|\n\nThe app to read user profiles without a signed in user. \n \nData.Read\n\n|\n\nThis application to access Log Analytics data. \n \n\n### Option 2: Create custom Azure AD application\n\n 1. As an Azure administrator, log in to the Azure Portal.\n\n 2. Navigate to AzureActive 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 the following:\n\n * Name: Expel Cloud Service.\n\n * Supported account types: accounts in this organizational directory only (first option).\n\n 4. After you fill out the fields, click Register to create the new application.\n\n 5. The settings page for the Expel Cloud Service app you just created opens.\n\nIf not, navigate to AzureActive Directory > App Registrations > View all\napplications (if you don’t see the new app) > Expel Cloud Service.\n\n * Make a note of the Application (client) ID and the Directory (tenant) ID for use in later steps.\n\n 6. Open API permissions. Click \\+ Add a permission. Add these permissions.\n\nIn APIs my organization uses, locate this permission...\n\n|\n\nSelect this value and click + Add permissions \n \n---|--- \n \ntype Log Analytics and select Log Analytics API > Application Permissions.\n\n|\n\nData.Read \n \ntype Microsoft Graph and select Microsoft Graph > Application Permissions.\n\n|\n\nSecurityEvents.Read.All \n \n 7. After you assign the permissions, click Grant admin consent and Yes.\n\n 8. Navigate to Expel Cloud Service > Certificates & secrets to begin create an API key (aka client secret). To create a new key, click +New client secret.\n\n * Add a description for the secret (for example: ExpelAPI) and select Never for expiration. Click Add to create the secret.\n\n * You see a new secret (API Key) appear under Client secrets. Copy the value and save it for later. It disappears after you navigate away from this screen.\n\n## Step 3: Enable roles within Azure subscriptions\n\nSome event sources within Azure require Role-Based Access (RBAC) roles to be\ngranted to the Azure AD Application within each Azure subscription. One of\nthese RBAC roles granted to our Azure AD Application should also be granted to\nthe Expel user created in Step 1 to allow Expel to investigate further into\nany alerts.\n\nThis section walks through granting the Azure Log Analytics Reader role to\nboth the Azure AD Application from Step 2 and the Expel user from Step 1.\n\n 1. Navigate to Subscriptions in the main Azure service menu by searching Subscriptions.\n\n 2. Select the subscription(s) Workbench will monitor. This step is a requirement or Workbench cannot poll any logs. Repeat the steps below for each subscription.\n\n 3. Add the below roles by clicking Access Control (IAM) > +Add > Add role assignment, assigning access to Azure AD user, group or application, and selecting the ExpelAzure Integration enterprise app or Expel Cloud Service app that you created earlier. \n\n * Log Analytics Reader: Required role to ingest logs.\n\n 4. Repeat the above step and assign Log Analytic Reader role to Azure AD expel_analyst@expel.io.\n\n## Step 4: Enable Azure resource logs\n\nThe ExpelAzure Integration monitors alerts and logs across a variety of Azure\nresources. Some of these alerts and logs are accessible by default, but some\nmust be enabled for Workbench to monitor that particular resource.\n\nThe following Azure resources require user configuration to be monitored. Note\nthat not all Azure deployments use these resources and enabling logging within\nthe resources only widens the Expel default monitoring capabilities for Azure.\n\n### Create a resource log storage account\n\nThe Expel integration collects resource logs from an Azure Storage Account.\nThis section outlines how to create that storage account and provide access to\nExpel.\n\n 1. Create a V2 Storage account.\n\n 2. Add the below role by clicking Access Control (IAM) > +Add > Add role assignment, assigning access to Azure AD user, group or application, and selecting the ExpelAzure Integration enterprise app or Expel Cloud Service app that was created earlier.\n\n * Storage Blob Data Reader: Required role to ingest logs.\n\n 3. Click Save.\n\n 4. Storage accounts can have Network Access Control Lists (ACLs) set that limit which IP addresses can access those accounts. Expel has 6 egress IP addresses that can be allowed. All requests to storage accounts come from 1 of 6 IP addresses. We’ve designed this so it can scale significantly without us having to add new IP addresses to the 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 5. Azure also provides a way to allow for logs to be read from these types of accounts without having to enable access or change existing Network ACLs. Navigate to Networking from the menu and click Firewalls and virtual networks.\n\n 6. If Allow access from is set to Selected networks, select the Allow read access to storage logging from any network to allow access to logs.\n\n### Note\n\nThe access to these logs is still managed through RBAC roles.\n\n### Enable Azure storage logs\n\nAzure Storage logs gives Workbench context around Azure user activity to help\nus to determine whether that activity is malicious. If you’re unsure of\nwhether to enable logging for storage accounts, work with your engagement\nmanager to help determine what approach is best for you.\n\n 1. Navigate to the Storage Account view within the Azure portal. The following steps must be done for each Storage Account.\n\n 2. Select Diagnostic settings menu.\n\n 3. For each storage type: Blob, File, Queue, and Table, click Add diagnostic setting.\n\n 4. For the log category, select StorageRead, StorageWrite, StorageDelete, and archive to the storage account created in previous steps.\n\n 5. Click Save.\n\n 6. Repeat these steps each storage account that Expel must monitor.\n\n### Enable Azure storage logs: classic\n\nIf you are using Classic deployment, use the following steps to enable Classic\nstorage account logging.\n\n 1. Navigate to the Storage Account view within the Azure portal. The following steps must be done for each Classic Storage Account:\n\n 2. Select Diagnostics settings (classic) menu.\n\n 3. Turn Status to On if not already set. Ensure each operation is selected under Logging section for each tab: Blob, File, Queue, and Table properties.\n\n 4. Click Save.\n\n 5. Assign the Expel Enterprise Application or Custom AzureActive Directory (AD) Application to the Storage Blob Data Reader role for each Classic Storage Account that is going to be monitored. Access Control (IAM) > +Add > Add role assignment. See beginning of Step 4 for details.\n\nFor the Storage Blob Data Reader role for each Classic Storage Account that is\ngoing to be monitored: Access Control (IAM) > +Add > Add role assignment, see\nbeginning of Step 4 for details.\n\n## Step 5: Configure Azure 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, log into https://workbench.expel.io/settings/security-devices?setupIntegration=azure.\n\n 2. Complete all fields using the credentials and information you collected in Option 1 or Option 2.\n\n![Screen Shot 2021-03-05 at 12.38.23\nPM.png](https://support.expel.io/hc/article_attachments/6760430172563/uuid-\ndc2f46e8-dba8-70d8-e080-3152bfe03841.png)\n\n**In this field...**\n\n|\n\n**put this** information... \n \n---|--- \n \nSIEM\n\n|\n\nSelect Expel Cloud Service. \n \nName\n\n|\n\nThe name you assign the security device. \n \nLocation\n\n|\n\nMicrosoft Cloud. \n \nDirectory (tenant) ID\n\n|\n\nAzure AD Directory/Tenant ID. \n \nApplication (client) ID\n\n(Option 2 only)\n\n|\n\nThe AzureApplication (Client) ID that we saved in Option 2. \n \nApplication (client) Secret\n\n(Option 2 only)\n\n|\n\nThe Client Secret that you saved in Option 2. \n \nUse storage account contributor role (Y/N)\n\n|\n\nLeave this blank - this field is only used to support legacy onboarding. \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"} \ No newline at end of file diff --git a/article_1500002873022.json b/article_1500002873022.json new file mode 100644 index 0000000000000000000000000000000000000000..5416c65dfca552d936fa0bf9c0e51d4b25c12b16 --- /dev/null +++ b/article_1500002873022.json @@ -0,0 +1 @@ +{"title": "Microsoft Sentinel setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500002873022-Microsoft-Sentinel-setup-for-Workbench", "date": "2021-02-17T20:45:01Z", "contents": "This article provides prerequisites and onboarding steps for Microsoft\nSentinel.\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 * Microsoft Sentinel permissions and roles\n\n * Step 1: Enable console access\n\n * Step 2: Enable API access for Workbench\n\n * Option 1: Enable the ExpelAzure Integration Enterprise Application within Azure\n\n * Option 2: Create custom Azure AD application\n\n * Step 3: Enable Azure Log Analytics access\n\n * Option 1: Enable Azure Log Analytics access per workspace\n\n * Option 2: Enable Azure Log Analytics access per subscription\n\n * Step 4: Configure Microsoft Sentinel in Workbench\n\n## About connecting your device\n\nConnecting your device to Workbench allows Workbench to ingest the logs. Azure\nlogs include a great deal of information that can take hours to manually\nreview. And not all Azure alerts need attention.\n\nExpel uses API integrations to connect directly to the Microsoft Azure\nplatform. We support authentication through an AzureActive Directory app. To\ncollect data, Workbench communicates directly with APIs, including the\nMicrosoft Security Graph API to poll alerts from Microsoft Sentinel. Workbench\nalso queries Azure Log Analytics to enrich Sentinel alerts with the Azure Log\nAnalytics context that originally generated that alert.\n\n## Before you start\n\nBefore getting started, make sure you have an AzureActive Directory (AD) admin\non hand to grant permissions.\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## Microsoft Sentinel permissions and roles\n\nExpel Workbench requires a combination of Microsoft Azure AD Application\npermissions as well as a role assigned to the Microsoft Azure AD application.\n\nTo make requests to the Microsoft Graph Security API, the Microsoft Azure AD\nApplication must have this Microsoft Graph API permission:\n\nThis permission...\n\n|\n\ndoes this... \n \n---|--- \n \nSecurityEvents.Read.All\n\n|\n\nAllows the app to read your organization’s security events on behalf of the\nsigned-in user. \n \nTo query Log Analytics workspace data, the Microsoft Azure AD Application must\nhave this Log Analytics API permission:\n\nThis permission...\n\n|\n\ndoes this... \n \n---|--- \n \nData.Read\n\n|\n\nReads Log Analytics data. \n \nThe Microsoft Azure AD Application must also be assigned this role either for\nthe subscription that contains the Microsoft Sentinel Workspace or directly w/\nthe Microsoft Sentinel Workspace.\n\nThis role...\n\n|\n\ndoes this... \n \n---|--- \n \nLog Analytics Reader\n\n|\n\nViews and searches all monitoring data as well as views monitoring settings,\nincluding viewing the configuration of Azure diagnostics on all Azure\nresources. \n \n### Remediation Capabilities\n\nThis permission...\n\n|\n\ndoes this... \n \n---|--- \n \nDisable user account\n\n|\n\nAllows the app to enable and disable users' accounts, on behalf of the signed-\nin user. \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 in to the Azure portal as a user who's assigned a limited administrator directory role or the Guest Inviter role.\n\n 2. In the navigation pane, select AzureActive Directory.\n\n 3. Under Manage, select Users > New guest user.\n\n 4. On the New user page, select Invite user, fill out the email address (expel_analyst@expel.io), and optionally include a message.\n\n 5. Under roles, add the Global Reader role.\n\n 6. Select Invite to automatically send the invitation to the guest user.\n\n 7. After you send the invitation, the user account is automatically added to the directory as a guest.\n\n## Step 2: Enable API access for Workbench\n\nTo integrate Microsoft Sentinel with Workbench, we need to create secure\ncredentials to the API. You have 2 options for enabling API access:\n\n * Option 1: Enabling the ExpelAzure Integration Enterprise Application within Azure\n\n * Option 2: Creating a custom AzureActive Directory (AD) Application\n\nIn most cases, enabling the Enterprise Application (option 1) is the\nrecommended approach. However, because Enterprise Application supports access\nfor multiple Microsoft integrations (Azure, Microsoft Sentinel, Azure Log\nAnalytics, and so on), it can be the case that the permissions granted to the\nEnterprise Application are more than the minimum required for the Microsoft\nSentinel integration alone.\n\nThe second option is for cases where the absolute minimum permissions are\nrequired. In either case, the table below lists the required items that should\nbe obtained during this step:\n\n**Item we need**\n\n|\n\n**Description** \n \n---|--- \n \nAzure Directory\n\n(Tenant) ID\n\n|\n\nA unique identifier for your Azure instance. Workbench needs this information\nto route our API requests to the right place. \n \nApplication (client) ID\n\n(Option 2 only)\n\n|\n\nA unique identifier for the application you create that grants Workbench the\naccess it needs to your Azure instance. \n \nApplication (client) Secret\n\n(Option 2 only)\n\n|\n\nThe API secret that allows Workbench to authenticate as the created\napplication to your Azure instance. \n \n### Option 1: Enable the ExpelAzure Integration Enterprise Application within\nAzure\n\n 1. As an Administrator, navigate to the Expel Admin Consent Page.\n\n 2. Review and accept requested permissions.\n\n 3. The ExpelAzure Integration app should now appear under Enterprise Applications. Review properties and make sure that all permissions are properly granted. These permissions are:\n\nThis permission...\n\n|\n\nallows this... \n \n---|--- \n \nUser.Read\n\n|\n\nUsers to sign in to the app and allows the app to read the profile of signed-\nin users. It also allows the app to read basic company information of signed-\nin users. \n \nSecurityEvents.Read.All\n\n|\n\nThe app to read your organization’s security events without a signed-in user. \n \nUser.ReadWrite.All\n\n|\n\nThe app to read and update user profiles without assigned in user. \n \nUser.ReadAll\n\n|\n\nThe app to read user profiles without a signed in user. \n \nData.Read\n\n|\n\nThis application to access Log Analytics data. \n \n\nWrite down the Directory (Tenant) ID when viewing the ExpelAzure Integration\napplication for use in later steps.\n\n### Option 2: Create custom Azure AD application\n\n 1. As an Azure administrator, log in to the Azure Portal and open AzureActive Directory.\n\n 2. Navigate to App registrations and create a new app by clicking \\+ New registration.\n\n 3. Fill in the application details. You can fill these in however you want, but we recommend the following:\n\n * Name: Expel Cloud Service.\n\n * Supported account types: Accounts in this organizational directory only (first option).\n\n 4. After you fill out the fields, click Register to create the new application.\n\n 5. The Settings page opens for the Expel Cloud Service app you just created.\n\nIf not, navigate to AzureActive Directory > App Registrations > View all\napplications (if you don’t see the new app) > Expel Cloud Service.\n\n * Make a note of the Application (Client) ID and the Directory (Tenant) ID for use in later steps.\n\n 6. Open API permissions. Click \\+ Add a permission. Add these permissions.\n\nIn APIs my organization uses, locate this permission...\n\n|\n\nselect this value and click + Add permissions. \n \n---|--- \n \ntype Log Analytics and select Log Analytics API > Application Permissions.\n\n|\n\nData.Read \n \ntype Microsoft Graph and select Microsoft Graph > Application Permissions.\n\n|\n\nSecurityEvents.Read.All \n \n 7. Click APIs my organization uses, type Log Analytics and select Log Analytics API > Application Permissions.\n\n 8. After permissions are assigned, click Grant admin consent, and Yes at the prompt.\n\n 9. Navigate to Expel Cloud Service>Certificates & secrets to begin creating an API key (aka client secret). To create a new key, click \\+ New client secret.\n\n * Add a description for the secret (for example, ExpelAPI) and select Never for expiration. Click Add to create the secret.\n\n * You see a new client secret (API Key) appear under Client secrets. Copy the value and ID and save it for later. It disappears after you navigate away from this screen.\n\n## Step 3: Enable Azure Log Analytics access\n\nMicrosoft Sentinel can be run on top of multiple Azure Log Analytics\nworkspaces. These workspaces are used as data stores for the Microsoft\nSentinel service. Querying these Azure Log Analytics workspaces allows Expel\nto enrich Microsoft Sentinel alerts with the Azure Log Analytics context that\noriginally generated that alert.\n\nTo view all Azure Log Analytics workspaces associated with Microsoft Sentinel,\nnavigate to the Microsoft Sentinel blade within the Azure Portal.\n\nThe Azure Log Analytics Reader role must be given to the Azure AD Application\ncreated in Step 2 for each of the Microsoft Sentinel-enabled Azure Log\nAnalytics workspaces to be monitored. Access can be granted in 2 ways or\nthrough some combination.\n\n * Option 1: Per individual Azure Log Analytics workspace.\n\n * Option 2: For all workspaces within an Azure subscription.\n\n### Tip\n\nThe Expel Microsoft Sentinel integration only monitors Microsoft Sentinel\nrunning on top of Log Analytic workspaces that it's allowed to read from. If\nMicrosoft Sentinel is running on top of a Azure Log Analytics workspace that\nare not granted permissions through the following steps, it isn't monitored.\n\n### Option 1: Enable Azure Log Analytics access per workspace\n\nThe following steps outline how to enable Azure Log Analytics Reader role per\na single Azure Log Analytics workspace. These steps must be repeated for each\nmonitored Azure Log Analytics workspace:\n\n 1. As an Azure administrator, log in to the Azure Portal.\n\n 2. In the navigation pane, select Azure Log Analytics workspaces.\n\n 3. Click the name of the workspace whose role assignments you want to change.\n\n 4. Click Access Control (IAM) > \\+ Add > Add role assignment.\n\n 5. In the Add role assignment pane set the following fields:\n\n * Role: Azure Log Analytics Reader.\n\n * Assign access to: Azure Ad user, group or application.\n\n * Select: Search and click the Azure AD App created in Step 2.\n\n 6. Click Save.\n\nRepeat these steps for all workspaces to be monitored.\n\n### Option 2: Enable Azure Log Analytics access per subscription\n\nThe following steps outline how to enable Azure Log Analytics Reader role per\nan Azure Subscription. Repeat these steps for **each** monitored Azure\nSubscription.\n\n 1. As an Azure administrator, log in to the Azure Portal.\n\n 2. In the navigation pane, select Subscriptions.\n\n 3. Click the subscription whose role assignments you want to change.\n\n 4. Click Access Control (IAM) > \\+ Add > Add role assignment.\n\n 5. In the Add role assignment pane set the following fields:\n\n * Role: Azure Log Analytics Reader.\n\n * Assign access to: Azure Ad user, group or application.\n\n * Select: Search and click the Azure AD App created in Step 2.\n\n 6. Click Save.\n\nAll Azure Log Analytics workspaces within this subscription can be monitored.\n\nRepeat these steps for any other subscriptions to be monitored.\n\n## Step 4: Configure Microsoft Sentinel 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=azure_sentinel.\n\n 2. Complete all fields using the credentials and information you collected in Step 2 and Step 3.\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\nMicrosoft Cloud \n \nDirectory (Tenant) ID\n\n|\n\nAzure AD Tenant/Directory ID \n \nApplication (Client) ID\n\n(Option 2 only)\n\n|\n\nThe Azure Application (Client) ID that we saved in Step 2, Option 2. \n \nApplication (Client) Secret\n\n(Option 2 only)\n\n|\n\nThe Client (Application) Secret that we saved in Step 2, Option 2. \n \nWorkspace IDs\n\n(optional)\n\n|\n\nThis optional field accepts a comma-separated list of Azure Log Analytics\nworkspace IDs. By default, the integration monitors any workspaces which have\npermissions assigned in Step 3. This field can be used to define a subset of\nthose workspaces that should be monitored. This can be useful when assigning\npermissions at the Azure subscription level, but you want to only monitor some\nMicrosoft Sentinel workspaces within that subscription.\n\nTo get the Azure Log Analytics workspace ID associated with an Microsoft\nSentinel workspace:\n\n 1. Navigate to the Microsoft Sentinel blade within the Azure Portal.\n\n 2. Click the Microsoft Sentinel workspace.\n\n 3. Click Settings > Workspace Settings and the Workspace ID is listed at the top of the Overview. \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"} \ No newline at end of file diff --git a/article_1500002873042.json b/article_1500002873042.json new file mode 100644 index 0000000000000000000000000000000000000000..066df453e1ab7b2d1d783fbcf3c5dd68db4d2156 --- /dev/null +++ b/article_1500002873042.json @@ -0,0 +1 @@ +{"title": "Deploying the Expel Assembler on Microsoft Azure", "url": "https://support.expel.io/hc/en-us/articles/1500002873042-Deploying-the-Expel-Assembler-on-Microsoft-Azure", "date": "2021-02-17T20:45:03Z", "contents": "This article describes how to deploy the Expel Assembler on Microsoft Azure.\nFor more information on the general Assembler provisioning process, see How to\nprovision Expel Assembler.\n\n### Note\n\nYou may need to do things differently than described here, depending on how\nyour Azure is configured.\n\n#### In this article\n\n * Step 1: Upload the Virtual Hard Disk (VHD) to Azure\n\n * Step 2: Create a virtual machine from the VHD\n\n## Step 1: Upload the Virtual Hard Disk (VHD) to Azure\n\nIf you prefer using the Azure CLI, go to https://docs.microsoft.com/en-\nus/azure/virtual-machines/linux/upload-vhd and follow Option 1 for Upload a\nVHD. Or, follow these steps to upload the VHD through the Azure Portal.\n\n 1. Extract the downloaded .zip file In Windows, right-click on the downloaded file to open the context menu and click Extract All.\n\n 2. Go to https://portal.azure.com/.\n\n 3. Go to Storage Accounts.\n\n 4. Create a new storage account with a Performance of \"standard\" (to create a storage account of kind General Purpose v2) or use an existing General Purpose v2 storage account.\n\n 5. In the storage account you want to use, select Blob Service, then click the \\+ Container button to create a new storage container.\n\n 6. Give the new container a name, and click Create.\n\n 7. In the new container, click the Upload button, and select the extracted VHD file to upload. This is a 30GB file, so it can take a while to upload.\n\n## Step 2: Create a virtual machine from the VHD\n\n 1. Go to Images. It’s not in the default Favorites, so you may have to access it from All Services.\n\n 2. Click Create.\n\n 3. Type the following values:\n\n * Name/Subscription/Resource Group/Location/Zone Resiliency: your choice.\n\n * OS type: Linux.\n\n * VM Generation: Gen 1.\n\n * Storage blob: select the VHD you uploaded.\n\n * Account type: your choice. This is the storage location of the image, not your VM itself, so HDD performance is acceptable.\n\n * Host caching: Read/write.\n\n 4. Click Create.\n\n 5. After the image is created, select the image name, then Create VM.\n\n 6. Type the following values:\n\n * Subscription/Resource Group/Virtual machine name/Region/Availability options: your choice.\n\n * Size: F4s_v2 size or, if you prefer, another size with at least 4 virtual CPUs and 8GB RAM.\n\n * VM disk type: SSD.\n\n * Authentication type: Password.\n\n * Username: temp. This account won’t be used, but Azure makes you create one. We’ll delete it after the VM is running.\n\n * Password: your choice (again, this isn't actually used, so you don't need to remember it).\n\n * Public inbound ports: none.\n\n * License type: Other (the Assembler is CentOS-based, which doesn't require a license).\n\n 7. Click Review + create. If everything looks good, click Create.\n\n 8. Select the Virtual Machine after it is created.\n\n 9. Under Support + Troubleshooting on the left menu, select Serial Console.\n\nGo back to How to provision Expel Assembler and continue with Activate the\nAssembler through the virtual machine console.\n\n"} \ No newline at end of file diff --git a/article_1500004107881.json b/article_1500004107881.json new file mode 100644 index 0000000000000000000000000000000000000000..b21f92b40e3ffff3ce208e5298399ee2a83e9784 --- /dev/null +++ b/article_1500004107881.json @@ -0,0 +1 @@ +{"title": "Box setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500004107881-Box-setup-for-Workbench", "date": "2021-03-17T16:43:41Z", "contents": "This article explains how to connect your Box to Workbench.\n\n#### In this article\n\n * Step 1: Enable API access for Workbench\n\n * Step 2: Configure the technology in Workbench\n\n## Step 1: Enable API access for Workbench\n\nTo integrate the technology with Workbench, we need an enterprise admin on\nhand with access to Developer Console and Admin Console to build and authorize\na Custom App. If you're unsure, reach out to your customer success engineer or\nemail devicehealth@expel.io.\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 in to your Developer Console.\n\n 2. Select Create New App.\n\n 3. Select Server Authentication (Client Credentials Grant).\n\n 4. Name your custom app Expel App and click Create App.\n\n 5. Click Fetch Client Secret and make note of Client ID, and Client Secret, as you only see it 1 time.\n\n 6. Select the app access level as App + Enterprise Access.\n\n 7. Select the following application scopes:\n\n * Read all files and folders stored in Box.\n\n * Manage enterprise properties.\n\n 8. On the Authorization tab, Review and Submit the app for authorization.\n\n 9. The app status now reads Pending Authorization.\n\n 10. Authorize the app through email or sign in to your Admin Console and click Apps from the top left side of the page.\n\n 11. Under Custom Apps, find the app that was submitted and select Authorize App.\n\n 12. Navigate to Account & Billing from the top left side of the page and take note of your Enterprise ID.\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. 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 Box.\n\n![Screen Shot 2021-03-17 at 6.56.18\nPM.png](https://support.expel.io/hc/article_attachments/13874831449107/uuid-27b2d642-b6a8-544d-8ac7-b6484c2503f4.png)\n\n * Complete all fields using the credentials and information you collected in 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"} \ No newline at end of file diff --git a/article_1500004789522.json b/article_1500004789522.json new file mode 100644 index 0000000000000000000000000000000000000000..37b465900fda803d5704a48979d4950cf4e0d737 --- /dev/null +++ b/article_1500004789522.json @@ -0,0 +1 @@ +{"title": "Signal Sciences setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500004789522-Signal-Sciences-setup-for-Workbench", "date": "2021-03-23T21:48:41Z", "contents": "This article explains how to connect Signal Sciences to Workbench.\n\n#### In this article\n\n * Step 1: Enable console access\n\n * Step 2: Enable API access for Expel\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### 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 Corp Manage and click Corp Users.\n\n 2. Click Add User.\n\n 3. Type the email address listed below and select User role and site memberships for Expel to watch.\n\n * Email: soc+@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 * Role: User\n\n 4. Click Invite User.\n\n 5. After the user is invited, notify your engagement manager to expect an email for account activation and password setup.\n\n## Step 2: Enable API access for Expel\n\nTo integrate the technology with Workbench, we need to create secure\ncredentials to the API.\n\n 1. Go to My Profile and select API Access Tokens.\n\n 2. Click Add API access token.\n\n 3. Type Expel API as the name and click Create API access token.\n\n 4. Copy the Token value and save it for later.\n\n 5. Click Continue to finish creating the access token.\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/settings/security-devices?setupIntegration=signal_sciences.\n\n 2. Type the required information as follows:\n\n![Screen Shot 2021-07-16 at 5.32.54\nPM.png](https://support.expel.io/hc/article_attachments/13874989127827/uuid-2cd7456b-eeba-c474-89ae-2003790327e6.png)\n\n * For Name and Location type Signal Sciences and Cloud.\n\n * For Username type the user created in Step 1.\n\n * For API key type the access token generated in Step 2.\n\n * For Server address type the host name of the Signal Sciences dashboard.\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"} \ No newline at end of file diff --git a/article_1500005488942.json b/article_1500005488942.json new file mode 100644 index 0000000000000000000000000000000000000000..ebe566e912c8c041b94794aa8852edf752a8d452 --- /dev/null +++ b/article_1500005488942.json @@ -0,0 +1 @@ +{"title": "Prisma Cloud Compute setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500005488942-Prisma-Cloud-Compute-setup-for-Workbench", "date": "2021-03-30T18:19:33Z", "contents": "This article explains how to connect Prisma Cloud Compute to Workbench.\n\n#### In this article\n\n * Step 1: Add service account\n\n * Step 2: Determine Prisma Cloud Compute console URL\n\n * Self-hosted installation\n\n * SaaS installation\n\n * Step 3: Configure the technology in Workbench\n\n## Step 1: Add service account\n\nService accounts differ from user accounts in that they don't need an email\naddress associated with them and don't need to be validated or activated in an\nexternal system before they can be used. You must have the System\nAdministrator role on Prisma Cloud Compute to add a service account.\n\n### Caution\n\nThink carefully about the information you provide, because after you create a\nservice account, you can't make changes. You must delete it and start over.\n\n 1. Select Settings > Users and then select Add New > Service Account. The Account Details tab appears.\n\n 2. Type these account details:\n\n * Service Account Name: expel_service_account\n\n * Role: System Admin\n\n 3. Click Next. The Access Key Details tab appears.\n\n 4. Type an Access Key Name (your choice).\n\n### Caution\n\nDo **NOT** select Enable Expiration.\n\n 5. Click Save & Create (1 of 2) to generate the key. The Access Key Results screen appears.\n\n 6. Click Download .csv file to download your access key as a .csv file and then store it in a secure location.\n\n### Note\n\nAccess keys are not stored on Prisma Cloud Compute, so this is the only\nopportunity that you have to download it.\n\n 7. To view the new service account, select Settings > Users and type the service account name in the Search field. If there is a problem with the service account, delete it and start over at Step 1.\n\n## Step 2: Determine Prisma Cloud Compute console URL\n\nPrisma Cloud Compute can be either a self-hosted or SaaS installation. The\nPrisma Cloud Compute console URL depends on your specific installation. Use\nthe following sections to determine your Prisma Cloud Compute console URL.\n\n### Self-hosted installation\n\nFor self-hosted environments, the Prisma Cloud Compute API is exposed on port\n8083 (HTTPS). This port is specified at install time in twistlock.cfg.\n\n * For Kubernetes Installations (most common):\n\n * Console service is exposed by a LoadBalancer.\n\n * The console URL is the LoadBalancer followed by port 8083: `https://:8083`\n\n * For Onebox installations:\n\n * Console installed on a standalone host.\n\n * The Console URL is the IP address or DNS name of the host followed by port 8083: `https://:8083`\n\n### SaaS installation\n\n 1. Log into Console.\n\n 2. Go to Manage > System > Utilities.\n\n 3. The console URL is listed under Path to Console at the bottom of the page.\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. Go to https://workbench.expel.io/settings/security-devices?setupIntegration=prisma_cloud_compute.\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/13874847398931/uuid-4506e23f-2077-48ba-0932-53d611c7c099.png)\n\n 2. Do one of the following:\n\n * If you are running a Prisma Cloud Compute SaaS installation, then select Cloud for Where is your device.\n\n * If you are running a Prisma Cloud Compute self-hosted installation, select On-prem and then select Assembler from the list. Select the assembler you set up in Getting connected to Expel Workbench\n\n 3. For Name and Location type Prisma and for Location either Cloud or On-prem.\n\n 4. For Username type the Access Key ID created in Step 1.\n\n 5. For Password type the Secret Access Key created in Step 1.\n\n 6. For Server address type the console URL determined in Step 2.\n\n 7. For Prisma Cloud Compute multi-tenant (only available for on-prem deployments), select Yes or No.\n\n 8. 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"} \ No newline at end of file diff --git a/article_1500005644182.json b/article_1500005644182.json new file mode 100644 index 0000000000000000000000000000000000000000..47e639ef723a1841b0a26750a5dd6d885d31481a --- /dev/null +++ b/article_1500005644182.json @@ -0,0 +1 @@ +{"title": "Dropbox setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500005644182-Dropbox-setup-for-Workbench", "date": "2021-03-31T19:24:59Z", "contents": "This article explains how to connect Dropbox to Workbench.\n\n#### In this article\n\n * Step 1: Enable API access for Workbench\n\n * Step 2: Configure the technology in Workbench\n\n## Step 1: Enable API access for Workbench\n\nTo integrate the technology with Workbench, we need to create secure\ncredentials to the API.\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. Login to https://www.dropbox.com/developers/apps/create.\n\n 2. Select Dropbox API on the first page.\n\n 3. Select Full Dropbox for access type.\n\n 4. Give your app a name in the following format: Expel \\- .\n\n 5. Click Create app.\n\n 6. Go to Permissions tab and grant the token the following permissions:\n\n * Account Info: account_info.read\n\n * Files and folders: account_info.read\n\n * Team Data: team_data.member\n\n * Members: groups.read\n\n * Sessions\n\n * sessions.list\n\n * events.read\n\n 7. Click Submit at the bottom of the page.\n\n 8. Go to the recently created app and find the App Key and App Secret.\n\n 9. Paste the Dropbox OAuth authorize URL (with your App Key filled in) into your browser. You must be logged in for this to work: `https://www.dropbox.com/oauth2/authorize?client_id=&response_type=code&token_access_type=offline`\n\n 10. Click Continue and Allow.\n\n 11. Copy the Access Code provided on the next screen.\n\n 12. Run the request to Dropbox `oauth/token` route with Access Token, App ID. `curl -d \"code=\" -d \"grant_type=authorization_code\" -d \"client_id=\" -d \"client_secret=\" -X POST https://www.dropbox.com/oauth2/token`\n\n 13. Copy the refresh_token from the JSON response value to add to Workbench in step 2. Example response: `{'access_token': '', 'token_type': 'bearer', 'expires_in': 14400, 'refresh_token': , 'scope': 'account_info.read events.read files.metadata.read groups.read sessions.list team_data.governance.read team_data.governance.write team_data.member', 'uid': '', 'team_id': 'team-id'}`\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.\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 Dropbox.\n\n![Screen Shot 2021-04-13 at 2.26.16\nPM.png](https://support.expel.io/hc/article_attachments/13874866828179/uuid-a5205dc1-1ac3-4227-93c9-5648d3d83e6f.png)\n\n * For Name type what you want to name the Dropbox device.\n\n * For Location type Dropbox Cloud.\n\n * API token can be left blank.\n\n * For Refresh Token paste the generated token value from Step 1.\n\n * For Application ID and Application Secret paste the values 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"} \ No newline at end of file diff --git a/article_1500006064802.json b/article_1500006064802.json new file mode 100644 index 0000000000000000000000000000000000000000..3681d936c7f04c1bf5325198cf47f87438f2aaf3 --- /dev/null +++ b/article_1500006064802.json @@ -0,0 +1 @@ +{"title": "Google Workspace (formerly G Suite) setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500006064802-Google-Workspace-formerly-G-Suite-setup-for-Workbench", "date": "2021-04-05T20:43:37Z", "contents": "This document provides prerequisites and Expel Workbench on-boarding steps for\nGoogle Workspace.\n\nItems to be produced\n\n|\n\nDescription \n \n---|--- \n \nAdmin Username\n\n|\n\nThe admin username used to generate the service account. Only Admin accounts\ncan access the Admin SDK reports API, so we need to impersonate the admin user\nthrough our service account. \n \nService Credentials JSON File\n\n|\n\nThe credential file generated for the service account. \n \nAPI Scopes\n\n|\n\nThe permissions granted to the service account. This must be exactly what was\nprovisioned in Google Workspace. \n \n#### In this article\n\n * Step 1: Provision Expel Service Account in Google Workspace\n\n * Step 2: Configure Google Workspace in Workbench\n\n## Step 1: Provision Expel Service Account in Google Workspace\n\n 1. Go to the Google Developers Console and sign in as a super administrator.\n\n 2. Under IAM & Admin, click Manage Resources.\n\n 3. Click Create Project.\n\n 4. Type project details and click Create.\n\nFor this field\n\n|\n\nType this \n \n---|--- \n \nProject name\n\n|\n\nCan be anything you want but we recommend \"ExpelAPI\". \n \nOrganization\n\n|\n\nThe name of your organization. \n \nLocation\n\n|\n\nTypically the name of your organization. You can put it wherever makes the\nmost sense, however. \n \n 5. Each project uses its own set of APIs. For Expel to communicate with Google Workspace APIs, we need to enable the Admin SDK for the newly created project. Navigate to the newly created project.\n\n 6. Search for Admin SDK and open.\n\n 7. Enable the Admin SDK for the new project.\n\n 8. Create a Service Account for Expel Access. Navigate to Menu > IAM & admin > Service accounts.\n\n 9. Click Create Service Account.\n\n 10. Fill in the service account details.\n\nFor this field\n\n|\n\nType this \n \n---|--- \n \nService account name\n\n|\n\nCan be anything but we recommend \"ExpelAPI\". \n \nService account ID\n\n|\n\nCan be anything but we recommend \"ExpelAPI\". \n \nService account description\n\n|\n\nCan be anything but we recommend \"ExpelAPI\". \n \n 11. Click Done.\n\n 12. In the IAM & Admin section, click Service Accounts. For the service account that relates to this integration, click the Actions button and then Manage keys. In the Add Key section, click Create new key. Select JSON and click Create. After you click Create, a JSON file is downloaded.\n\n### Tip\n\nKeep this file in a safe place! It contains the credentials for this service\naccount.\n\n 13. Enable domain-wide delegation for the service account.\n\n * Back on the Service Accounts screen, click Actions and then click Manage Details.\n\n * Select Enable Google Workspace Domain-wide Delegation under Details section.\n\n 14. After the service account is created, in the Details area, copy Unique ID.\n\n 15. Grant the service account the required API permission scope.\n\n * Open the Google Workspace admin console https://admin.google.com/ac/owl/domainwidedelegation\n\n * Navigate to Security > API Controls > Manage Domain Wide Delegation.\n\n * Click Add New.\n\n * Client Name: The Client ID that we saved from our Service Account, in the earlier step.\n\n * API Scopes: You can copy and paste all, which are comma-delimited or add the scopes individually.\n\nhttps://www.googleapis.com/auth/admin.directory.group.readonly,\nhttps://www.googleapis.com/auth/admin.directory.user.readonly,\nhttps://www.googleapis.com/auth/admin.directory.rolemanagement.readonly,\nhttps://www.googleapis.com/auth/admin.directory.orgunit.readonly,\nhttps://www.googleapis.com/auth/admin.reports.audit.readonly,\nhttps://www.googleapis.com/auth/admin.reports.usage.readonly\n\nScope for only retrieving organizational units.\n\n## Step 2: Configure Google Workspace 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 right of the page, click Add Security Device.\n\n 4. Search for and select Google Workspace.\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/6760426035859/uuid-02f73e28-98c2-bae1-0bf8-8df569567ba0.png)\n\n 5. Fill in the following information.\n\n * Select Expel Cloud Service for SIEM.\n\n * Type device Name and Location.\n\n * For Admin username, type the email address of the Super Administrator that created the service account in Step 1.\n\n * For Service Credentials JSON, type the contents of the JSON file for the service account, generated in Step 1.\n\n * For API scopes, type the API Scopes from Step 1.\n\n 6. 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#### Related terms\n\nGSuite, G Suite\n\n"} \ No newline at end of file diff --git a/article_1500007357281.json b/article_1500007357281.json new file mode 100644 index 0000000000000000000000000000000000000000..c78f4222f9c3d285d0363610dedff8ec462afac7 --- /dev/null +++ b/article_1500007357281.json @@ -0,0 +1 @@ +{"title": "SentinelOne setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500007357281-SentinelOne-setup-for-Workbench", "date": "2021-04-15T14:54:23Z", "contents": "This article provides onboarding steps for SentinelOne. Connecting the Expel\nWorkbench to SentinelOne installation requires a user account with the proper\nlevel of access, API access, and an API authentication token. The first step\nis to create a new user account in SentinelOne and configure the account with\nthe proper roles. The next step is to enable API access for the new user\naccount. After that's complete, you can connect SentinelOne to Workbench and\ntest the connection.\n\n#### In this article\n\n * Step 1: Create new user account and role in SentinelOne\n\n * Step 2: Enable API access for Expel\n\n * Step 3: Create an authentication token that allows the Expel Workbench to access the SentinelOne API\n\n * Step 4: Configure SentinelOne in Workbench\n\n## Step 1: Create new user account and role in SentinelOne\n\nThis step creates a user account for Expel that keeps the Expel activity\nseparate from other activity on the SentinelOne 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. Log into SentinelOne, navigate to Settings > Users > Roles. Duplicate the Viewer role.\n\n 2. Rename the new Viewer role: Viewer - Expel.\n\n 3. Add these additional permissions:\n\n * Endpoint: Remote Shell, Initiate Scan, File Fetch, and Fetch Logs.\n\n * Threat: Fetch Threat File.\n\n * Deep Visibility: File Fetch.\n\n 4. Click Save.\n\n 5. Navigate to Settings > Users and click New User.\n\n 6. For Full Name type Expel SOC.\n\n 7. For Email Address type soc+@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 8. Assign the Expel SOC account to the Viewer - Expel role.\n\n 9. Notify your engagement manager that the new account is created and the registration email is sent.\n\n## Step 2: Enable API access for Expel\n\n 1. Navigate to Settings > User and click New User.\n\n 2. For Full Name type Expel API.\n\n 3. For Email Address type soc+_api@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 4. Role Settings: IR Team is the least privileged role that gives Expel the necessary API permissions for polling alerts and disconnecting/isolating hosts.\n\n 5. Click Save.\n\n 6. Navigate to settings on the left side panel and click Users.\n\n 7. Find the Expel User created for API access.\n\n 8. Edit the API user's details and select the checkbox next to Can generate API Token.\n\n 9. Notify your engagement manager that the new account is created and the registration email is sent.\n\n## Step 3: Create an authentication token that allows the Expel Workbench to\naccess the SentinelOne API\n\n 1. Log out of the SentinelOne Console.\n\n 2. Log back into the SentinelOne Console, this time as the newly-created Expel API User.\n\n 3. In the upper right, Expel API > select My User.\n\n 4. From the Option list, select Generate API Token.\n\n 5. Click Download. The generated token is used next in the registration steps for Workbench.\n\n## Step 4: Configure SentinelOne 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.\n\n![Workbench Registration after Step\n5.png](https://support.expel.io/hc/article_attachments/14675940927251/uuid-9c138399-49d6-9c46-56b2-fe1b7af0e1bd.png)\n\n 2. Fill in the fields like this:\n\n * For Name type a name for the security device.\n\n * For Location type cloud.\n\n * For Server address type the SentinelOne device hostname in the following format: `https://.sentinelone.net`. Make sure you include your port number at the end like this example: **https:// .sentinelone.net:40**.\n\n * For API Key type the API key generated in Step 3.5.\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#### Related terms\n\nSentinelOne, Sentinel1, sentinal, sentielone, Sentinel\n\n"} \ No newline at end of file diff --git a/article_1500008391262.json b/article_1500008391262.json new file mode 100644 index 0000000000000000000000000000000000000000..a744170f98bbc00240c618f195cf894a1a75a70e --- /dev/null +++ b/article_1500008391262.json @@ -0,0 +1 @@ +{"title": "Sumo Logic CSE setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500008391262-Sumo-Logic-CSE-setup-for-Workbench", "date": "2021-04-26T18:19:26Z", "contents": "### 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#### 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 in to the Sumo Logic CIP console to create a new user.\n\n 2. Navigate to Administration > Users and Roles > Users and click the Add User button at the top right of the page.\n\n![users_and_roles.png](https://support.expel.io/hc/article_attachments/6760457067667/uuid-b1d28df5-b4ca-4162-a7e4-b7be9cc26eb8.png)\n\n 3. FIll in the below information.\n\n![create_new_user.png](https://support.expel.io/hc/article_attachments/6760441828243/uuid-\nbc0b08df-b25a-de33-7f4d-4f5153b10ec4.png)\n\n * For First Name type Expel.\n\n * For Last Name type SOC analysts.\n\n * For Email type: soc+@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 * For Roles select the analyst role.\n\n * Click Add New User.\n\n 4. Verify that Expel SOC now appears on the Users page.\n\n 5. Sign into Sumo Logic CSE console.\n\n 6. Navigate to Accounts.\n\n![accounts_cse.png](https://support.expel.io/hc/article_attachments/6760419995667/uuid-7b31ba24-4385-c704-a04c-024ab7744214.png)\n\n 7. Click Invite at the top right of the page.\n\n![invite_cse.png](https://support.expel.io/hc/article_attachments/6760453152403/uuid-2a93d9a5-34ed-6ba6-5683-bfdc6adda461.png) \n--- \n \n 8. Invite the Sumo Logic CIP user from step 1 with a role of Analyst.\n\n![invite_users_cse.png](https://support.expel.io/hc/article_attachments/6760441981203/uuid-04cec0d2-ff27-4e7f-5bda-37db56308d7e.png) \n--- \n \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. Edit the Sumo Logic CSE user created in step 1.\n\n 2. Select API Key Enabled.\n\n![api_key_enabled_Cse.png](https://support.expel.io/hc/article_attachments/6760442020627/uuid-\nabb3da10-ec58-9c9e-f450-b9391eba2c93.png)\n\n 3. Select YES, REGENERATE API KEY.\n\n![regenerate_api_key_cse.png](https://support.expel.io/hc/article_attachments/6760489487763/uuid-8c401e35-4da0-0575-184f-392bd61aee7a.png)\n\n 4. Click UPDATE and log out.\n\n 5. Log back into Sumo Logic CSE console with the new user created in step 1.\n\n 6. Click the user profile at the top right of the page.\n\n![profile_cse.png](https://support.expel.io/hc/article_attachments/6760457483539/uuid-a69a87fb-6d73-155d-cebd-3a1fec51128d.png)\n\n 7. Copy API Key and make note of it.\n\n![copy_api_key_cse.png](https://support.expel.io/hc/article_attachments/6760442171795/uuid-8d787c2d-498f-eb3c-e187-c9fd1cc7e1e6.png)\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![Button_WB_add_security_device.png](https://support.expel.io/hc/article_attachments/6886601255699/uuid-9c919067-8376-9d92-c0a3-f21e8ff144a7.png)\n\n 4. Search for and select Sumo Logic Cloud.\n\n 5. Type Name and Location. For example Sumo Logic CSE and Expel Lab.\n\n![sumo_logic_cloud_device_template.png](https://support.expel.io/hc/article_attachments/6760442293907/uuid-\necfb5780-51ee-d1a2-4bcb-a29d65c1d394.png) \n--- \n \n * For Server type the Sumo Logic CSE URL.\n\n * For API Key type the API Key copied and noted during step 2.\n\n * For Console Login type the information for user created in step 1.\n\n * 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"} \ No newline at end of file diff --git a/article_1500008403302.json b/article_1500008403302.json new file mode 100644 index 0000000000000000000000000000000000000000..9d08f3b74b3f6c5b6102afed13ec75145471be13 --- /dev/null +++ b/article_1500008403302.json @@ -0,0 +1 @@ +{"title": "CrowdStrike Falcon Complete setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500008403302-CrowdStrike-Falcon-Complete-setup-for-Workbench", "date": "2021-04-26T20:09:33Z", "contents": "This guide is specific to the CrowdStrike Falcon Complete service. For\nCrowdStrike Falcon, use the CrowdStrike Falcon article instead.\n\n#### In this article\n\n * Before you start\n\n * About console permissions in your devices\n\n * Step 1: Enable console access\n\n * Step 2: Enabling the OAuth2 API\n\n * Step 3: Configure the technology in Workbench\n\n## Before you start\n\n**If you plan to enroll in the Expel Hunting service, your organization\nrequires a Falcon Data Replicator subscription.**\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### 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\nExpel is a CrowdStrike Certified Managed Security Provider partner. To allow\nthe Expel partner console access to your console, do the following:\n\n 1. Print, complete, and sign the CrowdStrike MSP Authorization Form. This form can be provided by the Expel customer success engineer.\n\n 2. Attach the completed form in an email to CrowdStrike Falcon Complete Support. An Expel customer success engineer can help and can provide a template to send to CrowdStrike Falcon Complete Support.\n\nTo integrate the technology with Expel, we need to create secure credentials\nto the API.\n\n## Step 2: Enabling the OAuth2 API\n\nTo enable the OAuth2 API, follow the steps below:\n\n 1. After you log into the Falcon UI, navigate to Support > API Clients and Keys.\n\n 2. If API Clients and Keys doesn't appear in your CrowdStrike Falcon Complete UI, you need to reach out to CrowdStrike Falcon Complete Support to get it enabled for the integration. An Expel customer success engineer can help you with this.\n\n 3. Select Add new API Client.\n\n 4. Type Expel as the Client Name.\n\n 5. Type Expel API Access as the Description.\n\n 6. Select the following permissions. **Bold** is required. The more permissions you allow, the better the SOC analysts can research what's happening and the faster they can respond.\n\nIn this area...\n\n|\n\nthis permission...\n\n|\n\ndoes this...\n\n|\n\nNotes \n \n---|---|---|--- \n \nDetections\n\n|\n\n**Read** and **Write**\n\n|\n\n**Read** : view information about a detection, such as its behavior, severity,\nassociated host, timestamps, and so on.\n\n**Write** : modify metadata about a detection, such as its status, assignee,\nand description.\n\n|\n\nWrite permission is only required to use the Mark in Progress option in\nCrowdStrike. \n \nHosts\n\n|\n\n**Read** and Write\n\n|\n\n**Read** : Search for hosts and get host details, using standard or scrolling\npagination. Details include OS type and version, sensor version, assigned\npolicies, containment status, and more.\n\nWrite: Take action on hosts, including containing or lifting containment on a\nhost.\n\n|\n\nWrite permission for Hosts is required for Auto Host Containment. For more\ninformation, see the CrowdStrike Auto Host Containment article. \n \nIncidents\n\n|\n\n**Read**\n\n|\n\n**Read** : Search and view details on incidents and behaviors.\n\nWrite: Perform actions on incidents, such as adding tags or comments or\nupdating the incident name or description.\n\n|\n\nRead is required to allow Expel to Mark alerts as 'in-progress' when Expel\nprocesses them.\n\nTo select Incidents, you need Falcon Insight XDR enabled. \n \nReal Time Response (RTR)\n\n|\n\nRead and Write\n\n|\n\nRead: Run RTR commands that get information from a host, equivalent to the RTR\nRead OnlyAnalyst role.\n\nWrite: Run RTR commands that send information to a host, equivalent to the RTR\nActive Responder role.\n\n| \n \nIOC Management\n\n|\n\nRead and Write\n\n|\n\nRead: Search your custom IOCs and view hosts that observed your custom IOCs.\n\nWrite: Create, modify, or delete your custom IOCs.\n\n|\n\nWrite permission is required to block hashes through auto-remediation. For\nmore information, see the Auto Block Bad Hashes article. \n \n 7. Click Save.\n\n 8. Make a record of your Client, Client Secret, and Base URL for the API.\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. Login to https://workbench.expel.io/settings/security-devices?setupIntegration=crowdstrike.\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/13874944693779/uuid-9318eb43-cd36-665a-5394-1a0e3bd0f5a8.png)\n\n 2. For Name type the host name of the device.\n\n 3. For Location type the geographic location of the appliance.\n\n 4. After typing the name and location, complete the remaining fields using the credentials and information you collected in Step 2 above.\n\n * API Username and API Key can be left blank.\n\n * Type OAuth2 Client ID from Step 2 in Client ID.\n\n * Type OAuth2 Secret from Step 2 in Client secret.\n\n * Leave Mark in console blank because the API access is read-only.\n\n * Type the Base URL from Step 2 in CrowdStrike API access.\n\n * Enable CrowdScore ingest, type y.\n\n### Note\n\nRequires the incidents:read permission aboveto work.\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"} \ No newline at end of file diff --git a/article_1500008418581.json b/article_1500008418581.json new file mode 100644 index 0000000000000000000000000000000000000000..e96842afa2d586d2878bafbab4faaac0c8660549 --- /dev/null +++ b/article_1500008418581.json @@ -0,0 +1 @@ +{"title": "Protectwise setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500008418581-Protectwise-setup-for-Workbench", "date": "2021-04-26T17:46:46Z", "contents": "This article explains how to connect Protectwise to Workbench.\n\n#### In this article\n\n * Step 1: Enable console access\n\n * Step 2: Enable API access for Expel\n\n * Step 3: Configure Protectwise 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 Expel activity\nseparate from other activity on the Protectwise 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. Settings > User Management > Add User.\n\n 2. For First Name type Expel.\n\n 3. For Last Name type SOC.\n\n 4. For Email type soc+@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 5. Type a Password.\n\n 6. Select Admin as the role.\n\n 7. Click Save.\n\n## Step 2: Enable API access for Expel\n\nThis procedure creates an authentication token that allows access to the\nProtectwise API.\n\nCreate the API token for the ‘soc+@expel.io’ Account\n\n_Reference_ : https://api.protectwise.com/momfodhxhz/getting_started.html\n\n * Make a POST request to _https://api.protectwise.com/api/v1/token_\n\n \n \n { \"email\": \"john.doe@protectwise.com\", \"password\": \"MyPassword!\" } \n\n * You receive a response with your token.\n\n \n \n { \"token\": \"john.doe@protectwise.com@@a45ec285-22d2-48af-b75c-9688f71a9eac\" } \n\nFor example\n\n \n \n curl -H \"Content-Type: application/json\" -d \n '{\"email\":\"john.doe@protectwise.com\",\"password\":\"MyPassword!\"}'\n https://api.protectwise.com/api/v1/token\n\nMake note of the token used next for registration within Workbench.\n\n## Step 3: Configure Protectwise 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, navigate to Settings and click Security Devices.\n\n 3. At the top right of the page, click Add Security Device.\n\n 4. Search for and select Protectwise.\n\n![Screen Shot 2021-05-04 at 12.40.11\nPM.png](https://support.expel.io/hc/article_attachments/13874955097107/uuid-9472355d-1c79-e53f-0931-02bb08ecbaa6.png)\n\n * For Name type the host name of the Protectwise device.\n\n * For Location type the geographic location of the appliance.\n\n * For Token type the generated in step 2.\n\n 5. Click Save.\n\n 6. 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"} \ No newline at end of file diff --git a/article_1500008499562.json b/article_1500008499562.json new file mode 100644 index 0000000000000000000000000000000000000000..32112f5f7a420079b6f59f2990dfed62f252e0d3 --- /dev/null +++ b/article_1500008499562.json @@ -0,0 +1 @@ +{"title": "Phishing submission buttons set up", "url": "https://support.expel.io/hc/en-us/articles/1500008499562-Phishing-submission-buttons-set-up", "date": "2021-04-27T11:44:15Z", "contents": "### Note\n\nIf you're unable to use any of our Phishing email reporting buttons, reach out\nto your engagement manager.\n\n## Phishing Submission buttons\n\nExpel developed buttons for Google Workspace and Microsoft 365 for submitting\nphishing candidates.\n\n## Microsoft 365 Reporting Phishing button\n\nThis process must be completed by one of the organization’s Microsoft 365\nadministrators with the proper permissions.\n\n * Microsoft 365 Report Phishing Button Onboarding Guide\n\n## Google Workspace Report Phishing button\n\nThis process must be completed by one of the organization’s Google Workspace\nadministrators with the proper permissions.\n\n * Google Workspace Report Phishing Button Onboarding Guide\n\n#### Related terms\n\nwhitelist, white list, gsuite, blacklist, black list\n\n"} \ No newline at end of file diff --git a/article_1500008525361.json b/article_1500008525361.json new file mode 100644 index 0000000000000000000000000000000000000000..9187db638db2de01714c28b99962081998bc38e0 --- /dev/null +++ b/article_1500008525361.json @@ -0,0 +1 @@ +{"title": "Expel Managed Phishing set up", "url": "https://support.expel.io/hc/en-us/articles/1500008525361-Expel-Managed-Phishing-set-up", "date": "2021-04-27T11:36:06Z", "contents": "****\n\n## Before you start\n\nReview the customer questionnaire.\n\n## Step 1: Add Expel email communications to your allow list\n\nEstablish trust by adding inbound and outbound emails to your allow list.\n\n * **Outbound** : custom forwarding email (provided by Expel): @expel-phishing.io.\n\n * **Inbound** : acknowledgement and outcome response emails from Expel: soc@expel.io.\n\n## Step 2: Forward phishing submissions\n\nExpel includes phishing submission buttons for Microsoft 365 and Google\nWorkspace for forwarding phishing emails.\n\n### Tip\n\nIf the above button can't be deployed, you can forward your phishing inbox\nsubmissions to Expel with original phishing email **as an EML attachment** to\nthe custom forwarding email destination provided by Expel.\n\nSend a test email submission to Expel using your customer forwarding email\nprovided by Expel. Indicate in that email _“This is a test for the Expel\nManaged Phishing service.”_\n\n"} \ No newline at end of file diff --git a/article_1500008525761.json b/article_1500008525761.json new file mode 100644 index 0000000000000000000000000000000000000000..e87d8e33e984bb925d20f5116127bef43483313e --- /dev/null +++ b/article_1500008525761.json @@ -0,0 +1 @@ +{"title": "Expel Managed Phishing Customer Questionnaire", "url": "https://support.expel.io/hc/en-us/articles/1500008525761-Expel-Managed-Phishing-Customer-Questionnaire", "date": "2021-04-27T11:40:10Z", "contents": "#### General questions\n\nAnswers to the questions in this section are helpful but not required for\ninitial onboarding.\n\n * What email service do you use?\n\n * What email gateway do you use?\n\n * How many email submissions are you getting on average a day? How many on average a day are confirmed malicious?\n\n * What actions do you take today on confirmed phishing emails? For example, delete all sent emails globally, block sender, block malicious urls, hashes, and so on. What vendor tools do you use to take each of these actions?\n\n * Where are your email trace logs stored and are they accessible to Expel?\n\n#### Sending/receiving emails\n\n * What is the email domain(s) we should expect to see phishing submissions coming from?\n\n * Do you need to create allow lists or establish trust anywhere in your environment for forwarded phishing email communications? If yes, the following are the involved addresses:\n\n * **Outbound** : Custom forwarding email (provided by Expel): @expel-phishing.io\n\n * **Inbound** : Acknowledgement and outcome response emails from Expel: soc@expel.io\n\n#### Phishing Submission Buttons\n\n * Expel has add-on buttons for Google Workspace and Microsoft 365 for phishing submissions.\n\n * What is your typical timeline for deployment of this type of add-on?\n\n * Let your Expel engagement manager know you anticipate any significant delays in deploying the button.\n\n### Tip\n\nIf the above button can't be deployed, you can forward your phishing inbox\nsubmissions to Expel with original phishing email **as an EML attachment** to\nthe custom forwarding email destination provided by Expel.\n\n**Expel Email Responses**\n\n * Do you want Expel to send phishing outcome responses sourced from your security team email _(adjustment of ‘from’ header)_?\n\n * If your ‘Alignment Mode’ for DKIM/SPF is set to **relaxed,** (it is by default unless otherwise overridden) Expel generates a set of DKIM/SPF records which you need to add through your DNS provider.\n\n * If your ‘Alignment Mode’ for DKIM/SPF is set to **strict,** we need to have further discussions on how to best accommodate this setup.\n\n * If yes, do you use DKIM/DMARC?\n\n * If yes, how often do you run them? What vendor do you use?\n\n * Do you run phishing simulations?\n\n * Do you have a logo you can provide us for branding our responses back to your submitters?\n\n * If yes, provide to your engagement manager. Preference: 140 pixels wide, .png file.\n\n * What would you like responses to your submitters for the following to be?:\n\n * **Acknowledgement emails** \\- This is when we acknowledge we received the submission.\n\n**Default response:**\n\nHello,\n\nThanks for reporting a suspected phishing attempt. We’ll examine the provided\nemail content and follow up when we’re done. If we find malicious content,\nwe’ll include recommended next steps.\n\nIn the meantime, leave the suspect email alone. Don’t download attachments,\nclick links, or reply to the sender.\n\nThank you,\n\nSecurity Team\n\n**Benign/Safe email outcomes** \\- This is after we've investigated and\nconfirmed the email is safe to interact with.\n\n**Default response:**\n\nHello,\n\nWe've found the email “{subject}” to be a legitimate email which you're free\nto respond to, if needed. We appreciate your vigilance!\n\nThank you,\n\nSecurity Team\n\n**Malicious/Not Safe outcomes** \\- This is after we've investigated and\nconfirmed the email is malicious and not safe to interact with.\n\n**Default response:**\n\nHello,\n\nAfter investigation, we've identified the email “{subject}” as not safe and we\nare working on remediating. Please refrain from interacting with email or\nsender in the meantime. We appreciate your vigilance!\n\nThank you,\n\nSecurity Team\n\n**Simulation emails** \\- This is after we receive a submission resulting from\na phishing simulation exercise.\n\n**Default response:**\n\nHello,\n\nCongratulations! You identified the email “{subject}” as phishing, and it was\nin fact sent as a phishing simulation for training purposes. Continue to stay\nvigilant!\n\nThank you,\n\nSecurity Team\n\nEscalations\n\n * Do you want to be paged during non-business hours if we need additional information from you before determining if an email is malicious?\n\n### Note\n\nThis can result in pages late at night for emails that end up being\nbenign/safe.\n\n"} \ No newline at end of file diff --git a/article_1500008674681.json b/article_1500008674681.json new file mode 100644 index 0000000000000000000000000000000000000000..eb8a84386d3d8155b10e049201ab17e003dc8bf0 --- /dev/null +++ b/article_1500008674681.json @@ -0,0 +1 @@ +{"title": "Microsoft 365 Report Phishing button set up", "url": "https://support.expel.io/hc/en-us/articles/1500008674681-Microsoft-365-Report-Phishing-button-set-up", "date": "2021-04-28T16:25:11Z", "contents": "### Note\n\nThis process must be completed by one of the organization’s Microsoft 365\nadministrators with the proper permissions.\n\n#### Step 1: Deploy add-in using the 365 Admin Center\n\n 1. Navigate to the Microsoft 365 admin center: https://admin.microsoft.com/AdminPortal.\n\n 2. On the left navigation bar near the bottom, expand Settings and click Integrated Apps.\n\n![image-2](https://support.expel.io/hc/article_attachments/6650271320979/uuid-1d9dad2b-2f66-3904-2e38-d4bab0e3a923.png)\n\n 3. In the header, click Add-Ins.\n\n![image-3](https://support.expel.io/hc/article_attachments/6650236394515/uuid-16f1eab9-c18e-9a0b-b1e8-7b46e8a95c8b.png)\n\n 4. In the tab that appears, click Deploy Add-in.\n\n![image-4](https://support.expel.io/hc/article_attachments/6650255663763/uuid-02993d36-c3bd-\neb34-652a-0c6b057dc3ec.png)\n\n 5. Click Next and then click Upload custom apps.\n\n![O365_Submission_Button_Image_5.png](https://support.expel.io/hc/article_attachments/6650227713555/uuid-c5caa6a9-5f4a-7c59-1ffd-\ned9c4952d4fa.png)\n\n 6. Select I have the manifest file (.xml) on this device and click Choose File. Find the manifest file. Select the file and click Upload.\n\n![image-5](https://support.expel.io/hc/article_attachments/6650243246867/uuid-1c223c54-9f0f-f8f0-5d37-98824ed039ef.png)\n\n 7. In the next screen, decide who to deploy this button to in the first section. In the next section, select Fixed (Default). After you’re satisfied with the selections, click Deploy.\n\n![image-6](https://support.expel.io/hc/article_attachments/6650255816595/uuid-7b0354e5-cbbb-\nee9d-41c2-d0616848fcb7.png)\n\nThe deployment can take up to a few minutes. After it's complete, you see a\nsuccess message.\n\n![image-8](https://support.expel.io/hc/article_attachments/6650243344787/uuid-\nab80c13a-e69d-50d8-7aee-87ac267b650f.png)\n\n 8. After completion, you see the Expel Managed Phishing add-in in the list of installed add-ins. Microsoft notes that it can take up to 12 hours for the add-in to propagate to all users but if you reached this point, the installation is complete.\n\n![image-9](https://support.expel.io/hc/article_attachments/6650255917971/uuid-1b2ca6b6-3d1b-4436-ef07-11824b20584f.png)\n\n"} \ No newline at end of file diff --git a/article_1500008693401.json b/article_1500008693401.json new file mode 100644 index 0000000000000000000000000000000000000000..3e991201f18214dc2147796cd5f5762e069cb6c9 --- /dev/null +++ b/article_1500008693401.json @@ -0,0 +1 @@ +{"title": "Add users to Workbench setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500008693401-Add-users-to-Workbench-setup-for-Workbench", "date": "2021-04-28T19:11:32Z", "contents": "You can add users to the Expel Workbench. This is helpful because you may need\nother members of your staff to see the status of your environment or view\nwhat's going on.\n\nBefore you add a user, make sure you know the level of access the user needs:\nOrganization Analyst or Organization Admin. Administrator rights shouldn't be\nassigned to everyone. For example, only Organization Admins can add new users\nand edit or delete user accounts in Workbench.\n\n### Note\n\nFor specific details about what each role can do, see User role rights in\nExpel Workbench.\n\nClick to jump to the task at hand:\n\n * Add user account\n\n * Resend enrollment email\n\n * Edit user account\n\n * Lock/Unlock user account\n\n * Delete user 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## Add user account\n\nTo add a user to your organization, take these steps:\n\n 1. In a new browser tab, login to https://workbench.expel.io.\n\n 2. From any screen, click Organization Settings > Users. The Users list appears.\n\n 3. In the upper right, click \\+ Add User.\n\n 4. The Add User screen appears. Complete the following:\n\n * Email/Username: Must be an email address.\n\n * Organization: select the organization this user should have access to. If you don't have multiple organizations, this list isn't available.\n\n * First name: the user's first name.\n\n * Last name: the user's last name.\n\n * Workbench user role: select Organization Admin or Organization Analyst role for this user.\n\n### Tip\n\nKeep in mind that Organization Admin gives full administrator rights to your\norganization's Workbench.\n\n * Assignable: select if you want this user to be assigned alerts, actions, or investigations. For example, an analyst needs to see these. An admin may not need to see them.\n\n 5. Click Save.\n\n 6. The new user account appears with a Locked status.\n\n### Note\n\nThe account can't be used until it's activated. See Activate your Workbench\naccount for instructions.\n\n 7. After the user account is activated, the Status changes to Active or Assignable.\n\n## Resend enrollment email\n\nTo resend a user enrollment email message, take these steps:\n\n 1. In a new browser tab, login to https://workbench.expel.io.\n\n 2. From any screen, click Organization Settings and then click Users.\n\n 3. On the right side of the screen, click the Down Arrow for the user.\n\n 4. In the menu that appears, select Resend Enrollment Email. A success message appears.\n\n## Edit user account\n\nTo edit user information or settings, take these steps:\n\n 1. In a new browser tab, login to https://workbench.expel.io.\n\n 2. From any screen, click Organization Settings > Users.\n\n 3. On the right side of the screen, click the Down Arrow for the user.\n\n 4. In the menu that appears, select View and edit. User account information appears.\n\n 5. To edit user information and settings, click Edit User. Editing works the same as for Add user account.\n\n### Note\n\nTo edit user notifications, see the User notifications setup for Workbench.\n\n 6. Click Save.\n\n## Lock/Unlock user account\n\nTo lock or unlock a user account, take these steps:\n\n 1. In a new browser tab, login to https://workbench.expel.io.\n\n 2. From any screen, click Organization Settings > Users.\n\n 3. On the right side of the screen, click the Down Arrow for the user.\n\n 4. Click Lock or Unlock. The account status changes accordingly.\n\n### Note\n\nIf the status message says Locked - Re-enrollment sent, it means the account\nmust be reactivated by the user. For instructions, see Activate your Workbench\naccount.\n\n## Delete user account\n\n### Note\n\nThe account is deleted immediately and the user account is no longer listed.\n\nTo delete a user account, take these steps:\n\n 1. In a new browser tab, login to https://workbench.expel.io.\n\n 2. From any screen, click Organization Settings > User.\n\n 3. On the right side of the screen, click the Down Arrow for the user.\n\n 4. Click Delete user.\n\n 5. Click Delete.\n\n"} \ No newline at end of file diff --git a/article_1500008929342.json b/article_1500008929342.json new file mode 100644 index 0000000000000000000000000000000000000000..038b2b29aa72fb9d5a1deef80670fea427119d36 --- /dev/null +++ b/article_1500008929342.json @@ -0,0 +1 @@ +{"title": "ServiceNow integration guide", "url": "https://support.expel.io/hc/en-us/articles/1500008929342-ServiceNow-integration-guide", "date": "2021-04-30T14:39:54Z", "contents": "You can connect Expel Workbench with ServiceNow. After you make the\nconnection,ServiceNow allows 2-way communication with Expel Workbench:\n\n * New tickets in ServiceNow create alerts in Workbench.\n\n * Status updates and other actions in Workbench update or close tickets in ServiceNow.\n\n****\n\n#### In this article\n\n * ServiceNow integration\n\n * Step 1: Configuring ServiceNow API access for Expel\n\n * Step 2: Configuring ServiceNow in Workbench\n\n * Standard workflows\n\n * Workbench can ingest ServiceNow tickets as alerts\n\n * Alert assignment changes in Workbench are reflected in ServiceNow\n\n * Investigation status of alerts is reflected in ServiceNow\n\n * Closing the Workbench alert closes the ServiceNow ticket\n\n * Advanced Workflows\n\n * Remediation or investigative actions assigned to you create tickets in ServiceNow\n\n * Remediation or investigative actions completed in Workbench close tickets in ServiceNow\n\n## ServiceNow integration\n\nTo configure ServiceNow with Workbench, contact your engagement manager, or\nour customer success engineer by tagging @cse in our joint Slack channel. You\ncan also email devicehealth@expel.io.\n\n### Step 1: Configuring ServiceNow API access for Expel\n\nThis procedure creates the user account and OAuth token required by Expel to\ncommunicate with your ServiceNow instance.\n\n 1. Log in to the ServiceNow instance using the administrator account.\n\n 2. Elevate your role to security_admin.\n\n 3. Navigate to User Administration, then Users, and create a new user account for Expel.\n\n 4. Grant the Expel user the incident_manager role. This gives it the required permissions to access the incidents table from the REST APIs.\n\n 5. Go to System OAuth > Application Registry > New.\n\n 6. Click Create an OAuth API endpoint for external clients.\n\n 7. Fill out the form and submit it.\n\n### Step 2: Configuring ServiceNow in Workbench\n\n****\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. Login to https://workbench.expel.io.\n\n 2. Go to Organization Settings > Security Devices.\n\n 3. Click \\+ Add Security Device.\n\n 4. Search for and select ServiceNow.\n\n 5. Complete all fields using the credentials and information you collected in Step 1.\n\n![mceclip1.png](https://support.expel.io/hc/article_attachments/6653763038739/uuid-43eb6aef-05e5-458a-4188-04c349b75c2d.png)\n\n * Name and Location: enter ServiceNow and for location either Cloud or On-prem.\n\n * Server Address: the ServiceNow instance URL. For example: https://dev1234.service-now.com.\n\n * Username and Password: Expel user credentials from Step 1.\n\n * Client ID and Client Secret: OAuth token from Step 1.\n\n * Assignment Group: Optional. You can leave it blank.\n\n * Console Login: Optional. You can leave it blank.\n\n 6. ****\n\nClick Save.\n\n****\n\nTo check if alerts are coming through, navigate to Alerts on the console page.\nClick the icon in the upper right to switch to grid view, then check the list\nfor device alerts.\n\n## Standard workflows\n\nThese workflows are automatically available after the ServiceNow integration\nsteps are complete.\n\n### Workbench can ingest ServiceNow tickets as alerts\n\nWorkbench can ingest alerts from ServiceNow if they are tagged for Expel. To\nenable this workflow, take the following steps.\n\n 1. Create a ServiceNow ticket.\n\n 2. Add the tag [Expel] to the beginning of the Short description.\n\n 3. Enter all required fields.\n\n 4. ****\n\nClick Save.\n\nThis ticket appears in Workbench as an Alert for an Expel analyst to triage\nand investigate.\n\n![image-10](https://support.expel.io/hc/article_attachments/6653758229267/uuid-1874ca51-b51f-e47d-69d1-1ae6524f7cfb.png)\n\n### Alert assignment changes in Workbench are reflected in ServiceNow\n\nWhen the Expel analyst picks up the ticket and assigns it to him or herself,\nthis status change is reflected in the ServiceNow ticket. This allows you to\nsee in ServiceNow that the ticket is being worked by Expel.\n\nIn ServiceNow, you see the Assigned to field of the ticket is now set to\nExpel(expeluser).\n\n### Investigation status of alerts is reflected in ServiceNow\n\nWhen Expel investigates an alert, we move the alert into an investigation (if\nwe need more information to understand what happened) or an incident (if we\nhave high confidence that unauthorized or high-risk activity occurred).\n\nIn ServiceNow, you see the following changes in the ticket:\n\n * The ticket’s state is set to In Progress.\n\n * The Assigned to field is set to Expel to indicate that Expel is actively investigating.\n\n * The ticket’s Work notes are updated with the Workbench investigation or incident name and URL.\n\n### Closing the Workbench alert closes the ServiceNow ticket\n\nAn alert can be closed in 1 of 2 ways in Workbench:\n\n 1. Directly from the Alerts list or grid view.\n\n 2. Indirectly, after an investigation or incident containing that alert is closed.\n\nIn the case where the closed alert started as a ServiceNow ticket, you see the\nfollowing in ServiceNow:\n\n * The original ServiceNow ticket State is set to Resolved.\n\n * The Work notes and Closure notes includes the closed reason category and comment from Workbench.\n\n## Advanced Workflows\n\nThese workflows are not part of the standard set because they require\nadditional setup from Expel which must be done on an individual customer\nbasis. If you want to use one or more of these workflows, contact your\nengagement manager.\n\n### Remediation or investigative actions assigned to you create tickets in\nServiceNow\n\nIn Workbench after a ServiceNow alert is added to an incident or an\ninvestigation, any remediation actions created and assigned to you are\nreflected in ServiceNow as separate tickets.\n\nA ServiceNow ticket for an Investigative action:\n\n * Has a short description identical to an investigation action email notification title, such as “ \\- Investigation Action Assigned - \n\n * Has Assignment Group assigned, set during your ServiceNow Integration Onboarding.\n\n * Contains a link to the investigative action in Workbench.\n\n * Contains in its Work notes instructions and comments to perform the investigation.\n\nA ServiceNow ticket for a Remediation action:\n\n * Has a short description identical to remediation action email notification title, such as “ \\- Remediation Action Assigned - .\n\n * Has Assignment Group assigned, set during your ServiceNow Integration Onboarding.\n\n * Contains a link to the Remediation Action in Workbench.\n\n * Contains in its Work Notes instructions and comments to perform the remediation.\n\n### Remediation or investigative actions completed in Workbench close tickets\nin ServiceNow\n\nThis workflow allows for additional syncing and custom field settings. With\nthis workflow, when investigative, verify, and remediation actions are\ncompleted in Workbench, they are closed in ServiceNow.\n\n****\n\n#### Related terms\n\nService now\n\n"} \ No newline at end of file diff --git a/article_1500009274782.json b/article_1500009274782.json new file mode 100644 index 0000000000000000000000000000000000000000..b6f4277bedebaaaf88607f6d69c99080174376d4 --- /dev/null +++ b/article_1500009274782.json @@ -0,0 +1 @@ +{"title": "QRadar setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500009274782-QRadar-setup-for-Workbench", "date": "2021-05-04T15:29:16Z", "contents": "This article explains how to connect QRadar to Workbench.\n\n#### In this article\n\n * Step 1: Enable console access\n\n * Step 2: Enable API access for Expel\n\n * Step 3: Configure QRadar 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 QRadar 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 Admin > Users. A new window opens.\n\n 2. Click +Add next to the search bar in the new window.\n\n 3. Type a User Name.\n\n 4. Complete User Description as you want.\n\n 5. For E-mail type: soc+@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 6. Under Authentication toggle Local Authentication Fallback on and type a password.\n\n 7. Set the User Role and Security Profile to Admin.\n\n 8. Click Save.\n\n 9. Close the window.\n\n## Step 2: Enable API access for Expel\n\nThis procedure creates an authentication token that allows the Expel Assembler\nto access the QRadar API.\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 Admin > Authorized Services. A new window opens.\n\n 2. Click the Add Authorized Service in the Manage Authorized Services window.\n\n 3. Type **Expel API** as the Service Name.\n\n 4. Make sure the User Role and Security Profile are set to Admin.\n\n 5. Select No Expiry.\n\n 6. Click Create Service.\n\n 7. Make note of the newly generated Authentication Token.\n\n## Step 3: Configure QRadar 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, navigate to Settings and click Security Devices.\n\n 3. At the top right of the page, click Add Security Device.\n\n 4. Search for and select QRadar.\n\n![Screen_Shot_2021-05-04_at_1.40.40_PM.png](https://support.expel.io/hc/article_attachments/6758684716947/uuid-342ada23-12e1-6e87-7cf7-a1d34921b607.png)\n\n * (On-prem) Select the Assembler with a network connectivity to the QRadar device.\n\n * For Name type the hostname of the QRadar device.\n\n * For Location, type the geographic location of the appliance.\n\n * For Server address type the hostname or console IP of device.\n\n * For API key type the Authentication Token created in step 2.\n\n * For Username and Password type the credentials created in step 1.\n\n 5. Click Save.\n\n 6. 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"} \ No newline at end of file diff --git a/article_1500009291541.json b/article_1500009291541.json new file mode 100644 index 0000000000000000000000000000000000000000..92de84ae8a0fd525e639e6cf2ad4d8fc7ac6d0f0 --- /dev/null +++ b/article_1500009291541.json @@ -0,0 +1 @@ +{"title": "DEVO (LogTrust) setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500009291541-DEVO-LogTrust-setup-for-Workbench", "date": "2021-05-04T15:09:46Z", "contents": "This article explains how to connect DEVO to Workbench.\n\n#### In this article\n\n * Step 1: Enable console access\n\n * Step 2: Enable API Access for Expel\n\n * Step 3: Configure DEVO 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 Expel activity\nseparate from other activity on the DEVO 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 > Users > and click ADD USER at the upper right of the page.\n\n 2. For E-mail type: soc+@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 3. For Username type soc@expel.io.\n\n 4. For Role select Administrator.\n\n 5. Click Save.\n\n## Step 2: Enable API Access for Expel\n\nThis procedure creates an authentication token that allows access to the DEVO\nAPI.\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 Administration > Credentials and click CREATE NEW API KEY at the upper right of the page.\n\n 2. Make note of the newly generated API Key and API Secret.\n\n## Step 3: Configure DEVO 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, navigate to Settings and click Security Devices.\n\n 3. At the top right of the page, click Add Security Device.\n\n 4. Search for and select DEVO.\n\n![Screen_Shot_2021-05-04_at_1.54.40_PM.png](https://support.expel.io/hc/article_attachments/13874957255955/uuid-\ndd457359-7019-3d52-16a4-0c26f1edb11d.png)\n\n 5. Type a Name for the DEVO device.\n\n 6. For Location type the geographic location of the appliance.\n\n 7. For Server Address type your DEVO Web URL address (for example, https://apiv2-us.devo.com/).\n\n 8. Type the API Key and API Secret generated in Step 2.\n\n 9. Click Save.\n\n 10. 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"} \ No newline at end of file diff --git a/article_1500009391681.json b/article_1500009391681.json new file mode 100644 index 0000000000000000000000000000000000000000..50af75d66c192bfbd9f0d371151f253f665930dc --- /dev/null +++ b/article_1500009391681.json @@ -0,0 +1 @@ +{"title": "Expel Hunting overview", "url": "https://support.expel.io/hc/en-us/articles/1500009391681-Expel-Hunting-overview", "date": "2021-05-05T17:09:48Z", "contents": "As an extension of your security team, we are focused on understanding the\nrisks to your organization, by leveraging the security signal your investments\ngenerate. Hunting is a way of furthering managing the risks that your\norganization is facing. We extend our focus beyond post-compromise activity to\nproactive monitoring of events/data that aren’t being surfaced by your\nexisting security investments.\n\n#### What is hunting?\n\nIn short, hunting is a proactive effort that applies a hypothesis to discover\nsuspicious activity or areas of risk that may have slipped by your security\ndevices. Rather than solely relying on our customer security devices to detect\nand generate alerts on certain activity, we query customer devices for a bulk\nset of data which we analyze based on our hypothesis and deliver additional\nvalue from our customers security investments.\n\n![image-0](https://support.expel.io/hc/article_attachments/15240943062035/uuid-473bc59a-abe5-67df-173f-4ff9d004213c.png)\n\nWith hunting, we assume that something already failed and you're compromised.\nThe attacker has gotten past the perimeter (inside the network) and we’re\nlooking for them. Because we don’t know where the attacker is hiding or who\nthey’re trying to impersonate, we start with a theory based on common tactics\nattackers use.\n\nWe use the MITRE ATT&CK Framework as our guide to developing new hunting\ntheories. It outlines the tactics and techniques attackers commonly use at\neach stage of the attack lifecycle. Events that match our theory become\ninvestigative leads for an analyst to further review.\n\n#### What’s our process?\n\n![image-1](https://support.expel.io/hc/article_attachments/6649954364563/uuid-5bd21de0-2356-1ab2-d2f4-9f4d1e5202e1.png)\n\n**Step 1:** Expel uses a library of hunting techniques to pick from,\nrepresenting hypotheses to detect risk at various stages of the attack\nlifecycle. engagement managers work with you to select hunting techniques or a\nseries of techniques that work best for you, based on your technology stack\nand available hunts at Expel.\n\n**Step 2** : Our hunting platform (Jager) uses Scavenger to schedule data\ncollection in your environment to fit the hypotheses of the hunts available in\nyour environment. This includes sorting, filtering, calculating, enriching and\ndown-selecting data based on specific logic.\n\n**Step 3** : engagement managers start a hunt for our SOC analysts to run,\nbased on feedback from the customer and the data collected by our hunting\nplatform.\n\n**Step 4:** Jager generates an output of items that meet the hypothesis of the\nhunt and prepares them for analyst review by uploading the results to\nWorkbench.\n\n**Step 5:** The SOC analysts use Jupyter Notebooks to analyze and triage the\npost-processing results from Jager. Jupyter Notebooks include customer\ncontext, tuning suppressions, enrichment, graphs, charts, tables and tools to\nhelp the SOC analysts identify indicators of risk from a bulk set of post-\nprocessing results.\n\n**Step 6:** The SOC analysts tag records which they think you should know\nabout. The tagged records are uploaded to the Workbench Findings report as\nwell as a finding note from the analyst.\n\n**Tags:**\n\n * **Malicious** : events identified as Malicious indicate attacker behavior or indicate serious risk. Malicious findings are generally accompanied by recommended containment and remediation actions or resilience recommendations.\n\n * **Suspicious** : events identified as Suspicious are events which cannot be confirmed. Either they're similar to some system administration type activities or further analysis of the event wasn't available through security tech and OSINT. These events can present risk and need further customer validation to determine if the activity is expected.\n\n * **Notable** : events identified as Notable are likely benign but noteworthy and can present limited risk to you.\n\n"} \ No newline at end of file diff --git a/article_1500009431062.json b/article_1500009431062.json new file mode 100644 index 0000000000000000000000000000000000000000..45d3d590336a4d6865d613394ebb26ce04e578a0 --- /dev/null +++ b/article_1500009431062.json @@ -0,0 +1 @@ +{"title": "Which hunts work with your technology?", "url": "https://support.expel.io/hc/en-us/articles/1500009431062-Which-hunts-work-with-your-technology-", "date": "2021-05-05T19:22:32Z", "contents": "This article shows you which technology works with each hunting technique.\n\n## Endpoint\n\nTechnology /Technique\n\n|\n\nVMware Carbon Black EDR (direct)\n\n|\n\nVMware Carbon Black Cloud Enterprise EDR (direct)\n\n|\n\nCrowdStrike Falcon\n\n(Falcon Data Replicator required)\n\n|\n\nElastic Endpoint Security (direct)\n\n|\n\nSentinelOne\n\n|\n\nMicrosoft Defender for Endpoint \n \n---|---|---|---|---|---|--- \n \n**SIEM**\n\n| | |\n\nSplunk\n\n|\n\nSumo Logic\n\n| | | \n \nAnomalous Process Creation - Database Applications\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | | |\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nAnomalous Process Creation - Productivity Applications\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | | |\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nAnomalous Process Creation - Web Server Applications\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | | |\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nExecution from User Directories\n\n| | |\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | | \n \nHistorical Scripting Interpreter Activity\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | | |\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | \n \nLegitimate Services for Command-and-Control\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | | | | | \n \nScripted Web Downloader\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | | | | | \n \nSuccessive Reconnaissance Commands\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | | | | \n| | | | | | | \n \n## Cloud\n\nTechnology /Technique\n\n|\n\nAmazon Web Services (AWS) (direct)\n\n|\n\nAzure (direct)\n\n|\n\nGoogle Workspace (direct)\n\n|\n\nMicrosoft 365 (direct)\n\n|\n\nOkta (direct)\n\n|\n\nOneLogin (direct) \n \n---|---|---|---|---|---|--- \n \nApp Consent Grants\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | \n \nEC2 Modifications\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | | | | \n \nEC2 Unused or Unsupported Cloud Regions\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | | | | \n \nGeo infeasibility\n\n| | |\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nIAM New User\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | | | | \n \nLogin from Datacenter\n\n| | |\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | | \n \nRDS Modifications\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | | | | \n \nSuspicious Inbox Rules\n\n| | | |\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | \n \n## Network\n\nTechnology /Technique\n\n|\n\nCisco ASA VPN\n\n|\n\nPalo Alto Networks \n \n---|---|--- \n \n**SIEM**\n\n|\n\nIBM QRadar\n\n|\n\nSplunk\n\n|\n\nSumo Logic\n\n|\n\nAzure Log Analytics (ALA)\n\n|\n\nExabeam Fusion SIEM\n\n|\n\nSplunk\n\n|\n\nSumo Logic \n \nConnections to Sinkholed Domains\n\n| | | | | | |\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nGeo infeasibility\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| | | | \n \nHTTP Beaconing\n\n| | | |\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/16716212874899/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n"} \ No newline at end of file diff --git a/article_1500009628381.json b/article_1500009628381.json new file mode 100644 index 0000000000000000000000000000000000000000..d21600f20be04d2e6c3bfc3140b267c61f5dda36 --- /dev/null +++ b/article_1500009628381.json @@ -0,0 +1 @@ +{"title": "Assembler assurance", "url": "https://support.expel.io/hc/en-us/articles/1500009628381-Assembler-assurance", "date": "2021-05-06T16:53:24Z", "contents": "This article covers what the assembler is, how it operates, who has access,\nand how we secure it.\n\n## Purpose\n\nThe assembler serves as a network proxy to allow Expel to access security\ndevices on customer-internal networks. These can be traditional physical on-\nprem networks, or cloud-based networks that function as internal networks.\n\n## Do I need an assembler?\n\nOnly if your security devices are _on-prem_ , either physically, or in a cloud\ninfrastructure logical equivalent. If your security devices are accessible\nthrough the internet, we can access them directly.\n\n## Supported deployment environments\n\n * VMWare\n\n * HyperV\n\n * Azure\n\n * AWS\n\n## System components\n\n * Operating system\n\n * CentOS 7\n\n * Open source components\n\n * Proxying software\n\n * Envoy\n\n * Nginx\n\n * Squid\n\n * Teleport (SSH access management)\n\n## Communications\n\n * The assembler doesn't require any inbound access from the internet. The only outbound connection that the assembler needs is for the VPN on TCP port 443 or 8099 to our VPN server (either one is sufficient). The VPN server domain is servicevpn.opsv2.expel.io.\n\n * The VPN tunnel uses TLS 1.2 with AES-256 encryption.\n\n * All connections from the assembler into the Expel back-end inside the VPN are blocked by the Expel VPN server except teleport.\n\n * Expel initiates all communication with the assembler inside the VPN:\n\n * via HTTPS on port 3128, 8443, and 9500 for proxying to security devices.\n\n * via GRPC on port 8500 for configuration of envoy.\n\n * via Teleport on port 3022 for SSH via Teleport for humans logging in for ad-hoc things.\n\n * via regular SSH on port 22 for Ansible configuration management.\n\n * Communications between the assembler and security tech are dependent on the specifics of each product you have, but generally are outbound from the assembler. The specifics are covered in the onboarding docs for your device.\n\n * Inbound SSH is blocked from the customer network to the assembler. If customer access to the assembler is required, use the console of your virtualization platform.\n\n * The assembler uses DHCP by default. If you prefer, you can use a static IP address.\n\n## Credential management\n\nCredentials for customer devices are never stored on the assembler. The Expel\nbackend provides the credentials with every job that's run on the assembler.\nThis is so that if someone physically walks away with the hypervisor on which\nthe assembler runs, they won't get the creds to your security devices.\n\n## How we build it\n\n * We follow a high-quality, modern software development process for everything that goes on the assembler, just like we do for our backend software.\n\n * We sign all the packages (RPMs) being installed on the assembler.\n\n * Security testing\n\n * Internal\n\n * Lynis\n\n * Regular security and vulnerability scans\n\n * Internal risk assessments and pen tests\n\n * External / third party validation\n\n * External risk assessment and pen test\n\n## How we access it\n\n * Account structure for assembler access\n\n * 1 customer account, can only be accessed from virtualization console (no SSH).\n\n * Expel employees use named accounts. 2FA is required to gain access to log in.\n\n * Proxy access to security tech\n\n * Authenticated Expel employees only, 2FA is required.\n\n * Auditing events on assembler\n\n * All commands issued by Expel analysts on the assembler are audited through teleport. Commands are logged locally on the assembler and logs are exported to central log system.\n\n * All security device access through proxy is logged using proxy infrastructure and includes URL and Expel analyst that initiated the request. Device access is logged locally to the assembler and can be passed to customer's event logging infrastructure upon request (passed as remote syslog).\n\n * Engineers only log into the assembler command line for troubleshooting and onboarding support. No one at Expel SSHs into the Assembler as a routine part of service delivery.\n\n## How we maintain it\n\n * Expel software updates are installed continuously as improvements are made. No customer involvement is needed in this.\n\n * On a quarterly basis, all assemblers are brought up to the latest patch level for all applications and operating system and rebooted.\n\n * If critical patches are required, they are performed on an as needed basis.\n\n * New versions are pushed automatically through Ansible.\n\n * It should never be necessary to reinstall the assembler from scratch. Expel updates are seamless and don't require customer interaction.\n\n## How we harden it\n\nWe use **Lynis** (https://cisofy.com/lynis/), which produces a sort of\nhardening score. Contact us for the annotated results of our most recent run.\n\n## How you can further reduce your risk\n\nUse your network segmentation capabilities (firewalls, and so on) to restrict\nthe assembler to only being able to access the security devices you want us to\naccess, not everything on your corporate network. See How to provision Expel\nAssembler for details.\n\n"} \ No newline at end of file diff --git a/article_1500010736281.json b/article_1500010736281.json new file mode 100644 index 0000000000000000000000000000000000000000..bf1a5fcc85f25728a42f71fa12b719e850fdce40 --- /dev/null +++ b/article_1500010736281.json @@ -0,0 +1 @@ +{"title": "Expel integrations", "url": "https://support.expel.io/hc/en-us/articles/1500010736281-Expel-integrations", "date": "2021-05-13T20:20:36Z", "contents": "Expel has out-of-the-box integrations with many cloud, endpoint, SaaS,\nnetwork, and SIEM technologies. This article lists direct and indirect\nintegrations currently in progress, as well as completed integrations. Those\nnot listed as direct require either sending logs to one of our supported SIEMs\nor network technologies. We also include a list of technologies we can use for\nhunting.\n\nThe integrations available specifically for your organization depend on what\nyour organization purchased. For more information about what your organization\npurchased, talk to the decision makers at your organization.\n\n### Note\n\nNew integrations and features go through a period of Early Access before being\nmade Generally Available. During Early Access, integrations and features are\nexposed to a wide range of customers, and refinements and fixes are made.\n\n**Kubernetes**\n\nVendor technology\n\n|\n\nSecurity signal \n \n---|--- \n \nAmazon Elastic Kubernetes Service (EKS)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Audit\nLogs \n \nGoogle Kubernetes Engine (GKE)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Audit\nLogs \n \n**Cloud Infrastructure**\n\nVendor technology\n\n|\n\nSecurity signal \n \n---|--- \n \nAmazon Web Services (AWS)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)CloudTrail\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Guard\nDuty \n \nMicrosoft Azure\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Defender\nfor Cloud Apps\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Activity\nLog\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Azure\nAD Sign-ins\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Azure\nAD Identity Protect \n \nGoogle Cloud Platform\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Admin\nActivity\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Event\nThread Detection (ETD) \n \nLacework ( _Early Access_ )\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)AWS\nWorkload Events \n \nPrisma Cloud Compute\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Audit\nEvents \n \n**Endpoint**\n\nVendor technology\n\n|\n\nIntegration type\n\nDirect\n\n|\n\nIntegration type\n\nvia SIEM \n \n---|---|--- \n \nCisco AMP\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nCrowdStrike Falcon Elite, Enterprise, and Premium\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nCyberArk PAM\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Splunk \n \nCybereason\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nCylancePROTECT AV\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nEndgame\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nMicrosoft Defender for Endpoint\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nPalo Alto Networks Cortex XDR Pro\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nSentinelOne\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nSymantec Endpoint Protection\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Exabeam\nFusion SIEM\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Splunk\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Sumo\nLogic \n \nTanium Core\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nTrellix HX (formerly FireEye HX)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nVMware Carbon Black EDR\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nVMware Carbon Black Cloud\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nWazuh\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \n**Network integrations**\n\nVendor technology\n\n|\n\nIntegration type\n\nDirect\n\n|\n\nIntegration type\n\nvia SIEM \n \n---|---|--- \n \nAttivo BOTSink\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Splunk\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Sumo\nLogic \n \nCheck Point - AV, Anti-Bot, and IPS ( _Early Access_ )\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Sumo\nLogic \n \nCisco ASA\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Splunk\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Sumo\nLogic \n \nCisco Firepower\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Splunk\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Sumo\nLogic \n \nCisco Meraki\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Splunk\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Sumo\nLogic \n \nCisco Umbrella\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nDarktrace\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nExtraHop Reveal(x) Enterprise ( _Early Access_ ) *360 is not supported*\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nForcepoint W Filter\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Exabeam \n \nFortinet FortiGate\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Microsoft\nSentinel\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Exabeam\nFusion SIEM\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Splunk\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Sumo\nLogic\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Securonix \n \nGuardicore ( _Early Access_ )\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \niBoss ( _Early Access_ )\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Splunk \n \nMcAfee IDS ( _Early Access_ )\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Exabeam\nFusion SIEM \n \nNetskope SWG\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nPalo Alto Firewall\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nPalo Alto Networks Prisma Access\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nProtectWise\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nSignal Sciences WAF\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nZscaler[a]\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Microsoft\nSentinel\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Splunk\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Sumo\nLogic \n \n[a] Requires the Nanolog Streaming Service (NSS), a virtual machine that must\nbe hosted by the customer. Zscaler requires customers to use NSS to transport\ndata from the customer’s Zscaler instance to a SIEM. \n \n**SIEM integrations**\n\nVendor technology\n\n|\n\nType of support[a]\n\nInvestigative source\n\n|\n\nType of support[b]\n\nDetection source \n \n---|---|--- \n \nAzure Log Analytics\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nDatadog\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nDEVO\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nElastic\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nExabeam Fusion XDR\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nExabeam Fusion SIEM\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nIBM QRadar\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nIBM QRadar on Cloud (QRoC)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nMicrosoft Microsoft Sentinel\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nSecuronix ( _Early Access_ )\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nSumo Logic Cloud SIEM Enterprise ( _Early Access_ )\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nSumo Logic Enterprise\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nSplunk Core\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nSplunk Enterprise Security\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nWazuh\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \n[a] Expel can query this SIEM to get more information to support the\ninvestigations of alerts coming from other sources.\n\n[b] This SIEM generates alerts that Expel can use to add detection value. \n \n**UEBA**\n\nVendor technology\n\n|\n\nIntegration type\n\nDirect\n\n|\n\nIntegration type\n\nvia SIEM \n \n---|---|--- \n \nProofpoint Insider Threat Management ( _Early Access_ )\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Sumo\nLogic \n \n**SaaS apps**\n\nVendor technology\n\n|\n\nIntegration type\n\nDirect\n\n|\n\nIntegration type\n\nvia SIEM \n \n---|---|--- \n \n1Password ( _Early Access_ )\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nBox\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nCyberArk Identity ( _Early Access_ )\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nDropbox\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nDuo\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nGitHub\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nGitLab ( _Early Access_ )\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nGoogle Workspace\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nMicrosoft Azure AD\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nMicrosoft Defender for Cloud Apps - formerly MCAS (includes Defender for\nIdentity)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nMicrosoft Intune ( _Early Access_ )\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nMicrosoft 365 (includes Azure AD)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nNetskope CASB\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nOkta\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nOneLogin\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nPing Identity via Exabeam\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nSaaS Security, formerly Prisma SaaS\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nSalesforce ( _Early Access_ )\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nSlack ( _Early Access_ )\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nSnowflake ( _Early Access_ )\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nVaronis\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nWorkday ( _Early Access_ )\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \n**Ticketing and notifications systems**\n\nVendor technology\n\n|\n\nNotifications\n\n|\n\nTicketing system \n \n---|---|--- \n \nAsana\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nJira\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nOpsGenie\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nPagerDuty\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nRequest Tracker for Incident Response\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nSlack\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nServiceNow\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nSplunk On-Call\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nStriven\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png) \n \nTeams\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \n**Hunting**\n\nVendor technology\n\n|\n\nAvailability\n\nYes\n\n|\n\nAvailability\n\nvia SIEM \n \n---|---|--- \n \n**On-prem infrastructure** \n \nCrowdStrike Falcon Elite, Enterprise, and Premium (Falcon Data Replicator\nsubscription required)\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Sumo\nLogic \n \nEndgame\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nMicrosoft Defender for Endpoint\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nPalo Alto Networks (Firewall)\n\n|\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Azure\nLog Analytics (ALA)\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Exabeam\nFusion SIEM\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Splunk\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)Sumo\nLogic \n \nSentinelOne\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nVMware Carbon Black EDR\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nVMware Carbon Black Cloud\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \n**Cloud Infrastructure** \n \nAmazon Web Services (AWS)\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nAzure\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \n**SaaS apps** \n \nDuo\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nGoogle Workspace\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nMicrosoft 365\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nOkta\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n| \n \nOneLogin\n\n|\n\n![WideYesIcon.png](https://support.expel.io/hc/article_attachments/15677369477395/uuid-67261e0b-2f97-7444-4db2-a07e9962b9c2.png)\n\n|\n\n"} \ No newline at end of file diff --git a/article_1500011625301.json b/article_1500011625301.json new file mode 100644 index 0000000000000000000000000000000000000000..503162c39534ac3e112766d2c506c493318c24c0 --- /dev/null +++ b/article_1500011625301.json @@ -0,0 +1 @@ +{"title": "PAN Cortex XDR Pro setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/1500011625301-PAN-Cortex-XDR-Pro-setup-for-Workbench", "date": "2021-05-21T18:01:50Z", "contents": "### Important\n\n**This guide is for XDR Pro only. Expel doesn't support XDR Prevent.**\n\nIntegrating your technology with Expel Workbench requires advanced user\nprivileges that some products don't offer. Palo Alto Networks (PAN) Cortex XDR\nPrevent has limitations on read/write privileges that prevent full\ncommunication with Expel Workbench. So, PAN Cortex XDR Pro is required for\nExpel 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 * Cortex API routes we use\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. Log onto Cortex XDR Pro.\n\n 2. In a new tab, open the Palo Alto Customer Support Portal.\n\n 3. Navigate to Members > Create New User.\n\n 4. Create a new user for the Expel SOC.\n\n * Type a Display Name.\n\n * Type a Password.\n\n * For First Name, type Expel and for Last Name, type **SOC**.\n\n * For Email Address, type soc+@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 5. Expel receives the account activation email and sets a new password.\n\n 6. In the Cortex XDR console navigate to Settings (gear Icon) > Configuration > Access Management > Users.\n\n 7. Confirm that the newly created Expel SOC user is present and edit the user to add the Privileged Security Admin role from the list of predefined roles. https://docs.paloaltonetworks.com/cortex/cortex-xdr/cortex-xdr-pro-admin/get-started-with-cortex-xdr-pro/manage-cortex-xdr-roles/administrative-roles.html\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. In the Cortex XDR Pro console, navigate to Settings > Configurations > Integrations > API Keys.\n\n 2. Click the Copy URL button and save the output, because you need it later.\n\n 3. In the upper right corner, click the New Key button.\n\n 4. In the Generate API Key window, make sure that the Security Level is set as Advanced. Make sure that the role includes all “Investigation” options selected. We recommend Instance Administrator as it selects all of the options that we need to complete investigative action.\n\n 5. Click Generate.\n\n 6. Be sure to copy the generated credentials as you can't access them again.\n\n 7. After it's generated, note your API Key ID.\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 your technology Cortex XDR Pro.\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/13874948069139/uuid-d48aad8e-19cd-1e07-479b-fc0ee154e376.png)\n\n 5. Complete all fields using the credentials and information you collected in Step 1 and Step 2 above.\n\n * For Name type the host name of the device.\n\n * For Location type the geographic location of the appliance.\n\n * For URL type your Cortex XDR Pro URL.\n\n * For API key type the API generated in Step 2.\n\n * For API key ID type the Key ID noted in Step 2.\n\n 6. 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### Cortex API routes we use\n\nRoute\n\n|\n\nPermission \n \n---|--- \n \n/public_api/v1/incidents/get_incidents\n\n|\n\nVIEW PRIVILEGES:Investigation \n \n/public_api/v1/incidents/get_incident_extra_data\n\n|\n\nVIEW PRIVILEGES:Investigation \n \n/public_api/v1/endpoints/get_endpoint\n\n|\n\nVIEW PRIVILEGES:Investigation \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"} \ No newline at end of file diff --git a/article_1500012224381.json b/article_1500012224381.json new file mode 100644 index 0000000000000000000000000000000000000000..34c41cff2e309ba40c612d14382376b5aa3a9951 --- /dev/null +++ b/article_1500012224381.json @@ -0,0 +1 @@ +{"title": "pyexclient documentation", "url": "https://support.expel.io/hc/en-us/articles/1500012224381-pyexclient-documentation", "date": "2021-05-25T19:50:34Z", "contents": "When Expel was founded, we had the goal of making our platform “flypaper for\ninventors.” What this means is that, if you have an idea, you should be able\nto safely test it out on top of our platform using existing technology levers\n(in this case APIs).\n\nThe Expel Workbench is JSON API compliant and uses swagger for API\nspecification/documentation. You can find the Expel swagger doc here.\nPyexclient is the python-ification of the JSON API spec. The pyexclient client\ncode, and much of the documentation, is auto generated from swagger spec file.\n\nClick here to go to the full pyexclient documentation.\n\n"} \ No newline at end of file diff --git a/article_1500012224701.json b/article_1500012224701.json new file mode 100644 index 0000000000000000000000000000000000000000..4373cc4ab6b1e2445ac8589c07956c43f02b4a3c --- /dev/null +++ b/article_1500012224701.json @@ -0,0 +1 @@ +{"title": "Workbench API", "url": "https://support.expel.io/hc/en-us/articles/1500012224701-Workbench-API", "date": "2021-05-25T19:52:16Z", "contents": "The Workbench Public API gives organizations the means to access and\nmanipulate their Expel Workbench data using custom API clients.\n\nWant to extract information into your reporting system? Have some innovative\ndata science idea for analyzing Expel alert evidence? Want to write your own\ncustom browser plugin to make your team's analysts more efficient?\n\nClick here to go to the full API.\n\n"} \ No newline at end of file diff --git a/article_15330742897811.json b/article_15330742897811.json new file mode 100644 index 0000000000000000000000000000000000000000..9e20c18a96db59d265cea582de77f4a7b844e0da --- /dev/null +++ b/article_15330742897811.json @@ -0,0 +1 @@ +{"title": "At the end of your free trial…", "url": "https://support.expel.io/hc/en-us/articles/15330742897811-At-the-end-of-your-free-trial-", "date": "2023-03-30T14:56:43Z", "contents": "Didn’t get to do everything you wanted during the trial? Reach out to your\ntrial guide (the person who emailed and called you with helpful tips during\nyour trial), or ``.\n\n##### What are you doing with my data?\n\nAt the end of your trial, your account is frozen. You still have access to\nExpel Workbench, but we won’t ingest any more data from your connected tech or\nmonitor your environment. After another 14 calendar days, we delete your\naccount and data. **We don’t store or keep your data in any way after the\n14-day frozen period.**\n\n##### Want to learn more about what Expel can offer?\n\nReach out to your trial guide. Or, go to Expel.com to see all the products we\nhave to offer.\n\n##### Want to learn more about Workbench?\n\nFeel free to explore this knowledge base! Here are some specific articles that\nmight interest you:\n\n * Getting started with Workbench\n\n * How To videos\n\n * Expel’s Cloud Detection strategies\n\n##### Want to learn more about Expel?\n\nExplore Expel.com, check out our resources, and see what others have to say\nabout Expel.\n\n"} \ No newline at end of file diff --git a/article_15330788033555.json b/article_15330788033555.json new file mode 100644 index 0000000000000000000000000000000000000000..f031453ee4fe128346c59895db4afe6835bde783 --- /dev/null +++ b/article_15330788033555.json @@ -0,0 +1 @@ +{"title": "Welcome to your 14-day free trial of Expel MDR for Cloud Infrastructure", "url": "https://support.expel.io/hc/en-us/articles/15330788033555-Welcome-to-your-14-day-free-trial-of-Expel-MDR-for-Cloud-Infrastructure", "date": "2023-03-30T14:56:42Z", "contents": "Congratulations! By signing up for a 14-day all-access pass to our security\noperations platform, Expel Workbench™, you’re one step closer to keeping your\ncloud environment secure and giving your team time to focus on what matters\nmost.\n\n### Note\n\nThis guide shows you how to run an incident simulation so you can experience\nthe power of Workbench. While unlikely, if Expel detects a legitimate threat\nin your cloud environment during the free trial, our SOC has you covered!\n\n##### How long is the trial?\n\n14 calendar days—this includes 10 business days and 4 non-workweek days. Your\ntrial ends 14 calendar days from the day you receive the email with\ninstructions on how to set up your account.\n\n##### Need help?\n\nAccess this knowledge base any time by clicking the blue circular icon in the\nbottom right corner of Expel Workbench. The Expel knowledge base widget\nappears after you click the button. Some articles are pinned for easy finding,\notherwise you can search for other keywords.\n\n##### Technical support\n\nOur Technical Support Engineers are here to help! Specific instructions on how\nto submit a technical support ticket are listed here. Technical Support\nEngineers respond to tickets by the end of the next business day.\n\n##### Talk to a human\n\nDuring the trial, you receive emails and calls from a real live person: _your\ntrial guide_. They are available to answer questions and help you easily\nnavigate the trial. Reach out if you need help at any time!\n\n"} \ No newline at end of file diff --git a/article_15330788100627.json b/article_15330788100627.json new file mode 100644 index 0000000000000000000000000000000000000000..8a63db1cd530b423e08cf2a155cd27e8dfa8ec23 --- /dev/null +++ b/article_15330788100627.json @@ -0,0 +1 @@ +{"title": "Before you start…", "url": "https://support.expel.io/hc/en-us/articles/15330788100627-Before-you-start-", "date": "2023-03-30T14:56:42Z", "contents": "There are a handful of free trial milestones, and some have prerequisites.\nHere’s what you need for certain milestones:\n\n##### Step 1: What you need to create a Workbench Account\n\nBe sure you have an MFA ready — you need one to create your account. This can\nbe Duo, Google Authenticator, or some other multi-factor authentication\napplication.\n\n##### Step 2: What you need to connect your cloud to Workbench\n\nDo you own the keys to your AWS, Azure, or GCP castle? You need administrative\nrights to connect your tech to Workbench. Specific permissions and\nrequirements are outlined in our onboarding guides, which are listed here.\n\n##### Step 3: When to invite colleagues to Workbench\n\nIf you _don’t_ own the keys to the castle, we encourage you to invite the\npeople who do own those keys to Workbench. There's no limit to the number of\nusers you can invite during your free trial.\n\n##### Step 4: How to run an incident simulation\n\nAfter your cloud environment is connected to Workbench, it’s time to “see the\nmagic” happen. Expel provides instructions to trigger an alert for each cloud\nenvironment and you can let Workbench do the rest. Keep an eye out for an\nemail from Workbench — it should take 15 minutes.\n\n"} \ No newline at end of file diff --git a/article_15331538042643.json b/article_15331538042643.json new file mode 100644 index 0000000000000000000000000000000000000000..91863437ae0edc3cabb34115f2f8496458d8d45c --- /dev/null +++ b/article_15331538042643.json @@ -0,0 +1 @@ +{"title": "Before you connect your cloud technologies", "url": "https://support.expel.io/hc/en-us/articles/15331538042643-Before-you-connect-your-cloud-technologies", "date": "2023-03-30T15:16:59Z", "contents": "We recommend reviewing the onboarding setup guides. There are several pre-\nrequisite actions that must be taken in your console before you can\nsuccessfully connect your instance to Expel Workbench.\n\n * If you don’t have the appropriate permissions or administrative rights, we encourage you to invite those who do to your free trial. Click Send User Invites in the Welcome to Expel Workbench area to start this process.\n\n * If you get stuck or need help at any point, click Submit a Technical Support ticket in the Welcome to Expel Workbench area. A Technical Support Engineer can help you.\n\n"} \ No newline at end of file diff --git a/article_15331538104467.json b/article_15331538104467.json new file mode 100644 index 0000000000000000000000000000000000000000..fe8444e0a9a695d713b9feb4ab5d3df84f614854 --- /dev/null +++ b/article_15331538104467.json @@ -0,0 +1 @@ +{"title": "Milestone 2: Welcome to Expel Workbench", "url": "https://support.expel.io/hc/en-us/articles/15331538104467-Milestone-2-Welcome-to-Expel-Workbench", "date": "2023-03-30T15:17:00Z", "contents": "Congratulations! You successfully started your Expel Workbench free trial.\nThis screen is your starting point. You can connect an AWS CloudTrail, Azure,\nor Google Cloud Platform instance.\n\nWe want you to experience the power of Expel Workbench. As part of this free\ntrial, we direct you to connect your cloud technology, and include\ninstructions on how to conduct an incident simulation.\n\n![image16.png](https://support.expel.io/hc/article_attachments/15331577567379/uuid-94131fd0-d5ff-9c80-990d-695073799724.png) \n---\n\n"} \ No newline at end of file diff --git a/article_15331538392467.json b/article_15331538392467.json new file mode 100644 index 0000000000000000000000000000000000000000..d0735dbb897e70db6e88a40cabdbe7bab83163e0 --- /dev/null +++ b/article_15331538392467.json @@ -0,0 +1 @@ +{"title": "Azure", "url": "https://support.expel.io/hc/en-us/articles/15331538392467-Azure", "date": "2023-03-30T15:17:03Z", "contents": "Connect your Azure instance manually or through our wizard. Click Set Up to\nstart the onboarding wizard. Click Connect manually >> at the top of the\ndialog box to open the manual entry form.\n\nSpecific onboarding instructions are listed below, and can also be found in\nWorkbench within the onboarding dialog box.\n\n * Azure Cloud (direct) setup for Workbench\n\n![image9.png](https://support.expel.io/hc/article_attachments/15331578198931/uuid-f074f951-0365-2cd6-fb35-65a54467dcaf.png) \n---\n\n"} \ No newline at end of file diff --git a/article_15331538528915.json b/article_15331538528915.json new file mode 100644 index 0000000000000000000000000000000000000000..e7614d790662cdd3bfb9fc6001b5cc69d45e3103 --- /dev/null +++ b/article_15331538528915.json @@ -0,0 +1 @@ +{"title": "Milestone 3: Conduct an incident simulation", "url": "https://support.expel.io/hc/en-us/articles/15331538528915-Milestone-3-Conduct-an-incident-simulation", "date": "2023-03-30T15:17:04Z", "contents": "After you connect your cloud environment to Expel Workbench, the Welcome to\nExpel Workbench area shows a _Healthy connection_ status with a green\ncheckmark.\n\nInstructions for how to trigger a test alert (a less fancy way of saying\n“incident simulation”) also appear in the Welcome to Expel Workbench area.\n\n![image2.png](https://support.expel.io/hc/article_attachments/15331590588435/uuid-9388c08d-9fe4-845d-5076-ee853abff3d9.png) \n--- \n \nClick the linked text next to your cloud environment to see specific\ninstructions on how to trigger a test alert.\n\n * Google Cloud Platform\n\n * AWS CloudTrail\n\n * Azure\n\nExpel Workbench emails you within 15 minutes indicating an Incident report is\nready for review. This is the last step in the incident simulation!\n\nClick the link in the email to open the Findings page in Expel Workbench, with\ndetails what happened and how Expel responded.\n\n![image3.png](https://support.expel.io/hc/article_attachments/15331578789011/uuid-\nadb6a51f-db17-0bbc-a3f9-cbc03d123bf8.png) \n---\n\n"} \ No newline at end of file diff --git a/article_15331538602643.json b/article_15331538602643.json new file mode 100644 index 0000000000000000000000000000000000000000..903e678708ba661acd27aae3119d76812b995e5c --- /dev/null +++ b/article_15331538602643.json @@ -0,0 +1 @@ +{"title": "About triggering alerts in the free trial", "url": "https://support.expel.io/hc/en-us/articles/15331538602643-About-triggering-alerts-in-the-free-trial", "date": "2023-03-30T15:17:05Z", "contents": "After you successfully connect a cloud environment, let’s do something to\ntrigger an alert so you can see what Expel can do for you!\n\nHere's what you do:\n\n 1. You take a simple action in your cloud environment.\n\n 2. You get an email within 10-15 minutes shows you what Expel discovered from your alert.\n\nCreating test alerts for GCP\n\nCreating test alerts for AWS\n\nCreating test alerts for Azure\n\n"} \ No newline at end of file diff --git a/article_15331538679571.json b/article_15331538679571.json new file mode 100644 index 0000000000000000000000000000000000000000..412a0fd042720b0fc86aed57c24ea815d50be2f4 --- /dev/null +++ b/article_15331538679571.json @@ -0,0 +1 @@ +{"title": "Creating test alerts for Azure", "url": "https://support.expel.io/hc/en-us/articles/15331538679571-Creating-test-alerts-for-Azure", "date": "2023-03-30T15:17:06Z", "contents": "Now that you have your device connected, here is a simple way to see Expel in\naction in your environment.\n\n##### Create a new Azure Automation Account with name _expeltestautomation_\n\nWant to see what Expel does after we detect something that we can tell on our\nown is probably malicious?\n\nCreate an Azure Automation Account named _expeltestautomation_ , and we\nproduce an incident as if this were a malicious activity. You don’t have to do\nanything in the automation account.\n\nOf course, there’s nothing inherently malicious in creating an automation\naccount. This is just an easy way to simulate how Expel responds to actual\nmalicious events.\n\nGo ahead and try it out!\n\n 1. Go to the Azure portal.\n\n 2. From the top menu, select \\+ Create a resource.\n\n 3. Under Categories, select IT & Management Tools, and then select Automation.\n\n 4. Click Create.\n\n 5. Select a Subscription and Resource Group.\n\n 6. Type the Automation account name **expeltestautomation**.\n\n 7. Select a Region.\n\n 8. Click Review + Create, then Create.\n\nWithin 10-15 minutes, you get an email from soc@expel.io with the subject\n_Findings ready for review_.\n\n 9. Click the link in that notification to see the kind of findings report we produce!\n\n### Tip\n\nYou can delete the automation account immediately after creating it.\n\n"} \ No newline at end of file diff --git a/article_15331538767635.json b/article_15331538767635.json new file mode 100644 index 0000000000000000000000000000000000000000..8abaf6c2f567301096c031a6fae93ba671262368 --- /dev/null +++ b/article_15331538767635.json @@ -0,0 +1 @@ +{"title": "Creating test alerts for GCP", "url": "https://support.expel.io/hc/en-us/articles/15331538767635-Creating-test-alerts-for-GCP", "date": "2023-03-30T15:17:07Z", "contents": "Now that you have your device connected, here are 2 simple ways to see Expel\nin action in your environment.\n\n##### Create a new project with project ID starting with _expeltestproject_\n\nWant to see what Expel does after we detect something that we can tell on our\nown is probably malicious?\n\nCreate a project whose ID starts with _expeltestproject_ , and we produce an\nincident as if this were a malicious activity. You don’t have to put anything\nin the project.\n\nOf course there’s nothing inherently malicious in creating a GCP project; this\nis just an easy way to simulate how Expel responds to actual malicious events.\n\nGo ahead and try it out!\n\n 1. Go to the GCP Cloud Resource Manager.\n\n 2. Click Create Project.\n\n 3. Give the project an ID that starts with _expeltestproject_. Project names in GCP must be globally unique, so try something like **expeltestproject-x8yf92f** , but vary the characters at the end, as that one’s already used!\n\n 4. Fill in the billing account, organization, and a location that makes sense.\n\n 5. Click Create.\n\nWithin 10-15 minutes, you get an email from soc@expel.io with the subject\n_Findings ready for review_.\n\n 6. Click the link in that notification to see the kind of findings report we produce!\n\n### Tip\n\nYou can shut down the project immediately after creating it.\n\n"} \ No newline at end of file diff --git a/article_15331576323603.json b/article_15331576323603.json new file mode 100644 index 0000000000000000000000000000000000000000..832e14d54f8c021e59c4457e3b75d1ca64dc23a3 --- /dev/null +++ b/article_15331576323603.json @@ -0,0 +1 @@ +{"title": "Milestone 1: Create Account", "url": "https://support.expel.io/hc/en-us/articles/15331576323603-Milestone-1-Create-Account", "date": "2023-03-30T15:16:58Z", "contents": "When you’re given access to the trial, you get an email from ``.\nCheck your spam folder if you don’t see it. The subject line is _Welcome to\nExpel!_ Click the Set Up My Account button to start the process.\n\n### Tip\n\nKeeping our users secure is table stakes for Expel. If you don't create your\naccount within 72 hours of receiving the activation email, your account locks.\nReach out to `` for help.\n\n"} \ No newline at end of file diff --git a/article_15331576564499.json b/article_15331576564499.json new file mode 100644 index 0000000000000000000000000000000000000000..d92ce49d7e4c3bb77bb99817f0d1439affa48096 --- /dev/null +++ b/article_15331576564499.json @@ -0,0 +1 @@ +{"title": "Connect your cloud instance to Expel Workbench", "url": "https://support.expel.io/hc/en-us/articles/15331576564499-Connect-your-cloud-instance-to-Expel-Workbench", "date": "2023-03-30T15:17:01Z", "contents": "If you have the appropriate administrative rights and permissions, you’re\nready to begin connecting your technology.\n\n![image8.png](https://support.expel.io/hc/article_attachments/15331577764499/uuid-949c54d8-dbb3-aff0-2817-49949269033f.png) \n--- \n \n**First,** find and review the relevant onboarding guide for your cloud\ntechnology. You need to make modifications within your console so that\nWorkbench can successfully connect and ingest data from your instance.\n\n"} \ No newline at end of file diff --git a/article_15331576606867.json b/article_15331576606867.json new file mode 100644 index 0000000000000000000000000000000000000000..c763e6d036972f1da95907b7ae59162414abfde7 --- /dev/null +++ b/article_15331576606867.json @@ -0,0 +1 @@ +{"title": "Google Cloud Platform", "url": "https://support.expel.io/hc/en-us/articles/15331576606867-Google-Cloud-Platform", "date": "2023-03-30T15:17:01Z", "contents": "Follow the steps outlined in the setup guide to connect your Google Cloud\nPlatform to Expel Workbench. Click Set Up to open the onboarding dialog box,\nwhich also contains links to the GCP setup guide.\n\n * Google Cloud Platform setup for Workbench\n\n![image5.png](https://support.expel.io/hc/article_attachments/15331539474323/uuid-\nef30cb4a-d676-b0c6-3603-bcfccacaa6a6.png) \n---\n\n"} \ No newline at end of file diff --git a/article_15331576681619.json b/article_15331576681619.json new file mode 100644 index 0000000000000000000000000000000000000000..a9f6caf9ce1a3a677862aedae533956c68007fe7 --- /dev/null +++ b/article_15331576681619.json @@ -0,0 +1 @@ +{"title": "AWS CloudTrail", "url": "https://support.expel.io/hc/en-us/articles/15331576681619-AWS-CloudTrail", "date": "2023-03-30T15:17:02Z", "contents": "Connect your AWS CloudTrail manually or through one of our wizards. The table\noutlines options based on what you need to connect.\n\n### Note\n\nIf you are using Control Tower, you **must** use our specific Control Tower\nguide. Our wizards don’t yet support Control Tower.\n\n##### To use the wizard\n\nClick Set Up next to AWS CloudTrail in the Welcome to Workbench area. The\nwizard opens in a dialog box.\n\n![image6.png](https://support.expel.io/hc/article_attachments/15331539636755/uuid-9977d5bf-c008-d0b1-321f-dac892683ecb.png) \n--- \n \nIf you are connecting manually, click Connect manually >> at the top of the\ndialog box to open the manual entry form. Specific onboarding instructions are\nlisted below, and can also be found in Workbench in the onboarding dialog box.\n\n * AWS CloudTrail — New CloudTrail setup for Workbench\n\n * AWS CloudTrail — Existing CloudTrail setup for Workbench\n\n * AWS CloudTrail — Existing CloudTrail with Control Tower setup for Workbench\n\n"} \ No newline at end of file diff --git a/article_15331576815123.json b/article_15331576815123.json new file mode 100644 index 0000000000000000000000000000000000000000..84f7b91349bfa86b8ba3bf04899c792de435cee6 --- /dev/null +++ b/article_15331576815123.json @@ -0,0 +1 @@ +{"title": "Want help connecting your tech?", "url": "https://support.expel.io/hc/en-us/articles/15331576815123-Want-help-connecting-your-tech-", "date": "2023-03-30T15:17:04Z", "contents": "If you want any help connecting your cloud to Expel Workbench, submit a\nZendesk ticket. Click the link text at the bottom of the Welcome to Expel\nWorkbench area, or click your user icon at the upper right of Expel Workbench\nand select Submit a ticket in Zendesk.\n\n![image12.png](https://support.expel.io/hc/article_attachments/15331540010131/uuid-5d55ff7d-6e5c-388d-2fb9-aaae2ff1fc1e.png) \n--- \n \nFrom the menu, click WB Support Ticket. Within the Subject, include the cloud\ntechnology you need help with. Add the words _Free trial_ for faster\nprioritization.\n\nBe as specific as possible within Request Details (what error did you\nencounter? Is there an error in a guide? And so on). Providing detailed\nscreenshots helps us even more!\n\n![image17.png](https://support.expel.io/hc/article_attachments/15331578416531/uuid-749a713e-1c4e-7eb3-4715-a8ff508bc01b.png) \n---\n\n"} \ No newline at end of file diff --git a/article_15331577270291.json b/article_15331577270291.json new file mode 100644 index 0000000000000000000000000000000000000000..6d7d89a4b68f6fce1f239a88469e131410d61a8c --- /dev/null +++ b/article_15331577270291.json @@ -0,0 +1 @@ +{"title": "Creating test alerts for AWS", "url": "https://support.expel.io/hc/en-us/articles/15331577270291-Creating-test-alerts-for-AWS", "date": "2023-03-30T15:17:08Z", "contents": "Now that you have your device connected, here are 2 simple ways to see Expel\nin action in your environment.\n\n##### Option 1: Create an IAM user with name _expeltestuser_\n\nWant to see what Expel does after we detect something that we can tell on our\nown is probably malicious?\n\nCreate an IAM user with name **expeltestuser** , and we produce an incident as\nif this were a malicious activity. You don’t have to give this user any roles,\npolicies, or credentials.\n\nOf course, there’s nothing inherently malicious in creating an IAM user. This\nis just an easy way to simulate how Expel responds to actual malicious events.\n\nLet's try it out!\n\n 1. Go to your AWS console.\n\n 2. Open the Identity and Access Management (IAM) service.\n\n### Tip\n\nThis is NOT the IAM Identity Center service.\n\n 3. Click Users > Add Users > enter the username expeltestuser.\n\n 4. Verify Provide user access to the AWS Management Console isn't selected. Click Next.\n\n 5. Leave the Permissions options as Add user to group.\n\n 6. Click Next > Create user.\n\nWithin 10-15 minutes, you get an email from soc@expel.io with the subject\n_Findings ready for review_.\n\n 7. Click the link in that notification to see the kind of findings report we produce!\n\n### Tip\n\nYou can immediately delete the user account you created.\n\n##### Option 2: Login by root AWS user account\n\nExpel also lets you know when something unusual has happened, so your security\nteam knows about it and can let us know if it’s expected or not.\n\nIt’s generally not a good practice to log in as the AWS root user account –\nthat is a single, all-powerful account with no built-in individual\naccountability. However, there are some non-routine operations in AWS that\nrequire you to use the root user account.\n\nWe configured your organization to generate an alert when the root account is\nused. We ask you to verify that the usage was authorized, through all the\nnotification mechanisms you've configured. By default, it’s just email. If you\ntell us the usage wasn't authorized, we create an incident and tell you\neverything we can about the situation.\n\nWe don’t alert on root login if your AWS account is less than 3 days old,\nbecause root logins are required during initial AWS account setup. So, if you\ncreated a brand-new test environment for trying out Expel, do Option 1 now,\nand then come back to this AWS root login test after your AWS account passes\nthe 3-day mark.\n\nGo ahead and try it out!\n\n 1. If you’re currently logged into AWS, log out.\n\n 2. Log in to the AWS environment you onboarded with the root user account.\n\nWithin 10-15 minutes, you get an email from soc@expel.io containing subject\n_Verify activity_.\n\n 3. Click the link in that notification to see how you tell us if this is Authorized or Not Authorized.\n\n 4. Click Authorized.\n\nIf this is real attacker activity and you click Not Authorized, our SOC\ncreates an incident and works with you to figure out what happened and what\nmust be done to remediate it.\n\n"} \ No newline at end of file diff --git a/article_15515753745939.json b/article_15515753745939.json new file mode 100644 index 0000000000000000000000000000000000000000..920a812d247599422093b9d4d644b63bf8b83fb0 --- /dev/null +++ b/article_15515753745939.json @@ -0,0 +1 @@ +{"title": "Setting up an email digest", "url": "https://support.expel.io/hc/en-us/articles/15515753745939-Setting-up-an-email-digest", "date": "2023-04-05T20:07:57Z", "contents": "Configure your digest on your profile page. Your configured digest appears\nunder Email Digests.\n\n 1. Click Organization Settings > My Profile.\n\n 2. On the right, click Create New Digest.\n\n![Digest_section.jpg](https://support.expel.io/hc/article_attachments/16562352123539/uuid-d3a114b0-4ddf-3c76-a83c-f0e31b9678b2.jpg)\n\n 3. Select the frequency to receive the digest.\n\n * For example, Daily at 13:00 UTC\n\n * For example, Weekly at 13:00 UTC\n\n![Email_digest_set_freq_result.png](https://support.expel.io/hc/article_attachments/15515804383251/uuid-96672141-5a2d-b597-a6c7-c597df62353e.png)\n\n 4. Click Save.\n\n 5. If you are already receiving a digest, you can edit or delete it by hovering over the container and clicking the pencil icon to edit or the trash icon to delete.\n\n![Digest_Hover_icons.png](https://support.expel.io/hc/article_attachments/16562392945683/uuid-28c81ba5-19ce-99ba-4c3d-5e3c42e0d3f5.png)\n\n"} \ No newline at end of file diff --git a/article_15515796047635.json b/article_15515796047635.json new file mode 100644 index 0000000000000000000000000000000000000000..df019c486f7af9b707af70a8049d8ffbd4a1ca21 --- /dev/null +++ b/article_15515796047635.json @@ -0,0 +1 @@ +{"title": "About the email digest", "url": "https://support.expel.io/hc/en-us/articles/15515796047635-About-the-email-digest", "date": "2023-04-05T20:07:56Z", "contents": "A digest is a scheduled summary of open actions assigned to your organization.\nThis digest is sent to your inbox at the cadence you specify when you create\nit.\n\nA digest provides you a quick and accessible way to see what actions need to\nbe completed by your organization and easily reference them in Workbench.\n\nConfiguring an email digest includes 3 parts:\n\n 1. **Content** : what goes into the email.\n\n 2. **Frequency** : how often you receive the email. Currently, you can only configure the frequency in which the digest is sent to your email.\n\n 3. **Destination** : where the email is sent.\n\nWhen the digest arrives in your inbox, you see an email with the subject:\n_Open actions assigned to your organization_. The email is a list of open\nremediation actions and open investigative actions.\n\nEach section lists the total number of open actions with a link to view them\nin Workbench. Each item includes:\n\n * the name of the open action\n\n * the investigation short link\n\n * a link to the open action in Workbench\n\n"} \ No newline at end of file diff --git a/article_16308546152339.json b/article_16308546152339.json new file mode 100644 index 0000000000000000000000000000000000000000..afc16047e2c0237d54544d54f5254f32a5d0d5cb --- /dev/null +++ b/article_16308546152339.json @@ -0,0 +1 @@ +{"title": "1Password setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/16308546152339-1Password-setup-for-Workbench", "date": "2023-05-03T15:33:02Z", "contents": "This article helps you connect 1Password to Workbench.\n\n#### In this article\n\nBefore you start\n\nStep 1: Create the 1Password token\n\nStep 2: Configure the technology in Workbench\n\nViewing security device details\n\n## Before you start\n\nYou must have admin permissions in 1Password.\n\n## Step 1: Create the 1Password token\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. In 1Password, log into the web dashboard and open the Integrations tab on the right panel.\n\n 2. Locate the Events Reporting tab and click Other.\n\n 3. Name the integration Expel. Set the Expires After field to Never.\n\n 4. In the Events to Report area, select:\n\n * Audit events\n\n * Items usage events\n\n * Sign-in attempts\n\n 5. Click Issue Token. Save the token for later use.\n\n#### Step 2: Configure the technology in Workbench\n\n 1. Log into https://workbench.expel.io/settings/security-devices?setupIntegration=1password. The Add Security device screen for 1Password appears.\n\n![1Pass_AddSecDev.png](https://support.expel.io/hc/article_attachments/16308585775635/uuid-168e9aeb-86ba-f91f-450b-6ef5f846c062.png)\n\n 2. Fill out the fields like this:\n\n * Name: Expel.\n\n * Location: the location of your server.\n\n * API token: the token created in Step 1.\n\n * Server address: select your server URL from the list.\n\n 3. Click Save.\n\n 4. Your device is now connected. To check device health, follow the Viewing security device details instructions below.\n\n## Viewing security device details\n\nAfter your devices are connected to Workbench, you can view details about\nthem. To open the device details, click Organization Settings > Security\nDevices. Locate the device you want more details for. Click the arrow next to\nthe name and click View details.\n\n![WB_View_Details_list.png](https://support.expel.io/hc/article_attachments/16308588693267/uuid-c32a5e42-ade3-0014-fe3a-c33b74fd5db9.png)\n\nThe side panel that appears looks like this:\n\n![WB_Side_panel.png](https://support.expel.io/hc/article_attachments/16308588821523/uuid-c3115552-f098-830e-6e67-62744b526c26.png)\n\nThe side panel contains the following sections:\n\n * **Device Health** : you see an Alerts Analysis dashboard snapshot for the selected device along with the device’s health status, connection, data, and alerts data. This at-a-glance information let's you stay on top of the device and what it's doing.\n\n### Tip\n\nIf you have a AWS CloudTrail device, you also see a Last data received time\nstamp that shows you when we last polled for log data. You also see a Last\nsuccessful poll time stamp. These help you know if your AWS CloudTrail device\nis communicating with Workbench, even if alerts aren't being generated. We're\nworking on deploying the last data received capability to other devices.\n\nIf you have a AWS CloudTrail, you also see View Inaccessible Accounts.\nClicking this button shows you the AWS accounts that are inaccessible to\nWorkbench. This can highlight gaps in service delivery for AWS CloudTrail. To\nprovide access, login to your AWS environment associated with the device and\ngrant permission.\n\n * **Information** : you see general device data, including the device name, location, GUID, and so on. These are the data points associated with creating or editing a device.\n\n * **History** : you see the history of changes in health status or edits made by a Workbench user. You know what changed, who made the change, and when.\n\nIn these sections you can click buttons to copy information or go directly to\nother areas in Workbench. Additionally, we include tool tips to help you\nunderstand what you're seeing.\n\nIn the side panel, you can edit the selected device by clicking Edit Device.\nYou can also navigate to the previous or next device in the list by clicking\nthe arrows.\n\n![WB_Side_panel_Top.png](https://support.expel.io/hc/article_attachments/16308586133651/uuid-703987a8-305d-3dac-0d00-3a788bc1c82a.png)\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"} \ No newline at end of file diff --git a/article_16311310801299.json b/article_16311310801299.json new file mode 100644 index 0000000000000000000000000000000000000000..05850eac767f76302dbbf90bb6aab4cc59f4254c --- /dev/null +++ b/article_16311310801299.json @@ -0,0 +1 @@ +{"title": "Security alerts and threat bulletins", "url": "https://support.expel.io/hc/en-us/articles/16311310801299-Security-alerts-and-threat-bulletins", "date": "2023-05-03T16:46:04Z", "contents": "We have many articles that detail recent threats and what we're doing about\nthem. Make sure you log in to see them.\n\n"} \ No newline at end of file diff --git a/article_16686655699347.json b/article_16686655699347.json new file mode 100644 index 0000000000000000000000000000000000000000..673c1055067a7e83751d043f2dfd65ac2380e36d --- /dev/null +++ b/article_16686655699347.json @@ -0,0 +1 @@ +{"title": "Snowflake setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/16686655699347-Snowflake-setup-for-Workbench", "date": "2023-05-16T16:05:09Z", "contents": "This article explains connecting Snowflake to Workbench.\n\n### Caution\n\nWhen the system runs queries and receives data, it consumes CU (compute units)\nwhich have a monetary value assigned to them. The cost can get high for a\nrobust environment.\n\n#### In this article\n\nBefore you start\n\nStep 1: Enable console access\n\nStep 2: Configure the technology in Workbench\n\nViewing security device details\n\n## Before you start\n\nMake sure you have the following available to you:\n\n * An account with sufficient permissions to perform the tasks detailed in this article. This guide was tested using the default ACCOUNTADMIN role.\n\n * The ability to run SQL queries.\n\n * Access to the openssl and base64 command line tools.\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 in to the Snowflake console and navigate to Admin > Warehouses. Create a new warehouse and name it Expel_warehouse. Click Create Warehouse.\n\n 2. Navigate to Admin > Users&Roles > Roles and create a new role named EXPELROLE. Click Create Role.\n\n 3. In SnowSQL CLI, grant the SECURITY_VIEWER role the the EXPELROLE with the following command:\n\n`GRANT DATABASE ROLE SNOWFLAKE.SECURITY_VIEWER TO ROLE EXPELROLE`\n\nThis command allows Expel to retrieve events from the following views:\n\n * SNOWFLAKE.ACCOUNT_USAGE.LOGIN_HISTORY\n\n * SNOWFLAKE.ACCOUNT_USAGE.GRANTS_TO_ROLES\n\n * SNOWFLAKE.ACCOUNT_USAGE.GRANTS_TO_USERS\n\n 4. Navigate to Admin > Users&Roles > Users and create a new user named EXPEL_INTEGRATION. Set the Default Role to EXPELROLE and the Default Warehouse to EXPEL_WAREHOUSE.\n\n 5. Click Save User.\n\n 6. In the openSSL command line, generate an encrypted RSA private key. You’re prompted to type a passphrase.\n\n`$ openssl genrsa 2048 | openssl pkcs8 -topk8 -v2 des3 -inform PEM -out\nrsa_key.p8`\n\n### Tip\n\nWrite down the passphrase because you need it later in this article.\n\n 7. Generate the corresponding public key using the following command:\n\n`$ openssl rsa -in rsa_key.p8 -pubout -out rsa_key.pub`\n\n 8. In Snowflake, use the following SQL statement to attach the public key from the previous step to the Expel user.\n\n`**ALTER USER** EXPEL_INTEGRATION SET RSA_PUBLIC_KEY='MIIBI...';`\n\nSee the Snowflake documentation for more information.\n\n 9. Navigate to Admin > Warehouses and transfer the ownership of EXPEL_WAREHOUSE to the EXPELROLE.\n\n 10. Determine the account identifier. It usually has the following format: `_orgname-account_name_`. It's typically in the URL you use to log in.\n\nDetailed instructions can be found here.\n\n 11. Encode the private key using the following command:\n\n`cat rsa_key.p8 | base64 > encoded_private_key.txt`\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. Log into https://workbench.expel.io/settings/security-devices?setupIntegration=snowflake. The Add Security Device screen for Snowflake appears.\n\n![Snowflake_AddSecDev.png](https://support.expel.io/hc/article_attachments/16686702745107/uuid-1ed86338-d9d7-e481-e15a-2eee4a52af4e.png)\n\n 2. Fill out the fields like this:\n\n * Name: Expel.\n\n * Location: the location of your server.\n\n * Username: EXPEL_INTEGRATION.\n\n * Account: the account identifier (URL).\n\n * Private key: the encoded private key.\n\n * Passphrase: the passphrase you used while generating the key.\n\n * Warehouse name: EXPEL_WAREHOUSE.\n\n 3. Click Save.\n\n 4. Your device is now connected. To check device health, follow the Viewing security device details instructions below.\n\n## Viewing security device details\n\nAfter your devices are connected to Workbench, you can view details about\nthem. To open the device details, click Organization Settings > Security\nDevices. Locate the device you want more details for. Click the arrow next to\nthe name and click View details.\n\n![WB_View_Details_list.png](https://support.expel.io/hc/article_attachments/16686702854035/uuid-c32a5e42-ade3-0014-fe3a-c33b74fd5db9.png)\n\nThe side panel that appears looks like this:\n\n![WB_Side_panel.png](https://support.expel.io/hc/article_attachments/16686770063123/uuid-c3115552-f098-830e-6e67-62744b526c26.png)\n\nThe side panel contains the following sections:\n\n * **Device Health** : you see an Alerts Analysis dashboard snapshot for the selected device along with the device’s health status, connection, data, and alerts data. This at-a-glance information let's you stay on top of the device and what it's doing.\n\n### Tip\n\nIf you have a AWS CloudTrail device, you also see a Last data received time\nstamp that shows you when we last polled for log data. You also see a Last\nsuccessful poll time stamp. These help you know if your AWS CloudTrail device\nis communicating with Workbench, even if alerts aren't being generated. We're\nworking on deploying the last data received capability to other devices.\n\nIf you have a AWS CloudTrail, you also see View Inaccessible Accounts.\nClicking this button shows you the AWS accounts that are inaccessible to\nWorkbench. This can highlight gaps in service delivery for AWS CloudTrail. To\nprovide access, login to your AWS environment associated with the device and\ngrant permission.\n\n * **Information** : you see general device data, including the device name, location, GUID, and so on. These are the data points associated with creating or editing a device.\n\n * **History** : you see the history of changes in health status or edits made by a Workbench user. You know what changed, who made the change, and when.\n\nIn these sections you can click buttons to copy information or go directly to\nother areas in Workbench. Additionally, we include tool tips to help you\nunderstand what you're seeing.\n\nIn the side panel, you can edit the selected device by clicking Edit Device.\nYou can also navigate to the previous or next device in the list by clicking\nthe arrows.\n\n![WB_Side_panel_Top.png](https://support.expel.io/hc/article_attachments/16686753644307/uuid-703987a8-305d-3dac-0d00-3a788bc1c82a.png)\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"} \ No newline at end of file diff --git a/article_360061332974.json b/article_360061332974.json new file mode 100644 index 0000000000000000000000000000000000000000..cd891d90c30791fbc8f3d4ca9842bf7bc84aff9b --- /dev/null +++ b/article_360061332974.json @@ -0,0 +1 @@ +{"title": "Securonix setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360061332974-Securonix-setup-for-Workbench", "date": "2021-02-17T20:44:46Z", "contents": "This article explains how to connect Securonix 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\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 the Securonix console, create a user for Expel. We recommend naming the user **expel-soc**.\n\n 2. In Menu > Administration > Settings, set Enable Web Services? to Yes. Provide these user credentials to Expel.\n\n## Step 2: Generate API credentials\n\nTo integrate the technology with Workbench, we need to create secure\ncredentials to the API.\n\nAPI credentials are generated by requests to the API itself to create a token\nused for future requests.\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 upper right of the page, select Add New Device.\n\n 4. Search for and select your technology.\n\n 5. Complete all fields using the credentials and information you collected in Step 1 and 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"} \ No newline at end of file diff --git a/article_360061332994.json b/article_360061332994.json new file mode 100644 index 0000000000000000000000000000000000000000..e6a69f5b03fcdddafd36ea1b78d9f09bf06c2780 --- /dev/null +++ b/article_360061332994.json @@ -0,0 +1 @@ +{"title": "Tanium (on-prem) setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360061332994-Tanium-on-prem-setup-for-Workbench", "date": "2021-02-17T20:44:47Z", "contents": "This article explains how to connect Tanium to Workbench.\n\n### Important\n\nThis article is for on-prem Tanium installations only. For Cloud-based Tanium\ninstallations, use the Tanium Cloud article instead.\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\nWhen you create a Tanium user configuration, by default it has no computer\nmanagement groups, alternative personas, user groups, or roles until you\nassign them. A user with no roles can log into the Tanium Console but can't\naccess anything. Don't create configurations for user accounts that you import\nfrom an LDAP server.\nhttps://docs.tanium.com/platform_user/platform_user/console_users.html#Create\n\nhttps://docs.tanium.com/platform_user/platform_user/console_users.html#Assign_roles\n\nWe use the following Tanium API routes for our integration:\n\n**Route**\n\n|\n\n**Permission** \n \n---|--- \n \n/api/v2/session/login\n\n|\n\nInteract:Login \n \n/api/v2/sensors/by-name\n\n|\n\nInteract:Read Sensor \n \n/api/v2/parse_question\n\n|\n\nInteract:Ask Dynamic Questions \n \n/api/v2/questions \n \n/api/v2/result_data/question/ \n \n/plugin/products/detect3/api/v1/alerts\n\n|\n\nThreat Response: Detect Alert Read \n \n/plugin/products/detect3/api/v1/intels\n\n|\n\nThreat Response: Detect Intel Read \n \n/plugin/products/detect3/api/v1/sources\n\n|\n\nThreat Response: Detect Source Read \n \n/plugin/products/detect3/api/v1/intels//labels\n\n|\n\nThreat Response: Detect Label Read \n \nThe **Interact Basic User role** grants us all the necessary permissions we\nneed to access the question/sensor APIs and Interact console.\nhttps://docs.tanium.com/interact/interact/requirements.html#table_Interact_module_\nroles\n\nThe **Threat Response Read Only User role** grants us all the necessary\npermissions we need to access the alerts APIs and Threat Response console.\n\nhttps://docs.tanium.com/threat_response/threat_response/requirements.html#user_roles.\nIf you are using a custom role, we also need **Detect Use API** permission as\nwell as the necessary permissions to make Threat Response available in\nconsole.\n\nThe Tanium client uses a username/password combination to create an\nauthenticated session. The returned session token is set on the session header\nfor all later requests.\n\n 1. From the Main menu, select Administration > Management > Users.\n\n 2. Click New User.\n\n 3. Specify a user name that matches one of the following:\n\n * A user account defined locally on the Tanium Server.\n\n * A user account defined in your IdP.\n\n * (Windows only) An AD account name. Specify just the username, not the domain name. Tanium Server uses Windows Authentication, and doesn't store or manage login credentials for the user.\n\n 4. Save the configuration and get ready to assign roles to a user.\n\n 5. From the Main menu, select Administration > Management > Users.\n\n 6. Click the User Name of the user configuration that you want to edit.\n\n 7. In the Roles and Effective Permissions section, click Manage.\n\n 8. In the Grant Roles section, click Edit, select Interact Basic User and Threat Response Read Only User, and click Save.\n\n 9. Click Show Preview to Continue to review your changes.\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. Login to 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 Tanium.\n\n![Screen Shot 2021-03-08 at 7.57.56\nAM.png](https://support.expel.io/hc/article_attachments/13874932432019/uuid-35f85dd9-3858-60d5-9e86-4ea8e8684756.png)\n\n 5. Complete the fields using the credentials and information you collected in Step 1.\n\n * Name: type the host name of the Tanium device.\n\n * Location: type the geographic location of the appliance.\n\n * Username and Password: type the username and password created in Step 1.\n\n * Server address: type the hostname or IP address of the Tanium device.\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"} \ No newline at end of file diff --git a/article_360061333014.json b/article_360061333014.json new file mode 100644 index 0000000000000000000000000000000000000000..50498506c374e685ba9f1958f770aa54b5e1eaa2 --- /dev/null +++ b/article_360061333014.json @@ -0,0 +1 @@ +{"title": "Configuring your SSO provider with Workbench", "url": "https://support.expel.io/hc/en-us/articles/360061333014-Configuring-your-SSO-provider-with-Workbench", "date": "2021-02-17T20:44:47Z", "contents": "### Tip\n\nWorkbench logins don't support SCIM. We only support SAML and local logins.\n\n 1. In Expel Workbench, navigate to Settings > My Organizations and select the organization. Click Integrations > Configure SSO.\n\n 2. Copy and paste the following from Expel Workbench into your SSO provider:\n\n * ACS URL or Single Sign-on URL: This can be called an Assertion Consumer Service URL or Redirect URL.\n\n * Audience URI or Audience: This can be called SP Entity or SP Entity ID.\n\n * ACS URI Validator: This may not be required, depending on your SSO provider.\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 3. Click Next.\n\n 4. In your SSO provider, set up an email parameter or attribute. The attribute name in Workbench is case sensitive, so make sure the attribute name is email, and not Email. To ensure this, you may need to create a custom attribute. Refer to your SSO provider’s documentation to complete this step.\n\n 5. Click Next.\n\n 6. Copy and paste the appropriate information from your SSO provider into Expel Workbench.\n\n * Single Sign-On URL or SAML 2.0 Endpoint: this can be called the Login URL.\n\n * Issuer or Issuer ID: this can be called Identity Provider Issuer or Entity ID.\n\n * Certificate: this can be copy and pasted or uploaded as an attachment.\n\n 7. Click Save.\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"} \ No newline at end of file diff --git a/article_360061333034.json b/article_360061333034.json new file mode 100644 index 0000000000000000000000000000000000000000..faa0daae3350f86be0bafc7fe188d08813118d7b --- /dev/null +++ b/article_360061333034.json @@ -0,0 +1 @@ +{"title": "Microsoft Defender for Cloud Apps setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360061333034-Microsoft-Defender-for-Cloud-Apps-setup-for-Workbench", "date": "2021-02-17T20:44:47Z", "contents": "This article helps you integrate your Microsoft Defender for Cloud Apps\ninstallation with the Expel Workbench.\n\n#### In this article\n\n * Step 1: Enable console access\n\n * Step 2: Enable Defender for Cloud Apps Enterprise Application\n\n * Option 1: Enable Defender for Cloud Apps integration (preferred)\n\n * Option 2: Create custom Azure AD application\n\n * Step 3: Configure the technology in Workbench\n\n#### Step 1: Enable console access\n\nYou can create either a local account or an AD user through portal.azure.com.\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. Go to admin.microsoft.com to create a new user.\n\n 2. Scroll to Users and click Active Users.\n\n 3. Select Add a user.\n\n 4. Set Expel as first name and SOC as last name.\n\n 5. Scroll to the bottom and grant global reader role for the user.\n\n#### Step 2: Enable Defender for Cloud Apps Enterprise Application\n\nTo integrate Defender for Cloud Apps with Expel, we need to create secure\ncredentials to the API. We provide 2 options for enabling API access:\n\n * Option 1: Enable the **Expel Defender for Cloud Apps Integration** Enterprise Application within Azure.\n\n * Option 2: Create a custom Azure Active Directory (AD) Application.\n\nUsually enabling the Enterprise Application (option 1) is the recommended\napproach. The second option is offered for cases where the absolute minimum\npermissions are required. In either case, the table below shows the required\nitems to obtain during this step:\n\n**Item we need**\n\n|\n\n**Description** \n \n---|--- \n \nAzure Directory (tenant) ID\n\n|\n\nA unique identifier for your Azure instance. Expel needs this information to\nroute our API requests to the right place. \n \nApplication (client) ID (Option 2 only)\n\n|\n\nA unique identifier for the application you create that grants Expel the\naccess it needs to your Defender for Cloud Apps instance. \n \nApplication (client) Secret (Option 2 only)\n\n|\n\nThe API secret that allows Expel to authenticate as the created application to\nyour Defender for Cloud Apps instance. \n \n### Option 1: Enable Defender for Cloud Apps integration (preferred)\n\n 1. As an Administrator, navigate to the Expel Admin Consent Page.\n\n 2. Review and accept requested permissions.\n\n 3. The Expel Defender for Cloud Apps Integration app now appears under Enterprise Applications. Review properties and make sure that all permissions were properly granted. Note the Directory (Tenant) ID when viewing the Expel Defender for Cloud Apps Integration application for use in later steps.\n\n 4. Skip to step 3.\n\n### Option 2: Create custom Azure AD application\n\n 1. Log into your Azure Active Directory account (https://portal.azure.com) and open Azure Active Directory.\n\n 2. Navigate to App registrations and create a new app by clicking \\+ New registration.\n\n 3. Fill in the application details. You can technically fill these in however you want, but we recommend the following:\n\n * Name: Expel Cloud Service.\n\n * Supported account types: accounts in this organizational directory only (first option).\n\n 4. After you fill out the fields, click Register to create the new application.\n\n 5. You navigate 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 Cloud Service.\n\n 6. Make a note of the Application (client) ID and the Directory (tenant) ID. We need that later.\n\n 7. Navigate to API permissions and click Add a permission.\n\n 8. Add these permissions for the Expel App.\n\n * Microsoft Cloud App Security\n\n * discovery.read\n\n * investigation.read\n\n * Microsoft Graph\n\n * User.Read\n\n 9. Select the appropriate API Category (for example, Microsoft Graph).\n\n 10. Select Application Permissions.\n\n 11. Select the appropriate permission(s) and click Add Permissions. (Image is a generic example.)\n\n 12. Repeat these steps for each permission needed. Verify that:\n\n * All permissions are added as Application permissions and NOT Delegated permissions.\n\n * All Permissions are assigned.\n\n * Consent is granted for the permissions by the AAD admin.\n\n 13. After permissions are assigned, click Grant admin consent, and click Yes at the prompt.\n\n 14. Navigate to Expel Cloud Service > Certificates & secrets to begin creating an API key (aka client secret). To create a new key, click +New client secret.\n\n 15. Add a description for the secret (like Expel API) and select Never for expiration. Click Add to create the secret.\n\n 16. You see a new client secret (API Key) appear under Client secrets.\n\n### Important\n\n**Copy the value and save it for later**. It disappears after you navigate\naway from this screen.\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, click this link to open the Add Security Device screen in Workbench.\n\n![MDCA_AddSecDev_Step3_1.png](https://support.expel.io/hc/article_attachments/13874870849043/uuid-12754bd5-c944-01e2-ae16-15486f033aed.png)\n\n 2. Fill out the fields like this:\n\n#### Field Name\n\n|\n\n#### What to put in it \n \n---|--- \n \nName\n\n|\n\nWhat you want to name the security device. \n \nLocation\n\n|\n\nMicrosoft Cloud \n \nTenant ID\n\n|\n\nAzure Directory (tenant) ID from Option 1 or Option 2. \n \nClient ID (Option 2 only)\n\n|\n\nThe Azure Application (client) ID created in Option 2. \n \nClient Secret (Option 2 only)\n\n|\n\nThe Application (client) Secret created in Option 2. \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#### Related terms\n\nMDCA, MCAS, MS Cloud App Security, MS Defender, Microsoft Cloud Application\nSecurity\n\n"} \ No newline at end of file diff --git a/article_360061333054.json b/article_360061333054.json new file mode 100644 index 0000000000000000000000000000000000000000..eac0d340885efe2beac1ea9611cefacd002d5e5f --- /dev/null +++ b/article_360061333054.json @@ -0,0 +1 @@ +{"title": "Sumo Logic setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360061333054-Sumo-Logic-setup-for-Workbench", "date": "2021-02-17T20:44:49Z", "contents": "This article explains how to connect Sumo Logic to Workbench.\n\n#### In this article\n\n * Before you start\n\n * Step 1: Enable console access\n\n * Create a role\n\n * Create a user\n\n * Option 1: Self onboarding\n\n * Option 2: Expel onboarding\n\n * Step 2: Generate API credentials\n\n * Step 3: Change email address\n\n * Step 4: Configure the technology in Workbench\n\n * Step 5: Edit the device to add console access\n\n## Before you start\n\nYou must have the Enterprise account type of Sumo Logic. Other account types\ndon't allow searches using the API, which is key to how Expel uses Sumo Logic.\nIf you don't have the Enterprise account type, contact your Sumo Logic\nrepresentative to upgrade.\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 happening on the Sumo Logic 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### Create a role\n\n 1. Log into the Sumo Logic device.\n\n 2. Navigate to Administration > Users and Roles.\n\n 3. Click the Roles tab and then click the Add Role button at the top right of the page.\n\n 4. Complete the information.\n\n * For Name type Expel.\n\n * For Description type Expel.\n\n * For Capabilities check:\n\n * View Collectors: this gives Expel read-only access to your data.\n\n * Create access keys: this allows this account to create an API key for programmatic access.\n\n 5. Click Save at the top to finish creating the role.\n\n### Create a user\n\nYou have 2 options for creating a new user.\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\nMethod\n\n|\n\nTasks\n\n|\n\nTime frame \n \n---|---|--- \n \nSelf onboard\n\n|\n\n 1. Create a user account that you have access to.\n\n 2. Activate the account and generate API credentials to onboard yourself.\n\n 3. Change registered email address to an Expel email address allowing Expel to manage the account and API management.\n\n|\n\nImmediate \n \nExpel onboard\n\n|\n\n 1. Create an Expel user account.\n\n 2. Expel generates the API credentials.\n\n 3. Expel adds device to Workbench.\n\n|\n\n1 business day \n \n#### Option 1: Self onboarding\n\n 1. Click the Users tab and then click the Add User button at the top right of the page.\n\n 2. Complete the information.\n\n * For First Name type Expel.\n\n * For Last Name type SOC.\n\n * For Email type: youremailaddress@yourcompanyname.com.\n\n * For Roles select the Expel role you created in the previous step.\n\n * Click Add New User.\n\n 3. Log out of Sumo Logic from your personal account.\n\n 4. Go to your email and open the \"Welcome to Sumo Logic!\" email.\n\n 5. Log into https://service.sumologic.com with the username and password from the email.\n\n 6. Set a new password for the account. Make note of this password because you later share it with Expel.\n\n 7. Go to step 2 to generate API credentials.\n\n 8. Go to step 3 to change the registered email address to an Expel email address.\n\n#### Option 2: Expel onboarding\n\n 1. Click the Users tab and then click the Add User button at the top right of the page.\n\n 2. Complete the information.\n\n * For First Name type Expel.\n\n * For Last Name type SOC.\n\n * For Email enter: soc+@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 * For Roles select the Expel role you created in the previous step.\n\n * Click Add New User.\n\n 3. Notify the Expel customer success engineer or your engagement manager that you created the new user account.\n\n * Your Expel team activates the account, generates API credentials, and adds the device to Workbench. You receive a notification that the device is added in Workbench within 1 business day. You can close this article because Expel continues this process for you.\n\n## Step 2: Generate API credentials\n\nThe normal interaction with Sumo Logic is through the API. This step creates\nthe Access Key that allows Expel to use the API.\n\n### Caution\n\nAPI access keys are associated with the user account that creates them.\n\n 1. Make sure you're still logged into Sumo Logic as the new user created in previous step.\n\n 2. Navigate to Expel SOC > Preference and click Add Access Key at the top right of the page.\n\n 3. For Name type Expel API, leave Allowlisted CORS Domains blank, and click Create Key.\n\n 4. Make note of the newly generated Access ID and Access Key which is used for registration in Workbench in step 4.\n\n 5. Click Done.\n\n## Step 3: Change email address\n\nHaving access to the emails from Sumo Logic enables Expel to rotate the\npassword on the account when necessary.\n\n 1. Under My Profile, click Change Email Address.\n\n 2. For Your New Email, type soc+@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 3. Type your current password to authorize the change.\n\n 4. Click Submit.\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. 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 Sumo Logic.\n\n 5. Type Name and Location. For example, Sumo Logic and Expel Lab.\n\n![SumoLogic_AddSecDev.png](https://support.expel.io/hc/article_attachments/11456029454355/uuid-\neb6a03c1-6878-ac11-4c5d-ba27aba63222.png)\n\n * In the Connection Settings area, type the Access ID from step 2 for the Username.\n\n * In the Connection Settings area, type the Access Key from step 2 for the Password.\n\n * For Server address type `https://service.us2.sumologic.com`.\n\n 6. Select the Data tier to run queries against within the Sumo Logic instance.\n\n * Continuous is the preferred data tier and the default selection.\n\n * Frequent is supported by Expel, but isn't recommended.\n\n### Note\n\nIf you need to support multiple data tiers, onboard a device for each tier.\n\n 7. Click Save.\n\n 8. 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"} \ No newline at end of file diff --git a/article_360061333134.json b/article_360061333134.json new file mode 100644 index 0000000000000000000000000000000000000000..78dc4a90e7a5edf5460139aee91501a5d64ef613 --- /dev/null +++ b/article_360061333134.json @@ -0,0 +1 @@ +{"title": "Cisco Umbrella setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360061333134-Cisco-Umbrella-setup-for-Workbench", "date": "2021-02-17T20:44:56Z", "contents": "This article explains how to connect Cisco Umbrella 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\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 > Accounts and click Add.\n\n 2. Add user’s email address soc+@expel.io and select Read Only User Role for the account.\n\n 3. Click Send Invitation. Expel completes account registration after the registration email is received.\n\n## Step 2: Generate API credentials\n\n 1. Use your admin account to create an API Key. This can be found under Admin > API Keys.\n\n 2. At the prompt, set an API Key Name, select the appropriate Key Scope(s), and set the Expiry Date.\n\n * For the API Key Name, set to your organization's preference or something like Reports Key.\n\n * For the Key Scope, select the following depending on the type of tenant you have: \n\n 1. Reports > Read-All: all customers must select this.\n\n 2. Admin > Customers: only if you have a Multi-Organization Umbrella console.\n\n * For the Expiry Date, set to Never expire. \n\n 3. Copy both the Key and the Secret provided.\n\nUse these to configure your technology in Workbench 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. Login to 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 your technology.\n\n 5. Complete all fields using the credentials and information you collected in Step 1 and Step 2. To complete the Console login, see the steps below.\n\n![WB_Cisco_Umbrella_Add_Device.png](https://support.expel.io/hc/article_attachments/13874953957395/uuid-\ndde3571a-e946-5523-3be9-a2de172b1df6.png)\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"} \ No newline at end of file diff --git a/article_360061333154.json b/article_360061333154.json new file mode 100644 index 0000000000000000000000000000000000000000..4f12240446f8a29a318d732ac60ebb234bf8819c --- /dev/null +++ b/article_360061333154.json @@ -0,0 +1 @@ +{"title": "AWS CloudTrail: New CloudTrail setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360061333154-AWS-CloudTrail-New-CloudTrail-setup-for-Workbench", "date": "2021-02-17T20:44:56Z", "contents": "This article describes how to connect your new AWS CloudTrail to the Expel\nWorkbench.\n\nIf you're...\n\n|\n\nuse this...\n\n|\n\nNotes \n \n---|---|--- \n \nsetting up new AWS CloudTrails\n\n|\n\nthis article\n\n|\n\nTo set up your device, you need:\n\n * Permissions to create and modify IAM policies and roles in each AWS account you want Expel to monitor.\n\n * An AWS Management Account ID or individual AWS Account ID(s) for each account you're going to onboard.\n\n * The AWS region in which you want to create an SQS queue to notify Expel of available CloudTrail data.\n\n \n \nconnecting an existing CloudTrail\n\n|\n\nthe existing installation steps\n\n| \n \nconnecting an existing CloudTrail that includes Control Tower\n\n|\n\nthe Control Tower connection steps\n\n| \n \n#### In this article\n\n * About connecting your device\n\n * Before you start\n\n * Server Side Encryption with AWS-KMS\n\n * About console permissions in your devices\n\n * Step 1: Configure a global CloudTrail\n\n * Step 2: Enable SSE-KMS encryption in the log S3 bucket\n\n * Step 3: Create an SQS queue to receive S3 notifications\n\n * Step 4: Add key policies\n\n * Step 5: Configure S3 notifications\n\n * Step 6: Create AWSIAM policy\n\n * Permissions description and explanation\n\n * Step 7: Create role\n\n * Step 8: Register AWS in Workbench\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### Server Side Encryption with AWS-KMS\n\nAWS KMS (key management services) allows you to manage cryptographic keys to\nencrypt/decrypt data at-rest. Many AWS services offer server side encryption\n(SSE) where the service is responsible for encrypting/decrypting the data on a\nprincipal’s (user/service) behalf.\n\nWe are encrypting all the data at rest (CloudTrail logs, CloudTrail log bucket\nand SQS queue messages) using a custom managed AWS key. All the required\npermissions for the AWS services to encrypt/decrypt data are specified in the\nkey policies. Additionally, the custom role that this integration assumes to\nmonitor your AWS account is attached with a policy to decrypt the CloudTrail\nlog S3 bucket using this key.\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: Configure a global CloudTrail\n\n 1. Log in to the AWS console. If you have multiple AWS accounts and use AWS Organizations, log into your primary account.\n\n 2. Ensure you are in the region you want to be the Home region for the new CloudTrail. The CloudTrail collects data from all regions, but it is stored in S3 in a specific region. You need to supply this region to Expel Workbench later in this process.\n\n 3. Navigate to the CloudTrail service and create a new trail.\n\n 4. Select trail attributes.\n\n### Important\n\nIf you select an existing S3 bucket or KMS key, the integration doesn't work.\nContact your engagement manager for help.\n\n * Name Trail: we recommend GlobalCloudTrail.\n\n * Select Create new S3 bucket and name bucket.\n\n * When creating a new trail, make sure that Enable for all accounts in my organization is selected if you are using AWS Organizations.\n\n * Enable Log file SSE-KMS encryption. Select New and type a KMS alias.\n\n * Enable Log file validation.\n\n * (Optional) If you are using SNS, select SNS Topic.\n\n 5. Leave the CloudWatch Logs and Tags sections blank and click Next.\n\n 6. Select log events.\n\n * Events: only select Management events. Leave the rest cleared.\n\n * Management events: select Read and Write. Leave Exclude AWS KMS events clear.\n\n * Click Next.\n\n 7. Verify Trail attributes and click Create Trail.\n\n## Step 2: Enable SSE-KMS encryption in the log S3 bucket\n\nTo enable Server Side Encryption (SSE) in the Trail log bucket, you must edit\nthe configuration of the trail log bucket.\n\n 1. Navigate to S3 and select the S3 trail log bucket created in Step 1. Select the Properties tab and Edit the Default Encryption section.\n\n 2. Edit the Default Encryption as follows:\n\n * Enable Server Side Encryption.\n\n * For Key Type, select AWS Key Management Service key (SSE-KMS).\n\n * For AWS KMS key, select Choose from your AWS KMS keys.\n\n * Type the key alias given in Step 1 and select it.\n\n * (Optional) Enable Bucket Key.\n\n * Note the Bucket ARN.\n\n 3. Click Save changes.\n\n## Step 3: Create an SQS queue to receive S3 notifications\n\nTo consume CloudTrail events from the trail’s S3 bucket, Workbench must be\nnotified when new event files are added to the S3 bucket. In this step, we\ncreate an SQS queue for these notifications.\n\n### Note\n\nThe SQS queue must be in the same account and region as the S3 bucket created\nin Step 1.\n\n 1. Navigate to Simple Queue Service. If this is the first SQS queue you created, click Get Started Now. If you already defined other SQS queues, click Create New Queue.\n\n 2. Create queue.\n\n * Details: Queue Name is filled in as ExpelMasterCloudTrailNotify. Select Standard Queue.\n\n * Configuration:\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. Access policy:\n\n * Select Advanced, change the Resource and aws:SourceArn sections of the following JSON then copy and paste to the text box.\n\n### Note\n\nYour SQS ARN is populated after you switch to the Advanced tab.\n\n \n {\n \"Version\": \"2012-10-17\",\n \"Id\": \"__default_policy_ID\",\n \"Statement\": [\n { \n \"Sid\": \"__owner_statement\",\n \"Effect\": \"Allow\",\n \"Principal\": {\n \"AWS\": \"*\"\n },\n \"Action\": \"SQS:SendMessage\",\n **\"Resource\": \" \",\n ** \"Condition\": {\n \"ArnLike\": {\n **\"aws:SourceArn\": \" \" \n ** }\n }\n }\n ]\n }\n \n\n 4. Enable Server Side Encryption and select AWS Key Management Service key (SSE-KMS) for Encryption key type. Type the key alias created in Step 1 and select the key.\n\n 5. Click Create Queue.\n\n## Step 4: Add key policies\n\n### Note\n\nYou must add this key policy to configure the S3 event notifications in the\nfollowing step.\n\nTo enable trail log bucket to encrypt messages that are being sent to the SQS\nqueue, you need to add key policies.\n\nNavigate to the KMS key created in Step 1.\n\n 1. Click Edit on the Key policy tab.\n\n 2. Copy the following JSON key policy snippet and append it to the end of the existing key policies.\n \n ,\n { \n \"Sid\": \"Allow cloudtrail bucket to encrypt/decrypt SQS\",\n \"Effect\": \"Allow\",\n \"Principal\": {\n \"Service\": \"s3.amazonaws.com\"\n },\n \"Action\": [\n \"kms:GenerateDataKey\",\n \"kms:Decrypt\"\n ],\n \"Resource\": \"*\",\n \"Condition\": {\n \"StringLike\": {\n **\"aws:SourceArn\": \" \"**\n }\n }\n }\n\n 3. Save the key policy and note the KMS ARN.\n\n## Step 5: Configure S3 notifications\n\n 1. Navigate to the S3 bucket containing your CloudTrail logs created in Step 1.\n\n 2. Navigate to Properties.\n\n 3. Select Create event notifications.\n\n 4. General configuration:\n\n * Event name: ExpelNotifyQueue.\n\n * Select All object create events under Event Types.\n\n 5. Destination:\n\n * Select SQS Queue under Destination.\n\n * Select Choose from your SQS queues and select the queue you created from the list. If you don't see your queue, you can select Enter SQS queue ARN and type the queue ARN in the field.\n\n 6. Save your changes.\n\n## Step 6: Create AWSIAM policy\n\nIn this step we create a permissions policy to assign to the IAM Role.\n\n### Important\n\nIf you use AWS organizations, the primary Expel role resides in the\norganization’s primary account where the CloudTrail, S3, and SQS queue were\ncreated for the integration.\n\nThe role and policy must be replicated across all the other accounts in the\norganization to perform AWS investigative actions. The policy in the sub-\naccounts can be changed to exclude the SQS and S3 resources.\n\n * Create AWSIAM Policy.\n\n * Navigate to the IAM service.\n\n * Go to Policies and click Create Policy.\n\n * Select the JSON tab and add the following permissions on the JSON tab:\n \n {\n \"Version\": \"2012-10-17\",\n \"Statement\": [\n {\n \"Sid\": \"VisualEditor0\",\n \"Effect\": \"Allow\",\n \"Action\": [\n \"ec2:DescribeInstances\",\n \"ec2:DescribeRegions\",\n \"ec2:DescribeSecurityGroups\",\n \"iam:List*\",\n \"iam:Get*\",\n \"rds:DescribeDBInstances\",\n \"rds:ListTagsForResource\",\n \"organizations:ListAccounts\",\n \"ec2:DescribeVolumes\",\n \"ecs:DescribeTaskDefinition\",\n \"ecs:ListTaskDefinitions\",\n \"lambda:GetFunction\",\n \"lambda:ListFunctions\",\n \"lightsail:GetInstances\",\n \"lightsail:GetRegions\",\n \"s3:ListAllMyBuckets\",\n \"s3:GetBucketNotification\",\n \"s3:GetEncryptionConfiguration\",\n \"cloudtrail:GetTrailStatus\",\n \"cloudtrail:DescribeTrails\",\n \"cloudtrail:GetTrail\",\n \"cloudtrail:ListTrails\",\n \"config:ListDiscoveredResources\",\n \"config:GetDiscoveredResourceCounts\",\n \"eks:DescribeCluster\",\n \"eks:ListClusters\",\n \"ecs:ListContainerInstances\",\n \"ecs:DescribeContainerInstances\",\n \"ecs:DescribeClusters\",\n \"ecs:ListClusters\",\n \"organizations:DescribeOrganization\"\n \n ],\n \"Resource\": \"*\"\n },\n {\n \"Effect\": \"Allow\",\n \"Action\": [\n \"sqs:DeleteMessage\",\n \"sqs:ReceiveMessage\"\n ],\n **\"Resource\": \" \"**\n },\n {\n \"Effect\": \"Allow\",\n \"Action\": [\n \"s3:GetObject\"\n ],\n **\"Resource\": \" /*\"**\n },\n {\n \"Effect\": \"Allow\",\n \"Action\": [\n \"kms:Decrypt\"\n ],\n **\"Resource\": \" \"**\n }\n ] \n }\n\n### Tip\n\nThere should be “/*” at the end of your S3 ARN in the Resource section. This\nallows the role to access all of the sub-folders in your bucket.\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 * Review and name the policy ExpelAPIPolicy.\n\n## Step 7: Create role\n\n 1. From within the IAM service, navigate to Roles and click Create Role.\n\n 2. Select Another AWS account and fill out the required fields.\n\n * Account ID: 012205512454 (the Expel AWS account ID).\n\n * External ID: this unique identifier is assigned to you by Expel. You can find it in your browser URL after navigating to Settings > My Organization in Workbench.\n\n![AWSNEWCloudtrailURL.png](https://support.expel.io/hc/article_attachments/16137610062867/uuid-7be070e6-190c-14e4-896d-15f962c7e4ba.png)\n\n 3. Attach the IAM policy from Step 1: Configure a global CloudTrail to the Role.\n\n 4. Skip Add Tags.\n\n 5. Review: Name the role ExpelServiceRole and create the Role.\n\n### Important\n\nAll accounts roles must have the same name for the integration to work.\n\n 6. Navigate to the role you just created and copy and save the following information:\n\n * Role ARN.\n\n * External ID Value on the Trust relationships tab.\n\n## Step 8: Register AWS 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. Login to https://workbench.expel.io/settings/security-devices?setupIntegration=aws.\n\n 2. Answer the questions, being sure to answer No to the second question, and then click Start.\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/6760397526035/uuid-41e55342-85c4-4540-b7e2-b7fea3ee941c.png)\n\n 3. Fill out the following fields:\n\n![mceclip4.png](https://support.expel.io/hc/article_attachments/6760379154707/uuid-3b0a083e-73cb-\nbd5f-ab80-e44944e28a44.png)\n\n * Role ARN: the Role ARN.\n\n * Role session name: use a unique name to identify the use of the role.\n\n### Note\n\nExternal ID is automatically populated.\n\n * Region: the AWS region containing the trail S3 and SQS.\n\n * SQS URL: Queue URL.\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"} \ No newline at end of file diff --git a/article_360061333174.json b/article_360061333174.json new file mode 100644 index 0000000000000000000000000000000000000000..891310d5d85729ed49dd88ea3815f74b709af8b1 --- /dev/null +++ b/article_360061333174.json @@ -0,0 +1 @@ +{"title": "Microsoft 365 Direct setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360061333174-Microsoft-365-Direct-setup-for-Workbench", "date": "2021-02-17T20:44:57Z", "contents": "This article provides prerequisites and onboarding steps for Microsoft 365\nDirect.\n\n#### In this article\n\n * Step 1: Enable Microsoft 365 audit logging\n\n * Verify Microsoft 365 audit logging status\n\n * Enable Microsoft 365 audit logging\n\n * Option 1: Enable audit logging in Microsoft 365 Security and Compliance Center in 5 steps\n\n * Option 2: Enable audit logging in Microsoft 365 with PowerShell in 3 steps\n\n * Step 2: Enable Microsoft 365 Enterprise Application\n\n * Option 1: Enable Microsoft 365 integration (preferred)\n\n * Option 2: Create Custom Azure AD Application\n\n * Step 3: Configure Microsoft 365 Direct in Expel Workbench\n\n * Step 4: Configure Azure AD Identity Protection in Expel Workbench (Premium P2 license required)\n\n#### Step 1: Enable Microsoft 365 audit logging\n\nAudit logging is required for Expel to provide detection and investigative\nvalue for Microsoft 365. The Microsoft 365 audit log records user and admin\nactivity and holds the data for 90 days. Audit logging could already be\nrunning on your Microsoft 365 installation. So, the first thing to do is\nverify.\n\n### Verify Microsoft 365 audit logging status\n\nUse the **Verify the auditing status for your organization** instructions from\nMicrosoft 365 support.\n\n * If audit logging is **ON** , skip to Step 2: Enable 0365 Enterprise Application.\n\n * If audit logging is **OFF** , follow the Enable Microsoft 365 audit logging instructions.\n\n### Enable Microsoft 365 audit logging\n\nYou can use either the Microsoft 365 Security and Compliance Center or the\nExchange Online PowerShell to activate audit logging.\n\n### Note\n\nIf you prefer PowerShell, skip to Option 2.\n\n#### Option 1: Enable audit logging in Microsoft 365 Security and Compliance\nCenter in 5 steps\n\n 1. Log to the Microsoft 365 Admin Portal with a global admin user or at minimum, a user with the Organization Management or Compliance Management roles.\n\n 2. Navigate to the Security & Compliance Center.\n\n 3. Navigate to Search & investigation > Audit log search.\n\n 4. Click Start recording user and admin activities.\n\n 5. That’s it! Microsoft 365 makes some changes behind the scenes and begins recording activity in the audit log.\n\n### Note\n\nThis change can take about 24 hours to complete.\n\n#### Option 2: Enable audit logging in Microsoft 365 with PowerShell in 3\nsteps\n\n 1. Connect to Exchange Online PowerShell.\n\n 2. Run the following PowerShell command to turn on audit log search in Microsoft 365.\n\n 3. That’s it! A message appears saying it can take up to 60 minutes for the change to take effect.\n\n### Tip\n\nMicrosoft: Turn Microsoft 365 audit log search on or off.\n\n#### Step 2: Enable Microsoft 365 Enterprise Application\n\nTo integrate Microsoft 365 Direct with Expel, we need to create secure\ncredentials to the API. We provide 2 options for enabling API access:\n\n * Option 1: Enable the **Expel Microsoft 365 Integration** Enterprise Application within Azure.\n\n * Option 2: Create a custom Azure Active Directory (AD) Application.\n\nUsually enabling the Enterprise Application (option 1) is the recommended\napproach. The second option is offered for cases where the absolute minimum\npermissions are required. In either case, the table below shows the required\nitems to obtain during this step:\n\n**Item we need**\n\n|\n\n**Description** \n \n---|--- \n \nAzure Directory (tenant) ID\n\n|\n\nA unique identifier for your Azure instance. Expel needs this information to\nroute our API requests to the right place. \n \nApplication (client) ID (Option 2 only)\n\n|\n\nA unique identifier for the application you create that grants Expel the\naccess it needs to your Microsoft 365 instance. \n \nApplication (client) Secret (Option 2 only)\n\n|\n\nThe API secret that allows Expel to authenticate as the created application to\nyour Microsoft 365 instance. \n \n### Option 1: Enable Microsoft 365 integration (preferred)\n\n 1. As an Administrator, navigate to the Expel Admin Consent Page.\n\n 2. Review and accept requested permissions.\n\n 3. The Expel Microsoft 365 Integration app now appears under Enterprise Applications. Review properties and make sure that all permissions were properly granted. Note the Directory (Tenant) ID when viewing the Expel Microsoft 365 Integration application for use in later steps.\n\n 4. Skip to step 3.\n\n### Option 2: Create Custom Azure AD Application\n\n 1. Log into your Azure Active Directory account (https://portal.azure.com) and open Azure Active Directory.\n\n 2. Navigate to App registrations and create a new app by clicking \\+ New registration.\n\n 3. Fill in the application details. You can technically fill these in however you want, but we recommend the following:\n\n * Name: Expel Cloud Service.\n\n * Supported account types: Accounts in this organizational directory only (first option).\n\n 4. After you fill out the fields, click Register to create the new application.\n\n 5. You navigate 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 Cloud Service.\n\n 6. Make a note of the Application (client) ID and the Directory (tenant) ID. We need that later.\n\n 7. Navigate to API permissions and click Add a permission.\n\n 8. Add these permissions for the Expel App.\n\n * Microsoft Graph API\n\n * AuditLog.Read.All\n\n * Directory.Read.All\n\n * Group.Read.All\n\n * IdentityRiskEvent.Read.All\n\n * SecurityEvents.Read.All\n\n * User.Read.All\n\n * Microsoft 365 Management APIs\n\n * ActivityFeed.Read\n\n * ActivityFeed.ReadDIp\n\n * ServiceHealth.Read\n\n 9. Select the appropriate API Category (for example, Microsoft Graph).\n\n 10. Select Application Permissions.\n\n 11. Select the appropriate permission(s) and click Add Permissions.\n\n 12. Repeat these steps for each permission needed. Verify that:\n\n * All permissions are added as Application permissions and NOT Delegated permissions.\n\n * All Permissions are assigned.\n\n * Consent is granted for the permissions by the AAD admin.\n\n 13. After permissions are assigned, click Grant admin consent, and Yes at the prompt.\n\n 14. Navigate to Expel Cloud Service > Certificates & secrets to begin creating an API key (aka client secret). To create a new key, click +New client secret.\n\n 15. Add a description for the secret (like Expel API) and select Never for expiration. Click Add to create the secret.\n\n 16. You see a new client secret (API Key) appear under Client secrets.\n\n### Important\n\n**Copy the value and save it for later**. It disappears after you navigate\naway from this screen.\n\n#### Step 3: Configure Microsoft 365 Direct 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### 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, log into https://workbench.expel.io/settings/security-devices?setupIntegration=office365. The Add Security Device page for Microsoft 365 (direct) appears.\n\n![office_365_direct_figure_19.png](https://support.expel.io/hc/article_attachments/6493190566675/uuid-937d0142-e3a3-26e1-ce1c-c9f8abcfc220.png)\n\n 2. Use this table to complete the fields.\n\n#### Field Name\n\n|\n\n#### What to put in it \n \n---|--- \n \nSIEM\n\n|\n\nSelect Expel Cloud Service from the list. \n \nName\n\n|\n\nWhat you want to name the security device. \n \nLocation\n\n|\n\nMicrosoft Cloud \n \nTenant ID\n\n|\n\nAzure Directory (tenant) ID from Option 1 or Option 2. \n \nClient ID (Option 2 only)\n\n|\n\nThe Azure Application (client) ID created in Option 2. \n \nClient Secret (Option 2 only)\n\n|\n\nThe Application (client) Secret created in Option 2. \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#### Step 4: Configure Azure AD Identity Protection in Expel Workbench\n(Premium P2 license required)\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_identity_protection. The Add Security Device page for Azure AD Identity Protection appears.\n\n 2. Refer to the table in the previous step to complete the fields.\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#### Related terms\n\nO 365, O365, Office365, ms 365, microsoft 365\n\n"} \ No newline at end of file diff --git a/article_360061333194.json b/article_360061333194.json new file mode 100644 index 0000000000000000000000000000000000000000..4252370a6675812348612bcde9ce8b9bb797549a --- /dev/null +++ b/article_360061333194.json @@ -0,0 +1 @@ +{"title": "Microsoft Defender for Endpoint setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360061333194-Microsoft-Defender-for-Endpoint-setup-for-Workbench", "date": "2021-02-17T20:44:58Z", "contents": "This article helps you integrate your Microsoft Defender for Endpoint\ninstallation with the Expel Workbench.\n\n#### In this article\n\n * Step 1: Enable console access\n\n * Option 1: Basic AAD permissions\n\n * Option 2: Role-based Access Control (RBAC) permissions\n\n * Step 2: Generate API credentials\n\n * Option 1: Enable Defender for Endpoint Enterprise Application (preferred)\n\n * Option 2: Create Custom Microsoft Azure AD application\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### 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 in to the Azure portal as a user assigned a limited administrator directory role or the Guest Inviter role.\n\n 2. In the navigation pane, select Azure Active Directory (AAD).\n\n 3. Under Manage, select Users.\n\n 4. Select New guest user.\n\n 5. On the New user page, select Invite user, fill out the email address (expel_analyst@expel.io), and optionally include a message.\n\n 6. Select Invite to automatically send the invitation to the guest user.\n\n 7. After you send the invitation, the user account is automatically added to the directory as a guest. You have 2 user permission options, Basic AAD Permissions and RBAC Permissions. See instructions for these options below.\n\n### Option 1: Basic AAD permissions\n\nThe simplest way to grant Expel access to the Microsoft Defender for Endpoint\nconsole is with basic AAD permissions.\n\n### Note\n\nIf the tenant is using RBAC (Role-Based Access Control) to manage permissions\nin Microsoft Defender for Endpoint, basic permissions won’t be an option for\nthat tenant. Use Option 2 in this case.\n\nYou have 2 permission levels for basic AAD access. Expel prefers full access\nbut can still operate with read-only access. However, some of our capabilities\nare limited.\n\nAccess Level\n\n|\n\nDescription \n \n---|--- \n \nFull access\n\n|\n\nUsers with full access can log in, view all system information and resolve\nalerts, submit files for deep analysis, and download the onboarding package.\nTo assign full access rights, add the users to all these Directory roles:\n\n * Security administrator\n\n * Security operator\n\n * Security reader\n\n \n \nRead only access\n\n|\n\nUsers with read-only access can log in, view all alerts, and related\ninformation. They can't change alert states, submit files for deep analysis or\nperform any state-changing operations. To assign read-only access rights, add\nthe users to the Security Reader AAD built-in role.\n\n### Note\n\nIn addition to the Security Reader role, the Security Operator role is also\nrequired to view EDR alerts within your Microsoft Defender for Endpoint\nconsole. If only granted the Security Reader role, we may not be able to view\nall of your alerts and may have limited investigate and monitoring\ncapabilities for your device(s). \n \n.\n\n### Option 2: Role-based Access Control (RBAC) permissions\n\nTo more granularly control what permissions Expel has in Microsoft Defender\nfor Endpoint, use RBAC permissions.\n\n### Caution\n\nEnabling RBAC in Microsoft Defender for Endpoint may have an unintended\nconsequence if you were previously using basic permissions. Users who were\npreviously granted Read-only access (Security Reader role) are denied access\nuntil they are added to a Microsoft Defender for Endpoint role.\n\n 1. Navigate to the Microsoft Defender for Endpoint console and open Settings > Permissions > Roles. Click \\+ Add role to create a new role for Expel.\n\n 2. On the role creation page, fill out the required fields:\n\n * Role name: name the role you’re creating.\n\n * Description: describe what this role is for.\n\n * Permissions : select the permissions to grant to Expel.\n\n * Required Permissions:\n\n * View Data (all)\n\n * Security operations\n\n * Threat and vulnerability management\n\n * Alerts investigation\n\n * Recommended Permissions:\n\n * Active remediation actions (all)\n\n * Security operations\n\n * Threat and vulnerability management\n\n * Remediation handling\n\n * Threat and vulnerability management\n\n * Exception handling\n\n * Live response capabilities (advanced)\n\n * Permissions not Required:\n\n * Manage security settings\n\n 3. Click Save.\n\n## Step 2: Generate API credentials\n\nTo integrate Microsoft Defender for Endpoint with Expel, we need to create\nsecure credentials to the API. You have 2 options for enabling API access:\n\n 1. Enable the Expel Defender for Endpoint Integration Enterprise Application within Azure.\n\n 2. Create a custom Azure Active Directory (AD) Application.\n\nUsually enabling the Enterprise Application is the recommended approach. The\nsecond option is offered for cases where the absolute minimum permissions are\nrequired. In either case, the table shows the required items to be obtained\nduring this step:\n\nItem we need\n\n|\n\nDescription \n \n---|--- \n \nAzure Directory (tenant) ID\n\n|\n\nA unique identifier for your Azure instance. Expel needs this information to\nroute our API requests to the right place. \n \nApplication (client) ID (Option 2 only)\n\n|\n\nA unique identifier for the application you create that grants Expel the\naccess it needs to your Azure instance. \n \nApplication (client) Secret (Option 2 only)\n\n|\n\nThe API secret that allows Expel to authenticate as the created application to\nyour Azure instance. \n \n### Option 1: Enable Defender for Endpoint Enterprise Application (preferred)\n\n 1. As an Administrator, navigate to the Expel Admin Consent Page.\n\n 2. Review and accept requested permissions.\n\n 3. The Expel Defender for Endpoint Integration app appears under Enterprise Applications. Review properties and ensure that all permissions are properly granted.\n\n 4. Note the Directory (Tenant) ID when viewing the Expel Defender for Endpoint Integration application for use in later steps.\n\n### Option 2: Create Custom Microsoft Azure AD application\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. On the next screen, create a name for the application and click Register.\n\n 4. Navigate to the application registration created, and open API permissions. Click Add permissions.\n\n 5. On the next screen, select APIs my organization uses tab and search for WindowsDefenderATP.\n\n 6. Click WindowsDefenderATP.\n\n 7. On the next screen, select Application permissions and then Add permissions.\n\n 8. On the next screen, select all of the required permissions below and click Add permissions. Required permissions are:\n\n * WindowsDefenderATP\n\n * AdvancedQuery.Read.All\n\n * Alert.Read.All\n\n * File.Read.All\n\n * Ip.Read.All\n\n * Machine.CollectForensics\n\n * Machine.Read.All\n\n * Score.Read.All\n\n * SecurityConfiguration.Read.All\n\n * SecurityRecommendation.Read.All\n\n * Software.Read.All\n\n * Url.Read.All\n\n * User.Read.All\n\n * Vulnerability.Read.All\n\n * Microsoft Graph\n\n * User.Read\n\n 9. Grant admin consent to the application.\n\n 10. Navigate to Certificates & secrets and click \\+ New client secret.\n\n### Caution\n\nThe client secret only appears 1 time! Make a note of this before navigating\naway from the page.\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/settings/security-devices?setupIntegration=microsoft_atp. You may be asked to log into Workbench.\n\n 2. Fill out the form like this:\n\n![MSDefenderForEndpoint_AddSecDev.png](https://support.expel.io/hc/article_attachments/14880776513939/uuid-a67143de-a087-c8f6-85a7-7757b82b8a55.png)\n\n * For Name type what you want to name the connection.\n\n * For Location type the server location.\n\n * For Directory (tenant) ID, type the Directory (tenant) ID from Step 2, Option 1, or Step 2, Option 2, depending on the option you selected.\n\n * For the Application (client) ID, type Application (client) ID from Step 2, Option 2.\n\n * For App (client) secret, type the Application (client) Secret from Step 2, Option 2.\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"} \ No newline at end of file diff --git a/article_360061333214.json b/article_360061333214.json new file mode 100644 index 0000000000000000000000000000000000000000..b49d8f753a980e618ced847e0d622349a2b4e5b3 --- /dev/null +++ b/article_360061333214.json @@ -0,0 +1 @@ +{"title": "Google Cloud Platform setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360061333214-Google-Cloud-Platform-setup-for-Workbench", "date": "2021-02-17T20:45:01Z", "contents": "This article explains how to connect GCP to Expel Workbench.\n\n#### In this article\n\n * Before you start\n\n * Step 1: Create a Google Cloud Platform project\n\n * Step 2: Create a service account\n\n * Step 3: Create cloud asset custom role and add to service account\n\n * Step 4: Configure a PubSub topic and subscription\n\n * Step 5: Create the aggregated organization log sinks\n\n * Step 6: Enable Event Threat Detection (optional)\n\n * Create continuous exports for cloud logging\n\n * Create a sink for Event Threat Detection\n\n * Step 7: Register Google Cloud Platform in Workbench\n\n## Before you start\n\n * A Google Cloud Platform admin account.\n\n * GCloud command-line tool installed.\n\n * A Google Workspace connector added to your Workbench account.\n\n### Important\n\nMake sure you elevate yourself to admin in Google Cloud Platform before you\nstart these steps.\n\n## Step 1: Create a Google Cloud Platform project\n\nCreate a project and call it expel-integration. Use it to host the rest of the\nintegration’s resources.\n\n## Step 2: Create a service account\n\n 1. Login to the GCP console and navigate to the expel-integration project.\n\n 2. From the navigation menu, go to IAM & Admin > Service Accounts.\n\n 3. Create a new service account and fill in the details.\n\n * Service account name: expel-gcp-integration\n\n * Service account ID: [auto-filled]\n\n * Service account description: used by Expel\n\n 4. Grant the service account Pub/Sub Subscriber and BigQuery Job User permissions.\n\n 5. Generate a JSON private key and download it.\n\n## Step 3: Create cloud asset custom role and add to service account\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. Open Google Cloud Platform.\n\n 2. Make sure you are under the Organization and not a project.\n\n 3. Navigate to IAM & Admin > Roles.\n\n 4. Click Create Role.\n\n 5. Fill in the Title, Description, and ID.\n\n 6. Click Add Permissions.\n\n 7. Add these to the requested permissions, then click Add:\n\n * cloudasset.assets.listResource\n\n * cloudasset.assets.listIamPolicy\n\n * cloudasset.assets.listOrgPolicy\n\n * cloudasset.assets.listAccessPolicy\n\n * cloudasset.assets.listOSInventories\n\n 8. After you are done adding permissions, click Create.\n\n 9. The next step is adding the Service Account with the Role to IAM. You might need to log out and back in to see the new role as an option.\n\n 10. Verify you are still under the Organization and not a project.\n\n 11. Navigate to IAM & Admin > IAM.\n\n 12. Click Add.\n\n 13. Paste in the Service Account Email (expel-gcp-integration@expel-integration.iam.gserviceaccount.com if following this guide's nomenclature) as the new Principal.\n\n## Step 4: Configure a PubSub topic and subscription\n\nConfiguring a PubSub topic and subscription creates a _middle-man_ for the\nsink and Expel receiving alerts. WIthout this step, Expel Workbench can't\nreceive alerts from Google Cloud.\n\n 1. Navigate to Pub/Sub > Topics.\n\n 2. Create a new topic.\n\n * Topic ID: expel-integration-topic\n\n * Select Add a default subscription. This creates a subscription that you change in the next step.\n\nMake note of the full topic name because we use it later. It has the format:\n\nprojects/[project-id]/topics/expel-integration-topic\n\n 3. Navigate to Pub/Sub > Subscriptions.* The _expel-integration-topic-sub_ subscription created in the last step appears in your list of subscriptions.\n\nChange the Acknowledgement deadline to 600 seconds and keep the default values\nfor the rest of the options.\n\nMake note of the full subscription name because we use it later. It looks like\nthis: `projects/[project-id]/subscriptions/expel-integration-topic-sub`\n\n## Step 5: Create the aggregated organization log sinks\n\n### Note\n\nOrganization sinks can’t be created from the Google Cloud console\nhttps://cloud.google.com/logging/docs/export/aggregated_sinks so we use the\ngcloud command-line tool.\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.\n\n * Use this command to filter activity logs:\n \n $ gcloud logging sinks create expel-org-sink-pubsub pubsub.googleapis.com/projects/[project-id]/topics/expel-integration-topic --include-children --organization=[org-id] --log-filter=\"logName=~\\\"cloudaudit\\.googleapis\\.com\\%2Factivity\\\" AND protoPayload.serviceName!=\\\"k8s\\.io\\\"\"\n\n * This automatically creates a new service account which must be granted Pub/Sub Publisher permissions on the integration’s topic.\n\nCreated\n[https://logging.googleapis.com/v2/organizations/000000000000/sinks/expel-org-\nsink].\n\nRemember to grant 'serviceAccount:o278854420484-586207@gcp-sa-logging.iam.\ngserviceaccount.com' the Pub/Sub Publisher role on the topic.\n\nMore information about sinks can be found at\nhttps://cloud.google.com/logging/docs/export/configure_export_v2\n\n 4. From the console, navigate to PubSub > Topics > expel-integration-topic. Use the Permissions tab to add the service account created above as a member.\n\n## Step 6: Enable Event Threat Detection (optional)\n\nEvent Threat Detection is a service offered by Google Cloud Platform at an\nadditional cost. If you do not use this service, skip this step. To learn more\nabout Event Threat Detection, go to: https://cloud.google.com/security-\ncommand-center/docs/concepts-event-threat-detection-overview#log_types.\n\nLinking Event Threat Detection with the Expel Workbench is a two-part process.\nYou must create continuous exports for cloud logging and then create a sink.\n\n### Create continuous exports for cloud logging\n\n 1. Go to the Security Command Center page in the GCP console.\n\n 2. Go to Settings and click Continuous Exports.\n\n 3. Verify Cloud Logging Export status is set to active.\n\n 4. Click Cloud Logging Export and verify Log findings to Cloud logging is enabled.\n\n 5. For Logging project, select the project from Step 1.\n\n 6. Click Save.\n\n### Create a sink for Event Threat Detection\n\n 1. Go to log router.\n\n 2. Create a new sink.\n\n 3. Name it ETD.\n\n 4. Description: Monitor Event Threat Detection for Expel.\n\n 5. Sink Destination: select the Pub/Sub topic created in Step 4 of this procedure.\n\n 6. Choose logs to include in sink: `resource.type=\"threat_detector\"`. The screen should look something like this:\n\n 7. Click Create Sink.\n\n 8. From the Console, navigate to PubSub > Topics > expel-integration-topic. Use the Permissions tab to verify the service account created above is added with the role of Pub/Sub Publisher.\n\n## Step 7: Register Google Cloud Platform 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. Login to https://workbench.expel.io.\n\n 2. Navigate to Organization Settings, then Security Devices.\n\n 3. At the top of the page, click \\+ Add Security Device.\n\n 4. Search for and select Google Cloud Platform.\n\n 5. Fill in the Connection Settings as follows:\n\n * Auth JSON: the JSON key from Step 2.\n\n * Subscription Name: the full PubSub subscription name from Step 4.\n\n * Organization ID: the GCP Organization ID from Step 3.\n\n 6. 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### Note\n\nDon’t forget to register your Google Workspace connector using the Expel\nGoogle Workspace onboarding docs. This is essential, even if you are not a\nGoogle Workspace customer. Google tracks OAuth 2.0 token grants for Google\nCloud Platform in the Google Workspace Admin Audit Logs.\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"} \ No newline at end of file diff --git a/article_360061644694.json b/article_360061644694.json new file mode 100644 index 0000000000000000000000000000000000000000..f16b35cd55e74e36d23915e81a960ae044ad4c7d --- /dev/null +++ b/article_360061644694.json @@ -0,0 +1 @@ +{"title": "Deploying the Expel Assembler in AWS", "url": "https://support.expel.io/hc/en-us/articles/360061644694-Deploying-the-Expel-Assembler-in-AWS", "date": "2021-02-26T17:13:41Z", "contents": "This article describes how to deploy the Expel Assembler in AWS. For more\ninformation on the general Assembler provisioning process, see How to\nprovision Expel Assembler.\n\nYou may need to do things differently than described in this procedure, based\non how you use AWS.\n\n#### In this article\n\n * Getting access to the Expel Assembler AMI\n\n * Start an instance from the Expel Assembler AMI\n\n * Register the assembler in Expel Workbench\n\n * Activate the assembler\n\n * Authorize the assembler in Expel Workbench\n\n#### Getting access to the Expel Assembler AMI\n\n 1. Send your AWS account ID and the AWS region(s) in which you want to deploy an Assembler to your customer success engineer or engagement manager.\n\n 2. Your engagement manager lets you know after the Expel Assembler AMI is shared with your account.\n\n#### Start an instance from the Expel Assembler AMI\n\n 1. Go to the AWS EC2 console at https://console.aws.amazon.com/ec2/.\n\n 2. Select AMIs from the left navigation pane.\n\n 3. Change the image selector list to Private Images.\n\n 4. Select the latest Expel Assembler image with owner 555836951224 (the Expel AWS Account ID).\n\n 5. Click Launch.\n\n 6. Select an instance type of t2.large. Change other instance parameters at your discretion.\n\n### Note\n\nThe Expel Assembler image allows inbound SSH from all addresses. Expel\nrecommends assigning the Assembler to a Security Group that restricts inbound\nSSH to your authorized IP addresses.\n\n 7. Click Review and Launch.\n\n 8. Click Launch.\n\n 9. Select a key pair that you to log into the Assembler.\n\n#### Register the assembler in Expel Workbench\n\n 1. In Expel Workbench, click Settings in the top navigation bar. You see a dialog 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 use names that are meaningful to both you and to Expel so you can easily identify the assembler. For example: ACME HQ.\n\n 3. Click Save.\n\n 4. Note the Install Code for the newly registered Assembler. You need this in the next section to activate the Assembler.\n\n 5. To add another Assembler, click the Add Assembler button and repeat the steps.\n\n#### Activate the assembler\n\n 1. SSH to the expel account on the instance you just launched: ssh expel@\n\n 2. Activate the Assembler by supplying the 8-character install code created in the previous step: sudo expelmanage –activate \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 3. Run exit to log out of the Assembler.\n\n#### Authorize the assembler in Expel Workbench\n\nGo back to How to provision Expel Assembler and continue with Authorize the\nAssembler in Expel Workbench.\n\n"} \ No newline at end of file diff --git a/article_360063148313.json b/article_360063148313.json new file mode 100644 index 0000000000000000000000000000000000000000..fabd5304077bb3a5b938e2f1268cd66893c8ce63 --- /dev/null +++ b/article_360063148313.json @@ -0,0 +1 @@ +{"title": "CrowdStrike Falcon setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360063148313-CrowdStrike-Falcon-setup-for-Workbench", "date": "2021-02-17T20:44:46Z", "contents": "This article explains how to connect CrowdStrike Falcon to Workbench.\n\n### Caution\n\nIf you are a CrowdStrike Complete customer, don't use this guide. Use the\nCrowdStrike Falcon Complete article instead.\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 * Step 1: Enable console access\n\n * Step 2: Enabling the OAuth2 API\n\n * Step 3: Configure the technology in Workbench\n\n## About connecting your device\n\nConnecting your device to Workbench allows Workbench to ingest the CrowdStrike\nlogs. CrowdStrike logs include a great deal of information that can take hours\nto manually review. And not all CrowdStrike alerts need attention.\n\nCrowdStrike Falcon generates various alert types, which consist of a Mitre\nATT&CK based detection framework. The Expel alert poller consumes all Falcon\nalerts except Machine Learning and Cloud-based ML with a vendor severity of\nInformation or Low.\n\nCrowdScore in CrowdStrike delivers prioritized incidents to streamline the\ntriage process and help analysts focus on the most critical threats first. But\nCrowdScore logs alone don't typically have full process genealogy / indicators\nassociated with them. This means that analysts generally need to do their own\ninvestigation using Event Search. Real Time Response also allows analysts to\nconnect to a host, typically to query information and pull files.\n\nAfter you connect CrowdStrike to Workbench, Workbench ingests Crowdscore\nIncidents. Workbench adds context, enriches with intel, and assesses the risk.\nDepending on your settings, Workbench can auto-remediate or send to an Expel\nanalyst for further investigation.\n\nAll Expel detections for CrowdStrike Falcon are available in the Expel\nWorkbench in the Detections area.\n\n## Before you start\n\n**If you plan to enroll in the Expel Hunting service, your organization needs\na Falcon Data Replicator subscription.**\n\n### Tip\n\nWe support CrowdStrike Falcon Elite, Enterprise, and Premium products.\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\nExpel is a CrowdStrike Certified Managed Security Provider partner. This\nallows Expel to use the Expel FlightControl account to log into your device.\nYou must request from CrowdStrike that Expel can have this access to your\nconsole and verify Expel is allowed to have it.\n\nAfter CrowdStrike sets up this access, Expel is assigned these 4 roles in your\nconsole:\n\n * Detections Exceptions Manager\n\n * Falcon Investigator\n\n * Falcon Security Lead\n\n * Real Time Responder - Active Responder\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\nTo allow Expel partner console access to your console, do the following:\n\n 1. Print, complete, and sign the CrowdStrike MSP Authorization Form. Request this form from your Expelcustomer success engineer.\n\n 2. Attach the completed form in an email back to us to devicehealth@expel.io. Expel sends this form to CrowdStrike, cc-ing you, requesting partner access to your console. After you confirm this access is allowed, Expel is granted access with the roles listed above.\n\n## Step 2: Enabling the OAuth2 API\n\n### Tip\n\nAs you complete this step, you may discover you're missing a scope. If that's\nthe case, contact your engagement manager for help.\n\n 1. After you log into the Falcon UI, navigate to Support and resources > API Clients and Keys.\n\n 2. Select Add new API Client.\n\n 3. Type Expel as the Client Name.\n\n 4. Type Expel API Access as the Description.\n\n 5. Select the following permissions. **Bold** is required. The more permissions you allow, the better the SOC analysts can research what's happening and the faster they can respond.\n\nIn this area...\n\n|\n\nthis permission...\n\n|\n\ndoes this...\n\n|\n\nNotes \n \n---|---|---|--- \n \nDetections\n\n|\n\n**Read** and **Write**\n\n|\n\n**Read** : view information about a detection, such as its behavior, severity,\nassociated host, timestamps, and so on.\n\n**Write** : modify metadata about a detection, such as its status, assignee,\nand description.\n\n|\n\nWrite permission is only required to use the Mark in Progress option in\nCrowdStrike. \n \nHosts\n\n|\n\n**Read** and Write\n\n|\n\n**Read** : Search for hosts and get host details, using standard or scrolling\npagination. Details include OS type and version, sensor version, assigned\npolicies, containment status, and more.\n\nWrite: Take action on hosts, including containing or lifting containment on a\nhost.\n\n|\n\nWrite permission for Hosts is required for Auto Host Containment. For more\ninformation, see the CrowdStrike Auto Host Containment article. \n \nIncidents\n\n|\n\n**Read**\n\n|\n\n**Read** : Search and view details on incidents and behaviors.\n\nWrite: Perform actions on incidents, such as adding tags or comments or\nupdating the incident name or description.\n\n|\n\nRead is required to allow Expel to Mark alerts as 'in-progress' when Expel\nprocesses them.\n\nTo select Incidents, you need Falcon Insight XDR enabled. \n \nReal Time Response (RTR)\n\n|\n\nRead and Write\n\n|\n\nRead: Run RTR commands that get information from a host, equivalent to the RTR\nRead OnlyAnalyst role.\n\nWrite: Run RTR commands that send information to a host, equivalent to the RTR\nActive Responder role.\n\n| \n \nIOC Management\n\n|\n\nRead and Write\n\n|\n\nRead: Search your custom IOCs and view hosts that observed your custom IOCs.\n\nWrite: Create, modify, or delete your custom IOCs.\n\n|\n\nWrite permission is required to block hashes through auto-remediation. For\nmore information, see the Auto Block Bad Hashes article. \n \n 6. Click Save.\n\n 7. Make a record of your Client ID and the Client Secret for the API. You need to finish the connection to Workbench.\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 in to https://workbench.expel.io/settings/security-devices?setupIntegration=crowdstrike.\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/13874927705747/uuid-9318eb43-cd36-665a-5394-1a0e3bd0f5a8.png)\n\n 2. For Name type the host name of the device.\n\n 3. For Location type the geographic location of the appliance.\n\n 4. After typing the name and location, complete the remaining fields using the credentials and information you collected in Step 2 above.\n\n * API Username and API Key can be left blank.\n\n * Type OAuth2 Client ID from Step 2 in Client ID.\n\n * Type OAuth2 Secret from Step 2 in Client secret.\n\n * Select the Base URL from Step 2 in CrowdStrike API address.\n\n * Mark alerts as 'in-progress' when Expel processes them?, select Yes.\n\n### Tip\n\nRequires the incidents:read permission above to work.\n\n * Enable Crowdstrike Falcon Identity Protection alert aggregation?, select Yes.\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"} \ No newline at end of file diff --git a/article_360063148333.json b/article_360063148333.json new file mode 100644 index 0000000000000000000000000000000000000000..78e88336003fe2fa532f489b74a06567e66c3216 --- /dev/null +++ b/article_360063148333.json @@ -0,0 +1 @@ +{"title": "Zscaler setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360063148333-Zscaler-setup-for-Workbench", "date": "2021-02-17T20:44:46Z", "contents": "This article explains how to connect Zscaler to Workbench.\n\n#### In this article\n\n * Before you start\n\n * Step 1: Send Zscaler events to a SIEM\n\n * Step 2: Configure the technology in Workbench\n\n * Step 3: Edit the device to add console access\n\n## Before you start\n\nBefore starting this procedure, you must have:\n\n * An SIEM that Expel supports for this integration, which includes any 1 of the following:\n\n * Microsoft Sentinel\n\n * Splunk\n\n * Sumo Logic\n\n### Note\n\nIf you have a SIEM that's supported by Expel but isn't listed here, contact\nus.\n\n * The Nanolog Streaming Service (NSS) from Zscaler to forward data to your SIEM.\n\n## Step 1: Send Zscaler events to a SIEM\n\nThe Nanolog Streaming Service (NSS) feed specifies the data from the logs that\nthe NSS sends to the SIEM. Expel uses 3 NSS feeds to forward data to a SIEM.\n\n 1. The EXPEL_MALWARE feed captures any malware class events.\n\n * **Feed Output Type: QRadar LEEF**\n\n * **Web Log Filters =** Security > Malware Classes : Sandbox, Spyware, Virus\n\n * **Feed Output Format =** %s{mon} %02d{dd}\n\n`%02d{hh}:%02d{mm}:%02d{ss} zscaler-\nEXPEL_MALWARE:LEEF:1.0|Zscaler|NSS|4.1|fqdn=%s{host}\\turl=%s{url}\\tmethod=%s{reqmethod}\\tuser_agent=%s{ua}\\turlclass=%s{urlclass}\\tcategory=%s{urlcat}\\treferrer=%s{referer}\\tresponse=%s{respcode}\\tprotocol=%s{proto}\\tduration_ms=%d{ctime}\\tsrc=%s{cip}\\tdst=%s{sip}\\tbytes_rx=%d{respsize}\\tbytes_tx=%d{reqsize}\\tappclass=%s{appclass}\\tappname=%s{appname}\\tflow_id=%d{recordid}\\torganization=%s{dept}\\tusername=%s{login}\\tvendor_version=%s{productversion}\\tname=%s{reason}\\talert_at=%s{time}%s{tz}\\talertaction=%s{action}\\tfile_hash=%s{bamd5}\\tmime_type=%s{filetype}\\tfilename=%s{filename}\\tscore=%d{riskscore}\\trealm=%s{location}\\tnsssvcip=%s{nsssvcip}\\tthreatname=%s{threatname}\\tmalwarecategory=%s{malw\narecat}\\tmalwareclass=%s{malwareclass}\\t\\n%s{mon} %02d{dd}\n%02d{hh}:%02d{mm}:%02d{ss} zscaler-nss:\nLEEF:1.0|Zscaler|NSS|4.1|%s{reason}|cat=%s{action}\\tdevTime=%s{mon} %02d{dd}\n%d{yy} %02d{hh}:%02d{mm}:%02d{ss} %s{tz}\\tdevTimeFormat=MMM dd yyyy HH:mm:ss\nz\\tsrc=%s{cip}\\tdst=%s{sip}\\tsrcPostNAT=%s{cintip}\\trealm=%s{location}\\tusrName=%s{login}\\tsrcBytes=%d{reqsize}\\tdstBytes=%d{respsize}\\trole=%s{dept}\\tpolicy=%s{reason}\\turl=%s{eurl}\\trecordid=%d{recordid}\\tbwthrottle=%s{bwthrottle}\\tuseragent=%s{ua}\\treferer=%s{ereferer}\\thostname=%s{ehost}\\tappproto=%s{proto}\\turlcategory=%s{urlcat}\\turlsupercategory=%s{urlsupercat}\\turlclass=%s{urlclass}\\tappclass=%s{appclass}\\tappname=%s{appname}\\tmalwaretype=%s{malwarecat}\\tmalwareclass=%s{malwareclass}\\tthreatname=%s{threatname}\\triskscore=%d{riskscore}\\tdlpdict=%s{dlpdict}\\tdlpeng=%s{dlpeng}\\tfileclass=%s{fileclass}\\tfiletype=%s{filetype}\\treqmethod=%s{reqmethod}\\trespcode=%s{respcode}\\tcontenttype=%s{contenttype}\\tunscannabletype=%s{unscannabletype}\\tdeviceowner=%s{deviceowner}\\tdevicehostname=%s{devicehostname}\\n`\n\n 2. The EXPEL_THREAT feed surfaces any Advanced Threat events.\n\n * **Feed Output Type: QRadar LEEF**\n\n * **Web Log Filters =** Security > Advanced Threats : Adware/Spyware Sites, Botnet Callback, Browser Exploit, Cross-site Scripting, Cryptomining, Malicious Content, Other Threat, Peer-to-Peer, Phishing, Spyware Callback, Suspicious Content, Suspicious Destination, Unauthorized Communication, Web Spam\n\n * **Feed Output Format =** %s{mon} %02d{dd}\n\n`%02d{hh}:%02d{mm}:%02d{ss} zscaler-\nEXPEL_THREAT:LEEF:1.0|Zscaler|NSS|4.1|fqdn=%s{host}\\turl=%s{url}\\tmethod=%s{reqmethod}\\tuser_agent=%s{ua}\\turlclass=%s{urlclass}\\tcategory=%s{urlcat}\\treferrer=%s{referer}\\tresponse=%s{respcode}\\tprotocol=%s{proto}\\tduration_ms=%d{ctime}\\tsrc=%s{cip}\\tdst=%s{sip}\\tbytes_rx=%d{respsize}\\tbytes_tx=%d{reqsize}\\tappclass=%s{appclass}\\tappname=%s{appname}\\tflow_id=%d{recordid}\\torganization=%s{dept}\\tusername=%s{login}\\tvendor_version=%s{productversion}\\tname=%s{reason}\\talert_at=%s{time}%s{tz}\\talertaction=%s{action}\\tfile_hash=%s{bamd5}\\tmime_type=%s{filetype}\\tfilename=%s{filename}\\tscore=%d\n{riskscore}\\trealm=%s{location}\\tnsssvcip=%s{nsssvcip\n}\\tthreatname=%s{threatname}\\tmalwarecategory=%s{malw\narecat}\\tmalwareclass=%s{malwareclass}\\t\\n%s{mon} %02d{dd}\n%02d{hh}:%02d{mm}:%02d{ss} zscaler-nss:\nLEEF:1.0|Zscaler|NSS|4.1|%s{reason}|cat=%s{action}\\tdevTime=%s{mon} %02d{dd}\n%d{yy} %02d{hh}:%02d{mm}:%02d{ss} %s{tz}\\tdevTimeFormat=MMM dd yyyy HH:mm:ss\nz\\tsrc=%s{cip}\\tdst=%s{sip}\\tsrcPostNAT=%s{cintip}\\trealm=%s{location}\\tusrName=%s{login}\\tsrcBytes=%d{reqsize}\\tdstBytes=%d{respsize}\\trole=%s{dept}\\tpolicy=%s{reason}\\turl=%s{eurl}\\trecordid=%d{recordid}\\tbwthrottle=%s{bwthrottle}\\tuseragent=%s{ua}\\treferer=%s{ereferer}\\thostname=%s{ehost}\\tappproto=%s{proto}\\turlcategory=%s{urlcat}\\turlsupercategory=%s{urlsupercat}\\turlclass=%s{urlclass}\\tappclass=%s{appclass}\\tappname=%s{appname}\\tmalwaretype=%s{malwarecat}\\tmalwareclass=%s{malwareclass}\\tthreatname=%s{threatname}\\triskscore=%d{riskscore}\\tdlpdict=%s{dlpdict}\\tdlpeng=%s{dlpeng}\\tfileclass=%s{fileclass}\\tfiletype=%s{filetype}\\treqmethod=%s{reqmethod}\\trespcode=%s{respcode}\\tcontenttype=%s{contenttype}\\tunscannabletype=%s{unscannabletype}\\tdeviceowner=%s{deviceowner}\\tdevicehostname=%s{devicehostname}\\n`\n\n 3. (Optional) You can add an additional feed, EXPEL_INVESTIGATE, to forward all web log data to your SIEM. SOC analysts use this information to understand, scope, and answer security questions related to threat behavior. Specifically, how it got there, what it is, and what must be done to remediate.\n\n * **Feed Output Type: QRadar LEEF**\n\n * **Web Log Filters =** None\n\n * **Feed Output Format =** %s{mon} %02d{dd}\n\n`%02d{hh}:%02d{mm}:%02d{ss} zscaler-\nEXPEL_INVESTIGATE:LEEF:1.0|Zscaler|NSS|4.1|fqdn=%s{host}\\turl=%s{url}\\tmethod=%s{reqmethod}\\tuser_agent=%s{ua}\\turlclass=%s{urlclass}\\tcategory=%s{urlcat}\\treferrer=%s{referer}\\tresponse=%s{respcode}\\tprotocol=%s{proto}\\tduration_ms=%d{ctime}\\tsrc=%s{cip}\\tdst=%s{sip}\\tbytes_rx=%d{respsize}\\tbytes_tx=%d{reqsize}\\tappclass=%s{appclass}\\tappname=%s{appname}\\tflow_id=%d{recordid}\\torganization=%s{dept}\\tusername=%s{login}\\tvendor_version=%s{productversion}\\tname=%s{reason}\\talert_at=%s{time}%s{tz}\\talertaction=%s{action}\\tfile_hash=%s{bamd5}\\tmime_type=%s{filetype}\\tfilename=%s{filename}\\tscore=%d{riskscore}\\trealm=%s{location}\\tnsssvcip=%s{nsssvcip}\\tthreatname=%s{threatname}\\tmalwarecategory=%s{malwarecat}\\tmalwareclass=%s{malwareclass}\\t\\n%s{mon}\n%02d{dd} %02d{hh}:%02d{mm}:%02d{ss} zscaler-nss:\nLEEF:1.0|Zscaler|NSS|4.1|%s{reason}|cat=%s{action}\\tdevTime=%s{mon} %02d{dd}\n%d{yy} %02d{hh}:%02d{mm}:%02d{ss} %s{tz}\\tdevTimeFormat=MMM dd yyyy HH:mm:ss\nz\\tsrc=%s{cip}\\tdst=%s{sip}\\tsrcPostNAT=%s{cintip}\\trealm=%s{location}\\tusrName=%s{login}\\tsrcBytes=%d{reqsize}\\tdstBytes=%d{respsize}\\trole=%s{dept}\\tpolicy=%s{reason}\\turl=%s{eurl}\\trecordid=%d{recordid}\\tbwthrottle=%s{bwthrottle}\\tuseragent=%s{ua}\\treferer=%s{ereferer}\\thostname=%s{ehost}\\tappproto=%s{proto}\\turlcategory=%s{urlcat}\\turlsupercategory=%s{urlsupercat}\\turlclass=%s{urlclass}\\tappclass=%s{appclass}\\tappname=%s{appname}\\tmalwaretype=%s{malwarecat}\\tmalwareclass=%s{malwareclass}\\tthreatname=%s{threatname}\\triskscore=%d{riskscore}\\tdlpdict=%s{dlpdict}\\tdlpeng=%s{dlpeng}\\tfileclass=%s{fileclass}\\tfiletype=%s{filetype}\\treqmethod=%s{reqmethod}\\trespcode=%s{respcode}\\tcontenttype=%s{contenttype}\\tunscannabletype=%s{unscannabletype}\\tdeviceowner=%s{deviceowner}\\tdevicehostname=%s{devicehostname}\\n`\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\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. In a new browser tab, log into https://workbench.expel.io/settings/security-devices?setupIntegration=Zscaler.\n\n 2. Complete the following fields in Workbench:\n\n![mceclip1.png](https://support.expel.io/hc/article_attachments/13874955821715/uuid-9d43e526-d4c0-0dfb-d5dc-\nddb469e2673c.png)\n\n * Select the SIEM. This device should already be onboard in Workbench.\n\n * Type the Name and Location of the device.\n\n * For SIEM index, type the name of the SIEM index that Zscaler events are being indexed to.\n\n 3. Click Save.\n\n 4. You can set up console access now or use the instructions below to set it up later.\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\nz scaler\n\n"} \ No newline at end of file diff --git a/article_360063148353.json b/article_360063148353.json new file mode 100644 index 0000000000000000000000000000000000000000..82124062b5ddafdfab38a02e2534dcc735e8dd7c --- /dev/null +++ b/article_360063148353.json @@ -0,0 +1 @@ +{"title": "Palo Alto setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360063148353-Palo-Alto-setup-for-Workbench", "date": "2021-02-17T20:44:47Z", "contents": "This article explains how to connect Palo Alto 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 Palo Alto 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### Note\n\nThe Expel Assembler needs access to the Palo Alto device or instance through\nport 443 (UI) and 443 (API) for on-premises onboardings.\n\nFor cloud instances, you need to allow Expel through the internet. Expel has 6\negress IP addresses. All requests to the API come from 1 of the 6 IP\naddresses:\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 1. Log onto the Palo Alto console.\n\n 2. On the console page, navigate to Device > Administrators.\n\n 3. Click Add at the bottom left of the page.\n\n 4. In Administrator dialog box, type expeluser for Name.\n\n 5. Type a Password.\n\n 6. For Administrator Type, select Dynamic.\n\n 7. Select Superuser (read-only) from the list below Administrator Type.\n\n 8. Click OK.\n\n 9. Verify that expeluser is created on the console page.\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 Palo Alto API.\n\n### Note\n\nSecurity Assertion Markup Language (SAML) authenticated accounts on Palo Alto\ncan't generate API keys.\n\n 1. In a new browser tab, open the following URL, replacing **< hostname or IP address>**, **< username>**, and **< password>** with the appropriate values for your Panorama console or the management interface of your Palo Alto Networks firewall: https:///api/?type=keygen&user=&password=\n\n * **< hostname or IP address>** is your Palo Alto URL from your console page.\n\n * **< username>** is the username created in Step 1 (expeluser).\n\n * **< password>** is the password entered in Step 1.\n\n 2. After the URL is complete, press Enter.\n\n 3. On the next screen, the generated API key appears. Save it for later use.\n\n 4. If you use Wildfire API, we also need a Wildfire API key in addition to the API key just created. Follow these instructions and create a Wildfire API key. Save it for later use.\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 Workbench. This link opens the Add Security Device screen directly.\n\n 2. On the Add Security Device screen, fill in the blanks like this:\n\n![Screen Shot 2021-03-08 at 7.21.46\nAM.png](https://support.expel.io/hc/article_attachments/10403447222547/uuid-d5338fc7-4c74-dfb9-375a-b9007a511396.png)\n\n * For Where is your device? select your installation type.\n\n * For On-prem installations, select your Assembler from the list.\n\n * For Server address type the hostname or IP address of the Palo Alto management interface. Device IP can be found in the Palo Alto console under Dashboard > General Information > MGT IP Address.\n\n * For Name and Location, use a name and location that are meaningful to you.\n\n * For API key type the API key generated in Step 2.\n\n * For PanOS version, OS version must be specified if OS version is <= 6.\n\n * For Wildfire API key type the Wildfire API key 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 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"} \ No newline at end of file diff --git a/article_360063148373.json b/article_360063148373.json new file mode 100644 index 0000000000000000000000000000000000000000..b6c3d10560cfb0efc1c2cf5967e69c98a8bdff81 --- /dev/null +++ b/article_360063148373.json @@ -0,0 +1 @@ +{"title": "AWS GuardDuty setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360063148373-AWS-GuardDuty-setup-for-Workbench", "date": "2021-02-17T20:44:49Z", "contents": "This article describes connecting AWS GuardDuty to Workbench.\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 * Step 1: Create an AWSIAM policy\n\n * Step 2: Create an IAM role\n\n * Step 3: Onboard AWS GuardDuty in Workbench\n\n## About connecting your device\n\nConnecting your device to Workbench allows Workbench to ingest the logs. AWS\nGuardDuty logs include a great deal of information that can take hours to\nmanually review. And not all AWS GuardDuty alerts need attention.\n\n## Before you start\n\n### Note\n\nYou need an AWS account with permissions to create and change IAM roles.\n\n 1. We have an onboarding wizard that uses Cloudformation templates to perform all of the following steps in Workbench.\n\n 2. If you prefer not to use the wizard, click Connect Manually to access the manual form and follow the instructions below.\n\n 3. If you are using an AWS GuardDuty Delegated Admin account, the following steps only need to be completed in that account. Only 1 device needs to be added to the Expel Workbench using the Delegated Admin account's primary region. If you are not using a Delegated Admin account, complete the following steps for each account you want monitored and add 1 device in Workbench per account.\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: Create an AWSIAM policy\n\nIn this step, we create a permissions policy to assign to the IAM Role.\n\n 1. Log into the AWS console and navigate to the IAM service.\n\n 2. Go to Policies and click Create Policy.\n\n 3. Add the following permissions using the JSON tab.\n \n {\n \"Version\": \"2012-10-17\",\n \"Statement\": [\n {\n \"Sid\": \"VisualEditor0\",\n \"Effect\": \"Allow\",\n \"Action\": [\n \"guardduty:GetFindings\",\n \"guardduty:ListDetectors\",\n \"ec2:DescribeRegions\",\n \"guardduty:ListFindings\",\n \"guardduty:GetDetector\"\n ],\n \"Resource\": \"*\"\n } \n ]\n }\n\n 4. Review and name the policy.\n\n## Step 2: Create an IAM role\n\nCreate an IAM role to connect to your AWS GuardDuty Service.\n\n 1. From within the IAM service, navigate to Roles and click Create Role.\n\n 2. Select Another AWS account and fill out the required fields.\n\n * Account ID: 012205512454 (the ExpelAWS account ID).\n\n * External ID: Provided to you by Expel.\n\n 3. Attach the IAM policy from Step 1 to the Role.\n\n 4. Give the Role a name and click Create Role.\n\n 5. Navigate to the role you just created and copy the following information for onboarding in Workbench.\n\n * Role ARN.\n\n * External ID Value on the Trust relationships tab.\n\n## Step 3: Onboard AWS GuardDuty 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=aws_guardduty.\n\n 2. The Add Security Device page for AWS GuardDuty appears. Use the wizard or click Connect Manually to add your AWS GuardDuty installation to Workbench manually.\n\n![mceclip1.png](https://support.expel.io/hc/article_attachments/6760368085651/uuid-5ee7a426-0767-1fd4-2652-81fbe353ac44.png)\n\n 3. Complete the following information:\n\n * For Name type the host name of the AWS GuardDuty device.\n\n * For Location type the geographic location of the appliance.\n\n * Role ARN: type the Role ARN from Step 2.\n\n * Role session name: Use a unique name to identify the role.\n\n * External ID: type the External ID from Step 2 if it's not automatically populated for you.\n\n * Region: type region of Primary AWS GuardDuty account. For example us-east-1\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"} \ No newline at end of file diff --git a/article_360063148393.json b/article_360063148393.json new file mode 100644 index 0000000000000000000000000000000000000000..922acc4f4db7a9d325a74f7340c27e594b5aa0a2 --- /dev/null +++ b/article_360063148393.json @@ -0,0 +1 @@ +{"title": "GitHub Cloud setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360063148393-GitHub-Cloud-setup-for-Workbench", "date": "2021-02-17T20:44:50Z", "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 cloud-hosted GitHub App\n\n * Step 2: Configure the technology in Workbench\n\n * Step 3: Update your GitHub logs to record/display IP addresses\n\n## Before you start\n\nYou must have:\n\n * A GitHub Enterprise account license. For more information, see GitHub's products.\n\n### Note\n\nThis procedure is specifically for cloud-hosted GitHub deployments. For on-\nprem, use the GitHub self-hosted (on-prem) Workbench setup guide.\n\n## Step 1: Install the cloud-hosted GitHub App\n\nExpel 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. Navigate to the Expel GitHub Integration Application installation page: https://github.com/apps/expelgithubintegration and click Install.\n\n 2. Follow the steps to install the application within the GitHub Organization you want to onboard.\n\n### Note\n\nIf you have multiple organizations, create a separate Security Device in\nWorkbench for each organization.\n\n 3. After you successfully install the application, note the Installation ID that can be found in your URL under the format \"github.com/.../installations//…\"\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/13874884072979/uuid-18f1e774-583c-2ff0-dd49-4b9c0a69dd08.png)\n\n 2. For Where is your device? select Cloud.\n\n 3. 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 slug URL. This is only required if you use an enterprise SAML identity provider, otherwise you can leave it blank.\n\n * For the Application installation ID type the installation ID from Step 1.\n\n 4. Leave the other fields blank.\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## Step 3: Update your GitHub logs to record/display IP addresses\n\nWhile not required, consider updating your GitHub audit logs to record/display\nIP addresses. These addresses are not automatically logged in GitHub. This is\na key field when the SOC analysts investigate GitHub activity.\n\nFollow the instructions located here for steps to set this up.\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"} \ No newline at end of file diff --git a/article_360063148413.json b/article_360063148413.json new file mode 100644 index 0000000000000000000000000000000000000000..a017c86894aaecde07a5a81fc7196a2f780fc477 --- /dev/null +++ b/article_360063148413.json @@ -0,0 +1 @@ +{"title": "DUO Cloud setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360063148413-DUO-Cloud-setup-for-Workbench", "date": "2021-02-17T20:44:51Z", "contents": "This article explains how to connect DUO Cloud to Expel Workbench.\n\n#### In this article\n\n * Before you start\n\n * Step 1: Generate API credentials\n\n * Step 2: Configure the technology in Workbench\n\n## Before you start\n\nHere's what you need to get started:\n\n * DUO Cloud administrator account with Owner role.\n\n * DUO Cloud Admin APIs enabled as these aren't enabled by default. For more information about DUO Cloud Admin APIs, go to https://duo.com/docs/adminapi.\n\n## Step 1: Generate API credentials\n\nTo integrate the technology with Workbench, we need to create secure\ncredentials to the API.\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. Log in to the DUO Cloud admin portal as an Owner (https://admin.duosecurity.com) and navigate to Applications > Protect an Application.\n\n * Click Protect this Application for the DUO Cloud Admin API.\n\n 2. On the next screen, copy and save the Integration key, Secret key, and API hostname for this application. These are the credentials Expel needs to connect to the DUO Cloud service.\n\n### Tip\n\nThese are not shown again, so save them now.\n\n 3. In the Settings section, name the application something descriptive. We recommend Expel API.\n\n 4. Check the following required permissions:\n\nPermissions\n\n|\n\n**What Expel does with it** \n \n---|--- \n \nGrant read information\n\n|\n\nReads total user count. \n \nGrant read log\n\n|\n\nReads audit logs for security monitoring. \n \nGrant read resource\n\n|\n\nReads user and groups information and enrich events with this context. \n \n 5. If you prefer to specify the IPs to access the API, list the following in the Networks for API Access field:\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 6. Click Save changes.\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, log into Workbench.\n\n![DUO_Device_Connect.png](https://support.expel.io/hc/article_attachments/13874867263251/uuid-b8854bdf-6a84-941d-8db3-f196c075019d.png)\n\n 2. Type in this information:\n\n * Name and Location.\n\n * API Hostname from Step 1.\n\n * Integration key from Step 1.\n\n * Secret key from 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"} \ No newline at end of file diff --git a/article_360063148453.json b/article_360063148453.json new file mode 100644 index 0000000000000000000000000000000000000000..1d8d38cedee1a0344067b99685893d30b9edcc7d --- /dev/null +++ b/article_360063148453.json @@ -0,0 +1 @@ +{"title": "VMware Carbon Black Endpoint Standard setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360063148453-VMware-Carbon-Black-Endpoint-Standard-setup-for-Workbench", "date": "2021-02-17T20:44:53Z", "contents": "This article explains how to connect VMware Carbon Black Endpoint Standard to\nWorkbench.\n\n#### In this article\n\n * Step 1: Enable console access\n\n * Step 2: Generate API credentials and SIEM access\n\n * Obtain the API and SIEM key for the Expel account\n\n * Subscribe to notifications\n\n * Step 3: Configure the technology in Workbench\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 Endpoint Standard\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. Navigate to gear icon on left side and click Users. Then click Add User on the top right of the screen.\n\n 2. For First name type Expel.\n\n * For Last name type SOC.\n\n * For Email: soc+@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 * For Role select Level 2 Analyst.\n\n * Click Save.\n\n## Step 2: Generate API credentials and SIEM access\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 VMware Carbon Black Endpoint Standard API and SIEM.\n\n### Obtain the API and SIEM key for the Expel account\n\n 1. Navigate to gear icon on left side and click Users. Then click Add User on the top right of the screen.\n\n 2. For Name type Expel.\n\n * For Access Level select API.\n\n * For Authorized IP address, type the IP address of the externally facing IP of the Expel Assembler. If you're unsure, the following code can be run on the Assembler to list the current IP: c`url -s http://ipchicken.com | egrep -o ‘([[:digit:]]{1,3}\\.){3}[[:digit:]]{1,3}’`\n\n * Click Save.\n\n 3. For SIEM access, follow the same steps above and select SIEM for Access level.\n\n 4. Make note of the API, SIEM API, and API IDs for each. These are used in Step 3 for registration within Workbench.\n\n### Subscribe to notifications\n\n 1. Navigate to the gear icon on the left side, click Notifications, then click ADD NOTIFICATION.\n\n 2. For Name type Expel Threat.\n\n 3. For Notify when select Threat and select Alert priority 3.\n\n 4. For Policy select All Policies.\n\n 5. Click in Search for API field and search for the SIEM API Key created for Expel in Obtain the API and SIEM key for the Expel account.\n\n 6. Click Save.\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, 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 VMware Carbon Black Endpoint Standard.\n\n 5. Complete all fields using the credentials and information you collected in Step 1 and Step 2.\n\n![Screen Shot 2021-03-30 at 7.49.42\nAM.png](https://support.expel.io/hc/article_attachments/6760462082451/uuid-2711e662-7eb1-aee0-63b2-ef9846f92c31.png)\n\n 6. Select an Assembler from the list. Select the assembler you set up in Getting connected to Expel Workbench.\n\n 7. Type Assembler Name and Location. For example: VMware Carbon Black Endpoint Standard and Expel Lab.\n\n![Screen Shot 2021-03-30 at 7.50.15\nAM.png](https://support.expel.io/hc/article_attachments/6760446170387/uuid-b22bd4b9-dbab-a5dd-0c3a-4fdcb269c622.png)\n\n * For Server address type the URL for the VMware Carbon Black Endpoint Standard server, including the port.\n\n * For SIEM key, type the SIEM API Key generated in Step 2.\n\n * For API connect, type API ID generated in Step 2.\n\n * For SIEM connect, type the SIEM API ID generated in Step 2.\n\n * For API key type the API generated in Step 2.\n\n * Username and Password fields are optional and can be left blank.\n\n 8. 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"} \ No newline at end of file diff --git a/article_360063148473.json b/article_360063148473.json new file mode 100644 index 0000000000000000000000000000000000000000..82d6e34714fea4fcdab2344e2f344c94eacf5000 --- /dev/null +++ b/article_360063148473.json @@ -0,0 +1 @@ +{"title": "CylancePROTECT AV setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/360063148473-CylancePROTECT-AV-setup-for-Workbench", "date": "2021-02-17T20:44:54Z", "contents": "This article explains how to connect CylancePROTECT AV 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\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 in to the CylancePROTECT AV Console as an administrator.\n\n 2. Click Settings > Users.\n\n 3. Add a user for Expel with a Read-Only role.\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. Log in to the CylancePROTECT AV Console as an administrator. Only administrators can create an application integration.\n\n 2. Select Settings > Integrations.\n\n 3. Click Add Application.\n\n 4. Type an Application Name. This must be unique within your organization.\n\n 5. Select Threats READ, Devices READ, and Users READ privileges.\n\n 6. Click Save. The application credentials appears.\n\n 7. Copy the Tenant ID located in the Integrations page and save for onboarding in Workbench.\n\n 8. Note your Cylance Service Endpoint. This can be found by mapping your CylancePROTECT AV in the table below. For example: `https://protect-euc1.cylance.com is https://protectapi-euc1.cylance.com`\n\n**URL**\n\n|\n\n**Service Endpoint** \n \n---|--- \n \nhttps://protect-apne1.cylance.com\n\n|\n\nhttps://protectapi-apne1.cylance.com \n \nhttps://protect-euc1.cylance.com\n\n|\n\nhttps://protectapi-euc1.cylance.com \n \nhttps://protect-au.cylance.com\n\n|\n\nhttps://protectapi-au.cylance.com \n \nhttps://protect-sae1.cylance.com\n\n|\n\nhttps://protectapi-sae1.cylance.com \n \nhttps://protect.us.cylance.com\n\n|\n\nhttps://protectapi.us.cylance.com \n \nhttps://protect.cylance.com\n\n|\n\nhttps://protectapi.cylance.com \n \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, 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 CylancePROTECT AV.\n\n 5. For Name type the hostname of the CylancePROTECT AV device.\n\n![Screen Shot 2021-03-05 at 10.27.48\nAM.png](https://support.expel.io/hc/article_attachments/13874929229971/uuid-c794f14d-6a6c-ad11-9ad1-066a77084f8a.png)\n\n * Location type the geographic location of the appliance.\n\n * Tenant ID type the Tenant ID generated in Step 2.\n\n * Application ID type the Application ID generated in Step 2.\n\n * Application secret type the application secret generated in Step 2.\n\n * Service Endpoint type your correct Service Endpoint from the table 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"} \ No newline at end of file diff --git a/article_360063148513.json b/article_360063148513.json new file mode 100644 index 0000000000000000000000000000000000000000..c890aaad4976d7cac0454b364e3346b904b20767 --- /dev/null +++ b/article_360063148513.json @@ -0,0 +1 @@ +{"title": "Deploying the Expel Assembler On VMWare", "url": "https://support.expel.io/hc/en-us/articles/360063148513-Deploying-the-Expel-Assembler-On-VMWare", "date": "2021-02-17T20:44:57Z", "contents": "This article describes how to deploy the Expel Assembler on VMWare. For more\ninformation on the general Assembler provisioning process, see How to\nprovision Expel Assembler.\n\n#### In this article\n\n * Deploy the Assembler virtual machine in your network\n\n#### Deploy the Assembler virtual machine in your network\n\nImport the file you downloaded from the Expel Workbench into your VMWare\nenvironment using your VMWare admin tools. The following instructions assume\nyou are using the VMWare ESXi web interface, but you’re free to use another\ntool.\n\n 1. Right+click the file you downloaded from Workbench and click Extract All.\n\n 2. Open VMWare.\n\n 3. Select Virtual Machines in the Navigator panel on the left.\n\n 4. Click the Create / Register VM button.\n\n 5. Click Deploy a Virtual Machine from an OVF or OVA file, then click Next.\n\n 6. Give the virtual machine a name, select the file you downloaded, then click Next.\n\n 7. Select the datastore to use for the virtual machine, then click Next. VMWare extracts the OVA file, which can take a few minutes.\n\n 8. Select your preferred network method and provisioning. Use the defaults unless you have a reason to change them. Click Next.\n\n 9. Review the settings, then click Finish. The OVA file uploads to the ESXi server, which can take a few minutes.\n\n 10. Select the newly imported virtual machine for the Assembler.\n\n 11. Click Console to open the console of the Assembler.\n\nGo back to How to provision Expel Assembler and continue with Activate the\nAssembler through the virtual machine console.\n\n"} \ No newline at end of file diff --git a/article_360063148573.json b/article_360063148573.json new file mode 100644 index 0000000000000000000000000000000000000000..b22d2f3b517e708260fdea9d1e507e83841269df --- /dev/null +++ b/article_360063148573.json @@ -0,0 +1 @@ +{"title": "Deploying the Expel Assembler on Hyper-V", "url": "https://support.expel.io/hc/en-us/articles/360063148573-Deploying-the-Expel-Assembler-on-Hyper-V", "date": "2021-02-17T20:45:03Z", "contents": "This article describes how to deploy the Expel Assembler on Hyper-V. For more\ninformation on the general Assembler provisioning process, see How to\nprovision Expel Assembler.\n\n### Note\n\nYour actual procedure may be slightly different based on your version of\nMicrosoft Windows.\n\n#### In this article\n\n * Deploy the Assembler virtual machine in your network\n\n#### Deploy the Assembler virtual machine in your network\n\n 1. Right+click the downloaded file to open the context menu and click Extract All.\n\n 2. Run the Hyper-V Manager from the Start menu.\n\n 3. From the Action menu, click Import Virtual Machine.\n\n 4. In the Locate Folder step, select the expel-assembler folder that you extracted.\n\n 5. Select the expel-assembler virtual machine.\n\n 6. On the Choose Import Type step, select Copy the virtual machine.\n\n 7. Select a destination. Accept the defaults if you don’t know where to put it.\n\n 8. Select storage folders. Accept the defaults if you’re not sure what to do.\n\n 9. Click Finish.\n\n 10. In the Hyper-V Manager, select the expel-assembler virtual machine.\n\n 11. Click Start to power on the virtual machine.\n\n 12. Click Connect to access the console of the virtual machine.\n\nGo back to How to provision Expel Assembler and continue with Activate the\nAssembler through the virtual machine console.\n\n"} \ No newline at end of file diff --git a/article_4402028026131.json b/article_4402028026131.json new file mode 100644 index 0000000000000000000000000000000000000000..8fc86df661917b3db04068168ce02ee177037771 --- /dev/null +++ b/article_4402028026131.json @@ -0,0 +1 @@ +{"title": "Wazuh on-prem setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/4402028026131-Wazuh-on-prem-setup-for-Workbench", "date": "2021-06-08T19:22:51Z", "contents": "By following these steps, you create a user account for Expel which keeps\nExpel activity separate from other activity on the Wazuh console.\n\n### Note\n\nThis guide is for on-premises installations of Wazuh. For cloud installations,\nsee the Wazuh cloud article.\n\n#### In this article\n\n * Step 1: Create an account in Elasticsearch\n\n * Step 2: Configure the technology in Workbench\n\n## Step 1: Create an account in Elasticsearch\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. Open the Elasticsearch console and select Stack Management from the Management menu.\n\n 2. Select Users and click Create user.\n\n * For Username type expel_svc.\n\n * Set the Password.\n\n * For Full name type Expel Service Account.\n\n * For Email type soc+@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 * For Roles select kibana_admin.\n\n 3. Click Create user.\n\n### Note\n\nNote the Elasticsearch server address and port number (the default port is\n9200) 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. In a new browser tab, login to https://workbench.expel.io/settings/security-devices?setupIntegration=wazuh. You may be asked to log into Workbench.\n\n 2. Fill in the form like this:\n\n![mceclip3.png](https://support.expel.io/hc/article_attachments/13874984727699/uuid-0de67f0a-08fd-a066-2bbe-2df97e0b1162.png)\n\n * For Where is your device? select On-prem.\n\n * For Assembler select the assembler you want to route the Wazuh traffic through.\n\n * For Name and Location type a name and location that are meaningful to you.\n\n * For Username and Password type the username and password created in Step 1.\n\n * For Server address type the server address with the port number from above.\n\n * For Is this a Wazuh cloud instance? select Yes or No, depending on whether you're onboarding a Wazuh-hosted 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"} \ No newline at end of file diff --git a/article_4402737067027.json b/article_4402737067027.json new file mode 100644 index 0000000000000000000000000000000000000000..e1bffeafcbba61c2e9b25a32d6e4b8dd92211f6d --- /dev/null +++ b/article_4402737067027.json @@ -0,0 +1 @@ +{"title": "PagerDuty integration", "url": "https://support.expel.io/hc/en-us/articles/4402737067027-PagerDuty-integration", "date": "2021-06-24T14:07:53Z", "contents": "This article explains how to integrate PagerDuty in Workbench.\n\n## Step 1: Set up PagerDuty integration in Workbench\n\n 1. From the main navigation bar, click Organization Settings.\n\n![PagerDuty_Step1_1.png](https://support.expel.io/hc/article_attachments/16562330152851/uuid-0d604306-56a7-adc7-54f0-42311a04ae1e.png)\n\n 2. Click your organization name.\n\n![PagerDuty_Step1_2.png](https://support.expel.io/hc/article_attachments/16562330272531/uuid-5045a8e8-4706-3fb1-eb94-2860b15ffb3d.png)\n\n 3. Open the Integrations tab.\n\n![PagerDuty_Step1_3.png](https://support.expel.io/hc/article_attachments/16562330355731/uuid-3e63a055-11fc-5eef-95bf-9e51343af815.png)\n\n 4. Scroll down to PagerDuty and click Open PagerDuty to begin integration. (If you don't see it, click Add a PagerDuty destination and the link appears.)\n\n![PagerDuty_Step1_4.png](https://support.expel.io/hc/article_attachments/15714350453267/uuid-d76ed8f2-f5ae-52a2-dd2c-74c6a0d35a84.png)\n\n 5. A new tab opens in your browser. Log in with your PagerDuty credentials.\n\n 6. In PagerDuty, select which service you want to add the integration to or create a new integration, then click Connect.\n\n### Note\n\nYou can only select 1 service.\n\nYou're redirected to Workbench. If the integration is successful, you see a\nmessage.\n\nThe PagerDuty connection information also appears.\n\n## Step 2: Configure your notifications in Workbench\n\n 1. Open the Notifications tab.\n\n![PagerDuty_Step2_1.png](https://support.expel.io/hc/article_attachments/15714350530451/uuid-07058a8e-e410-eedb-b571-d1726e8c1950.png)\n\n 2. Find the When an incident is created notification and click the Pencil icon.\n\n![PagerDuty_Step2_2.png](https://support.expel.io/hc/article_attachments/15714335156243/uuid-01d3579e-7b6e-880f-f196-e35e8edb909c.png)\n\n 3. Under Notify via, click Add another.\n\n![PagerDuty_Step2_3.png](https://support.expel.io/hc/article_attachments/15714350716307/uuid-\nfabed466-6cbb-d1ad-dbd3-24a0c36fac8e.png)\n\n 4. Click Select destination and select **PagerDuty** from the list.\n\n![PagerDuty_Step2_4.png](https://support.expel.io/hc/article_attachments/15714350813715/uuid-0690a517-5547-7309-86e5-8aaccb24bc91.png)\n\n 5. Click Save.\n\n![PagerDuty_Step2_5.png](https://support.expel.io/hc/article_attachments/15714335430163/uuid-9c2f7698-23ec-96a9-e770-300e9848c817.png)\n\n 6. (Optional) You can add PagerDuty to other notifications on this tab.\n\n## Step 3: Test your connection in Workbench\n\n 1. Open the Integrations tab, scroll down to PagerDuty and click the Test connection link.\n\n![PagerDuty_Step3_1.png](https://support.expel.io/hc/article_attachments/15714351002899/uuid-\nce82125c-c9d1-b68c-0d9f-b9c888c2b084.png)\n\n 2. The test creates and closes an incident in PagerDuty. Last tested shows the test date and a status message.\n\n![PagerDuty_Step3_2.png](https://support.expel.io/hc/article_attachments/15714335676563/uuid-96744519-df20-9e80-5354-68379bfabe1c.png)\n\n 3. In PagerDuty, navigate to your Incidents page. In the Activity for the Past 7 Days section, you see the test connection. It has a unique ID appended to the title. You see 2 rows for the test event, 1 for the triggered event and 1 for the resolved activity. That’s it!\n\n## Disconnect the PagerDuty integration from Workbench\n\nYou can disconnect the PagerDuty integration from Workbench.\n\n 1. In Workbench go to Organization Settings > My Organization > Integrations.\n\n 2. Scroll to PagerDuty. Click the Pencil icon.\n\n 3. Click Disconnect and delete. You no longer receive alert notifications from Expel through PagerDuty.\n\n## Frequently asked questions\n\n**Can Workbench send alerts to more than one PagerDuty service?**\n\nNot currently. As of now, alerts can only be configured to a single PagerDuty\nservice.\n\n**Do PagerDuty incidents resolve after the security incident is complete in\nWorkbench?**\n\nNo. At this time, the PagerDuty incident must be resolved from PagerDuty.\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"} \ No newline at end of file diff --git a/article_4404776915987.json b/article_4404776915987.json new file mode 100644 index 0000000000000000000000000000000000000000..00855cbfc9e1caacc5bbd446e0ed4060a4c211e5 --- /dev/null +++ b/article_4404776915987.json @@ -0,0 +1 @@ +{"title": "Varonis setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/4404776915987-Varonis-setup-for-Workbench", "date": "2021-08-04T21:02:36Z", "contents": "Connecting the Expel Workbench to a Varonis installation requires a Varonis\ndomain user account with access to DatAlerts. The first step is to configure\nthe account with the proper roles. After that's complete, you can connect\nVaronis to Workbench and test the connection.\n\n#### In this article\n\n * Step 1: Create and configure Varonis domain user account\n\n * Step 2: Configure the technology in Workbench\n\n * Step 3: Edit the device to add console access\n\n#### Step 1: Create and configure Varonis domain user account\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. In Varonis, create a domain user account. Make a note of the username and password on the account for later reference.\n\n 2. Navigate to the Varonis management console > Configuration > Security.\n\n 3. Assign the domain user the following roles:\n\n * Alerts View User\n\n * Directory Services Trends View User\n\n * File System Trends View User\n\n * Log View User\n\n * Reports View User\n\n * User\n\n * Web UI User\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 top of the page, click Add Security Device.\n\n 4. Search for and select Varonis.\n\n 5. Select an Assembler from the list. Select the assembler you set up in Getting connected to Expel Workbench.\n\n![Varinos_Dat_alert_connect_screen.png](https://support.expel.io/hc/article_attachments/13874926344211/uuid-b1cf5b18-1a13-19a8-b05f-deea6cf7ded7.png)\n\n * Type Assembler Name and Location. For example: Varonis and Expel Lab.\n\n * For API username and API password type the credentials created in Step 1.\n\n * For URL type the Varonis instance URL.\n\n * (Optional) For Verify tls type y or n.\n\n### Note\n\nType y to verify your server's TLS certificates.\n\n 6. Click Save.\n\n 7. You can set up console access now or 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"} \ No newline at end of file diff --git a/article_4405230350611.json b/article_4405230350611.json new file mode 100644 index 0000000000000000000000000000000000000000..f7dccf1d9079c8b89ad850feac22089652f80802 --- /dev/null +++ b/article_4405230350611.json @@ -0,0 +1 @@ +{"title": "OpsGenie setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/4405230350611-OpsGenie-setup-for-Workbench", "date": "2021-08-13T15:30:34Z", "contents": "This article explains how to connect OpsGenie to Workbench.\n\n#### In this article\n\nStep 1: Set up integration in OpsGenie\n\nStep 2: Set up integration in Workbench\n\nStep 3: Set up notifications in Workbench\n\nDisconnect OpsGenie from Workbench\n\n## Step 1: Set up integration in OpsGenie\n\n 1. In OpsGenie, navigate to Teams and select your team.\n\n 2. Click Integrations and then select your team's API. The API settings appear.\n\n 3. Copy the API key.\n\n## Step 2: Set up integration in Workbench\n\n 1. In a new browser tab, login to https://workbench.expel.io.\n\n 2. Click Organization Settings > My Organizations.\n\n 3. On the My Organization page, select the Organization to connect.\n\n 4. Click the Integrations tab.\n\n 5. Scroll down to OpsGenie and click Configure this integration.\n\n 6. Paste in the API key copied in Step 1 and click Add.\n\n## Step 3: Set up notifications 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. On the Organization Settings page, click the Notifications tab.\n\n![Settings_My_Org_Org_settings_Notifications_Example.png](https://support.expel.io/hc/article_attachments/15339884710803/uuid-9948ef60-1488-058f-ecbc-f10c39c3f3f7.png)\n\n 2. Click \\+ Add Notifications. Edit Notifications popup appears.\n\n 3. Select the options to sign up for alerts as needed.\n\n 4. Click Save.\n\nAfter triggering the event, an alert appears in OpsGenie under the Alerts\nsection.\n\n### Disconnect OpsGenie from Workbench\n\n 1. Go to Organization Settings > My Organization > > Integrations.\n\n 2. Scroll down to OpsGenie. Click the pencil next to OpsGenie.\n\n 3. Click Disconnect and delete.\n\nThe integration of the Workbench and OpsGenie is deleted.\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\nOps Genie, Opsgenie\n\n"} \ No newline at end of file diff --git a/article_4405567540115.json b/article_4405567540115.json new file mode 100644 index 0000000000000000000000000000000000000000..131f649abf1ed3d6def300a9eaa30af8ac440757 --- /dev/null +++ b/article_4405567540115.json @@ -0,0 +1 @@ +{"title": "User notifications setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/4405567540115-User-notifications-setup-for-Workbench", "date": "2021-08-19T17:56:26Z", "contents": "Workbench sends alerts and other messages to your organization. You watch\nthese channels, like Slack, but you might miss an important message. So, you\ncan set up notifications to be sent directly to your email address. These are\ncalled user notifications.\n\nYou create user notifications. Select the event to watch, like incidents or\ninvestigations. Then, select an action, like opened or closed. Workbench sends\nthe notifications to your email address.\n\n## How do I set up my notifications?\n\nBy default, Workbench gives you the most asked for notifications. Where it\ngoes from there is up to you.\n\nUse the User Notifications checklist to make a list of the notifications\nyou're interested in receiving. You can refer to this during the setup\nprocess.\n\nThe setup process is pretty simple. If you've ever created a rule in an email\nprogram, then this looks familiar:\n\n * First, select the event to watch, like incidents or investigations. Let's say Investigation.\n\n * Second, select an action, like opened or closed. (Investigation is closed.)\n\nThat's all there is to it! Workbench sends the selected notifications to you\nthrough email as events occur.\n\nYou can view, add, edit, and delete your notifications. Admins can do the same\nfor the users in their organization. Click below to jump to the task at hand:\n\n * Viewing your notifications\n\n * Viewing user notifications for your organization\n\n * Adding notifications\n\n * Editing notifications\n\n * Deleting notifications\n\n## Viewing your notifications\n\nTo view your notifications:\n\n 1. In a new browser tab, login to https://workbench.expel.io.\n\n 2. From any screen, click the green square with your initials in the top right corner.\n\n 3. Select Manage account.\n\n 4. Your notifications are in the Email Notifications tab.\n\n## Viewing user notifications for your organization\n\nAdmins can view and work with the user notification settings for all the users\nin their organization. This can be useful for onboarding to make sure the new\nuser has the appropriate notifications.\n\n### Note\n\nYou must be an Org Admin to make changes in this area.\n\nTo view user level notifications for the personnel in your organization:\n\n 1. In a new browser tab, login to https://workbench.expel.io.\n\n 2. Click Organization Settings > Users.\n\n 3. Find a user, then click the down arrow on the right side of that row.\n\n 4. Click View and edit. The user's notifications are in the Email notifications section.\n\n## Adding notifications\n\nTo add notifications:\n\n 1. When viewing yourself or (if you're an admin) when viewing another user, click \\+ Add Notification.\n\n![mceclip5.png](https://support.expel.io/hc/article_attachments/15848692703123/uuid-9cfc7613-a026-7819-2003-4dd9f1dae171.png)\n\n 2. A blank notification appears.\n\n![mceclip6.png](https://support.expel.io/hc/article_attachments/15848692779923/uuid-8b9c6610-e3d4-e9a0-05ba-f5e1ce78a8bf.png)\n\n 3. Select an event.\n\n![mceclip7.png](https://support.expel.io/hc/article_attachments/15848692919443/uuid-63a6c3bc-f908-c214-4159-422a8b1a87f2.png)\n\n 4. Select an action for that event.\n\n![mceclip8.png](https://support.expel.io/hc/article_attachments/15848736573075/uuid-\ncc3aaa15-2881-566a-de6d-e0e894778390.png)\n\n 5. Click Save.\n\n 6. The notification appears on the Email Notifications tab.\n\n## Editing notifications\n\nTo edit notifications:\n\n 1. Hover your mouse pointer over the notification and click the pencil. The notification appears.\n\n 2. Change the event, the action, the condition and/or the specific property as needed.\n\n 3. Click Save.\n\nYour edited notification appears in the Email Notifications tab.\n\n## Deleting notifications\n\nTo delete notifications:\n\n 1. Hover your mouse pointer over the notification and click the trash can.\n\n 2. Click Delete.\n\nThe deleted notification no longer appears in the Email Notifications tab.\n\n"} \ No newline at end of file diff --git a/article_4405590209683.json b/article_4405590209683.json new file mode 100644 index 0000000000000000000000000000000000000000..45f456c2faa30943f67620b475f190d5c1e5bec1 --- /dev/null +++ b/article_4405590209683.json @@ -0,0 +1 @@ +{"title": "User notifications default list", "url": "https://support.expel.io/hc/en-us/articles/4405590209683-User-notifications-default-list", "date": "2021-08-20T02:06:47Z", "contents": "These user notifications are provided by default:\n\n 1. When an incident is created.\n\n 2. When an incident is closed.\n\n 3. When an incident is reopened.\n\n 4. When an investigation is created.\n\n 5. When an investigation is assigned to my org.\n\n 6. When an investigation is closed.\n\n 7. When an investigative action is assigned to me.\n\n 8. When an investigative action is assigned to my org.\n\n 9. When a notify action is assigned to my org.\n\n 10. When a verify action is assigned to me.\n\n 11. When a verify action is assigned to my org.\n\n 12. When a remediation action is assigned to me.\n\n 13. When a remediation action is assigned to my org.\n\n 14. When a remediation action is automated.\n\n 15. When a comment is created.\n\n 16. When an assembler has a health status change.\n\nFor more information about user notifications, see User role rights in Expel\nWorkbench.\n\n"} \ No newline at end of file diff --git a/article_4405597050899.json b/article_4405597050899.json new file mode 100644 index 0000000000000000000000000000000000000000..fbd2f0afa2b27ced79f974054abfbbe85f859a89 --- /dev/null +++ b/article_4405597050899.json @@ -0,0 +1 @@ +{"title": "User notifications checklist", "url": "https://support.expel.io/hc/en-us/articles/4405597050899-User-notifications-checklist", "date": "2021-08-20T02:14:02Z", "contents": "This table contains all the possible event and action combinations for user\nnotifications. You can print this page and use it as a checklist to help you\nselect notifications and confirm that you entered all the needed notifications\nin Workbench.\n\n**Notify me for this event...**\n\n|\n\n**and this action** \n \n---|--- \n \nIncident\n\n|\n\nis created \n \nIncident\n\n|\n\nis closed \n \nIncident\n\n|\n\nis closed \n \nIncident\n\n|\n\nis downgraded \n \nIncident\n\n|\n\nis assigned to my org \n \nInvestigation\n\n|\n\nis created \n \nInvestigation\n\n|\n\nis closed \n \nInvestigation\n\n|\n\nhas an alert added \n \nInvestigation\n\n|\n\nis assigned to my org \n \nComment\n\n|\n\nis created \n \nResilience recommendation\n\n|\n\nis created \n \nResilience recommendation\n\n|\n\nis updated \n \nInvestigative action\n\n|\n\nis assigned to my org \n \nInvestigative action\n\n|\n\nis assigned to me \n \nRemediation action\n\n|\n\nis assigned to my org \n \nRemediation action\n\n|\n\nis completed \n \nRemediation action\n\n|\n\nis automated \n \nRemediation action\n\n|\n\nis assigned to me \n \nSecurity device\n\n|\n\nhas a health status change \n \nAssembler\n\n|\n\nhas a health status change \n \nIncident findings\n\n|\n\nare completed \n \nVerify action\n\n|\n\nis assigned to my org \n \nVerify action\n\n|\n\nis assigned to me \n \nNotify action\n\n|\n\nis assigned to my org \n \nUser account\n\n|\n\nis activated \n \nFor more information about user notifications, see the User notifications\narticle.\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"} \ No newline at end of file diff --git a/article_4406016918547.json b/article_4406016918547.json new file mode 100644 index 0000000000000000000000000000000000000000..73b79e854b08b1d4fc4f84a23f2cb4737661271d --- /dev/null +++ b/article_4406016918547.json @@ -0,0 +1 @@ +{"title": "Palo Alto Networks SaaS Security (formerly Prisma SaaS) setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/4406016918547-Palo-Alto-Networks-SaaS-Security-formerly-Prisma-SaaS-setup-for-Workbench", "date": "2021-08-27T19:38:21Z", "contents": "This article explains how to connect Palo Alto Networks SaaS Security to\nWorkbench.\n\n#### In this article\n\n * Step 1: Generate API credentials\n\n * Step 2: Configure the technology in Workbench\n\n * Step 3: Edit the device to add console access\n\n## Step 1: Generate API credentials\n\nThis procedure creates an authentication that allows Workbench to access the\nPalo Alto Networks SaaS Security API.\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. In Palo Alto Networks SaaS Security API, select Settings > External Service.\n\n 2. Click Add Client App.\n\n 3. Type Expel for the API Client Name.\n\n 4. Authorize the Expel API client for these Scopes:\n\n * Log access\n\n * Incident management\n\n * Quarantine management\n\n 5. Click Save.\n\n 6. SaaS Security API shows a Client Secret. Write down the Client Secret and save it.\n\n### Note\n\nYou must have the Client Secret for the next step.\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, 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 right of the page, click Add Security Device.\n\n 4. Search for and select Palo Alto Networks SaaS Security.\n\n 5. For SIEM, select Expel Cloud.\n\n![mceclip2.png](https://support.expel.io/hc/article_attachments/13874873865875/uuid-54f79552-243d-c172-6f70-8d17d0de3ef0.png)\n\n * Type the Server Name and Location.\n\n * For API ID, type Expel.\n\n * For API secret, type the secret generated in Step 1.\n\n * Select the SaaS Security server from the list.\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"} \ No newline at end of file diff --git a/article_4406380340755.json b/article_4406380340755.json new file mode 100644 index 0000000000000000000000000000000000000000..536eac6f58134fbb1c813b02edba604ad9e624cc --- /dev/null +++ b/article_4406380340755.json @@ -0,0 +1 @@ +{"title": "Netskope setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/4406380340755-Netskope-setup-for-Workbench", "date": "2021-09-03T17:19:08Z", "contents": "This article explains how to connect Netskope to Workbench.\n\n#### In this article\n\n * Step 1: Generate API Credentials\n\n * Step 2: Configure the technology in Workbench\n\n## Step 1: Generate API Credentials\n\nNetskope REST APIs use an auth token to make authorized calls to the API.\nExpel uses Netskope REST APIs to access resources through URI paths.\n\n### Note\n\nBefore you begin, reach out to Netskope to enable REST API v2.\n\n 1. In the Netskope UI, navigate to Settings > Tools > Rest API v2.\n\n 2. On the REST API v2 page, click New Token.\n\n 3. Type Expel for token name, select a token expiration time that fits in your company's policy, and then click Add Endpoint to select the API endpoints to use with the token.\n\n 4. Specify READ privileges for API endpoint api/v2/events/data/alert.\n\n 5. Click Save.\n\n 6. A confirmation opens showing whether the token creation was a success. If so, click Copy Token to save it for later use.\n\n### Note\n\nThe only opportunity to copy the token is immediately after you create it.\n\n 7. Click OK.\n\n 8. Confirm that the area at the top of the screen referencing REST API Status shows that it is enabled.\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, log into https://workbench.expel.io/settings/security-devices?setupIntegration=netskope.\n\n 2. Complete all fields using the credentials and information you collected in Step 1.\n\n![mceclip1.png](https://support.expel.io/hc/article_attachments/13874988010387/uuid-3a3268fd-c72d-afa7-ae13-7af7df59da33.png)\n\n * For Name type the host name of the device.\n\n * For Location type the geographic location of the appliance.\n\n * For Server type your Netskope URL.\n\n * For Token type the API generated 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"} \ No newline at end of file diff --git a/article_4406389054611.json b/article_4406389054611.json new file mode 100644 index 0000000000000000000000000000000000000000..4e09068ec1bb746705759bab74cf5dca5fd3ccb4 --- /dev/null +++ b/article_4406389054611.json @@ -0,0 +1 @@ +{"title": "Activate your Workbench account", "url": "https://support.expel.io/hc/en-us/articles/4406389054611-Activate-your-Workbench-account", "date": "2021-09-03T22:03:05Z", "contents": "While your Expel Workbench administrator can set up your account, only you can\nactivate it. After your account is ready, Workbench sends you an activation\ninvite.\n\n### Tip\n\nInvitations expire, so don't delay!\n\n## Before you start\n\nInstall an authenticator application, such as Duo or Google Authenticator, on\nyour smartphone or other portable device with a built-in camera. You must set\nup your account with MFA.\n\n## Create your Workbench account\n\nTo activate a Workbench account, take these steps:\n\n 1. Check your email for an activation invite from Workbench. If you didn't receive the invite, or it expired, contact your Workbench administrator.\n\n 2. Open your invite and click Set Up My Account.\n\n 3. Create a password by following the on-screen instructions, then click Next.\n\n### Note\n\nYour email address is your Workbench username.\n\n 4. Verify your account by following the on-screen instructions, then click Next.\n\n 5. Log into Workbench using your email address and the password you just created.\n\n![mceclip4.png](https://support.expel.io/hc/article_attachments/6760319649939/uuid-\nca1be0af-456a-8e05-e1e9-5ee2ac240bb8.png)\n\nWorkbench opens.\n\n"} \ No newline at end of file diff --git a/article_4406542775059.json b/article_4406542775059.json new file mode 100644 index 0000000000000000000000000000000000000000..819552ff0c831d1f2ad6b24316faff2c71401fa8 --- /dev/null +++ b/article_4406542775059.json @@ -0,0 +1 @@ +{"title": "Datadog setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/4406542775059-Datadog-setup-for-Workbench", "date": "2021-09-07T17:27:07Z", "contents": "This article explains how to connect your Datadog device to Workbench.\n\n#### In this article\n\n * Step 1: Create a service account and API credentials\n\n * Step 2: Configure the technology in Workbench\n\n * Step 3: Edit the device to add console access\n\n## Step 1: Create a service account and API credentials\n\nYou must have the System Administrator role on Datadog to add a service\naccount.\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### Caution\n\nThink carefully about the data you enter. After you create a service account,\nyou can't make changes. You have to delete it and start over.\n\n 1. Log in to the Datadog console.\n\n 2. Navigate to Organization Settings > API Keys.\n\n 3. Select \\+ New Key.\n\n 4. Name the key, then click Create Key.\n\n 5. Copy and paste or write down the API key for later use.\n\n 6. Navigate to Organization Settings > Service Accounts.\n\n 7. Select \\+ New Service Account.\n\n 8. Type the following details for the service account:\n\n * Name: Expel API Integration\n\n * Email: expel_analyst@expel.io\n\n * Role: `Datadog Read Only Role`\n\n 9. Click Create Service Account.\n\n 10. Select the created service account. A popup appears.\n\n 11. On the service account popup, select \\+ New Key.\n\n 12. Copy+paste or write down the Application 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. In a new browser tab, go to https://workbench.expel.io/settings/security-devices?setupIntegration=datadog.\n\n![mceclip16.png](https://support.expel.io/hc/article_attachments/13874990665363/uuid-2c57e0f6-98c5-218b-e846-0da030202346.png)\n\n 2. Complete these fields using the credentials and information you collected in Step 1:\n\n * Name: the host name of the device.\n\n * Location: the geographic location of the appliance.\n\n * Select your site.\n\n * API key: the API key generated in Step 1.\n\n * Application key: the Application key generated 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 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"} \ No newline at end of file diff --git a/article_4406597697555.json b/article_4406597697555.json new file mode 100644 index 0000000000000000000000000000000000000000..d6060f64c6e8c990a7865f294314e02d690cc725 --- /dev/null +++ b/article_4406597697555.json @@ -0,0 +1 @@ +{"title": "Wazuh​ OpenDistro for Elasticsearch setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/4406597697555-Wazuh-OpenDistro-for-Elasticsearch-setup-for-Workbench", "date": "2021-09-08T18:54:46Z", "contents": "This article helps you connect your Wazuh​ OpenDistro for Elasticsearch\ninstance to the Expel Workbench. You create a user account for Workbench, give\nthe account the necessary level of access, activate archiving, and then\nconnect the technology in Workbench.\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\nTo integrate the technology with Workbench, we need to create secure\ncredentials to the API.\n\n#### In this article\n\n * Step 1: Create a new user role\n\n * Step 2: Create a user account with the new role\n\n * Step 3: Map the role to the Wazuh module in Elasticsearch\n\n * Step 4: Enable Wazuh archives logging\n\n * Step 5: Create Kibana index pattern\n\n * Step 6: Connect your technology to Expel Workbench\n\n## Step 1: Create a new user role\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. Go to the Stack Management section of your Elasticsearch.\n\n 2. Select Roles and then click Create role.\n\n### Note\n\nDepending on the Elastic version number and/or the Wazuh installation process,\nRoles can also be found under Kibana > Roles.\n\n 3. Give the new role these options:\n\n * Cluster Permissions: cluster_all. If you can’t find cluster_all, all works as well.\n\n * Index Permissions: add the index subheading an asterisk(*), with index permissions — search, get, read.\n\n * Tenant permissions: global_tenant with Read only.\n\n 4. Click Save.\n\n## Step 2: Create a user account with the new role\n\nThis step varies depending upon your Elastic setup. If you can see the Users\ntab, follow these steps:\n\n 1. Go to the Users tab and click Create User.\n\n 2. Create a new internal user.\n\n 3. Select the newly created internal user. The Edit User page appears.\n\n 4. Select the newly created read-only role for this user.\n\nIf you can't see the Users tab, follow these steps:\n\n 1. Go to the Roles tab and select Create Internal User under Mapped users.\n\n 2. Create a new internal user.\n\n 3. Go back to the Roles tab and select Map Users.\n\n 4. Select the newly created user.\n\n## Step 3: Map the role to the Wazuh module in Elasticsearch\n\n 1. Go to Wazuh > Security > Roles mapping.\n\n 2. Create a new Role mapping with the following options:\n\n * Roles: select the newly created read-only role from the list.\n\n * Internal Users: select the newly created user from the list.\n\n 3. In a new browser tab, open the Elasticsearch API address.\n\n### Tip\n\nThis is usually the server with the ES API port (9200 is default), such as:\nhttps://es-server-address.com:9200/.\n\n 4. After an HTTP Basic Authentication window appears, type the credentials for the newly created user.\n\n 5. If you receive a JSON object from the ES API, the mapping works. Here is an example:\n\n![mceclip4.png](https://support.expel.io/hc/article_attachments/6760491897491/uuid-39e9a126-297d-8479-1325-982621d521e1.png)\n\n 6. If you don't receive a JSON object, contact your customer success engineer, or email devicehealth@expel.io for help.\n\n## Step 4: Enable Wazuh archives logging\n\nTo enable Workbench to log events from wazuh-archives-*, take these steps:\n\n 1. Open the file /var/ossec/etc/ossec.conf in your Wazuh manager endpoint and toggle the logall_json field to yes as shown below.\n\n![mceclip5.png](https://support.expel.io/hc/article_attachments/6760463591699/uuid-7a0fe648-2b4c-2be9-9649-c510dc83fd0b.png)\n\n 2. Open the file /etc/filebeat/wazuh-template.json in your Wazuh manager endpoint and append the string “wazuh-archives-4.x-*” to the index_patterns list as shown below.\n\n![mceclip6.png](https://support.expel.io/hc/article_attachments/6760443903763/uuid-c87d648d-b536-aab3-efe4-bc27dc8ebf98.png)\n\n 3. Open the file /etc/filebeat/filebeat.yml in your Wazuh manager endpoint and enable the archives module as shown below.\n\n![mceclip7.png](https://support.expel.io/hc/article_attachments/6760443962899/uuid-8714aeb9-9dfb-822d-f6f3-2f8bc7bd5516.png)\n\n 4. Restart the filebeat service and the Wazuh manager endpoint.\n\n * Systemd:\n\n * systemctl restart filebeat\n\n * systemctl restart wazuh-manager\n\n * SysV init:\n\n * service filebeat restart\n\n * service wazuh-manager restart\n\n 5. Go to Kibana > Discover and change the index to wazuh-archives-*.\n\n 6. Open your Kibana console and check the wazuh-archives-* index.\n\n * If you can see event logs in this index, go to Step 6.\n\n * If you can't see this index, go to Step 5.\n\n## Step 5: Create Kibana index pattern\n\n 1. Go to Kibana > Index Patterns and select Create Index Pattern.\n\n 2. Enter wazuh-archives-* as the pattern name, and click Next step.\n\n### Note\n\nKibana should list a few sources already.\n\n 3. Select @timestamp as the Time Field, then click Create index pattern.\n\n 4. Go to Kibana > Discover and change the index to wazuh-archives-*.\n\n 5. Open your Kibana console and check the wazuh-archives-* index.\n\n * If you can see event logs in this index, go to Step 6.\n\n * If you can't see this index, contact your customer success engineer, or email devicehealth@expel.io for help.\n\n## Step 6: Connect your technology to 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, 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 your technology Wazuh.\n\n 5. Complete all fields using the information you created in Step 2.\n\n![mceclip2.png](https://support.expel.io/hc/article_attachments/6760459899539/uuid-7809d568-1be9-090e-852f-aa7b02e47045.png)\n\n * Name: friendly name for the integration.\n\n * Location: where the Wazuh tech stack is placed within your organization.\n\n * Username: Username created in Step 2.\n\n * Password: Password created in Step 2.\n\n * Server address: type the Wazuh cloud server address with port number.\n\n * Is this a Wazuh cloud Instance?: N/A (Ignore).\n\n 6. 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"} \ No newline at end of file diff --git a/article_4406909457939.json b/article_4406909457939.json new file mode 100644 index 0000000000000000000000000000000000000000..016ad52d960bdbecaf54677d6632cd97c437d41a --- /dev/null +++ b/article_4406909457939.json @@ -0,0 +1 @@ +{"title": "Gmail Report Phishing button set up", "url": "https://support.expel.io/hc/en-us/articles/4406909457939-Gmail-Report-Phishing-button-set-up", "date": "2021-09-14T15:24:16Z", "contents": "#### In this article\n\n 1. Create Google Workspace Addon project\n\n 2. Create Google Workspace Cloud project\n\n 3. Connect Google Workspace Cloud and Addon projects\n\n 4. Install/deploy addon to domain\n\n## Step 1: Create Google Workspace Add on project\n\n 1. Navigate to https://script.google.com/ and login as the domain super admin. Click New project.\n\n![mceclip4.png](https://support.expel.io/hc/article_attachments/6650224554899/uuid-20482be5-1269-e0c8-3147-547f35c94c53.png)\n\n 2. Click Untitled project, rename the project **Report potential phishing** , and then click Rename.\n\n![mceclip5.png](https://support.expel.io/hc/article_attachments/6650250032531/uuid-41308c60-8668-033f-e7e0-e53cc6d3b66f.png)\n\n 3. Click the \\+ sign next to Files and select Script.\n\n![mceclip6.png](https://support.expel.io/hc/article_attachments/6650224682131/uuid-3086b025-a60c-14c5-2fab-3e3de553686b.png)\n\n 4. Type Config as the file name and press Enter. The file list looks like this:\n\n![mceclip7.png](https://support.expel.io/hc/article_attachments/6650233725459/uuid-1c0ee784-4bfb-2271-98f9-e52652cb9e48.png)\n\n 5. Click the Settings icon at the bottom of the navigation bar.\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/6650218209299/uuid-1f834cd2-7783-0c7a-1463-a9ff00b7f4cc.png)\n\n 6. Select the Show \"appscript.json\" manifest file in editor checkbox.\n\n![mceclip10.png](https://support.expel.io/hc/article_attachments/6650218253971/uuid-72fe47e7-20aa-e28a-bee2-cefde1885980.png)\n\n 7. Click the Code Editor icon in the navigation bar.\n\n![mceclip11.png](https://support.expel.io/hc/article_attachments/6650224884627/uuid-c785c5e2-e1ff-6191-026a-fb2e4693caf8.png)\n\nThe appscript.json file appears in the file list like the example below:\n\n![mceclip1.png](https://support.expel.io/hc/article_attachments/6650202508947/uuid-\nce3dba03-4d4c-51c7-408b-56bfe4482651.png)\n\n 8. Using the provided GmailAddOn.zip file, extract, copy, and paste the contents of each file into the corresponding files in the Apps Script editor.\n\n * Before\n\n![mceclip2.png](https://support.expel.io/hc/article_attachments/6650218386963/uuid-\nade0ab1d-f445-f6f5-376d-57ee1e786a29.png)\n\n * After\n\n![mceclip3.png](https://support.expel.io/hc/article_attachments/6650202647571/uuid-2d1e408f-c340-7487-2f5e-95c6476d64a1.png)\n\n 9. After the files are copied into and saved in the Apps Script editor, click Deploy and select New deployment.\n\n![mceclip4.png](https://support.expel.io/hc/article_attachments/6650218557331/uuid-4bbb30f5-7b6d-1a76-6f05-08c7f05ebe60.png)\n\n 10. Click the gear icon next to Select type and select Web app and Add-on.\n\n![mceclip16.png](https://support.expel.io/hc/article_attachments/6650234128659/uuid-7bc403e4-5297-e1ef-3e29-35d85c816574.png)\n\n 11. Type **Report potential phishing** as the New description, select the Anyone within… option under Who has access, and then click Deploy.\n\n![mceclip17.png](https://support.expel.io/hc/article_attachments/6650240732691/uuid-61c194f5-0f5b-c55a-8ca7-daf479d8ed2e.png)\n\n 12. After the deploy is complete, click Copy under the Deployment ID and paste the ID somewhere for use in a later step.\n\n### Note\n\nKeep this tab open. You return to it in a later step\n\n![mceclip18.png](https://support.expel.io/hc/article_attachments/6650240788755/uuid-c59fa582-4151-f9a6-fe1b-2073620eea59.png)\n\n## Step 2: Create Google Workspace Cloud project\n\n 1. Open a new browser tab and go to https://console.cloud.google.com/projectcreate, type **Report potential phishing** as the project name, and then click CREATE.\n\n![mceclip19.png](https://support.expel.io/hc/article_attachments/6650225437331/uuid-360a2c69-2598-d4a6-bfab-\nbcaba013da7b.png)\n\n 2. Click the top left menu icon, select APIs & Services, and then click Enabled APIs & services.\n\n![GmailPhishingButton_Step_2-2.png](https://support.expel.io/hc/article_attachments/7446299699987/uuid-9e93114e-2396-25df-a3de-5acf1cc78ddc.png)\n\n 3. Search for Google Workspace Marketplace SDK.\n\n![mceclip22.png](https://support.expel.io/hc/article_attachments/6650219006739/uuid-05806f52-24cd-3263-fb84-27974b4be55b.png)\n\n 4. Select Google Workspace Marketplace SDK from the search results.\n\n![mceclip23.png](https://support.expel.io/hc/article_attachments/6650253609107/uuid-532d5465-709d-2c2c-9ac2-9322c5447de0.png)\n\n 5. Click ENABLE.\n\n![mceclip24.png](https://support.expel.io/hc/article_attachments/6650225742355/uuid-c9c864df-7fbf-40ef-45f6-318f797e3d1a.png)\n\n 6. Click the App Configuration tab.\n\n![GmailPhishingButton_Step_2-7.png](https://support.expel.io/hc/article_attachments/7446299819667/uuid-697a2742-51e9-dfa1-4568-e8f22537012f.png)\n\n 7. From the App Configuration tab, click The OAuth Consent Screen must be enabled for this project.\n\n![mceclip26.png](https://support.expel.io/hc/article_attachments/6650253781651/uuid-5f36379f-5acb-c492-c606-5a2f92b93eae.png)\n\n 8. On the OAuth consent screen, select Internal and then click CREATE.\n\n![mceclip27.png](https://support.expel.io/hc/article_attachments/6650219295123/uuid-702fa0a6-1fd3-a4cb-\nfc51-6657e18857db.png)\n\n 9. Complete the following fields, leaving the rest empty, and then click SAVE AND CONTINUE.\n\n * App name: Report potential phishing\n\n * User support email: type an email address for the security team/help desk where end users can direct general questions if they have any\n\n * Developer contact information: support@expel.io\n\n 10. On the Edit app registration page, click ADD OR REMOVE SCOPES.\n\n![mceclip28.png](https://support.expel.io/hc/article_attachments/6650234797715/uuid-109f1e82-c9ea-e2f5-2c03-618fe5d96cad.png)\n\n 11. In the Update selected scopes area that opens, copy the following scopes into the Manually add scopes field.\n\n * https://www.googleapis.com/auth/gmail.addons.execute\n\n * https://www.googleapis.com/auth/gmail.addons.current.message.readonly\n\n * https://www.googleapis.com/auth/gmail.send\n\n![mceclip29.png](https://support.expel.io/hc/article_attachments/6650253984659/uuid-75d48b47-f570-ab29-4eaf-87eb3f72626b.png)\n\n 12. Click ADD TO TABLE.\n\n![mceclip30.png](https://support.expel.io/hc/article_attachments/6650251383699/uuid-4c2c35ef-095c-9824-1107-dde9b15246a7.png)\n\n 13. Verify that the 3 scopes are added to the table and are selected and click UPDATE.\n\n![mceclip31.png](https://support.expel.io/hc/article_attachments/6650226207635/uuid-81f36c36-7898-32bf-117f-82e126e747f1.png)\n\n 14. The Edit app registration page appears, showing the 3 scopes. Scroll to the bottom of the page and click SAVE AND CONTINUE.\n\n![mceclip32.png](https://support.expel.io/hc/article_attachments/6650254181011/uuid-\nfd087f30-54fc-103c-7731-dd99ba796e48.png)\n\n## Step 3: Connect Google Workspace Cloud and Add on projects\n\n 1. Go to the App configuration page: https://console.cloud.google.com/apis/api/appsmarket-component.googleapis.com/googleapps_sdk and copy the App ID.\n\n![mceclip33.png](https://support.expel.io/hc/article_attachments/6650254250003/uuid-c0003eb8-f03f-6fda-\nce99-97c3e29caf9e.png)\n\n 2. Go back to the Apps Script tab, or navigate to the Report potential phishing project at https://script.google.com and navigate to Project Settings, then click Change project at the bottom of the page.\n\n![mceclip34.png](https://support.expel.io/hc/article_attachments/6650251681043/uuid-f2da1b85-8e92-5464-788e-24bb77583648.png)\n\n 3. Paste the copied App ID from Step 3.1 into the GCP Project Number field, and then click Set project.\n\n![mceclip35.png](https://support.expel.io/hc/article_attachments/6650226481299/uuid-41c80159-69a3-d592-e1e8-5a32d782f072.png)\n\n 4. Go back to the API & Services cloud console tab https://console.cloud.google.com/apis/api/appsmarket-component.googleapis.com/googleapps_sdk, select the Google Workspace Add-on checkbox and Deploy using Apps Script deployment id, then type the Deployment ID copied from Step 1.\n\n![mceclip37.png](https://support.expel.io/hc/article_attachments/6650242014995/uuid-b41c432a-b3d5-763e-7183-26d874af515c.png)\n\n 5. Scroll to the OAuth Scopes section, click ADD SCOPE, and add the 3 scopes below. After complete, 5 scopes total should be listed, including the 2 defaults:\n\n * https://www.googleapis.com/auth/gmail.addons.execute\n\n * https://www.googleapis.com/auth/gmail.addons.current.message.readonly\n\n * https://www.googleapis.com/auth/gmail.send\n\n![mceclip38.png](https://support.expel.io/hc/article_attachments/6650226625555/uuid-49a27e80-bd89-eaae-e226-b4ccc295ff7a.png)\n\n 6. Select Admin Only Install for Installation Settings, select Private for App Visibility, and then click SAVE.\n\n![mceclip40.png](https://support.expel.io/hc/article_attachments/6650235618451/uuid-8490f1cd-7e7f-9ccf-6893-868d4fff4a04.png)\n\n 7. Scroll to Developer Links and type the following:\n\n * Developer Name: Expel\n\n * Developer Website URL: https://expel.io\n\n * Developer Email: support@expel.io\n\n![mceclip39.png](https://support.expel.io/hc/article_attachments/6650251974035/uuid-b8b2c06e-53da-8889-957d-32d3ccd594ad.png)\n\n 8. Select the Store Listing tab in the middle of the page. Click the down arrow next to English - under App Details.\n\n![GmailPhishingButton_Step_3-8.png](https://support.expel.io/hc/article_attachments/7446277021843/uuid-\naecd9914-ee94-c89e-ad3f-2e049f9c9e45.png)\n\n 9. Fill in the following App Details fields and then click DONE:\n\n * Application Name: Report potential phishing\n\n * Short Description: Report potential phishing emails\n\n * Detailed Description: Utility to help send potential phishing emails for triage\n\n![mceclip42.png](https://support.expel.io/hc/article_attachments/6650252155411/uuid-51577ea3-501f-6860-462e-4207f476257b.png)\n\n 10. Fill in the following remaining fields and then click PUBLISH:\n\n * Category: Administration and Management\n\n * Graphic Assets (click BROWSE and upload image from zip file):\n\n * Application Icon 32x32: 32x32.png\n\n * Application Icon 128x128: 128x128.png\n\n * Application Card Banner: 128x128.png\n\n * Screenshot (click BROWSE and upload image from zip file): 80x80.png\n\n * Support Links:\n\n * Terms of Service URL: https://expel.io\n\n * Privacy Policy URL: https://expel.io\n\n * Support URL: https://support.expel.io\n\n * Distribution: click All Regions or select from the Regions list.\n\n![GmailPhishingButton_Step_3-10.png](https://support.expel.io/hc/article_attachments/7446291004051/uuid-b3e83de9-d0c0-9da3-501f-5e8c00384fc3.png)\n\n## Step 4: Install add on to domain\n\n 1. Navigate to https://gsuite.google.com/marketplace/mydomainapps, click the Report potential phishing app, and then click Domain Install.\n\n![mceclip3.png](https://support.expel.io/hc/article_attachments/6650252220435/uuid-\nba8d80ba-b03b-4ad7-5f65-1e06a9aefcf9.png)\n\n 2. In the Domain wide install area, click CONTINUE.\n\n![mceclip2.png](https://support.expel.io/hc/article_attachments/6650242502675/uuid-d3f6d28d-c561-ed7c-b074-c04fb0563f32.png)\n\n 3. On the OAuth Consent Screen, click the I agree checkbox, and then click ALLOW.\n\n![mceclip1.png](https://support.expel.io/hc/article_attachments/6650255079571/uuid-1ef61e9f-bb56-e06f-bdcf-0fe3352f32a5.png)\n\n 4. After complete, you see a success message. Click DONE.\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/6650227079955/uuid-5623b17f-8de3-11ff-1b21-8af0305f6f40.png)\n\n 5. The add-on becomes available to end users shortly. It can take as long as 24 hours for the deployment to take effect.\n\n"} \ No newline at end of file diff --git a/article_4407074216851.json b/article_4407074216851.json new file mode 100644 index 0000000000000000000000000000000000000000..f366367d75d4d556422321144d2e8857b7e8392c --- /dev/null +++ b/article_4407074216851.json @@ -0,0 +1 @@ +{"title": "Microsoft 365 Message Trace set up", "url": "https://support.expel.io/hc/en-us/articles/4407074216851-Microsoft-365-Message-Trace-set-up", "date": "2021-09-16T14:23:17Z", "contents": "This procedure enables the Message Trace API for an Microsoft 365\ninstallation, which helps Expel investigate phishing submissions.\n\n## Before you start\n\nThis procedure varies depending on which option you selected while connecting\nyour Microsoft 365 installation to Workbench:\n\n * If you chose Option 1: Enable Microsoft 365 integration during installation, use Option 1 below.\n\n * If you chose Option 2: Create Custom Azure Application during installation, use Option 2 below.\n\nFor more information, see the Microsoft 365 Direct setup for Workbench. If you\nneed help, contact your engagement manager.\n\n## Option 1: If you choose to enable Microsoft 365 integration\n\n### New installation\n\n 1. Navigate to Azure AD roles and administrators, scroll down and select these roles:\n\n * Global reader\n\n * Security reader\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/9946760701331/uuid-e910e746-8ce5-4dc2-864a-9dcf7fe0f195.jpg)\n\n 2. Click Add assignments.\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/9946791954451/uuid-a4c61dc1-6d74-a4c3-c6ee-430db5d2b955.jpg)\n\n 3. Search for the Expel Microsoft 365 integration enterprise app and select it.\n\n![mceclip2.png](https://support.expel.io/hc/article_attachments/9946733282067/uuid-84729a7d-33ea-7e24-d04a-2eb2dae4ffae.jpg)\n\n 4. Click Add.\n\n![Add_assignments_click_add.jpg](https://support.expel.io/hc/article_attachments/9946747666067/uuid-\ndca7100b-ad67-9dc7-9f43-b80b8da4c71a.jpg)\n\n### Existing installation\n\n 1. Open the Expel Microsoft 365 Integration > API Permissions tab and select Grant admin consent.\n\n 2. Consent to the new API permissions.\n\n 3. Navigate to Azure AD roles and administrators, scroll down and select these roles:\n\n * Global reader\n\n * Security reader\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/9946760701331/uuid-e910e746-8ce5-4dc2-864a-9dcf7fe0f195.jpg)\n\n 4. Click Add assignments.\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/9946791954451/uuid-a4c61dc1-6d74-a4c3-c6ee-430db5d2b955.jpg)\n\n 5. Search for the Expel Microsoft 365 integration enterprise app and select it.\n\n![mceclip2.png](https://support.expel.io/hc/article_attachments/9946733282067/uuid-84729a7d-33ea-7e24-d04a-2eb2dae4ffae.jpg)\n\n 6. Click Add.\n\n![Add_assignments_click_add.jpg](https://support.expel.io/hc/article_attachments/9946747666067/uuid-\ndca7100b-ad67-9dc7-9f43-b80b8da4c71a.jpg)\n\n## Option 2: If you choose to create custom Azure application\n\n### New and existing installations\n\n 1. Follow all previous API permission steps for Option 2: Create Custom Azure Application in the Microsoft 365 Direct setup for Workbench.\n\n 2. Navigate to the custom Azure application and click API Permissions.\n\n 3. On the APIs my organization uses tab, click Add a permission.\n\n 4. Search for and select Microsoft 365 Exchange Online.\n\n![Office365_Message_Trace_API_Permissions.png](https://support.expel.io/hc/article_attachments/9946761239315/uuid-609af25e-2168-f59e-0186-138f7f30595e.jpg)\n\n 5. Select Application permissions and search for ReportingWebService in the Select permissions search field.\n\n![Request_API_permissions_Add.jpg](https://support.expel.io/hc/article_attachments/9946733777555/uuid-6ce1aacb-9984-2ef2-cdaa-78a57e31f8cb.jpg)\n\n 6. Select the ReportingWebService.Read.All permission, then click Add permissions.\n\n 7. Select Grant admin consent for Expel, and then click Yes.\n\n![Grant_admin_consent.jpg](https://support.expel.io/hc/article_attachments/9946748238099/uuid-53978678-bf7a-984f-d893-cb6650c211f7.jpg)\n\n 8. Confirm that consent is granted for the added permission.\n\n![Grant_admin_consent_confirm.jpg](https://support.expel.io/hc/article_attachments/9946734030867/uuid-a8bb21d4-b0d3-6e44-2391-3a18e054cb31.jpg)\n\n 9. Navigate to Azure AD roles and administrators, scroll down and select these roles:\n\n * Global reader\n\n * Security reader\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/9946760701331/uuid-e910e746-8ce5-4dc2-864a-9dcf7fe0f195.jpg)\n\n 10. Click Add assignments.\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/9946791954451/uuid-a4c61dc1-6d74-a4c3-c6ee-430db5d2b955.jpg)\n\n 11. Search for the custom Azure app registration and select it.\n\n![Add_assignments_Option2.jpg](https://support.expel.io/hc/article_attachments/9946761732499/uuid-5ca332cc-e240-bc87-5e0d-72ade5390b61.jpg)\n\n 12. Click Add.\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\nOffice365, O365, messagetrace, MessageTrace\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"} \ No newline at end of file diff --git a/article_4407386601875.json b/article_4407386601875.json new file mode 100644 index 0000000000000000000000000000000000000000..7c99ab0d8b0a5bd4c9a6ce7991cdbfc1a1530ce0 --- /dev/null +++ b/article_4407386601875.json @@ -0,0 +1 @@ +{"title": "Cybereason setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/4407386601875-Cybereason-setup-for-Workbench", "date": "2021-09-22T14:44:53Z", "contents": "Cybereason REST APIs use an auth token to make authorized calls to the API.\nExpel uses Cybereason REST APIs to access resources through URI paths. You\nneed to generate an API key and an Application key.\n\n#### In this article\n\n * Step 1: Generate user credentials\n\n * Step 2: Configure the technology in Workbench\n\n * Step 3: Edit the device to add console access\n\n## Step 1: Generate user 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\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. In the Cybereason UI, navigate to the User screen.\n\n 2. Click Create New User. The Create New User screen appears.\n\n 3. Type the required details.\n\n * Username: an email address. Make note of this for later use.\n\n * Password: a password. Make note of this for later use.\n\n * Change password on next login: don't select this.\n\n * Enable Two Factor Authentication (TFA): don't select this.\n\n * Custom roles: select Analyst and L3.\n\n * Predefined roles: select API User.\n\n 4. Click Add User.\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 top of the page, click Add Security Device.\n\n 4. Search for and select your technology Cybereason.\n\n![mceclip2.png](https://support.expel.io/hc/article_attachments/6760467609875/uuid-605c01c0-caa2-63a7-dbbc-603618a2c3a0.png)\n\n 5. Complete all fields using the credentials and information you collected in Step 1.\n\n![mceclip4.png](https://support.expel.io/hc/article_attachments/13874945183379/uuid-f33b1bef-0c1f-3617-c268-88a282da1a12.png)\n\n * For Name type the host name of the device.\n\n * For Location type the geographic location of the appliance.\n\n * For Username type the username generated in Step 1.\n\n * For Password type the password generated in Step 1.\n\n * For Server URL type the Cybereason device address.\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\nCyber reason, cyberreason,\n\n"} \ No newline at end of file diff --git a/article_4408681005843.json b/article_4408681005843.json new file mode 100644 index 0000000000000000000000000000000000000000..cfa937819cb9cbbe934a089b72fae4b8eab33890 --- /dev/null +++ b/article_4408681005843.json @@ -0,0 +1 @@ +{"title": "Exabeam Fusion SIEM setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/4408681005843-Exabeam-Fusion-SIEM-setup-for-Workbench", "date": "2021-10-15T18:09:23Z", "contents": "This article explains how to connect Exabeam Fusion SIEM 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\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 requires a dedicated user account, which allows us to respond to\nsecurity alerts and leverage the data available in Exabeam Fusion SIEM.\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. At the bottom of the homepage, navigate to Exabeam Admin Operations.\n\n 2. Under the Exabeam User Management section select Users.\n\n 3. Click Add User.\n\n 4. 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\nThis optional field can be left blank. \n \nPassword\n\n|\n\nType a password. **Save the password to enter later in the Workbench.** \n \n 5. 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 6. For a custom role, type Expel for Role Name and Expel Custom Role for Description.\n\n 7. Select Advanced Analytics, and choose the following permissions:\n\n**View** \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 \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 \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(s) 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_siem.\n\n 2. Complete all fields using the credentials and information you collected in Steps 1 and 2:\n\n![ExabeamFusionSIEM_AddSecDev.png](https://support.expel.io/hc/article_attachments/13874957868947/uuid-c37765e5-5d98-9f3a-2230-80280a6b39e4.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 Workbench.\n\n * Type Name (give your Exabeam a name).\n\n * Type the city or site where your Exabeam 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, use 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"} \ No newline at end of file diff --git a/article_4411628902035.json b/article_4411628902035.json new file mode 100644 index 0000000000000000000000000000000000000000..182b6d4fa4af9ede7f71e7bba82c30e58c6385b2 --- /dev/null +++ b/article_4411628902035.json @@ -0,0 +1 @@ +{"title": "Guardicore setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/4411628902035-Guardicore-setup-for-Workbench", "date": "2021-11-30T17:07:04Z", "contents": "This article explains how to connect Guardicore to Workbench.\n\n#### In this article\n\n * Step 1: Enable console access\n\n * Step 2: Connect your technology with 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. Login to Guardicore Centra and navigate to Administration > User Management > Users and then click \\+ Add User.\n\n 2. Fill in the fields as follows:\n\n * For Username type Expel.\n\n * Leave the Email Address field blank.\n\n * The Description field is optional. You can leave it blank if you want.\n\n * For Permission Scheme select Administrator.\n\n * Create a Temporary Password.\n\n### Caution\n\nDo NOT select \"Enable 2-Step Verification.\"\n\nDo NOT select \"Enable user to view passwords used in security incidents.\"\n\n 3. Click Save.\n\n 4. Login to Guardicore Centra using the user credentials you just created and set a new Password. Make a note of the new password for later use.\n\n## Step 2: Connect your technology with 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=guardicore.\n\n 2. Fill in these fields:\n\n![mceclip3.png](https://support.expel.io/hc/article_attachments/6760450742803/uuid-\nbf2fa16e-a964-22ba-4a48-183b6bab900a.png)\n\n * For Name type Expel API Access.\n\n * For Location type the geographic location of the server (or \"cloud\" for cloud servers).\n\n * For Server type the server URL address.\n\n * For Username type the username you created in Step 1.\n\n * For Password type the new (not temporary) password you 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"} \ No newline at end of file diff --git a/article_4422790330003.json b/article_4422790330003.json new file mode 100644 index 0000000000000000000000000000000000000000..b5317f6bda41f306a6decdf1e4c0e4dfe8d04556 --- /dev/null +++ b/article_4422790330003.json @@ -0,0 +1 @@ +{"title": "CyberArk Identity setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/4422790330003-CyberArk-Identity-setup-for-Workbench", "date": "2022-02-15T19:34:58Z", "contents": "This article describes how to connect your CyberArk Identity installation to\nthe Expel Workbench.\n\n#### In this article\n\n * Step 1: Create a New OAuth App in the Admin portal\n\n * Step 2: Configure the new OAuth 2.0 client\n\n * Step 3: Create scopes\n\n * Step 4: Create a confidential client\n\n * Step 5: Configure the technology in Workbench\n\n## Step 1: Create a New OAuth App in the Admin portal\n\nThe first step is to create a new OAuth Client on the CyberArk Identity Admin\nPortal.\n\n 1. Log in to your CyberArk Identity tenant.\n\n 2. Navigate to your user name at the top right corner and select Switch to Admin Portal from the list.\n\n 3. Click Skip on the Quickstart screen if it appears.\n\n 4. Click Apps in the Dashboard.\n\n 5. Click Add Web Apps and select the Custom tab on the Add Web Apps popup.\n\n 6. Locate OAuth2 Client in the list and click Add. This creates an OAuth2 Client for use with CyberArk Identity APIs.\n\n 7. Click Yes on the Add Web App popup that appears.\n\n 8. Click Close on the Add Web Apps popup. The app configuration screen appears.\n\n## Step 2: Configure the new OAuth 2.0 client\n\n 1. In the app configuration screen, the categories are listed on the left side of the screen.\n\n 2. For each category, type the appropriate data in the fields as follows:\n\n * Description:\n\n * Application ID: type a unique name (no spaces) and make a note of it for later use.\n\n * Application Name: type a descriptive name for the application.\n\n * Application Description: type a description of the application (optional; not seen by users).\n\n * Category: the default grouping for the app on the Admin Portal.\n\n * General Usage:\n\n * Client ID Type: select Confidential.\n\n * Issuer: the URL of the server issuing access tokens. Can be left as default.\n\n * Allow Redirects: specifies the redirects that should be trusted when redirection occurs during the Authorization Code and Implicit flows.\n\n * Tokens:\n\n * Token Type: specifies the type of token to issue (JwtRS256 or opaque). JwtRS256 is a JSON Web Token (JWT) composed of Base64-encoded user and claim information. An opaque token contains no information about the user. To obtain user and claim information for an opaque token an introspection URL must be used by passing the token.\n\n * Auth Methods: specifies the authentication flow(s) for which the specified token type should be issued.\n\n * Token Lifetime: specifies the duration of the token's lifespan.\n\n * Issue refresh tokens: when enabled, allows clients to request a refresh token that can be exchanged for a new access token. Not applicable for the Resource Owner flow.\n\n * Scope:\n\n * User must confirm authorization request: when enabled, this setting requires that the client open a popup where the user must select and approve the scope(s) to allow for the client.\n\n * Scope Definitions: allows one or more scopes to be specified for authorization by the client.\n\n * User Access: specifies the system role(s) that the user—a user represents a confidential client—containing the credentials must be included in, for a client to successfully authorize with those credentials, see Step 4 below for information on creating a user to represent a confidential client.\n\n * Changelog: lists changes made to the client.\n\n 3. Click Save.\n\n## Step 3: Create scopes\n\nUse the following steps to define scopes for an OAuth2 Client:\n\n 1. Navigate to Apps and select the application to set the scope(s) for.\n\n 2. Click Scope.\n\n 3. Under Scope definitions, click Add. The Scope definitions popup appears.\n\n 4. Type a Name for the new scope, and a Description (optional).\n\n 5. Click Add and type this scope: `Redrock/*`\n\n 6. Click Save.\n\n## Step 4: Create a confidential client\n\nTo authorize a confidential client (a client that provides a client ID and\nclient secret), you must create a user entity representing the confidential\nclient.\n\n 1. Navigate to Core Services > Users to open the Create CyberArk Identity Directory User screen.\n\n 2. Click Add User.\n\n 3. Type the application's client ID into the Login Name field.\n\n 4. Type values into the Email Address and Display Name fields. Confidential clients don't use these values, but they are required to satisfy the required fields of the user form.\n\n 5. Type the application's client secret into the Password and Confirm Password fields.\n\n 6. Navigate to the Status section at the bottom and enable Is OAuth confidential client.\n\n 7. Click Create User. A confidential client who specifies the client ID and secret can now authorize against your CyberArk Identity Tenant.\n\n## Step 5: Configure the technology in Workbench\n\nNow that we have the correct access configured and noted the credentials, we\ncan integrate your technology 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. 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 CyberArk Identity, then fill in the fields like this:\n\n![Cyberark_Device_setup.png](https://support.expel.io/hc/article_attachments/13874832271379/uuid-e6a4e642-7fef-1a74-3ffb-d8d275e04974.png)\n\n * For Name, type CyberArk.\n\n * For Location, type either Cloud or On-prem.\n\n * For Application ID, type the Application ID when the Client is created.\n\n * For Username, type the Client ID.\n\n * For Password, type the Client Secret.\n\n * For Server, type the Server URL.\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"} \ No newline at end of file diff --git a/article_4484518380563.json b/article_4484518380563.json new file mode 100644 index 0000000000000000000000000000000000000000..1cc288b5536a524b6796465520b440c51987123f --- /dev/null +++ b/article_4484518380563.json @@ -0,0 +1 @@ +{"title": "Organization Notifications setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/4484518380563-Organization-Notifications-setup-for-Workbench", "date": "2022-02-24T19:49:04Z", "contents": "This document helps you configure notification messages sent to your\norganization from the Expel Workbench.\n\n## Before you start\n\nTo do this procedure, you must have:\n\n * Organization admin privileges in Workbench.\n\n * At least 1 communication channel established between your organization and Workbench. Communication channels currently available include:\n\n * Slack\n\n * Microsoft Teams\n\n * Ticketing System: Asana, Jira, ServiceNow\n\n * PagerDuty\n\n * OpsGenie\n\n### Note\n\nIf you don't see a link to the needed communication channel, contact your\nengagement manager for help.\n\n## What are organization notifications?\n\nExpel Workbench sends alerts and other messages to your organization. What\nthese messages are about and how you should react varies from one to the next.\nTo acquaint yourself with notifications and how to interpret them, read the\nNotification definitions guide.\n\n## How do I set up notifications for my organization?\n\nOrganization admins can choose which notifications to receive and how they are\nreceived. Any communications tool your organization integrates with Workbench\ncan be used. This includes Slack, PagerDuty, and more.\n\nUse the Organization Notifications checklist to make a list of the\nnotifications you're interested in receiving and how you want them delivered.\nYou can refer to this during the setup process.\n\nThe setup process is pretty simple. If you've ever created a rule in an email\nprogram, then this looks familiar:\n\n * First, select the event to watch, like incidents or investigations. Let's say Investigation.\n\n * Second, select an action, like opened or closed. (Investigation is closed.)\n\n * (Optional) If +Add Condition appears, you can refine your notification by selecting a general condition, like reason to close, and then selecting a specific condition, like possible policy violation. (Investigation is closed and the reason to close is a possible policy violation.) Conditions narrow your notifications down to specific issues you care the most about.\n\n * Finally, select one or more communication paths. If there is a communication path you want but it's not there, contact your engagement manager. (When Investigation is opened, notify through Slack and PagerDuty.)\n\nThat's all there is to it! Workbench sends the selected notifications to your\norganization through the communication path(s) you specified as events occur.\n\nOrganization admins can view, add, edit, and delete organization\nnotifications. Click below to jump to a task:\n\n * Viewing notifications\n\n * Adding notifications\n\n * Editing notifications\n\n * Deleting notifications\n\n## Viewing notifications\n\nTo view notifications settings for your organization:\n\n 1. In a new browser tab, login to https://workbench.expel.io.\n\n 2. From any screen, click Settings.\n\n![WB_Settings_Navigate.png](https://support.expel.io/hc/article_attachments/6760310133779/uuid-6b482479-6d73-9d31-0665-79c9106ccb4d.png)\n\n 3. Click My Organizations on the left side of the screen.\n\n![mceclip4.png](https://support.expel.io/hc/article_attachments/6760292295827/uuid-d8de0ec6-2938-77a9-6f1b-d55c54147e27.png)\n\n 4. Click the Notifications tab.\n\n![mceclip5.png](https://support.expel.io/hc/article_attachments/6760292356755/uuid-29fb2313-b80f-20be-5365-c8d4a9d5c272.png)\n\n 5. The notifications are listed in the tab.\n\n![mceclip4.png](https://support.expel.io/hc/article_attachments/6760330914579/uuid-65d63622-9dd6-d065-f210-543c36a00c85.png)\n\n## Adding notifications\n\nTo add notifications:\n\n 1. Click \\+ Add Notification.\n\n![mceclip5.png](https://support.expel.io/hc/article_attachments/15131224088979/uuid-9cfc7613-a026-7819-2003-4dd9f1dae171.png)\n\n 2. A blank notification appears.\n\n![mceclip6.png](https://support.expel.io/hc/article_attachments/6760371368723/uuid-8b9c6610-e3d4-e9a0-05ba-f5e1ce78a8bf.png)\n\n 3. Select an event.\n\n![mceclip7.png](https://support.expel.io/hc/article_attachments/6760371415315/uuid-63a6c3bc-f908-c214-4159-422a8b1a87f2.png)\n\n 4. Select an action for that event.\n\n![mceclip8.png](https://support.expel.io/hc/article_attachments/6760379294867/uuid-\ncc3aaa15-2881-566a-de6d-e0e894778390.png)\n\n 5. (Optional) If +Add condition is available, click it and then select a condition and a specific property for that event.\n\n![CondNotification_SelectCondition.png](https://support.expel.io/hc/article_attachments/13583954843795/uuid-f49e6c4f-c5b7-c75e-50a2-518ef8215f16.png)\n\n 6. Select a notification channel.\n\n![mceclip9.png](https://support.expel.io/hc/article_attachments/6760356446227/uuid-413cf705-4bff-363d-f6f3-0b2dd8fb4c50.png)\n\n 7. (Optional) Click \\+ Add Another add another notification channel.\n\n### Tip\n\nYou can select 2 or more channels for a notification.\n\n![mceclip10.png](https://support.expel.io/hc/article_attachments/6760292715155/uuid-\nbeebf5c2-1030-5392-356d-2388c36c811e.png)\n\n 8. Click Save.\n\n![mceclip11.png](https://support.expel.io/hc/article_attachments/6760331443475/uuid-988264e1-e0a2-5c93-a21b-7fb9ecbac7c2.png)\n\n 9. The notification appears on the Notifications tab.\n\n![mceclip13.png](https://support.expel.io/hc/article_attachments/6760331556371/uuid-\naed9b635-7e18-172a-f940-2c8eb1df738b.png)\n\n## Editing notifications\n\nTo edit notifications:\n\n 1. Hover your mouse pointer over the notification and click the pencil.\n\n![mceclip15.png](https://support.expel.io/hc/article_attachments/6760331623955/uuid-\naf435a59-9b94-385c-a65f-80e291cfdc51.png)\n\n 2. The notification appears.\n\n![mceclip16.png](https://support.expel.io/hc/article_attachments/6760356739987/uuid-e7313b7a-c68f-04be-58a9-655e35d049ef.png)\n\n 3. Change the notification as needed.\n\n![mceclip17.png](https://support.expel.io/hc/article_attachments/6760310938771/uuid-5a3d91a7-c365-0219-8206-3c8cdd5e85ba.png)\n\n 4. Click Save.\n\n 5. Your edited notification appears in the Email Notifications section.\n\n![mceclip18.png](https://support.expel.io/hc/article_attachments/6760356888339/uuid-a2ce3161-5466-2418-21aa-285106bba15b.png)\n\n## Deleting notifications\n\nTo delete notifications:\n\n 1. Hover your mouse pointer over the notification and click the trash can.\n\n![mceclip19.png](https://support.expel.io/hc/article_attachments/6760356951059/uuid-\necc8cb9f-0be1-ba89-941d-c99fcdbc8dda.png)\n\n 2. The Delete Notification popup appears. Click Delete.\n\n![mceclip20.png](https://support.expel.io/hc/article_attachments/6760357014547/uuid-c16d9293-9a74-ec89-06ae-e35d7dafb81a.png)\n\n## Where do we go from here?\n\nAfter setting up notifications for your organization, a logical next step\nshould be to set up notifications for your individual users. Similar to\norganization notifications, user notifications are sent through email. For\ninstructions, see the User Notifications setup guide.\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"} \ No newline at end of file diff --git a/article_4626253095571.json b/article_4626253095571.json new file mode 100644 index 0000000000000000000000000000000000000000..aa922546d4ca4aa045b326fab2339ea6ed2dd471 --- /dev/null +++ b/article_4626253095571.json @@ -0,0 +1 @@ +{"title": "Organization Notifications checklist", "url": "https://support.expel.io/hc/en-us/articles/4626253095571-Organization-Notifications-checklist", "date": "2022-03-08T15:33:09Z", "contents": "This table contains all the possible event and action combinations for\norganization notifications. If the **condition** fields are blank, there is no\nmodifier for that notification type. The **Notify through this path** column\nis blank so that you can fill in the notification channel(s) of your choice.\n\nYou can print this page and use it as a checklist to help you select\nnotifications and confirm that you entered all the desired notifications in\nWorkbench:\n\n**For this event...**\n\n|\n\n**and this action...**\n\n|\n\n**with this condition...**\n\n|\n\n**and this specific property...**\n\n|\n\n**Notify through this path: (Slack, PagerDuty, and so on)** \n \n---|---|---|---|--- \n \nAssembler\n\n|\n\nhas a health status change\n\n| | | \n \nExpel Alert\n\n|\n\nis created\n\n|\n\nalert severity\n\n|\n\ncritical\n\nhigh\n\nmedium\n\nlow\n\ntesting\n\ntuning\n\n| \n \nExpel Alert\n\n|\n\nis closed\n\n|\n\nalert severity\n\n|\n\ncritical\n\nhigh\n\nmedium\n\nlow\n\ntesting\n\ntuning\n\n| \n \nExpel Alert\n\n|\n\nis closed\n\n|\n\nreason to close\n\n|\n\nactivity blocked\n\nactivity failed\n\nbenign\n\nfalse positive\n\nIT misconfiguration\n\nother\n\nPhishing simulation\n\npossible policy violation\n\nPUP/PUA\n\ntesting\n\n| \n \nIncident\n\n|\n\nis created\n\n|\n\nincident severity\n\n|\n\nis critical\n\nis not critical\n\n| \n \nIncident\n\n|\n\nis downgraded\n\n|\n\nincident severity\n\n|\n\nis critical\n\nis not critical\n\n| \n \nIncident\n\n|\n\nis assigned to my org\n\n|\n\nincident severity\n\n|\n\nis critical\n\nis not critical\n\n| \n \nInvestigation\n\n|\n\nis created\n\n| | | \n \nInvestigation\n\n|\n\nis closed\n\n|\n\nreason to close\n\n|\n\nactivity blocked\n\nactivity failed\n\nbenign\n\nfalse positive\n\nIT misconfiguration\n\nother\n\nPhishing simulation\n\npossible policy violation\n\nPUP/PUA\n\ntesting\n\n| \n \nInvestigation\n\n|\n\nhas an alert added\n\n| | | \n \nInvestigation\n\n|\n\nis assigned to my org\n\n| | | \n \nInvestigative action\n\n|\n\nis assigned to my org\n\n| | | \n \nNotify action\n\n|\n\nis assigned to my org\n\n| | | \n \nRemediation action\n\n|\n\nis assigned to my org\n\n|\n\nremediation action type\n\n|\n\nblock command and control communications\n\nblock known bad hashes\n\nblock malicious domains and IPs\n\nblock sender address\n\nblock sender domain\n\ncontain hosts\n\ncontain infected removable media\n\ndelete compromised instances\n\ndelete malicious files\n\ndisable and modify AWS access keys\n\ndisable user account\n\nmitigate vulnerability\n\nother remediation\n\nreimage compromised hosts\n\nremove and block email forwarding address\n\nremove inbox rules for known compromised accounts\n\nremove malicious email\n\nreset credentials\n\n| \n \nRemediation action\n\n|\n\nis automated\n\n|\n\nremediation action type\n\n|\n\nblock known bad hashes\n\ncontain hosts remove\n\ndisable user account\n\nmalicious email\n\n| \n \nSecurity device\n\n|\n\nhas a health status change\n\n| | | \n \nVerify action\n\n|\n\nis assigned to my org\n\n| | | \n \nFor instructions on configuring organization notifications, see the\nOrganization Notifications article.\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"} \ No newline at end of file diff --git a/article_4827953089683.json b/article_4827953089683.json new file mode 100644 index 0000000000000000000000000000000000000000..c39b175ef7f8520a5a64162334bb8519f924b3dd --- /dev/null +++ b/article_4827953089683.json @@ -0,0 +1 @@ +{"title": "Salesforce setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/4827953089683-Salesforce-setup-for-Workbench", "date": "2022-03-16T18:38:48Z", "contents": "This article provides instructions for connecting your Salesforce to the Expel\nWorkbench.\n\n#### In this article\n\n * Before you start\n\n * Step 1: Create Profile for access control\n\n * Step 2: Create Expel user\n\n * Step 3: Get security token\n\n * Step 4: Create connected app\n\n * Step 5. Connect your technology to Workbench\n\n## Before you start\n\n * **Salesforce Shield or Real-Time Event Monitoring is required.**\n\n * Find your Salesforce domain. Save this information for later use.\n\n * Make sure Real-Time Event Monitoring streams are enabled for all available event objects. Click this link for more information about real-time event monitoring.\n\n## Step 1: Create Profile for access control\n\nSalesforce uses profiles to manage user access to data, so the first step is\nto create a profile for Expel.\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. In Salesforce, navigate to Profiles.\n\n 2. Clone the Read Only profile and name it Expel. Click Save.\n\n 3. Verify that API Enabled is selected under Administrative Permissions.\n\n 4. Enable Customize Application Permissions under Administrative Permissions. This is required to enable Logout Events.\n\n 5. Enable View Real-Time Event Monitoring Data under General User Permissions.\n\n 6. Click Save Profile.\n\n## Step 2: Create Expel user\n\nNow that the Expel profile is created, the next step is to create a user with\nthat profile.\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 Users.\n\n 2. Click New User.\n\n 3. Type in the required information:\n\n * For Last Name type ExpelAPI.\n\n * For Alias type expelapi.\n\n * For Email: soc+@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 * For Username and Nickname use the Salesforce default entries.\n\n * For Role select any role.\n\n * For User License select Salesforce.\n\n * For Profile select Expel.\n\n 4. Click Save.\n\n 5. Reset Password for the user.\n\n### Note\n\nThe new password is sent to the email address for the Expel Salesforce User.\n\n## Step 3: Get security token\n\n 1. From your personal settings, type **reset** in the Quick Find text box, and then select Reset My Security Token.\n\n 2. Click Reset Security Token.\n\n### Note\n\nThe new security token is sent to the email address for the Expel Salesforce\nUser.\n\n## Step 4: Create connected app\n\n 1. Login to Salesforce with the same user credentials that you want to collect data in your Salesforce deployment.\n\n 2. From Setup, type `App Manager` in the Quick Find text box, then select App Manager.\n\n 3. Click New Connected App.\n\n 4. Type the connected app name (Expel), which appears in the App Manager and on its App Launcher tile.\n\n 5. Type the API name.\n\n### Tip\n\nThe default is a version of the name without spaces. Only letters, numbers,\nand underscores are allowed. If the original app name contains any other\ncharacters, edit the default name.\n\n 6. Type your contact email for Salesforce.\n\n 7. In the API (Enable OAuth Settings) area of the page, select Enable OAuth Settings.\n\n 8. Select Enable for Device Flow.\n\n 9. Select the following OAuth scopes to apply to the connected app:\n\n * Manage user data via APIs (api)\n\n 10. Click Save.\n\n### Note\n\nIt can take about 10 minutes for the changes to take effect.\n\n 11. Retrieve the Consumer Key and Consumer Secret from the app page.\n\n### Note\n\nSave this info for later use.\n\n## Step 5. Connect your technology to 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 Organization Settings and click Security Devices.\n\n 3. At the top of the page, click \\+ Add Security Device.\n\n 4. Type in the required information:\n\n![mceclip9.png](https://support.expel.io/hc/article_attachments/6760359862035/uuid-5c89ff92-016b-e750-d503-104fd8d06e1c.png)\n\n * For Name create a name.\n\n * For Location type the physical location of your Salesforce domain.\n\n * For Salesforce domain type your Salesforce domain info from Before You Begin.\n\n * For Client ID type the Connected App’s Consumer Key.\n\n * For Client secret, type the Connected App’s Consumer Secret.\n\n * For Username type the Expel user’s username.\n\n * For Password type the Expel user’s password.\n\n * For Security token, type the Expel user’s security token.\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"} \ No newline at end of file diff --git a/article_5039466666771.json b/article_5039466666771.json new file mode 100644 index 0000000000000000000000000000000000000000..a49600ad54577f96e5bbd12a951c9fa14b8d1cae --- /dev/null +++ b/article_5039466666771.json @@ -0,0 +1 @@ +{"title": "Palo Alto WildFire API token creation", "url": "https://support.expel.io/hc/en-us/articles/5039466666771-Palo-Alto-WildFire-API-token-creation", "date": "2022-03-25T13:36:15Z", "contents": "This procedure creates an authentication token that allows the Expel Assembler\nto access the Palo Alto WildFire API.\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#### Step 1: Generate API credentials\n\nTo integrate the technology with Expel Workbench, we need to create secure\ncredentials to the API.\n\n 1. For **WildFire Appliance** follow this guide: https://docs.paloaltonetworks.com/wildfire/u-v/wildfire-api/get-started-with-the-wildfire-api/get-your-api-key/get-your-wildfire-appliance-api-key.html\n\n 2. For **WildFire Public Cloud** follow this guide: https://docs.paloaltonetworks.com/wildfire/u-v/wildfire-api/get-started-with-the-wildfire-api/get-your-api-key/get-your-wildfire-public-cloud-api-key.html#id3809ea9e-090f-459b-a382-9689383d1855\n\n#### Step 2: Configure the technology 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, log in to Workbench (this link opens the Add Security Device screen directly).\n\n 2. For WildFireAPI key type the API key generated in Step 1.\n\n![Palo_alto_Add_device_Wildfire_key](https://support.expel.io/hc/article_attachments/6760382172691/uuid-\nfda89578-d23c-909c-3e64-6ef41b3b8fc6.png)\n\n 3. Click Save.\n\n"} \ No newline at end of file diff --git a/article_5042493348627.json b/article_5042493348627.json new file mode 100644 index 0000000000000000000000000000000000000000..3e78e90fac145f4fcb7d56cea5c9ac358cf305c7 --- /dev/null +++ b/article_5042493348627.json @@ -0,0 +1 @@ +{"title": "Tanium Cloud (TaaS) setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/5042493348627-Tanium-Cloud-TaaS-setup-for-Workbench", "date": "2022-03-25T15:27:27Z", "contents": "This article provides prerequisites and onboarding steps for connecting your\nTanium Cloud installation to the Expel Workbench.\n\n#### In this article\n\n * Step 1: Enable console access\n\n * Step 2: Create an API Token\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\nWhen you create a Tanium user configuration, by default it has no computer\nmanagement groups, alternative personas, user groups, or roles until you\nassign them. A user with no roles can log into the Tanium Console but can't\naccess anything. Don't create configurations for user accounts that you import\nfrom an LDAP server.\n\nWe use the following Tanium API routes for our integration:\n\n**Route**\n\n|\n\n**Permission** \n \n---|--- \n \n/api/v2/session/login\n\n|\n\nInteract:Login \n \n/api/v2/sensors/by-name\n\n|\n\nInteract:Read Sensor \n \n/api/v2/parse_question\n\n|\n\nInteract:Ask Dynamic Questions \n \n/api/v2/questions \n \n/api/v2/result_data/question/ \n \n/plugin/products/detect3/api/v1/alerts\n\n|\n\nThreat Response: Detect Alert Read \n \n/plugin/products/detect3/api/v1/intels\n\n|\n\nThreat Response: Detect Intel Read \n \n/plugin/products/detect3/api/v1/sources\n\n|\n\nThreat Response: Detect Source Read \n \n/plugin/products/detect3/api/v1/intels//labels\n\n|\n\nThreat Response: Detect Label Read \n \nThe Interact Basic Userrole grants us all the necessary permissions we need to\naccess the question/sensor APIs and Interact console.\n\nThe Threat Response Read Only User role grants us all the necessary\npermissions we need to access the alerts APIs and Threat Response console.\n\nIf you are using a custom role, we also need **Detect Use API** permission as\nwell as the necessary permissions to make Threat Response available in\nconsole.\n\nThe Tanium client uses a username/password combination to create an\nauthenticated session. The returned session token is set in the session header\nfor all subsequent requests.\n\n 1. From the Main menu, select Administration > Management > Users.\n\n 2. Click New User.\n\n 3. Specify a user name that matches 1 of the following:\n\n * A user account defined locally on the Tanium Server.\n\n * A user account defined in your IdP.\n\n * (Windows only) An AD account name. Specify just the user name, not the domain name. The Tanium Server uses Windows Authentication, and doesn't store or manage login credentials for the user.\n\n 4. Save the configuration and get ready to assign roles to a user.\n\n 5. From the main menu, select Administration > Management > Users.\n\n 6. Click the User Name of the user configuration that you want to edit.\n\n 7. In the Roles and Effective Permissions section, click Manage.\n\n 8. In the Grant Roles section, click Edit, select Interact Basic User and Threat Response Read Only User, and click Save.\n\n 9. Click Show Preview to Continue to review the impact of your changes.\n\n## Step 2: Create an API Token\n\n 1. Sign into the Tanium Console as the user and persona for whom you want to create a token.\n\n### Note\n\nThe authentication credentials and authorization permissions of a token are\nthose of the requesting persona. To limit access to computer groups and\ncontent sets, create a persona with the desired permissions and then sign in\nwith the new persona.\n\n 2. From the Main menu, go to Administration > Permissions > API Tokens.\n\n 3. Click New API Token and configure the token settings:\n\n * Notes (optional): type a description of the purpose for this token.\n\n * Expire in days: type the expiration interval 365. By default, the maximum interval is 365 days. If you don't enter a value, the interval defaults to 7 days.\n\n 4. Trusted IP addresses: Enter the external IP addresses of the systems from which you will use this token to authenticate with the Tanium Server. Use commas or line breaks to separate multiple entries. Expel uses a group of static egress IP addresses to complete polling of the security device and for console access. Add the following IPs to the Trusted IP address 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 5. Click Save and review the token details.\n\n 6. Copy the token to your clipboard and store as you need this to add this to Workbench.\n\n### Note\n\nYou cannot view the token in the Tanium Console after the visibility timeout\n(5 minutes) expires, or you refresh the API Tokens page or grid, or you\nnavigate to another console page.\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. Login to 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 your technology (Tanium).\n\n![mceclip6.png](https://support.expel.io/hc/article_attachments/6760454120211/uuid-1f4f0dbf-00df-\nffbd-c5bf-77c3e74c5693.png)\n\n 5. Complete the fields as follows:\n\n * For Name, type the host name of the Tanium device.\n\n * For Location, type the geographic location of the appliance.\n\n * For Server address, type your Tanium Cloud URL.\n\n * For Username and Password, type the username and password created in Step 1.\n\n * For Token, type the API token that you created in Step 2.\n\n 6. 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"} \ No newline at end of file diff --git a/article_5442136503571.json b/article_5442136503571.json new file mode 100644 index 0000000000000000000000000000000000000000..cf85c94505a07569baef9b44f732dd568fa14a91 --- /dev/null +++ b/article_5442136503571.json @@ -0,0 +1 @@ +{"title": "How to submit a support ticket in Workbench", "url": "https://support.expel.io/hc/en-us/articles/5442136503571-How-to-submit-a-support-ticket-in-Workbench", "date": "2022-04-11T16:43:35Z", "contents": "If you need support, you can open a support ticket from Workbench.\n\n 1. While in Workbench, click your initials in the top right.\n\n 2. From the menu that appears, click Submit a ticket in Zendesk.\n\n![SubmitTicketInWB.png](https://support.expel.io/hc/article_attachments/6760307825299/uuid-2791704d-e1bc-8a84-5c92-b5342943956c.png)\n\n 3. Complete the form that appears. Be as specific and complete as possible about the issue.\n\n 4. After you're done, click OK.\n\n##### Related terms\n\nopen a support ticket, get support help, product support\n\n"} \ No newline at end of file diff --git a/article_6179440802195.json b/article_6179440802195.json new file mode 100644 index 0000000000000000000000000000000000000000..75895ac1e529cbceb0ff0b8c271810e24e6c67a8 --- /dev/null +++ b/article_6179440802195.json @@ -0,0 +1 @@ +{"title": "Enabling Gmail Logs in BigQuery", "url": "https://support.expel.io/hc/en-us/articles/6179440802195-Enabling-Gmail-Logs-in-BigQuery", "date": "2022-05-12T14:38:16Z", "contents": " 1. Navigate to the Gmail setup console in Google Workspace admin: https://admin.google.com/ac/apps/gmail/setup\n\n![mceclip0.png](https://support.expel.io/hc/article_attachments/6179413528723/uuid-93f66009-9c00-64a2-12c3-e9826df902b2.png)\n\n 2. Hover over Email Logs in BigQuery and click the pencil icon. In the section that appears, select the Enable checkbox and type a Description. Select the same project that the service account belongs to from the previous steps.\n\n 3. Type gmail_logs_dataset as the name for the new BigQuery dataset and click SAVE.\n\n![mceclip1.png](https://support.expel.io/hc/article_attachments/6179440939283/uuid-b243ac47-7841-1cfd-63e3-e78a5e893bac.png)\n\n 4. From the IAM console in the project where the service account was created, click the pencil icon and add the role BigQuery Job User to the service account.\n\n![mceclip8.png](https://support.expel.io/hc/article_attachments/6179451770771/uuid-f164e180-615a-2bbd-2ffe-b54690c94076.png)\n\n 5. Search for and add BigQuery Job User and click SAVE.\n\n![mceclip9.png](https://support.expel.io/hc/article_attachments/6179451812499/uuid-8f19a8c4-84b4-13c3-4f07-5a19402c2cff.png)\n\n 6. Navigate to BigQuery in the Google Cloud console: https://console.cloud.google.com/bigquery and find the gmail_logs_dataset. Open the menu on the right and click Open.\n\n![mceclip2.png](https://support.expel.io/hc/article_attachments/6179400019347/uuid-\nec6b80a7-3cd0-f47f-6ca2-ee438a88d5ab.png)\n\n 7. Default retention is set to 60 days, but we recommend changing that to 30 days. From the dataset details, click EDIT DETAILS.\n\n![mceclip3.png](https://support.expel.io/hc/article_attachments/6179400073619/uuid-8634c6e1-0fa2-eeae-a998-5270e6d5d894.png)\n\n 8. Type the length of time to retain the log tables and click SAVE.\n\n![mceclip13.png](https://support.expel.io/hc/article_attachments/6179430456339/uuid-8f836c4e-0d86-1618-b947-ff5b9f4f56aa.png)\n\n 9. Click SHARING and select Permissions.\n\n![mceclip4.png](https://support.expel.io/hc/article_attachments/6179413873427/uuid-\ndfcd224b-42a1-ac21-51df-4ec5fbf54f9a.png)\n\n 10. Add the service account under New principals and select the role BigQuery Data Viewer. Click SAVE to close the panel.\n\n![mceclip15.png](https://support.expel.io/hc/article_attachments/6179413918739/uuid-7f6464a4-56c9-0074-d616-d769032b976d.png)\n\n"} \ No newline at end of file diff --git a/article_6216735920403.json b/article_6216735920403.json new file mode 100644 index 0000000000000000000000000000000000000000..3197a020f5d13543bcb338e3e418e8d29b4c9791 --- /dev/null +++ b/article_6216735920403.json @@ -0,0 +1 @@ +{"title": "OneLogin setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/6216735920403-OneLogin-setup-for-Workbench", "date": "2022-05-13T21:15:00Z", "contents": "This article explains how to connect OneLogin 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\nNow that we have the correct access configured and noted the credentials, we\ncan integrate your tech with Workbench.\n\n 1. In the OneLogin console, select Administration.\n\n 2. Select Users and then New User.\n\n 3. Fill in the following fields:\n\n * First name: Expel\n\n * Last name: SOC\n\n * For Email: soc+@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 * Username: same as email\n\n * Password: set by user\n\n * Company: Expel\n\n * Leave the other fields blank.\n\n 4. Click Save User.\n\n 5. Notify your engagement manager 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 OneLogin as a user with Admin privileges.\n\n 2. Navigate to Administration.\n\n 3. Navigate to Developers > API Credentials.\n\n 4. Select New Credential.\n\n 5. Give the credential a name (such as Expel API) and select Read All and click Save.\n\n 6. Save a copy of the Client ID and Client Secret.\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. Login to 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 OneLogin.\n\n![image8.png](https://support.expel.io/hc/article_attachments/13874890260883/uuid-58a5755f-847c-75ca-d583-cff823181bcc.png)\n\n * Give the device a Name and Location.\n\n * Fill in fields for Client Secret and Client ID with credentials generated in Step 2.\n\n * Specify the Region of the OneLogin device (US, EU).\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"} \ No newline at end of file diff --git a/article_6760236234643.json b/article_6760236234643.json new file mode 100644 index 0000000000000000000000000000000000000000..d3adf58d1bcba47fc0077cabd12ee1988bfd9088 --- /dev/null +++ b/article_6760236234643.json @@ -0,0 +1 @@ +{"title": "Wazuh Cloud setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/6760236234643-Wazuh-Cloud-setup-for-Workbench", "date": "2022-06-06T16:24:47Z", "contents": "By following these steps, you create a user account for Expel which keeps\nExpel activity separate from other activity on the Wazuh console.\n\n### Note\n\nThis guide is for cloud installations of Wazuh. For on-premises installations,\nsee the Wazuh on-prem article.\n\n#### In this article\n\n * Step 1: Get the Elastic API\n\n * Step 2: Create an account in Elastic\n\n * Step 3: Setup the archives index\n\n * Step 4. Configure the technology in Workbench\n\n * Step 5: Edit the device to add console access\n\n## Step 1: Get the Elastic API\n\n 1. Ask Wazuh support (cloud@wazuh.com) to expose the Elastic API and allow list these 6 IPs:\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 2. Write down the exposed Elastic API. Your API URL should be similar to https://.cloud.wazuh.com/api/elastic/. Notify your engagement manager if your URL doesn't end with the suffix `/api/elastic`.\n\n## Step 2: Create an account in Elastic\n\nThis step configures a user with a **read-only** role for Expel to access this\nAPI.\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. Go to Open Distro for Elasticsearch > Security > Roles > Create > Role.\n\n 2. Create a role with these options:\n\n * Cluster Permissions: cluster_all.\n\n * Index Permissions: Add the index - * , with index permissions - search, get, read.\n\n * Tenant permissions: global_tenant with Read only.\n\n 3. Go to the Mapped Users tab and select Create Internal User.\n\n 4. Type a username and password for the new user and write them down.\n\n 5. Go back to the Roles screen and click Map users.\n\n 6. Select the newly created user and click Save.\n\n 7. Go to Wazuh > Security > Roles mapping.\n\n 8. Create a new Role mapping with these options:\n\n * Roles: readonly.\n\n * Internal users: select the newly created user from the list.\n\n## Step 3: Setup the archives index\n\nThis step sets up the Wazuh-archives index.\n\n 1. Go to Wazuh > Management > Configuration > Edit Configuration.\n\n 2. Change the logall_json setting to yes.\n\n`**< ossec_config>** **< ossec_config>** **< global>** **<\njsonout_output>yes** **< alerts_log>yes** **<\nlogall>no** **< logall_json>yes** **< /global>**`\n\n 3. After you configure the archive, the archive file goes to cold storage. For investigative purposes, we want to query this index in real-time. The next step is to reach out to your Wazuh support team to change this index to hot storage. This is a change to the filebeat.yml file which must be done by the Wazuh cloud support team.\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. In a new browser tab, log into https://workbench.expel.io/settings/security-devices?setupIntegration=wazuh. You may be asked to log into Workbench.\n\n 2. Fill out the form like this:\n\n![mceclip9.png](https://support.expel.io/hc/article_attachments/13874952023443/uuid-\nff7d3863-dab6-b829-18f4-964bb231eff4.png)\n\n * Where is your device? Cloud.\n\n * Name: any name for the integration.\n\n * Location: Cloud.\n\n * Username: Username for the newly created user.\n\n * Password: Password for the newly created user.\n\n * Server address: type the Wazuh cloud server address.\n\n### Note\n\nDon't type the Elastic API address.\n\n * Is this a Wazuh cloud Instance?: select Yes.\n\n 3. Click Save.\n\n 4. You can set up console access now or 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"} \ No newline at end of file diff --git a/article_6789159650067.json b/article_6789159650067.json new file mode 100644 index 0000000000000000000000000000000000000000..34d569b0a1618f5ce51cc9034bf58d6e25e131d1 --- /dev/null +++ b/article_6789159650067.json @@ -0,0 +1 @@ +{"title": "Google Workspace Alert Center setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/6789159650067-Google-Workspace-Alert-Center-setup-for-Workbench", "date": "2022-06-07T16:40:02Z", "contents": "This article helps you add the Google Workspace Alert Center to your Expel\nWorkbench.\n\n#### In this article\n\n * Before you start\n\n * Step 1: Enable Google Workspace APIs\n\n * Step 2: Grant the service account the required API permission scope\n\n## Before you start\n\nGoogle Workspace must be onboarded before onboarding the Google Workspace\nAlert Center.\n\n## Step 1: Enable Google Workspace APIs\n\n 1. Open the Google Cloud Console.\n\n 2. From the menu in the upper left, click APIs & Services > Library.\n\n 3. In the search field, type Google Workspace Alert Center API and press Enter.\n\n 4. In the list of search results, click the Google Workspace Alert Center API.\n\n 5. Click Enable.\n\n## Step 2: Grant the service account the required API permission scope\n\n 1. Open the Google Workspace admin console https://admin.google.com/ac/owl/domainwidedelegation\n\n 2. Navigate to Security > API Controls > Manage Domain Wide Delegation.\n\n 3. Find and select the Expel service account set up when you onboarded Google Workspace.\n\n 4. Add this API permission scope to the list: `https://www.googleapis.com/auth/apps.alerts`\n\n 5. Save and close.\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"} \ No newline at end of file diff --git a/article_7041816059923.json b/article_7041816059923.json new file mode 100644 index 0000000000000000000000000000000000000000..23e801b1a6bf7794088c035e0924469365617c9c --- /dev/null +++ b/article_7041816059923.json @@ -0,0 +1 @@ +{"title": "Google Cloud Platform setup for Workbench Appendix", "url": "https://support.expel.io/hc/en-us/articles/7041816059923-Google-Cloud-Platform-setup-for-Workbench-Appendix", "date": "2022-06-16T16:10:11Z", "contents": "## Data access log support in BigQuery\n\nData Access audit logs generate log events from the resource interaction plane\nof Google Cloud Platform. This includes event logging of requests to Google\nCloud Platform resources such as object read/write operations, to answer\nquestions such as “Who accessed file data in a storage bucket?” Expel doesn't\noffer monitoring and detection support for Data Access audit logs; however,\nExpel can use these logs to support alert triage and investigations.\n\nTo generate these logs, Google Cloud Platform customers must enable them.\nReview Google’s pricing reference for more information.\n\n### Note\n\nThese logs can be long, especially if resources are being accessed by the\npublic or other high-volume situations. Make sure you thoroughly understand\nthe cost impact before enabling Data Access audit logs.\n\n#### In this article\n\n * Before you start\n\n * Step 1: Configure BigQuery\n\n * Step 2: Create the BigQuery org sink\n\n * Step 3: Enable data access logs\n\n * Default Configuration Option\n\n * Cost Conscious Option\n\n * Enabling the Logs by Service\n\n## Before you start\n\n 1. Google Cloud Platform setup for Workbench completed.\n\n 2. Gcloud command-line tool installed.\n\n## Step 1: Configure BigQuery\n\n 1. Navigate to BigQuery in the expel-integration project and create a new dataset.\n\n * Dataset ID: expel_integration_dataset\n\n * Data location: Default\n\n * Default Table Expiration: 30 days\n\n * Encryption: Google-managed key\n\n 2. From the dataset settings, click SHARE DATASET, and grant the expel-gcp-integration service account (created in Step 2 of theGoogle Cloud Platform onboarding guide) the BigQuery Data Viewer and BigQuery User roles.\n\n## Step 2: Create the BigQuery org sink\n\n### Note\n\nOrganization sinks can’t be created from the Google Cloud console\nhttps://cloud.google.com/logging/docs/export/configure_export_v2 so we use the\ngcloud command-line tool.\n\n 1. Login to Google Cloud Platform.\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 BigQuery org sink:\n\n * If your organization plans to use Event Threat Detection service, use this command:\n \n $ gcloud logging sinks create expel-org-sink-bigquery bigquery.\n googleapis.com/projects/[project-id]\n /datasets/expel_integration_ dataset --include-children\n --organization=[org-id] --log\n filter=\"logName=~\\\"cloudaudit\\.googleapis\\.com\\%2Fdata_access\\\"\n OR resource.type=\\\"threat_detector\\\"\"\n\n * If your organization does not plan to use the Event Threat Detection service, use this command:\n \n $ gcloud logging sinks create expel-org-sink-bigquery bigquery.\n googleapis.com/projects/[project-id]\n /datasets/expel_integration_ dataset --include-children\n --organization=[org-id] --log\n filter=\"logName=~\\\"cloudaudit\\.googleapis\\.com\\%2Fdata_access\\\"\"\n\nThis automatically creates a new service account which must be granted\nBigQuery Data Editor in the expel_integration_dataset in the console.\n\n## Step 3: Enable data access logs\n\nAdmin Activity audit logs are enabled by default in Google Cloud Platform.\nDuring your initial onboarding, your organization was configured to send Admin\nActivity audit logs and Event Threat Detection alerts to Expel for monitoring\nand security detection support. Data Access audit logs are not enabled by\ndefault in Google Cloud Platform and have a cost to do so.\n\nReference\n\nhttps://cloud.google.com/logging/docs/audit/understanding-audit-logs\n\nhttps://cloud.google.com/logging/docs/audit/configure-data-access\n\n### Default Configuration Option\n\nA default audit log configuration can be set at the organization IAM so all\nnew folders and projects inherit the configuration. This saves you from\nadministrative hassle down the road.\n\n### Cost Conscious Option\n\nIf you only want to collect Data Access audit logs from projects with\nparticularly sensitive data or perhaps just production projects, you can\nconfigure audit logs in any IAM and IAM inheritance applies configuration as\nnecessary. For example, if your organization has a production project with\nsensitive client data stored in Cloud Storage, you can consider only enabling\nthe Google Cloud Storage Data Access audit logs in that particular project and\nleave it turned off in all of the other projects.\n\n### Enabling the Logs by Service\n\nFrom the IAM console, click Audit Logs. Each service API can be enabled or\ndisabled from this table. Some of the services to consider enabling:\n\n * Cloud Billing API\n\n * Cloud Build API\n\n * Cloud Functions API\n\n * Cloud Key Management Service (KMS) API\n\n * Cloud Logging API\n\n * Cloud Memorystore for Redis API\n\n * Cloud Pub/Sub API\n\n * Cloud Resource Manager API\n\n * Cloud SQL\n\n * Compute Engine API\n\n * Google App Engine Admin API\n\n * Google Cloud Deployment Manager V2 API\n\n * Google Cloud Storage\n\n * Identity and Access Management (IAM) API\n\n * Secret Manager API\n\n### Note\n\nSome services are prone to generate large volumes of log data (for example,\nKubernetes, Compute Engine API and Google Cloud Storage), which can\nsignificantly affect cost.\n\nSelect your audit logging preference, and click Save.\n\nAs new projects are created and services are enabled by users, audit logging\nconfiguration should be inherited in IAM appropriately and data is recorded to\nyour BigQuery table.\n\n#### Related terms\n\nGSuite, G Suite\n\n"} \ No newline at end of file diff --git a/article_7376174841747.json b/article_7376174841747.json new file mode 100644 index 0000000000000000000000000000000000000000..e684467ffc2d36210211c1d67349e58b212cf4fc --- /dev/null +++ b/article_7376174841747.json @@ -0,0 +1 @@ +{"title": "Fortinet via SIEM setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/7376174841747-Fortinet-via-SIEM-setup-for-Workbench", "date": "2022-06-29T14:54:21Z", "contents": "This article helps you to connect your Fortinet 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 Fortinet 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 Fortinet to a desired SIEM\n\n * Step 2: Configure the SIEM in Workbench\n\n * Step 3: Configure Fortinet in Workbench\n\n## Step 1: Logging Fortinet to a desired SIEM\n\nRefer to your SIEM documentation or work with your SIEM representative to port\nin Fortinet 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 * Secureonix\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 Fortinet logs are flowing through and available.\n\n## Step 3: Configure Fortinet 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=fortinet_via_siem.\n\n![FortinetViaSIEM_AddSecDev.png](https://support.expel.io/hc/article_attachments/7376357531539/uuid-781b209c-5e67-17f8-afe6-f79c785c9c48.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 Fortinet 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 Resource group name, type the Secureonix resource group name for this device.\n\n * For Vendor, type either the Exabeam Fusion SIEM vendor or the Microsoft Sentinel device vendor 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"} \ No newline at end of file diff --git a/article_8589363228435.json b/article_8589363228435.json new file mode 100644 index 0000000000000000000000000000000000000000..f4eda9177d14b64f6fe37dfdbf131c2df0a937e0 --- /dev/null +++ b/article_8589363228435.json @@ -0,0 +1 @@ +{"title": "Elasticsearch setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/8589363228435-Elasticsearch-setup-for-Workbench", "date": "2022-08-11T18:42:37Z", "contents": "This article helps you connect your Elasticsearch installation with the Expel\nWorkbench.\n\n#### In this article\n\n * Step 1: Enable console and API 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 and 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. Open Kibana and use the User Creation Wizard to to create a user for Expel with a role that grants Read privileges to the Indices that host your security logs. For instructions, see: https://www.elastic.co/guide/en/kibana/current/using-kibana-with-security.html#security-create-roles\n\n 2. Make note of the Username and Password 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. In a new browser tab, login to https://workbench.expel.io/settings/security-devices?setupIntegration=generic_elasticsearch.\n\n![Elasticsearch_WB_AddSecDev.png](https://support.expel.io/hc/article_attachments/13874957471379/uuid-\naff7810b-e33f-0548-07f8-593400529216.png)\n\n 2. For Where is your device? select Cloud or On-prem.\n\n 3. Fill in the other fields like this:\n\n * For Assembler, select your Assembler from the list. (On-prem only.)\n\n * For Name and Location, type in a unique name and describe the general physical location of the server.\n\n * For Username and Password, type in the credentials you created in Step 1.\n\n * For Server address, copy/paste the Elasticsearch endpoint. Be sure to use the Elasticsearch endpoint and not the Kibana endpoint.\n\n * For Index, type in where the security logs are hosted on the server.\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"} \ No newline at end of file diff --git a/article_9016309101843.json b/article_9016309101843.json new file mode 100644 index 0000000000000000000000000000000000000000..37734245220a415b8e7f85c02b527dfdd324a517 --- /dev/null +++ b/article_9016309101843.json @@ -0,0 +1 @@ +{"title": "Workday setup for Workbench", "url": "https://support.expel.io/hc/en-us/articles/9016309101843-Workday-setup-for-Workbench", "date": "2022-08-26T20:27:15Z", "contents": "This procedure helps you integrate your Workday installation with the Expel\nWorkbench.\n\n#### In this article\n\n * Before you start\n\n * Enable console access\n\n * Step 1: Create an Integration System user account\n\n * Step 2: Create a security group\n\n * Step 3: Generate API credentials\n\n * Step 4: Enable activity logging\n\n * Step 5: Create a custom signon report\n\n * Step 6: Configure the technology in Workbench\n\n## Before you start\n\nYou must have an account with these security groups assigned to it:\n\n * Security Administrator\n\n * System Auditor\n\n * Report Administrator\n\n## 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 happening on the Workday console.\n\n## Step 1: Create an Integration System user account\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 Workday device and navigate to Create Integration System User.\n\n 2. Fill in the Account Information like this:\n\n * For User Name type Expel_user.\n\n * Create and verify a Password. Make note of it for use later.\n\n * For Session Timeout Minutes type 0.\n\n * Select Do Not Allow UI Sessions.\n\n 3. Click OK.\n\n 4. Navigate to Maintain Password Rules and add Expel_user to the list of System Users exempt from password expiration.\n\n 5. Click OK.\n\n## Step 2: Create a security group\n\n 1. Navigate to Create Security Group and fill in the fields like this:\n\n * For Type of Tenanted Security Group select Integration System Security Group (Unconstrained).\n\n * For Name type Expel Client Security Group.\n\n * For Email enter: youremailaddress@yourcompanyname.com.\n\n * For Roles select the Expel role you created in the previous step.\n\n * Click Add New User.\n\n 2. Click OK.\n\n 3. In the Edit Integration System Security Group (Unconstrained) window, add Expel_user to the Integration System Users list.\n\n 4. Click OK.\n\n 5. Navigate to View Domain for the System Auditing domain.\n\n 6. Open the System Auditing Actions menu and select Domain > Edit Security Policy Permissions.\n\n 7. Add the Expel Client Security Group to these tables:\n\n * Report/Task Permissions: select View.\n\n * Integration Permissions: select Get.\n\n * Customer Report creation: select View and Modify.\n\n * System Auditing: select View and Get.\n\n * Security Administration: select Get.\n\n 8. Click OK.\n\n 9. Navigate to Activate Pending Security Policy Changes and activate the changes.\n\n 10. Click OK.\n\n## Step 3: Generate API credentials\n\nThe normal interaction with Workday is through the API. This step creates the\nAccess Key that allows Expel to use the API.\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 Register API Client for Integrations and fill in the fields like this:\n\n * For Client Name type Expel CollectorsCo.\n\n * Select Non-Expiring Refresh Tokens.\n\n * For Scope (Functional Areas) select System.\n\n 2. Click OK.\n\n 3. Make note of the newly generated Client Secret and Client ID which are used for registration in Workbench. If you lose the Client Secret, you can create a new one with Generate New API Client Secret.\n\n 4. Click Done.\n\n 5. Navigate to View API Clients. All endpoints must be set explicitly, including the `token_endpoint` and `rest_api_endpoint` because of Workday's unique URL structure. Make a copy of these two endpoints for use later:\n\n * Workday REST API Endpoint (example: `https:///ccx/api/privacy/v1/`)\n\n * Token Endpoint (example: `https:///ccx/oauth2//token`)\n\n 6. Navigate to the API Clients for Integrations tab, find the Expel client in the list, and open the menu (3 dots) for that client.\n\n 7. In the menu, select API Client > Manage Refresh Token for Integrations.\n\n 8. On the Manage Refresh Tokens for Integrations screen, select Expel_user in the Workday Account field and click OK.\n\n 9. On the Delete or Regenerate Refresh Token screen, select Generate New Refresh Token and click OK.\n\n 10. Make a copy of the Refresh Token for use later and click Done.\n\n## Step 4: Enable activity logging\n\n 1. Navigate to Edit Tenant Setup - System and select Enable User Activity Logging.\n\n 2. Click OK.\n\n 3. Navigate to Edit Tenant Setup - Security and select OAuth 2.0 Clients Enabled.\n\n 4. Click OK.\n\n## Step 5: Create a custom signon report\n\n 1. Navigate to Copy Standard Report to Custom Report and select Candidate Signons and Attempted Signons from the Standard Report Name list.\n\n 2. Click OK.\n\n 3. Change the Name to Custom Signons and Attempted Signons Report for Expel and select Optimized for Performance.\n\n 4. Click OK.\n\n 5. Edit the Data Source Filter field and select the Workday System Accounts Signons in Range filter.\n\n 6. Go to the Columns tab, click the + button and add these fields:\n\n * Operating System\n\n * Password Changed\n\n * Request Originator\n\n * SAML Identity Provider\n\n * Forgotten Password Reset Request\n\n * Multi-Factor Type\n\n * Is Device Managed\n\n * UI Client Type\n\n * Browser Type\n\n * Device is Trusted\n\n 7. In the Column Heading Override column, remove the text for Field > Session ID and Field > System Account.\n\n 8. Open the Advanced tab, and under Web Service Options, select Enable As Web Service.\n\n 9. Click OK.\n\n 10. Open the Share tab, select Share with specific authorized groups and users, and then add Expel_user to Report Owned by.\n\n 11. Click OK.\n\n 12. Click Done to finish saving the custom report settings.\n\n 13. Search for Custom Signons and Attempted Signons Report for Expel in the search bar and run the report.\n\n 14. On the report screen, open the Actions menu and select Web Service > View URLs.\n\n 15. Click OK and copy the URL from the JSON link.\n\n 16. Remove query parameters from the URL so that it contains `//` and add the Expel_user within the URL: `https:///ccx/service/customreport2//Expel_user/Custom_Signons_and_Attempted_Signons_Report_for_Expel_New`\n\n## Step 6: 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. This link opens the Add Security Device screen directly.\n\n 2. Fill in the fields like this:\n\n![Workday_AddSecDev_2.png](https://support.expel.io/hc/article_attachments/14672349271955/uuid-649b5158-01a1-5127-9e33-43c122b9b525.png)\n\n * Where is your device?: select Cloud.\n\n * Name and Location: any meaningful name (Expel, for example) and location that help you keep track of the integration.\n\n * Client ID: Client ID generated in Step 3.3.\n\n * Client Secret: Client Secret generated in Step 3.3.\n\n * Refresh token: Refresh token generated in Step 3.12.\n\n * REST API endpoint: REST API endpoint copied in Step 3.5.\n\n * Token endpoint: Token endpoint copied in Step 3.5.\n\n * Sign on report endpoint: Endpoint copied in Step 5.16.\n\n * Sign on report username: Username created in Step 1.2.\n\n * Sign on report password: Password created in Step 1.2.\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"} \ No newline at end of file