> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/d-j-integrations/fortinet/fortinet-forticnapp-formerly-lacework-setup-for-workbench.md).

# Fortinet FortiCNAPP (formerly Lacework) Setup for Workbench

## Step 1: Enable Console Access <a href="#h_01hh4e4k3pkdtqyfdwakep6k4r" id="h_01hh4e4k3pkdtqyfdwakep6k4r"></a>

Create a user in FortiCNAPP for Workbench or create an SSO user for Workbench with access to FortiCNAPP.

Having read-only access to the interface of your technology allows Expel to dig deeper during incident investigations. Our device health team uses this access to investigate potential health issues with your tech. For more information, see [Why Expel Asks for Console Access](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md).

## Step 2: Generate API credentials <a href="#h_01hh4e4k3p1rhwrcg0sv34qe69" id="h_01hh4e4k3p1rhwrcg0sv34qe69"></a>

To integrate the technology with Workbench, you need to create secure credentials to the API.

FortiCNAPP provides a combination of API Access keys and tokens to be used by clients and client applications to access the FortiCNAPP API. API access key IDs and secret access keys are created using the FortiCNAPP Console. Temporary access (bearer) tokens, used by clients, are created using the FortiCNAPP API.

Only administrators can create API access keys, with a limit of two per user. An API access key doesn't expire but can be disabled or deleted. After creation, administrators can download and securely store the secret key.

To create an API key:

1. In FortiCNAPP, navigate to **Settings > Configuration > API Keys**.
2. On the Service user API keys tab, click **+ Add New**.
3. Type a **name** for the key and an optional description and click **Save**.
4. Download the generated API key file and open it in an editor to view. ([Fortinet API key docs reference](https://docs.fortinet.com/document/forticnapp/latest/administration-guide/155000/api-keys))

## Step 3: Add FortiCNAPP as a Security Device in Workbench <a href="#h_01hh4e4k3psaj6v7d2e5mjwnm9" id="h_01hh4e4k3psaj6v7d2e5mjwnm9"></a>

Now that you have the correct access configured and noted the credentials, you can integrate your tech with Workbench.

1. [Log in to Workbench](https://workbench.expel.io/auth/login?orig=%2F).
2. In the side menu, navigate to **Settings > Security Devices**.
3. At the top of the page, click **Add Security Device**.
4. Search for "FortiCNAPP" and select the integration.
5. Complete the following fields:
   * **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName FortiCNAPP”; this name will display in Workbench under the Name column, and is a text string that you can filter on.
   * **Location** - enter the location of your integration, for example “cloud;” this is also a text string that you can filter on, so we recommend being consistent with location naming across your Expel integrations.
   * **URL** - enter the host name or IP address of the FortiCNAPP management interface. Device IP can be found in the FortiCNAPP console under **Dashboard > General Information > MGT IP Address**.
   * **API key** - enter the secret generated in [Step 2](#h_01hh4e4k3p1rhwrcg0sv34qe69).
   * **ADOM name** - specify your ADOM name. If not specified, it will default to `root`.
6. Click **Save**.
7. On the console access screen, select **Set up now**.
8. In the Console Login area, type these details:
   * **Console URL** - enter the console URL from the Server address in the Connection Settings area above. At the end of the URL, type **/login**.
   * **Username** and **Password** - enter the credentials you created in [Step 1](#h_01hh4e4k3pkdtqyfdwakep6k4r).
   * **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 Customer Success Manager (CSM) or to support.
9. Click **Save**.

Your device should be created successfully within a few seconds. A few reminders:

* After your connection is healthy, it will take some time for your device to begin polling and receiving data.
* To check on the status, select the downward arrow for your device in the first column and choose **View details**.
* Polling will happen first; data will be received after that. **You must refresh the page to see updates.**
* If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, [contact our support team for help](/support/how-to-reach-us.md).
* To check if alerts are coming through, navigate to **Dashboards > Alert Analysis**. Scroll to the device you want to check, and select the **Expel Alerts** tab to reveal more alert information. It can take 36 to 72 hours for alerts to appear after setup, as we [tune your device](/workbench-reference/alerts/how-expel-alerts-work.md#device-tuning).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.expel.io/connect-your-technology/d-j-integrations/fortinet/fortinet-forticnapp-formerly-lacework-setup-for-workbench.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.