CM EPM Managed Nessus

The EPM Managed Nessus script contains code to evaluate and perform several actions based on different existing conditions locally. Not all may be executed, but all are evaluated.

• Repair a related registry issue.

• Detect the availability of Active Directory as this requires the data held in the following OU attributes from each ITSO to succeed.

  • a. utexasEduAzureSingle1 OU attribute - EPM managed Nessus requires that a Department’s 4-character department code be documented appropriately in Active Directory in the utexasEduAzureSingle1 OU attribute. Also known as "ownedby".

  • b. utexasEduAzureSingle2 OU attribute - Endpoints managed by TRecs or LAITS must use the utexasEduAzureSingle2 OU attribute, as appropriate. Also known as "supportedby".

  • c. utexasEduAzureMulti1 OU attribute - All Nessus groups currently used to install and link Nessus agents, one per line, must be documented in the utexasEduAzureMulti1 OU attribute. ‘Windows’ is no longer required as a Nessus Group.

• Uninstall all detectable instances of a Nessus Agent.

• Unlink existing Nessus Agents given the following criteria:

  • a. Nessus agent is installed, and Nessus groups are available from the AD attribute, but are not recorded locally.

  • b. Nessus agent is installed, Nessus groups are available from the AD attribute, and are recorded locally, but they do not match.

  • c. Nessus agent is installed and linked but the link status is ‘disconnected for more than 24 hours’, ‘authentication error’, or ‘not linked to a manager’

• Install latest Nessus Agent using group info from the AD attribute and recording the groups used to link

• Link an unlinked Nessus Agent using group info from the AD attribute and recording the groups used to link

• Set the ‘update_hostname’ Nessus Agent property to ‘yes’.