- 10 Jul 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
PDQ Connect - Deploy Package
- Updated on 10 Jul 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
PDQ Connect - Deploy Package deploys missing software/packages to devices in PDQ Connect for:
- Devices that match the results of the selected saved query, and match the Enforcement Action Dynamic Value statement, if defined, or devices selected on the Devices page.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
General Settings
- Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
- Add description - Add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
- Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
- Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
- Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
This enforcement action runs on Device assets.
Use stored credentials from PDQ Connect Adapter - Select this option to use the PDQ Connect connected adapter credentials.
- When you select this option, the Select Adapter Connection drop-down is available, and you can choose which adapter connection to use for this Enforcement Action.
- When not enabled, see Connection Parameters
Required Fields
These fields must be configured to run the Enforcement Set.
Package ID/Package Version ID - The IDs of the software packages to deploy to the devices. Add a package ID, and then click Enter for each additional package ID.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
Connection Parameters
When Use stored credentials from the PDQ Connect adapter is toggled Off, these fields are required:
- Host Name or IP Address - The hostname or IP address of the [PDQ Connect] server.
- API Key - An API Key associated with a user account that has permissions to fetch assets. For information on how to obtain an API Key, see the PDQ Connect API.
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.
HTTPS Proxy - Connect the adapter to a proxy instead of directly connecting it to the domain.
HTTPS Proxy User Name - The user name to use when connecting to the server using the HTTPS Proxy.
HTTPS Proxy Password - 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 PDQ Connect API.
Endpoint: Swagger UI
- POST /v1/api/deployments - Deploys a package version to the target devices or groups.
For more details about other Enforcement Actions available, see Action Library.