When scans are launched the policy is encrypted with a one use random 128-bit key and transported using TLS v1.2 with a 4096-bit key. Scan Credentials – Are stored inside of a policy which is encrypted within the containers AES-256 global key.

In Indexes – Index data is stored on encrypted media using at least one level of AES-256 encryption. Tenable does not back up any data to physical off-site media or physical systems. All replication is done within via the provider. In Backups / Replication – Volume snapshots and data replicas are stored with the same level of encryption as their source, no less than AES-256. The controller uses the key to encrypt the policy, which includes the credentials to be used during the scan The scanner requests the policy from the platform If there is a job, the platform generates a random key of 128-bits Scanners contact the platform every 30 seconds Scanners uses this key to authenticate back to the controller when requesting jobs, plugin updates and updates to the scanner binary The platform generates a random key of 256 bit length for each scanner connected to the container and passes that key to scanner during the linking process This removes the need for firewall changes and allows the customer to control the connections via firewall rules. Traffic is encrypted via SSL communication using TLS 1.2 with a 4096-bit key. Tenable.io Sensor Communication – Traffic from the sensors to the platform is always initiated by the sensor and is outbound-only over port 443.

In Transport – Data is encrypted in transport using TLS v1.2 with a 4096-bit key (this includes internal transports). Some data classes include a second-level of per-file encryption. You can also view the security in the FAQ:Īll data in all states in the Tenable.io platform is encrypted with at least one level of encryption, using no less than AES-256.Īt Rest – Data is stored on encrypted media using at least one level of AES-256 encryption.

How to use nessus safely