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 in meeting the requirements to integrate with Hyperproof and collect the proof you need.
Hyperproof supports collecting proof from Elasticsearch. When you create a Hypersync between Hyperproof and Elasticsearch, you can automatically collect the following proof types:
Elasticsearch proof types and fields
Proof type | Fields | Testable |
User List | Profile Id, User Name, Full Name, Email Address | Yes |
This Hypersync supports importing a user list for an access review. See Importing a list of application users with a Hypersync for more information.
Automated control tests
Hyperproof has a collection of preconfigured, ready-to-deploy, customizable automated tests spanning a wide array of integrated services and proof types. For information on available tests for proof collected by this Hypersync, see the Automated control test library and Using the automated control test library.
Requirements
To connect to Elasticsearch and collect proof, your Elasticsearch configuration must meet the following requirements:
An Elasticsearch administrator must create an API key for Hyperproof to use. This is done under Management > Security > API keys > Create API key. Ensure that the key has at least user list read access.
Connection configuration
Authentication type: Custom
Custom authentication parameters: Base URL, API Key
Note: Service accounts are recommended for integrations between Hyperproof and other applications. Service accounts are easier for your IT admin to maintain and ensure that your integrations will continue running when individuals change roles or leave the company.
When you create an Elasticsearch Hypersync for the first time, you must provide the following information:
Base URL - this is the URL that your organization uses to access Elasticsearch. If you are using a cloud service like Elastic Cloud, the base URL is provided by the service and looks something like: https://your-cluster-id.region.provider.elastic-cloud.com
API Key - enter the API Key that Hyperproof should use to access Elasticsearch.
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.
Certain cloud services offer specialized IP filtering options in their cloud consoles to lock down specific cloud API endpoints for security and compliance. You can use the Hyperproof static IP addresses to allow communication between Hyperproof Hypersyncs and your cloud service.
If your instance is on a private network, add the static IP address for the Hyperproof instance where your organization is hosted to your company's allowlist.
Hyperproof US IP addresses - 20.184.128.53, 52.159.252.1
Hyperproof EU IP addresses - 9.141.172.46, 4.185.45.100
Hyperproof Gov IP addresses - 4.155.77.155, 4.155.78.5, 4.155.8.97
See Hyperproof instances for more information.