![Hyperproof.Io [Test] Help Center](https://downloads.intercomcdn.com/i/o/xgk1dxp2/757668/427b255f2659cc7e0853d6a00ec1/628914ae2617199b7d999ba797a5305a.png)
📝 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.
Requirements
To connect to Elasticsearch and collect proof your Elasticsearch configuration must meet the following requirements:
An administrator on Elasticsearch must create an API key for use by Hyperproof. 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
When you create a 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.