knowledge-base / article_10853659813395.json
intertwine-expel's picture
Upload 155 files
a6ab323
raw
history blame
2.79 kB
{"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"}