The AWS PaaS Service takes responsibility for the Operating System (OS) layer in between the AWS Infrastrucrue and a Service (IaaS) and application technology layers.
Covers production and non-production environments for Windows, RHEL, CentOS, ubuntu, Debian and others.
- Suitable for OFFICIAL (formerly IL2/IL3) and/or SENSITIVE workloads.
- Multiple data centres (AZs), 3 EU regions (including the UK).
- NCSC Cloud Security Principles aligned, Security Cleared (SC) staff available.
- Connectivity options for N3, PSN, Janet, RLi and regional networks.
- Provides support for Windows and Linux operating systems.
- Covers serverless technologies like elastic beanstalk and Lambda.
- Includes PaaS services: Key Management, directory services,
- Integrated role-based access control across all AWS services (IAM).
- Comprehensive, cross service API audit logging and security (CloudTrail).
- Integration with other AWS services (24x7 support and consolidated billing).
- Training and architectural patterns/guidance (well architected).
- Offers significant savings compared to on-premises solutions.
- Obtain and configure additional capacity with minimal disruption.
- Pay only for capacity you actually use.
- Highly reliable environment.
£35 per instance per month
- Free trial available
Moortec Solutions Ltd
|Email or online ticketing support||Email or online ticketing|
|Support response times||Reponse times and the hours of support depends upon the level of support. The gold service level provides 1 hours response 24x365.|
|User can manage status and priority of support tickets||Yes|
|Online ticketing support accessibility||WCAG 2.0 AA or EN 301 549|
|Phone support availability||24 hours, 7 days a week|
|Web chat support||No|
|Onsite support||Yes, at extra cost|
Gold Service 24 x 375 Priority 1 incidents are responded to within 1 hour. Priority 2 within 4 hours. Priority 3 within 24 hours. Priority 4 within 48 hours.
Silver Service Mon-Fri 7am - 9pm Priority 1 incidents are responded to within 4 hours. Priority 2 within 12 hours. Priority 3 within 48 hours. Priority 4 within 5 working days.
Bronze Service Mon-Fri 9am - 5pm Priority 1 incidents are responded to within 8 hours. Priority 2 within 24 hours. Priority 3 within 72 hours. Priority 4 within 7 working days.
The support costs are included in the compute platform costs, and start from £100 per month per instance.
We provide cloud support engineers.
|Support available to third parties||Yes|
Onboarding and offboarding
A range of resources exist to help customers get started with Moortec's PaaS Service. These include: the AWS comprehensive documentation (in multiple formats), access to templates, and face-to-face training.
This can be on how to deploy and use complete Moortec preconfigured AMIs, or self-service access to AWS resources from within Moortec managed accounts and VPCs.
|End-of-contract data extraction||
Customers can choose from one of several mechanisms for extracting the data.
(1) Data may be copied out using secure tools (such as ftps) at any time, subject to security controls.
Following termination or expiry of the relationship:
(2) Moortec will arrange for the Moortec AWS Account(s) containing data (and other AWS resources) to be transferred to either the customer or the customer's nominated representative.
(3) Moortec will transfer the data to alternative AWS storage nominated by the customer, or
(4) Moortec will extract the data onto suitably encrypted portable media and provide that to the customer.
In any event, the 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.
Buyer may terminate the relationship with Moortec for any reason by (i) providing Moortec 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.
Moortec customers retain control and ownership of their data. Moortec will not erase customer data for 30 days following an account termination. This allows customers to retrieve content from Moortec 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||No|
|Command line interface||No|
|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. storage) 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.
|Infrastructure or application metrics||Yes|
|Other metrics||Regular reports on backup operations: success, failure, restores, etc.|
|Supplier type||Not a reseller|
|Staff security clearance||Conforms to BS7858:2012|
|Government security clearance||Up to Developed Vetting (DV)|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing 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||Other|
|Other data at rest protection approach||Moortec relies upon the AWS 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||
|Equipment disposal approach||In-house destruction process|
Backup and recovery
|Backup and recovery||Yes|
|What’s backed up||
The on-boarding process will identify those resources that require backups and Moortec will schedule regular automatic backups of these.
Changes to the schedule or ad hoc backups can be requested by raising a support ticket with the Moortec support portal.
|Scheduling backups||Users contact the support team to schedule backups|
|Backup recovery||Users contact the support team|
|Data protection between buyer and supplier networks||
|Other protection between networks||
Network devices, including firewall and other boundary devices, are in place to monitor and control communications at the external boundary of the network and at key internal boundaries within the network. These boundary devices employ rule sets, access control lists (ACL), and configurations to enforce the flow of information to specific information system services.
ACLs, or traffic flow policies, are established on each managed interface, which manage and enforce the flow of traffic. ACL policies are approved by Amazon Information Security.
|Data protection within supplier network||
|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
Moortec relies upon the AWS SLAs for several services. Due to the rapidly evolving nature of AWS’s product offerings, these SLAs are best reviewed directly on our website via the links below:
• Amazon EC2 SLA: http://aws.amazon.com/ec2-sla/
• Amazon S3 SLA: http://aws.amazon.com/s3-sla
• Amazon CloudFront SLA: http://aws.amazon.com/cloudfront/sla/
• Amazon Route 53 SLA: http://aws.amazon.com/route53/sla/
• Amazon RDS SLA: http://aws.amazon.com/rds-sla/
• AWS Shield Advanced SLA: https://aws.amazon.com/shield/sla/
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.
For IaaS services Moortec will provide access to a customised dashboard with API and events; configurable alerting (email / SMS / messaging) that is based upon the AWS dashboard.
Moortec will report an PaaS service outages via email alerts and/or SMS.
Identity and authentication
|Other user authentication||
Moortec relies upon the AWS controls that controls access via unique user ID/password authentication. No actions are permissible without authentication. Remote access is multi-factor, login attempts are limited, remote administrative access attempts are logged and reviewed by Security. Suspicious activity initiates incident response procedures.
A session lock out policy that is systematically enforced: locks are retained until identification/authentication procedures are concluded.
AWS’s Identity and Access Management (IAM) system controls access to AWS services/resources. IAM facilitates the issuance of access permissions per user/group. MFA is available at no extra cost.
|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 once a year|
|Management access authentication||2-factor authentication|
|Devices users manage the service through||
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||At least 12 months|
|Access to supplier activity audit information||You control when users can access audit information|
|How long supplier audit data is stored for||At least 12 months|
|How long system logs are stored for||At least 12 months|
Standards and certifications
|ISO/IEC 27001 certification||Yes|
|Who accredited the ISO/IEC 27001||EY CertifyPoint|
|ISO/IEC 27001 accreditation date||11/11/2016|
|What the ISO/IEC 27001 doesn’t cover||N/A|
|ISO 28000:2007 certification||No|
|CSA STAR certification||Yes|
|CSA STAR accreditation date||11/11/16|
|CSA STAR certification level||Level 2: CSA STAR Attestation|
|What the CSA STAR doesn’t cover||N/A|
|Who accredited the PCI DSS certification||Coalfire Systems Inc|
|PCI DSS accreditation date||11/7/2016|
|What the PCI DSS doesn’t cover||N/A|
|Other security accreditations||Yes|
|Any other security accreditations||
|Named board-level person responsible for service security||Yes|
|Security governance accreditation||Yes|
|Security governance standards||
|Other security governance standards||Moortec relies upon the AWS ISO/IEC 27001 certificate for the AWS based services.|
|Information security policies and processes||Cyber Essentials Plus; ISO 27017; ISO 27018; SOC 1/2/3|
|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||
IaaS: 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.
PaaS: Moortec performs vulnerability scans on the guest operating systems covered by the service. Identified vulnerabilities are monitored and evaluated. Countermeasures are designed and implemented to neutralise known/newly identified vulnerabilities.
|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 potential compromise incidents, based on AWS Service/Security Team- set thresholds.
Requests to AWS KMS are logged and visible via the 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 after turning on AWS CloudTrail.
|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.
|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||Third-party|
|Third-party virtualisation provider||Amazon AWS|
|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.|
|Price||£35 per instance per month|
|Discount for educational organisations||No|
|Free trial available||Yes|
|Description of free trial||
Introductory 12 months free. Conditions apply.
e.g. 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
|Pricing document||View uploaded document|
|Skills Framework for the Information Age rate card||View uploaded document|
|Terms and conditions document||View uploaded document|