Best Practices for Securing Oracle E-Business Suite Release 12

8/10/2019 Best Practices for Securing Oracle E-Business Suite Release 12

1/68

Best Practices for Securing

Oracle E-Business Suite

Release 12

Oracle Corporation

Version 1.0.0


2/68

ii Best Practices for Securing Oracle E-Business Suite Release 12

Latest version of this document available underMetalink Note 403537.1.

Revision History

Version Release Date Descriptions

1.0.0 Feb 2007 Initial version for Release 12, based on 11iversion ML 189367.1

Copyright 2007 Oracle. All rights reserved.

Primary Authors: Erik Graversen, James Nurthen

Contributors: David Kerr, George Buzsaki, Deepak Louis, Andy Philips, Ashok Subramanian, Rajiv Muthyala,Remi Aimsuphanimit, Emily Nordhagen.

Excerpts of documents [IntA, IntB] reproduced with permission from Integrigy Corporation.

This document is provided for informational purposes only and the information herein is subject to change

without notice. Please report any errors herein to Oracle Corporation by filing a documentation bug against

product code 510, component SEC_COMP. Oracle Corporation does not provide any warranties covering and

specifically disclaims any liability in connection with this document.

Oracle is a registered trademark.

Oracle Corporation World Headquarters

500 Oracle Parkway

Redwood Shores, CA 94065

U.S.A.

Worldwide Inquiries:

650.506.7000

Fax 650.506.7200

Worldwide Support:

http://www.oracle.com/support


3/68

Table of Contents

iii

Overview...............................................................................................................................................................1System Wide Advice 2

Changes from 11i 3

Oracle TNS Listener Security...............................................................................................................................5Hardening 5Network 5

Authentication 6

Authorization 7

Audit 8

Oracle Database Security......................................................................................................................................9Hardening 9

Authentication 9

Authorization 10

Audit 12

Oracle Application Tier Security........................................................................................................................15Hardening 15

Authorization 16

Audit 16

E-Business Suite Security...................................................................................................................................17Hardening 17

Network 18

Authentication 19

Authorization 22

Audit 24

Advanced Audit 26

Desktop Security.................................................................................................................................................29Hardening 29

Operating Environment Security ...................... ........................... ......................... ...................... ........................ 31Hardening 31

Network 32Authentication 33

Authorization 34

Maintenance 34

Extras for Experts ......................... ........................... ...................... ......................... ........................... .................37Detect and Prevent Duplicate User Sessions 37

Customize Password Validation 37

Advanced Security/Networking Option (ASO/ANO) 37

Configure Listener on a Non-Default TCP Port 38

Hardening External Procedure (EXTPROC) Services 38

Appendix A: Security Setup Forms....................................................................................................................43

Appendix B: Security Setup Forms That Accept SQL Statement ......................................................................45

Appendix C: Database Schemas Shipped with E-Business Suite ......................................................................47Appendix D: Processes Used by E-Business Suite.............................................................................................51

Appendix E: Ports Used by E-Business Suite ....................................................................................................53

Appendix F: Sample Linux Hardening of the Application Tier .........................................................................55

Appendix G: References & More Resources......................................................................................................59


4/68

Table of Contents

iv


5/68

Security Checklist

v

Security Checklist

This section contains a summary of this documents best practice suggestions and

their page locations. Use this summary as a security reference guide or checklist.

Overview Keep software up to date 2

Restrict network access to critical services 2 Follow the principle of least privilege 2 Monitor system activity 2

Keep up to date on latest security information 2 UPdated Technology Stack 3 Modified Directory Structure 3

Oracle TNS Listener Security Harden operating environment 5

Add IP restrictions or enable Valid Node Checking 5 Specify connection timeout 6 Enable encryption of network traffic 6

Enable TNS Listener password 6 Enable admin restrictions 7 Enable TNS Listener logging 8

Oracle Database Security Harden operating environment 9

Disable XDB 9 Review database links 9 Remove operating system trusted remote logon 9

Implement two profiles for password management 10 Change default installation passwords 10 Restrict access to SQL trace files 11

Remove operating system trusted remote roles 11 Limit file system access within PL/SQL 11 Limit dictionary access 11

Revoke unneccessary grants GIVEN to APPLSYSPUB 11 Configure the database for auditing 12 Audit database connections 12 Audit database schema changes 12 Audit other activities 13 Audit administrators and their actions 13

Review audit records 13 Maintain audit records 14


6/68

Security Checklist

vi

Secure audit records 14

Oracle Application Tier Security

Harden operating environment 15 Remove application server banner 15 Remove unnecessary directives 15 Turn off directory indexing 15

Unload Apache autoindex module 16 Prevent search engine indexing 16 Protect administrative web pages 16

Disable test pages 16 Configure logging 16

E-Business Suite Security

Harden operating environment 17 Strike passwords from adpatch logs 17

Set Workflow notification mailer SEND_ACCESS_KEY to N 18 Set Tools environment variables 18 Use SSL (HTTPS) between browser and web server 18

Use External webtier if exposing any part of EBS to the internet 18 Use Terminal Services for client-server programs 18 Change passwords for seeded application user accounts 19

Consider Using Single-Sign-On 20 Tighten logon and session profile options 20 Create new user accounts safely 20

Create shared responsibilities instead of shared accounts 20 Configure Concurrent Manager for safe authentication 20 Activate Server Security 20

Review Guest user responsibilities 22 Review users with administrative responsibilities 22 Limit access to security related forms 22

Limit access to forms allowing SQL entry 22 Set other security related profile options 22 Restrict responsibilities by web server trust level 23

Set Sign-On audit level 24 Monitor system activity with OAM 24

Retrieve audit records using Reports 24 Retrieve audit records using SQL 25 Purge audit records 25 Review data tracked (no Reports available) 25

Configuring audit trail 26 Generate and identify audit trail objects 26 Choose tables to audit 26


7/68

Security Checklist

vii

Retrieve audit records using SQL 27

Purge audit records 27 References on E-Business Suite auditing 27

Desktop Security Configure browser 29 Update browser 29

Turn off AutoComplete in Internet Explorer 29 Set policy for unattended PC sessions 29

Operating Environment Security Cleanup file ownership and access 31 Cleanup file permissions 31

Lockdown operating system libraries and programs 32

Filter IP packets 32 Prevent spoofing 33

Eliminate telnet connections 33 Eliminate ftp connections 33 Verify network configuration 33

Monitor for attacks 33 Configure accounts securely 33 Limit root access 33

Manage user accounts 34 Do Not Allow guest accounts 34 Secure NFS 34

Secure operating system Devices 34 Secure executables 34 Secure file access 34

Extras for Experts Detect and Prevent Duplicate User Sessions 37

Customize Password Validation 37 Advanced Security/Networking Option (ASO/ANO) 37 Configure Listener on a Non-Default TCP Port 38

Hardening External Procedure (EXTPROC) Services 38 EXTPROC Listener Configuration 39

EXTPROC Testing Procedure 40


8/68

Security Checklist

viii

Appendix A: Security Setup Forms

Appendix B: Security Setup Forms That Accept SQL Statement

Appendix C: Database Schemas Shipped with E-Business Suite

Appendix D: Processes Used by E-Business Suite

Appendix E: Ports Used by E-Business Suite

Appendix F: Sample Linux Hardening of the Application Tier

Appendix G: References & More Resources


9/68

Overview

1

Overview

In todays environment, a properly secured computing infrastructure is critical. When securing the infrastruc-

ture, a balance must be struck between risk of exposure, cost of security and value of the information protected.

Each organization determines its own correct balance. To that end, we provide best practices (practical advice)

for securing Oracles E-Business Suite.

The recommendations that follow cross three tiers of machines (browser, application middle-tier and database)

and fall into five categories (hardening, network security, authentication, authorization and auditing). We cover

security for the Database and Listener, the Application Server, the E-Business Suite and individual desktops. We

follow this with advice for hardening operating systems including a sample Linux hardening (in the Appendix).

The last section Extras for Experts c ollects together advice that goes beyond the typical best practice.

Each section contains advice spanning five categories:

Hardening Covers hardening the file system, programs, products and configuration.

Network Covers physical topology, firewalls, IP restrictions at web server and database listener.

Authentication Covers account management, password management and other account related activities.

Authorization Covers restrictions to executables, data files, web pages, administrative tools, etc.

Audit Covers configuration, on-going review and purging.

iAS

ORACLE HOME

Apache

Concurrent Manager

Discoverer

Forms

TNS Listener

Tools

APPL_TOPCOMMON_TOP,JAVA_TOP,HTML_TOP, PORTAL_TOP,JRE_TOP, PRODUCT_TOPS

ORACLE HOME

APPLICATIONTIER

Terminal Server

Listener

RDBMS

RDBMS

ORACLE HOME

Web Browser

Forms applet

DESKTOPTIER DATABASETIER

Sun JRE


10/68

Overview

2

SYSTEM WIDE ADVICE

Some advice applies to the entire E-Business deployment and the infrastructure in which it operates.

KEEP SOFTWARE UP TO DATE

One of the principles of good security practice is to keep all software versions and patches up to date. Through-

out this document, we assume an E-Business Suite maintenance l evel of 12.0.0 or later. The latest version of

Autoconfig (TXK) configures a system following advice from this document. It also contains a patch set

checker to assist with patch application. This cannot be emphasized enough, for many reasons including good

security practice, move to the latest version of Autoconfig and Patch Tools (AD).

RESTRICT NETWORK ACCESS TO CRITICAL SERVICES

Keep both the E-Business application middle-tier and the database behind a firewall. In addition, place a fire-

wall between the middle-tier and the database. The firewalls provide assurance that access to these systems is

restricted to a known network route, which can be monitored and restricted, if necessary. As an alternative, a

firewall router substitutes for multiple, independent firewalls.

If firewalls cannot be used, be certain to configure the TNS Listener Valid Node Checking feature which

restricts access based upon IP address.

Restricting database access by IP address often causes application client/server programs to fail for DHCP cli-

ents. To resolve this, consider using static IP addresses, a software/hardware VPN or Windows Terminal Ser-

vices or its equivalent.

FOLLOW THE PRINCIPLE OF LEAST PRIVILEGE

The principle of least privilege states that users should be given the least amount of privilege to perform their

jobs. Over ambitious granting of responsibilities, roles, grants, etc., especially early on in an organizations life

cycle when people are few and work needs to be done quickly, often leaves a system wide open for abuse. User

privileges should be reviewed periodically to determine relevance to current job responsibilities.

MONITOR SYSTEM ACTIVITY

System security stands on three legs: good security protocols, proper system configuration and system monitor-

ing. Auditing and reviewing audit records address this third requirement. Each component within a system has

some degree of monitoring capability. Follow audit advice in this document and regularly monitor audit records.

KEEP UP TO DATE ON LATEST SECURITY INFORMATION

Oracle continually improves its software and documentation. Check this note yearly for revisions.


11/68

Overview

3

DIFFERENCES FROM 11I

If you are familiar with Oracle E-Business Suite 11i and the 11i version of this document these are the most

important differnces that you will notice between 11i and Release 12.

UPDATED TECHNOLOGY STACK

Release 12 has updated the entire technology stack, the table below summarizes the changes in versions and

highlights retired technology pieces.

MODIFIED DIRECTORY STRUCTURE

Release 12 has changed the way the file systems are organized. From a security perspective the most interesting

point is the introduction of the INSTANCE_TOP which is a new directory that contains instance specific config-

uration files and log files. This provides a cleaner separation of code directories and directories with instance

specific and variable data. See the Oracle Application Concepts guide from the installation DVD for more

detail.

11i Release 12

Database

9iR2 (9.2.0.x) 10gR2 (10.2.0.2.0)

Application Tier

IAS 1.0.2.2 + Developer 6i Fusion Middle Ware

OHS 1.0.2.2 (1.3.19 fork) OHS 10.1.3 (1.3.34 fork)

jserv oc4j

modplsql -eliminated-a

a. modplsql is no longer required in Release 12 and is not configured

Forms 6i Forms 10.1.2.0.2

Reports 6i Reports 10.1.2.0.2b

b. ReportWriter10 is only call ed from Concurrent Managers in Release 12 (no longerinvocable via the web interface)

Tools Oracl e_home: 8.0.6 Tools Oracle_home: 10.1.2

IAS Oracle_home: 8.1.7.4 Java Oracle_home: 10.1.3

JDBC 9 or 10 JDBC 10.2.0

Desktop Tier

JRE for Forms applet: Oracle Jinitiator JRE for Form applet: Sun JRE 1.5.0_8


12/68

Overview

4


13/68

Oracle TNS Listener Security

5


Oracle clients communicate with the database using the Transparent Network Substrate (TNS) protocol. When

the Listener receives a connection request (tcp port 1521, by default), it starts up a new database process andestablishes a connection between the client and the database.

This section contains security recommendations for the TNS Listener.

HARDENING

HARDEN OPERATING ENVIRONMENT

Follow the hardening instructions for Operating Environment Security on page 31.

NETWORK

ADD IP RESTRICTIONS OR ENABLE VALID NODE CHECKING

Valid Node Checking allows or denies access from specified IP addresses to Oracle services. To enable Valid

Node Checking for 9iand above, set the following parameters in$TNS_ADMIN/sqlnet.ora:

tcp.validnode_checking = YEStcp.invited_nodes = ( X.X.X.X, hostname, ... )tcp.excluded_nodes = ( hostname, X.X.X.X, ... )

The first parameter turns on Valid Node Checking. The latter two parameters respectively specify the IP

addresses or hostnames that are permitted to make or are denied from making network connections to Oracle

services. ReplaceX.X.X.Xwith the middle-tiers IP addresses. Middle-tier applications include web servers,

forms servers, concurrent managers, discoverer, terminal servers, central administrator machines and any

remote monitoring tool that uses SQLNet.

Note, use of SQLNet clients such assqlplus,toad, ADI from a windows desktop is not recommended. If

implemented, that desktop cannot use DHCP. Use a static IP address.

AutoConfig supports automated configuration. For more information, refer to Metalink Note 387859.1: Using

AutoConfig to Manage System Configurations with Oracle Applications Release 12 - or the Oracle Applications

Listener

RDBMS

RDBMS

ORACLE HOME

DATABASETIER


14/68


6

Concepts manual. AutoConfig enabled systems may use the latest OAM minipack to implement the manual

steps highlighted above.

SPECIFY CONNECTION TIMEOUT

In$TNS_ADMIN/listener.ora, set the following parameter:

CONNECT_TIMEOUT_$ORACLE_SID = 10

For example,

CONNECT_TIMEOUT_VIS12 = 10

WhereVIS12is the value of the ORACLE_SIDin this example.

Use the parameterCONNECT_TIMEOUTto specify the amounts of time, in seconds, for the Oracle Listener to

wait for the connection from a client to complete.

ENABLE ENCRYPTION OF NETWORK TRAFFIC

Ensure that the TNS network traffic in you EBS environment is not sent in-the-clear by enabling encryption of

the TNS (aka SQL*Net) traffic.

MetaLink note 391248.1 contains the instructions on how to do this for 11i - the setting of sqlnet.ora parameters

is relevant also for Release 12.

AUTHENTICATION

ENABLE TNS LISTENER PASSWORD

Setting a password for the Listener is one of the most important hardening procedure. These instructions assume

that the listener name is VIS12. The default for oracle databases in general is LISTENER while for EBS data-bases it is set to the SID of the dat abase.

Start the Listener control program:

$ lsnrctl

Set the current Listener in case you have more than one listener defined, then change the password.

LSNRCTL> set current_listener VIS12Current Listener is VIS12

LSNRCTL> change_passwordOld password: -- just hit returnNew password: -- new, secure password

Reenter new password: -- new, secure passwordConnecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=dbs01)(PORT=1541)))

Password changed for VIS12The command completed successfully

LSNRCTL> set passwordPassword:The command completed successfully

LSNRCTL> save_configConnecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=dbs01)(PORT=1541)))Saved DBLSNR configuration parameters.Listener Parameter File /x/db/tech_st/10.2.0/network/admin/VIS12_dbs01/listener.ora


15/68


7

The command completed successfully

This added the following lines tolistener.ora:

#----ADDED BY TNSLSNR 13-JAN-2007 11:47:56---

PASSWORDS_VIS12 = D911537D50B15546#--------------------------------------------

With the Listener password protected, ensure that file and directory settings can only be changed by editing the

listener.orafile (not via set commands in lsnrctl). Enable ADMIN_RESTRICTIONS by adding the fol-

lowing line tolistener.oraand reload the configuration file into the Listener:

$ echo "ADMIN_RESTRICTIONS_VIS12 = ON" >> listener.oraLSNRCTL> set current_listener VIS12

Current Listener is VIS12

LSNRCTL> set passwordPassword:The command completed successfully

LSNRCTL> reload

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=dbs01)(PORT=1541)))The command completed successfully

With these settings, the Listener configuration file cannot be changed via the tnslsnrprocess.

To undo these steps:

1. Editlistener.oraand remove the linesPASSWORDS_andADMIN_RESTRICTIONS_

2. Stop thetnslsnrprocess (usinglsnrctl or useps to find the pid andkillto kill it)

3. Restart the listener (usinglsnrctlstart)

Note, password protecting the TNS Listener has the following effects:

nly the oracle user can stop the TNS Listener usinglsnrctlwithout providing the password. The Listener process requires a password to listSERVICESorSTATUS.

This breaks some monitoring and remote administration tools, if they do not expect to provide a password.

Cannot start, stop, check status or run services on remote machines vialsnctrl. Use Enterprise Manager

for remote administration.

AUTHORIZATION

ENABLE ADMIN RESTRICTIONS

In$TNS_ADMIN/listener.ora, set the following parameter:

ADMIN_RESTRICTIONS_=ON

For example,

ADMIN_RESTRICTIONS_VIS12=ON

WhereVIS12is the name of the listener (equal to ORACLE_SIDin EBS)


16/68


8

Note, when ADMIN_RESTRICTIONSis ON, all theset commands inlsnrctl are disabled and the only way

to change the configuration is to edit the listener.orafile. Because password restrictions are enabled, some

remote administration tools may subsequently fail.

AUDIT

ENABLE TNS LISTENER LOGGING

To enable logging, in$TNS_ADMIN/listener.oraset the following parameters:

LOG_STATUS = ONLOG_DIRECTORY_$ORACLE_SID = $TNS_ADMINLOG_FILE_$ORACLE_SID = $ORACLE_SID

For example,

LOG_STATUS = ONLOG_DIRECTORY_VIS12 = /u/db/tech_st/10.2.0/network/admin/VIS12_dbs01

LOG_FILE_VIS12 = VIS12

WhereVIS12is theLISTENER_NAME.


17/68

Oracle Database Security

9


This section contains security recommendations for the Database.

HARDENING



DISABLE XDB

To support XDB, the TNS Listener process listens on two additional TCP ports: 2100 for ftp access and 8080 for

http access. Oracle E-Business Suite does not require these services; they should be disabled.

To disable XDB, remove or comment out the line in init.orathat reads*.dispatchers='(PROTOCOL=TCP) (SERVICE=sidXDB)'

REVIEW DATABASE LINKS

Review database links in both production and development environments.

AUTHENTICATION

Middle-tier applications logon to the database through application schemas rather than end-user accounts. Some

individuals (IT Administrators) may require direct access to the application database via their own schema.

REMOVE OPERATING SYSTEM TRUSTED REMOTE LOGON

This setting prevents the database from using an insecure logon protocol. Make sure init.ora contains:

REMOTE_OS_AUTHENT=FALSE

Listener

RDBMS

RDBMS

ORACLE HOME

DATABASETIER


18/68


10

IMPLEMENT TWO PROFILES FOR PASSWORD MANAGEMENT

The database provides parameters to enforce password management policies. However, some of the database

password policy parameters could lock-out the E-Business Suite. Because of this, we make specific recommen-

dations for or against using certain management features depending upon schema type.

Database profiles contain limits on database resources and password policies. Create two database profiles: one

for middle-tier application schemas and one for human beings. Assign middle-tier application schemas to the

first profile and all accounts used by administrators to the second profile.

For more information on profiles, see CREATE PROFILE in the Oracle SQL Reference documentation.

CHANGE DEFAULT INSTALLATION PASSWORDS

Following an installation, the application database instance contains default, open schemas with default pass-

words. These accounts and corresponding passwords are well-known, and they should be changed, especially

for a database to be used in a production environment. Default schemas come from different sources:

1. Default database administration schemas

2. Schemas belonging to optional database features neither used nor patched by E-Business Suite

3. Schemas belonging to optional database features used but not patched by E-Business Suite

4. Schemas belonging to optional database features used and patched by E-Business Suite

5. Schemas common to all E-Business Suite products

6. Schemas associated with specific E-Business Suite products

For the schemas in categories 1, 2 and 3, use standard database commands to change a password:

SQL> alter user identified by ;

For the schemas in categories 4, 5 and 6, use the application password change tool:

$ FNDCPASS APPS/ 0 Y SYSTEM/ ORACLE

To save time, category six (6) schema passwords may be changed en masseusing FNDCPASS. FNDCPASS

accepts a keywordALLORACLEforcing a change of all managed (category 6) schemas to the new password.

$ FNDCPASS APPS/ 0 Y SYSTEM/ ALLORACLE

To determine which schemas are managed by E-Business Suite (categories 4, 5 and 6), run the AD adutconf.sql

script. Appendix C: Database Schemas Shipped with E-Business Suite on page 47 contains a list of the sche-

mas by category, instructions and notes for managing schema passwords.

Patch 4926128 contain a SQL script that will list all open accounts with default password in your database.

Password Parameters Appl ication Profi le Admi nistrator Profile

FAILED_LOGIN_ATTEMPTS UNLIMITED 5

PASSWORD_LIFE_TIME UNLIMITED 90

PASSWORD_REUSE_TIME 180 180

PASSWORD_REUSE_MAX UNLIMITED UNLIMITED

PASSWORD_LOCK_TIME UNLIMITED 7

PASSWORD_GRACE_TIME UNLIMITED 14

PASSWORD_VERIFY_FUNCTION Recommended Recommended


19/68


11

AUTHORIZATION

RESTRICT ACCESS TO SQL TRACE FILES

Theinit.oraparameter_TRACE_FILES_PUBLICgrants file system read access to anyone who has acti-vated SQL tracing. Set this to i ts default value ofFalse.

_TRACE_FILES_PUBLIC=FALSE

REMOVE OPERATING SYSTEM TRUSTED REMOTE ROLES

Set the init.ora parameterREMOTE_OS_ROLESto False to prevent insecure remote roles.

REMOTE_OS_ROLES=FALSE

LIMIT FILE SYSTEM ACCESS WITHIN PL/SQL

The parameterUTL_FILE_DIR limits file system access for all database accounts using the PL/SQL API

UTL_FILE. Oracle E-Business Suite maintains some disk files and needs this parameter set.

UTL_FILE_DIR = ,,...

Avoid:

UTL_FILE_DIR = *

LIMIT DICTIONARY ACCESS

SetO7_DICTIONARY_ACCESSIBILITYto Falseto prevent users with Select ANY privilege from reading

data dictionary tables. False is the default for the 10g database.

O7_DICTIONARY_ACCESSIBILITY = FALSE

REVOKE UNNECCESSARY GRANTS GIVEN TO APPLSYSPUB

The following table lists the privileges that should be granted to t heAPPLSYSPUBschema. These are set in

/admin/sql/afpub.sql.

APPLSYSPUB

EXECUTE ON FND_DISCONNECTED

EXECUTE ON FND_MESSAGE

EXECUTE ON FND_PUB_MESSAGE

EXECUTE ON FND_SECURITY_PKG

EXECUTE ON FND_SIGNON

EXECUTE ON FND_WEBFILEPUB

INSERT ON FND_SESSIONSINSERT ON FND_UNSUCCESSFUL_LOGINS

SELECT ON FND_APPLICATION

SELECT ON FND_APPLICATION_TL

SELECT ON FND_APPLICATION_VL

SELECT ON FND_LANGUAGES_TL


20/68


12

To check permissions, login as SYSTEM and issue the following query:

SELECT * FROM dba_tab_privs WHERE grantee ='APPLSYSPUB';

To revoke unnecessary privileges granted to APPLSYSPUB schema, see patch 3763612. Release 12 Rapid Install

has a cleanAPPLSYSPUBby default. In addition, you should understand the implications of privil eges on cus-

tom objects granted to PUBLIC or a role.

AUDIT

This section describes the auditing capabilities available in Oracle database for Oracle E-Business Suite. Theserecommendations should not have a measurable performance impact.

CONFIGURE THE DATABASE FOR AUDITING

Ininit.ora, setAUDIT_TRAILto DB,OS orTRUE. Consult with the Applications Database Administrator

before setting this value to TRUE. When set toOS, the database stores its audit records on the file system:

AUDIT_TRAIL = OS

Set parameterAUDIT_FILE_DESTto the directory where the audit records should be stored. When not set,

AUDIT_FILE_ DESTdefaults to$ORACLE_HOME/rdbms/audit. In this example, the database places audit

records in directory/u01/logs/db/audit.

AUDIT_FILE_DEST = /u01/logs/db/audit

Restart the database for these parameters to take effect.

Note, the database generates some audit records by default, whether or not AUDIT_TRAILis enabled. For

example, Oracle automatically creates an operating system file as an audit record when a user logs in as SYSDBA

or asINTERNAL.

AUDIT DATABASE CONNECTIONS

Monitoring and auditing database sessions provides valuable information on database activity and is the only

way to identify certain types of attacks (for example, password guessing attacks on an application schema). By

auditing database sessions, suspicious connections to highly privileged schemas may be identified.

To audit sessions, login throughsqlplusas SYSTEMand issue the following command:SQL> audit session;

AUDIT DATABASE SCHEMA CHANGES

Audit any changes to the standard Oracle E-Business Suite database schemas or creation of new schemas. As

rare events, these changes may indicate inappropriate or malicious activity.

SELECT ON FND_LANGUAGES_VL

SELECT ON FND_LOOKUPS

SELECT ON FND_PRODUCT_GROUPS

SELECT ON F ND_PRODUCT_INSTALLATIONS

APPLSYSPUB


21/68


13

To audit schema changes, login through sqlplus as SYSTEMand issue the following command:

SQL> audit user;

AUDIT OTHER ACTIVITIES

To complete the recommended auditing, enable three other audit events: create database link, alter system and

system audit. The remaining audit options generate significant entries of little value. Oracle E-Business Suite

dynamically creates, alters and drops objects (tables, index, packages, etc.) on a regular basis. Auditing these

other actions provides little meaningful information.

To audit the last three events, login throughsqlplusas SYSTEM and issue the following commands:

SQL> AUDIT DATABASE LINK; -- Audit create or drop database linksSQL> AUDIT PUBLIC DATABASE LINK; -- Audit create or drop public database links

SQL> AUDIT SYSTEM AUDIT; -- Audit statements themselvesSQL> AUDIT ALTER ANY ROLE by ACCESS; -- Audit alter any role statementsSQL> AUDIT ALTER DATABASE by ACCESS; -- Audit alter database statements

SQL> AUDIT ALTER SYSTEM by ACCESS; -- Audit alter system statementsSQL> AUDIT CREATE ROLE by ACCESS; -- Audit create role statements

SQL> AUDIT DROP ANY ROLE by ACCESS; -- Audit drop any role statementsSQL> AUDIT PROFILE by ACCESS; -- Audit changes to profilesSQL> AUDIT PUBLIC SYNONYM by ACCESS; -- Audit public synonyms statements

SQL> AUDIT SYSDBA by ACCESS; -- Audit SYSDBA privilegesSQL> AUDIT SYSOPER by ACCESS; -- Audit SYSOPER privilegesSQL> AUDIT SYSTEM GRANT by ACCESS; -- Audit System grant privileges

AUDIT ADMINISTRATORS AND THEIR ACTIONS

Connections to the database as well asSYSDBAand SYSOPER actions (instance startup/shutdown) are always

logged to the directory$ORACLE_HOME/rdbms/audit. This file contains the operating system user and ter-

minal ID.

REVIEW AUDIT RECORDS

IfAUDIT_TRAILis set toOS, review audit records stored in the file name inAUDIT_FILE_DEST.

IfAUDIT_TRAILis set toDB, retrieve audit records from the SYS.AUD$ table. The contents can be viewed

directly or via the following views:

DBA_AUDIT_EXISTS

DBA_AUDIT_OBJECT

DBA_AUDIT_SESSION

DBA_AUDIT_STATEMENT

DBA_AUDIT_TRAIL

DBA_OBJ_AUDIT_OPTS

DBA_PRIV_AUDIT_OPTS

DBA_STMT_AUDIT_OPTS

The audit trail contains a lot of data; begin by focusing on the following:

Username Oracle Username.

Terminal Machine from which the user originated.

Timestamp Time the action occurred.

Object Owner The owner of the object that the user touched.

Object Name The name of the object that the user touched.


22/68


14

Action Name The action that occurred against the object (INSERT, UPDATE, DELETE, SELECT,

EXECUTE).

MAINTAIN AUDIT RECORDS

Archive and purge the audit trail on a regular basis, at least every 90 days. The database connection entries take

up significant space. Backup the audit file before purging.

SECURE AUDIT RECORDS

Audit data may contain confidential or privacy related data. Restrict audit trail access appropriately.


23/68


15


This section contains security recommendations for the Application Server.

HARDENING



REMOVE APPLICATION SERVER BANNER

To avoid exposing Apache version and enabled modules, turn off the banner in httpd.conf:

Set ServerSignature offSet ServerTokens Prod

REMOVE UNNECESSARY DIRECTIVES

If not using Autoconfig, use the following guidelines to remove unnecessary Apache directives.

In addition to any example or sample directories, remove or comment out references to documentation directo-

ries and other directives not needed to operate the application. Comment following in httpd.conf

TURN OFF DIRECTORY INDEXING

There are two goals when protecting a web server:

Reduce the amount of information available.

Reduce access to non-application related areas.

Directory indexes display the contents of a directory if there is not an index.htm or similar file available. Dis-abling this entry prevents an intruder from viewing the files in a directory, potentially finding a file that may be

of use in their quest to access the system. The quickest way to disable this feature is to modify

${IAS_ORACLE_HOME}/Apache/Apache/conf/httpd.confand ${IAS_ORACLE_HOME}/Apache/

Apache/conf /httpd_pls.co nfconfiguration files and comment out the following line:

# IndexOptions FancyIndexing

iAS

ORACLE HOME

ApacheOC4J

APPLICATIONTIER


24/68


16

UNLOAD APACHE AUTOINDEX MODULE

This module automatically generates directory indexes. To disable the module inhttpd.conf, comment these

lines as follows.

#LoadModule autoindex_module libexec/mod_autoindex.so#AddModule mod_autoindex.c

PREVENT SEARCH ENGINE INDEXING

For internet facing web servers, enable robot exclusion. This may be done either with a robots.txt file or

using a META tag. Seehttp://www.robotstxt.org/wc/robots.htmlfor more information.

AUTHORIZATION

Within Oracle Application Server, a number of web pages provide administrative and testing functionality.

These pages offer information about various services, the servers state and its configuration. While useful for

debugging, these pages must be restricted or disabled in a production system.

PROTECT ADMINISTRATIVE WEB PAGES

Use the configuration filehttpd.conf to limit web page access to a list of trusted hosts. To do this, create a

filetrusted.confand include it in the httpd.conffile. This new file contains the following content.

Replace uri-to-protect with the path of the page you wish t o protect

Replace with host machines from which administrators may connect.

Order deny,allowDeny from all

Allow from localhost

DISABLE TEST PAGES

Add the following directives inhttpd.confto prevent access fast-cgi test pages:

Order deny,allowDeny from all

Or better yet - unconfigure fast-cgi, it is not required by Release 12.

AUDIT

CONFIGURE LOGGING

Oracle Application Server respects Apaches logging parameters. When activated, as is done by default, the

server logs data about all web access to the system.


25/68


17


This section contains security recommendations for the Oracle E-Business Suite.

HARDENING



STRIKE PASSWORDS FROM ADPATCH LOGS

To stop adpatch from logging passwords, use the following flag:

adpatch flags=hidepw

iAS

ORACLE HOME

Apache

Concurrent Manager

Discoverer

Forms

TNS Listener

Tools

APPL_TOPCOMMON_TOP, JAVA_TOP,HTML_TOP, PORTAL_TOP,JRE_TOP, PRODUCT_TOPS

ORACLE HOME

APPLICATIONTIER

Terminal Server

Listener

RDBMS

RDBMS

ORACLE HOME

DATABASETIER

OC4J


26/68


18

SET WORKFLOW NOTIFICATION MAILER SEND_ACCESS_KEY TO N

WhenSEND_ACCESS_KEYis set toY, the workflow notification email bypasses the E-Business Suite sign-on

process; email notifications contain an access key. The key allows the user to access t he Notification Details

web page directly without authenticating. SetSEND_ACCESS_KEYto Nto prevent inclusion of the key with the

Notification Detail link. When set to N, an unauthenticated user who clicks on the notification link must sign onbefore accessing the Notification Details web page.

For more information, refer to Oracle Workflow Administrator's Guide .

SET TOOLS ENVIRONMENT VARIABLES

Prevent forms users from using the enter-query feature on a production system.

In Release 12 the forms parameters are set in the configuration file:

/x/inst/apps/VIS12_dbs01/ora/10.1.2/forms/server/default.env

NETWORK

USE SSL (HTTPS) BETWEEN BROWSER AND WEB SERVER

Information sent over the network and across the Internet in clear text may be intercepted. Secure Sockets Layer

(SSL) is an encryption scheme that negotiates an exchange of encryption keys. These keys are packaged in Cer-

tificates issued by a Certificate Authority (CA).

For information on setting up SSL with the Oracle E-Business Suite, refer to 376700.1 Enabling SSL for Ora-cle Applications Release 12.

USE EXTERNAL WEBTIER IF EXPOSING ANY PART OF EBS TO THE INTERNET

If you expose any part of your EBS production system to the internet, you should consult MetaLink Note

380490.1 for our best practice advice for deploying external EBS products to the internet. This document

describes the role of DMZs, external web-tiers, external responsibilities, URL firewall and reverse proxies in a

secure external EBS deployment.

USE TERMINAL SERVICES FOR CLIENT-SERVER PROGRAMS

Deploy components requiring direct connection to t he E-Business Suite database on servers rather than on end-

user desktop machines.

A majority of the E-Business Suite architecture supports this through a three-tier architecture; browser sessions

connect to middle-tier servers running Oracle 10g Application Server. If you have a well considered need to

connect to the database directly from a desktop, deploy a remote server environment based on Windows Server

Terminal Services, Citrix or Tarantella.

Form Environment Variable Value

FORMS_RESTRICT_ENTER_QUERY TRUE


27/68


19

While deploying the required applications development and/or production runtime tools on Terminal Services,

configure SQLNet Valid Node Checking and Application Server Security. The former isolates SQLNet access to

the Terminal Server and the latter identifies the terminal server to applications. These both prevent end-user

desktops from c onnecting to the production database instance. Register the terminal server used to deploy the

client/server components as a Managed SQLNet Access node. Further details are provided in section Add IPrestrictions or enable Valid Node Checking on page 5 and Activate Server Security on page 20.

AUTHENTICATION

CHANGE PASSWORDS FOR SEEDED APPLICATION USER ACCOUNTS

Oracle ships seeded user accounts with default passwords. Change the default passwords immediately. Depend-

ing on product usage, some seeded accounts may be disabled. You disable an application user account by setting

the END_DATE for the account. Do not disable SYSADMINorGUESTuser accounts.

Account Product / Purpose Change Disable

AME_INVALID _APPROVER AME WF migration 11.5.9 to 11.5.10 Y YANONYMOUS FND/AOL Anonymous for non-logged users Y Y

APPSMGR Routine maintenance via concurrent requests Y Y

ASGADM Mobile gateway related products Y Ya

a. Required for Mobile Sales, Service, and Mobile Core Gateway components.

ASGUEST Sales Application guest user Y Yb

b. Required for Sales Application.

AUTOINSTALL AD Y Y

CONCURRENT MANAGER FND/AOL: Concurrent Manager Y Y

FEEDER SYSTEM AD Supports data from feeder system Y Y

GUEST Guest application user Y N

IBE_ADMIN iSupport Admin user Y Yc

c. Required for iStore.

IBE_GUEST iSupport Guest user Y Yc

IBEGUEST iSupport Guest user Y Yc

IEXADMIN Internet Expenses Admin Y Y

INITIAL SETUP AD Y Y

IRC_EMP_GUEST iRecruitment Employee Guest Login Y Y

IRC_EXT_GUEST iRecruitment External Guest Login Y Y

MOBILEADM Mobile Applications Admin Y Y

OP_CUST_CARE_ADMIN Customer Care Admin for Oracle Provisioning Y Y

OP_SYSADMIN OP (Process Manufacturing) Admin User Y Y

STANDALONE BATCH PROCESS FND/AOL Y Y

SYSADMIN Application Systems Admin Y N

WIZARD AD Application Implementation Wizard Y Y

XML_USER Gateway Y Y


28/68


20

CONSIDER USING SINGLE-SIGN-ON

Oracle E-Business Suite Release 12 support integration with a Single Sign-On (SSO). For more information on

Single Sign-On deployments, refer to Metalink Note 376811.1 Integrating Oracle E-Business Suite Release 12

with Oracle Internet Directory and Oracle Single Sign-On.

TIGHTEN LOGON AND SESSION PROFILE OPTIONS

For local application users, the profile option settings below support strong passwords, account lockout after too

many failed logons and session inactivity timeout.

CREATE NEW USER ACCOUNTS SAFELY

Oracle User Management (UMX) provides a common user registration flow in which a user can enter a new

password or select to have one generated randomly. UMX uses workflow to drive the registration process once a

request has been submitted. See UMX Documentation for more details.

CREATE SHARED RESPONSIBILITIES INSTEAD OF SHARED ACCOUNTS

When users share one account, the system cannot identify which user performs a function, preventing account-

ability. Users share the same functions or permission sets, while the system tracks individual user actions.

CONFIGURE CONCURRENT MANAGER FOR SAFE AUTHENTICATION

Concurrent Manager passes the APPS schema password to concurrent programs on the command line. Because

some Operating Systems allow all machine users to read a programs command line arguments, the password

may be intercepted. To prevent this, define the concurrent program executable as a HOSTprogram in the Con-

current Program Executable form. EnterENCRYPTin the Execution Options field of the Concurrent Programs

window when defining a concurrent program using this executable. ENCRYPTsignals Concurrent Manager to

pass the username/password in the environment variable FCP_LOGIN. Concurrent Manager leaves argument $1

blank. To prevent username/password from being passed, enterSECURE in the Execution Options field. With

this change, Concurrent Manager does not pass the username/password to the program.

ACTIVATE SERVER SECURITY

Oracle E-Business Suite Release 12 is deployed in a multi-tier configuration with one database server and many

possible middle-tier application servers. The application servers include Apache JSP/Servlet, Forms, Discov-

erer. Any program which makes a SQLNet connection to the Oracle Applications database needs to be trusted atsome level. The Server Security feature ensures that SQLNet connections originate from trusted machines.

Setup Server Security

The application server security feature is activated by default.

This setting is affected by the autoconfig variable s_appserverid_authentication.

Profile Option Name Recommendation

SIGNON_PASSWORD_LENGTH 8

SIGNON_PASSWORD_HARD_TO_GUESS YES

SIGNON_PASSWORD_NO_REUSE 180

ICX_SESSION_TIMEOUT 30


29/68


21

Application Server Security has three states:

OFF Inactivates Server Security. Server and code IDs are not checked. Appropriate for machines com-pletely under an adminis trators control. OK for development systems without production data.

ON Equivalent to OFF from a security perspective. Not recommended for production systems.

SECURE Recommended; only registered application servers and trusted code modules may connect.

Check Server Security Status

Check the Server Security status using the STATUS command in the AdminAppServer utility before activating

server security to ensure that all desired Application Servers have been registered. For details, see System

Administrators Guide, Administering Server Security.

Adding Server IDs

Register application servers as trusted machines with a database server. The .dbcfile contains the Application

Servers ID.

Use the AdminAppServer utility to generate server IDs and register them with a database. The program adds

them to the database automatically when the AdminAppServer is used to create a .dbcfile:

jre oracle.apps.fnd.security.AdminAppServer apps/ \ADD [SECURE_PATH=$FND_TOP/secure] \DB_HOST= \DB_PORT= \DB_NAME=

See the section on Creating DBC files in Administering Oracle Applications Security in Release 11i for more

details.

Updating Server IDs

jre oracle.apps.fnd.security.AdminAppServer apps/ \

UPDATE DBC= APPL_SERVER_ID

Providing theAPPL_SERVER_ID argument forces a new ID to be generated and added to the .dbcfile. If the

APPL_SERVER _IDargument is not provided, AdminAppServer synchronizes the server IDs found in the .dbc

file with the database automatically.

Deleting Server IDs

jre oracle.apps.fnd.security.AdminAppServer apps/ \

DELETE DBC=

Server Security Activation

To activate basic server security from the command line ( ONmode):

jre oracle.apps.fnd.security.AdminAppServer apps/ \AUTHENTICATION ON DBC=


30/68


22

To activate full server security from the command line (SECUREmode):

jre oracle.apps.fnd.security.AdminAppServer apps/ \AUTHENTICATION SECURE DBC=

To deactivate server security from the command line ( OFFmode):

jre oracle.apps.fnd.security.AdminAppServer apps/ \AUTHENTICATION OFF DBC=

AUTHORIZATION

REVIEW GUEST USER RESPONSIBILITIES

To represent an unauthenticated user session the E-Business Suite uses a guest account for certain applications

(such as iStore). Limit guest user responsibilities to those necessary for sign-on and guest access. The Define

User Form allows the System Administrator to review and modify guest user responsibilities.

REVIEW USERS WITH ADMINISTRATIVE RESPONSIBILITIES

In E-Business Suite, the SYSADMIN responsibility has broad administrative privileges. For this reason, regu-

larly review this list of users. In addition to the generic SYSADMIN responsibility, most products have their

own administrative responsibility. Review these responsibilities from time to time. Define and assign appropri-

ate responsibilities for end users that clearly reflect their line of duty.

LIMIT ACCESS TO SECURITY RELATED FORMS

Some forms allow users to modify the E-Business Suite security setup. Through these forms users could alter

security configuration (e.g. grant inappropriate privileges to themselves or to others). Assign users only those

responsibilities necessary for them to perform their tasks. Appendix A: Security Setup Forms on page 43 con-

tains a list of forms that allow security setup. Consider auditing the database tables listed there.

LIMIT ACCESS TO FORMS ALLOWING SQL ENTRY

To improve flexibility, some forms allow users to enter SQL statements. These forms are typically used during

the initial setup of the system. In a production system access to these forms must be restricted. Appendix B:

Security Setup Forms That Accept SQL Statement on page 45 contains a list of Forms that allow the user to

edit code, add code or otherwise affect executable code. Restrict access to these forms by assigning the respon-

sibility to a small group of users. Consider auditing the database tables listed in the appendix.

SET OTHER SECURITY RELATED PROFILE OPTIONS

Refer to the table below and set t he suggested values for the profile options.

Profile Option Suggest

AuditTrail:Activate Yes

Concurrent:Report Access Level User

FND:Diagnostics No

Sign-on:Notification Yes

Utilities:Diagnostics No


31/68


23

RESTRICT RESPONSIBILITIES BY WEB SERVER TRUST LEVEL

When web servers have been assigned a server trust level the system may restrict access to a responsibility

based upon that trust level. Three trust levels are supported:

1. administrative2. normal

3. external

Typically, administrativeweb servers are used exclusively by system administrators, are considered secure and

have full application access with few limitations.Normalweb servers are those used by employees within a

companys intranet and requiring non-administrative responsibilities. Lastly, customers or employees outside of

a companys firewall connect to externalservers. These have access to a small set of responsibilities.

Setting the Server Trust Level for a Server

To assign a trust level to a Web server, the administrator sets the NODE_TRUST_LEVEL profile option. This

option, a server-based profile option, can be set to either 1, 2 or 3. The number 1 means administrative, 2 means

normaland 3 means external. To avoid having to set the NODE_TRUST_LEVEL for every single Web server,

administrators may wish to set the NODE_TRUST_LEVEL profile to some default level of trust at the site

level. If no value is set for NODE_TRUST_LEVEL, the Web server is assumed to have a trust level of 1 (i.e.,

administrative).

Restricting Access to a Responsibility

When a user logs on to Oracle Applications via a Web server, the system determines which responsibilities are

valid for that user, and of those responsibilities, which can be accessed from that particular Web server. The sys-

tem returns only responsibilities appropriate for the Web server Trust Level.

To restrict access to a responsibility, set the Application Server Trust Level profile option value for that respon-

sibility to be the number 1, 2 or 3. This indicates that only Web servers with the same or greater ordinal trust

level may access that responsibility.

For example, a responsibility with an Application Server Trust Level set to 1 (administrative) would only be

available if the Web server has its Application Server Trust Level set to 1 ( administrative), as well. A responsi-

bility with Application Server Trust Level set to 2 (normal) would only be available if the Web server has its

Server Trust Level set to either 1 (administrative ) or 2 (normal).

Profile Option - Application Server Trust Level

Responsibilities or applications with the specified level of trust can only be accessed by an application server

with at least the same level of trust. Users can see this profile option, but they cannot update it. The system

administrator access is described in the following table:

The internal name for this profile option is APPL_SERVER_TRUST_LEVEL.

Level Visible Allow Update

Site Yes YesApplication Yes Yes

Responsibility Yes Yes

User No No


32/68


24

References

For more information on how to enable and use the above security features, refer to Oracle Applications System

Administrator's Guide.

AUDIT

This chapter describes how to configure and use Oracle E-Business Suite audit features. It provides an explana-

tion of the features available, configuration steps and best practices for auditing. It also suggests which common

application objects like foundation objects, users and responsibilities to audit.

Often, E-Business Suite deployments do not take advantage of the auditing features due to the perceived com-

plexity and performance issues. Properly configuring auditing and limiting auditing to appropriate tables should

not have a measurable performance impact.

SET SIGN-ON AUDIT LEVEL

The valid settings for the profile optionSIGNONAUDIT:LEVEL

areNone

,User

,Responsibility

and

Form. At site level, set this profile option toFormto enable as much auditing as possible. At this setting, the

system logs all user sign-ons, responsibility selections and form accesses to APPLSYS.FND_LOGINS,APPL-

SYS.FND_LOGIN_RESPONSIBILITIESand APPLSYS.FND_LOGIN_RESP_FORMS, respectively.

Refer to the Oracle Applications System Administrator's Guide for more information.

MONITOR SYSTEM ACTIVITY WITH OAM

Oracle Application Manager (OAM) provides screens for monitoring current and past system activity. In addi-

tion, OAM provides a framework extensible for running custom OAM reports. Monitoring features include cur-rent and historic user activity down to the page access level and current and historical Concurrent Manager

activity. See OAM documentation for complete product information.

Regarding Page Access Tracking, it tracks Oracle Applications usage statistics non-intrusively and with negligi-

ble performance impact. It tracks Web-based and Form-based accesses across technology stacks and correlates

them for each user session. SeeMetalink Note 402116.1for more detailed information about Page Access

Tracking.

RETRIEVE AUDIT RECORDS USING REPORTS

Oracle E-Business Suite ships standard reports to access signon, unsuccessful signon, responsibility usage, form

usage and concurrent request usage. Access these reports through the system administrator responsibility.

Signon Audit Concurrent Requests Signon Audit Forms

Signon Audit Responsibilities

Signon Audit Unsuccessful Logins

Signon Audit Users

Profile Option Name Description Recommend

SIGNONAUDIT:LEVEL Set at site-level to track actions starting when the user logs on. Form


33/68


25

RETRIEVE AUDIT RECORDS USING SQL

The system stores end-user access data in the following tables. Develop SQL scripts to query these tables to

generate reports.

APPLSYS.FND_LOGINS APPLSYS.FND_LOGIN_RESP ONSIBILITIES

APPLSYS.FND_LOGIN_RESP _FORMS

APPLSYS.FND_UNSUCCESSF UL_LOGINS

FND_CONCURRENT_REQUESTS

ICX.ICX_FAILURES

PURGE AUDIT RECORDS

Purge end-user access data using thePurge Signon Audit Data concurrent program. The current program purges

all audit records older than a user supplied date. Run this concurrent program between once a week and once a

month, retaining 30 to 90 days of records. This concurrent program purges the following tables:

FND_LOGIN_RESP_FORMS

FND_LOGIN_RESPONSIBILITIES

FND_LOGINS

FND_UNSUCCESSFUL_LOGINS

Purge concurrent request data using thePurge Concurrent Request and/or Manager Data concurrent program.

Run this concurrent program at least once a week and retain 14 to 90 days of records.

Periodically archive and truncate theF ND_SIGNON_xxxxtables.

REVIEW DATA TRACKED (NO REPORTS AVAILABLE)

Some data tracked by the system do not have a ssociated reports. Nevertheless, these audit records contain valu-

able information.

Who Columns

For most E-Business Suite tables, database rows are updated with the creation and last update information. The

system stores this information in the following columns (known as Who Columns):

Join with FND_USERS and FND_LOGINS tables to identify the application user tracked in the audit record.

Note, only the last update to record is saved. To save the entire history of a row, enable Oracle E-Business Suite

Audit Trail.

Who Column Name Description

CREATION_DATE Date and Time row was created

CREATED_BY Oracle Applications user ID from FND_USER

LAST_UPDATE_LOGIN Login ID from FND_LOGINS

LAST_UPDATE_DATE Date and Time row as last updated

LAST_UPDATED_BY Oracle Applications user ID from FND_USERS


34/68


26

Unsuccessful Logins

The system automatically stores unsuccessful logon attempts in the APPLSYS.FND_UNSUCCESSFUL_LOGINS

andICX.ICX_FAILUREStables. TheICX_FAILUREStable holds more information than the

FND_UNSUCCESSFUL_LOGINS. Both the FND_UNSUCCESSFUL_LOGINSand ICX_FAILURES tables contain

unsuccessful logins via the Personal Home Page (Self Service/Web Interface). Failed Forms logins are loggedonly to theFND_UNSUCCESSFUL_LOGINS table. This functionality cannot be disabled.

ADVANCED AUDIT

Oracle E-Business Suite implements its own auditing mechanisms, Audit Trails.

Auditing database row changes is performance intensive. Limit auditing to non-transactional data. Auditing

transactional data may cause significant performance degradation. Tables with more than a few changes an hour

should not be considered for row level auditing. Plan and c onsult with a DBA before enabling Audit Trails.

This feature keeps a complete history of changes made at a table a nd column level. When initialized, a concur-

rent program creates a shadow table and places triggers on the columns to be audited. The triggers store column

changes in the shadow table -- a table whose name is the instance tables name appended with _A.

CONFIGURING AUDIT TRAIL

To enable Audit Trail, follow these steps:

1. Set System profile optionAuditTrail: Activate to True

2. Navigate throughSecurity -> AuditTrail -> Installto set schemas for auditing

3. Navigate throughSecurity -> AuditTrail -> Groupsto create audit groups and set tables to be audited. Set

audit group to Enabled Requested

4. Navigate throughSecurity -> AuditTrail -> Tables to set columns in tables to be audited

5. RunAuditTrail Update Tables to activate auditing

GENERATE AND IDENTIFY AUDIT TRAIL OBJECTS

To create the shadow tables as explained in the auditing section above, run the AuditTrail Update Tablesconcur-

rent program, which activates auditing. This program creates triggers on each audited column in the original

table. In addition, it creates two views for each c olumn with the names _AC# and _AV# where # is a sequential

number.

Shadow Table =_A

Update Trigger =_AU

Insert Trigger =_AI

Delete Trigger =_AD

Changes View =_AV#

Complete View =_AC#

CHOOSE TABLES TO AUDIT

Consider auditing some of the tables that control system security.

ALR_ALERTS

FND_AUDIT_COLUMNS

FND_AUDIT_GROUPS

FND_AUDIT_SCHEMAS


35/68


27

FND_AUDIT_TABLES

FND_CONCURRENT_PROGRAMS

FND_DATA_GROUPS

FND_DATA_GROUP_UNITS

FND_ENABLED_PLSQL

FND_FLEX_VALIDATION

FND_FORM

FND_FORM_FUNCTIONS

FND_GRANTS

FND_MENUS

FND_MENU_ENTIRES

FND_ORACLE_USERID

FND_PROFILE_OPTIONS

FND_PROFILE_OPTION_VALUES

FND_REQUEST_GROUPS

FND_REQUEST_GROUP_UNITS

FND_RESP_FUNCTIONS

FND_USER_RESP_GROUPS

RETRIEVE AUDIT RECORDS USING SQL

Access Audit Trail records through SQL. Oracle does not ship Audit Trail reports. Use shadow tables and views

for accessing the records.

PURGE AUDIT RECORDS

Purge the audit trail information on a regular basis. Prior to purging, disable the Audit Trail.

Use the following procedure to purge audit data:

1. As System Administrator, selectSecurity -> Audit Trail -> Groups .

2. Select the Security Audit group and set the group state to Disable Purge Table.3. Run the Audit Trail Update Tables Report.

4. Purge the data from the shadow table.

5. SelectSecurity -> Audit Trail -> Groups .

6. Select the Security Audit group and set the group state to Enable.

7. Run the Audit Trail Update Tables Report

REFERENCES ON E-BUSINESS SUITE AUDITING

Oracle10gR2 Administrators Guide Auditing Database Use

Oracle Applications System Administrators Guide User and Data Auditing

Metalink Note 105624.1 Troubleshooting (Audit Trail)

Metalink Note 60828.1 Overview of Oracle Applications AuditTrails Metalink Note 69660.1 Understanding Data Auditing in Oracle Application Tables


36/68


28


37/68

Desktop Security

29

Desktop Security

This section contains security recommendations for the Desktop.

HARDENING

CONFIGURE BROWSER

SeeMetalink Note 389422.1Recommended Browsers for Oracle Applications 12.0 for information about

securing the desktop.

UPDATE BROWSER

Update browser when new versions are released; they often include new security features.

Check browser for built-in safety features.

When using Internet Explorer:

upgrade to at least Version 6.0.

check Microsoft website for the latest browser security patches (http://www.microsoft.com)

TURN OFF AUTOCOMPLETE IN INTERNET EXPLORER

For kiosk machines, change Internet Explorers autocomplete settings. IE can automatically show previous val-

ues entered in the same form field. Although desirable for frequently accessed pages, for privacy and security

reasons this feature should be disabled.

To turn OFF the Auto Complete feature:

1. Navigate throughTools->Internet Options-> Content

2. From theContenttab, click the AutoCompletebutton.

3. Uncheck "forms" and "User names and passwords on forms".

Also, do not use the "remember password" function; this is a known security vulnerability.

SET POLICY FOR UNATTENDED PC SESSIONS

People may attempt to access unattended workstation while the user is still logged into the system. The user

should never leave their workstation unattended while logged into the system because it makes the system

accessible to others who may walk up to the computer. Organizations should set a corporate policy for handling

unattended PC sessions. Users are recommended to use the password-locked screen savers feature on all PCs.

Web Browser

Forms applet,

DESKTOPTIER

Sun Java


38/68

Desktop Security

30


39/68

Operating Environment Security

31


The environment in which Oracle Applications run contributes to or detracts from overall system security. This

section contains security recommendations for tightening Oracle file system security along with more generaladvice for overall system hardening.

HARDENING

CLEANUP FILE OWNERSHIP AND ACCESS

1. The directory$ORACLE_HOME/bin contains Oracle executables. Check that the operating system owner of

these executables matches the operating system user under which the files have been installed. A typical

mistake is to install the executables in useroracles directory but owned byroot.

2. Check that the operating system user chosen as the owner of Oracle E-Business Suite owns all of the files in

the$APPL_TOP directory.

3. Prevent remote login to the Oracle (and root) accounts. Instead, require that legitimate users connect to their

own accounts andsu to the Oracle account. Better yet, use sudoto restrict access to executables. Find more

information aboutsudoat http://www.courtesan.com/sudo.

CLEANUP FILE PERMISSIONS

Refer to the product installation documentation for the complete instructions on setting file permissions.

On Unix systems:

1. Set the permissions on$ORACLE_HOME/binto 0751 or less. Set all other directories in $ORACLE_HOME to

0750 or less. Note, this limits access to the Oracle user and its groups (probably DBA).

2. Set file permissions forlistener.ora and sqlnet.orato 0600.

3. Set file permissions fortnsnames.orato 0644.

4. Ensure that the owner, group and modes of the Oracle files created upon installation are set to allow mini-mum privilege. The following commands make this change. Note, the group and owner are for illustration

only, the correct group and owner should be substituted.$chgrp -R $ORACLE_HOME$chown -R $ORACLE_HOME

5. Review owners and groups when cloning a database.

6. Protect the$ORACLE_HOME/rdbms/admindirectory including catalog.sql,catproc.sqland

backup scripts.

7. Secure scripts containing usernames and passwords.

8. Verify that set userid (SUID) and set group id (SGID) are not set on binaries. In general, Oracle recommends

that the SUID and SGID bits to be removed from binaries shipped by Oracle.

Warning:If Concurrent Manager runs on the Database tier and using the BEQ adapter to avoid TCP cost,

the SUID and/or SGID bit must be set on the Oracle database executable in $ORACLE_HOME/bin. This

may also apply for any third party products running on the db tier.

On windows systems, NTFS must be used. The FAT/FAT32 file system provides no security.


40/68


32

LOCKDOWN OPERATING SYSTEM LIBRARIES AND PROGRAMS

The database and applications require that the underlying operating system provide certain services.

1. X Server

a. Oracle Installer requires access to the X server which in turn may require access to an X font server.b. Application middle-tiers and web-tiers do not require an X server.

c. A production Database does not require access to an X server.

This means that there is no requirement to install X on any of the EBS servers if a remote X Display can be pro-

vided during installation.

2. Printers

Applications may require access to printers normally via the lpd interface on port 515/TCP. If possible,

restrict access to the operating system users who absolutely need the printing facility from the shell.

3. Electronic Mail

Applications may require access to a SMTP Mail Transfer Agent (SMTP MTA) typically sendmailor

qmailon port 25/TCP. This is required for outbound emails, typically notifications from the workflow sys-

tem. If possible, restrict access to the operating system users who absolutely need the mail facility from the

shell.4. Remote Access

Use secure shell (ssh) to access middle-tier and database hosts. This replaces telnet, rsh, rlogin, rcp and ftp.

Although not required by the E-Business Suite, the following services may provide operational convenience:

1. NTP (Network Time Protocol) for synchronizing the clock on the UNIX hosts to provide accurate audit

records and simplify trouble-shooting.

2. CRON for operating system cleanup and log file rotation

3. Monitoring agents for monitoring operating system, database and application components for health and

security

NETWORK

To secure the network, limit access to services users need and make those services as secure as possible. Dis-

abling unused services reduces securing and monitoring work.

FILTER IP PACKETS

IP filtering helps to prevent unwanted access. On the internet or large network, use a firewall machine or router

with firewalling capabilities.

A firewall machine sits between the internet and the intranet or the intranet and the internal servers. It provides a

point of resistance by protecting ins ide systems from external users. A firewall machine can filter packets and/or

be a proxy s erver. Firewalls may be software or hardware based. For software solutions, dedicate a machine to

be the firewall. Do not assume that using Network Address Translation (NAT) s ubstitutes for a firewall.

Filtering out unused services at the firewall or router level stops infiltration attempts earlier in the process.

Unless running NFS between networks, turn off all RPC ports on the router. Better yet, implement a default OFF

policy, opening only those ports known to be required.

On the host, create access control lists in/var/adm/inetd.secto limit which hosts can connect to the local

machine. Turn off unused services in /etc/inetd.conf.


41/68


42/68


34

Root, and only root, should have UID 0.

Check root .* files for security holes. The root .* files SHOULD have 700 or 600 permissions. The mini-

mal umask for root is 022 (rwxr-xr-x). A umask of 077 (rwx------) is best, but often not practical.

To avoid trojan horse programs, always use full pathnames including aliases. Root should NEVER have .

in path. NEVER allow non-root write access to any directories in root's path. If possible, do not create root's temporary files in publicly writable directories.

MANAGE USER ACCOUNTS

Do not share user accounts. Remove or disable user accounts upon termination. Disable login for well known

accounts that do not need direct login access (bin, daemon, sys, uucp, lp, adm). Require strong passwords and,

in some cases, a restricted shell.

DO NOT ALLOW GUEST ACCOUNTS

It is hard to imagine what kind of guests should have access to a production EBS system. For this reason do not

allow guest access.

AUTHORIZATION

SECURE NFS

Only run NFS as needed, apply latest patches. When creating the /etc/exports file, use limited access flags when

possible (such as readonlyornosuid). By using fully qualified hostnames, only the named host may access the

file system.

SECURE OPERATING SYSTEM DEVICES

Device files/dev/null,/dev/ttyand /dev/consoleshould be world writable but NEVER executable.

Most other device files should be unreadable and unwritable by regular users.

SECURE EXECUTABLES

Always get programs from a known source. Use a c hecksum to verify they have not been altered.

SECURE FILE ACCESS

Create minimal writable file systems (esp. system files/directories). Limit user file writes to their own directo-

ries and/tmp. Add directories for specific groups. Limit important file access to authorized personnel. Use set-

uid/setgid only where absolutely necessary.

MAINTENANCE

Good security practice does not end after installation. Continued maintenance tasks include:

Install the latest software patches.

Install latest operating system patches.

Verify user accounts - delete or lock accounts no longer required.

Run security software and review output.


43/68


35

Keep up to date on security issues by subscribing to security mailing lists, reading security news groups and

following the latest security procedures.

Implement trusted file systems like NIS, NIS+ or others such as HP-UX trusted system.

Test the system with tools like NESSUS (network security) and CRACK (password checker).

Install Tripwire to detect changes to files.

Monitor log files including btmp, wtmp, syslog, sulog, etc. Consider setting up automatic email or paging to

warn system administrators of any suspicious behavior. Also check the snort logs.


44/68


36


45/68

Extras for Experts

37

Extras for Experts

Security policy must balance risk of attack, cost of defense and value of data protected. This section contains

recommendations that improve security, but may not be appropriate for every deployment.

DETECT AND PREVENT DUPLICATE USER SESSIONS

When properly patched and configured, the E-Business Suite raises a Workflow event when the same user has

multiple, open sessions. A subscription attached to this event may take some action including closing the old

session under the same user name or sending an email notification to the administrator.

Patch 2128669 contains an example demonstrating how to write a custom event and/or additional subscriptions.

The subscription calls a rule function that updates the ICX_SESSIONS table setting the DISABLED_FLAG='Y'

for all other sessions for the user. This renders the other sessions invalid. The next user action returns the

browser to a login screen indicating the session is invalid. User names appearing in the subscription's parameter

list are excluded from this functionality.

This functionality is disabled by default.

CUSTOMIZE PASSWORD VALIDATION

To customize password validation create a Java class that implements theoracle.apps.fnd.secu-

rity.PasswordValidationJava interface. The interface requires three methods:

1. public boolean validate(String user, String password

This method takes a username and password, and returnsTrueorFalse, indicating whether the user's pass-

word is valid or invalid, respectively.

2. public String getErrorStackMessageName()

This method returns the name of the message to display when the user's password is deemed invalid (i.e., the

validate() method returnsFalse).3. public String getErrorStackApplicationName()

This method returns the application short name for the aforementioned error message.

After writing the customized password validator, set profile option SIGNON_PASSWORD_CUSTOMto the full

name of the class. If the name of the Java class is yourco.security.AppsPasswordValidation, then

the value ofSIGNON_PASSWORD_CUSTOMmust be "yourco.security.AppsPasswordValidation".

Note, this class must be loaded int o the Application database using theloadjavacommand.

ADVANCED SECURITY/NETWORKING OPTION (ASO/ANO)

Oracle Advanced Security provides a single source of integration with network encryption and authentication

solutions, single sign-on services, and security protocols. The option protects against threats to the security of

distributed environments. Specifically, Oracle Advanced Security provides the following features:

Data Integrity: Prevents data modification during transmission.

Data Privacy: Prevents data disclosure during transmission.

Authentication: Identifies users, hosts and clients securely and provides single sign-on.

Authorization: Ensure that a user, program, or process receives appropriate object access privileges.


46/68

Extras for Experts

38

Metalink Note 391248.1 provides more information on using ASO/ANO to encrypt your Oracle E-Business

Suite 11i network traffic.

CONFIGURE LISTENER ON A NON-DEFAULT TCP PORT

By default, the TNS Listener receives service requests on TCP port 1521. Configure it to listen on another port

number. Although not foolproof, this makes attacks more difficult.

HARDENING EXTERNAL PROCEDURE (EXTPROC) SERVICES

The Oracle database uses the external procedure service to call external C programs. This extends the function-

ality of PL/SQL to routines that can be written in C to perform complex calculations, such as mathematical

modeling or files system interactions. This functionality exploits the ability of the Listener to issue operating

system commands. The external procedures are supposed to issue the commands to the Listener on a special IPC

pipe named EXTPROC. The specification exists in thelistener.oraparameter file as

(ADDRESS_LIST = (ADDRESS = (PRTOCOL = IPC) (KEY = EXTPROC))

These external procedures operate by instructing the Listener to issue these operating system commands on their

behalf. Because the Listener runs with the privilege of the operating system user, the only limits on external pro-

cedures are the limits on what that account can do.

The following Oracle E-Business suite components use EXTPROC services:

1. Oracle Intermedia cartridges -- InterMedia needs to be installed with 11i.

2. Oracle Email Center.

3. Oracle Demand Planning Express implementation.

To protect against some EXTPROC attack vectors:

1. Create two Oracle TNS Listeners, one for the Oracle database and one for PL/SQL EXTPROC.

2. Remove EXTPROC specific entries from the Oracle Database Listener configuration files.

3. Configure the Oracle EXTPROC Listener with an IPC protocol address only.

If TCP connectivity is required, configure a TCP protocol address, but use a port other than the one the Ora-

cle Listener for the database is using. Ensure that the Oracle Listener created for PL/SQL EXTPROC runs as

an unprivileged operating system user (e.g., nobody on Unix). On Windows platforms, run the Oracle

TNS Listener process as an unprivileged user and not as the Windows LOCAL SYSTEM user. Give this

user the operating system privilege to Logon as a service.

4. If the Oracle Listener for PL/SQL EXTPROC has been configured with a TCP address, do the following:

a. Modify the EXTPROC specific entry in $ORACLE_HOME/network/admin/tnsnames.orato

reflect the correct port for the new Oracle Listener.

b. Enable Valid Node Checking and restrict access t o those network clients requiring EXTPROC.

c. Restrict access to the Oracle Listener for PL/SQL EXTPROC only. Use a separate$TNS_ADMIN/sql-

net.ora file for this Oracle Listener. Store this file in any directory other than the one in which the

database listener.oraand sqlnet.ora files are located. Copy the listener.orawith the con-

figuration of the Oracle Listener for PL/SQL EXTPROC into this other directory as well. Before startingthe Oracle Listener for PL/SQL EXTPROC, set the TNS_ADMINenvironment variable (or Windows

Registry parameter) to specify the directory in which the new configuration files for PL/SQL EXTPROC

are stored.

5. Ensure that the file permissions on separate$TNS_ADMIN/listener.oraare set to 600. Because it con-

tains the password, only the owner should read the file.

6. Change the password to a strong password for any privileged database account or an ordinary user given

administrative privileges in the database that has the ability to add packages or libraries and access system


47/68

Extras for Experts

39

privileges in the database (such as CREATE ANY LIBRARY). This step may not be applicable for default

E-Business Suite implementations. This may be useful for customizations that involve addition of new sche-

mas or customized PL/SQL code to be called as an external procedure service.

EXTPROC LISTENER CONFIGURATION

See below for the format of the dedicated EXTPROC Listener. The parameters appear in$ TNS_ADMIN/lis-

tener.ora. Replace the $ORACLE_SID with name of the Oracle database instance (SID),

$ORACLE_HOME with the value of ORACLE HOME directory for this Listener and $TNS_ADMIN with the

directory location of the Listener parameter files.

$ORACLE_SID_EXTPROC =(ADDRESS_LIST =

(ADDRESS= (PROTOCOL= IPC)(KEY= EXTPROC$ORACLE_SID)))

SID_LIST_$ORACLE_SID_EXTPROC =(SID_LIST =

(SID_DESC =(SID_NAME = PLSExtProc)(ORACLE_HOME = $ORACLE_HOME)

(PROGRAM = extproc))

)

STARTUP_WAIT_TIME_$ORACLE_SID_EXTPROC = 0CONNECT_TIMEOUT_$ORACLE_SID_EXTPROC = 10

TRACE_LEVEL_$ORACLE_SID_EXTPROC = OFF

LOG_DIRECTORY_$ORACLE_SID_EXTPROC = $TNS_ADMIN

LOG_FILE_$ORACLE_SID_EXTPROC = $ORACLE_SID_EXTPROCTRACE_DIRECTORY_$ORACLE_SID_EXTPROC = $TNS_ADMINTRACE_FILE_$ORACLE_SID_EXTPROC = $ORACLE_SID_EXTPROC

The configuration below should appear in $TNS_ADMIN/tnsnames.ora. Replace $ORACLE_SID with the

name of the Oracle database i nstance (SID).

extproc_connection_data =(DESCRIPTION=

(ADDRESS_LIST =

(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC$ORACLE_SID)))(CONNECT_DATA=

(SID=PLSExtProc)(PRESENTATION = RO)

) )

Example: EXTPROC Listener configured separately

This example shows how to configure EXTPROC Listener services. In it, the LISTENER NAME is

VSEC1159_EXTPROC and ORACLE_SID is VSEC1159.

VSEC1159_EXTPROC =

(ADDRESS_LIST =(ADDRESS= (PROTOCOL= IPC)(KEY= EXTPROCVSEC1159))


48/68

Extras for Experts

40

)

SID_LIST_VSEC1159_EXTPROC =(SID_LIST =

(SID_DESC =

(SID_NAME = PLSExtProc)(ORACLE_HOME = /u01/oracle/vsec1159db/9.2.0.5)

(PROGRAM = extproc))

)

STARTUP_WAIT_TIME_VSEC1159_EXTPROC = 0CONNECT_TIMEOUT_VSEC1159_EXTPROC = 10TRACE_LEVEL_VSEC1159_EXTPROC = OFF

LOG_DIRECTORY_VSEC1159_EXTPROC = /u01/oracle/vsec1159db/9.2.0.5/network/adminLOG_FILE_VSEC1159_EXTPROC = VSEC1159_EXTPROCTRACE_DIRECTORY_VSEC1159_EXTPROC = /u01/oracle/vsec1159db/9.2.0.5/network/adminTRACE_FILE_VSEC1159_EXTPROC = VSEC1159_EXTPROC

Example: The tnsnames.ora parameter that corresponds to EXTPROC Listener.

extproc_connection_data =

(DESCRIPTION=(ADDRESS_LIST =

(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROCVSEC1159))

)(CONNECT_DATA=

(SID=PLSExtProc)

(PRESENTATION = RO)) )

EXTPROC TESTING PROCEDURE

This section explains a procedure to test if EXTPROC is enabled. The EXTPROC Listener must be configured

and working for InterMedia option to run. Do the following to test whether InterMedia is working:

1. Create a user to work with InterMedia Text:

creat

Documents

Best Practices for Securing Oracle E-Business Suite Release 12