We have experience and knowledge of managing cloud-based public service databases, and can use a hybrid approach; utilising new and existing functionalities into Azure SQL database, adhering to information governance principles and standards. Our bespoke database tool PPwT, is tailored to the public sector and aligned to NHS digitalisation aims.
- Database-as-a-Service which adapts as the organisation grows
- SQL database continually learns your unique software patterns
- Tunes performance
- Helps you manage and monitor apps
- Connects to the SQL database in your preferred language
- Helps you build security enhanced applications
- Pay as you go service
- Building and maintaining applications is easier
- Built-in intelligence improves performance
- Conforms to DPA
£550 to £1250 per person
Clarity Tech Ltd
|Service constraints||All Microsoft Azure constraints and limits will be applicable e.g. Virtual Machine Scale Sets limits, Networking limits, DNS limits, Storage limits etc|
|Email or online ticketing support||Email or online ticketing|
|Support response times||
Clarity Tech JIRA Service Tool
We will acknowledge the issue within 4 working hour and provide a response including an action plan for resolution or cause within 8 working hours.
We will acknowledge the issue within 6 working hours and provide a response including an action plan for resolution or cause within 10 working hours.
We will respond within 1 working day and will aim to provide a fix within 5 working days of the incident being reported.
Where applicable, we will provide a solution as part of the next release.
|User can manage status and priority of support tickets||No|
|Phone support availability||9 to 5 (UK time), Monday to Friday|
|Web chat support||No|
|Onsite support||Yes, at extra cost|
We provide 1st, 2nd and 3rd Level support.
1st Line: £120/day
2nd Line: £280/day
3rd Line: £400/day
We will provide technical account manager
|Support available to third parties||Yes|
Onboarding and offboarding
|Getting started||Will provide user documentation.|
|Other documentation formats||MS Word|
|End-of-contract data extraction||
All Virtual Machine Images and Data Storage are available in a Azure Data Warehouse, which cab be downloaded from these storage account.
It depends upon user's retention policy.
|End-of-contract process||End-of-contract will be dependent on the specific requirements of the solution provided. All the necessary Data ready for export, extraction, or deletion will be provided and included in the price of contract. Any additional requirements will be charged according to our SIFA rate card.|
Using the service
|Web browser interface||Yes|
|Using the web interface||Will provide access to Azure Web Interface and Portal to manage service. User will be provided access to Azure Dashboard to carry out changes. Note: Role-based access control (RBAC) will be applied, which will enables access management for Azure resources. Using RBAC, you can segregate duties within your team and grant only the amount of access to users, groups and applications that they need to perform their jobs. Role-based access can be granted to users using the Azure portal, Azure Command-Line tools or Azure Management APIs.|
|Web interface accessibility standard||WCAG 2.1 AA or EN 301 549|
|Web interface accessibility testing||Basic Testing|
|What users can and can't do using the API||Users can perform basic create, read, update, and delete (CRUD) operations by using the Representational State Transfer (REST) interface provided by SharePoint 2013. The REST interface exposes all of the SharePoint entities and operations that are available in the other SharePoint client APIs. One advantage of using REST is that you don’t have to add references to any SharePoint 2013 libraries or client assemblies. Instead, you make HTTP requests to the appropriate endpoints to retrieve or update SharePoint entities, such as webs, lists, and list items. SharePoint Client API will depend on following three factors; The type of application, Your existing skills and The device on which the code runs. Note: Role-based access control (RBAC) will be applied, which will enables access management for Azure resources. Using RBAC, you can segregate duties within your team and grant only the amount of access to users, groups and applications that they need to perform their jobs. Role-based access can be granted to users using the Azure portal, Azure Command-Line tools or Azure Management APIs.|
|API automation tools||Puppet|
|API documentation formats||
|Command line interface||Yes|
|Command line interface compatibility||
|Using the command line interface||Using Azure CLI 2.0, which is Azure's new command-line experience for managing Azure resources. It can be used on macOS, Linux, and Windows. Complete details of using CLI2.0 and any limitations are available in https://docs.microsoft.com/en-us/cli/azure/overview. Note: Role-based access control (RBAC) will be applied, which will enables access management for Azure resources. Using RBAC, you can segregate duties within your team and grant only the amount of access to users, groups and applications that they need to perform their jobs. Role-based access can be granted to users using the Azure portal, Azure Command-Line tools or Azure Management APIs.|
|Independence of resources||Using Azure Resource Manager and Monitoring within Azure Portal, which will enables us to keep track of demand.|
|Infrastructure or application metrics||Yes|
|Supplier type||Reseller providing extra support|
|Organisation whose services are being resold||Microsoft/Rackspace/UKCloud|
|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||Complies with a recognised standard (for example CSA CCM version 3.0)|
|Penetration testing frequency||At least every 6 months|
|Penetration testing approach||In-house|
|Protecting data at rest||
|Data sanitisation process||Yes|
|Data sanitisation type||
|Equipment disposal approach||A third-party destruction service|
Backup and recovery
|Backup and recovery||Yes|
|What’s backed up||Resources within Microsoft Azure and using it's backup facility|
User will use Azure Scheduler that lets them create jobs in the cloud that reliably invoke services inside and outside of Azure – such as calling HTTP/S endpoints or posting messages to Azure Storage queues, Azure Service Bus queues or Azure Service Bus topics. User can choose to run jobs straight away, on a recurring schedule or at some point in the future.
Scheduler allows users to create, update, delete, view, and manage jobs and job collections programmatically, by using scripts, and in the portal.
|Scheduling backups||Users contact the support team to schedule backups|
|Data protection between buyer and supplier networks||
|Data protection within supplier network||Legacy SSL and TLS (under version 1.2)|
Availability and resilience
|Guaranteed availability||99.9% - Will be covered by Microsoft SLA|
|Approach to resilience||Using Azure|
|Outage reporting||Email alerts|
Identity and authentication
|Access restrictions in management interfaces and support channels||
Will use Azure identity management and access control security best practices include:
Centralize your identity management
Enable Single Sign-On (SSO)
Deploy password management
Enforce multi-factor authentication (MFA) for users
Use role based access control (RBAC)
Control locations where resources are created using resource manager
|Access restriction testing frequency||At least every 6 months|
|Management access authentication||
|Devices users manage the service through||Directly from any device which may also be used for normal business (for example web browsing or viewing external email)|
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||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 certifications||Yes|
|Any other security certifications||Cyber Security Essential|
|Named board-level person responsible for service security||Yes|
|Security governance certified||No|
|Security governance approach||Information Governance Training|
|Information security policies and processes||
|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||
We use Microsoft Visual Services tool as well as Azure Monitoring dashboard to track components of our services.
We use Azure Cloud to simulate testing environment which is similar to the operating environment. Testing including performance and security is carried out prior to release.
|Vulnerability management type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Vulnerability management approach||Will use Azure Security Center which offers integrated vulnerability assessment with Qualys cloud agents as part of the Virtual Machine. The solution can be deployed to multiple VMs at one time and once deployed, the Qualys agent will start reporting vulnerability data to the Qualys management platform, which in turn provides vulnerability and health monitoring data back to Security Center. Users can quickly identify vulnerable VMs from the Security Center dashboard. Additional reports and information are available in the Qualys management console, which is linked directly from Security Center.|
|Protective monitoring type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Protective monitoring approach||Using Microsoft global 24x7 incident response service that works to mitigate the effects of attacks and malicious activity. The incident response team follows established procedures for incident management, communication, and recovery, and uses discoverable and predictable interfaces with internal and external partners alike.|
|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||
Will use following process phases:
• Identification – Events will be investigated and will be assigned a severity classification.
• Containment – The escalation team will evaluates the scope and impact of an incident.
• Eradication – After the situation is contained, the escalation team moves toward eradicating any damage caused by the security breach, and identifies the root cause for why the security issue occurred.
• Recovery – System and services will be returned to a full working capacity.
• Customer’s notified if data breaches or unauthorized access.
|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||Microsoft|
|How shared infrastructure is kept separate||Depending on organisation structure, there are different options available in Azure e.g. can use Virtual Network. It will also depend on architectural design as well.|
|Description of energy efficient datacentres||
We use Microsoft Data Centers which adheres to the EU Code of Conduct for Energy Efficient datacentres. For full details please refer to the following link.
|Price||£550 to £1250 per person|
|Discount for educational organisations||No|
|Free trial available||No|