Type:
Workaround
Summary:
When an instance of SQL Server is Secured with Encryptionizer it may interfere with the functioning of the Imperva Agent.
Additional Information:
When attempting to connect the Imperva Agent to the Secured SQL Server instance you may receive an “Access Denied” message from the Imperva Agent, part of the Imperva Data Protection and Database Audit product.
Encryptionizer includes several anti-hacking features that prevent code injection into the Secured SQL Server process. However, in the case of the Imperva Agent, the injection is not malicious.
You can turn off Encryptionizer’s anti-injection feature with the following procedure. Note that this will require restarting SQL Server (and possibly a reboot).
- Enter a Command Window as Administrator
- On a x64 (64-bit) Operating System run these two commands:
REG.EXE ADD HKLMSOFTWARENetLibParameters /reg:32 /v Features /t REG_DWORD /d 1 /f
REG.EXE ADD HKLMSOFTWARENetLibParameters /reg:64 /v Features /t REG_DWORD /d 1 /f - On an x86 (32-bit) Operating System run this command:
REG.EXE ADD HKLMSOFTWARENetLibParameters /v Features /t REG_DWORD /d 1 /f - From the Encryptionizer main menu start the Administration Wizard.
- If the SQL instance is already Secured, Unsecure it. At the end click Relaunch.
- Resecure the SQL instance with the same keys and additional options previously used.
- Finally, restart the SQL Server instance.
- Restart the Imperva agent.
- If the Imperva Agent is still unsuccessful in connecting, try rebooting the system.
- If still unsuccessful, contact NetLib Support.
Warning:
Disabling the Encryptionizer anti-injection feature for a Secured SQL Instance will allow any injections, both safe (such as Imperva) and malicious. We recommend you disable this feature only as needed.