Mobilise Cloud Services Ltd

Google Cloud Platform (GCP) Managed Service

Mobilise utilise Google Cloud Platform to provide a complete managed service for customers. Using GCP services, Mobilise provide IaaS/PaaS & FaaS cloud-based services to deliver scalable, secure and highly available hosting solutions, letting customers focus on delivering new digital services to the cloud.

Features

  • Service Desk - Change/Problem/Incident Management
  • Customer Obsession - delivering reviews and satisfaction surveys
  • Cloud Centre of Excellence – delivering innovative solutions improving services
  • Google Cloud Partner
  • Enablement through DevOps; automating build, test and deployments CICD
  • Infrastructure and Application capabilities to transition services to GCP
  • Security Event Management
  • 24/7 Next Generation Monitoring and Alerting
  • 24x7x365 monitoring, alerting and SLA
  • GCP services: SaaS, PaaS, IaaS, FaaS Data and AI/ML services

Benefits

  • Google Cloud Partner
  • Pay-as-you-go cloud consumption model
  • Certified experts, delivering well architected design solutions
  • DevOps and Migration capabilities utilised across government
  • Secure cloud based solution with robust access management controls
  • Next generation logging, monitoring and alerting utilising machine learning
  • Capacity and Cost Management processes for further savings
  • Security vetted UK based team
  • ISO27001 security and ISO9001 quality certified service
  • ITIL aligned best practice processes

Pricing

£0.01 to £0.01 a virtual machine a month

Service documents

Request an accessible format
If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at james.carnie@mobilise.cloud. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 12

Service ID

7 0 6 7 9 2 3 4 9 8 7 7 2 6 7

Contact

Mobilise Cloud Services Ltd James Carnie
Telephone: 07817317694
Email: james.carnie@mobilise.cloud

Service scope

Service constraints
Please refer to https://cloud.google.com/compute/docs/ for more information on service constraints.
System requirements
See https://cloud.google.com/compute/docs/

User support

Email or online ticketing support
Email or online ticketing
Support response times
Our standard SLA response time is 15 minutes and the level of SLAs can be tailored for each customer based on a priority system. Service availability can be arranged to cover a standard business working week 9-5 or a fully managed 24/7 SLA.
User can manage status and priority of support tickets
Yes
Online ticketing support accessibility
WCAG 2.1 AA or EN 301 549
Phone support
Yes
Phone support availability
24 hours, 7 days a week
Web chat support
No
Onsite support
Onsite support
Support levels
As a Google Cloud Partner, Mobilise are expertly placed to off GCP support and advice to your business.
Our ISO27001 Service Desk is manned 24x7x365 by GCP certified engineers - most of whom maintain an SC clearance. This allows us to deal with sensitive Government information using our quality and information security processes.
Our Design Solution, Migration & DevOps capabilities are utilised across government and utilise well-architected patterns to ensure we meet the highest standards. Mobilise have a wealth of experience delivering and supporting Government solutions using highly repeatable, reliable, automated patterns using infrastructure as code.
Next generation monitoring automatically identifies new resources, scales to meet demand and uses machine learning to identify outliers, providing insightful statistical information.
Support levels can be tailored to meet the customers requirements - which will be reported on and managed by our engagement lead following customer obsession policies.
Support available to third parties
Yes

Onboarding and offboarding

Getting started
Google provide a range of learning materials including detailed documentation, blogposts, tutorials, learning videos, online courses, training days, hands on labs and bootcamps. Google also offer support from the public sector team allowing Government to contact Google for further advice.

Mobilise can also provide additional onboarding and training support to complement the AWS material already provided.

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:
https://codelabs.developers.google.com/
Best practices: https://cloud.google.com/docs/enterprise/best-practices-for-enterprise-organizations
Service documentation
Yes
Documentation formats
  • HTML
  • PDF
End-of-contract data extraction
If resources have been defined using Infrastructure as Code, then users will have the appropriate data in their source control systems. Other conventional tools used for backing up or extracting data can be used on virtual machines (such as rsync). Databases can have data extracted using the softwares proprietary tooling to create 'data dumps'. GCP also provides services for migrating machines/data out of GCP.
End-of-contract process
Buyer may terminate the relationship with Supplier for any reason by (i) providing Supplier with notice and (ii) closing Buyers account for all services for which Supplier provide an account closing mechanism. Buyers pay for the services they use to the point of account termination.

Using the service

Web browser interface
Yes
Using the web interface
Users will have access to the Google Cloud Console, where they can perform changes through the GCP Web Interface.

Users will have access to Mobilise Service Desk portal which allows them to raise incidents and changes. It also allows customers the option to look through historical data, generate reports and customise their view.
Web interface accessibility standard
WCAG 2.1 AA or EN 301 549
Web interface accessibility testing
N/A
API
Yes
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 favourite language.

https://cloud.google.com/apis/
API automation tools
  • Ansible
  • Chef
  • SaltStack
  • Terraform
  • Puppet
  • Other
API documentation
Yes
API documentation formats
  • HTML
  • PDF
  • Other
Command line interface
Yes
Command line interface compatibility
  • Linux or Unix
  • Windows
  • MacOS
  • Other
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.

https://cloud.google.com/sdk/

Scaling

Scaling available
Yes
Scaling type
  • Automatic
  • Manual
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 authorisation 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)
Usage notifications
Yes
Usage reporting
  • API
  • Email
  • SMS

Analytics

Infrastructure or application metrics
Yes
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

Resellers

Supplier type
Not a reseller

Staff security

Staff security clearance
Conforms to BS7858:2012
Government security clearance
Up to Security Clearance (SC)

Asset protection

Knowledge of data storage and processing locations
Yes
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
Yes
Datacentre security standards
Supplier-defined controls
Penetration testing frequency
At least every 6 months
Penetration testing approach
Another external penetration testing organisation
Protecting data at rest
Other
Other data at rest protection approach
Google Cloud Platform encrypts customer content stored at rest, without any action required from the customer, using one or more encryption mechanisms.

Data for storage is split into chunks, and each chunk is encrypted with a unique data encryption key. These data encryption keys are stored with the data, encrypted with ("wrapped" by) key encryption keys that are exclusively stored and used inside Google’s central Key Management Service. 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.

https://cloud.google.com/security/encryption-at-rest/default-encryption/
Data sanitisation process
Yes
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
Yes
What’s backed up
  • Databases
  • Virtual Machines
  • Kubernetes Clusters
  • Elastic Clusters
  • Cloud Resources (Virtual Machines, Managed Databases etc.)
  • File Storage
Backup controls
Users can control backup schedules by applying tagging to specific resources or by scheduling changes through email, phone and a web portal.
Datacentre setup
Multiple datacentres with disaster recovery
Scheduling backups
Users contact the support team to schedule backups
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)
Data protection within supplier network
Other
Other protection within supplier network
Google employs several security measures to help ensure the authenticity, integrity, and privacy of data in transit.

Google encrypts and authenticates all data in transit at one or more network layers when data moves outside physical boundaries not controlled by Google or on behalf of Google. Data in transit inside a physical boundary controlled by or on behalf of Google is generally authenticated but not necessarily encrypted.

Depending on the connection that is being made, Google applies default protections to data in transit. For example, Google secures communications between the user and the Google Front End (GFE) using TLS.

https://cloud.google.com/security/encryption-in-transit/

Availability and resilience

Guaranteed availability
GCP has a raft of SLAs for hundreds of services which can be viewed on their site at https://cloud.google.com/terms/sla
Approach to resilience
Google operates a global network of data centres to reduce risks from geographical disruptions. The link below includes the locations of Google data centres:
http://www.google.com/about/datacenters/inside/locations/

Google does not depend on failover to other providers and builds redundancy and failover into its own global infrastructure.

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
Outage reporting
Google maintains a dashboard with service availability and service issues here:
https://status.cloud.google.com/

Identity and authentication

User authentication
  • 2-factor authentication
  • Identity federation with existing provider (for example Google apps)
  • Limited access network (for example PSN)
  • Dedicated link (for example VPN)
  • Username or password
  • Other
Other user authentication
A built-in Password Monitor is visible to the end user upon password
creation and to the System Administrators of the tenant whom can decide to force a password change on any user that is later detected to have a password that is weak. Google's native authentication has
protections in place that would detect a brute force attack and challenge the user to solve a Captcha and would auto lock the account if suspicious activity is detected. The tenant's System Administrators can
reset that account for the end user.
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. IAM access policies are defined at the project level using granular controls of users and groups or using ACLs.

Support services are only provided to authorized customer administrators whose identities have been verified in several ways. Google access is monitored and audited by our dedicated security, privacy, and internal audit teams.

https://cloud.google.com/iam/
https://cloud.google.com/security/overview/whitepaper#administrative_access
https://cloud.google.com/files/Google-Cloud-CSA-CAIQ-January2017-CSA-CAIQ-v3.0.1.pdf
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)

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
User-defined
Access to supplier activity audit information
You control when users can access audit information
How long supplier audit data is stored for
At least 12 months
How long system logs are stored for
At least 12 months

Standards and certifications

ISO/IEC 27001 certification
Yes
Who accredited the ISO/IEC 27001
Axelos Global Best Practice
ISO/IEC 27001 accreditation date
24/01/2014
What the ISO/IEC 27001 doesn’t cover
N/A
ISO 28000:2007 certification
No
CSA STAR certification
Yes
CSA STAR accreditation date
01/01/2016
CSA STAR certification level
Level 5: CSA STAR Continuous Monitoring
What the CSA STAR doesn’t cover
https://cloud.google.com/security/compliance/csa-star
PCI certification
Yes
Who accredited the PCI DSS certification
https://cloud.google.com/security/compliance/pci-dss
PCI DSS accreditation date
01/01/2016
What the PCI DSS doesn’t cover
https://cloud.google.com/security/compliance/pci-dss
Other security certifications
No

Security governance

Named board-level person responsible for service security
Yes
Security governance certified
Yes
Security governance standards
  • ISO/IEC 27001
  • Other
Other security governance standards
Cyber Essentials Plus; ISO 27017
Information security policies and processes
https://cloud.google.com/security/compliance

Custom, ISO27001, ISO27017, ISO270018

Operational security

Configuration and change management standard
Supplier-defined controls
Configuration and change management approach
Configuration changes are raised through change requests to the Mobilise ISO 27001 service desk, where a series of approvals must be met before the change is delivered. Changes can be tracked by customers and rollback plans are always included.

Changes are assessed for potential security impacts by GCP certified architects using a peer to peer review mechanism before final approval from authorised party.
Vulnerability management type
Supplier-defined controls
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.

https://cloud.google.com/security/overview/whitepaper#vulnerability_management
Protective monitoring type
Supplier-defined controls
Protective monitoring approach
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. This analysis is performed using a combination of open-source and commercial tools for traffic capture and parsing. A proprietary correlation system built on top of Google technology also supports this analysis. Network analysis is supplemented by examining system logs to identify unusual behavior, such as attempted access of customer data. Google security engineers place standing search alerts on public data repositories to look for security incidents that might affect the company’s infrastructure.

https://cloud.google.com/security/overview/whitepaper#monitoring
Incident management type
Supplier-defined controls
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.

https://cloud.google.com/security/overview/whitepaper#incident_management

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
Yes
Who implements virtualisation
Supplier
Virtualisation technologies used
KVM hypervisor
How shared infrastructure is kept separate
Customer environments are logically segregated, preventing users and customers from accessing unassigned resources. Customers maintain full control over their data access. Services which provide virtualised operational environments to customers, ensure that customers are segregated and prevent cross-tenant privilege escalation and information disclosure via hypervisors and instance isolation.

Following well-architected patterns, Mobilise can establish further controls to protect customers data.

Energy efficiency

Energy-efficient datacentres
Yes
Description of energy efficient datacentres
GCP is committed to running their business in the most environmentally friendly way possible.
https://cloud.google.com/sustainability

Pricing

Price
£0.01 to £0.01 a virtual machine a month
Discount for educational organisations
Yes
Free trial available
Yes
Description of free trial
https://cloud.google.com/free
Link to free trial
https://cloud.google.com/free

Service documents

Request an accessible format
If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at james.carnie@mobilise.cloud. Tell them what format you need. It will help if you say what assistive technology you use.