We offer object storage (Multi-regional, regional, nearline and coldline for achival storage), block storage, RBDMS (Cloud SQL for MySQL & PostgreSQL), NoSQL databases (Cloud Datastore, BigTable), fully managed data warehouse (BigQuery), and a fully managed, mission-critical relational database service built for transactional consistency, high availability, and global scale (Cloud Spanner).
- Fully-managed big data (petabyte-scale) SQL data warehouse
- Managed SQL and highly-scalable managed NoSql databases.
- Resilient, secure, low-cost, storage for binary objects
- Fully-managed global-scale transactionally-consistent SQL database
- NoSql databases which automatically scale to meet your needs
- Fully managed alternatives to Hadoop
- Build on Google's data processing knowhow
- UK Data Centre coming soon.
- Focus on analytics not operational support
- Data storage that grows with you, however much you need
- Highly scalable
- Highly available
- High performance
- Industry standard interfaces
- Access multiple object storage classes using the same API
£0.01 per unit
Cloud Technology Solutions Ltd
|Email or online ticketing support||Yes, at extra cost|
|Support response times||
CTS Support: 1st, 2nd, 3rd line support provided by cloud support engineers and if required technical account manager assigned. Costs for the service start from £5000 and will be based on levels required, response times, resolutions times and hours of availability required. Calls are processed and managed based on standard P1, P2, P3, P4 classifications. Support channels provided include web, phone and email. Service Level Agreement (SLA) is defined and provided to the customer as part of the service design and transition to their live operations environment.
15m Platinum Support, 1 hour Gold Support.
Support service details at https://cloud.google.com/support/
|User can manage status and priority of support tickets||Yes|
|Online ticketing support accessibility||WCAG 2.0 AA or EN 301 549|
|Phone support availability||24 hours, 7 days a week|
|Web chat support||Yes, at an extra cost|
|Web chat support availability||9 to 5 (UK time), Monday to Friday|
|Web chat support accessibility standard||WCAG 2.0 AA or EN 301 549 9: Web|
|Web chat accessibility testing||
Product used is tested using a variety of screen readers and browsers. The following combinations are reported to provide the most accessible experience when using our products:
If you're using Windows, we recommend using NVDA with Firefox.
If you're using OSX, we recommend using VoiceOver with Safari.
|Onsite support||Yes, at extra cost|
|Support levels||1st, 2nd and 3rd line support is provided by cloud support engineers and in some cases a technical account manager is assigned. Costs for the service start from £5000 and will be based on the levels required, response times, resolutions times and hours of availability required. Calls are processed and managed based on standard P1, P2, P3, P4 classifications. Support channels provided include web, phone and email. Service Level Agreement (SLA) is defined and provided to the customer as part of the service design and transition to their live operations environment.|
|Support available to third parties||Yes|
Onboarding and offboarding
CTS are a Google Premier Partner with a proven track record of deploying Google into Central & Local Government, Education, 3rd Sector and Private sector. CTS Provide on-site user training, VIP training, Admin Training, Change Management, Technical & Strategic consultancy, Project Management.
Google Documentation, training, worked examples, best practices, and a free usage tier are available to assist users with getting started on Google Cloud Platform.
Getting Started: https://cloud.google.com/getting-started/
Online Documentation: https://cloud.google.com/docs/
Training Sessions: https://cloud.google.com/training/
Google Developers Codelabs provide a guided, tutorial, hands-on coding experience:
Best practices: https://cloud.google.com/docs/enterprise/best-practices-for-enterprise-organizations
Free tier available: https://cloud.google.com/free/
|End-of-contract data extraction||Google's adoption of open APIs and open source technology allows users to move their data easily between cloud environments and prevent vendor lock-in (https://cloudplatform.googleblog.com/2016/07/how-to-escape-lock-in-with-a-multi-cloud-stack26.html). We offer third party solutions for offline data import/export (https://cloud.google.com/storage/docs/offline-media-import-export), and VM migration through recommended partners (https://cloud.google.com/migrate/). Further to this Articles 7 and 8 of Google Data Processing and Security Terms (https://cloud.google.com/terms/data-processing-terms) states that Google will provide the ability to correct, block, export and delete the Customer Data during the terms of the agreement. To the extent the customer does not have the ability migrate Customer Data to another system, Google will, at Customer’s reasonable expense, comply with any reasonable requests to assist in this.|
|End-of-contract process||On the expiry or termination of the Agreement, after a recovery period of up to 30 days following such expiry or termination, Google will delete the Customer-Deleted Data within a maximum period of 180 days, unless applicable legislation or legal process prevents it from doing so.|
Using the service
|Web browser interface||Yes|
|Using the web interface||
Deploy, scale and diagnose issues via a simple web based interface. You can securely manage and monitor everything that powers your cloud application.
|Web interface accessibility standard||None or don’t know|
|How the web interface is accessible||We are working towards making our products and services more accessible for assistive technology users.|
|Web interface accessibility testing||We are working towards improving the testing of our products and services with assistive technology users.|
|What users can and can't do using the API||
You can automate your workflows in your language by accessing the Google Cloud Platform products from your code. Cloud APIs provide similar functionality to Cloud SDK and Cloud Console, and allow you to automate your workflows by using your favorite language.
|API automation tools||
|Other API automation tools||
|API documentation formats||
|Command line interface||Yes|
|Command line interface compatibility||
|Using the command line interface||
The CLI can be used to access products and services on GCP from the command-line. You can run these tools interactively or in your automated scripts.
|Independence of resources||
GCP runs on top of Google's infrastructure which serves billions of users across many products and services, the integrity and scale of those services ensures that user demand is handled appropriately.
Customer data is logically segregated by domain to allow data to be produced for a single tenant only.
The authorization to provision additional processing capacity is obtained through budget approvals and
managed through internal SLAs as part of an effective resource economy.
Further details - https://cloud.google.com/files/Google-Cloud-CSA-CAIQ-January2017-CSA-CAIQ-v3.0.1.pdf (Section AAC-03.1 and IVS-04.3)
|Infrastructure or application metrics||Yes|
|Other metrics||See documentation for further metrics https://cloud.google.com/products/management/|
|Supplier type||Reseller providing extra features and support|
|Organisation whose services are being resold|
|Staff security clearance||Other security clearance|
|Government security clearance||None|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing locations||
|User control over data storage and processing locations||Yes|
|Datacentre security standards||Complies with a recognised standard (for example CSA CCM version 3.0)|
|Penetration testing frequency||At least every 6 months|
|Penetration testing approach||Another external penetration testing organisation|
|Protecting data at rest||
|Other data at rest protection approach||
Google hard drives leverage technologies like FDE (full disk encryption) and drive locking.
|Data sanitisation process||Yes|
|Data sanitisation type||
|Equipment disposal approach||Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001|
Backup and recovery
|Backup and recovery||Yes|
|Backup controls||This varies between services, users can control what backups are performed via the web interface, CLI or APIs.|
|Datacentre setup||Multiple datacentres with disaster recovery|
|Scheduling backups||Users schedule backups through a web interface|
|Backup recovery||Users can recover backups themselves, for example through a web interface|
|Data protection between buyer and supplier networks||
|Other protection between networks||
Securing data in transit is a high priority for Google. Google was the first major cloud provider to enable HTTPS/TLS by default. Google has also upgraded all our RSA certificates to 2048-bit keys, making our encryption in transit for Cloud Platform and all other Google services even stronger. Perfect forward secrecy (PFS) minimizes the impact of a compromised key, or a cryptographic breakthrough. It protects network data by using a short- term key that lasts only a couple of days and is only held in memory, rather than a key that’s used for years and kept on durable storage.
|Data protection within supplier network||
|Other protection within supplier network||
Google encrypts Cloud Platform data as it moves between our data centers on our private network. Traffic on Google's networks is encrypted.
Availability and resilience
SLAs are service specific:
|Approach to resilience||
Google operates a global network of data centers to reduce risks from geographical disruptions. The link
below includes the locations of our data centers:
Google does not depend on failover to other providers and builds redundancy and failover into its own
Google performs annual testing of its business continuity plans to simulate disaster scenarios that
simulate catastrophic events that may disrupt Google operations.
https://cloud.google.com/files/Google-Cloud-CSA-CAIQ-January2017-CSA-CAIQ-v3.0.1.pdf (section BCR-01)
Google maintains a dashboard with service availability and service issues here:
Identity and authentication
|Access restrictions in management interfaces and support channels||
Google Cloud Identity & Access Management (IAM) lets administrators authorize who can take action on
specific resources, giving you full control and visibility to manage cloud resources centrally. For
established enterprises with complex organizational structures, hundreds of workgroups and potentially
many more projects, Cloud IAM provides a unified view into security policy across your entire
organization, with built-in auditing to ease compliance processes. IAM access policies are defined at the
project level using granular controls of users and groups or using ACLs.
For further information see;
|Access restriction testing frequency||At least once a year|
|Management access authentication||
|Devices users manage the service through||
Audit information for users
|Access to user activity audit information||Users have access to real-time audit information|
|How long user audit data is stored for||Less than 1 month|
|Access to supplier activity audit information||Users have access to real-time audit information|
|How long supplier audit data is stored for||At least 12 months|
|How long system logs are stored for||User-defined|
Standards and certifications
|ISO/IEC 27001 certification||Yes|
|Who accredited the ISO/IEC 27001||Ernst & Young CertifyPoint B.V.|
|ISO/IEC 27001 accreditation date||April 15th 2016|
|What the ISO/IEC 27001 doesn’t cover||See certificate for full list of products covered, anything not listed is not covered. https://cloud.google.com/files/ISO27001_Digital_2016.pdf|
|ISO 28000:2007 certification||No|
|CSA STAR certification||Yes|
|CSA STAR accreditation date||01/01/2017|
|CSA STAR certification level||Level 1: CSA STAR Self-Assessment|
|What the CSA STAR doesn’t cover||
For further information see;
|Who accredited the PCI DSS certification||Reviewed by an independent Qualified Security Assessor|
|PCI DSS accreditation date||19/05/2016|
|What the PCI DSS doesn’t cover||The validation enables PCI Level 1 merchants to use Google Cloud Platform for their processing services.|
|Other security certifications||Yes|
|Any other security certifications||
|Named board-level person responsible for service security||Yes|
|Security governance certified||Yes|
|Security governance standards||
|Other security governance standards||
SSAE16 / ISAE 3402 Type II:
SOC 3 public audit report
FedRamp ATO for Google App Engine
PCI DSS v3.1
EU Data Protection Directive
EU-U.S. Privacy Shield Framework
|Information security policies and processes||
Custom, ISO27001, ISO27017, ISO270018
|Configuration and change management standard||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Configuration and change management approach||In Google production environments, software updates are manually vetted to ensure the stability of the system. Changes are then tested and cautiously rolled out to systems. The details vary somewhat depending on the service being considered, but all development work is separated from the operation systems, testing occurs in a multi-staged fashion in both environments and in dedicated test settings. We can share, under NDA, the SOC2 audit report (based on standards from the International Auditing and Assurance Standards Board), which describes the change management process. Additionally, changes to code go through a process of code review involving additional engineer(s).|
|Vulnerability management type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Vulnerability management approach||
Google administrates a vulnerability management process that actively scans for security threats using a combination of commercially available and purpose-built in-house tools, intensive-automated and manual penetration efforts, quality assurance processes, software security reviews and external audits. The vulnerability management team is responsible for tracking and following up on vulnerabilities. Once a vulnerability requiring remediation has been identified, it is logged, prioritized according to severity, and assigned an owner. The vulnerability management team tracks and follows up frequently until remediated. Google also maintains relationships with members of the security research community to track issues in Google services and open-source tools.
|Protective monitoring type||Supplier-defined controls|
|Protective monitoring approach||
Google’s security monitoring program is focused on information gathered from internal network traffic, employee actions on systems and outside knowledge of vulnerabilities. At many points across our global network, internal traffic is inspected for suspicious behavior, such as the presence of traffic that might indicate botnet connections. Network analysis is supplemented by examining system logs to identify unusual behavior, such as attempted access of customer data. They actively review inbound security reports and monitor public mailing lists, blog posts, and wikis. Automated network analysis helps determine when an unknown threat may exist and escalates to Google security staff.
|Incident management type||Conforms to a recognised standard, for example, CSA CCM v3.0 or ISO/IEC 27035:2011 or SSAE-16 / ISAE 3402|
|Incident management approach||
We have a rigorous incident management process for security events that may affect the confidentiality, integrity, or availability of systems or data. This process specifies courses of action, procedures for notification, escalation, mitigation, and documentation. Google’s security incident management program is structured around the NIST guidance on handling incidents (NIST SP 800–61). Key staff are trained in forensics and handling evidence in preparation for an event, including the use of third-party and proprietary tools. Testing of incident response plans is performed for key areas, such as systems that store sensitive customer information.
|Approach to secure software development best practice||Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v3.0)|
Separation between users
|Virtualisation technology used to keep applications and users sharing the same infrastructure apart||Yes|
|Who implements virtualisation||Supplier|
|Virtualisation technologies used||KVM hypervisor|
|How shared infrastructure is kept separate||
Customer data is logically segregated by domain to allow data to be produced for a single tenant only. Read white paper here : https://cloud.google.com/security/security-design/resources/google_infrastructure_whitepaper_fa.pdf
https://cloud.google.com/files/Google-Cloud-CSA-CAIQ-January2017-CSA-CAIQ-v3.0.1.pdf (Section AAC-03.1)
|Price||£0.01 per unit|
|Discount for educational organisations||No|
|Free trial available||Yes|
|Description of free trial||Any customer may initiate a trial of the service with a $300 free credit. The trial is available outside of the scope of G-Cloud and not offered under G-Cloud terms and conditions.|
|Link to free trial||https://cloud.google.com/free/|
|Pricing document||View uploaded document|
|Terms and conditions document||View uploaded document|