Updated Go live checklist topic in Cloud Guide (#6083)

- Updated prelaunch checklist with updated version in PDF format
- Added security configuration section to Go Live Checklist topic
- Updated links in the Product configuration section

Author: meker12

common/pdf/Pre-Launch.Checklist_4_23_2018.docx

@@ -6,7 +6,7 @@ functional_areas:
   - Testing
 ---
 
-Before you deploy to the Production environment, download the [Go live checklist]({{ site.baseurl }}/common/pdf/Pre-Launch.Checklist_4_23_2018.docx) and use it with these instructions to confirm that you have completed all required configuration and testing. See an overview of the complete deployment process for Starter and Pro at [Deploy your store]({{ page.baseurl }}/cloud/live/stage-prod-live.html).
+Before you deploy to the Production environment, download the [Go live checklist]({{ site.baseurl }}/common/pdf/magento-commerce-cloud-prelaunch-checklist.pdf), and use it with these instructions to confirm that you have completed all required configuration and testing. See an overview of the complete deployment process for Starter and Pro at [Deploy your store]({{ page.baseurl }}/cloud/live/stage-prod-live.html).
 
 ## Completely test in Production {#test}
 
@@ -16,9 +16,9 @@ See [Test deployment]({{ page.baseurl }}/cloud/live/stage-prod-test.html) for te
 
 You need to complete configurations for your DNS including:
 
-*  Set all necessary redirects, especially if you are migrating from an existing site
-*  Set the zone’s root resource record to address the hostname
-*  Lower the value for the Time-to-Live (TTL) to refresh DNS information to correctly point customers faster to the Production store
+-  Set all necessary redirects, especially if you are migrating from an existing site
+-  Set the zone root resource record to the hostname address
+-  Lower the value for the Time-to-Live (TTL) setting to refresh DNS information so customers are directed to the correct Production store more quickly
 
 We recommend a significantly lower TTL value when switching the DNS record. This value tells the DNS how long to cache the DNS record. When shortened, it refreshes the DNS faster. For example, changing this value from 3 days to 10 minutes. Be advised, this adds load to the web server.
 
@@ -29,20 +29,20 @@ This does not work for an [apex domain](https://blog.cloudflare.com/zone-apex-na
 
 The following list contains examples of DNS providers for informational purposes. Use your preferred DNS provider.
 
-*  CNAME with ALIAS record from [Dyn](http://dyn.com)
-*  ANAME record on [DNS Made Easy](http://www.dnsmadeeasy.com)
-*  ANAME at [easyDNS](https://www.easydns.com)
-*  ACNAME at [CloudFlare](https://www.cloudflare.com)
-*  ALIAS at [PointDNS](https://pointhq.com)
+-  CNAME with ALIAS record from [Dyn](http://dyn.com)
+-  ANAME record on [DNS Made Easy](http://www.dnsmadeeasy.com)
+-  ANAME at [easyDNS](https://www.easydns.com)
+-  ACNAME at [CloudFlare](https://www.cloudflare.com)
+-  ALIAS at [PointDNS](https://pointhq.com)
 
 Many other DNS providers also offer workarounds to accomplish this goal. The most common is to add a CNAME record for the `www` host on the domain and then use the DNS provider's redirect service to redirect the apex over to the `www` version of the domain. Consult your DNS provider for more information.
 
 Another option for apex domain is to add A records, which maps a domain name to the Fastly IP addresses:
 
-*  `151.101.1.124`
-*  `151.101.65.124`
-*  `151.101.129.124`
-*  `151.101.193.124`
+-  `151.101.1.124`
+-  `151.101.65.124`
+-  `151.101.129.124`
+-  `151.101.193.124`
 
 ### TLS and Fastly {#fastly-tls}
 
@@ -56,34 +56,36 @@ Make a final pass for any Production configurations in the store(s). If you need
 
 The following are recommended changes and checks:
 
-*  Outgoing email has been tested
-*  Base URL and Base Admin URL are set correctly
-*  Change the default Magento Admin password
-
-   See [Configuring Admin Security](http://docs.magento.com/m2/ee/user_guide/stores/security-admin.html) for further information on Admin configurations.
-
-*  Optimize all images for the web
-*  [Enable minification](http://docs.magento.com/m2/ee/user_guide/system/file-optimization.html) for JS, CSS, and HTTP
+-  [Completed Outgoing email testing]({{ page.baseurl }}/cloud/project/sendgrid.html)
+-  [Secure configuration for Admin credentials and Base Admin URL](http://docs.magento.com/m2/ee/user_guide/stores/security-admin.html)
+-  [Optimize all images for the web]({{ page.baseurl }}/cloud/cdn/fastly-image-optimization.html)
+-  [Check minification settings for HTML, Javascript, and CSS]({{ page.baseurl }}/cloud/deploy/static-content-deployment.html)
 
 ## Verify Fastly caching {#verifyfastly}
 
-Test and verify Fastly caching is correctly working in Production. For detailed tests and checks, see [Fastly testing]({{ page.baseurl }}/cloud/live/stage-prod-test.html#fastly).
-
-*  Make sure that pages are being correctly cached in the page cache and Fastly
-*  Make sure the Fastly Extension is up-to-date
-*  Make sure the Fastly VCL is up-to-date
+-  Test and verify that Fastly caching is working correctly on the Production site. For detailed tests and checks, see [Fastly testing]({{ page.baseurl }}/cloud/live/stage-prod-test.html#fastly).
+-  [Ensure that the latest version of the Fastly CDN Module for Magento 2 is installed in your Production environment]({{ page.baseurl }}/cloud/cdn/configure-fastly.html#upgrade)
+-  [Ensure that the most current version of the Fastly VCL code has been uploaded]({{ page.baseurl }}/cloud/cdn/configure-fastly.html#upload-vcl-snippets)
 
 ## Performance testing {#performance}
 
 We recommend that you review the [Magento Performance Toolkit]({{ site.mage2bloburl }}/{{ page.guide_version }}/setup/performance-toolkit) options as part of your pre-launch readiness process.
 
 You can also test using the following 3rd party options:
 
-*  [Siege](https://www.joedog.org/siege-home/): Traffic shaping and testing software to push your store to the limit. Hit your site with a configurable number of simulated clients. Siege supports basic authentication, cookies, HTTP, HTTPS and FTP protocols.
-*  [Jmeter](http://jmeter.apache.org/): Excellent load testing to help gauge performance for spiked traffic, like for flash sales. Create custom tests to run against your site.
-*  [New Relic](https://support.newrelic.com/) (provided): Helps locate processes and areas of the site causing slow performance with tracked time spent per action like transmitting data, queries, Redis, and so on.
-*  [Blackfire]({{ page.baseurl }}/cloud/project/project-integrate-blackfire.html) (provided): Helps track through the issues New Relic finds and helps you dig deeper into the issue for specifics. Blackfire profiles the environment and helps locate bottlenecks in depth: process, method call, query, load, and so on.
-*  [WebPageTest](https://www.webpagetest.org/) and [Pingdom](https://www.pingdom.com/): Real-time analysis of your site pages load time with different origin locations. Pingdom may cost a fee. WebPageTest is a free tool.
+-  [Siege](https://www.joedog.org/siege-home/): Traffic shaping and testing software to push your store to the limit. Hit your site with a configurable number of simulated clients. Siege supports basic authentication, cookies, HTTP, HTTPS and FTP protocols.
+-  [Jmeter](http://jmeter.apache.org/): Excellent load testing to help gauge performance for spiked traffic, like for flash sales. Create custom tests to run against your site.
+-  [New Relic](https://support.newrelic.com/) (provided): Helps locate processes and areas of the site causing slow performance with tracked time spent per action like transmitting data, queries, Redis, and so on.
+-  [Blackfire]({{ page.baseurl }}/cloud/project/project-integrate-blackfire.html) (provided): Helps track through the issues New Relic finds and helps you dig deeper into the issue for specifics. Blackfire profiles the environment and helps locate bottlenecks in depth: process, method call, query, load, and so on.
+-  [WebPageTest](https://www.webpagetest.org/) and [Pingdom](https://www.pingdom.com/): Real-time analysis of your site pages load time with different origin locations. Pingdom may cost a fee. WebPageTest is a free tool.
+
+## Security configuration
+
+-  [Set up your Magento Security Scan]({{ page.baseurl }}/cloud/live/live.html#security-scan)
+-  [Secure configuration for Admin user](http://docs.magento.com/m2/ee/user_guide/stores/security-admin.html)
+-  [Secure configuration for Base Admin URL](https://docs.magento.com/m2/ee/user_guide/stores/store-urls-custom-admin.html)
+-  [Remove any users no longer on the {{ site.data.var.ece}} project]({{ page.baseurl}}/cloud/project/user-admin.html)
+-  [Configure two-factor authentication]({{ page.baseurl }}/security/two-factor-authentication.html)
 
 ## Performance monitoring