What permissions and scopes are needed?

Hypersyncs use the minimum required permissions to collect the proof requested. Where possible, Hypersyncs use read-only permissions, roles, and APIs. For Oauth connections, Hyperproof asks the user to authorize the minimum scopes required. Where apps have read-only scopes, Hyperproof uses them.

Minimum permissions take different forms in different apps. In some cases, there are fine-grained permissions that can allow/deny access to particular resources or using specific APIs. In other cases, permissions are granted through roles or other mechanisms. Hyperproof aims to always use the minimum permissions following the app model for roles and permissions. Your IT admin will be familiar with how your company handles permissions for each application.

Below is an example that shows what AWS permissions are needed for different Hypersyncs. You can see that all of the permissions are read-only (Get, List, Describe) and correspond closely with the proof that is created.