EPAM Systems Ltd.

Cloud Hosting

Digital Transformation, Microsoft Azure, Google GCP, Amazon Artificial Intelligence, Amazon Big Data, Cloud Tooling, Amazon DevSecOPs , Amazon Cloud Security, Microsoft Azure Big Data, Amazon Lambda, Amazon Aurora, Amazon OpsWorks, Amazon IoT core, Amazon IOT Analytics, AWS IOT Device Management, Amazon Kinesis Data Analytics Amazon SageMaker Ground Truth

Features

  • Suits OFFICIAL
  • Available in the London Region
  • NCSC Cloud Security Principles aligned Security Cleared
  • Connectivity options N3, HSCN, PSN, Police , Janet
  • Natural language chatbots AI Powered Speech Analytics
  • Deploy into automated Infrastructure/Platform as a Service architecture
  • No code necessary to store data to common destinations
  • Automated Data Labeling - Amazon SageMaker Ground Truth
  • Data querying, filtering and search in apps

Benefits

  • Easily manage applications at scale
  • Track real-time usage of applications
  • Perform complex queries and aggregation across your on-premise
  • Pay for use with no minimum fees or usage.
  • DDOS protection at the Edge with AWS Shield
  • Rapid development of applications using SQL
  • Ability to leverage existing open source tooling via Apache Flink
  • Rapidly create data processing pipeline with little to no coding
  • Highly scalable fully managed service allowing simple scaling
  • Integration with other Amazon services 24x7 support

Pricing

£1,000 to £2,000 a person a day

  • Education pricing available

Service documents

Request an accessible format
If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at kiran_choubina@epam.com. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 12

Service ID

6 2 8 5 8 8 2 3 1 5 4 2 2 1 6

Contact

EPAM Systems Ltd. Kiran Choubina
Telephone: 07980893148
Email: kiran_choubina@epam.com

Service scope

Service constraints
Records are limited to 1000kB, Amazon Kinesis Data Analytics, Amazon IOT is currently only available in the Ireland and Frankfurt Regions (EU), and 10 non-eu regions internationally
System requirements
  • N/A
  • Terms and Conditions of all major Cloud Providers apply.

User support

Email or online ticketing support
Yes, at extra cost
Support response times
Enterprise- General guidance cases < 24 hours; system impaired cases < 12 hours; production system impaired cases < 4 hours; production system down cases < 1 hour; business-critical system down cases < 15 minutes
Developer:
General guidance cases < 24 business hours; system impaired cases < 12 business hours.

Business:
General guidance cases < 24 hours; system impaired cases < 12 hours; production system impaired cases < 4 hours; production system down cases
< 1 hour.
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
24 hours, 7 days a week
Web chat support
Web chat
Web chat support availability
24 hours, 7 days a week
Web chat support accessibility standard
None or don’t know
How the web chat support is accessible
You can sign in to the Support Center at https://console.aws.amazon.com/support/home#/ by using the email address and password associated with your Amazon account. To log in with other credentials, see Accessing AWS Support.
Web chat accessibility testing
Unable to provide a response at this time.
Onsite support
Yes, at extra cost
Support levels
Basic
24/7 customer service, support forums, 4 Core “Trusted Adviser” checks, personal health dashboard. No TAM. Free

Developer:
As above + business hours access to technical/architural Cloud Support Associates via email (one primary contact). No TAM. 3%x monthly AWS usage.

Business:
As above + 24/7 access to Cloud Support Engineers via email, chat and phone for unlimited contacts; architecture, 3rd party software and programmatic case management support. TAM. Greater of $100 or spend-dependent percentage (pm).

Enterprise
As above, plus architectural review, operations support, training, assigned concierge, proactive guidance, TAM. Greater of $15,000 or spend-dependent percentage (pm).
Support available to third parties
Yes

Onboarding and offboarding

Getting started
Amazon provides a range of resources to help customers get started on our services. These include: comprehensive documentation (in multiple formats), introductory videos, hands-on labs, online and in-person training, access to a large ecosystem of partners and support from the public sector account team.
Service documentation
Yes
Documentation formats
  • HTML
  • ODF
  • PDF
End-of-contract data extraction
EPAM End-of-contract data extraction procedures are available on request.
Data may be copied out using OS-level tools (such as xopy or rsync). Data may be copied out using AWS API tools to download data.
EPAM will follow the guidelines stated on clauses (7.5,7.6 & 7.7) of the g-cloud 11- proposed framework agreement and the exit plan on g-cloud proposed call -off agreement. Any service that would lie outside the g-cloud 11 framework and the call-off agreement would be treated as a chargeable activity.
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 11 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.
Any service that would lie outside the g-cloud 11 framework and the call-off agreement would be treated as a chargeable activity.

Using the service

Web browser interface
Yes
Using the web interface
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.
Web interface accessibility standard
None or don’t know
How the web interface is accessible
You can sign in to the Support Center at https://console.aws.amazon.com/support/home#/ by using the email address and password associated with your AWS account. To log in with other credentials, see Accessing AWS Support.
Web interface accessibility testing
None
API
Yes
What users can and can't do using the API
All functionality is exposed via an API.
API automation tools
  • Ansible
  • Chef
  • OpenStack
  • SaltStack
  • Terraform
  • Puppet
  • Other
Other API automation tools
  • Kubernetes
  • Docker
  • OpenShift
  • Azure Resource Management
  • Amazon API
  • Offer SDKs for Python, Ruby, PHP, JavaScript, Java, .NET, Node.js.
  • Cloud Foundry
API documentation
Yes
API documentation formats
  • Open API (also known as Swagger)
  • HTML
  • ODF
  • PDF
  • Other
Command line interface
Yes
Command line interface compatibility
  • Linux or Unix
  • Windows
  • MacOS
  • Other
Using the command line interface
All functionality is available via the CLI.
users can set up the service through the command line interface
users can make changes to the service through the command line interface
no known limitations

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
  • Memory
  • Network
  • Number of active instances
Reporting types
  • API access
  • Real-time dashboards
  • 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 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
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
In-house
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
Amazon 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
Files, virtual machines, databases, code, machine image
Backup controls
Users are able to specify their backup requirements, retention periods and archiving. Manual or scheduled API call
Datacentre setup
Multiple datacentres with disaster recovery
Scheduling backups
Users contact the support team to schedule backups
Backup recovery
  • Users can recover backups themselves, for example through a web interface
  • Users contact the support team

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
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
Dashboards, API's, Email & Text Alerts.
Outage Reporting part of our service, we align with the NCSC 14 Cloud principles.

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)
  • Limited access network (for example PSN)
  • Dedicated link (for example VPN)
  • Username or password
Access restrictions in management interfaces and support channels
Access restrictions in management interfaces and support channels are in place and are strictly enforced n order to maintain a secure service, users need to be properly authenticated before being allowed to perform management activities, report faults or request changes to the service.
EPAM ensures that all management requests which could have a security impact are performed over secure and authenticated channels. Strong authentication is in place which is regularly exercised, audited and reviewed at least once a year. Only authorised individuals from within the organisation can use those mechanisms to affect your use of the service.
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)
  • Limited access network (for example PSN)
  • Dedicated link (for example VPN)
  • Username or password
Devices users manage the service through
  • Dedicated device on a segregated network (providers own provision)
  • Dedicated device on a government network (for example PSN)
  • 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

Access to user activity audit information
Users receive audit information on a regular basis
How long user audit data is stored for
At least 12 months
Access to supplier activity audit information
Users receive audit information on a regular basis
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
DNV-GL, Palace House, 3 Catherdral Street, London, SE1 9DE
ISO/IEC 27001 accreditation date
31/05/2017
What the ISO/IEC 27001 doesn’t cover
Unknown.
ISO 28000:2007 certification
Yes
Who accredited the ISO 28000:2007
DNV-GL, Palace House, 3 Cathedral Street, London, SE1 9DE
ISO 28000:2007 accreditation date
31/05/2017
What the ISO 28000:2007 doesn’t cover
Unknown.
CSA STAR certification
No
PCI certification
Yes
Who accredited the PCI DSS certification
DNV-GL, Palace House, 3 Cathedral Street, London, SE1 9DE
PCI DSS accreditation date
31/05/2017
What the PCI DSS doesn’t cover
Unknown.
Other security certifications
No

Security governance

Named board-level person responsible for service security
Yes
Security governance certified
Yes
Security governance standards
  • CSA CCM version 3.0
  • ISO/IEC 27001
Information security policies and processes
EPAM is dedicated to protecting all managed information assets by using its ISAE 3402 and ISO 27001:2013 compliant Information Security Management System.
The EPAM Systems has developed Information Security Policy to ensure the following:
• Information and information systems are available to meet the business requirements of EPAM Systems.
• Valuable or sensitive information is protected from unauthorized access, disclosure or interception.
• The accuracy and completeness of information is protected from unauthorized or failed modification.
• Information security is designed and implemented within the development lifecycle of information systems.
• All regulatory, legislative and contractual security obligations are fulfilled.
• The establishment and maintenance of the Information Security Management System is in line with the strategic risk management directives of EPAM Systems.
• Business Continuity Plans are produced, maintained and tested to ensure vital information and services are available when needed.
• Appropriate Information Security and Data Privacy awareness education and coaching are provided to all staff members to maintain security awareness throughout.

The EPAM Systems Information Security Policy directly affects current working practices and supporting infrastructures, and it is formally reviewed on an annual basis.

Yuri Goliyad, Global Head of Operations / Data Privacy Officer

Operational security

Configuration and change management standard
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Configuration and change management approach
Change management is to create an environment where changes can be made with the least amount of risk and impact to the organization. To deliver reliable and effective services, organizations need to ensure that change is planned and purposeful, and that they follow change management processes that balance the need for prompt action with the need for reliable services that are in compliance with policies and regulations. Change management is all about making the right decisions about a change, based on a clear understanding of the proposed change and its costs and risks
Vulnerability management type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Vulnerability management approach
EPAM follow Continuous Vulnerability Management (CVM).
The main objective of Continuous Vulnerability Management (CVM) is to detect and remediate vulnerabilities in a manner close to real time.
CVM should equip IT Security, IT and Asset Owners with real time alerts and recommended remediation solutions.
Continuous Vulnerability Management consists of deployed solutions to monitor the critical assets in real time and periodic scans either internally or externally.
Every endpoint, within the EPAM network is equipped with a Qualys agent to optimize network load and communicate with cloud services everywhere anytime.
Protective monitoring type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Protective monitoring approach
Primary competency for the monitoring is within Application and Infrastructure Management Competency Center (AIM CC). Webinars , presentation materials and use cases are available, please feel free to request OrgCompetencyAIMPresales@epam.com.
On a high level there are 3 types of tools:
APM/Classical monitoring Solutions;
Operational intelligence solutions – aka Log aggregators with BI capabilities;
Synthetic transactions monitoring tools.
These 3 types of tools are used for different purposes and usually in combination with each other , feel free to contact AIM CC for more details.
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
EPAM has adopted the ITIL® best practices framework for IT Service Management to improve service delivery and in turn improve customer satisfaction.
Working together, the processes and functions defined within ITIL focus on the entire lifecycle of a service, including Service Strategy, Service Design, Service Transition, Service Operation, and Continual Service Improvement.
These processes are designed to:
Ensure that IT Services are aligned to the needs of customers.
Improve availability and stability of services.
Improve communication within IT and with customers.
Set appropriate expectations for IT services.
Improve efficiency of internal processes.

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
EPAM’s commitment to sustainability has generated dozens of discrete green initiatives including many that stress direct energy-saving and carbon-footprint reduction practices. EPAM Carbon Footprint Calculator tool was developed to calculate and guide us to reduce our own foot print. EPAM Partnered with Carbon Footprint UK in an effort continue promoting the energy management system to improve the overall energy-using efficiency across all our sites. Carbon Footprint UK Ltd carried out a Carbon Footprint assessment on 4 of EPAM sites in Minsk, Kyiv, Moscow, and Budapest. We have been given a recommendations based on our findings on the steps we need to undertake to reduce our Footprint and how we can also offset our carbon footprint in each of these sites. We aware of and align with the EU code of conduct for energy-efficient datacentres.

Pricing

Price
£1,000 to £2,000 a person a day
Discount for educational organisations
Yes
Free trial available
No

Service documents

Request an accessible format
If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at kiran_choubina@epam.com. Tell them what format you need. It will help if you say what assistive technology you use.