WAF & Firewall is set up to keep customer data secured and protected from hackers. JetRails handles the setup of Cloudflare at the edge to allow legitimate requests while blocking malicious requests.
Sansec's eComscan security scanner is integrated into the JetRails platform. This tool is used by Adobe and runs 17,000 security tests to help identify potential malware. Features include server-side monitoring, vulnerability tracking and detection, flexible integration and powerful threat intelligence. The research team analyzes over 200 eCommerce hacks per week. This produces a valuable stream of attack vectors and IOCs, which are continuously fed into eComscan. View sample report.
JetRails is also partnered with Sucuri for additional monitoring and staying on top of emerging website security threats. Features include traffic filtering, incident response, SIEM integration and file integrity monitoring.
Magento Configurations / Performance Tuning
In this part of the process, the Onboarding Engineer will fine tune all of the configurations for your specific Magento installation and requirements. Some items include:
Provisioning The New Environment
Single-tenant dedicated server environments typically get provisioned in about a day or two. Multi-server clusters can take several days depending on architecture. Cloud solutions on AWS are more complex and can also take up to a week to prepare. While there is a general playbook for Magento 2 environments, each installation is unique and every environment is prepared for the specific requirements of the installation. For added security and performance, Magento 2 environments are typically Ubuntu/Nginx without cPanel.
Steps that will help make the process as seamless as possible.
Onboarding engineer schedules initial call to review the process, discuss technical aspects of the migration and plan the timeline with all stakeholders. This is a critical activity that involves preparing all of the team members and the client team on expectations, communication, and collaboration for the migration. Here you will iron out details such as responsibilities, timelines & success measurement. Some items that are typically reviewed during this call:
Gathering contact information on everyone involved in the migration
IPs that need to be whitelisted for access
DNS zone file
Current services and versions of: PHP, Redis, Elasticache, RabbitMQ, MySQL, etc.
Specific tools necessary such as Composer
Onboarding Engineers hours of operation - Typically 10am - 6pm CST (Monday through Friday)
Covering any nuances that are specific to your Magento installation
Example timeline for a migration:
Data Request & Sync
To save time while the new environment is being deployed, make sure to white-list your new hosting provider and prepare SSH access to the current environment. Root access is typically preferred but not always necessary. As long as there is a way to obtain a copy of the web files and database, your new hosting provider should be able to take care of the rest. Use secure communication tools such as: https://secret.jetrails.cloud/
Once access is verified and obtained, the onboarding engineer will clone the web files and database and sync them to the new environment. Additional items that may be necessary: copy of SSL certificates, copy of additional framework integrations such as WordPress or any other customizations.
Handoff For Testing
This stage allows developers and merchants to verify functionality prior to scheduling the final sync and flip-over. When migrating to a modern environment, you will likely run into scenarios where adjustments may be necessary. There are also times where your development team may need to adjust the design of the site to be compatible with the new architecture. Having a single person responsible for sign-off on functionality testing will help prevent unexpected behavior upon launch. Once the site is running as expected, a UAT (user acceptance testing) form should be filled out prior to taking next steps.
Configuration Freeze & Scheduling Go-Live
At this point in time, no changes should be made to the configurations or source code to prevent unexpected behavior at go-live. A final sync and cutover is scheduled with the onboarding engineer. Technical contacts from the infrastructure, development and merchant's teams should be present during the cutover.
Post On-boarding Review
After the migration is wrapped up, a call should be scheduled to review mission-critical information to ensure success. Topics include: