Sectigo - Delete Custom Deployment Location

Sectigo - Delete Custom Deployment Location removes a deployment location from an SSL certificate in Sectigo Certificate Manager 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 stored credentials from the Sectigo adapter - Select this option to use credentials from an existing Sectigo 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 a Sectigo adapter connection.
Location ID - Enter the ID of the deployment location to delete.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

📘
Note
The action runs on Sectigo SSL certificate assets. Axonius reads the Sectigo certificate ID from each asset. Assets without a certificate ID fail with the status Missing SSL Certificate ID. If the location does not exist, for example because it was already deleted, the action fails for that asset with a "not found" status.

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 of your Sectigo Certificate Manager server (default: https://cert-manager.com).

Username - The Sectigo username Axonius uses to authenticate.

Password - The password for the Sectigo user.

Customer URI - The customer URI of your Sectigo Certificate Manager account.

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 Sectigo Certificate Manager API - DELETE /api/ssl/v2/{sslId}/location/{locationId}

Required Ports

Axonius must be able to communicate via the following ports:

TCP port 443 (HTTPS)

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:

A Sectigo Certificate Manager account that can authenticate with a username, password, and customer URI.
Permission to manage SSL certificates and their deployment locations. Confirm the exact Sectigo role with your Sectigo administrator.

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
Sectigo API v2	Yes	Uses `/api/ssl/v2/{sslId}/location/{locationId}`.

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

Updated 14 days ago

Did this page help you?