Dalet Galaxy and Windows Data Execution Prevention (DEP)

When Data Execution Prevention (DEP) is enabled on Windows, some of Dalet Galaxy Java agents may terminate unexpectedly or drop active connections. This appears to be due to how DEP enforces memory execution restrictions, which can sometimes interfere with certain runtime behaviors in Java applications.

While DEP is a valid security feature, in practice, it primarily protects against a specific class of memory-based exploits (such as buffer overflows that execute injected code). These types of attacks are relatively uncommon in modern, well-managed environments especially when other security controls are in place (e.g., up-to-date OS patching, endpoint protection, network segmentation, and restricted access).

In this context, disabling DEP for Dalet Galaxy is considered low risk, particularly because:

• The system is running trusted, controlled workloads
• It is not exposed to untrusted code execution
• Other security layers remain active and effective

Given the operational impact that could be seen, we recommend disabling DEP (or alternatively configuring it more selectively) to ensure stability of the Java agents.

To disable DEP, please run: bcdedit.exe /set nx AlwaysOff

To enable DEP, run bcdedit.exe /set nx AlwaysOn