ProArch IT Solutions

Microsoft Azure Cloud Data Platform

An opinionated architecture for processing data of varying volume, variety, veracity and velocity
Automated accelerators to deploy, configure and secure this architecture in Azure
Options for deploying a team to help build out data assets or work in a mixed model

Features

  • Data ingestion
  • Data transformation
  • Data modelling
  • Data security
  • Data visualisation
  • Real-time, batch, ad-hoc and once off data processing
  • Data wrangling
  • Pipelines
  • Optional AI (e.g. Machine Learning) and Data Science support
  • Data Lake

Benefits

  • Quick to deploy
  • Opinionated architecture reduces technical sprawl
  • Opinionated architecture provides a proven patterns
  • PaaS pay as you Go convenience and pricing
  • CI/CD automation by design
  • SecDevOps by design
  • Documented design accelerates architectural approval
  • Optimised through experience from previous projects
  • Build on top it yourself or work with us
  • Cold, warm and hot storage options

Pricing

£450 to £1400 per person per day

Service documents

G-Cloud 11

677723479375018

ProArch IT Solutions

Jason Barrett

07973115088

jasonb@proarch.com

Service scope

Service scope
Service constraints We provide a cloud platform hosted on Azure and design DR and Business Continuity in to implementations. However we are subject to Microsoft's Azure SLAs. https://azure.microsoft.com/en-gb/support/legal/sla/summary/
System requirements
  • Access to the internet
  • Approved or ability for us to assist with cloud approval
  • Azure Active Directory or ability for us to help implement

User support

User support
Email or online ticketing support Email or online ticketing
Support response times Typically within a few hours
User can manage status and priority of support tickets No
Phone support Yes
Phone support availability 24 hours, 7 days a week
Web chat support No
Onsite support Yes, at extra cost
Support levels Support is negotiated on a per-customer basis depending on requirements. This could range from ad-hoc support to a dedicated on-site resource.
Support available to third parties No

Onboarding and offboarding

Onboarding and offboarding
Getting started Stakeholders may review the High Level Design to gain an understanding of the platform. Further documentation specific to client implementations specify the configuration deployed. Engagement options include project delivery, co-working and knowledge transfer through pairing or more traditional training. Extensive training is available for the tools that comprise the platform.
Service documentation Yes
Documentation formats
  • HTML
  • PDF
End-of-contract data extraction Proarch either leverage a client's Azure instance (subscription) where we deploy on to client-controlled environments with full access to the data or alternatively, we leverage the Microsoft CSP (Cloud Solution Provider) model where we provision and manage the Azure subscription but the client retains the right to transfer or take ownership. Typically the platform lives on after the contract completes.
End-of-contract process Typically the data platform remains in operation indefinitely and past the completion date of the contract.

Using the service

Using the service
Web browser interface Yes
Using the web interface View and manage resources
Create data workflows
Access data wrangling tools
Build out data engineering code
Build and deploy Data Science models
Access build and release pipelines
View, branch and merge source code and assets
Web interface accessibility standard WCAG 2.1 AA or EN 301 549
Web interface accessibility testing https://cloudblogs.microsoft.com/industry-blog/government/2018/09/11/accessibility-conformance-reports/
API Yes
What users can and can't do using the API Our platform is underpinned by Microsoft Azure's extensive Management API
API automation tools Other
Other API automation tools Azure DevOps
API documentation Yes
API documentation formats
  • Open API (also known as Swagger)
  • HTML
  • Other
Command line interface Yes
Command line interface compatibility
  • Linux or Unix
  • Windows
  • MacOS
Using the command line interface Our platform is underpinned by Microsoft Azure and is orchestrated using Azure CLI )https://docs.microsoft.com/en-us/cli/azure/?view=azure-cli-latest) and PowerShell where required. Note that not all features are supported in CLI and require PowerShell. PowerShell is only supported in Windows.

Scaling

Scaling
Scaling available Yes
Scaling type Manual
Independence of resources We leverage the elasticity of cloud based Platform as a service. Scale for some components is fully elastic where you pay for what you use. These services are truly elastic where users are highly unlikely to impact others. Other services are elastic on a capacity basis, when users reach that capacity, they will start to impact each other, at which point scaling the service to a higher tier (compute and price point) will lift the ceiling.
Usage notifications Yes
Usage reporting Other

Analytics

Analytics
Infrastructure or application metrics Yes
Metrics types Other
Other metrics
  • Health Monitoring
  • Cost Monitoring
  • Volumes
  • Usage
Reporting types
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request

Resellers

Resellers
Supplier type Reseller providing extra features and support
Organisation whose services are being resold We implement a platform built on top of Azure

Staff security

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

Asset protection

Asset protection
Knowledge of data storage and processing locations Yes
Data storage and processing locations
  • United Kingdom
  • European Economic Area (EEA)
  • EU-US Privacy Shield agreement 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 once a year
Penetration testing approach Another external penetration testing organisation
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
  • Other
Other data at rest protection approach https://docs.microsoft.com/en-us/azure/security/security-azure-encryption-overview
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
Backup and recovery Yes
What’s backed up
  • Configuration
  • Data
  • Metadata
  • Code
Backup controls This is built in to the platform configuration via replicating data in to sister data centers. Frequency and scope can be controlled.
Datacentre setup Multiple datacentres with disaster recovery
Scheduling backups Supplier controls the whole backup schedule
Backup recovery Users contact the support team

Data-in-transit protection

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
  • Other
Other protection between networks Expressroute can be implemented. https://azure.microsoft.com/en-gb/services/expressroute/
Integration runtimes are used for secure data gateways: https://docs.microsoft.com/en-gb/azure/data-factory/create-self-hosted-integration-runtime#tlsssl-certificate-requirements
Data protection within supplier network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
Other protection within supplier network Virtual Network Service Endpoints https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-service-endpoint-policies-overview

Availability and resilience

Availability and resilience
Guaranteed availability Availability monitoring: https://azure.microsoft.com/en-us/status/
SLA and Service credits (refunds - see individual resources): https://azure.microsoft.com/en-gb/support/legal/sla/
Approach to resilience https://azure.microsoft.com/en-gb/features/resiliency/
Outage reporting Through Azure Service Health: https://azure.microsoft.com/en-gb/features/service-health/

Identity and authentication

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)
  • Dedicated link (for example VPN)
  • Username or password
Access restrictions in management interfaces and support channels Access control is managed through Azure Active Directory role based access control. https://docs.microsoft.com/en-gb/azure/active-directory/fundamentals/active-directory-whatis
Access restriction testing frequency At least once a year
Management access authentication
  • 2-factor authentication
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Dedicated link (for example VPN)
  • Username or password
  • Other
Description of management access authentication Other protection between networks

Expressroute can be implemented. https://azure.microsoft.com/en-gb/services/expressroute/ Integration runtimes are used for secure data gateways: https://docs.microsoft.com/en-gb/azure/data-factory/create-self-hosted-integration-runtime#tlsssl-certificate-requirements
Devices users manage the service through
  • Dedicated device on a segregated network (providers own provision)
  • Dedicated device over multiple services or networks
  • Any device but through a bastion host (a bastion host is a server that provides access to a private network from an external network such as the internet)
  • Directly from any device which may also be used for normal business (for example web browsing or viewing external email)

Audit information for users

Audit information for users
Access to user activity audit information You control when users can access 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 User-defined
How long system logs are stored for User-defined

Standards and certifications

Standards and certifications
ISO/IEC 27001 certification No
ISO 28000:2007 certification No
CSA STAR certification No
PCI certification No
Other security certifications No

Security governance

Security governance
Named board-level person responsible for service security Yes
Security governance certified No
Security governance approach We apply standard best practices including the principle of least privilege, RBAC (readers, contributors, admins), certificates, managed identities, four eyes, separation of concern, defence in depth and STRIDE and DREAD for threat modelling.
Information security policies and processes Security review, peer code review.

Operational security

Operational security
Configuration and change management standard Supplier-defined controls
Configuration and change management approach Code and deployment scripts are built via continuous integration off a tracked source control branch and packaged as artefacts.
Artifacts are published via automation scripts hosted on secure deployment agents (Azure DevOps)
Code outside of source control is never deployed
Automation is the primary deployment mechanism
All build and deployments are logged at a granular level
Vulnerability management type Supplier-defined controls
Vulnerability management approach We rely on PaaS components which are managed and patched by Microsoft
We configure and lock down all available security options on the services used
Protective monitoring type Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Protective monitoring approach Risks are monitored through Azure Security Center

https://docs.microsoft.com/en-us/azure/security/azure-security-management.

https://docs.microsoft.com/en-us/azure/security-center/security-center-detection-capabilities

Incidents are responded to immediately on detection.
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 We encourage customers to use their current incident management process and engage us for 2nd or 3rd line.

Secure development

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

Separation between users

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 (Azure)
How shared infrastructure is kept separate https://docs.microsoft.com/en-us/azure/security/azure-isolation

Energy efficiency

Energy efficiency
Energy-efficient datacentres Yes
Description of energy efficient datacentres https://www.microsoft.com/en-us/research/wp-content/uploads/2013/02/BuildingMoreEfficientDC.pdf

https://e3p.jrc.ec.europa.eu/node/575

Pricing

Pricing
Price £450 to £1400 per person per day
Discount for educational organisations No
Free trial available No

Service documents

pdf document: Pricing document pdf document: Terms and conditions
Service documents
Return to top ↑