Azure Migration FAQ
Questions about site migration:
How long will my website be in maintenance mode?
- Your site will mostly likely remain in maintenance mode for one hour. We will be in contact if we expect an extended delay.
Will I have a new URL to access my PrismWeb site?
- No. Your URL for your website will remain the same.
Will I have a new URL to access my Staging site?
- Yes. Your new URL is staging.prismservices.net/sitename. Each site name is unique to your store. If you are unsure about your site name, you can find it in the URL bar of your browser. For example, your current staging URL is staging.thecampushub.com/sitename.
Will I have a new URL to access my PrismWeb Manager site?
- Yes, your new URL will be manager.prismservices.net/sitename. Each site name is unique to your store. If you are unsure about your site name, you can find it in the URL bar of your browser. For example, your current staging URL is manager.thecampushub.com/sitename.
What if the cutover date assigned to me doesn’t work?
- If you have concerns about your assigned date, please submit a ticket through the PrismWeb ticket portal.
After the migration, are there anymore security actions PrismRBS will need to take may affect my site?
- No! Moving forward, only normal security maintenance will be performed.
What actions should customers take prior to moving into the Azure environment?
- Shift4 and Mira Pay customers should adjust firewall settings to expedite the Azure migration process.
- In order to simplify the network configuration and support future growth, we’ve reserved a dedicated block of IP addresses, which you should add to your existing firewall rules. The new PrismWeb IP block is 18.104.22.168/29 (22.214.171.124–126.96.36.199).
- We recognize that firewall changes must be carried out by your IT department, so we strongly encourage you to engage with them as soon as possible. Necessary firewall changes include:
- Add an outbound firewall exception for TCP 80 (HTTP),443 (HTTPS),1443 FileCloud) to the IP range 188.8.131.52/29 (184.108.40.206–220.127.116.11). This should only be additive. Do not remove or replace any existing rules.
What does migrating to the new environment in Azure mean for my site’s security?
- We have been working with SISA throughout the re-architecting process to ensure the new environment conforms to the Microsoft PCI model template. The new environment incorporates all of the controls added in response to the security incidents this year, as well as additional controls.
Questions for Tender Retail customers:
Why can’t Tender Retail be used within the Azure environment?
- Because security is our top priority, we will only be supporting payment gateways that remove or reduce PCI scope for both the web platform and our customers. As a result, the new platform will not support payments from Tender Retail. Shift4 and MiraPay both offer end-to-end point encryption of credit card data through their iFrame solutions.
As a Tender Retail customer, what are my options?
- The best option for Tender Retail users is to transition to the Shift4 payment gateway for PrismWeb as soon as possible. The benefit to your store is that Shift4 offers point-to-point encryption and tokenization of credit card information. P2PE encrypts cardholder data right at the terminal, so sensitive cardholder data never enters the merchant’s environment, and tokenization replaces stored credit card data with random, alphanumeric value that is useless to data thieves.
Is Shift4 available in Canada? I thought it wasn’t.
- Shift4 is available in Canada, however, they currently cannot provide P2PE pin pads that can be used in Canada due to the laws regarding data transfer across border lines.
What are the issues regarding the use of Tender Retail in-store on POS versus for PrismWeb payment processing?
- From an eCommerce perspective, Tender Retail puts our system in PCI scope as it does not offer payment tokenization or an iFrame solution.
What are the implications of using Tender Retail in-store for POS transactions?
- If implemented according to standards, there is minimal risk at the POS/Core side for PCI, because the systems do not touch the credit card information.
How do I initiate the transition process to Shift4?
- To get started with the Shift4 transition, it’s important to contact us as soon as possible at firstname.lastname@example.org.
- We’ve been working diligently with Shift4 to create a seamless transition plan.
- In order to get you set up on Shift4, there are a few things we need from you, including a signed contract addendum and a completed VAR sheet. Please note, you’ll need to engage with your bank in order to obtain the necessary details for the VAR sheet. After you initiate your transition process with us, we encourage you to contact your bank.
- You also need to update to the latest version of PrismCore (18.104.22.168) prior to the transition.