Configuring bypassing rules for NX

Prev Next

The NX feature uses the Windows Data Execution Prevention (DEP) feature to protect processes against exploits that try to execute code from writable memory area (stack/heap). MP-NX also provides granular bypass capability and raises violation events that can be viewed on the Windows Event Viewer console.

To protect processes against exploits that try to execute code from writable memory area, configure rules to add executables to NX. This technique prevents code from being run from a non-executable memory region.

Task

Syntax

Description

Bypass executables from NX.

sadmin attr add –n <filename1 ... filenameN>

Specify one or more executables where NX must be bypassed.

For example, sadmin attr add –n alg.exe

Bypass an executable and its child processes from NX.

sadmin attr add –n -y <filename1 ... filenameN>

Specify an executable where NX must be bypassed, including its child processes. You can specify the -y option only with the -n option.

For example, sadmin attr add –n -y alg.exe

Remove executables from NX bypass.

sadmin attr remove –n <filename1 ... filenameN>

Specify one or more executables to remove from NX bypass; in effect NX is enforced.

For example, sadmin attr remove –n alg.exe

List the executables that are bypassed from NX.

sadmin attr list –n

Lists all executables that NX bypasses.

For example, sadmin attr list –n

Flush NX bypass rules from all executables.

sadmin attr flush –n

Removes the NX bypass rules from all executables.

For example, sadmin attr flush –n