Sweet Security

Sweet Security is a runtime CNAPP platform that provides cloud workload visibility, threat detection, and vulnerability management through eBPF-based sensors.

Use Cases the Adapter Solves

• Cloud Workload Inventory: Gain complete visibility into all cloud workloads monitored by Sweet Security's eBPF-based sensors across your cloud environments, enabling comprehensive asset tracking and management.
• Runtime Security Posture Assessment: Identify devices protected by Sweet Security's runtime detection capabilities to ensure coverage across cloud infrastructure and validate security controls are active.

Asset Types Fetched

• Devices

Data Retrieved through the Adapter

Devices

• Hostname, Device Name

Before You Begin

Required Ports

• TCP port 443 (HTTPS)

Authentication Methods

API Key and Secret Authentication

The adapter authenticates using an API Key and Secret pair to obtain a Bearer token from the /v1/auth/token endpoint. The token is automatically refreshed every hour and used for all subsequent API requests.

APIs

Axonius uses the Sweet Security API. The following endpoints are called:

• POST /v1/auth/token - Authenticate and obtain JWT bearer token
• GET /v1/explorer/schedule - List all explorer schedules
• GET /v1/explorer/schedule/{scheduleId}/reports - Retrieve reports for each schedule (filtered by successful status)
• GET /v1/explorer/report/{reportId}/download - Download device data in NDJSON format

Required Permissions

The following permissions are required:

• API Token Creation - Permissions to create and manage API tokens in Sweet Security
• Explorer Access - Access to Sweet Security's explorer schedules and reports

Note: The exact permission names should be confirmed with your Sweet Security administrator or Sweet Security support, as the API documentation is not publicly available.

Supported From Version

Supported from Axonius version 8.21

Connecting the Adapter in Axonius

1. Navigate to the Adapters page, search for Sweet Security, and click on the adapter tile.
2. Click Add Connection.
3. To connect the adapter in Axonius, provide the following parameters:

Required Parameters

1. Sweet Security Base URL - Base URL for the Sweet Security API. Example: https://eapi.sweet.security
2. API Key - The API Key obtained from Sweet Security's API Tokens settings page. Example: your-api-key-value
3. Secret - The Secret value associated with the API Key, obtained from Sweet Security's API Tokens settings page.

Optional Parameters

1. Verify SSL - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
2. HTTPS Proxy - Connect the adapter to a proxy instead of directly connecting it to the domain.
3. HTTPS Proxy User Name - The user name to use when connecting to the value supplied in Sweet Security Base URL via the value supplied in HTTPS Proxy.
4. HTTPS Proxy Password - The password to use when connecting to the server using the HTTPS Proxy.

To learn more about common adapter connection parameters and buttons, see Adding a New Adapter Connection.

Advanced Settings

The Sweet Security adapter supports the standard Custom Parsing advanced setting for devices, which allows you to customize field mappings and data parsing logic.