Recently Viewed Topics
Reporting and Traditional Network Scanning (Tenable.sc)
The primary purpose of the reporting tier was to allow for centralized analytics and reporting of data collected from the Nessus Agents and existing traditional network scans. Dashboards, analytics, reports, and Assurance Report Cards are leveraged on this tier.
The following processes and uses take place in Tenable.sc.
- Nessus Manager and Tenable.io were added to Tenable.sc as an “agent capable” scanners.
- Agent scans in Tenable.sc were configured to retrieve Nessus Agent scan results from Nessus Manager and Tenable.io.
- Agent data was placed in new repositories according to existing data models.
- Analytics, dashboards, reports, and Assurance Report Cards in Tenable.sc were leveraged for all assessment types (Agent and Network Scanning).
- Tenable.sc required additional data repositories to support the Nessus Agent results. Tenable recommended that Initech establish multiple new repositories in Tenable.sc for Nessus Agent results, because combining agent and network assessment results in the same repository can cause reporting challenges.
- Initech needed to perform a full analysis on their current Tenable.sc hardware configuration to determine if additional CPU/RAM/HD was required for the additional data resulting from importing Nessus Agent scan results.
- Initech needed to evaluate their existing traditional scan structures/policies to ensure limited data overlap once Nessus Agent assessments were implemented and data imported into Tenable.sc.
Design assumptions included:
- Initech will establish multiple repositories to store Nessus Agent scan results.
- Initech will establish 60-100 agent jobs to retrieve Nessus Agent scan results from Tenable.io and Nessus Manager.
- Initech will evaluate current infrastructure to determine if additional CPU/RAM/HDD is required.
- Initech will evaluate existing scan structures/policies to limit data overlap.