The SQL Server Extensible Key Management enables third-party EKM/HSM vendors to register their modules in SQL Server. When registered, SQL Server users can use the encryption keys stored on EKM modules. This enables SQL Server to access the advanced encryption features these modules support such as bulk encryption and decryption, and key management functions such as key aging and key rotation.
To define the attributes of an external Extensible Key Management provider, which provides cryptographic functionality for SQL Server, use the SQL Server Cryptographic Provider Editor to define a cryptographic provider in a SQL Server 2008, 2012, 2014, or 2016 physical model.
To define a SQL Server cryptographic provider
The SQL Server Cryptographic Provider Editor opens.
Note: Click New on the toolbar to create a new cryptographic provider. Use the Enter filter text box to filter a very large list of cryptographic providers to quickly locate the one that you want to define.
Specifies the name of the cryptographic provider. You can change the name of the cryptographic provider in this field.
Specifies the file type of the file that implements the SQL Server Extensible Key Management interface.
Specifies whether the status of the cryptographic provider is enabled.
Generates SQL during forward engineering. Clear the check box if you do not want to generate SQL.
The cryptographic provider is defined and the SQL Server Cryptographic Provider Editor closes.
Copyright © 2017 erwin Inc.
All rights reserved.
|
|