Veritas Data Insight Release Notes

In 6.4

The following features, enhancements, or changes are now available in Data Insight 6.4.

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

Data Insight now supports FIPS level 140-2. Administrator can choose to enable FIPS mode during installation or upgrade.

For all CIFS supported devices

Data Insight now supports Kerberos Authentication to Management Server log in and Self Service portal, as a secure method of authentication.

For more information about upgrade implications, refer to Configuring EMC Isilon monitoring in Veritas Data Insight Administrator's guide.

Enhanced framework for better in-context help.

Data Insight is now IPv6 compliant.

New classification policies are introduced in every release expanding the compliance and privacy use-cases to newer markets. This release (4.0.0) brings in following new enhancements, policies, and patterns for automatic content classification for supported workloads.

Exact Data Match (EDM)

Unlike most classification techniques that rely on pattern matching to identify sensitive data, Exact Data Match (EDM) triggers a classification response when the actual data that needs to be protected is detected. By matching on the exact data, this reduces the rate of false positives and allows for much higher levels of accuracy in automatic classification. EDM uses a fingerprint method whereby an extract of a database or table is provided as source file in either CSV or TXT format. The table is ingested, and rules are created that indicate a match when one or more columns of a single row are detected in proximity. EDM is ideal when the identification of discrete customer data, employee data, and any other sensitive data repository maintained within a table is required.

Exact Data Match is useful to detect:

Exact Data Match provides the following benefits:

EDM can be enabled or disabled from YAML.

Following VIC policies have been added:

Transparent Patterns

Transparent patterns are new built-in patterns that provide users visibility into the internal logic of the pattern. With this, users have better control and defensibility over pattern matching criteria .Users can copy the existing transparent patterns and modify them for customer-specific logic. This also allows users to create custom policies using Transparent Patterns and when Veritas updates the underlying transparent patterns, their customized policies will be automatically updated as well. The following transparent patterns are introduced:

Improved Python Source Code Detection

VIC release includes improved logic for detecting small Python source code files.

Data Insight 6.4 uses Azure application with application scope permissions for performing operations like scan, discovery, and so on. With this change, user impersonation is no longer needed.