Druva Data Resiliency Cloud

Service scope

Software add-on or extension: No
Cloud deployment model: Public cloud
Service constraints: The Service is cloud based and constraints are likely to be end user specific. The only key restraint is this service only holds backup data in AWS clouds
System requirements: AWS

This service just requires normal levels of access

User support

Email or online ticketing support: Email or online ticketing
Support response times: Business critical offered as standard with priority of response set by customer. Critical having 1 hour initial, high 2 hours, medium 4 hours and low 8 hours. We offer premium support (at a cost) with critical being 30 mins, high 1 hour, medium 2 hours, and low 4 hours
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: Web chat
Web chat support availability: 24 hours, 7 days a week
Web chat support accessibility standard: WCAG 2.1 AA or EN 301 549
Web chat accessibility testing: Unknown
Onsite support: No
Support levels: Business critical offered as standard with priority of response set by customer. Critical having 1 hour initial, high 2 hours, medium 4 hours and low 8 hours. We offer premium support (at a cost) with critical being 30 mins, high 1 hour, medium 2 hours, and low 4 hours
Support available to third parties: Yes

Onboarding and offboarding

Getting started: Druva operates a knowledge base portal for help and configuration documentation as well as free online learning videos to assist with service training
Service documentation: Yes
Documentation formats: HTML
End-of-contract data extraction: Users can extract data manually from within the system at any time. An bulk export service is available at an additonal cost. Upon termination of the contract, data is transferred back to the client over a secure channel (TLS 1.2) or other storage medium of their choice.
End-of-contract process: Customer will have 30 days to retrieve their data after termination of services. If you wish to retrieve data more than 30 days after termination, customer will be charged the current price for every additional storage day. Data will be returned either via direct transfer, where we will export Customer Data into Customer’s AWS account under the selected S3 bucket; or a portable physical media provided by Customer (i.e. SATA, USB connected media or AWS Snowball).

Using the service

Web browser interface: Yes
Supported browsers: Internet Explorer 11

Microsoft Edge

Firefox

Chrome

Safari

Opera
Application to install: Yes
Compatible operating systems: Android

IOS

Linux or Unix

MacOS

Windows
Designed for use on mobile devices: Yes
Differences between the mobile and desktop service: N/a
Service interface: Yes
User support accessibility: None or don’t know
Description of service interface: There is a GUI Portal that allows users to access all aspects of the backup service
Accessibility standards: WCAG 2.1 AA or EN 301 549
Accessibility testing: Unknown
API: Yes
What users can and can't do using the API: We have both Events and Actionalble APIs

Please see following link to see documentation outlining all requirements:
https://developer.druva.com/reference
API documentation: Yes
API documentation formats: HTML
API sandbox or test environment: No
Customisation available: No

Scaling

Independence of resources: The service is cloud provisioned and right sized for each individual organisations workload demands. The right sizing of the cloud environment ensure performance demands are comfortably meet. The service is scalable using Amazon AWS Compute and Storage for all Servers, allowing it to use further resources as and when necessary. No further customer investment in additional technologies is necessary to ensure scalability of the service- this is included in the service per user cost

Analytics

Service usage metrics: Yes
Metrics types: Service availability,
deduplication rates,
successful backups,
successful restores,
Active users,
Reporting types: API access

Real-time dashboards

Regular reports

Reports on request

Resellers

Supplier type: Reseller providing extra support
Organisation whose services are being resold: Druva Data Resiliency Cloud

Staff security

Staff security clearance: Other security clearance
Government security clearance: None

Asset protection

Knowledge of data storage and processing locations: Yes
Data storage and processing locations: United Kingdom
User control over data storage and processing locations: Yes
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 SSAE-16 / ISAE 3402

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
Equipment disposal approach: Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001

Data importing and exporting

Data export approach: Users can extract data manually from within the system at any time. An bulk export service is available at an additonal cost
Data export formats: Other
Other data export formats: Exported back in the original format
Data import formats: Other
Other data import formats: N/A

Data-in-transit protection

Data protection between buyer and supplier networks: TLS (version 1.2 or above)
Data protection within supplier network: TLS (version 1.2 or above)

Availability and resilience

Guaranteed availability: We provide an SLA of 99.5% uptime and 99.99999% Customer Data durability
Approach to resilience: AWS Multi-way redundancy: The cloud instance for the customer is alwalys replicated between 3 physically different data centres as part of the Amazon AWS availability zone feature. In the case of access being not availabile from 1 datacentre, the customers instance will be instantly available from 1 of the 2 further datacentres.
Outage reporting: Outages of the system availability or the storage component are communicated to all assigned administrators within a cloud instance via email as well as via the Support Portal. An online dashboard also reports instance of global outages

Identity and authentication

User authentication needed: Yes
User authentication: Other
Other user authentication: Druva supports the use of cloud-based SSO solutions such as Okta, Ping Identity, and Microsoft ADFS for both administrators and end users. Organizations can also leverage more traditional directory service implementations, such as Microsoft Active Directory or LDAP, for user authentication.
Access restrictions in management interfaces and support channels: Users and management are seperated and controlled with separate authentication portals. RBAC is also used to determine a users level of system access
Access restriction testing frequency: At least once a year
Management access authentication: 2-factor authentication

Username or password

Other
Description of management access authentication: Via SSO and MFA

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: At least 12 months
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: At least 12 months

Standards and certifications

ISO/IEC 27001 certification: Yes
Who accredited the ISO/IEC 27001: Schellman LLP
ISO/IEC 27001 accreditation date: 28/09/2023
What the ISO/IEC 27001 doesn’t cover: N/a
ISO 28000:2007 certification: No
CSA STAR certification: Yes
CSA STAR accreditation date: 17/02/2023
CSA STAR certification level: Level 1: CSA STAR Self-Assessment
What the CSA STAR doesn’t cover: N/a
PCI certification: No
Cyber essentials: Yes
Cyber essentials plus: No
Other security certifications: Yes
Any other security certifications: ISAE 3000 Type II audit performed yearly by KPMG

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: Druva's security program is based on NIST 800-53, documented policies can be found at security.druva.com

Operational security

Configuration and change management standard: Supplier-defined controls
Configuration and change management approach: Druva has documented policies and procedures regarding change management, patch management, and deployment of changes in the Configuration Management Policy. Both change and patch management follow the same process. The procedures regarding patch management exist to verify that relevant, up-to-date patches and security updates are installed. Changes to the application and database are requested using a Change Request (CR) in a ticketing system. Changes are approved as per the authorization matrix defined in Cloud Operations Guide. The change implementer is granted access to the production server for deploying the changes based on approval from the Cloud Operations Head.
Vulnerability management type: Supplier-defined controls
Vulnerability management approach: Vulnerability Management for the Druva Cloud Service is done as follows: Critical Vulnerabilities are patched in 14 days or less. High Vulnerabilities are patched in 30 days or less. Medium Vulnerabilities are patched in 90 days or less. Low Vulnerabilities are patched in 180 days or less.
Protective monitoring type: Supplier-defined controls
Protective monitoring approach: Druva has logging systems and log reviews to detect security issues such as loss, misuse, or unauthorized access to Customer Data. This includes developing a baseline of expected activity within the Cloud Services; logging to detect activity exceeding baseline thresholds. Logs shall be regularly reviewed by Druva, either manually or using log parsing tools. Logs will be retained for a minimum of six months and protected from unauthorized access, modification, and accidental or deliberate destruction. Customers that wish to retain audit trails beyond this period can do through our events API and ingest the logs into their own SIEM system.
Incident management type: Supplier-defined controls
Incident management approach: Druva has a documented Incident Response Plan that includes steps to respond to security incidents including identification, investigation, response, mitigation, customer notification, and root cause analysis.

Secure development

Approach to secure software development best practice: Supplier-defined process

Public sector networks

Connection to public sector networks: No

Social Value

Fighting climate change

We take our environmental management and the impact we have on the environment very seriously. We have environmental policies in place and hold the ISO14001 accreditation. Our environmental assessments are conducted annually by an external Lead ESOS Assessor; they are signed-off by the board and compliance reported to the regulator (the Environment Agency). Our environmental policy is published on our website at https://www.bytes.co.uk/company/sustainability/environmental.
Bytes achieved carbon net zero in March 2022 through approved carbon offsetting schemes. We are always seeking to reduce our impact on the environment. We aim to minimise waste, reduce pollutants and use renewable materials. Our offices have recycling facilities for cans, plastic and paper. We aim to reduce our office printing to zero within the next few years.
An Environmental Steering Committee has been established to coordinate environmental activities and drive change.
To drastically reduce our emissions, we have switched to renewable energy. Our Head Office has reached our first milestone of using a specialist 100% renewable electricity provider. We are also exploring options to install solar panels on our Headquarters building.
Other environmental initiatives include installing electric vehicle charging points and encouraging staff to commute to work without the car (setting up a car share network and installing secure cycle parking).
We produce a SECR (Streamlined Energy and Carbon Reporting) report that details the companies energy consumption and carbon emissions. This report is produced annually by an independent assessor.
This report provides details of our emissions in Scope 1, 2 and 3 categories. It details the activities previously taken to reduce emissions and also recommendations for further improvements.
For scope 1,2 and 3 emissions we aim to reduce these by 50% by 2025-2026 from our 2021 baseline.
We aim to be Net Zero by 2040, covering our own operational emissions.

Pricing

Price: £3.40 a user a month
Discount for educational organisations: Yes
Free trial available: Yes
Description of free trial: 30 Day free Trial - Fully functioning

Features

Benefits

Service documents

Framework

Service ID

Contact

Service scope

User support

Onboarding and offboarding

Using the service

Scaling

Analytics

Resellers

Staff security

Asset protection

Data importing and exporting

Data-in-transit protection

Availability and resilience

Identity and authentication

Audit information for users

Standards and certifications

Security governance

Operational security

Secure development

Public sector networks

Pricing

Service documents

Cookies on Digital Marketplace

Druva Data Resiliency Cloud

Features

Benefits

Pricing

Service documents

Framework

Service ID

Contact

Service scope

User support

Onboarding and offboarding

Using the service

Scaling

Analytics

Resellers

Staff security

Asset protection

Data importing and exporting

Data-in-transit protection

Availability and resilience

Identity and authentication

Audit information for users

Standards and certifications

Security governance

Operational security

Secure development

Public sector networks

Social Value

Pricing

Service documents