Google's best-in-class infrastructure is engineered to handle the most data-intensive work on the planet, giving you the flexibility to scale quickly, while still maintaining admin control. GCP frees you from the overhead of managing infrastructure, provisioning servers, and configuring networks
- Elastic Compute on demand
- Build and configure VMs via secure self-service portal & API
- A range of service levels, VM sizes and licencing options
- Scale one to thousands of virtual machines instances, almost instantly.
- Benefit from built-in virtual networking and load balancing
- Drive for hybrid consistency with on-premises systems.
- Petascale Datawarehousing with BigQuery
- Machine Learning and Artificial Intelligence
- Pay only for capacity you actually use
- Elastic computing. Scale up and down as needed
- Secure and reliable environment
- Run enterprise applications in the cloud with world-class support.
- Build security-enhanced, compliant solutions.
- Maximise the benefit of existing investments using hybrid connections.
- Get true HPC capabilities in the cloud, on demand.
£0.01 per unit
- Free trial available
The Server Labs Ltd.
|Service constraints||See https://cloud.google.com/terms/sla/ to determine applicable constraints based on buyers requirements.|
|Email or online ticketing support||Email or online ticketing|
|Support response times||
Critical: 24x7x365 Response time <= 30 mins Resolution time <= 2 h
High:24x7x365 Response time <=60 mins Resolution time <= 4 h
Medium: Office Hours Response time <= 8 h Resolution time: <= 24 h
Low: Office Hours Response time <= 24 h Resolution time <= 48 h
|User can manage status and priority of support tickets||Yes|
|Online ticketing support accessibility||None or don’t know|
|Phone support availability||9 to 5 (UK time), Monday to Friday|
|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||None or don’t know|
|How the web chat support is accessible||Skype or Google hangout|
|Web chat accessibility testing||N/A|
|Onsite support||Yes, at extra cost|
We offer support in either 24x7 and 9x5 modes.
Cost varies by the amount of services deployed
The service has a preventative component, with periodic maintenance, monthly reporting and continuous improvement of the infrastructure, and a corrective component, when problems occur in the system covered by this support contract.
Once an issue has been received by The Server Labs, the procedure takes the following steps.
• Verification of the issue and escalation to second level support.
• Communication to customer of the solution to be undertaken.
• Restoration of any service lost working with the DBA and or engineer assigned to the project.
• Restoration of any data lost working with the DBA assigned to the project.
• Update of the system documentation if necessary.
• Closeout of the issue with description of actions undertaken.
|Support available to third parties||Yes|
Onboarding and offboarding
There are plenty of tutorials for getting started on GCP
In addition, The Server Labs can offer consultancy to help onboard users.
|Other documentation formats||Online videos and interactive learning portals|
|End-of-contract data extraction||Customer are able to remove their data at any time through the same means they uploaded. Either over their network (internet or cloud interconnect) or via the Cloud Storage Import/Export services. https://cloud.google.com/storage/docs/offline-media-import-export|
|End-of-contract process||Please see https://cloud.google.com/terms/sla/ and https://cloud.google.com/terms/|
Using the service
|Web browser interface||Yes|
|Using the web interface||Manage and deploy services via the Google Cloud Portal. See https://cloud.google.com/products/|
|Web interface accessibility standard||WCAG 2.0 AA or EN 301 549|
|Web interface accessibility testing||GCP works best in Chrome and can benefit from accesibility add-ons.|
|What users can and can't do using the API||
Users are able to utilise the GCP APIs for each service within the platform. Anything that can be done through the console can be done via the API.
As well as REST APIs, Language SDKs exist for C#,Go,Java,Node.js,PHP,Python and Ruby
|API automation tools||
|API documentation formats||HTML|
|Command line interface||Yes|
|Command line interface compatibility||
|Using the command line interface||
The Google Cloud SDK https://cloud.google.com/sdk/ provides a powerful command line that can work with the following platform services:
Cloud ML Engine
|Independence of resources||GCP represents a hyper-scale public cloud service with minimum SLAs|
|Infrastructure or application metrics||Yes|
|Supplier type||Not a reseller|
|Staff security clearance||Other security clearance|
|Government security clearance||Up to Baseline Personnel Security Standard (BPSS)|
|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 once a year|
|Penetration testing approach||Another external penetration testing organisation|
|Protecting data at rest||
|Other data at rest protection approach||See https://cloud.google.com/security/encryption-at-rest/|
|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|
|What’s backed up||
|Backup controls||The user can control their own backups using scheduled API calls.|
|Datacentre setup||Multiple datacentres with disaster recovery|
|Scheduling backups||Users schedule backups through a web interface|
|Data protection between buyer and supplier networks||
|Other protection between networks||For data in transit, Google uses industry-standard secure transport protocols, such as TLS/SSL, between user devices and Google datacenters. You can enable encryption for traffic between your own virtual machines (VMs) and your users. With Google VPC, you can use the industry-standard IPsec protocol to encrypt traffic between your corporate VPN gateway and GCP as well as between the VMs located on your Virtual Network.|
|Data protection within supplier network||
|Other protection within supplier network||
Google uses a multi-layered security model
Privacy is also respected for GDPR
Availability and resilience
|Guaranteed availability||See https://cloud.google.com/terms/sla/|
|Approach to resilience||Please see https://cloud.google.com/security/infrastructure/|
|Outage reporting||Please see https://status.cloud.google.com/|
Identity and authentication
|Access restrictions in management interfaces and support channels||
Google Cloud Identity & Access Management (IAM) lets administrators authorise who can take action on
specific resources, giving you full control and visibility to manage cloud resources centrally. For
established enterprises with complex organisational 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||15/04/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||03/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||See https://cloud.google.com/security/compliance/pci-dss/|
|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||
EU Model Contract Clauses
UK NCSC Cloud Security Principles
|Information security policies and processes||
Your data is critical to your business, and you take great care to keep it safe and under your control. We want you to feel confident that taking advantage of G Suite and Google Cloud Platform doesn’t require you to compromise on security or control of your business’s data.
|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, prioritised 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||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|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 behaviour, such as the presence of traffic that might indicate botnet connections. Network analysis is supplemented by examining system logs to identify unusual behaviour, 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||Please see https://cloud.google.com/security/infrastructure/|
|Price||£0.01 per unit|
|Discount for educational organisations||No|
|Free trial available||Yes|
|Description of free trial||Please see https://azure.microsoft.com/en-us/free|
|Pricing document||View uploaded document|
|Skills Framework for the Information Age rate card||View uploaded document|
|Service definition document||View uploaded document|
|Terms and conditions document||View uploaded document|