Nessus Agent deployment to campus Jamf instances
Table of Contents
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
Section Content
- Application and Global Settings
- Deploying Microsoft Defender to macOS devices
- Compliance Configuration and Extension Attribute
- EPM Core team audit of Jamf Pro server
- Global Configuration Policies
- Global Security & Compliance policies
- MAC Address Randomization: How it works and What IT needs to know
- macOS Packet Firewall
- Nessus Agent deployment to campus Jamf instances
- Application Usage Logs
- OS Patching: UT Macintosh Security Updates and Reboot Policy
- Automatic install of Code42 in Campus JAMF
- Upgrade to future macOS major releases
- Jamf - Site Administrator Policies
- Application installs and patching
- Installing UT-Track
- Centrally Managed iOS Password Standards
- Jamf - Server Maintenance and Update Process
- Jamf Connect
- Welcome to Jamf - Service Overview
- Common Configuration Profiles for Site Administrators
- Test and pilot