Data Aggregation in a Hybrid Environment
This section briefly identifies areas to consider when aggregating Nessus Agent data from Nessus Manager into Tenable.sc repositories. It is important to note that communications to the Nessus Manager for data retrieval initiate from Tenable.sc. Once Nessus Agent data has been imported, all normal Tenable.sc operations such as vulnerability analysis, compliance, and workflow automation apply.
- Carefully consider agent group size to reduce the volume of data being imported into Tenable.sc at a given time. You should limit the number of agents per scan in Nessus Manager or Tenable.io to 1,000 agents. If you import large amounts of data to Tenable.sc while parallel operations are occurring, Tenable.sc performance may be impacted.
- Properly plan the number of Nessus scanners and Nessus Managers connected to Tenable.sc, seeking guidance from Tenable technical support staff if needed.
- Properly plan the number of concurrent scans to include agent scans (agent data retrieval process), concurrent users, number of dashboards configured, and frequency/type of reports operating on a Tenable.sc, seeking guidance from Tenable technical support staff if needed.