• Compatible with all current nShield models
• Must be installed onto a host running a supported version of the Linux OS, Windows Server, or Windows OS, and have the nShield Security World software installed
• Supports Operator Card Set & Softcard protected keys
• Compatible with the nShield Container Option Pack, allowing WSOP instantiations to be containerized

• Compatible with nShield Connect XC and nShield 5c HSMs
• Compatible with nShield as a Service for cloud-hosted HSM deployments

• nCOP supports any number of hardserver or application containers, and can work with any number of container hosts (physical or virtualized server instances)
• When used in conjunction with network-attached nShield HSMs, client licenses will be required depending on the scale of deployment. The option pack includes a weighting factor for calculating the number of client licenses required based on the maximum number of running application containers to be deployed. Refer to licensing options table below for guidelines on the number of client licenses required for different sized deployments

• Supported on all current nShield HSM models
• Azure BYOK: Requires nShield Security World Software v12.60 and firmware v12.60 or later
• AWS and Google Compute Engine: Requires nShield Security World software v12.40 or later
• Salesforce: Requires nShield Security World software v12.70 and firmware v12.70 or later

This release has been tested for compatibility on a range of platforms, including:

• Microsoft Windows 11 x64
• Microsoft Windows Server 2022 x64
• Microsoft Windows Server 2022 Core x64
• Red Hat Enterprise Linux 8 x64
• Red Hat Enterprise Linux 9 x64
• Oracle Enterprise Linux 8 x64

From a security perspective, Microsoft SQL Server supports the use of cryptographic keys to protect its databases. These encryption keys can be used to perform two levels of encryption:

• Transparent Data Encryption (TDE): Encrypts entire databases without changing existing queries or applications. When SQL Server loads a TDE-encrypted database into memory from disk storage, it automatically decrypts it. This enables clients to query the database within the server environment without manual decryption. The database is re-encrypted when saved to disk storage. When using TDE, data is unprotected by encryption while in memory, and TDE supports one encryption key per database at a time.
• Cell-Level Encryption (CLE): Requires specifying data and encryption key(s) for encryption. CLE uses one or more keys to encrypt individual cells or columns, enabling fine-grained access policies for sensitive database data. Only specified data is encrypted: other data remains unencrypted. This minimizes exposure in database servers and client applications. CLE can also be applied to tables encrypted with TDE. Note: CLE data is decrypted in memory as needed, and different encryption keys can encrypt separate data within the same table.

• Stand-alone service
• Database failover clusters using either nShield Solo or nShield Connect