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.
When you create a Hypersync between Hyperproof and Google Cloud Platform (GCP), you can automatically collect the following proof types:
Google Cloud Platform proof types and fields
Service | Proof type | Fields | Testable |
Cloud Storage | Bucket Encryption | Bucket Name, Encryption Type, Encryption Key | Yes |
Cloud Storage | Bucket Lifecycle Rules | Bucket Name, Bucket, Action, Age, Created Before, Custom Time Before, Days Since Custom Time, Days Since Noncurrent Time, Is Live, Matches Prefix, Matches Storage Class, Matches Suffix, Noncurrent Time Before, Num Newer Versions | No |
Cloud Storage | Bucket Replication | Bucket Name, Location Type, Location | Yes |
Cloud Storage | Bucket Retention Settings | Bucket Name, Retention Period, Effective Time, Locked | No |
Cloud Storage | Bucket Settings | Bucket Name, Location Type, Location, Versioning, Encryption Type, Encryption Key | Yes |
Cloud Storage | Bucket Versioning | Bucket Name, Versioning | Yes |
Compute Engine | Firewall Rules | Name, Network, Direction, Log Config, Disabled | Yes |
Compute Engine | List of Disk Encryption Settings | ID, Name, Zone, Disk Encryption Key, Source Snapshot Encryption Key | Yes |
Compute Engine | List of Images | Name, Source Image, Location, Disk Size, Family, Architecture, Creation Time, Labels | Yes |
Compute Engine | List of Instance Groups | Name, Instances, Template, Autoscaling, Zone, Creation Time | Yes |
Compute Engine | List of Instance Templates | Name, Machine type, Image, Disk type, Creation Time | Yes |
Compute Engine | List of Running Instances | Name, Instance template Network Interfaces: Internal IP, External IP | No |
Compute Engine | List of Snapshots | Name, Location, Snapshot Size, Creation Time, Source Disk, Disk Size | Yes |
Compute Engine | Minimum TLS Version | Name, Minimum TLS version, Profile, Creation Time | Yes |
IAM | Custom Project Roles | Title, Name, Description | Yes |
IAM | Project Members | Resource Type, Resource, Principal, Role | Yes |
Kubernetes Engine | List of Clusters | Zone, Project, Status, Name, Location, Mode, Number of nodes, Total vCPUs, Total memory, Labels Networking: Private cluster, network, Subnet, Pod address range, Service access range, Intranode visibility, NodeLocal DNSCache, HTTP Load Balancing, Subsetting for L4 Internal Load Balancers, Control plane authorized networks, Network policy, Dataplane V2 Security: Binary authorization, Shielded GKE nodes, Confidential GKE node, Workload identity, Workload identity namespace, Legacy authorization | No |
Kubernetes Engine | List of Pod Security Policies | Zone, Cluster, Run As User, Run As Group, Run As Non Root, FS Group, FS Group Change Policy, Name, Privileged, Allow Privilege Escalation, Readonly Root FS Run as User: Rule, Ranges Run as Group: Rule, Ranges FS Group: Rule, Ranges | Yes |
Kubernetes Engine | List of Workloads | Zone, Name, Status, Type, Pods, Namespace, Cluster | Yes |
SQL | Backup Configuration | Project, Instance Name, Backup Location, Backup Enabled, Start Time, Retained Backups, Point In Time Recovery, Transaction Log Retention Days | Yes |
SQL | Backup Runs | Project, Instance Name, Identifier, Kind, Type, Start Time, End Time, Location, Status | Yes |
VPC | List of Networks | ID, Name, Subnets, MTU, Mode, Global Dynamic Routing | No |
VPC | List of Subnets | Region, Name, ID, Network, State, IPv4 CIDR, IPv6 CIDR | No |
This Hypersync supports importing a user list for an access review. See Importing a list of application users with a Hypersync for more information.
Kubernetes Engine
List of Pod Security Policies
Note: This proof type is compatible only with Kubernetes version 1.22 or higher. If you use a lower version of Kubernetes, the proof will not be generated.
Kubernetes has deprecated PodSecurityPolicies in version 1.21. See this Kubernetes article for information on migrating from PodSecurityPolicies to the built-in PodSecurity admission controller. Migrate from PodSecurityPolicy to the Built-In PodSecurity Admission Controller.
Setting up Google Cloud Platform
The Hypersync for Google Cloud Platform can collect data from a single project or from all projects within an organization or resource folder. Use the sections below to create a Hyperproof service account and assign it the appropriate roles and permissions to collect Google Cloud Platform proof.
Note: Some sections of this document contain separate steps depending on whether you are collecting data from a single project or multiple projects. Be sure to follow the correct set of steps.
Step 1: Creating a Hyperproof service account
Open a Google Cloud Platform project.
Single project: Open the project you want to sync.
Multiple projects: Open any project in your organization. Remember which one; you'll turn on two APIs in it in Step 3.
From the left menu, select IAM & Admin and then select Service Accounts.
Click Create Service Account.
Enter a name, such as Hyperproof Service Account, and optionally a description.
Click Done.
Step 2: Creating an IAM role for the service account
The role gives the service account read-only access to the data the Hypersync collects. When configuring the IAM role, add these permissions to the role:
|
|
If you're syncing multiple projects, also add these five permissions:
resourcemanager.folders.getresourcemanager.folders.getIamPolicyresourcemanager.organizations.getresourcemanager.organizations.getIamPolicyresourcemanager.projects.list
Adding the IAM role for a single project
From the left menu, select IAM & Admin and then select Roles.
Click Create Role.
Enter a name, such as Hypersync Role.
Click Add Permissions, add the permissions listed above, and then click Create.
From the left menu, select IAM.
Click Grant Access.
In New principals, enter the service account's email address. It appears once you start typing.
From Select a role, select the role you just created.
Click Save.
Adding the IAM role for multiple projects
From the left menu, select IAM & Admin and then select Roles.
From the resource selector at the top of the page, select your organization.
Click Create Role.
Enter a name, such as Hypersync Org Role.
Click Add Permissions, add all of the permissions listed above, including the five extra permissions, and then click Create.
From the left menu, select IAM.
From the resource selector, select the organization or folder that contains the projects you want to sync.
Click Grant Access.
In New principals, enter the service account's email address. It appears once you start typing.
From Select a role, select the role you just created.
Click Save.
Step 3: Turning on APIs
In Google Cloud Platform, search for each API below and turn it on. Do this before you create the Hypersync, or it may fail with an unspecified error.
Turning on APIs for a single project
Turn on these APIs in the project you're syncing:
Identity and Access Management (IAM) APICloud Resource Manager APICloud SQL Admin APICompute Engine APICloud Storage APIKubernetes Engine API
Turning on APIs for multiple projects
Turn on these APIs in the project where you created the service account:
Identity and Access Management (IAM) APICloud Resource Manager APICloud SQL Admin API
Turn on these APIs in every project you're syncing:
Compute Engine APICloud Storage APIKubernetes Engine API
Step 4: Creating a JSON key
From the left menu, select IAM & Admin and then select Service Accounts.
Select the service account you created in Step 1.
Click Keys.
Click Add Key and then select Create new key.
Select JSON and click Create. The JSON file downloads to your computer.
Important: The JSON key gives access to your Google Cloud Platform data. Store it securely, and delete the downloaded file after you connect Hyperproof.
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.
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.
Connection configuration
Authentication type: Custom
Custom authentication parameters: Private JSON 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.
