Anson Resolution

Managed Infrastructure

Compute as a Service provides you with the trusted, connected and flexible cloud platform you need to deliver enterprise and cloud-native applications. Cloud Storage is a secure, massively scalable and very resilient next generation storage platform designed to address a wide variety of use-cases.

Features

  • Select hosting from: AWS, Azure, UKCloud or Google.
  • Integrate with dedicated or private environments.
  • Resilience through the use of multiple regions
  • Aligned with NCSC Cloud Security Principles.
  • Connect over the internet, PSN, HSCN, RLI or JANET.
  • Comprehensive Monitoring solution.
  • Hybrid options available
  • Cloud object storage natively enables application deduplication & redundancy.
  • Integrates with existing, native and virtualized, enterprise applications.
  • Pay for what you use, scale indefinitely and on-demand.

Benefits

  • Enabling cost savings by selection of most appropriate hosting option.
  • Get the resources you need, when you need them.
  • Reduce risk by using proven design blueprints
  • Architect solutions with confidence that applications and services remain available.
  • Delivers solutions on a cloud aligned with NCSC best practice.
  • Multiple use cases: Backup, Archiving, replacement for shared storage.
  • Reduce local compliance overhead with pre-accredited solutions.
  • Know where your data is at all times.
  • Easy to adopt: test, develop and run proof of concepts.
  • Avoid the liability and cost of owning your own infrastructure.

Pricing

£5000 per instance per month

Service documents

Framework

G-Cloud 11

Service ID

8 2 6 4 7 9 6 3 6 2 6 0 1 4 1

Contact

Anson Resolution

Mike Dyer

07984 781614

contact@ansonresolution.co.uk

Service scope

Service constraints
The Services are always available except for:
• scheduled maintenance carried out during a regular maintenance window, such as backups, database administration and log processing.
• Public holidays (in England and Wales) where the service desk will not be manned.
For scheduled maintenance windows we will give customers at least 4 weeks notice, and endeavour to schedule the windows for lower impact time periods. Over any 12 month period, the average maintenance windows will not exceed 4 hours per month.
All users, configurators and administrators will require internet access or connectivity through the government secure internet to the platform.
System requirements
  • EUDs fully patched and protected by up to date AV.
  • Scheduled maintenance carried out during a regular maintenance window.
  • All users require internet access or government network connectivity.
  • All users to sign SyOps and Acceptable Use Policy.

User support

Email or online ticketing support
Email or online ticketing
Support response times
Initial response within one hour, Monday to Friday 0800 to 1800.
No response at weekends.
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
Web chat is based around Slack which can be acessed by any web browser that supports HTML5 or its own desktop client, and can also accessible programmatically via its API.
Web chat accessibility testing
Nil.
Onsite support
Yes, at extra cost
Support levels
There are two Service levels offered:

• Standard, which provides support during the working day, supported by 24/7 monitoring.
• Enhanced, which allows for long day or 24/7 support where required. Enhanced support incurs additional charges.

All Service Levels include a full ITIL Service Management system including Incident, Problem and Change Management, Release and Deployment Management, Access,
Availability and Capacity Management, Service Measurement and Reporting.
A Technical Account Manager will own the relationship and be responsible for ensuring that the service meets the customers’ needs.
Level 1 Support responds to helpdesk queries, simple resolution such as passwords and account changes.
Level 2 Support includes: Infrastructure support, responding to all support issues in line with agreed SLAs, performing root cause analysis of problems, including raising tickets for other 3rd party support providers, if required.
Level 3 application support issue fixes are provided either by client or third party delivery teams, with support issues added to the story backlog for prioritisation by the product owner.
Disaster Recovery processes are assumed to have been designed and implemented as part of systems and applications development. Our support offering includes carrying out any agreed disaster recovery procedures where these are not automated.
Support available to third parties
Yes

Onboarding and offboarding

Getting started
A Service Specialist will work with the client to understand the scope and nature of the required services, including: the deployment process, any integration requirements of legacy services/applications, end users, segmentation and associated security profiles. Details include agreeing reporting requirements and scheduling, formats and transportation. This will normally take place prior to contract award.
It is assumed that the Customer will work together with the Support team to decide on roles and responsibilities of customer and supplier. Customer will work together with the Support Team on the requirements for the cloud environment and provide sign-off on the same before commencement of services.
Designated and authorized resource from customer side will actively work with Support Team to resolve any dependencies on the customer team.
We will provide User Guides, both online and in crib card format as part of user activation.
Onsite training can also be provided as an additional charged item.
Service documentation
Yes
Documentation formats
PDF
End-of-contract data extraction
All data will be returned to the client, on CD or DVD, in the original format it was stored and managed. Additional formats, such as client specific XML, or export mechanisms can be provided at extra cost.
Log data can also be transferred and is charged in accordance with our SFIA rates.
End-of-contract process
Termination of service, for any reason, triggers the development and implementation of a Termination phase. A Termination Plan will be produced and agreed with the customer. A generic termination plan is available, on request, and this will be tailored to reflect appropriate roles and responsibilities. Production of this tailored plan is included within the service price.
On termination of the service, all client data will be destroyed in accordance with Anson Resolution Information Assurance processes, which are appropriate for Official and Official Sensitive data. For particularly sensitive data additional Government approved sanitization or destruction mechanisms can be deployed, at extra cost.

Using the service

Web browser interface
No
API
No
Command line interface
No

Scaling

Scaling available
Yes
Scaling type
Manual
Independence of resources
Each user operates in a separate instance, provisioned with their own platform.
Usage notifications
Yes
Usage reporting
Email

Analytics

Infrastructure or application metrics
Yes
Metrics types
  • CPU
  • Disk
  • Memory
  • Network
  • Number of active instances
Reporting types
  • Regular reports
  • Reports on request

Resellers

Supplier type
Not a reseller

Staff security

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

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
Supplier-defined controls
Penetration testing frequency
At least once a year
Penetration testing approach
‘IT Health Check’ performed by a CHECK service provider
Protecting data at rest
Physical access control, complying with another standard
Data sanitisation process
Yes
Data sanitisation type
Deleted data can’t be directly accessed
Equipment disposal approach
A third-party destruction service

Backup and recovery

Backup and recovery
Yes
What’s backed up
  • Files
  • Virtual Machines
  • Applications
  • Databases
Backup controls
By agreed amendment to the Service Management Plan.
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-in-transit protection

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

Availability and resilience

Guaranteed availability
Availability 97.0%. Users are credited a service credit of up to 10% of monthly charge (15% for Enhanced support) if availability falls below this level.
Standard SLAs are assumed as:
• 0800 to 1800 for Standard Support
• 24x7 Access For Enhanced Support and Crisis incidents only
Approach to resilience
Available on request.
Outage reporting
E Mail alerts.
Recorded message.

Identity and authentication

User authentication
2-factor authentication
Access restrictions in management interfaces and support channels
There is no access from User Accounts to management interfaces.
System Admins access management capabilities from dedicated machines connected via an SSTP VPN requiring proprietary Certificates.
Access restriction testing frequency
At least once a year
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

Access to user activity audit information
Users contact the support team to get audit information
How long user audit data is stored for
At least 12 months
Access to supplier activity audit information
Users contact the support team to get audit information
How long supplier audit data is stored for
At least 12 months
How long system logs are stored for
Between 1 month and 6 months

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

Named board-level person responsible for service security
Yes
Security governance certified
No
Security governance approach
Security Governance follows the ISO 27001 model. Certification is being applied for.
Information security policies and processes
NOC/SOC are responsible for monitoring systems and responding to customer events. In the first instance they are accountable to the Head of Customer Support, whose responsibilities include the secure operation of all systems. Where appropriate they pass issues for resolution to either the System Design Authority, they do, however, retain ownership of the issues’ resolution.
The Chief Security Officer (CSO) is responsible for all aspects of security of the company and its services. He:
• Runs an internal and external audit programme to ensure that policies are being adhered to and are effective.
• Maintains a record of who has signed SyOps and what access they have been granted.
• Has oversight of the development, maintenance and update of risk assessments.
• Runs a security training programme for all staff.
• Is available to provide advice on the handling of security incidents.
The CSO is directly accountable to the CEO.
The System Design Authority owns the Change process including making security assessments of change impacts, and where appropriate obtaining advice from the CSO.

Operational security

Configuration and change management standard
Supplier-defined controls
Configuration and change management approach
The System Design Authority owns the Configuration Management Database and process.
Configuration items are discovered through an automated process. Verification audits take place prior to, and after, major changes, and recovery of a major incident. Additionally Configuration verification is conducted periodically.
Change Process: Classification begins when an incident or change is identified. If appropriate a Change Request is raised and passed for Evaluation where the impact is quantified including assessing the security implications. Modeling and Testing is conducted to ensure that the impact on the environment is fully understood. In Implementation the change is embodied and Configuration Items recorded.
Vulnerability management type
Supplier-defined controls
Vulnerability management approach
Regular vulnerability scans are performed on the system.
On identification, Vulnerabilities are prioritised based on the Common Vulnerability Scoring System (CVSS) Version 3. This uses analysis of the Exploitability and Impact of a Vulnerability to generate an initial assessment of its priority, and to track the progressive impact of mitigations applied.
Normally a 4 week Test and Patch cycle is employed, however, there is also a facility for expedited deployment of urgent patches as an emergency Change, identified either by CVSS scoring or by early warning from organisations such as CiSP, Threat Intelligence or Customer CERTs.
Protective monitoring type
Supplier-defined controls
Protective monitoring approach
Log Data is recorded to a policy aligned with CESG Good Practice Guide 13 (GPG 13) Recording Profile A (Aware), which is appropriate for Official Data. Enhanced collection to align with GPG 13 Recording Profiles B (Deter), C (Detect/Resist), D (Defend) for data of greater sensitivity can also be provided at additional cost
The data we monitor includes: Integrated dynamic asset management and network discovery, log and event correlation and analysis, Network Traffic Analysis, Deep Packet Inspections, IDS, Vulnerability Scanning, Blacklist monitoring, Privileged User monitoring, Collaboration and continuous service improvement.
Incident management type
Supplier-defined controls
Incident management approach
Incidents can be triggered either by Customer issues or in response to system events. Standard processes are defined for common events.
Initial Customer Response:
• Priority 1 –15 minutes
• Priority 2 –4 hours
• Priority 3 –12 hours
• Priority 4 –24 hours
Incident Resolution:
• Priority 1 –8 hours
• Priority 2 –16 hours
• Priority 3 –24 hours
• Priority 4 –28 hours

In response to either a very high Business Impact or multiple related instances a Major Incident can be declared, bringing a higher level of support resourcing and a dedicated Incident communications channel.

Secure development

Approach to secure software development best practice
Conforms to a recognised standard, but self-assessed

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
UK Cloud
How shared infrastructure is kept separate
Compute separation is enforced at the hypervisor level by the trusted VMWare product.
Each platform user owns separate Operating System, building on this separation.
Management access is separated from user access, and the strength of this separation is subject to regular testing.
Customer networks are separated by VLANs and the implementation of the separation regularly monitored.

Energy efficiency

Energy-efficient datacentres
No

Pricing

Price
£5000 per instance per month
Discount for educational organisations
No
Free trial available
No

Service documents

Return to top ↑