Repositories

Repositories are databases within Tenable Security Center that contain vulnerability data. You can share repositories with users and organizations based on admin-defined assets. Repositories provide scalable and configurable data storage. Optionally, you can share repository data between multiple Tenable Security Centers.

Note: The maximum repository size is 64 GB. For best performance, Tenable recommends splitting repositories larger than 32 GB.

When adding a local repository, you designate storage within Tenable Security Center for different types of vulnerability data (identified by IPv4 addresses, IPv6 addresses, agents, or mobile scanners). Scanners attached to a Tenable Security Center populate your local repositories with vulnerability data. For more information, see Local Repositories.

When adding an external repository, you access a local repository from another Tenable Security Center:

  • Remote repositories allow you to share repository data from one Tenable Security Center deployment to your primary Tenable Security Center deployment via an SSH session. By default, Tenable Security Center uses ECDSA keys for remote repository authentication.

    Note: When you upgrade to Tenable Security Center 6.5.x from version 6.4.x or earlier, benchmark results will not appear until after the next repository sync.

  • Offline repositories allow you to share repository data from one Tenable Security Center deployment to your primary Tenable Security Center deployment via manual export and import (a .tar.gz archive file). You can combine data from several repository files into a single offline repository by importing multiple files to the offline repository.

External repository data is static and used solely for reporting purposes. For more information, see External Repositories.

For more information, see Add a Repository and Manage Repositories. For information about Tenable Security Center repository data encryption, see Encryption Strength.

Tip: If you need to remove data from a repository (for example, to remove retired asset data or to resolve a license issue), see the knowledge base article.