Ihave my nessus data in splunk, and in my example below I would like to search for all critical findings, and for each of those I would like to correlate the finding with the plugin data and present the details and remediation. The search does not work, and I would like some help if I'm doing this correctly (I'm a complete newbie with the foreach-command).
Have I missed something _really_ obvious or is this one of those scenarios where the business requirement means the rule stays disabled, and we use a mitigation through Sentinel/MDE rulesets to detect and respond?
@sirkillnotalot We've run into this as well. You either block and break Nessus, or audit and allow the activity to occur. We've decided to leave that particular ASR rule in audit mode and alert any time it fires unless the user is our nessus service account.
Thanks for the information. Could you please provide more details about configuring to conect to Tenable.sc or Tenable.io ? I'm struggling to determine how the Agent was installed on Red Hat 7 and 8. I haven't found anything named "Nessus" except in the user directory
No ports used by Tenable/nessus are open on the server. I've checked both active and inactive services but can't locate a service named "Tenable" or "Nessus". Could you suggest a command to help me find the elusive agent and its configuration file? It's perplexing; I can't locate it in /opt or anywhere else.
The server is detected by
cloud.tenable.com, and it reports vulnerabilities. Despite trying all the commands you mentioned, I can't figure out how it's configured. Is there an alternative way it might be set up?
I wrote a Chef cookbook for installing Nessus agent, but it does require that you have the agent link key to enable it. I won't post the entire cookbook here as I originally wrote it for AWS automation, but here are some excerpts that might help you find where it is, installing the RPM and linking it to the Tenable Nessus server.
The next step is to get a vulnerability scan of a vulnerable web application. I wont go into how to use Nessus here, but one of the export options is a ".nessus" which is just an XML file. There is actually too much data in this file, but you can leave it as is. If you want to read it you can remove the sections because all we want are the Reports. For this test, I ran a scan against
google-gruyere.appspot.com, which is an unsecured app available to the internet. Dont do this from AWS or someone will come looking for you, ask me how I know...
Tenable now supports a One-Click deployment of Nessus Agents via Microsoft's Azure portal. This solution provides an easy way to install the latest version of Nessus Agent on Azure virtual machines (VM) (whether Linux or Windows) by either clicking on an icon within the Azure portal or by writing a few lines of PowerShell script.
The most important field is the Nessus Linking Key (nessusLinkingKey, required). It is always required. This document explains where to find it: Retrieve the Tenable Nessus Agent Linking Key (Tenable Nessus Agent 10.4). In the PowerShell interface, specify nessusLinkingKey under -ProtectedSettings so that it will be encrypted by Azure. All other fields are passed unencrypted through -Settings.
You can choose whether to link with Nessus Manager or Tenable.io. In the command-line interface, this is done by setting nessusManagerApp (nessusManagerApp, required) to cloud, or to local. Those are the only two choices.
If you choose Nessus Manager, you must provide the Nessus Manager host (nessusManagerHost) and port number (nessusManagerPort). The extension accepts an IP address or fully qualified domain name.
If you need more help at any point in this article, you can contact the Azure experts on the MSDN Azure and Stack Overflow forums. Alternatively, you can file an Azure support incident. Go to the Azure support site and select Get support. For information about using Azure Support, read the Microsoft Azure support FAQ. If you experience issues with the extension, contact Tenable support.
3a8082e126