Procedures

Install and configure the HSM hardware and software as described in Install the software and create or share the Security World.

Install Microsoft Active Directory Certificate Services as described in Install and configure AD CS with Windows Server Enterprise, with the following settings:

Install and configure the HSM hardware and software as described in Install the software and create or share the Security World.

Install Microsoft Active Directory Certificate Services as described in Install and configure AD CS with Windows Server Enterprise.

In the Private Key window, select Use existing private key, then Select an existing private key on this computer. Select Next.

In the Select Existing Key window, select Change.

In the Change Cryptographic Provider window, select the CSP that contains the created key. Delete the contents of the CA common name field, then select Search. The search finds the existing private key. Select the key, then select Allow administrator interaction when the private key is accessed by the CA. Select Next.

In the Cryptography for CA window, select the appropriate hash algorithm. Select Next.

In the CA Name window, select Next.

In the Validity Period window, specify the validity period. Select Next.

In the CA Database window, specify the certificate database locations and certificate database log locations. Select Next.

In the Confirmation window, select Configure.

Wait for the configuration to complete. After successful completion, close the AD CS configuration window.

Verify that the CA service has successfully started by running the command:

> sc query certsvc

Verify the CA key by running the command:

> certutil -verifykeys

If it is not already on your system installation, create the %SystemRoot%\capolicy.inf file, where %SystemRoot% is the system environment variable for the Windows installation folder, by default C:\WINDOWS\capolicy.inf with the following content:

[Version]
Signature="$Windows NT$"
[certsrv_server]
EnableKeyCounting=True

Install the CA using the HSM KSP.

Enable auditing for the CA service by running the command:

> certutil -setreg ca\auditfilter 1

Stop the certsvc service. Run:

> net stop certsvc

Select Start > Administrative Tools > Certification Authority, right-click the CA, then select Properties.

Select the Auditing tab and check the box for Start and Stop Active Directory Certificate Services.

Select Start > Administrative Tools > Local Security Policy.

Select Local Policy, expand it, then select Audit Policy.

In the right pane, double-click Audit Object Access, then select Success and Failure.

Select Apply, select OK, then close the window.

Update the local security policies by opening a command prompt and running the command:

> gpupdate.exe /force

Restart the CA service to pick up the changes, by running the commands:

> net start certsvc

Run Eventvwr.exe.

Select Windows Logs > Security.

Filter for event ID 4881 (CA startup event) or event ID 4880.

Verify the CA startup event shows the PrivateKeyUsageCount property with a corresponding value.

Sign in to the machine where the CA is installed, with an account that has Domain Admin level privileges.

Run certtmpl.msc from a command prompt, or via the Run command.

Right-click the OCSP Response Signing Template and select Duplicate Template.

Change the Compatibility Settings to the following:

Select OK.

Select General > Template Display Name and enter a name for the new OCSP Response Signing template.

Select Request handling > Authorize additional service accounts to access the private key.

Select Key Permissions.

In the Permissions window, select Add, then select Object Types.

Select the Service Accounts option, then select OK.

In Enter the object names to select, enter Network Service, select Check Names, then select OK.

The default validity period and renewal period for an OCSP Signing certificate are 2 weeks and 2 days respectively. If the private key(s) of the OCSP Signing key pair(s) are to be protected by an HSM, then the validity period of the certificate can be extended because of the improved security protection afforded by the private key(s).

Select Cryptography > Provider Category, then select the provider from the list.

Select the cryptographic algorithm name from the list, then specify the minimum key size.

Select Requests must use one of the following providers. This will enable the selection of the cryptographic providers populated in the list. Select the nShield CSP or KSP as available.

Modify the request hash to the required hash algorithm.

If the environment in which the certificate will be used contains either Windows XP or Windows Server 2003 machines, do not select Use alternate signature format.

Select Security > Add, then select Object Types.

Select Computers, then select OK.

In Select Users, enter the name of a server that will act as an OCSP Responder, then select Check Names. If the name of the server is found, it will appear underlined in the box. Then select OK.

Select the server name and in Permissions, ensure that Read & Enroll permissions are selected.

Configure permissions for all servers that will use this template.

To add all servers at once, separate the names with a semi-colon (;), then select Check Names. If the entries are correct, all server names will be underlined. Then the permissions for each server can be set to have Read & Enroll.

Select OK. This will create the new OCSP Signing Template ready for use.

On the CA that will be making use of the OCSP Responder, enable the new template for issuance.

Ensure that the installer is 12.40.02 or later.

Do not permit the AutoRun to start the installation process. If it does, cancel or quit the installation immediately.

Open a File Explorer window and browse to the CD root directory.

Right-click Setup.exe and select Run as Administrator.

Depending on the configuration, your local administrator credentials may be requested to execute this step.

From the list of components to install, select:

Then select Next on each of the dialogs which appear. The software is installed, then confirmation dialogs appear. Accept all the default parameters for these. The installer will then quit.

Add the %nfast_home%\bin directory to the system PATH environment variable. This should be done via the Advanced System Settings and Environment Variables options from the System link on the Start menu.

This allows the Security World binaries to be accessible system wide without having to specify the %nfast_home%\bin directory every time.

Determine which location the network connection has been configured with. Public is the default unless specified otherwise.

Right-click the Windows icon on the task bar and select Control Panel.

Select System and Security and then Allow an app through Windows Firewall.

Select Change Settings and then Allow another app.

Select Browse, navigate to hardserver.exe, select Open, then select Add. Location:

On the OCSP Server, enroll the client with the HSM:

> nethsmenroll --force --verify-nethsm-details <IP_address_of_HSM>

Manually copy the World file and the module file from C:\ProgramData\nCipher\Key Management Data\local on the RFS to the same location on the OCSP Responder node.

Sign in to the OCSP Responder as the local administrator or using a Domain account with local administrator privileges.

Security World software and wizards must be run using the true local administrator account in order for all file permissions to be written correctly.

Select the Windows icon on the taskbar, select the down arrow, then select nCipher > CNG Configuration Wizard.

If a User Account Control (UAC) dialog appears, select Yes.

In the wizard, select Next. Ensure Use the existing security world is selected, then select Next.

In Set Module States, ensure that Mode is set to operational and that State is usable. Select Next.

If the mode is not operational, that is, it states pre-initialization, ensure that the Security World is loaded into the module.

In Key Protection Setup, ensure that Operator Card Set protection is selected if you are using OCS protection. Do not select Always use the wizard when creating or importing keys. Do not create a new Operator Card Set. Select Next.

If you are not using an OCS, select Module Protection. Module protection should be used for the OCSP Responder to ensure that certificate auto-enrolment completes without needing administrator interaction.

To install the Key Service Provider (KSP), in Software Installation, select Next, then select Finish.

To check whether the nShield KSP is properly installed, run the following command at a command prompt:

> certutil -csplist

Provider Name: nCipher Security World Key Storage Provider

On the OCSP Responder server, in Server Manager, select Add Roles and Features.

On the Before You Begin screen, select Next.

On the Select Installation Type screen, select Next.

On the Select Destination Server screen, select Next.

On the Select Server Roles screen, select Active Directory Certificate Services.

In the Add Roles and Features Wizard dialog that appears, select Add Features.

On the Server Roles screen, select Next.

On the Select Features page, select Next.

On the Active Directory Certificate Services screen, select Next.

Clear Certification Authority, select Online Responder instead, then select Next.

If the Add Roles and Features wizard appears, select Add Features.

On the Role Services screen, select Next.

Confirm the chosen installation options by selecting Install.

On the Installation Results screen, select Close.

Ensure that all the chosen configuration options successfully installed. Investigate any errors before proceeding.

From the notifications section in Server Manager Dashboard, select Post-Deployment Configuration.

In the resulting window, select Next and then select Configure.

Check that the output shows that the Online Responder role has been successfully configured.

From the Administrative Tools folder, open Online Responder Management.

On the left hand side, select Revocation Configuration.

In the Actions pane, select Add Revocation Configuration.

On the Getting started screen, select Next.

On the Name the Revocation Configuration page, type a friendly name for the configuration and then select Next.

The selected name should represent the CA that the Responder configuration is being created for. This name is only used to identify the configuration to administrators.

Select Select CA Certificate Location > Select a certificate for an existing Enterprise CA, then select Next.

Select Choose CA Certificate screen > Browse CA certificates published in Active Directory, then select Browse.

In Select Certification Authority, select the CA that the Responder configuration is created for, select OK, then select Next.

In Select Signing Certificate, ensure that Automatically select a signing certificate and Auto-enrol for an OCSP Signing certificate are selected. Also ensure that the OCSPResponseSigning template is selected, then select Next.

On the Revocation Provider screen, select Provider.

In the Base CRLs section of the resulting dialog box, select the URL, then select OK.

The OCSP Responder uses the CRL generated by the selected CA it is being configured for to obtain its information about the status of certificates issued by the CA.

Ensure the URL includes the correct encoding, with %20 for space characters.

Clear Refresh CRLs based on their validity periods box. Enter the required value for Update CRLs at this refresh interval (min).

Back on the Revocation Provider screen, select Finish.

Ensure that the configuration of the OCSP Responder completes successfully. Investigate any issues before proceeding.

Right click the newly created Revocation Configuration and select Edit Properties.

Select the Signing tab.

Change the Hash algorithm to at least SHA256. This is mandatory if using FIPS 140-2 Level 3 because the default SHA1 option is not supported.

Select OK.

Right-click the server FQDN under the Array Configuration option, then select Set as Array Controller.

After the OCSP Responder has been configured and the key pair generated successfully on the HSM, the following command should be run to commit local Security World data, such as application key tokens, to the RFS:

> rfs-sync --commit

In the Certification Authority MMC, right-click the CA and select Properties.

Select Extensions > Select Extension > Authority Information Access (AIA), then select Add, and enter the name of the OCSP URL:

http://<FQDN-of-OCSP-server>/ocsp.

Select OK.

Select Include in the online certificate status protocol (OCSP) extension, then select OK.

A window prompts you to restart the CA. Select Yes and wait for the CA to restart.

Open Notepad and create a file called rsa.inf with contents similar to the following on your local C drive:

[Version]
Signature = "$Windows NT$"
[NewRequest]
Subject = "C=GB,CN=rsa.inf"
KeyAlgorithm = RSA
KeyLength = 2048
ProviderName = "nCipher Security World Key Storage Provider"
KeyUsage = 0xf0
MachineKeySet = True
RequestType = PKCS10
[EnhancedKeyUsageExtension]
OID = 1.3.6.1.5.5.7.3.1
[Extensions]
1.3.6.1.5.5.7.48.1.5 = Empty

From the command prompt navigate to your local C drive and run the following command:

> certreq -new rsa.inf rsa.req

Check that rsa.req is listed in the directory.

In the command line run the command:

> certreq -submit -attrib -CertificateTemplate:WebServer rsa.req

Select the CA certificate from the Certification Authority list window that appears and save it as rsa.cer in your local directory.

Navigate to the directory where you saved the certificate and look for rsa.cer.

Run the following command:

> certutil -verify -urlfetch rsa.cer

Leaf certificate revocation check passed
CertUtil: -verify command completed successfully.

Select Start > Run, enter certsrv.msc, then select OK.

Windows Server Enterprise:

Windows Server Core:

Right-click the Revoked Certificates folder, then select All Tasks, Publish.

Select OK to select a New CRL.

Right-click the CA, then select Properties.

Select the Extensions tab.

Check that the Select extension drop-down list box shows CRL Distribution Point (CDP).

Select any of the listed CRL distribution points, then select Remove, then Yes.

Select Apply.

Select Yes to restart the service, then select OK to close the dialog.

To check that clients can still obtain revocation data in the command prompt, navigate to the folder where the certificate is stored, then type:

> certutil -url rsa.cer

Select Certs (from AIA), then select Retrieve.

Select CRLs (from CDP), then select Retrieve.

Compare the results to what you had earlier when you removed a CRL distributed point. CRLs show they have been verified.

Select OCSP (from AIA), then select Retrieve.

Select Exit.

To check details about the certificate and its CA configuration in the command prompt, navigate to the folder where the certificate is stored, then type:

> certutil -verify rsa.cer > rsa.txt

Open the text file rsa.txt. The last few lines should be as follows:

Verified Issuance Policies: None
Verified Application Policies:
1.3.6.1.5.5.7.3.1 Server Authentication
Leaf certificate revocation check passed
CertUtil: -verify command completed successfully

Using PowerShell, back up the CA database by running the command:

> Backup-CARoleService - Path <path_to_backup_file> - DatabaseOnly

> certutil - config WINserver1\CA-example -backupdb C:\Users\Administrator\Documents\dbexample backup

Export the certificate on machine #1:

Back up the contents of the Security World data from the following location: C:\ProgramData\nCipher\KeyManagement Data\local.

Uninstall the CA from machine #1.

Copy the backup of the Security World data to the following folder on machine #2: C:\ProgramData\nCipher\KeyManagement Data\local.

Load the Security World onto the HSM on machine #2 by running the command:

> new-world -l

Run the CNG Configuration Wizard.

> capingwizard

Copy and install the X.509 certificate into the local user Trusted Root CA Store on machine #2:

Install the certificate to the Cert:\LocalMachine\My\ store. Using PowerShell, navigate to the LocalMachine:

> Set-Location -Path Cert:\LocalMachine\My\

> Import-Certificate -FilePath <path to certificate>\Certificate_Name.cer

Repair the certificate store by running the following command from the console:

> certutil -f -repairstore -csp "nCipher Security World Key Storage Provider" my "<cert serial number>"

my "Personal"
================ Certificate 0 ================
Serial Number: 13fa1422bfba4f9a4303e2aa162c25b2
Issuer: CN=ADCS-IO-CA, DC=ADCSDC, DC=internal
NotBefore: 11/10/2019 09:44
NotAfter: 11/10/2024 09:51
Subject: CN=ADCS-IO-CA, DC=ADCSDC, DC=internal
Certificate Template Name (Certificate Type):CA
CA Version: V0.0
Signature matches Public Key
Root Certificate: Subject matches Issuer
Template: CA, Root Certification Authority
Cert Hash(sha1): 486232dc0583012d47c75c74eb0d1b65da9f9484
Key Container = ADCS-IO-CA
Provider = nCipher Security World Key Storage Provider
Private key is NOT exportable
Signature test passed
CertUtil: -repairstore command completed successfully.

Select Start > Server Manager to open Server Manager.

Install and configure the CA as described in Install and configure AD CS with Windows Server Enterprise.

Install and configure AD CS with the following settings:

When the CA installation is complete, select Close in the Results window.

Stop the CA service.

Copy the backup of the CA database data to machine #2.

Run the command:

> certutil -shutdown

On machine #2, restore the CA database by running the command:

> certutil.exe -f -restoredb <BackupDirectory>

Restart the CA by running the command:

> net start certsvc

Verify that the CA service has started successfully by running the command:

> sc query certsvc

Using PowerShell, back up the CA database by running the command:

> Backup-CARoleService - Path <path_to_backup_file> - DatabaseOnly

> certutil - config WINserver1\CA-example -backupdb C:\Users\Administrator\Documents\dbexample backup

Export the certificate on machine #1:

Back up the contents of the Security World data from the following location: C:\ProgramData\nCipher\KeyManagement Data\local.

Uninstall the CA from machine #1.

Copy the backed-up Security World data on the following path on machine #2: C:\ProgramData\nCipher\KeyManagement Data\local.

Load the Security World onto the HSM on machine #2, by running the command:

> new-world -l

Run the CNG Configuration Wizard.

> capingwizard

Create the temporary folder C:\temp.

Add the system environment variable NFAST_NFKM_TOKENSFILE:

Copy and install the X.509 certificate into the local user Trusted Root CA Store on machine #2:

Install the certificate into Cert:\LocalMachine\My\ store. Using PowerShell, navigate to the LocalMachine:

> Set-Location -Path Cert:\LocalMachine\My\

> Import-Certificate -FilePath <path to certificate>\Certificate_Name.cer

At an elevated command prompt, use preload to relink the CA certificate and private key.

> preload --module=1 -f c:\temp\nfast_nfkm_tokensfile --cardset-name="<CARDSET_NAME>" certutil -repairstore -csp "ncipher security world key storage provider" my "<SHA-1_THUMBPRINT_OF_CA_CERT>"

> preload --module=1 -f c:\temp\nfast_nfkm_tokensfile --softcard-name="<CARDSET_NAME>" certutil -repairstore -csp "ncipher security world key storage provider" my "<SHA-1_THUMBPRINT_OF_CA_CERT>"

my "Personal"
================ Certificate 0 ================
Serial Number: 13fa1422bfba4f9a4303e2aa162c25b2
Issuer: CN=ADCS-IO-CA, DC=ADCSDC, DC=internal
NotBefore: 11/10/2019 09:44
NotAfter: 11/10/2024 09:51
Subject: CN=ADCS-IO-CA, DC=ADCSDC, DC=internal
Certificate Template Name (Certificate Type):CA
CA Version: V0.0
Signature matches Public Key
Root Certificate: Subject matches Issuer
Template: CA, Root Certification Authority
Cert Hash(sha1): 486232dc0583012d47c75c74eb0d1b65da9f9484
Key Container = ADCS-IO-CA
Provider = nCipher Security World Key Storage Provider
Private key is NOT exportable
Signature test passed
CertUtil: -repairstore command completed successfully.

Ensure that the nShield Service Agent is running. This can be viewed in the task tray.

At an elevated command prompt, use preload before you install the CA.

> preload --module=1 -f c:\temp\nfast_nfkm_tokensfile --cardset-name="<CARDSET_NAME>" pause

> preload --module=1 -f c:\temp\nfast_nfkm_tokensfile --softcard-name="<CARDSET_NAME>" pause

Select Start > Server Manager to open Server Manager.

Install and configure the CA as described in Install and configure AD CS with Windows Server Enterprise.

Install and configure AD CS with the following settings:

When the CA installation is complete, select Close in the Results window.

Remove the previously added system environment variable NFAST_NFKM_TOKENSFILE.

Stop the CA service, then copy the backed-up CA database data onto machine #2.

Run the command:

>certutil -shutdown

On machine #2, restore the CA database by running the command:

>certutil.exe -f -restoredb <BackupDirectory>

Restart the CA by running the command:

>net start certsvc

Verify that the CA service has started successfully by running the command:

>sc query certsvc

Back up the CA database by running the command:

> certutil -config <CA_config_string> -backupdb <BackupDirectory>

Back up the Security World data and the private key, which are found in C:\ProgramData\nCipher\Key Management Data\local. For more information about backing up a Security World, refer to the User Guide for the HSM.

Uninstall the CA from machine #1.

Copy the backed-up Security World data and the private key to C:\ProgramData\nCipher\Key Management Data\local on machine #2.

Load the Security World onto the HSM on machine #2, by running the command:

> new-world -l

Run the CNG Configuration Wizard, then select Use existing Security World.

Install Microsoft Active Directory Certificate Services with the following settings:

Copy the backed-up CA database data onto machine #2.

Run the command:

> certutil -shutdown

On machine #2, restore the CA database by running the command:

> certutil.exe -f -restoredb <BackupDirectory>

Restart the CA by running the command:

> net start certsvc

Verify that the CA service has started successfully by running the command:

> sc query certsvc