|
|
@@ -208,11 +208,17 @@ In Nessus manager, the agent scans are scheduled. Agents are linked to the Nessu
|
|
|
|
|
|
When you are setting up a new server and you see this error for the Nessus agent, it means the Nessus Manager already has your agent in its inventory. To fix this, log into the Nessus Manager > Sensors > Find your agent > click on X to delete. Restart the agent to have it enroll again. Creds for Nessus Manager are in Vault.
|
|
|
|
|
|
-Error message:
|
|
|
+Error message:
|
|
|
```
|
|
|
[error] [agent] Link fail: [409] An agent with the uuid '53543366-b28f-41de-937c-81d736e93a90' already exists
|
|
|
```
|
|
|
|
|
|
+## Tenable.sc Scanning Strategy
|
|
|
+
|
|
|
+Tenable does not have a way to pull host information from AWS. To keep things dynamic and not require us to update IP lists, a host discovery scan is setup with all possible IPs. After the host discovery scan runs, the dynamic assets lists should pick up the correct IPs and scan only those IPs. This keeps the scan times shorter.
|
|
|
+
|
|
|
+XDR Host Discovery (scan) -> Systems that have been Scanned (assets list) -> XDR OS Discovery (scan) -> All XDR IP / Agents -> XDR Vulnerability Scan
|
|
|
+
|
|
|
## Scan Troubleshooting
|
|
|
|
|
|
To run a diagnostic scan on a single IP, put the IP as the target of the scan and as the diagnostic target. You can put anything in the password. Note that you will not be able to view the results only send them to support.
|
Brad Poulton