Actions38
- APM Actions
- ASM Actions
- Authentication Actions
- LTM Actions
- System Actions
ASM → Update Signatures
AI-generatedSummary
Starts an ASM background task on the BIG-IP that updates the attack signature database, either from an already-uploaded signature file or via live update.
Inputs
- Update Fields > Filename — Path to a signature file already uploaded to the BIG-IP. Sent as
filenamein the request body. If left empty, the description says a live update is used. - Update Fields > Is User Defined — Boolean, default false. Sent as
isUserDefinedin the request body. Set it to true when the file contains user-defined signatures. - Request Options — Node-level settings: batching (items per batch and interval), ignore SSL issues, proxy, and timeout (default 10000 ms).
Output shape
The JSON response from POST /mgmt/tm/asm/tasks/update-signatures, one item per input item. This is normally the task record that the BIG-IP creates.
The call only starts the task. Its completion is not awaited. To track progress, use the Check Task Status operation with task type 'Update Signatures' and the task ID from the response. The exact response fields are not defined in the node source. Authentication and host come from the bigIpF5Api credential.
Examples
Example 1: Pull the latest signatures from F5 via live update
Leave the Update Fields collection empty, so no filename is sent.
Example 2: Install a signature file that was uploaded earlier
Add Filename with the file's path on the BIG-IP. Leave Is User Defined off.
Example 3: Load custom user-defined signatures
Set Filename to the uploaded file and set Is User Defined to true.