This G-Cloud 9 service is no longer available to buy.

The G-Cloud 9 framework expired on Monday 1 October 2018. Any existing contracts with Zaizi Limited are still valid.
Zaizi Limited

Managed Big Data Platform

Fully managed big data, open date and data warehouse platform for managing data at petabyte scale and enabling simple and efficient analysis of the data using existing or new business intelligence tools. Full 24 x7 support and single point of management for ease of use and maximum availability

Features

  • Suitable for OFFICIAL and OFFICIAL SENSITIVE workloads
  • Data centres available from 3 UK regions including the UK
  • Based on AWS set of Big Data Tools including Redshift
  • Connectivity Options including PSN, JANET and N3
  • Fast Query and I/O Performance
  • Parallel Queries across multiple nodes
  • Custom JDBC/ODBC drivers for download
  • Fully Managed Service with 24 x 7 Option
  • Full proactive ITIL service management / service improvements
  • Open Data Platform integration

Benefits

  • Fully integrated Big Data platform across constituent AWS services
  • Fully enabled backup and disaster recovery processes
  • Automated provisioning, configuring and monitoring a cloud data warehouse
  • Rapidly scalable to support highly dynamic data loads
  • Comprehensive logging and security
  • Role Based access control across platform
  • Single interface point for management and support
  • Integration capability with other platforms (Cloudera, Solr, ElasticSearch)
  • Platform for provision of open data service (public sector data)

Pricing

£1,000 a unit 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 sales@zaizi.com. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 9

Service ID

4 7 6 7 6 4 6 7 1 9 5 3 1 4 1

Contact

Zaizi Limited Andrew Hawkins
Telephone: 0203 582 8330
Email: sales@zaizi.com

Service scope

Service constraints
This platform makes use of AWS services
System requirements
N/A

User support

Email or online ticketing support
Email or online ticketing
Support response times
Zaizi offer Level 2 and Level 3 support service supporting the application, platform and infrastructure as required. We operate under an ITIL model incorporating a Continual Improvement (CI) and automated testing approach. Support is offered for: Core Business Hours 8:00 – 18:00 Extended Business hours (not weekends and Bank Holidays) 24/7 Support Via UK and Overseas Support Desk Zaizi prioritises all issues raised aiming to resolve within agreed response and resolution times, the table below provides the typical response times offered. P1: Response 1hr, target resolution 4hrs P2: Response 2hr, target resolution 24hrs P3: Response 4hrs, target 5 business days
User can manage status and priority of support tickets
Yes
Online ticketing support accessibility
None or don’t know
Phone support
Yes
Phone support availability
24 hours, 7 days a week
Web chat support
No
Onsite support
Yes, at extra cost
Support levels
Zaizi offer Level 2 and Level 3 support service supporting the application, platform and infrastructure as required. We operate under an ITIL model incorporating a Continual Improvement (CI) and automated testing approach. Support is offered for: Core Business Hours 8:00 – 18:00 Extended Business hours (not weekends and Bank Holidays) 24/7 Support Via UK and Overseas Support Desk Zaizi prioritises all issues raised aiming to resolve within agreed response and resolution times, the table below provides the typical response times offered. P1: Response 1hr, target resolution 4hrs P2: Response 2hr, target resolution 24hrs P3: Response 4hrs, target 5 business days
Support available to third parties
Yes

Onboarding and offboarding

Getting started
We offer onsite training and offsite training on the service at additional cost and document the service and SLA
Service documentation
Yes
Documentation formats
  • HTML
  • ODF
  • PDF
End-of-contract data extraction
We provide an off boarding service which is charged at T&M. The scope of the support and work required will be scoped on notice of termination.
End-of-contract process
All off boarding and final documentation will be chargeable however our services are designed around open systems and to be as flexible for client on-boarding and off boarding as feasible.

Using the service

Web browser interface
No
API
No
Command line interface
No

Scaling

Scaling available
Yes
Scaling type
Automatic
Independence of resources
Our management processes monitor and assess performance for each client and our service scales accordingly to ensure performance baselines our met
Usage notifications
Yes
Usage reporting
  • Email
  • Other

Analytics

Infrastructure or application metrics
Yes
Metrics types
  • CPU
  • Disk
  • HTTP request and response status
  • Memory
Reporting types
  • Regular reports
  • Reports on request

Resellers

Supplier type
Reseller providing extra features and support
Organisation whose services are being resold
Amazon Web Services

Staff security

Staff security clearance
Conforms to BS7858:2012
Government security clearance
Up to Developed Vetting (DV)

Asset protection

Knowledge of data storage and processing locations
Yes
Data storage and processing locations
  • United Kingdom
  • European Economic Area (EEA)
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
Other data at rest protection approach
AWS adheres to independently validated privacy, data protection, security protections and control processes. (Listed under “certifications”). AWS is responsible for the security of the cloud; customers are responsible for security in the cloud. AWS enables customers to control their content (where it will be stored, how it will be secured in transit or at rest, how access to their AWS environment will be managed). Wherever appropriate, AWS offers customers options to add additional security layers to data at rest, via scalable and efficient encryption features. AWS offers flexible key management options and dedicated hardware-based cryptographic key storage.
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
  • Machine Images
  • Files
  • Databases
Backup controls
Backup schedule is agreed as part of the service agreement and SLA
Datacentre setup
Multiple datacentres with disaster recovery
Scheduling backups
Users contact the support team to schedule backups
Backup recovery
Users contact the support team

Data-in-transit protection

Data protection between buyer and supplier networks
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
Data protection within supplier network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway

Availability and resilience

Guaranteed availability
Individual SLA's are agreed with each client
Approach to resilience
The AWS Business Continuity plan details the process that AWS follows in the case of an outage, from detection to deactivation. AWS has developed a three-phased approach: Activation and Notification Phase, Recovery Phase, and Reconstitution Phase. This approach ensures that AWS performs system recovery and reconstitution efforts in a methodical sequence, maximizing the effectiveness of the recovery and reconstitution efforts and minimizing system outage time due to errors and omissions. AWS maintains a ubiquitous security control environment across all regions. Each data centre is built to physical, environmental, and security standards in an active-active configuration, employing an n+1 redundancy model, ensuring system availability in the event of component failure. Components (N) have at least one independent backup component. All data centres are online and serving traffic. In case of failure, there is sufficient capacity to enable traffic to be load-balanced to the remaining sites. Customers are responsible for implementing contingency planning, training and testing for their systems hosted on AWS. AWS provides customers with the capability to implement a robust continuity plan, including the utilization of frequent server instance back-ups, data redundancy replication, and the flexibility to place instances and store data within multiple geographic regions across multiple Availability Zones.
Outage reporting
Email alerts and support calls. AWS also have a public dashboard available how we expect to proactively any outages with the client

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)
  • Limited access network (for example PSN)
  • Dedicated link (for example VPN)
  • Username or password
Access restrictions in management interfaces and support channels
All access is managed through Zaizi support calls. Within the AWS environment AWS controls access via unique user ID/password authentication. No actions are permissible without authentication. Remote access is multi-factor, login attempts are limited, remote administrative access attempts are logged and reviewed by Security. Suspicious activity initiates incident response procedures. A session lock out policy that is systematically enforced: locks are retained until identification/authentication procedures are concluded. AWS’s Identity and Access Management (IAM) system controls access to AWS services/resources. IAM facilitates the issuance of access permissions per user/group. MFA is available at no extra cost
Access restriction testing frequency
At least every 6 months
Management access authentication
2-factor authentication
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 receive audit information on a regular basis
How long user audit data is stored for
At least 12 months
Access to supplier activity audit information
Users receive audit information on a regular basis
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
Bureau Veritas
ISO/IEC 27001 accreditation date
21/4/2015
What the ISO/IEC 27001 doesn’t cover
The following is excluded from the scope of Zaizi’s Statement of ISO 27001:2013 Statement of Applicability: A.11.2.4 – Equipment Maintenance Reason - No fixed asset has high-value (i.e. >£3k) are depreciated on purchase and have no residual value after 3 years. Items considered beyond economic local repair are the subject of straight replacement from new. Servers are leased and cloud-based and out of scope of this requirement. A.11.1.5 – Working in secure areas. Reason Zaizi does not operate a system of permanent secure areas. Secure area working is restricted to customer sites in accordance with current HMG information classification guidelines. Working on-premise is constrained to the HMG classification of OFFICIAL. A.14.2.7 – Outsourced Development. Reason - Zaizi does not outsource the development of software (it is a software development house).
ISO 28000:2007 certification
No
CSA STAR certification
No
PCI certification
No
Other security accreditations
Yes
Any other security accreditations
Cyber Essentials

Security governance

Named board-level person responsible for service security
Yes
Security governance accreditation
Yes
Security governance standards
ISO/IEC 27001
Information security policies and processes
We are fully ISO27001 assured and follow standard procedures. Our processes are reviewed internally at management level at regular intervals during the year, including our Chief Exec and CSIO. Incidents are managed by our CSIO and by the process alerted to the Management team

Operational security

Configuration and change management standard
Supplier-defined controls
Configuration and change management approach
Ziazi follows ITIL processes for service delivery including compliance to ISO27001. The AWS platform. Changes to AWS services and features follow secure software development practices, including security risk reviews prior to launch. Developer access to production environments is via explicit access system requests, subject to owner review and authorisation. Teams set bespoke change management standards per service, underpinned by standard AWS guidelines. All production environment changes are reviewed, tested and approved. Stages include design, documentation, implementation (including rollback procedures), testing (non-production environment), peer to peer review (business impact/technical rigour/code), final approval by authorised party.
Vulnerability management type
Supplier-defined controls
Vulnerability management approach
AWS Security performs vulnerability scans on the host operating system, web applications, and databases in the AWS environment. Approved 3rd party vendors conduct external assessments (minimum frequency: quarterly). Identified vulnerabilities are monitored and evaluated. Countermeasures are designed and implemented to neutralise known/newly identified vulnerabilities. AWS Security monitors newsfeeds/vendor sites for patches and receives customer intelligence via http://aws.amazon.com/security/vulnerability-reporting/. AWS customers are responsible for all scanning, penetration testing, file integrity monitoring and intrusion detection for their Amazon EC2 and Amazon ECS instances/ applications. Scans should include customer IP addresses (not AWS endpoints). AWS endpoint testing is part of AWS compliance vulnerability scans.
Protective monitoring type
Supplier-defined controls
Protective monitoring approach
AWS deploys (pan-environmental) monitoring devices to collect information on unauthorized intrusion attempts, usage abuse, and network/application bandwidth usage. Devices monitor: • Port scanning attacks • Usage (CPU, processes, disk utilization, swap rates, software-error generated losses) • Application metrics • Unauthorized connection attempts Near real-time alerts flag potential compromise incidents, based on AWS Service/Security Team- set thresholds. Requests to AWS KMS are logged and visible via the account’s AWS CloudTrail Amazon S3 bucket. Logs provide request information, under which CMK, and identify the AWS resource protected through the CMK use
Incident management type
Supplier-defined controls
Incident management approach
AWS adopts a three-phased approach to manage incidents: 1. Activation and Notification Phase 2. Recovery Phase 3. Reconstitution Phase To ensure the effectiveness of the AWS Incident Management plan, AWS conducts incident response testing, providing excellent coverage for the discovery of defects and failure modes as well as testing the systems for potential customer impact. The Incident Response Test Plan is executed annually, in conjunction with the Incident Response plan. It includes multiple scenarios, potential vectors of attack, the inclusion of the systems integrator in reporting and coordination and varying reporting/detection avenues.

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
Third-party
Third-party virtualisation provider
Amazon Web Services
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 virtualized operational environments to customers, ensure that customers are segregated and prevent cross-tenant privilege escalation and information disclosure via hypervisors and instance isolation. Different instances running on the same physical machine are isolated from each other via the Xen hypervisor. The Amazon EC2 firewall resides within the hypervisor layer, between the physical network interface and the instance's virtual interface. All packets pass through this layer. The physical random-access memory (RAM) is separated using similar mechanisms.

Energy efficiency

Energy-efficient datacentres
Yes

Pricing

Price
£1,000 a unit a month
Discount for educational organisations
No
Free trial available
No

Documents

Pricing document
Pricing document
Skills Framework for the Information Age rate card
Skills Framework for the Information Age rate card
Terms and conditions document
Terms and conditions document

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 sales@zaizi.com. Tell them what format you need. It will help if you say what assistive technology you use.