Tenable proof types and permissions
Note
Hyperproof connects to many third-party systems that frequently change, including the system interface. Contact your System Administrator or the third-party provider for assistance meeting the requirements to integrate with Hyperproof and collect the proof you need.
When you create a Hypersync between Hyperproof and Tenable, you can automatically collect proof based on the following services:
Access Control Permissions
This proof type requires
ADMINISTRATOR [64]privileges and should be granted to the Tenable user account used to configure the Tenable Hypersync.Access Groups
Note that Tenable has consolidated and moved user/group management to the Tenable Access Control page. Refer to the official Tenable documentation.
Rules
Security Vulnerabilities
Include Unlicensed Assets
List of Assets
List of Users
User Group
Tip
If you don’t see the same number of vulnerabilities in your proof that you see in the Tenable console, it’s because the Tenable console groups the instances together whereas Hyperproof shows every single instance.
Tip
Sev 0,1,2,3,4 maps to Info, Low, Medium, High, and Critical, respectively.
Requirements
All proof types require an Administrator role. Refer to the official Tenable documentation.
To connect to Tenable you must create an API key in Tenable under My Profile > API Keys > Generate.
Note
Be sure to save the Access Key and Client Secret created when generating the API Key. This information is required when configuring the Hypersync for Tenable.
Connection configuration
When you configure the Hypersync for Tenable for the first time you must provide the following information:
Access Key - This key is provided in Tenable when you generate your API Key.
Client Secret - This secret is provided in Tenable when you generate your API Key.
Additional documentation
Note
You only need to connect Hyperproof to the app once, and then you can create as many Hypersyncs as you need. Additionally, you can create multiple Hypersyncs for a single control or label.