Anomaly Detection
Perks
Powered By GitBook
CMP Data Access Policy
Security and Data Access Policy for Cloud Management Platform
This document outlines what customer data Cloud Management Platform accesses, why, what data is stored, and how we do that. If you're not using DoiT Cloud Management Platform for the following features, this article doesn't apply.
    Enterprise Cloud Accounts (formerly Sandboxes)
    Google Cloud Rightsizing
    Google Kubernetes Engine Metering
    BigQuery FinOps
    Google Cloud and/or AWS Proactive Quota Monitoring
    AWS ASG Optimizer
TL;DR: We only access data required for Cloud Management Platform (CMP) functionality. We store and handle your data in a secure way, encrypted in transit and at rest. We do not provide the data to any 3rd party, with the exceptions required for core CMP functionality and listed below.

What we access

The list below denotes all permissions we require to your Google Cloud Organization and why.
While this provides us permissions to read info about your resources, none of these allow us to access your data, such as GCS objects or a BigQuery table's data.
The following permissions are used to get information about your Google Cloud resource hierarchy and correlate it with billing.
1
resourcemanager.organizations.get
2
resourcemanager.organizations.getIamPolicy
3
resourcemanager.folders.get
4
resourcemanager.folders.list
5
resourcemanager.projects.get
6
resourcemanager.projects.list
Copied!
The following permission is required for CMP Sandbox functionality (create Google Cloud projects)
1
resourcemanager.projects.create
Copied!
The following permissions are required to provide you with Rightsizing Recommendations for your Google Compute Engine instances across your entire organization
1
recommender.computeInstanceMachineTypeRecommendations.list
2
compute.instances.list
Copied!
The following set of permissions required for implementing Rightsizing recommendations:
1
compute.instances.setMachineType
2
compute.instances.stop
3
compute.instances.start
Copied!
The following permissions are used to check the status (and enable if required) Google Cloud APIs (such as the Recommender API)
1
serviceusage.services.enable
2
serviceusage.services.get
3
serviceusage.services.list
4
serviceusage.services.use
Copied!
The following permissions are required for the BigQuery FinOps Dashboard to get actionable cost optimization recommendations for your Google BigQuery environment.
1
logging.sinks.create
2
bigquery.datasets.create
3
logging.sinks.get
4
bigquery.datasets.get
5
bigquery.tables.get
6
bigquery.tables.list
7
bigquery.jobs.get
8
bigquery.jobs.list
9
bigquery.jobs.listAll
10
bigquery.jobs.create
Copied!
The following permissions are required to list your clusters for their GKE usage metering export configuration used to enable GKE reports in cloud analytics.
1
container.clusters.list
2
container.clusters.get
Copied!
The following policies/permissions are required to proactively monitor AWS Quotas, access to the billing data, as well as the security posture of your AWS accounts:
1
arn:aws:iam::aws:policy/SecurityAudit
2
arn:aws:iam::aws:policy/AWSSavingsPlansReadOnlyAccess
3
arn:aws:iam::aws:policy/job-function/Billing
4
support:DescribeTrustedAdvisorCheckSummaries
5
support:DescribeTrustedAdvisorCheckRefreshStatuses
6
support:DescribeTrustedAdvisorChecks
7
support:DescribeSeverityLevels
8
support:RefreshTrustedAdvisorCheck
9
support:DescribeSupportLevel
10
support:DescribeCommunications
11
support:DescribeServices
12
support:DescribeIssueTypes
13
support:DescribeTrustedAdvisorCheckResult
14
trustedadvisor:DescribeNotificationPreferences
15
trustedadvisor:DescribeCheckRefreshStatuses
16
trustedadvisor:DescribeCheckItems
17
trustedadvisor:DescribeAccount
18
trustedadvisor:DescribeAccountAccess
19
trustedadvisor:DescribeChecks
20
trustedadvisor:DescribeCheckSummaries
Copied!
AWS ASG Optimizer analyzes your Auto Scaling Groups based on cost and usage and get recommendations to replace on-demand EC2 instances with Spot instances.
1
autoscaling:BatchDeleteScheduledAction
2
autoscaling:BatchPutScheduledUpdateGroupAction
3
autoscaling:CreateOrUpdateTags
4
autoscaling:UpdateAutoScalingGroup
5
autoscaling:Describe*
6
cloudformation:ListStacks
7
cloudformation:Describe*
8
ec2:CreateLaunchTemplate
9
ec2:CreateLaunchTemplateVersion
10
ec2:ModifyLaunchTemplate
11
ec2:RunInstances
Copied!

What we store

We only store data required for CMP functionality.
    Cloud Billing exports- required for core Billing functionality; stored in BigQuery
    User information - required for core CPM functionality; stored in Firestore
    Assets created via using CMP (Invoices, Billing Profiles, etc.) - required for core CMP functionality; stored in Firestore
    Contracts - required for core CMP functionality; stored in Google Cloud Storage
    Service Account Keys - required for core CPM functionality; stored in Firestore and encrypted with KMS

How we handle and store your data

All data we handle are encrypted in transit using industry-standard protocols like HTTPS (TLS).
All data we store are encrypted at rest:
    Google BigQuery - using Google-managed encryption keys and Advanced Encryption Standard (AES)
    Google Firestore - using Google-managed encryption keys and AES
    Google Cloud Storage - using Google-managed encryption keys and AES
    Service Account Keys - encrypted using Google Cloud KMS and stored in Google Secret Manager

Who can access your data?

DoiT International employees in customer-facing roles, such as Account managers and Support engineers, can access your data using the CMP platform. Only a small team of core CMP developers is able to access your data directly in the underlying storage.
Service Account keys are only used by backend systems to retrieve relevant data from GCP. Only a small team of core CMP developers has access to the KMS keys used for encryption and would be able to decrypt the keys.

3rd parties

We do not provide your data to any 3rd party, with the exceptions listed below required for core CMP functionality.
    CMP Support - We use ZenDesk as a backend for support ticketing functionality. All ticket-related data are stored in ZenDesk and retrieved using ZenDesk APIs [1].
    Payments - We use Stripe for payments. All payment-related data (such as Credit card or bank account details) are stored in the Stripe platform and used via Stripe APIs [2].

Compliance

EU and GDPR Compliance - we have many customers in the European Economic Area and we handle your data in compliance with the General Data Protection Regulation (GDPR) [3].
We're working towards completing our SOC 2 Type 2 audit. We anticipate the Type 2 report being available during Q2, 2021.

External references

Last modified 6d ago