brightsolid online innovation Ltd.

Brightsolid Public Cloud

Brightsolid's Public Cloud offerings are tailored to those looking for a hybrid cloud. Customers are supported in the choice, provision and configuration of virtual machines in Azure and Amazon by a trusted partner.


  • Support build and configuration of AWS & Azure Services
  • A range of options and sizes
  • A simplified billing model
  • All the features available in public cloud


  • Supported by Scottish based Cloud and Colocation Provider
  • Operated by UK owner/operator with 20+ experience in service
  • In region support by skilled and qualified UK service team
  • Tailored compute, back up and & storage options
  • Process & Procedures; ISO 27001 and Cyber Essentials + Accredited


£0.0004 per instance

  • Free trial available

Service documents

G-Cloud 10


brightsolid online innovation Ltd.

Malcolm Smith

01382 429000

Service scope

Service scope
Service constraints See: & www
System requirements See

User support

User support
Email or online ticketing support Email or online ticketing
Support response times Clients can contact Brightsolid by telephone and simple questions can be answered immediately. As an SLA Brightsolid would consider general questions as a Priority 4 request and has a 4 hour response
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 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 None or don’t know
How the web chat support is accessible Brightsolid allows clients with accessibility needs to contact us using skype for business. Skype for business includes a range options for visual or hearing impaired clients, including the use of own devices for skype allowing the use of favoured assistive technologies for the visually impaired such as screen readers or magnifiers. For hearing impaired users transcription services can be made available in real time via CART (Communication Access Real-time Translation)
Web chat accessibility testing Brightsolid has not competed testing of these services in house. The use of standard Microsoft products is preferred as these have gone through rigorous market testing by the market leader in office based software
Onsite support Yes, at extra cost
Support levels Brightsolid has a multi layered support approach. We offer pre-delivery support to design & configure solutions for clients. In life support is provided to authorise users via our support desk. Our support desk operate a tickets based priority system to respond to support requests. Users are able to contact support via a number of channels including email, phone and chat. Additional support is offered via our service management and client engagement manager teams.
Support available to third parties Yes

Onboarding and offboarding

Onboarding and offboarding
Getting started Users are provide with documentation to help them get started for using the service; During the set up phase Brightsolid engineers support any user start requirements
Service documentation Yes
Documentation formats
  • HTML
  • PDF
End-of-contract data extraction Data may be copied out 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

Using the service

Using the service
Web browser interface Yes
Using the web interface Customers will be provided with access to the relevant service post implementation to manage the service:

Services can be set up an fully managed through the web console and

No limitation shall be set unless client request limitation for cost capping purposes
Web interface accessibility standard None or don’t know
How the web interface is accessible Brightsolid allows access into Microsoft and Amazon's self services portals: Both companies build accessibility into their products enabling users to personalize their PCs to make them safer and easier to see, hear, and use. Accessibility is a fundamental consideration during product design, development, testing, and release
Web interface accessibility testing Brightsolid has not competed testing of these services in house. The use of standard Microsoft and Amazon products is preferred as these have gone through rigorous market testing by the market leaders in cloud computing and office software
What users can and can't do using the API All functionality is exposed through the AWS API. For Microsoft Solutions Users have access to the Azure API Management Service and the Azure Service Management API
API automation tools
  • Ansible
  • Chef
  • SaltStack
  • Terraform
  • Puppet
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 CLI


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 ensure that customers are segregated via security management processes/controls at the network and hypervisor level.

The public cloud providers continuously monitors service usage to project infrastructure needs to support availability commitments/requirements and maintain a capacity planning model to assess infrastructure usage and demands at least monthly, and usually more frequently. In addition, capacity planning models support the planning of future demands to acquire and implement additional resources based upon current resources and forecasted requirements.
Usage notifications Yes
Usage reporting
  • Email
  • SMS
  • Other


Infrastructure or application metrics Yes
Metrics types
  • CPU
  • Disk
  • HTTP request and response status
  • Memory
  • Network
  • Number of active instances
Reporting types
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request


Supplier type Reseller providing extra support
Organisation whose services are being resold AWS & Amazon

Staff security

Staff security
Staff security clearance Conforms to BS7858:2012
Government security clearance Up to Developed Vetting (DV)

Asset protection

Asset protection
Knowledge of data storage and processing locations Yes
Data storage and processing locations
  • United Kingdom
  • European Economic Area (EEA)
User control over data storage and processing locations Yes
Datacentre security standards Supplier-defined controls
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 Wherever appropriate, Public Cloud Users are offeredoptions to add additional security layers to data at rest, via scalable and efficient encryption features. These can include flexible key management options and dedicated hardware-based cryptographic key storage.
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 In-house destruction process

Backup and recovery

Backup and recovery
Backup and recovery Yes
What’s backed up
  • Files
  • Virtual Machines
  • Databases
Backup controls Additional Back Up Services are available from both providers: up
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
  • 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
  • Bonded fibre optic connections
  • Legacy SSL and TLS (under version 1.2)
Data protection within supplier network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Legacy SSL and TLS (under version 1.2)

Availability and resilience

Availability and resilience
Guaranteed availability Brightsolid typically guarantees 99.9% availability for client environments however this is subjects to the SLA of the service being provided by the Public Cloud Supplier used
Approach to resilience Brightsolid designs our infrastructure to be N+1 compliant. This includes our data centres inclusive of all main components such as power, cooling, fire suppression and early smoke detection apparatus. Our cloud infrastructures are designed with N1 capability with infrastructure replicated in our Dundee and Aberdeen data centres. For services which are reliant on Public Cloud compute we are reliant on the resilience of the Public Cloud providers. Both public clouid providers confirm N+1 resolience in services
Outage reporting We have several options for reporting outages that are available according to client preference. These include: Real time dashboards that clients can access with agreed metrics on availability; Alerts which can be automatically set up to email or page to authorised clients. Additionally our 24 hour support team will contact users if services outages occur. Outages which breach agreed service levels are followed up with Incident Reports detailing Root Cause Analysis and any follow up actions

Identity and authentication

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
Access restrictions in management interfaces and support channels User access control are available to AWS/Azure 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 tagged and only permitted with relevant security keys

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

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

Standards and certifications

Standards and certifications
ISO/IEC 27001 certification Yes
Who accredited the ISO/IEC 27001 Certification Europe (UK) Ltd/Public Cloud providers by alternative providers
ISO/IEC 27001 accreditation date 19/01/2015
What the ISO/IEC 27001 doesn’t cover Public Cloud infrastructures - these are certified by AWS and Microsoft respectively
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 Yes
Security governance standards ISO/IEC 27001
Information security policies and processes "brightsolid implements 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.  Line managers in association with our security team are responsible for familiarizing employees with security policies.

brightsolid has established information security processed and procedures that are aligned with defined structure, reporting lines, and responsibilities. Leadership involvement provides clear direction and visible support for security initiatives.  

The output of internal security 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.

Operational security

Operational security
Configuration and change management standard Supplier-defined controls
Configuration and change management approach Changes to the public cloud provider 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 Supplier-defined controls
Vulnerability management approach The public cloud providers frequently 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.

brightsolid and the public cloud providers monitors newsfeeds/vendor sites for patches and receives customer intelligence via specific customer feedback channels

with public cloud services customers are responsible for all scanning, penetration testing, file integrity monitoring and intrusion detection for their services. Scans should include customer IP addresses.
Protective monitoring type Supplier-defined controls
Protective monitoring approach The Public Cloud providers collect information on unauthorized intrusion attempts, usage abuse, and network/application bandwidth usage. Devices monitor:

• Port scanning attacks
• Usage (CPU, processes, disk utilization)
• Application metrics
• Unauthorized connection attempts

Near real-time alerts flag incidents, based on set thresholds.

Logging is conducted to store audit data on customers environments
Incident management type Supplier-defined controls
Incident management approach Brightsolid follows an ITIL based incident management process following 5 key steps:
1) Incident Identification; Our management tools, employees or customers highlight an issue;
2) Incident Logging; The incident is logged in our Service Management System
3) Incident Categorisation & Prioritisation; We categorise and prioritise incidents based on our SLA;
4) Response: Appoint a incident team made up of an incident manager, technical lead and communications manager; This team drive the incident through incident diagnosis; escalation; investigation and diagnosis; resolution and recovery to incident closure
5) Incident Reports are issued inclusive of follow up actions

Secure development

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

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 AWS & Microsoft Azure Proprietary software
How shared infrastructure is kept separate Organisations are kept separate through the separation feature of the virtualisation software and the several layers of network logical separation using solutions such as VLAN, Edge Device separation and VRFs. Public cloud solutions can also be architected with complete physical separation.

Energy efficiency

Energy efficiency
Energy-efficient datacentres Yes


Price £0.0004 per instance
Discount for educational organisations No
Free trial available Yes
Description of free trial Various Trial services are available with public cloud options. Detailed information available upon request


Pricing document View uploaded document
Skills Framework for the Information Age rate card View uploaded document
Service definition document View uploaded document
Terms and conditions document View uploaded document
Return to top ↑