Type of Work: Applying downloaded Linux and Windows Updates and Security Patches

Location: EPhost Office, San Diego, CA 92123

Purpose: EPhost Web Administrators will be working on the EPhost Network performing Linux and Windows Updates on all Windows servers.

Window Start: 7/16/2017 - 8:00pm PST
Window End: 7/17/2017 - 12:00am PST

Service Impact: This work is expected to take approximately 4 hours and you may experience intermittent access to your website during the maintenance window.

Schedule: The window for Network Maintenance is scheduled to begin at 8:00pm on Sunday, July 16th, 2017, and end at 12:00am on Monday, July 17th, 2017. Should additional time be required, notice will be provided and the work window will be expanded.

Testing & Planning: All testing and planning being conducted during this window is part of a pre-defined checklist designed by the EPhost Web Administrator team.

Regression Planning: The EPhost Web Administrator team will be on-site managing this window. As with any Network Maintenance, while highly unlikely, there is a possibility that something unexpected may occur during the work process. Should any issues arise, all equipment will be placed back into standard operation and the work will be postponed until the issue is resolved.

In order to keep up-to-date with today’s security standards, EPhost will be implementing some changes to ensure the shared hosting and managed dedicated servers are secure. These changes were required by PayPal, and Authorize.Net, as well as industry best-practices. All customers making outbound calls to secure APIs, for payment transactions or other uses, could be affected.

All EPhost shared hosting and managed dedicated servers will have SSL 2.0, SSL 3.0, TLS 1.0 and TLS 1.1 disabled & TLS 1.2 enabled as of June 16th 2017. This affects both inbound and outbound SSL connections. Please ensure your application is compatible with these server changes for TLS 1.2 to connect to your API or payment gateway.

Please Note: In order to ensure secure transactions in the future, all API and payment processors will require TLS 1.2 as of June 2017.

All managed server clients will be contacted individually to find out if they would like us to update their server(s). Or please feel free to contact us.

The following changes will be implemented on all EPhost Infrastructure and Shared Web Servers.

Windows and Linux

1) Disable SSL 2.0, SSL 3.0, TLS 1.0 and TLS 1.1
2) TLS 1.2 enabled

Programming languages will have the following changes made.

1)Coldfusion - Update JDK 8 or higher

2)PHP cURL - http://docs.php.net/manual/en/migration56.openssl.php#migration56.openssl.crypto-method (You will need your developer to assist in updating your website code if you use cURL)

3)ASP.NET - Upgrade to Framework 4.6 (This will require ASP.NET 4.0 extension in control panel, ASP.NET 2.0 will not work)

All these changes will be made on June 16th @ 3PM PST

If you have any questions or concerns or would like a sandbox account to test, please email us at support@ephost.com

Type of Work: Applying downloaded Linux and Windows Updates and Security Patches

Location: EPhost Office, San Diego, CA 92123

Purpose: EPhost Web Administrators will be working on the EPhost Network performing Linux and Windows Updates on all Windows servers.

Window Start: 6/18/2017 - 8:00pm PST
Window End: 6/19/2017 - 12:00am PST

Service Impact: This work is expected to take approximately 4 hours and you may experience intermittent access to your website during the maintenance window.

Schedule: The window for Network Maintenance is scheduled to begin at 8:00pm on Sunday, June 18th, 2017, and end at 12:00am on Monday, June 19th, 2017. Should additional time be required, notice will be provided and the work window will be expanded.

Testing & Planning: All testing and planning being conducted during this window is part of a pre-defined checklist designed by the EPhost Web Administrator team.

Regression Planning: The EPhost Web Administrator team will be on-site managing this window. As with any Network Maintenance, while highly unlikely, there is a possibility that something unexpected may occur during the work process. Should any issues arise, all equipment will be placed back into standard operation and the work will be postponed until the issue is resolved.

Expansion to 2-series Bank Identification Numbers (BINs) for Mastercard

Bank Identification Numbers (BINs), which are the first six-digits of the account number, are fundamental to payments. They identify the issuing institution for the account and ensure that each transaction is routed correctly.

Mastercard® has received an additional range of 2-series numbers to add to the 5-series that we currently provide. The 2-series BINs operate in the same way as the 5-series and we have made changes to our systems to accommodate the new numbers. Readiness for the 2-series across our issuers, merchants and other partners is tracking on target dates listed below. Mastercard customer financial institutions can expect to be issued 2-series BINs starting in 2017.

What merchants need to know

All merchant POS (Point of Sale) terminals and related systems, webpage checkout software and anywhere a Mastercard card number is accepted or housed, must be 2-series ready per timing in the table below. Merchants should work with their acquirer or service provider to evaluate their systems to determine whether updates are needed to accept 2-series BIN payments. Merchants who would like to request 2-series test or production cards can send an email to 2series_test_cards@mastercard.com.
Potential implications for merchants

POS terminals and/or cash register updates
Educating your employees
Reporting, processing and reconciliation
E-commerce/online checkout

Download 2-series BIN impact evaluation checklist for merchants:
https://www.mastercard.us/content/dam/mccom/en-us/documents/merchant-2-series-BIN-impact-checklist-aug-2016.pdf

In order to keep up-to-date with today’s security standards, EPhost will be implementing some changes to ensure the shared hosting and managed dedicated servers are secure. These changes were required by PayPal, and Authorize.Net, as well as industry best-practices. All customers making outbound calls to secure APIs, for payment transactions or other uses, could be affected.

All EPhost shared hosting and managed dedicated servers will have SSL 2.0, SSL 3.0, TLS 1.0 and TLS 1.1 disabled & TLS 1.2 enabled as of June 16th 2017. This affects both inbound and outbound SSL connections. Please ensure your application is compatible with these server changes for TLS 1.2 to connect to your API or payment gateway.

Please Note: In order to ensure secure transactions in the future, all API and payment processors will require TLS 1.2 as of June 2017.

All managed server clients will be contacted individually to find out if they would like us to update their server(s). Or please feel free to contact us.

The following changes will be implemented on all EPhost Infrastructure and Shared Web Servers.

Windows and Linux

1) Disable SSL 2.0, SSL 3.0, TLS 1.0 and TLS 1.1
2) TLS 1.2 enabled

Programming languages will have the following changes made.

1)Coldfusion - Update JDK 8 or higher

2)PHP cURL - http://docs.php.net/manual/en/migration56.openssl.php#migration56.openssl.crypto-method (You will need your developer to assist in updating your website code if you use cURL)

3)ASP.NET - Upgrade to Framework 4.6 (This will require ASP.NET 4.0 extension in control panel, ASP.NET 2.0 will not work)

All these changes will be made on June 16th

If you have any questions or concerns or would like a sandbox account to test, please email us at support@ephost.com

Type of Work: Cloud Network Software Upgrade

Location: EPhost Datacenter, San Diego, CA 92123

Purpose: EPhost Web Administrators will be working on the EPhost Cloud Network performing an upgrade to the EPhost Cloud software.

Window Start: 05/13/17 - 11:00 pm PST
Window End: 05/14/17 - 3:00 am PST

Service Impact: This work is expected to take approximately 1 hour, though we have allocated 4 hours. You may experience intermittent access to the EPhost Cloud Network as the software is updated.

Schedule: The window for Cloud Network Maintenance is scheduled to begin at 11:00 pm PST on Saturday, May 13th, 2017, and end at 3:00 am PST on Sunday, May 14th, 2017. Should additional time be required, notice will be provided and the work window will be expanded.

Testing & Planning: All testing and planning being conducted during this window is part of a pre-defined checklist designed by the EPhost Web Administrator team.

Regression Planning: The EPhost Web Administrator team will be on-site managing this window. As with any Network Maintenance, while highly unlikely, there is a possibility that something unexpected may occur during the work process. Should any issues arise, all equipment will be placed back into standard operation and the work will be postponed until the issue is resolved.