Appsbroker Ltd

Google Cloud Platform

Google Cloud Platform (GCP) is a suite of powerful cloud services offered by Google. Appsbroker utilises GCP to create bespoke solutions. Our capabilities span Application Development, Data Analytics and Machine Learning, HCT/HPC and Collaboration. Appsbroker work for a range of industries including research, manufacturing, media and entertainment, finance and more.


  • Elastic; Compute, Storage, Networking, IaaS & PaaS on demand
  • Highly configurable VMs, range of sizes and OS supported
  • 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
  • Peta-scale Data Lakes or Data Warehousing
  • Machine Learning and Artificial Intelligence, from auto to custom


  • Pay as you consume pricing
  • Fully elastic, scale up or down as required
  • Secure, trusted and resilient environment
  • Supported platform with agreed Service Level Objectives
  • Highly secure and compliant platform to build upon
  • Maximise the benefit of existing investments using hybrid connections
  • Get true HPC capabilities in the cloud, on demand


£0.01 a unit a month

Service documents


G-Cloud 12

Service ID

2 6 8 7 5 6 9 9 4 8 2 5 5 3 1


Appsbroker Ltd Appsbroker Sales
Telephone: 01793 391 420

Service scope

Service constraints
Service Level Objectives for Google Cloud Platform can be found here:

Terms of use can be found here:
System requirements
Public or private connectivity to Google Cloud

User support

Email or online ticketing support
Yes, at extra cost
Support response times
Average response times are under 30 minutes for all tickets, although as per standard SLA only P1 priority tickets have this as initial response time SLA.
User can manage status and priority of support tickets
Online ticketing support accessibility
None or don’t know
Phone support
Phone support availability
24 hours, 7 days a week
Web chat support
Web chat
Web chat support availability
24 hours, 7 days a week
Web chat support accessibility standard
None or don’t know
How the web chat support is accessible
Chat is available as a chat client, web interface and also as part of the ticketing service.
Web chat accessibility testing
N/A managed by Google
Onsite support
Yes, at extra cost
Support levels
Bespoke upon request
Support available to third parties

Onboarding and offboarding

Getting started
Google provides extensive documentation for each service that runs on Google Cloud Platform (, there is also a helpful getting started guide:

Our Professional Services can work directly with you to also assist on this journey, anything from Best Practice guides to hands-on training and knowledge share of both the platform, but also methodologies and ways of working.
Service documentation
Documentation formats
  • ODF
  • PDF
  • Other
Other documentation formats
Google Docs
End-of-contract data extraction
Customers own and have full access to their data and can extract of download in a variety of formats
End-of-contract process
Full ownership and cost of running would be handed to the client

Using the service

Web browser interface
Using the web interface
Manage and deploy services via the Google Cloud Portal. See
Web interface accessibility standard
None or don’t know
How the web interface is accessible
Any modern web browser
Web interface accessibility testing
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
  • Ansible
  • Chef
  • OpenStack
  • SaltStack
  • Terraform
  • Puppet
API documentation
API documentation formats
  • Open API (also known as Swagger)
  • HTML
Command line interface
Command line interface compatibility
  • Linux or Unix
  • Windows
  • MacOS
Using the command line interface
The Google Cloud SDK provides a command line capability across the platform and allows programmable control over the platform and many of its services. Full details of the SDK can be found here:


Scaling available
Scaling type
  • Automatic
  • Manual
Independence of resources
Google operates its cloud platform at a global scale, additionally, single tenanted instances are available on the platform
Usage notifications


Infrastructure or application metrics
Metrics types
  • CPU
  • Disk
  • HTTP request and response status
  • Memory
  • Network
  • Number of active instances
Reporting types
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request


Supplier type
Reseller providing extra support
Organisation whose services are being resold

Staff security

Staff security clearance
Other security clearance
Government security clearance
Up to Security Clearance (SC)

Asset protection

Knowledge of data storage and processing locations
Data storage and processing locations
  • United Kingdom
  • European Economic Area (EEA)
  • EU-US Privacy Shield agreement locations
  • Other locations
User control over data storage and processing locations
Datacentre security standards
Managed by a third party
Penetration testing frequency
At least every 6 months
Penetration testing approach
Another external penetration testing organisation
Protecting data at rest
  • Physical access control, complying with CSA CCM v3.0
  • Physical access control, complying with SSAE-16 / ISAE 3402
  • Physical access control, complying with another standard
  • Encryption of all physical media
  • Scale, obfuscating techniques, or data storage sharding
  • Other
Other data at rest protection approach
Google uses several layers of encryption to protect customer data at rest in Google Cloud Platform products.
Google Cloud Platform encrypts customer content stored at rest, without any action required from the customer, using one or more encryption mechanisms. Google's Key Management Service is redundant and globally distributed.
Data stored in Google Cloud Platform is encrypted at the storage level using either AES256 or AES128.
Data sanitisation process
Data sanitisation type
  • Explicit overwriting of storage before reallocation
  • Deleted data can’t be directly accessed
  • Hardware containing data is completely destroyed
Equipment disposal approach
In-house destruction process

Backup and recovery

Backup and recovery
What’s backed up
  • All data contained on the platform
  • All machine configuration
  • All platform configuration
Backup controls
Configured individually (automated or manually) gainst each service
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
  • Users contact the support team

Data-in-transit protection

Data protection between buyer and supplier networks
  • Private network or public sector network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Bonded fibre optic connections
  • Legacy SSL and TLS (under version 1.2)
  • Other
Other protection between networks
Networks can be protected by using either a VPN or a dedicated pipe; Interconnect.
Data protection within supplier network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Legacy SSL and TLS (under version 1.2)
  • Other
Other protection within supplier network
GCP data is encrypted while it is "in transit", whether it is travelling over the Internet between the customer and Google, or moving within Google as it shifts from one data centre to another. We encrypt this data between Google and our customers using HTTPS with forwarding secrecy.

Availability and resilience

Guaranteed availability
Each of Google's services that run on the platform come with Service Level Objectives (SLOs), these can be found here:
Approach to resilience
Please see
Outage reporting
Availability and status of each service running on Google can be found here:

Identity and authentication

User authentication
  • 2-factor authentication
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google apps)
  • Dedicated link (for example VPN)
  • Username or password
Access restrictions in management interfaces and support channels
All users have to authenticate using Google single sign-on. For internal users, we enforce two-factor authentication.
Access restriction testing frequency
At least every 6 months
Management access authentication
  • 2-factor authentication
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Dedicated link (for example VPN)
  • Username or password
Devices users manage the service through
  • Dedicated device on a segregated network (providers own provision)
  • Dedicated device over multiple services or networks
  • Any device but through a bastion host (a bastion host is a server that provides access to a private network from an external network such as the internet)
  • Directly from any device which may also be used for normal business (for example web browsing or viewing external email)

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
Access to supplier activity audit information
Users have access to real-time audit information
How long supplier audit data is stored for
How long system logs are stored for

Standards and certifications

ISO/IEC 27001 certification
Who accredited the ISO/IEC 27001
ISO/IEC 27001 accreditation date
What the ISO/IEC 27001 doesn’t cover
Full coverage
ISO 28000:2007 certification
CSA STAR certification
CSA STAR accreditation date
CSA STAR certification level
Level 1: CSA STAR Self-Assessment
What the CSA STAR doesn’t cover
See link to Google CSA STAR compliance.
PCI certification
Who accredited the PCI DSS certification
Refer to certification
PCI DSS accreditation date
What the PCI DSS doesn’t cover
This certification allows PCI Level 1 merchants to use Google Cloud Platform for processing payment
Other security certifications
Any other security certifications
  • SOC 1, SOC 2, SOC 3
  • FedRamp
  • SSAE16 / ISAE 3402 Type II
  • ISO 27017 and 27018

Security governance

Named board-level person responsible for service security
Security governance certified
Security governance standards
  • CSA CCM version 3.0
  • Other
Other security governance standards
Google Cloud Platform conforms to the following standards (ref:
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.


Operational security

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."

Secure development

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
Who implements virtualisation
Virtualisation technologies used
Other virtualisation technology used
Predominantly Kubernetes, Velostrata though others are supports, full information can be found here:
How shared infrastructure is kept separate
Using Authentication, Sharding and Encryption, no data or services can be shared unless explicitly allowed.

Google Virtual Private Cloud (VPC) can additionally be used to isolate network traffic

Energy efficiency

Energy-efficient datacentres
Description of energy efficient datacentres
Google data centres are among the most energy efficient data centres in the world. See link detail Google Data Centre policy also


£0.01 a unit a month
Discount for educational organisations
Free trial available
Description of free trial
Access to Google Cloud Platform in order to gain access to a number of Google Cloud Platform (GCP) applications
Link to free trial

Service documents