Pulsant Ltd

Pulsant Managed AWS

Pulsant's Managed AWS (IaaS) solution is delivered as Infrastructure as a Service, providing flexible, high performance, high capacity virtual server (VM). This service can be used in conjunction with any of Pulsant's other cloud services to deliver a hybrid cloud model. Managed service available with defined and financially backed SLA's.

Features

  • Virtual Machine(s) hosted within AWS Cloud
  • Closely integrated with Microsoft tools
  • 99.95% availability
  • 24/7/365 service monitoring
  • Supported by a ISO27001, ISO9001 and CSA Star accredited partner
  • Direct connectivity to AWS Cloud

Benefits

  • 24/7/365 service monitoring
  • 99.95% Service availability - protecting your business reputation
  • Accredited provider aligned to Public Sector service requirements
  • Reduce CAPEX, minimal OPEX and consistent cost structure
  • Advance backup monitoring underpins industry leading SLA's
  • Over 12 years experience in supporting Public Sector organisations
  • Choice of carrier and carrier neutrality
  • Experienced audit support through dedicated compliance team
  • Flexible and scalable service

Pricing

£0.007 per instance per day

  • Free trial available

Service documents

Framework

G-Cloud 11

Service ID

8 2 0 7 8 8 7 6 4 8 6 7 2 7 1

Contact

Pulsant Ltd

John Easson

0345 119 9911

john.easson@pulsant.com

Service scope

Service constraints
The Azure platform is designed so that maintenance can be carried out without interruption to those systems being protected. Though some individual jobs may be delayed during maintenance those jobs will resume when possible and continue service as normal.

In order to reduce risk of unplanned downtime, Pulsant will apply strict change management procedures and configuration management control in applying system or application changes. A regular maintenance schedule will be applied for timely application of systems and application updates. Change control will consider impact of change and rollback procedures if release is unsuccessful.
System requirements
Internet connectivity

User support

Email or online ticketing support
Email or online ticketing
Support response times
Response times to questions and support requests are as follows:
Routine: within 30 minutes, measured during business hours

Service Affecting (must be notified by telephone): Within 30 minutes

Critical (must be notified by telephone): Within 15 minutes
User can manage status and priority of support tickets
Yes
Online ticketing support accessibility
WCAG 2.1 A
Phone support
Yes
Phone support availability
24 hours, 7 days a week
Web chat support
No
Onsite support
Yes, at extra cost
Support levels
Our Azure Cloud service provides:
Availability
The Azure Cloud designed and maintained to achieve a target availability of 99.95% measured on a calendar month.

Support Hours
We operate and resource a technical support team so that customers have access to highly trained staff 24 hours a day, 7 days a week, 365 days a year.

Change Completion
Simple - Within 24 hours
Complex - As scheduled and agreed based on change requirements

Incident Response Times:
Critical - 24/7/365 (must be notified by telephone) - response within 15 minutes
Impacting Service - 24/7/365 (must be notified by telephone) - response within 30 minutes
Routine - Business hours - response within 30 minutes measured during business hours

Azure Cloud service is delivered to clients as an infrastructure as a Service model. Where clients require a managed service, the cost of the managed service is included within the pricing document uploaded as part of this service.

The above support levels are included as part of the service and carry no additional cost.

Pulsant also provide an Account Manager.
Support available to third parties
No

Onboarding and offboarding

Getting started
Pulsant can provide suitable training for standard procedures to customers taking on the service and if required bespoke training can be arranged on request ensuring customers’ proficient use of the service.
Service documentation
Yes
Documentation formats
PDF
End-of-contract data extraction
Customers are able to remove their data at any time through the same means they uploaded. Either over their network (internet or express route) or via the Azure Import/Export services.
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.

Buyers pay for the services they use to the point of account termination. Please see the AWS UK G-Cloud 9 Pricing Document affiliated with this Service in the Digital Marketplace.

Supplier customers retain control and ownership of their data. Supplier will not erase customer data for 30 days following an account termination. This allows customers to retrieve content from Supplier services so long as the customer has paid any charges for any post-termination use of the service offerings and all other amounts due.

Using the service

Web browser interface
Yes
Using the web interface
The Cloud portal allows users to:
- Create and manage virtual networks
- Create and manage virtual machines
- Manage virtual firewalls (where those firewalls are provided by the Cloud platform)
- Allocate and de-allocate virtual resources
Web interface accessibility standard
WCAG 2.1 A
Web interface accessibility testing
Pulsant tests all software whether new, or upgrades/ enhancements to existing software prior to release.

Pulsant are committed to ensuring all user interfaces are accessible and where required will work with assistive technology users.
API
Yes
What users can and can't do using the API
Almost all functionality for each of our services is exposed through the web console.

The web console facilitates management for all aspects of the AWS account in a consolidated view whilst providing access to all services and their respective functionalities.

In some cases, specific configuration parameters of a service are dedicated to, and only available from, the CLI, SDK, or API interface.
API automation tools
  • Ansible
  • Chef
  • Terraform
  • Puppet
API documentation
Yes
API documentation formats
  • HTML
  • PDF
  • Other
Command line interface
Yes
Command line interface compatibility
  • Linux or Unix
  • Windows
  • MacOS
  • Other
Using the command line interface
AWS CLI is optimised for managing and administering AWS resources from the command line, and for building automation scripts that work against the AWS Management Console.

Scaling

Scaling available
Yes
Scaling type
  • Automatic
  • Manual
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 (i.e. EC2) ensure that customers are segregated via security management processes/controls at the network and hypervisor level.

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

Analytics

Infrastructure or application metrics
Yes
Metrics types
  • CPU
  • Disk
  • HTTP request and response status
  • Network
  • Number of active instances
  • Other
Other metrics
  • AWS resources: e.g. Amazon EC2/Amazon RDS DB instances, DynamoDB tables
  • Custom metrics generated by customers’ applications and services
  • Metrics associated with log files generated by the application
Reporting types
  • API access
  • Real-time dashboards

Resellers

Supplier type
Not a reseller

Staff security

Staff security clearance
Other security clearance
Government security clearance
Up to Baseline Personnel Security Standard (BPSS)

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
  • Other locations
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
  • Physical access control, complying with CSA CCM v3.0
  • Physical access control, complying with SSAE-16 / ISAE 3402
  • Other
Other data at rest protection approach
AWS adheres to independently validated privacy, data protection, security protections and control processes. (Listed under “certifications”).

AWS is responsible for the security of the cloud; customers are responsible for security in the cloud. AWS enables customers to control their content (where it will be stored, how it will be secured in transit or at rest, how access to their AWS environment will be managed).

Wherever appropriate, AWS offers customers options to add additional security layers to data at rest, via scalable and efficient encryption features. AWS offers 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
Yes
What’s backed up
  • Under user control
  • Machine Image
Backup controls
Manual or scheduled API call
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

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
  • Legacy SSL and TLS (under version 1.2)
  • Other
Other protection between networks
Customer environments are logically segregated to prevent users and customers from accessing resources not assigned to them. AWS gives customers ownership and control over their content by design through simple, but powerful tools that allow customers to determine how their content will be secured in transit.
AWS enables customers to open a secure, encrypted channel to AWS services using TLS/SSL, and/or IPsec or TLS VPN (if applicable), or other means of protection the customer wish to use.
API calls can be encrypted with TLS/SSL to maintain confidentiality; the AWS Console connection is encrypted with TLS.
Data protection within supplier network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
Other protection within supplier network
Customer environments are logically segregated to prevent users and customers from accessing resources not assigned to them. AWS gives customers ownership and control over their content by design through simple, but powerful tools that allow customers to determine how their content will be secured in transit.
AWS enables customers to open a secure, encrypted channel to AWS services using TLS/SSL, and/or IPsec or TLS VPN (if applicable), or other means of protection the customer wish to use.
API calls can be encrypted with TLS/SSL to maintain confidentiality; the AWS Console connection is encrypted with TLS.

Availability and resilience

Guaranteed availability
AWS currently provides SLAs for several services. Due to the rapidly evolving nature of AWS’s product offerings, SLAs are best reviewed directly on our website via the link below: https://aws.amazon.com/legal/service-level-agreements/

Well-architected solutions on AWS that leverage AWS Service SLA’s and unique AWS capabilities such as multiple Availability Zones, can ease the burden of achieving specific SLA requirements.
Approach to resilience
The AWS Business Continuity plan details the process that AWS follows in the case of an outage, from detection to deactivation. AWS has developed a three-phased approach: Activation and Notification Phase, Recovery Phase, and Reconstitution Phase. This approach ensures that AWS performs system recovery and reconstitution efforts in a methodical sequence, maximizing the effectiveness of the recovery and reconstitution efforts and minimizing system outage time due to errors and omissions.

AWS maintains a ubiquitous security control environment across all regions. Each data centre is built to physical, environmental, and security standards in an active-active configuration, employing an n+1 redundancy model, ensuring system availability in the event of component failure. Components (N) have at least one independent backup component. All data centres are online and serving traffic. In case of failure, there is sufficient capacity to enable traffic to be load-balanced to the remaining sites.

Customers are responsible for implementing contingency planning, training and testing for their systems hosted on AWS. AWS provides customers with the capability to implement a robust continuity plan, including the utilization of frequent server instance back-ups, data redundancy replication, and the flexibility to place instances and store data within multiple geographic regions across multiple Availability Zones.
Outage reporting
Public dashboard; personalised dashboard with API and events; configurable alerting (email / SMS / messaging)

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
  • Other
Other user authentication
AWS’s Identity and Access Management (IAM) system controls access to AWS services/resources. No actions are permissible without authentication. IAM facilitates the issuance of access permissions per user/group. MFA is available at no extra cost.

AWS CoudTrail allows you to log, continously monitor and retain events related to API calls across your AWS infrastructure.
Access restrictions in management interfaces and support channels
IAM provides user access control to AWS 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 signed by customers’ Amazon Secret Access Key (either the root AWS Account’s Secret Access Key or the Secret Access key of a user created with AWS IAM). Amazon EC2 API calls cannot be made on customers’ behalf without access to customers’ Secret Access Ke.

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

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
You control when users can access audit information
How long supplier audit data is stored for
Between 6 months and 12 months
How long system logs are stored for
Between 6 months and 12 months

Standards and certifications

ISO/IEC 27001 certification
Yes
Who accredited the ISO/IEC 27001
EY CertifyPoint
ISO/IEC 27001 accreditation date
03/12/2018
What the ISO/IEC 27001 doesn’t cover
N/A
ISO 28000:2007 certification
No
CSA STAR certification
Yes
CSA STAR accreditation date
03/12/2018
CSA STAR certification level
Level 2: CSA STAR Attestation
What the CSA STAR doesn’t cover
N/A
PCI certification
Yes
Who accredited the PCI DSS certification
Coalfire Systems Inc
PCI DSS accreditation date
27/03/2019
What the PCI DSS doesn’t cover
N/A
Other security certifications
Yes
Any other security certifications
  • Cyber Essentials Plus
  • ISO 27017
  • ISO 27018
  • SOC 1/2/3

Security governance

Named board-level person responsible for service security
Yes
Security governance certified
Yes
Security governance standards
  • ISO/IEC 27001
  • Other
Other security governance standards
Cyber Essentials Plus; ISO 27017; ISO 27018; SOC 1/2/3
Information security policies and processes
AWS 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. AWS Security Assurance is responsible for familiarizing employees with the AWS security policies.

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

The output of AWS Leadership 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.

Policies are approved by AWS leadership at least annually or following a significant change to the AWS environment.

Operational security

Configuration and change management standard
Supplier-defined controls
Configuration and change management approach
Changes to AWS 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
AWS Security 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.

AWS Security monitors newsfeeds/vendor sites for patches and receives customer intelligence via http://aws.amazon.com/security/vulnerability-reporting/.

AWS customers are responsible for all scanning, penetration testing, file integrity monitoring and intrusion detection for their Amazon EC2 and Amazon ECS instances/ applications. Scans should include customer IP addresses (not AWS endpoints). AWS endpoint testing is part of AWS compliance vulnerability scans.
Protective monitoring type
Supplier-defined controls
Protective monitoring approach
AWS deploys (pan-environmental) monitoring devices to collect information on unauthorized intrusion attempts, usage abuse, and network/application bandwidth usage. Devices monitor:

• Port scanning attacks
• Usage (CPU, processes, disk utilization, swap rates, software-error generated losses)
• Application metrics
• Unauthorized connection attempts

Near real-time alerts flag incidents, based on AWS Service/Security Team- set thresholds.

Requests to AWS KMS are logged and visible via account’s AWS CloudTrail Amazon S3 bucket. Logs provide request information, under which CMK, and identify the AWS resource protected through the CMK use. Log events are visible to customers after turning on AWS CloudTrail in their account.
Incident management type
Supplier-defined controls
Incident management approach
AWS adopts a three-phased approach to manage incidents:

1. Activation and Notification Phase
2. Recovery Phase
3. Reconstitution Phase

To ensure the effectiveness of the AWS Incident Management plan, AWS conducts incident response testing, providing excellent coverage for the discovery of defects and failure modes as well as testing the systems for potential customer impact.

The Incident Response Test Plan is executed annually, in conjunction with the Incident Response plan. It includes multiple scenarios, potential vectors of attack, the inclusion of the systems integrator in reporting and coordination and varying reporting/detection avenues.

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

Virtualisation technology used to keep applications and users sharing the same infrastructure apart
Yes
Who implements virtualisation
Supplier
Virtualisation technologies used
Other
Other virtualisation technology used
AWS proprietary
How shared infrastructure is kept separate
Customer environments are logically segregated, preventing users and customers from accessing unassigned resources. Customers maintain full control over their data access. Services which provide virtualized operational environments to customers, ensure that customers are segregated and prevent cross-tenant privilege escalation and information disclosure via hypervisors and instance isolation.

Different instances running on the same physical machine are isolated from each other via the Xen hypervisor. The Amazon EC2 firewall resides within the hypervisor layer, between the physical network interface and the instance's virtual interface. All packets pass through this layer. The physical random-access memory (RAM) is separated using similar mechanisms.

Energy efficiency

Energy-efficient datacentres
Yes
Description of energy efficient datacentres
AWS is committed to running our business in the most environmentally friendly way possible. In addition to the environmental benefits inherently associated with running applications in the cloud, AWS has a long-term commitment to achieve 100% renewable energy usage for our global infrastructure footprint. We’ve made a lot of progress on this commitment. In January 2018, AWS achieved 50% renewable energy usage.

To date, we have announced nine new renewable energy projects (three wind farms and six solar farms), and these projects will deliver a total of 2 million MWh of energy annually onto the electric grid powering AWS data centers located in the AWS US East (Ohio) and AWS US East (N. Virginia) Regions. The electricity produced from these projects is enough to power the equivalent of over 190,000 U.S. homes annually, which is approximately the size of the city of Atlanta, Georgia.
More information is available on the AWS and Sustainability page.

AWS introduced its first carbon-neutral region in 2011. Today, AWS offers customers five AWS Regions that are carbon-neutral:

• US West (Oregon)
• AWS GovCloud (US-West)
• EU (Frankfurt)
• EU (Ireland)
• Canada (Central)

Pricing

Price
£0.007 per instance per day
Discount for educational organisations
No
Free trial available
Yes
Description of free trial
Introductory 12 months free. Conditions apply.

750 hours of Amazon EC2 Linux t2.micro instance usage (1 GiB of memory and 32-bit and 64-bit platform support) – enough hours to run continuously each month*

Service documents

Return to top ↑