Unencrypted Data Check

sp_Develop

Added Unencrypted Data

Check Id: 28

The table column returned for this check might have unencrypted data that you might want to have encrypted for best practices or industry specific compliance. You will need to determine if the data needs to be protected at rest, in transit or both.

With SQL Server you have a couple choices to implement hashing or encryption

• SQL Server Always Encrypt
• SQL Server Transparent Data Encryption (TDE)
• You could develop your own or utilize a development framework pattern to implement a custom one-way hashing, hashing with salting or encryption using AES-128, AES-192, AES-256.

Edited Using Prefix in Index Name

Check Id: [NONE YET]

Removed the table portion in the index naming convention.

Other Changes

• Added Product Version check variables. Useful when used in checking for specific features in different version.
• Change SQL_Latin1_General_CP1_CI_AI to SQL_Latin1_General_CP1_CI_AS
• Ignoring __EFMigrationsHistory tables now

Test Database

• Added table and data for testing Unencrypted Data
• Added table for DevelopCheckToSkip for testing Check Skip feature
• Changed SSN to ColumnName on the dbo.UniqueConstraint table because it is now used in Unencrypted Data check

Development Application Settings

• Modified the Redgate SQL Prompt Team Expanded formatting style to handle control flow better.