IONIX - Add FQDNs To Inventory

IONIX - Add FQDNs To Inventory adds fully qualified domain names (FQDNs) to the IONIX FQDN inventory for:

Assets returned by the selected query or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

When accessing an enforcement action using the API, you must use the backend form of field names.

Use the Syntax Helper to find the correct name. In the enforcement action, enable Configure Dynamic Values and select Syntax Helper.

Note

Not all asset types are supported for all Enforcement Actions.

See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.

See Actions supported for Aggregated Security Findings.

See Actions supported for Software.

Required Fields

These fields must be configured to run the Enforcement Action.

Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
Configure Dynamic Values (optional) - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

Use Adapter connection - Select this option to use credentials from an existing IONIX adapter connection. By default, the first connection is selected.
- When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.
  
  📘
  Note
  To use this option, you must successfully configure an IONIX adapter connection.
Source Field - Enter the name of the asset field that holds the FQDN to submit (default: domain). Axonius reads this field across all adapters on each matched asset, for example domain on Domains & URLs assets or hostname on Devices.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

📘
Note
Assets that do not have a text value in the Source Field fail with a status that names the field. Duplicate values are submitted once. Axonius submits FQDNs in batches of up to 5,000 per request.

Additional Fields

This Enforcement Action does not have additional optional fields.

Connection Settings

💡
Connection and Credentials

When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

Host Name or IP Address - The base domain for the IONIX API. It must contain a prefix of http:// or https://. Do not add any specific endpoints after the domain. For example: https://api.portal.ionix.io.

API Key - An API key associated with an IONIX user account that can add FQDNs to the inventory.

Verify SSL (Optional) (default: enabled) - Selects whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings. This setting is enabled by default on all new adapter settings. If you need to disable SSL verification, make sure you disable this setting.)

HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.

HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

Gateway Name - Select the Gateway through which to connect to perform the action.

APIs

Axonius uses the IONIX API - POST /api/v1/settings/organization-management/manage-fqdns/

Required Ports

Axonius must be able to communicate via the following ports:

TCP port 80/443

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have the necessary permissions to perform this enforcement action.

The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:

The following permissions and requirements are needed:

An IONIX API key. Axonius sends the key as a Bearer token in the Authorization header.
The API key's user account must be permitted to manage the organization's FQDNs. [To Verify] Consult with IONIX for the exact permissions.

To learn more about Enforcement Actions, see Enforcement Actions.

Version Matrix

This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.

Version	Supported	Notes
IONIX API v1	Yes	Uses `/api/v1/settings/organization-management/manage-fqdns/`.

For more details about other enforcement actions available, see Action Library.

Updated about 2 hours ago

Did this page help you?