Nessus Agent deployment to campus Jamf instances
- Katelyn Russell
Nessus deployment to all Macs is enabled in the campus Jamf instances using policy GLOBAL - Nessus agent install/link which uses the script GLOBAL-nessus-install-link
The policy is set to run once a day. It will do a link check and report status. If Nessus is not linked, it will link it. If it is not installed, it will install it, then link it.
The script outputs the result of "nessuscli agent status" to the policy log.
Prerequisites
- inventory.plist
For the script to work, the site must have a policy for creating an inventory.plist file, which contains the Nessus Group to be linked
 - see Policy and script for creating a utexas inventory.plist file
EPM is available to IT Support Organizations (ITSOs) with any endpoint management questions. If you have a question about a specific endpoint client, please reach out to your local endpoint client support organization.
- Welcome to Jamf - Service Overview
- Application and Global Settings
- Global Security & Compliance policies
- macOS Packet Firewall
- Upgrade to future macOS major releases
- EPM Core team audit of Jamf Pro server
- Compliance Configuration and Extension Attribute
- Automatic install of Code42 in Campus JAMF
- Global Configuration Policies
- Deploying Microsoft Defender to macOS devices
- OS Patching: UT Macintosh Security Updates and Reboot Policy
- Nessus Agent deployment to campus Jamf instances
- MAC Address Randomization: How it works and What IT needs to know
- Jamf Connect
- Jamf - Site Administrator Policies
- Application installs and patching
- Installing UT-Track
- Centrally Managed iOS Password Standards
- Test and pilot
- Jamf - Server Maintenance and Update Process
Welcome to the University Wiki Service! Please use your IID (yourEID@eid.utexas.edu) when prompted for your email address during login or click here to enter your EID. If you are experiencing any issues loading content on pages, please try these steps to clear your browser cache.