To perform agent scanning, Tenable.sc fetches agent scan results from agent-capable Nessus Manager or Tenable.io instances. Using Nessus Agents for scanning reduces network usage and allows devices to maintain their scan schedules even when disconnected from the network. Tenable.sc fetches these results for review with other acquired information about the host and network.
You can configure one or both methods of fetching agent scan results in Tenable.sc:
Agent scans fetch results from agent scans you add and launch in Tenable.sc. When you add an agent scan in Tenable.sc, Tenable.sc creates a corresponding agent scan in an instance of Nessus Manager that you linked to Tenable.sc. When you launch an agent scan in Tenable.sc, Tenable.sc launches the corresponding scan in Nessus Manager, then imports the results into Tenable.sc.
You can create agent scans in Tenable.sc using
only the Basic Agent Scan template. For more information, see Agent Scan and Policy Templates in the Nessus Agent Deployment and User Guide.
For more information, see Agent Scans.
Agent synchronization jobs fetch results from agent scans you previously created and launched in Nessus Manager or Tenable.io.
Agent synchronization jobs can fetch results from agent scans configured in Nessus Manager or Tenable.io using any agent scan template.
For more information, see Agent Synchronization Jobs.
To configure agent scanning:
Tip: If you want to configure an agent scan, use an agent-capable Nessus Manager instance as a Nessus scanner in Tenable.sc.
- Configure Nessus Agents in either Nessus Manager or Tenable.io, as described in Deployment Workflow in the Nessus Agent Deployment and User Guide.
- Add your agent-capable Nessus Manager or Tenable.io instance as a Nessus scanner in Tenable.sc, as described in Nessus Scanners.
- Add one or more agent repositories in Tenable.sc, as described in Add a Repository.
- Do one or both of the following:
What to do next: