DBRaaS uses native database technologies to create database log based replication into the cloud. For example an Oracle standby automatically spun up in AWS.
DBRaaS is a subset of Disaster Recovery and can be used where a complete site wide DR solution is not required.
- cloud compute model for costing
- cloud based standby database
- automated build using devop methods based on your software versions
- dsp manged service can be layered on top
- support includes 247 enterprise monitoring
- bring your own licenses
- solution can be on-premise to cloud, cloud-to-cloud, cloud-to-on-premise)
- no need to provide physical hardware or secondary DC
- increased scalability to add DR capability quickly as business grows
- faster time to market - less worry over the infrastructure
- flexibility and creativity - quick deployment and changes with DR
- support for the standby can easily be absorbed by dsp
- dsp support includes an essential proactive monitor and alerting solution
- cost effective
£100 to £2000 per instance per month
- Education pricing available
- Free trial available
dsp managed services
|Service constraints||Processor architecture in our cloud providers is limited to intel compatible processors. Non Intel based workloads can be migrated into our cloud offereing after a conversion exercise / process.|
|Email or online ticketing support||Email or online ticketing|
|Support response times||Structured SLA according to priority|
|User can manage status and priority of support tickets||Yes|
|Online ticketing support accessibility||None or don’t know|
|Phone support availability||24 hours, 7 days a week|
|Web chat support||No|
|Onsite support||Yes, at extra cost|
Post project warranty of 30 days
if dsp support is in place then std working hours 0830-1800 or 247.
cost is variable dependant on a number of factors.
dp will provide both a technical account manager and a team of cloud/DBA support engineers.
|Support available to third parties||Yes|
Onboarding and offboarding
|Getting started||This is not an end user deployment|
|End-of-contract data extraction||Standard DBA standby db decommission applies, dsp can assist in this and removal of VM's. Data extraction is not an issue as this is passive standby solution. All the data exists in the primary database.|
|End-of-contract process||The standby db will be spun down and removed along with the VM. If dsp managed services are engaged there is an additional end or service process which is covered under a different service description.|
Using the service
|Web browser interface||Yes|
|Using the web interface||Dsp managed services provide web portal views on alerts and service desk tickets status.|
|Web interface accessibility standard||None or don’t know|
|How the web interface is accessible||N/a|
|Web interface accessibility testing||N/a|
|Command line interface||Yes|
|Command line interface compatibility||
|Using the command line interface||Full O/S access|
|Independence of resources||As per the cloud vendor guarantees (AWS, Azure and Oracle).|
|Infrastructure or application metrics||Yes|
|Supplier type||Not a reseller|
|Staff security clearance||Other security clearance|
|Government security clearance||Up to Developed Vetting (DV)|
|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||Other|
|Other data at rest protection approach||Tbc|
|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|
Backup and recovery
|Backup and recovery||Yes|
|What’s backed up||
|Backup controls||Specification of what is backed is defined at the service definition stage and during take on.|
|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 protection between buyer and supplier networks||
|Data protection within supplier network||IPsec or TLS VPN gateway|
Availability and resilience
|Guaranteed availability||Availability matches that of the end cloud provider (Microsoft for Azure, Amazon for AWS and Oracle for Oracle cloud. dsp services layered over this have separate SLA's as described in another service section.|
|Approach to resilience||Aavailable on request.|
Outages are reported by the the vendor via public dashboard and email alerts.
In addition DSP's services including monitoring (if taken) will also alert via dashboards, email, phone and text messages generated from dsp's monitor and alerting solution. e.g. for Azure dsp has specific Azure UIM probes that will alert our service desk to an outage (and other defined errors).
Identity and authentication
|Other user authentication||Dsp can use a variety of authentication depending on the requirement. dsp DBA's for example would use 2 factor authenticatipn for specific sites.|
|Access restrictions in management interfaces and support channels||We employ role-based access controls wherever supported by the service. We apply the principle of least privilege for all users. Admin rights are only granted where there is a clear and justified requirement. Administrative actions are audited and checked regularly.|
|Access restriction testing frequency||At least every 6 months|
|Management access authentication||Username or password|
|Devices users manage the service through||
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||User-defined|
|Access to supplier activity audit information||Users contact the support team to get audit information|
|How long supplier audit data is stored for||User-defined|
|How long system logs are stored for||User-defined|
Standards and certifications
|ISO/IEC 27001 certification||No|
|ISO 28000:2007 certification||No|
|CSA STAR certification||No|
|Other security accreditations||No|
|Named board-level person responsible for service security||Yes|
|Security governance accreditation||Yes|
|Security governance standards||Other|
|Other security governance standards||The cloud vendor will have a strict governance standard, available upon request.|
|Information security policies and processes||As per the vendor policy, available upon request.|
|Configuration and change management standard||Supplier-defined controls|
|Configuration and change management approach||
Dsp is aligned to the ITIL framework.
Cloud assets are recorded in our secure CMDB.
We advise on regular CAB meeting to discuss, plan and action changes in a structured manner. Changes are submitted 24 hrs prior to CAB meeting and require approval prior to the change happening.
|Vulnerability management type||Supplier-defined controls|
|Vulnerability management approach||
Dsp maintain a senior level partner status with the vendors eg. Microsoft and Oracle from whom receive security updates notifications such as bug reports and critical patches to secure vulnerabilities.
dsp's patching regimes agreed with the end clients aims to apply regular patching on a quarterly basis and critical security patches will be applied immediately following approval at a emergency CAB.
dsp gets it's information from a variety of online sources and from the vendors. Details available on request.
|Protective monitoring type||Supplier-defined controls|
|Protective monitoring approach||
The cloud providers/vendors provide industry standard monitoring and protection that will alert our engineers in the event of policy violations, unusual access patterns and other security events.
when a compromise is detected, dsp will convene an emergency meeting of relevant stakeholders authorised to take preventative action to resolve a security incident. Clear communication to clients at all times, clarifying impact of incidents and actions taken to resolve them.
we would respond immediately.
|Incident management type||Supplier-defined controls|
|Incident management approach||Dsp uses the ITIL framework incident management approach with well defined procedures covering both standard working hours and 24*7. Procedures cover regular processing of incidents against a priority ranking with an associated SLA. This is managed via our service desk system which also handles incidents initiated via the automated monitor and alerting. The process also includes structured client updates and responses via email.|
|Approach to secure software development best practice||Supplier-defined process|
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||The cloud vendor (Azure, AWS etc)|
|How shared infrastructure is kept separate||There is a highly secure subscription model where all the VM's within a subscription are locked down to a specific user base.|
|Price||£100 to £2000 per instance per month|
|Discount for educational organisations||Yes|
|Free trial available||Yes|
|Description of free trial||Varies according to the situation but for example sap provides a database DR as a service in both AWS and Amazon as a trail service.|
|Pricing document||View uploaded document|
|Terms and conditions document||View uploaded document|