Zoocha Limited

Drupal Hosting

Drupal hosting leverages the Amazon Web Services toolset to provide a high performance Drupal hosted solution in the cloud. Our Drupal hosting services reduces the time required to obtain and boot new server instances, allowing you to quickly scale capacity, as your computing requirements change across your hosted Drupal CMS.

Features

• Drupal Optimised AWS Hosting Infrastructure
• Suitable for OFFICIAL (formerly IL2/IL3) and/or SENSITIVE workloads
• 7 availability zones, 3 EU regions (including the UK)
• NCSC Cloud Security Principles aligned, Security Cleared (SC) staff available
• Elastic, web-scale computing made easier for developers
• Complete control of your computing resources
• Choice of multiple instance types, operating systems, and software packages
• Select configuration of memory, CPU, and instance storage
• Tools to build failure resilient and scalable applications

Benefits

• High performance Drupal hosting on tailored AWS infrastructure
• Comprehensive, cross service API audit logging and security (CloudTrail)
• Integration with other AWS services (24x7 support and consolidated billing)
• Training and architectural patterns/guidance (well architected)
• Quickly scale capacity, both up and down
• Obtain and configure capacity with minimal friction
• Pay only for capacity you actually use
• Highly reliable environment
• Migrate services by importing VMs from Vmware and HyperV

£300 an instance a month

• Education pricing available

Service documents

• Pricing document

  PDF

• Skills Framework for the Information Age rate card

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

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

Framework

G-Cloud 14

Service ID

819018926344581

Contact

William Huggins
441992256700
info@zoocha.com

Service scope

• Service constraints: N/A
• System requirements:
  • Drupal
  • PHP

User support

• Email or online ticketing support: Email or online ticketing
• Support response times: 15 minutes for critical support (24/7/365); ; Our standard support hours are 9am to 5.30pm Monday to Friday, exluding bank holidays. Zoocha also offers extended support hours from 7am to 9pm Monday to Friday, exluding bank holidays.
• User can manage status and priority of support tickets: Yes
• Online ticketing support accessibility: WCAG 2.1 A
• Phone support: Yes
• Phone support availability: 9 to 5 (UK time), Monday to Friday
• Web chat support: Web chat
• Web chat support availability: 9 to 5 (UK time), Monday to Friday
• Web chat support accessibility standard: WCAG 2.1 A
• Web chat accessibility testing: N/A
• Onsite support: Yes, at extra cost
• Support levels: Zoocha provide a multi tier support service which is contracted as 'support days per month' @ £700 per day and utilisation against contracted support time is reported monthly. Contracted support time can be increased or decreased (to a minimum of 1 day per month) at any time during the contract, by providing 30 days notice.; ; Our standard support hours are 9am to 5.30pm Monday to Friday, exluding bank holidays. Zoocha also offers extended support hours from 7am to 9pm Monday to Friday, exluding bank holidays. ; ; Critical support can be provided on a 24/7/365 basis at an additional cost of £250 per month, which guarentees a 15 minute response and 2 hour resolution of all critical issues.; ; Service level agreements (SLA's) cover uptime, incident response and incident resolution.; ; Each client will have a named Client Services Manager, who will be their main point of contact and will be responsible for the monthly service reviews.; ; Zoocha's support service is ISO certified to a UKAS rated standard for 9001:2015, 14001:2015, 22301:2019, 27001:2022.; ; Note: Overages (support time used above the contracted amount) is charged at £150 per hour.
• Support available to third parties: Yes

Onboarding and offboarding

• Getting started: Zoocha provide a fully managed service for Drupal hosting on AWS. In addition, AWS provides a range of resources to help customers get started. These include: comprehensive documentation (in multiple formats), introductory videos, hands-on labs, online and in-person training, access to a large ecosystem of partners and support from the public sector account team.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
• End-of-contract data extraction: As part of the Zoocha managed service, all client data will be extracted and securely transferred to the client at the end of the contract. In addition, data may be copied out directly from AWS using OS-level tools (such as xopy or rsync).
• 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. Supplier customers retain control and ownership of their data. Supplier will not erase customer data for 30 days following an account termination. This allows customers to retrieve content from Supplier services so long as the customer has paid any charges for any post-termination use of the service offerings and all other amounts due.

Using the service

• Web browser interface: Yes
• Using the web interface: Almost all functionality for each of our services is exposed through the web console. ; ; The web console facilitates management for all aspects of the AWS account in a consolidated view whilst providing access to all services and their respective functionalities. ; ; In some cases, specific configuration parameters of a service are dedicated to, and only available from, the CLI, SDK, or API interface.
• Web interface accessibility standard: WCAG 2.1 A
• Web interface accessibility testing: N/A
• API: Yes
• What users can and can't do using the API: All functionality is exposed via an API.
• API automation tools:
  • Ansible
  • Chef
  • SaltStack
  • Terraform
  • Puppet
  • Other
• Other API automation tools:
  • Wide range of 3rd party services hook into AWS APIs.
  • SDKs for Python
  • SDKs for Ruby
  • SDKs for PHP
  • SDKs for JavaScript
  • SDKs for Java
  • SDKs for .NET
  • SDKs for Node.js
• API documentation: Yes
• API documentation formats:
  • HTML
  • PDF
• Command line interface: Yes
• Command line interface compatibility:
  • Linux or Unix
  • Windows
  • MacOS
• Using the command line interface: All functionality is available via the CLI.

Scaling

• Scaling available: Yes
• Scaling type: Automatic
• Independence of resources: Customer environments are logically segregated to prevent users and customers from accessing resources not assigned to them. Services which provide virtualized operational environments to customers (i.e. EC2) ensure that customers are segregated via security management processes/controls at the network and hypervisor level. AWS continuously monitors service usage to project infrastructure needs to support availability commitments/requirements. AWS maintains a capacity planning model to assess infrastructure usage and demands at least monthly, and usually more frequently. In addition, the AWS capacity planning model supports the planning of future demands to acquire and implement additional resources based upon current resources and forecasted requirements.
• Usage notifications: Yes
• Usage reporting:
  • API
  • Email
  • SMS
  • Other
• Other usage reporting: Automated creation of service desk ticket; Slack

Analytics

• Infrastructure or application metrics: Yes
• Metrics types:
  • CPU
  • Disk
  • HTTP request and response status
  • Network
  • Number of active instances
  • Other
• Other metrics:
  • AWS resources: e.g. Amazon EC2/Amazon RDS DB instances, DynamoDB tables
  • Custom metrics generated by customers’ applications and services
  • Metrics associated with log files generated by the application
• Reporting types:
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request

Resellers

• Supplier type: Reseller providing extra features and support
• Organisation whose services are being resold: AWS

Staff security

• Staff security clearance: Other security clearance
• Government security clearance: Up to Baseline Personnel Security Standard (BPSS)

Asset protection

• Knowledge of data storage and processing locations: Yes
• Data storage and processing locations:
  • United Kingdom
  • European Economic Area (EEA)
  • Other 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: ‘IT Health Check’ performed by a Tigerscheme qualified provider or a CREST-approved service provider
• 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
• 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: 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: Machine Image
• Backup controls: Manual or scheduled API call
• 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-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
• Data protection within supplier network: Other
• Other protection within supplier network: Customer environments are logically segregated to prevent users and customers from accessing resources not assigned to them. AWS gives customers ownership and control over their content by design through simple, but powerful tools that allow customers to determine how their content will be secured in transit. AWS enables customers to open a secure, encrypted channel to AWS services using TLS/SSL, and/or IPsec or TLS VPN (if applicable), or other means of protection the customer wish to use. API calls can be encrypted with TLS/SSL to maintain confidentiality; the AWS Console connection is encrypted with TLS.

Availability and resilience

• Guaranteed availability: AWS currently provides SLAs for several services. Due to the rapidly evolving nature of AWS’s product offerings, SLAs are best reviewed directly on the website via the links below:; ; • Amazon EC2 SLA: http://aws.amazon.com/ec2-sla/ ; • Amazon S3 SLA: http://aws.amazon.com/s3-sla ; • Amazon CloudFront SLA: http://aws.amazon.com/cloudfront/sla/ ; • Amazon Route 53 SLA: http://aws.amazon.com/route53/sla/ ; • Amazon RDS SLA: http://aws.amazon.com/rds-sla/; • AWS Shield Advanced SLA: https://aws.amazon.com/shield/sla/ ; ; Well-architected solutions on AWS that leverage AWS Service SLA’s and unique AWS capabilities such as multiple Availability Zones, can ease the burden of achieving specific SLA requirements.
• 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: Public dashboard; personalised dashboard with API and events; configurable alerting (email / SMS / messaging)

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: 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 restrictions in management interfaces and support channels: IAM provides user access control to AWS services, APIs and specific resources. Other controls include time, originating IP address, SSL use, and whether users authenticated via MFA devices. API calls to launch/terminate instances, change firewalls, and perform other functions are signed by customers’ Amazon Secret Access Key (either the root AWS Account’s Secret Access Key or the Secret Access key of a user created with AWS IAM). Amazon EC2 API calls cannot be made on customers’ behalf without access to customers’ Secret Access Ke. API calls can be encrypted with TLS/SSL for confidentiality and customers can use TLS/SSL-protected API endpoints.
• 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 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: SOCOTEC
• ISO/IEC 27001 accreditation date: 08/11/2023
• What the ISO/IEC 27001 doesn’t cover: All Zoocha services are covered.
• ISO 28000:2007 certification: No
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: Yes
• Cyber essentials plus: Yes
• 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
• Information security policies and processes: Both Zoocha and AWS implement formal, documented policies and procedures that provide guidance for operations and information security within the organisation. Policies address purpose, scope, roles, responsibilities and management commitment. Employees maintain policies in a centralised and accessible location. AWS Security Assurance is responsible for familiarizing employees with the AWS security policies.; ; AWS has established information security functions that are aligned with defined structure, reporting lines, and responsibilities. Leadership involvement provides clear direction and visible support for security initiatives.; ; The output of AWS Leadership reviews include any decisions or actions related to:; • Improvement of the effectiveness of the ISMS.; • Update of the risk assessment and treatment plan.; • Modification of procedures and controls that affect information security to respond to internal or external events that may impact the ISMS.; • Resource needs.; • Improvement in how the effectiveness of controls is measured. Policies are approved by AWS leadership at least annually or following a significant change to the AWS environment.

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: 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. Emergency changes follow AWS incident response procedures. Exceptions to change management processes are documented and escalated to AWS management.
• Vulnerability management type: Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
• 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/. Zoocha 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: Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
• 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 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. Log events are visible after turning on AWS CloudTrail.
• 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: Zoocha Drupal hosting benefits from AWS three-phased approach to managing 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: Supplier
• Virtualisation technologies used: Other
• Other virtualisation technology used: AWS proprietary
• 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
• Description of energy efficient datacentres: AWS is committed to running our business in the most environmentally friendly way possible. In addition to the environmental benefits inherently associated with running applications in the cloud, AWS has a long-term commitment to achieve 100% renewable energy usage for our global infrastructure footprint. We’ve made a lot of progress on this commitment. In January 2018, AWS achieved 50% renewable energy usage. To date, we have announced nine new renewable energy projects (three wind farms and six solar farms), and these projects will deliver a total of 2 million MWh of energy annually onto the electric grid powering AWS data centers located in the AWS US East (Ohio) and AWS US East (N. Virginia) Regions. The electricity produced from these projects is enough to power the equivalent of over 190,000 U.S. homes annually, which is approximately the size of the city of Atlanta, Georgia. More information is available on the AWS and Sustainability page. AWS introduced its first carbon-neutral region in 2011. Today, AWS offers customers five AWS Regions that are carbon-neutral:; • US West (Oregon); • AWS GovCloud (US-West); • EU (Frankfurt); • EU (Ireland); • Canada (Central)

Social Value

• Social Value:

  Social Value

  • Fighting climate change
  • Tackling economic inequality
  • Equal opportunity
  • Wellbeing

  Fighting climate change

  Zoocha are proud to be certificated to the ISO 14001 standard (by a UKAS rated accreditation body) since early 2023. This internationally recognized standard for Environmental Management Systems (EMS) helps organisations such as Zoocha in identifying, managing, and continually improving their environmental performance. ; ; While ISO 14001 doesn't explicitly target carbon emissions, it supports the reduction of a variety of practices, such as Zoocha’s environmental policy which outlines our commitment to reducing environmental impacts, including carbon emissions.; ; Zoocha's services are also 'Green Mark' certified.; ; Zoocha has an established EMS, which includes plans, procedures, and practices to achieve our objectives and targets. This included the development of strategies to reduce energy consumption, improving process efficiency (such as in hosting environments), and switching to low-carbon energy sources.

  Tackling economic inequality

  At Zoocha, we understand the profound impact that economic inequality can have on communities and industries alike. Our approach to tackling this issue is multi-faceted, rooted in our core values of People, Trust, Value, Quality, and Success. We strive to create opportunities and foster an inclusive environment where everyone has the chance to thrive.; ; Firstly, we ensure that our hiring practices are fair and inclusive, offering equal opportunities for people from diverse backgrounds. This is crucial in the tech industry, where diversity can drive innovation and creativity. By building a team that reflects a wide range of experiences and perspectives, we not only enhance our own services but also contribute to reducing the skills gap in the technology sector.; ; We also extend our commitment to economic equality through our work with clients in the higher education, public sector, health, and Charity/NGO sectors. By delivering high-quality digital solutions that improve accessibility, efficiency, and engagement, we help these organisations serve their communities more effectively, indirectly combating economic inequality by providing better access to essential services.; ; Finally, our contributions to the Drupal Open Source project reflect our belief in the power of technology as a force for good. By supporting the Drupal community through financial support, code contributions, and knowledge sharing, we help ensure that cutting-edge technology is available and accessible to all, democratizing access to digital tools that can empower individuals and organizations worldwide.; ; In these ways, Zoocha actively works towards a more equitable world, leveraging our expertise and resources to make a difference in the communities we serve and beyond.

  Equal opportunity

  The Zoocha culture, policies and processes explicitly ban any discrimination including (but not limited to) on the grounds of age, disability, gender reassignment, marriage/civil partnership, pregnancy/maternity, race, religion or belief, sex or sexual orientation. Zoocha aspires to provide a diverse workforce, a composition of which reflects that of the broader community.; ; In accordance with our policy, Zoocha is totally committed to the principles and practice of equal opportunities as an employer. Our directors and members of senior management are empowered to recruit and manage employees, advocate our policies and make every effort to ensure that all actions and decisions have equity at their core.

  Wellbeing

  At Zoocha, our employee wellbeing is a top priority and we offer a number of services to accommodate this. Our benefits scheme includes birthdays off, 25 days of annual leave per year, gym memberships, mental health support and private health care. These are offered to our employees to ensure that we are able to provide a comfortable, secure work space that everybody can enjoy. ; ; We also offer all of our employees the opportunity to take advantage of a flexible working schedule which allows them to work from any location and attend to any needs throughout the day. While we encourage the onboarding of local employees to support employment opportunities, we are more than happy to accommodate our remote employees, supplying any equipment needed in order to create a comforting home office space, as well as booking hotel stays if they want to visit the office for a more sociable atmosphere.

Pricing

• Price: £300 an instance a month
• Discount for educational organisations: Yes
• Free trial available: No

Service documents

• Pricing document

  PDF

• Skills Framework for the Information Age rate card

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

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