How does a Hyperproof user create a new Hypersync?
The first step in creating a Hypersync is selecting the app where the data for the proof will be pulled from. We use the term application/app to reference sources like AWS or GitHub.
If this is the first time a Hypersync is created for an app, the user is prompted to establish a connection between Hyperproof and the app. The user needs to enter their credentials that authorize Hyperproof to access the app, as well as limit the permissions/scope granted.
After the connection to the app has been established, future Hypersyncs may simply reuse it. Connections can also be shared. One Hyperproof user can establish the connection, and then decide what other user may create Hypersyncs with that connection. This workflow is helpful because there is no need to re-enter credentials.
App credentials are typically issued by the organization's IT admin. The rest of this document is designed to help both the Hyperproof user and the IT admin understand how Hypersyncs work and the steps necessary to get them up and running.
Note
Workflow
Select the app where the proof data will be pulled from, e.g. Azure or GitHub.
Provide credentials if a connection has not already been created.
Select the specific proof you want to collect.
Note
For any given app, many different proof types can be generated to satisfy different compliance requirements and controls. At this time, there is no way to see a sample of the proof types in the app without actually setting them up. If you can’t find the proof you need, reach out to us in our forum.
Tip
Many proof types have criteria to help narrow down the information that is collected. For example, you may see criteria specific to both the app and the proof such as user types, repositories, and severity. The criteria used is shown in the proof.
Configure:
The Hypersync's schedule (when it runs)
Whether the proof should be versioned or added as a new file
The output format (PDF or Excel)
A name for the proof (which is also the name of the Hypersync)