LANDesk security management actions

These actions enable you to incorporate LANDesk Management Suite's security management functionality with Process Manager.

LANDesk security management actions are described below.

Note: For all LDMS actions, Core credential set is a required value, and should be the first attribute you fill in. If you select a field to set up the integration with an LDMS core, make sure the field is mapped to a Listener value that matches the Display name you provided for the LDMS core in the Process Manager database utility.

Add vulnerabilities to a group

This action enables you to add vulnerabilities to a security group. When the action occurs in the course of a process, the designated vulnerabilities are added to the specified security group. The updated group with the added vulnerabilities can then be used from the LANDesk Management Suite core server.

• Auditing template: The auditing template to use (see "Auditing templates").
• Core credential set: The display name of the core server (see "Configuring LANDesk cores").
• Name: The name of the action.
• Group name: The security group to add the vulnerabilities to (see "Inserting a custom security group").
• Vulnerability list: The vulnerabilities to add to the group. The ID can be a field (recommended) or a comma-delimited list of the vulnerabilities (see "Inserting vulnerability IDs").

Autofix vulnerabilities

This action enables you to automatically fix vulnerabilities. When the action occurs in the course of a process, it causes LANDesk Management Suite to fix the vulnerability immediately.

• Auditing template: The auditing template to use (see "Auditing templates").
• Core credential set: The display name of the core server (see "Configuring LANDesk cores").
• Name: The name of the action.
• Group name: The name of the security group to fix (see "Inserting a custom security group").

Create custom security group

This action enables you to create a security group. When the action occurs in the course of a process, the custom security group is created on the LANDesk Management Suite core server.

• Auditing template: The auditing template to use (see "Auditing templates").
• Core credential set: The display name of the core server (see "Configuring LANDesk cores").
• Name: The name of the action.
• Group name: The name of the custom security group. In order to avoid duplicate group names, it's recommended that you use a variable as the group name or part of the group name (see "Inserting a custom security group").
• Results: The field in which to place the new custom security group name (see "Inserting fields").

Delete custom security group

This action enables you to delete a custom security group. When the action occurs in the course of a process, the designated custom security group is deleted from LANDesk Management Suite.

• Auditing template: The auditing template to use (see "Auditing templates").
• Core credential set: The display name of the core server (see "Configuring LANDesk cores").
• Name: The name of the action.
• Group name: The name of the custom security group to delete (see "Inserting a custom security group").

Get vulnerabilities

This action enables you to get vulnerabilities. When the action occurs in the course of a process, vulnerabilities are obtained from LANDesk Management Suite.

• Auditing template: The auditing template to use (see "Auditing templates").
• Core credential set: The display name of the core server (see "Configuring LANDesk cores").
• Name: The name of the action.
• Custom filter SQL: A filter that returns vulnerabilities based on the provided SQL statement. This portion of the statement is the "where" clause, and can be left blank if no filtering is needed. (See"Inserting SQL statements").
• Severity: A filter that returns vulnerabilities based on the given severity level. For blocked applications (whether used alone or when included with another type), do not specify a Severity filter, as doing so will prevent either type's vulnerabilities from being downloaded.
• Vulnerability filter: A filter that returns vulnerabilities based on whether they are custom or downloaded vulnerabilities. If custom, "Filter SQL" will be used.
• Vulnerability status: A filter that returns vulnerabilities based on the given vulnerability status.
• Vulnerability type: A filter that returns vulnerabilities based on the given vulnerability type.
• Results: The field in which to place the list of vulnerabilities that are returned as a result of the applied filters (see "Inserting fields"). If no filter is applied, all vulnerabilities are returned. The list is comma-delimited.

Scan/repair vulnerabilities

This action enables you to scan for vulnerabilities on a managed LANDesk device and repair them. When the action occurs in the course of a process, a scheduled task is created in LANDesk Management Suite and run immediately in order to scan or repair the designated device(s).

• Auditing template: The auditing template to use (see "Auditing templates").
• Core credential set: The display name of the core server (see "Configuring LANDesk cores").
• Name: The name of the action.
• Distribution task name: The name assigned to the distribution task in LDMS (see "Assigning a distribution task").
• Group name: The name of the security group to scan for (see "Inserting a custom security group").
• Repair option: Specifies whether to stage or repair the device and which method to use.
• Success percentage: The percentage of devices to need to have their vulnerabilities scanned or repaired in order for the action to be successful.
• Device name: The device to be scanned or repaired (see "Inserting fields").
• Query name: The query name of a LANDesk query that will resolve at least one device, which is accessible by the LANDesk Management Suite user (see "Inserting fields").
• Target option: Specifies whether to target a single device or a query.