π¨ IMPORTANT π¨
Please note, when selecting the DeviceName
this must be unique to avoid issues when scanning.
Please note, that every organisation has a different environment, different device/software management processes and very different requirements so we can only provide a generic guide β we cannot account for every eventuality, but we hope this helps.
Get your agent information
Go to your Intruder account > Targets > Add Target > Internal Target > Mass Deployment, and then retrieve the required information (Prefix and Key):
You will be presented with the following screen:
You can then grab the installer file by going to your Intruder account > Targets > Add Target > Internal Target > Single agent
When the following modal appears, enter Windows, the OS version, and any device name (this is not needed as the device names will be uniquely generated as part of the deployment).
After clicking 'Download agent', you can then download and save the .msi
file.
Installation instructions modal
Make sure you download the Nessus Agent to a clean folder on your computer (in this case and for the remainder of this guide we will refer to the agent MSI file as
NessusAgent-10.1.1-Win32.msi
please note that the10.1.1
part may change as new versions are released).Take a copy of the command and keep it handy so you can extract the information you need to deploy to multiple agents.
In our example the command we will refer to is:
msiexec /i "NessusAgent-10.1.1-Win32.msi" NESSUS_SERVER="cloud.tenable.com:443" NESSUS_KEY=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef NESSUS_NAME=01234567-89ab-cdef-0123-456789abcdef_MYDEVICE /qn
Prepare your .intunewin package
Download the Microsoft Intune Win32 App Packaging Tool Microsoft via Github:
Create a folder and download your NessusAgent MSI file (
NessusAgent-10.1.1-Win32.msi
from the previous stage) in to that folder; if it's already in it's own folder don't worry about this step.Create an installation file (named
Install.cmd
) in the same folder as yourNessusAgent-10.1.1-Win32.msi
file, and add the following installation command on a single line:
msiexec /i "NessusAgent-10.1.1-Win32.msi" NESSUS_SERVER="cloud.tenable.com:443" NESSUS_KEY=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef NESSUS_NAME=01234567-89ab-cdef-0123-456789abcdef_%ComputerName% /qn
Now, make sure that you:
Replace the
NessusAgent-10.1.1-Win32.msi
with the exact name of the MSI you downloaded previouslyReplace the
NESSUS_KEY
value with the one in the command you copied from the portal in the previous stageReplace the
NESSUS_NAME
value with the one in the command you copied from the portal in the previous stage, but add_%ComputerName%
to the end of theNESSUS_NAME
value (%ComputerName%
is a placeholder that will be automatically replaced with the name of computer at installation time).
Save the
Install.cmd
file and closeOpen a Command Prompt
cmd.exe
as Administrator (right-click on Command Prompt and "Run as Administrator")Run
IntuneWinAppUtil.exe
from the Intune Win32 App Packaging Tool that you downloaded previously.Follow the steps to create the
.intunewin
package that can be used to deploy to multiple systems:Please specify the source folder:
This should be the folder where yourNessusAgent-10.1.1-Win32.msi
andInstall.cmd
files are locatedPlease specify the setup file:
This should be theNessusAgent-10.1.1-Win32.msi
Please specify the output folder:
This should be the location you want to save the.intunewin
package, such asC:\Temp
Deploy your .intunewin package
In Intune you will need to add a Windows app (Win32)
When creating the app select
App package file
and upload your.intunewin
package fileAdd your App Information if needed:
Name
Description
Publisher
etc.
Select
Program
and change theInstall command
setting toInstall.cmd
Make sure the
Uninstall command
setting is sensibleMake sure your App requirements are appropriate
Make sure the
Detection rules
contains a manually configured detection rule:Rule type:
this should be set toMSI
MSI product code:
this should be pre-populated
Make sure the
Return codes
are appropriate, they should be pre-populatedAdd your app
You should now be able to deploy your app to a test system and validate that the agent calls back to your Intruder portal account.
If you come unstuck, it might be worth reviewing the other help article found here.