Why The DEP feature (Data Execution Prevention) must be turned OFF when using the Siebel Applications
The DEP feature (Data Execution Prevention) must be turned OFF when used with Siebel, as Oracle has not yet included the specialized code required to fully implement this feature. This may be done by unchecking the relevant box on the individual client browsers, or by using the Group Policy tools, or by using the relevant Vista control panel. A description of how to turn off DEP with Vista may be found here: http://www.vistax64.com/tutorials/65790-dep-turn-off-programs.html.
DEP can be disabled in the following ways:
1.IE8 > Tools > Internet Options > Advanced tab
2.Starting CMD "As Administrator" and running the command
bcdedit.exe /set {current} nx AlwaysOff
3.IE Group Policy administration tool
In order to support DEP under Windows, a computer's processor must support hardware-enforced DEP. You can determine this by running
wmic OS Get DataExecutionPrevention_Available
in a CMD window; "TRUE" means hardware support exists. The level of DEP running can be determined by running
wmic OS Get DataExecutionPrevention_SupportPolicy
This returns an integer from 0-3.
The default value is "2" in which case only Windows system components and services have DEP applied. A value of "0" means DEP is always off and "1" is always on for all processes.
Setting this value to "3" is a potential work-around. The policy in this case is that DEP is enabled for all processes but Administrators can manually create a list of specific applications which do not have DEP applied.
Implementation of the DEP feature is dependent on using the Microsoft VS 2008 compiler. Siebel is currently compiled with the VS 2003 compiler but plans to move to the VS 2008 compiler in an upcoming release. Until then it is not technically possible for Siebel to support DEP/NX.
It is important to understand that the DEP feature only helps with one kind of security vulnerability - code injection. Siebel software includes protection against this specific mechanism. The ENCODEDATA parameter prevents execution of any code that is in Siebel data, and this is the default setting for Siebel.
Related Articles:
Browse Categories
User login
Navigation
Popular content
- Autosys Job Handling (13,688)
- GE UNIVERSAL REMOTE INSTRUCTIONS (12,386)
- Siebel User properties (9,114)
- Test 1 - NC Drivers License Test - DMV Question Dump (8,811)
- Making a View "Read Only" based on a criteria: Aspect User Property (4,231)
- Siebel Application Response Measurement (SARM) (4,167)
- Siebel Predefined Queries (PDQ) – Reference (4,091)
- Siebel Server Component Event Logging (3,676)
- Strategies for Building Team Cohesion (3,163)
- How to create the EBC’s in Siebel (3,096)
Readers who viewed this page, also viewed:
- Server Sizing for Siebel Analytics - OBIEE (50.0%)
- What to expect from Open UI for Siebel CRM (43.8%)
- CRM Siebel Application on iPad and iPhone (43.8%)
- D&B Announces Availability of D&B360TM for Siebel CRM (43.8%)
- Siebel Multi Lingual Changes – Considerations (43.8%)
- Configuring Actuate Siebel Reports Server – Post Installation Tasks (43.8%)
- Installing Patch in Siebel 8 - Client using Opatch Utility (43.8%)
- How to collect analytical information about the usage of Siebel Views (43.8%)
- Resolving Siebel High Interactivity problems (37.5%)
- How to Troubleshoot Database Errors Caused by Deleting Repositories using Siebel Tools (37.5%)
