Veritas Data Insight Installation Guide
- Understanding the Veritas Data Insight architecture
- About Veritas Data Insight
- About the Management Server
- About the Collector worker node
- About the Indexer worker node
- About the Classification worker node
- About the Self-Service Portal node
- About Communication Service
- About the DataInsightWatchdog service
- About the DataInsightWorkflow service
- About Veritas Data Insight installation tiers
- Preinstallation
- Installing Veritas Data Insight
- About installing Veritas Data Insight
- Federal Information Processing Standards (FIPS)
- Performing a single-tier installation
- Performing a two-tier installation
- Performing a three-tier installation
- Installing the Management Server
- Installing the worker node
- Installing the Classification Server
- Installing the Self-Service Portal
- Installing a Linux Classification Server or Collector worker node
- Installing a Linux Indexer worker node
- Installing Veritas Data Insight in Azure Cloud Environment
- Installing Veritas Data Insight in AWS Cloud Environment
- Upgrading Veritas Data Insight
- Post-installation configuration
- Installing Windows File Server agent
- Getting started with Data Insight
- Uninstalling Veritas Data Insight
- Appendix A. Installing Data Insight using response files
Federal Information Processing Standards (FIPS)
The Federal Information Processing Standards (FIPS) define U.S. and Canadian Government security and interoperability requirements for computer systems. The FIPS 140-2 standard specifies the security requirements for cryptographic modules. It describes the approved security functions for symmetric and asymmetric key encryption, message authentication, and hashing. For more information on the FIPS 140-2 standard and its validation program, see the National Institute of Standards and Technology (NIST) and the Communications Security Establishment Canada (CSEC) Cryptographic Module Validation Program website at: https://csrc.nist.gov/projects/cryptographic-module-validation-program
Where the Data Insight documentation states that a version of Data Insight is "FIPS 140-2-compliant", it means the following:
Data Insight uses FIPS 140-2-validated instances of algorithms and hashing functions in all instances where data is encrypted or hashed.
Data Insight manages cryptographic keys and message authentication in a secure manner, as required of FIPS 140-2-validated cryptographic modules.
To achieve FIPS 140-2 compliance, Data Insight uses a FIPS 140-2-validated cryptographic module to provide the required cryptographic functionality. The Veritas Data Insight Cryptographic Module handles the encryption and decryption of passwords, the hashing of data, and random number generation.
The certificate numbers for the cryptographic modules that are used within the Veritas Data Insight Cryptographic Module are 1012, 1337, and 1894 on the list of validated FIPS 140-2 modules that the NIST publishes. See the following:
https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules/search#1012
http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/ 1401val2010.htm#1337
http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/ 1401val2013.htm#1894
Note the following points if you want to use Data Insight in a FIPS 140-2-compliant environment:
FIPS 140-2-compliant versions of Data Insight store data on your storage devices using FIPS-compliant algorithms. However, you may want to check with the storage provider whether your storage devices are FIPS-compliant.
If you want to run Windows in FIPS 140 compliance mode, you must enable the Windows group policy setting or local policy setting for FIPS-compliant algorithms. This setting restricts the use of non-compliant algorithms in the Microsoft .NET Framework.
See the Microsoft knowledge base article at
http://support.microsoft.com/kb/811833
To use File System Archiving with placeholder shortcuts on an EMC Celerra device, you must configure the Celerra DataMover to use the Secure Sockets Layer (SSL) protocol. Check your Celerra documentation for details of FIPS compliance, if required.
Following modules are not FIPS compliant:
NetApp Manageability SDK used for supporting NetApp devices
Box SDK used for supporting Box cloud sources
Amazon S3 SDK used supported Amazon S3 sources