Aqua Workload Protection
  • 18 Nov 2024
  • 2 Minutes to read
  • Contributors
  • Dark
    Light

Aqua Workload Protection

  • Dark
    Light

Article summary

Aqua Security Workload Protection provides services which secure containers, Kubernetes, serverless functions, and VMs against evolving cloud native threats with runtime security, powered by real-world threat intelligence.

Integration Method: API

Tables: Detection Finding, Vulnerability Finding, Device Inventory, Scan Activity

DataBee connects to Aqua Workload Protection APIs to get incidents, vulnerabilities, scan history, risky containers, and other workload related information.

This integration has been tested against the Aqua Enterprise API v2.

Aqua Workload Protection Configuration

Aqua user requirements

You need an Aqua user to authenticate with the REST API before using any of the API endpoints. This user must be configured as follows:

  • Role: At least one of the user's roles includes one or more permission sets and application scopes, which meet the requirements defined below. There are no other requirements.

  • Permission set(s): Your applications will generally require either read-only and/or write access to certain types of Aqua Platform objects (e.g., images or security policies). In your permission set(s), assign View Only and/or Edit permissions, respectively, to these types of objects. Refer to Permission Sets for information on creating and configuring permission sets.

  • Application scope(s): Your applications will be able to access Aqua Platform objects within the application scope(s) associated with the user that has been authenticated. Refer to Application Scopes for information on creating and configuring application scopes.

Generate a CSPM API key and secret
  1. Login to your Aqua Workload Protection dashboard account and navigate to Account Management.

  1. Under the Account Management page, navigate to Settings > API Keys.

  1. Click Generate Key.

  2. Copy and save the API Key and Secret values.

  1. In the API Keys screen, click Edit from the vertical ellipsis on the same row as the newly generated API key.

  1. In the Global Permissions section, disable the Enable global admin permission option.

  1. In the Granular Permissions section, enable the tokens:readwrite and roles:assign options

  1. Click Save.

DataBee Configuration

  1. Log into the DataBee console and navigate to the Data > Datasources tab. Click on the Add New Data Source button.

  1. Search for the Aqua Workload Protection option using the search bar in the Add New Data Source page.

  1. Select the API Ingest option and enter appropriate owner details in the Configure Data source form. Click on Next.

  1. In the configuration dialog, enter the following

    • Authorization Method: HMAC Auth

    • Integration Key: Paste the previously generated API key

    • Secret Key: Paste the previously generated Secret

  1. Replace the <auth_endpoint> placeholder in the 1st URL with the token url endpoint based on your geographical region.

  1. Replace <instance> placeholder in the remaining API URL(s) with the environment ID of your Aqua Security account instance. The environment ID can be found in the base URL which will be provided by the Aqua Support team.

  2. Click Submit


Was this article helpful?

What's Next
Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.
ESC

Eddy AI, facilitating knowledge discovery through conversational intelligence