Migrator Pro for Exchange 20.11.1 - Installation and Configuration Guide

Appendix A. STIG Environments

Please note the following considerations for STIG environments.

SQL Express

The SQL Express option should not be chosen when installing Migrator Pro for Exchange. SQL Express does not include the following settings or features needed for STIG environments:

• SQL Server must be monitored to discover unauthorized changes to stored procedures. (SQL Agents is not part of SQL Express) 41403, 41404, 41405

A dedicated SQL Server (full version) should be used.

Additional Information

Microsoft SQL Server 2012 Database Security Technical Implementation Guide (stigviewer.com)

Microsoft SQL Server 2012 Database Instance Security Technical Implementation Guide (stigviewer.com)

MS SQL Server 2016 Instance Security Technical Implementation Guide (stigviewer.com)

MS SQL Server 2016 Database Security Technical Implementation Guide (stigviewer.com)

Appendix B. Deployment in FIPS Environment

Binary Tree Migrator Pro for Exchange 20.11.1 can be successfully deployed in a FIPS environment by following the procedure described in this document.

The audience for this section is technical implementation consultants deploying Migrator Pro for Exchange.

Cryptographic usage

Migrator Pro for Exchange relies on the following Third-Party cryptographic libraries for its cryptographic needs.

Background

To execute in a FIPS compliant mode, a Windows environment requires the Microsoft Policy “System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing” setting enabled.

Microsoft states that “This policy is only advisory to applications. Therefore, if you enable the policy, it does not make sure that all applications will comply”.

Migrator Pro for Exchange leverages Microsoft’s CryptoAPI (CAPI) and CryptoAPI Next Generation (CNG) for its cryptographic needs

Microsoft Product Relationship with CNG and CAPI libraries is documented here: https://technet.microsoft.com/en-us/library/cc750357.aspx

“Rather than validate individual components and products, Microsoft chooses to validate only the underlying cryptographic modules. Subsequently, many Windows components and Microsoft products are built to rely on the Cryptographic API: Next Generation (CNG) and legacy Cryptographic API (CAPI) FIPS 140 validated cryptographic modules. Windows components and Microsoft products use the documented application programming interfaces (APIs) for each of the modules to access various cryptographic services.

Prerequisites

External to Migrator Pro for Exchange, the following server configurations are necessary to set up the environment for FIPS Mode.

1. Windows Server 2012 R2 or later must be installed and up to date.

2. The following group policies must be enabled:

   1. System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.

      1. Ensure this policy is enabled.

   2. Network Security: Configure encryption types allowed for Kerberos.

      1. Ensure the “AES128_HMAC_SHA1” and “AES256_HMAC_SHA1” values are selected.

      2. NOTE: Authentication of target accounts with synchronized passwords requires Kerberos encryption type “RC4_HMAC_MD5” to be allowed for participating devices.

3. Insecure SCHANNEL Server protocols must be disabled.

   1. SSL 2.0, SSL 3.0, TLS 1.0, TLS 1.1

4. SSL certificate for Web Hosting issued by a trusted certificate authority.

5. SQL Server Encrypted Connections must be enabled.

   1. See reference links for configuration details

Installation and operation

For environments with existing Migrator Pro for Exchange installations, the installation must be upgraded to version 20.11 or later. If the existing installation is configured with remote Migrator Pro for Exchange Workers, the remote Workers need to be upgraded to version 20.11 or later.

For new installations, Migrator Pro for Exchange 20.11 enforces all FIPS mode requirements, no additional steps are required.

Website SSL Certificate Installation

1. Ensure the certificate and CA certificate chain has been installed on the server.

2. Open Internet Information Services (IIS) Manager.

3. Expand the Sites node in the Connections pane.

4. Right-click the “Default Web Site” website node and choose “Edit Bindings…”.

   1. If the site has an “https” binding, select it and click “Edit…”

   2. If the site does not have an “https” binding, click “Add…”

      1. From the “Type” drop-down, select “https”.

   3. From the “SSL certificate” drop-down, select the appropriate certificate.

   4. Click OK.

   5. Remove the “http” binding.

5. In the IIS Manager Features View pane, double-click “SSL Settings”.

   1. Check the “Require SSL” checkbox and click “Apply” in the Actions pane.

6. Validate the website can be accessed and the bowers is indicating the certificate is valid and trusted.

References

System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing

Network security: Configure encryption types for Kerberos

Windows Server SCHANNEL Protocol Settings

Internet Information Services (IIS) 7.0 Set Up SSL Certificates

Internet Information Services (IIS) 8.0 Centralized SSL Certificates

Enable encrypted connections - SQL Server | Microsoft Docs

KB3135244 - TLS 1.2 support for Microsoft SQL Server