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.

Authentication type: OAuth

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 a Hypersync between Hyperproof and Azure Kubernetes, you can automatically collect the following proof types:

Azure Kubernetes proof types and fields

Proof type	Fields	Testable
List of AKS Clusters	Name, Location, Kubernetes version, API server address, Network type (plugin), Pod CIDR, Service CIDR, DNS service IP, Docker bridge CIDR, Network Policy, Load balancer, Private cluster, Authorized IP Ranges	Yes
List of Deployments	Name, Namespace, Ready, Up-to-date, Available, Age	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.

Note: The Azure Kubernetes Service RBAC Reader and Azure Kubernetes Service Cluster User Role roles need to be assigned to the user’s credentials for the Hypersync to work.

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.