P. 1
EBS_SEC_1_0_0

EBS_SEC_1_0_0

|Views: 414|Likes:
Publicado por94050668

More info:

Published by: 94050668 on Apr 20, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

04/11/2013

pdf

text

original

Sections

  • Overview
  • SYSTEM WIDE ADVICE
  • KEEP SOFTWARE UP TO DATE
  • RESTRICT NETWORK ACCESS TO CRITICAL SERVICES
  • FOLLOW THE PRINCIPLE OF LEAST PRIVILEGE
  • MONITOR SYSTEM ACTIVITY
  • KEEP UP TO DATE ON LATEST SECURITY INFORMATION
  • UPDATED TECHNOLOGY STACK
  • MODIFIED DIRECTORY STRUCTURE
  • Oracle TNS Listener Security
  • HARDENING
  • HARDEN OPERATING ENVIRONMENT
  • NETWORK
  • ADD IP RESTRICTIONS OR ENABLE VALID NODE CHECKING
  • SPECIFY CONNECTION TIMEOUT
  • ENABLE ENCRYPTION OF NETWORK TRAFFIC
  • AUTHENTICATION
  • ENABLE TNS LISTENER PASSWORD
  • AUTHORIZATION
  • ENABLE ADMIN RESTRICTIONS
  • AUDIT
  • ENABLE TNS LISTENER LOGGING
  • Oracle Database Security
  • DISABLE XDB
  • REVIEW DATABASE LINKS
  • REMOVE OPERATING SYSTEM TRUSTED REMOTE LOGON
  • IMPLEMENT TWO PROFILES FOR PASSWORD MANAGEMENT
  • CHANGE DEFAULT INSTALLATION PASSWORDS
  • RESTRICT ACCESS TO SQL TRACE FILES
  • REMOVE OPERATING SYSTEM TRUSTED REMOTE ROLES
  • LIMIT FILE SYSTEM ACCESS WITHIN PL/SQL
  • LIMIT DICTIONARY ACCESS
  • REVOKE UNNECCESSARY GRANTS GIVEN TO APPLSYSPUB
  • CONFIGURE THE DATABASE FOR AUDITING
  • AUDIT DATABASE CONNECTIONS
  • AUDIT DATABASE SCHEMA CHANGES
  • AUDIT OTHER ACTIVITIES
  • AUDIT ADMINISTRATORS AND THEIR ACTIONS
  • REVIEW AUDIT RECORDS
  • MAINTAIN AUDIT RECORDS
  • SECURE AUDIT RECORDS
  • Oracle Application Tier Security
  • REMOVE APPLICATION SERVER BANNER
  • REMOVE UNNECESSARY DIRECTIVES
  • TURN OFF DIRECTORY INDEXING
  • UNLOAD APACHE AUTOINDEX MODULE
  • PREVENT SEARCH ENGINE INDEXING
  • PROTECT ADMINISTRATIVE WEB PAGES
  • DISABLE TEST PAGES
  • CONFIGURE LOGGING
  • E-Business Suite Security
  • STRIKE PASSWORDS FROM ADPATCH LOGS
  • SET WORKFLOW NOTIFICATION MAILER SEND_ACCESS_KEY TO N
  • SET TOOLS ENVIRONMENT VARIABLES
  • USE SSL (HTTPS) BETWEEN BROWSER AND WEB SERVER
  • USE EXTERNAL WEBTIER IF EXPOSING ANY PART OF EBS TO THE INTERNET
  • USE TERMINAL SERVICES FOR CLIENT-SERVER PROGRAMS
  • CHANGE PASSWORDS FOR SEEDED APPLICATION USER ACCOUNTS
  • CONSIDER USING SINGLE-SIGN-ON
  • TIGHTEN LOGON AND SESSION PROFILE OPTIONS
  • CREATE NEW USER ACCOUNTS SAFELY
  • CREATE SHARED RESPONSIBILITIES INSTEAD OF SHARED ACCOUNTS
  • CONFIGURE CONCURRENT MANAGER FOR SAFE AUTHENTICATION
  • ACTIVATE SERVER SECURITY
  • REVIEW GUEST USER RESPONSIBILITIES
  • REVIEW USERS WITH ADMINISTRATIVE RESPONSIBILITIES
  • LIMIT ACCESS TO SECURITY RELATED FORMS
  • LIMIT ACCESS TO FORMS ALLOWING SQL ENTRY
  • SET OTHER SECURITY RELATED PROFILE OPTIONS
  • RESTRICT RESPONSIBILITIES BY WEB SERVER TRUST LEVEL
  • SET SIGN-ON AUDIT LEVEL
  • MONITOR SYSTEM ACTIVITY WITH OAM
  • RETRIEVE AUDIT RECORDS USING REPORTS
  • RETRIEVE AUDIT RECORDS USING SQL
  • PURGE AUDIT RECORDS
  • REVIEW DATA TRACKED (NO REPORTS AVAILABLE)
  • ADVANCED AUDIT
  • CONFIGURING AUDIT TRAIL
  • GENERATE AND IDENTIFY AUDIT TRAIL OBJECTS
  • CHOOSE TABLES TO AUDIT
  • REFERENCES ON E-BUSINESS SUITE AUDITING
  • Desktop Security
  • CONFIGURE BROWSER
  • UPDATE BROWSER
  • TURN OFF AUTOCOMPLETE IN INTERNET EXPLORER
  • SET POLICY FOR UNATTENDED PC SESSIONS
  • Operating Environment Security
  • CLEANUP FILE OWNERSHIP AND ACCESS
  • CLEANUP FILE PERMISSIONS
  • LOCKDOWN OPERATING SYSTEM LIBRARIES AND PROGRAMS
  • FILTER IP PACKETS
  • PREVENT SPOOFING
  • ELIMINATE TELNET CONNECTIONS
  • ELIMINATE FTP CONNECTIONS
  • VERIFY NETWORK CONFIGURATION
  • MONITOR FOR ATTACKS
  • CONFIGURE ACCOUNTS SECURELY
  • LIMIT ROOT ACCESS
  • MANAGE USER ACCOUNTS
  • DO NOT ALLOW GUEST ACCOUNTS
  • SECURE NFS
  • SECURE OPERATING SYSTEM DEVICES
  • SECURE EXECUTABLES
  • SECURE FILE ACCESS
  • MAINTENANCE
  • Extras for Experts
  • DETECT AND PREVENT DUPLICATE USER SESSIONS
  • CUSTOMIZE PASSWORD VALIDATION
  • ADVANCED SECURITY/NETWORKING OPTION (ASO/ANO)
  • CONFIGURE LISTENER ON A NON-DEFAULT TCP PORT
  • HARDENING EXTERNAL PROCEDURE (EXTPROC) SERVICES
  • EXTPROC LISTENER CONFIGURATION
  • EXTPROC TESTING PROCEDURE
  • 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

Best Practices for Securing Oracle E-Business Suite Release 12

Oracle Corporation
Version 1.0.0

Latest version of this document available under Metalink Note 403537.1.

Revision History
Version 1.0.0 Release Date Feb 2007 Descriptions Initial version for Release 12, based on 11i version 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

ii

Best Practices for Securing Oracle E-Business Suite Release 12

Table of Contents

Overview...............................................................................................................................................................1
System Wide Advice Changes from 11i Hardening Network Authentication Authorization Audit Hardening Authentication Authorization Audit Hardening Authorization Audit Hardening Network Authentication Authorization Audit Advanced Audit Hardening Hardening Network Authentication Authorization Maintenance Detect and Prevent Duplicate User Sessions Customize Password Validation Advanced Security/Networking Option (ASO/ANO) Configure Listener on a Non-Default TCP Port Hardening External Procedure (EXTPROC) Services 2 3 5 5 6 7 8 9 9 10 12 15 16 16 17 18 19 22 24 26 29 31 32 33 34 34 37 37 37 38 38

Oracle TNS Listener Security...............................................................................................................................5

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

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

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

Desktop Security.................................................................................................................................................29 Operating Environment Security ........................................................................................................................31

Extras for Experts ...............................................................................................................................................37

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 ......................................................................47 Appendix 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

iii

Table of Contents iv .

Use this summary as a security reference guide or checklist.Security Checklist Security Checklist This section contains a summary of this document’s best practice suggestions and their page locations. Overview Keep software up to date Restrict network access to critical services Follow the principle of least privilege Monitor system activity Keep up to date on latest security information UPdated Technology Stack Modified Directory Structure 2 2 2 2 2 3 3 Oracle TNS Listener Security Harden operating environment Add IP restrictions or enable Valid Node Checking Specify connection timeout Enable encryption of network traffic Enable TNS Listener password Enable admin restrictions Enable TNS Listener logging 5 5 6 6 6 7 8 Oracle Database Security Harden operating environment Disable XDB Review database links Remove operating system trusted remote logon Implement two profiles for password management Change default installation passwords Restrict access to SQL trace files Remove operating system trusted remote roles Limit file system access within PL/SQL Limit dictionary access Revoke unneccessary grants GIVEN to APPLSYSPUB Configure the database for auditing Audit database connections Audit database schema changes Audit other activities Audit administrators and their actions Review audit records Maintain audit records 9 9 9 9 10 10 11 11 11 11 11 12 12 12 13 13 13 14 v .

Security Checklist Secure audit records 14 Oracle Application Tier Security Harden operating environment Remove application server banner Remove unnecessary directives Turn off directory indexing Unload Apache autoindex module Prevent search engine indexing Protect administrative web pages Disable test pages Configure logging 15 15 15 15 16 16 16 16 16 E-Business Suite Security Harden operating environment Strike passwords from adpatch logs Set Workflow notification mailer SEND_ACCESS_KEY to N Set Tools environment variables Use SSL (HTTPS) between browser and web server Use External webtier if exposing any part of EBS to the internet Use Terminal Services for client-server programs Change passwords for seeded application user accounts Consider Using Single-Sign-On Tighten logon and session profile options Create new user accounts safely Create shared responsibilities instead of shared accounts Configure Concurrent Manager for safe authentication Activate Server Security Review Guest user responsibilities Review users with administrative responsibilities Limit access to security related forms Limit access to forms allowing SQL entry Set other security related profile options Restrict responsibilities by web server trust level Set Sign-On audit level Monitor system activity with OAM Retrieve audit records using Reports Retrieve audit records using SQL Purge audit records Review data tracked (no Reports available) Configuring audit trail Generate and identify audit trail objects Choose tables to audit 17 17 18 18 18 18 18 19 20 20 20 20 20 20 22 22 22 22 22 23 24 24 24 25 25 25 26 26 26 vi .

Security Checklist Retrieve audit records using SQL Purge audit records References on E-Business Suite auditing 27 27 27 Desktop Security Configure browser Update browser Turn off AutoComplete in Internet Explorer Set policy for unattended PC sessions 29 29 29 29 Operating Environment Security Cleanup file ownership and access Cleanup file permissions Lockdown operating system libraries and programs Filter IP packets Prevent spoofing Eliminate telnet connections Eliminate ftp connections Verify network configuration Monitor for attacks Configure accounts securely Limit root access Manage user accounts Do Not Allow guest accounts Secure NFS Secure operating system Devices Secure executables Secure file access 31 31 32 32 33 33 33 33 33 33 33 34 34 34 34 34 34 Extras for Experts Detect and Prevent Duplicate User Sessions Customize Password Validation Advanced Security/Networking Option (ASO/ANO) Configure Listener on a Non-Default TCP Port Hardening External Procedure (EXTPROC) Services EXTPROC Listener Configuration EXTPROC Testing Procedure 37 37 37 38 38 39 40 vii .

Security Checklist 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 viii .

cost of security and value of the information protected. Covers account management. PORTAL_TOP. The last section “Extras for Experts” collects together advice that goes beyond the typical best practice. JRE_TOP. web pages. data files. a properly secured computing infrastructure is critical. etc. password management and other account related activities. HTML_TOP. authentication. Covers physical topology. we provide best practices (practical advice) for securing Oracle’s E-Business Suite. Each section contains advice spanning five categories: Hardening Network Authentication Authorization Audit Covers hardening the file system. PRODUCT_TOPS ORACLE HOME Tools In today’s environment. network security. We cover security for the Database and Listener. When securing the infrastructure. To that end. the E-Business Suite and individual desktops. on-going review and purging. JAVA_TOP. products and configuration. Covers configuration. We follow this with advice for hardening operating systems including a sample Linux hardening (in the Appendix). application middle-tier and database) and fall into five categories (hardening. administrative tools. a balance must be struck between risk of exposure.Overview Overview DESKTOP TIER Web Browser Forms applet Sun JRE APPLICATION TIER DATABASE TIER Apache Listener RDBMS ORACLE HOME iAS ORACLE HOME RDBMS Forms Discoverer TNS Listener Concurrent Manager Terminal Server APPL_TOP COMMON_TOP. Each organization determines its own correct balance. firewalls. programs. Covers restrictions to executables. IP restrictions at web server and database listener. authorization and auditing). The recommendations that follow cross three tiers of machines (browser. the Application Server. 1 .

Each component within a system has some degree of monitoring capability. grants. we assume an E-Business Suite maintenance level of 12. especially early on in an organization’s life cycle when people are few and work needs to be done quickly. In addition. a software/hardware VPN or Windows Terminal Services or its equivalent. roles. Throughout this document. User privileges should be reviewed periodically to determine relevance to current job responsibilities.0 or later. Restricting database access by IP address often causes application client/server programs to fail for DHCP clients.. To resolve this. If firewalls cannot be used. 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. Check this note yearly for revisions. etc. MONITOR SYSTEM ACTIVITY System security stands on three legs: good security protocols. Auditing and reviewing audit records address this third requirement. The firewalls provide assurance that access to these systems is restricted to a known network route. 2 . for many reasons including good security practice. place a firewall between the middle-tier and the database. It also contains a patch set checker to assist with patch application. proper system configuration and system monitoring. KEEP UP TO DATE ON LATEST SECURITY INFORMATION Oracle continually improves its software and documentation.Overview SYSTEM WIDE ADVICE Some advice applies to the entire E-Business deployment and the infrastructure in which it operates. move to the latest version of Autoconfig and Patch Tools (AD). The latest version of Autoconfig (TXK) configures a system following advice from this document. be certain to configure the TNS Listener Valid Node Checking feature which restricts access based upon IP address. RESTRICT NETWORK ACCESS TO CRITICAL SERVICES Keep both the E-Business application middle-tier and the database behind a firewall. independent firewalls.0. KEEP SOFTWARE UP TO DATE One of the principles of good security practice is to keep all software versions and patches up to date. often leaves a system wide open for abuse. a firewall router substitutes for multiple. consider using static IP addresses. This cannot be emphasized enough. if necessary. As an alternative. which can be monitored and restricted. Follow audit advice in this document and regularly monitor audit records.

0.1.0.1.2 (1.0. UPDATED TECHNOLOGY STACK Release 12 has updated the entire technology stack.2.2.2 Reports 10.0 JRE for Form applet: Sun JRE 1. modplsql is no longer required in Release 12 and is not configured b.0.0_8 a.x) Application Tier IAS 1. From a security perspective the most interesting point is the introduction of the INSTANCE_TOP which is a new directory that contains instance specific configuration files and log files.1. ReportWriter10 is only called from Concurrent Managers in Release 12 (no longer invocable via the web interface) MODIFIED DIRECTORY STRUCTURE Release 12 has changed the way the file systems are organized. 11i Database 9iR2 (9.Overview 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. This provides a cleaner separation of code directories and directories with instance specific and variable data.3 JDBC 10.2 Java Oracle_home: 10.4 JDBC 9 or 10 Desktop Tier JRE for Forms applet: Oracle Jinitiator Release 12 10gR2 (10.1.0.34 fork) oc4j -eliminated-a Forms 10.2.0) Fusion Middle Ware OHS 10.6 IAS Oracle_home: 8.2.3.2.7. the table below summarizes the changes in versions and highlights retired technology pieces.2.2 + Developer 6i OHS 1.3 (1.0.1.2.5.3. See the “Oracle Application Concepts” guide from the installation DVD for more detail.1.0.19 fork) jserv modplsql Forms 6i Reports 6i Tools Oracle_home: 8.2b Tools Oracle_home: 10.2. 3 .

Overview 4 .

X. set the following parameters in $TNS_ADMIN/sqlnet.1: Using AutoConfig to Manage System Configurations with Oracle Applications Release 12 .X. For more information. HARDENING HARDEN OPERATING ENVIRONMENT Follow the hardening instructions for “Operating Environment Security” on page 31.X.X. ADI from a windows desktop is not recommended. This section contains security recommendations for the TNS Listener.Oracle TNS Listener Security Oracle TNS Listener Security DATABASE TIER Listener RDBMS ORACLE HOME RDBMS Oracle clients communicate with the database using the Transparent Network Substrate (TNS) protocol. Use a static IP address. To enable Valid Node Checking for 9i and above. .validnode_checking = YES tcp. .. 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. X.. NETWORK ADD IP RESTRICTIONS OR ENABLE VALID NODE CHECKING Valid Node Checking allows or denies access from specified IP addresses to Oracle services. If implemented.or the Oracle Applications 5 .X. hostname..X. ) tcp. discoverer. refer to Metalink Note 387859. Middle-tier applications include web servers. by default).ora: tcp. concurrent managers. When the Listener receives a connection request (tcp port 1521. use of SQLNet clients such as sqlplus. AutoConfig supports automated configuration.invited_nodes = ( X. ) The first parameter turns on Valid Node Checking.. toad. Replace X.X. central administrator machines and any remote monitoring tool that uses SQLNet. it starts up a new database process and establishes a connection between the client and the database. forms servers.X with the middle-tiers’ IP addresses.excluded_nodes = ( hostname. Note.X. that desktop cannot use DHCP. terminal servers.

set the following parameter: CONNECT_TIMEOUT_$ORACLE_SID = 10 For example.2. MetaLink note 391248. secure password Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=dbs01)(PORT=1541))) Password changed for VIS12 The command completed successfully LSNRCTL> set password Password: The command completed successfully LSNRCTL> save_config Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=dbs01)(PORT=1541))) Saved DBLSNR configuration parameters.just hit return New password: -.0/network/admin/VIS12_dbs01/listener. Listener Parameter File /x/db/tech_st/10.ora.new. Start the Listener control program: $ lsnrctl Set the current Listener in case you have more than one listener defined. CONNECT_TIMEOUT_VIS12 = 10 Where VIS12 is the value of the ORACLE_SID in this example. AUTHENTICATION ENABLE TNS LISTENER PASSWORD Setting a password for the Listener is one of the most important hardening procedure. then change the password.ora parameters is relevant also for Release 12. secure password Reenter new password: -.ora 6 . LSNRCTL> set current_listener VIS12 Current Listener is VIS12 LSNRCTL> change_password Old password: -. Use the parameter CONNECT_TIMEOUT to specify the amounts of time. 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.new. SPECIFY CONNECTION TIMEOUT In $TNS_ADMIN/listener.1 contains the instructions on how to do this for 11i . for the Oracle Listener to wait for the connection from a client to complete.the setting of sqlnet. These instructions assume that the listener name is VIS12. The default for oracle databases in general is “LISTENER” while for EBS databases it is set to the SID of the database.Oracle TNS Listener Security Concepts manual. in seconds. AutoConfig enabled systems may use the latest OAM minipack to implement the manual steps highlighted above.

ADMIN_RESTRICTIONS_VIS12=ON Where VIS12 is the name of the listener (equal to ORACLE_SID in EBS) 7 . ensure that file and directory settings can only be changed by editing the listener. Edit listener.ora and remove the lines PASSWORDS_<listener> and ADMIN_RESTRICTIONS_<listener> 2. Enable ADMIN_RESTRICTIONS by adding the following line to listener.ora and reload the configuration file into the Listener: $ echo "ADMIN_RESTRICTIONS_VIS12 = ON" >> listener. check status or run services on remote machines via lsnctrl.ora. Use Enterprise Manager for remote administration. The Listener process requires a password to list SERVICES or STATUS. Stop the tnslsnr process (using lsnrctl or use ps to find the pid and kill to kill it) 3.Oracle TNS Listener Security The command completed successfully This added the following lines to listener. Cannot start.ora LSNRCTL> set current_listener VIS12 Current Listener is VIS12 LSNRCTL> set password Password: The command completed successfully LSNRCTL> reload Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=dbs01)(PORT=1541))) The command completed successfully With these settings. if they do not expect to provide a password. password protecting the TNS Listener has the following effects: Οnly the oracle user can stop the TNS Listener using lsnrctl without providing the password. Restart the listener (using lsnrctl start) Note. AUTHORIZATION ENABLE ADMIN RESTRICTIONS In $TNS_ADMIN/listener.ora: #----ADDED BY TNSLSNR 13-JAN-2007 11:47:56--PASSWORDS_VIS12 = D911537D50B15546 #-------------------------------------------- With the Listener password protected. the Listener configuration file cannot be changed via the tnslsnr process. This breaks some monitoring and remote administration tools. stop. set the following parameter: ADMIN_RESTRICTIONS_<listener>=ON For example. To undo these steps: 1.ora file (not via set commands in lsnrctl).

LOG_STATUS = ON LOG_DIRECTORY_VIS12 = /u/db/tech_st/10.0/network/admin/VIS12_dbs01 LOG_FILE_VIS12 = VIS12 Where VIS12 is the LISTENER_NAME. 8 . Because password restrictions are enabled. AUDIT ENABLE TNS LISTENER LOGGING To enable logging.2. when ADMIN_RESTRICTIONS is ON. all the set commands in lsnrctl are disabled and the only way to change the configuration is to edit the listener.ora file. in $TNS_ADMIN/listener.ora set the following parameters: LOG_STATUS = ON LOG_DIRECTORY_$ORACLE_SID = $TNS_ADMIN LOG_FILE_$ORACLE_SID = $ORACLE_SID For example. some remote administration tools may subsequently fail.Oracle TNS Listener Security Note.

Oracle E-Business Suite does not require these services. Some individuals (IT Administrators) may require direct access to the application database via their own schema.dispatchers='(PROTOCOL=TCP) (SERVICE=sidXDB)' REVIEW DATABASE LINKS Review database links in both production and development environments. REMOVE OPERATING SYSTEM TRUSTED REMOTE LOGON This setting prevents the database from using an insecure logon protocol. HARDENING HARDEN OPERATING ENVIRONMENT Follow the hardening instructions for “Operating Environment Security” on page 31. the TNS Listener process listens on two additional TCP ports: 2100 for ftp access and 8080 for http access. DISABLE XDB To support XDB. To disable XDB. remove or comment out the line in init. Make sure init. they should be disabled.ora contains: REMOTE_OS_AUTHENT=FALSE 9 . AUTHENTICATION Middle-tier applications logon to the database through application schemas rather than end-user accounts.Oracle Database Security Oracle Database Security DATABASE TIER Listener RDBMS ORACLE HOME RDBMS This section contains security recommendations for the Database.ora that reads *.

“Appendix C: Database Schemas Shipped with E-Business Suite” on page 47 contains a list of the schemas by category. Because of this.Oracle Database Security IMPLEMENT TWO PROFILES FOR PASSWORD MANAGEMENT The database provides parameters to enforce password management policies. 5 and 6. instructions and notes for managing schema passwords. run the AD adutconf. Default schemas come from different sources: 1. category six (6) schema passwords may be changed en masse using FNDCPASS. 5. 2 and 3. For the schemas in categories 4. and they should be changed. use the application password change tool: $ FNDCPASS APPS/<apps_pwd> 0 Y SYSTEM/<system_pwd> ORACLE <SCHEMA> <NEW_PWD> To save time. use standard database commands to change a password: SQL> alter user <SCHEMA> identified by <NEW_PASSWORD>. the application database instance contains default. 10 . For more information on profiles. see CREATE PROFILE in the Oracle SQL Reference documentation. 4. However. 5 and 6).sql script. 2. especially for a database to be used in a production environment. 3. we make specific recommendations for or against using certain management features depending upon schema type. $ FNDCPASS APPS/<apps_pwd> 0 Y SYSTEM/<system_pwd> ALLORACLE <NEW_PWD> To determine which schemas are managed by E-Business Suite (categories 4. Password Parameters FAILED_LOGIN_ATTEMPTS PASSWORD_LIFE_TIME PASSWORD_REUSE_TIME PASSWORD_REUSE_MAX PASSWORD_LOCK_TIME PASSWORD_GRACE_TIME PASSWORD_VERIFY_FUNCTION Application Profile UNLIMITED UNLIMITED Administrator Profile 5 90 180 UNLIMITED 180 UNLIMITED UNLIMITED UNLIMITED 7 14 Recommended Recommended Database profiles contain limits on database resources and password policies. These accounts and corresponding passwords are well-known. 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. FNDCPASS accepts a keyword ALLORACLE forcing a change of all managed (category 6) schemas to the new password. CHANGE DEFAULT INSTALLATION PASSWORDS Following an installation. 6. Patch 4926128 contain a SQL script that will list all open accounts with default password in your database. some of the database password policy parameters could lock-out the E-Business Suite. Default database administration schemas Schemas belonging to optional database features neither used nor patched by E-Business Suite Schemas belonging to optional database features used but not patched by E-Business Suite Schemas belonging to optional database features used and patched by E-Business Suite Schemas common to all E-Business Suite products Schemas associated with specific E-Business Suite products For the schemas in categories 1. open schemas with default passwords.

<dir3>.Oracle Database Security AUTHORIZATION RESTRICT ACCESS TO SQL TRACE FILES The init. REMOTE_OS_ROLES=FALSE LIMIT FILE SYSTEM ACCESS WITHIN PL/SQL The parameter UTL_FILE_DIR limits file system access for all database accounts using the PL/SQL API UTL_FILE. 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 the APPLSYSPUB schema.sql.<dir2>. 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_SESSIONS INSERT ON FND_UNSUCCESSFUL_LOGINS SELECT ON FND_APPLICATION SELECT ON FND_APPLICATION_TL SELECT ON FND_APPLICATION_VL SELECT ON FND_LANGUAGES_TL 11 . UTL_FILE_DIR = <dir1>. Avoid: UTL_FILE_DIR = * LIMIT DICTIONARY ACCESS Set O7_DICTIONARY_ACCESSIBILITY to False to prevent users with Select ANY privilege from reading data dictionary tables. These are set in <FND_TOP>/admin/sql/afpub. Set this to its default value of False.ora parameter REMOTE_OS_ROLES to False to prevent insecure remote roles.ora parameter _TRACE_FILES_PUBLIC grants file system read access to anyone who has activated SQL tracing. Oracle E-Business Suite maintains some disk files and needs this parameter set.. _TRACE_FILES_PUBLIC=FALSE REMOVE OPERATING SYSTEM TRUSTED REMOTE ROLES Set the init..

ora. CONFIGURE THE DATABASE FOR AUDITING In init. In addition. whether or not AUDIT_TRAIL is enabled.Oracle Database Security APPLSYSPUB SELECT ON FND_LANGUAGES_VL SELECT ON FND_LOOKUPS SELECT ON FND_PRODUCT_GROUPS SELECT ON FND_PRODUCT_INSTALLATIONS To check permissions. By auditing database sessions. login as SYSTEM and issue the following query: SELECT * FROM dba_tab_privs WHERE grantee ='APPLSYSPUB'. To audit sessions. OS or TRUE. Note. the database stores its audit records on the file system: AUDIT_TRAIL = OS Set parameter AUDIT_FILE_DEST to the directory where the audit records should be stored. AUDIT DATABASE SCHEMA CHANGES Audit any changes to the standard Oracle E-Business Suite database schemas or creation of new schemas. AUDIT_FILE_DEST defaults to $ORACLE_HOME/rdbms/audit. you should understand the implications of privileges on custom objects granted to PUBLIC or a role. Release 12 Rapid Install has a clean APPLSYSPUB by default. set AUDIT_TRAIL to DB. these changes may indicate inappropriate or malicious activity. For example. Consult with the Applications Database Administrator before setting this value to TRUE. When set to OS. AUDIT This section describes the auditing capabilities available in Oracle database for Oracle E-Business Suite. 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. Oracle automatically creates an operating system file as an audit record when a user logs in as SYSDBA or as INTERNAL. suspicious connections to highly privileged schemas may be identified. see patch 3763612. the database generates some audit records by default. To revoke unnecessary privileges granted to APPLSYSPUB schema. 12 . As rare events. AUDIT_FILE_DEST = /u01/logs/db/audit Restart the database for these parameters to take effect. login through sqlplus as SYSTEM and issue the following command: SQL> audit session. the database places audit records in directory /u01/logs/db/audit. When not set. In this example. These recommendations should not have a measurable performance impact. password guessing attacks on an application schema).

AUDIT OTHER ACTIVITIES To complete the recommended auditing. PROFILE by ACCESS. The owner of the object that the user touched. Oracle E-Business Suite dynamically creates. If AUDIT_TRAIL is set to DB. etc. review audit records stored in the file name in AUDIT_FILE_DEST. enable three other audit events: create database link. 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. Auditing these other actions provides little meaningful information. This file contains the operating system user and terminal ID. ALTER SYSTEM by ACCESS. DROP ANY ROLE by ACCESS. ALTER DATABASE by ACCESS. login through sqlplus as SYSTEM and issue the following command: SQL> audit user.Oracle Database Security To audit schema changes. SYSTEM GRANT by ACCESS. login through sqlplus as SYSTEM and issue the following commands: SQL> SQL> SQL> SQL> SQL> SQL> SQL> SQL> SQL> SQL> SQL> SQL> SQL> AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT DATABASE LINK. index. The remaining audit options generate significant entries of little value. -------------Audit Audit Audit Audit Audit Audit Audit Audit Audit Audit Audit Audit Audit create or drop database links create or drop public database links statements themselves alter any role statements alter database statements alter system statements create role statements drop any role statements changes to profiles public synonyms statements SYSDBA privileges SYSOPER privileges System grant privileges AUDIT ADMINISTRATORS AND THEIR ACTIONS Connections to the database as well as SYSDBA and SYSOPER actions (instance startup/shutdown) are always logged to the directory $ORACLE_HOME/rdbms/audit. REVIEW AUDIT RECORDS If AUDIT_TRAIL is set to OS. packages. ALTER ANY ROLE by ACCESS.) on a regular basis. PUBLIC SYNONYM by ACCESS. The name of the object that the user touched. SYSTEM AUDIT. alter system and system audit.AUD$ table. retrieve audit records from the SYS. CREATE ROLE by ACCESS. PUBLIC DATABASE LINK. SYSDBA by ACCESS. alters and drops objects (tables. Time the action occurred. 13 . begin by focusing on the following: Username Terminal Timestamp Object Owner Object Name Oracle Username. SYSOPER by ACCESS. Machine from which the user originated. To audit the last three events.

Backup the audit file before purging. The database connection entries take up significant space. SELECT. MAINTAIN AUDIT RECORDS Archive and purge the audit trail on a regular basis. UPDATE.Oracle Database Security Action Name The action that occurred against the object (INSERT. Restrict audit trail access appropriately. DELETE. 14 . SECURE AUDIT RECORDS Audit data may contain confidential or privacy related data. at least every 90 days. EXECUTE).

remove or comment out references to documentation directories and other directives not needed to operate the application. Reduce access to non-application related areas. potentially finding a file that may be of use in their quest to access the system.Oracle Application Tier Security Oracle Application Tier Security APPLICATION TIER Apache OC4J ORACLE HOME iAS This section contains security recommendations for the Application Server. turn off the banner in httpd.conf: Set ServerSignature off Set ServerTokens Prod REMOVE UNNECESSARY DIRECTIVES If not using Autoconfig.htm or similar file available. Comment following in httpd.conf TURN OFF DIRECTORY INDEXING There are two goals when protecting a web server: Reduce the amount of information available. Disabling this entry prevents an intruder from viewing the files in a directory.conf configuration files and comment out the following line: # IndexOptions FancyIndexing 15 . REMOVE APPLICATION SERVER BANNER To avoid exposing Apache version and enabled modules.conf and ${IAS_ORACLE_HOME}/Apache/ Apache/conf/httpd_pls. HARDENING HARDEN OPERATING ENVIRONMENT Follow the hardening instructions for “Operating Environment Security” on page 31. In addition to any example or sample directories. Directory indexes display the contents of a directory if there is not an index. The quickest way to disable this feature is to modify ${IAS_ORACLE_HOME}/Apache/Apache/conf/httpd. use the following guidelines to remove unnecessary Apache directives.

allow Deny from all Allow from localhost <list of TRUSTED IPs> </Location> DISABLE TEST PAGES Add the following directives in httpd.org/wc/robots. 16 .unconfigure fast-cgi.conf and include it in the httpd. This new file contains the following content.conf.*$"> Order deny.conf file. it is not required by Release 12. as is done by default. To disable the module in httpd.c PREVENT SEARCH ENGINE INDEXING For internet facing web servers. These pages offer information about various services. these pages must be restricted or disabled in a production system. See http://www. the server logs data about all web access to the system. AUDIT CONFIGURE LOGGING Oracle Application Server respects Apache’s logging parameters. a number of web pages provide administrative and testing functionality. AUTHORIZATION Within Oracle Application Server. #LoadModule autoindex_module libexec/mod_autoindex. the server’s state and its configuration.Oracle Application Tier Security UNLOAD APACHE AUTOINDEX MODULE This module automatically generates directory indexes. When activated.conf to limit web page access to a list of trusted hosts. PROTECT ADMINISTRATIVE WEB PAGES Use the configuration file httpd.conf to prevent access fast-cgi test pages: <Location ~ "^/fcgi-bin/echo. Replace “uri-to-protect” with the path of the page you wish to protect Replace <list of TRUSTED IPs> with host machines from which administrators may connect.allow Deny from all </Location> Or better yet . enable robot exclusion. While useful for debugging.robotstxt. <Location "uri-to-protect"> Order deny.html for more information. This may be done either with a robots. To do this.so #AddModule mod_autoindex. create a file trusted.txt file or using a META tag. comment these lines as follows.

use the following flag: adpatch flags=hidepw 17 . PRODUCT_TOPS ORACLE HOME Tools This section contains security recommendations for the Oracle E-Business Suite.E-Business Suite Security E-Business Suite Security APPLICATION TIER DATABASE TIER Apache OC4J Listener RDBMS ORACLE HOME iAS ORACLE HOME RDBMS Forms Discoverer TNS Listener Concurrent Manager Terminal Server APPL_TOP COMMON_TOP. PORTAL_TOP. JAVA_TOP. JRE_TOP. HARDENING HARDEN OPERATING ENVIRONMENT Follow the hardening instructions for “Operating Environment Security” on page 31. HTML_TOP. STRIKE PASSWORDS FROM ADPATCH LOGS To stop adpatch from logging passwords.

env Form Environment Variable FORMS_RESTRICT_ENTER_QUERY Value TRUE NETWORK USE SSL (HTTPS) BETWEEN BROWSER AND WEB SERVER Information sent over the network and across the Internet in clear text may be intercepted. In Release 12 the forms parameters are set in the configuration file: /x/inst/apps/VIS12_dbs01/ora/10.1. browser sessions connect to middle-tier servers running Oracle 10g Application Server. refer to Oracle Workflow Administrator's Guide. you should consult MetaLink Note 380490. For information on setting up SSL with the Oracle E-Business Suite. URL firewall and reverse proxies in a secure external EBS deployment. refer to 376700. external responsibilities. 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.2/forms/server/default. When set to N. an unauthenticated user who clicks on the notification link must sign on before accessing the Notification Details web page. external web-tiers. SET TOOLS ENVIRONMENT VARIABLES Prevent forms users from using the enter-query feature on a production system. A majority of the E-Business Suite architecture supports this through a three-tier architecture.1 “Enabling SSL for Oracle Applications Release 12”. The key allows the user to access the Notification Details web page directly without authenticating. 18 . email notifications contain an access key.E-Business Suite Security SET WORKFLOW NOTIFICATION MAILER SEND_ACCESS_KEY TO N When SEND_ACCESS_KEY is set to Y. the workflow notification email bypasses the E-Business Suite sign-on process. Secure Sockets Layer (SSL) is an encryption scheme that negotiates an exchange of encryption keys. USE TERMINAL SERVICES FOR CLIENT-SERVER PROGRAMS Deploy components requiring direct connection to the E-Business Suite database on servers rather than on enduser desktop machines. This document describes the role of DMZs. Set SEND_ACCESS_KEY to N to prevent inclusion of the key with the Notification Detail link.1 for our best practice advice for deploying external EBS products to the internet. These keys are packaged in Certificates issued by a Certificate Authority (CA). deploy a remote server environment based on Windows Server Terminal Services. For more information. If you have a well considered need to connect to the database directly from a desktop. Citrix or Tarantella.

Account AME_INVALID_APPROVER ANONYMOUS APPSMGR ASGADM ASGUEST AUTOINSTALL CONCURRENT MANAGER FEEDER SYSTEM GUEST IBE_ADMIN IBE_GUEST IBEGUEST IEXADMIN INITIAL SETUP IRC_EMP_GUEST IRC_EXT_GUEST MOBILEADM OP_CUST_CARE_ADMIN OP_SYSADMIN STANDALONE BATCH PROCESS SYSADMIN WIZARD XML_USER Product / Purpose AME WF migration 11.E-Business Suite Security While deploying the required applications development and/or production runtime tools on Terminal Services. b. configure SQLNet Valid Node Checking and Application Server Security. These both prevent end-user desktops from connecting to the production database instance. Required for iStore.10 FND/AOL – Anonymous for non-logged users Routine maintenance via concurrent requests Mobile gateway related products Sales Application guest user AD FND/AOL: Concurrent Manager AD – Supports data from feeder system Guest application user iSupport Admin user iSupport Guest user iSupport Guest user Internet Expenses Admin AD iRecruitment Employee Guest Login iRecruitment External Guest Login Mobile Applications Admin Customer Care Admin for Oracle Provisioning OP (Process Manufacturing) Admin User FND/AOL Application Systems Admin AD – Application Implementation Wizard Gateway Change Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Disable Y Y Y Ya Yb Y Y Y N Yc Yc Yc Y Y Y Y Y Y Y Y N Y Y a. some seeded accounts may be disabled. 19 . c. Register the terminal server used to deploy the client/server components as a Managed SQLNet Access node. Do not disable SYSADMIN or GUEST user accounts. Change the default passwords immediately. Required for Mobile Sales. AUTHENTICATION CHANGE PASSWORDS FOR SEEDED APPLICATION USER ACCOUNTS Oracle ships seeded user accounts with default passwords. Service.5.9 to 11. and Mobile Core Gateway components. You disable an application user account by setting the END_DATE for the account. Required for Sales Application. Depending on product usage.5. Further details are provided in section “Add IP restrictions or enable Valid Node Checking” on page 5 and “Activate Server Security” on page 20. The former isolates SQLNet access to the Terminal Server and the latter identifies the terminal server to applications.

UMX uses workflow to drive the registration process once a request has been submitted. CONFIGURE CONCURRENT MANAGER FOR SAFE AUTHENTICATION Concurrent Manager passes the APPS schema password to concurrent programs on the command line. the password may be intercepted. To prevent username/password from being passed. the system cannot identify which user performs a function.1 “Integrating Oracle E-Business Suite Release 12 with Oracle Internet Directory and Oracle Single Sign-On”. 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. CREATE SHARED RESPONSIBILITIES INSTEAD OF SHARED ACCOUNTS When users share one account. Discoverer. enter SECURE in the Execution Options field. refer to Metalink Note 376811. while the system tracks individual user actions. Because some Operating Systems allow all machine users to read a program’s command line arguments. With this change. Any program which makes a SQLNet connection to the Oracle Applications database needs to be trusted at some level. Forms. the profile option settings below support strong passwords. account lockout after too many failed logons and session inactivity timeout. preventing accountability. The Server Security feature ensures that SQLNet connections originate from trusted machines. This setting is affected by the autoconfig variable “s_appserverid_authentication”.E-Business Suite Security CONSIDER USING SINGLE-SIGN-ON Oracle E-Business Suite Release 12 support integration with a Single Sign-On (SSO). Enter ENCRYPT in the Execution Options field of the Concurrent Programs window when defining a concurrent program using this executable. Concurrent Manager leaves argument $1 blank. The application servers include Apache JSP/Servlet. ENCRYPT signals Concurrent Manager to pass the username/password in the environment variable FCP_LOGIN. define the concurrent program executable as a HOST program in the Concurrent Program Executable form. Users share the same functions or permission sets. See UMX Documentation for more details. Profile Option Name SIGNON_PASSWORD_LENGTH SIGNON_PASSWORD_HARD_TO_GUESS SIGNON_PASSWORD_NO_REUSE ICX_SESSION_TIMEOUT Recommendation 8 YES 180 30 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. TIGHTEN LOGON AND SESSION PROFILE OPTIONS For local application users. To prevent this. 20 . Concurrent Manager does not pass the username/password to the program. Setup Server Security The application server security feature is activated by default. For more information on Single Sign-On deployments.

Appropriate for machines completely under an administrator’s control. Deleting Server IDs jre oracle.dbc file contains the Application Server’s ID. AdminAppServer synchronizes the server IDs found in the .dbc file. ON SECURE Recommended.dbc file: jre oracle. If the APPL_SERVER_ID argument is not provided.AdminAppServer apps/<apps-passwd> \ AUTHENTICATION ON DBC=<dbc file path> 21 . Administering Server Security.security. For details.fnd. Server and code IDs are not checked. The program adds them to the database automatically when the AdminAppServer is used to create a .AdminAppServer apps/<apps-passwd> \ DELETE DBC=<dbc file path> Server Security Activation To activate basic server security from the command line (ON mode): jre oracle.E-Business Suite Security Application Server Security has three states: OFF Inactivates Server Security.fnd. 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. The . only registered application servers and trusted code modules may connect. Equivalent to OFF from a security perspective.AdminAppServer apps/<apps-passwd> \ ADD [SECURE_PATH=$FND_TOP/secure] \ DB_HOST=<database host> \ DB_PORT=<database port> \ DB_NAME=<database sid> See the section on Creating DBC files in Administering Oracle Applications Security in Release 11i for more details.fnd. Use the AdminAppServer utility to generate server IDs and register them with a database.apps.dbc file with the database automatically.AdminAppServer apps/<apps-passwd> \ UPDATE DBC=<dbc file path> APPL_SERVER_ID Providing the APPL_SERVER_ID argument forces a new ID to be generated and added to the . Not recommended for production systems. see System Administrators Guide.apps. Updating Server IDs jre oracle. OK for development systems without production data. Adding Server IDs Register application servers as trusted machines with a database server.security.apps.security.security.apps.fnd.

Profile Option AuditTrail:Activate Concurrent:Report Access Level FND:Diagnostics Sign-on:Notification Utilities:Diagnostics Yes User No Yes No Suggest 22 . These forms are typically used during the initial setup of the system. “Appendix A: Security Setup Forms” on page 43 contains a list of forms that allow security setup. the SYSADMIN responsibility has broad administrative privileges.security. LIMIT ACCESS TO SECURITY RELATED FORMS Some forms allow users to modify the E-Business Suite security setup. Review these responsibilities from time to time. Consider auditing the database tables listed in the appendix. Assign users only those responsibilities necessary for them to perform their tasks. SET OTHER SECURITY RELATED PROFILE OPTIONS Refer to the table below and set the suggested values for the profile options.apps.apps.fnd.AdminAppServer apps/<apps-passwd> \ AUTHENTICATION OFF DBC=<dbc file path> 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). “Appendix B: Security Setup Forms That Accept SQL Statement” on page 45 contains a list of Forms that allow the user to edit code. The Define User Form allows the System Administrator to review and modify guest user responsibilities. REVIEW USERS WITH ADMINISTRATIVE RESPONSIBILITIES In E-Business Suite. For this reason.fnd.E-Business Suite Security To activate full server security from the command line (SECURE mode): jre oracle. In addition to the generic SYSADMIN responsibility. add code or otherwise affect executable code. grant inappropriate privileges to themselves or to others). In a production system access to these forms must be restricted. some forms allow users to enter SQL statements. Restrict access to these forms by assigning the responsibility to a small group of users. Through these forms users could alter security configuration (e. Define and assign appropriate responsibilities for end users that clearly reflect their line of duty. Limit guest user responsibilities to those necessary for sign-on and guest access.g. regularly review this list of users. Consider auditing the database tables listed there.AdminAppServer apps/<apps-passwd> \ AUTHENTICATION SECURE DBC=<dbc file path> To deactivate server security from the command line (OFF mode): jre oracle. LIMIT ACCESS TO FORMS ALLOWING SQL ENTRY To improve flexibility. most products have their own administrative responsibility.security.

set the Application Server Trust Level profile option value for that responsibility to be the number 1. Users can see this profile option. external Typically. 2 means normal and 3 means external. and of those responsibilities. as well. 2 or 3. can be set to either 1. 2 or 3. 23 . customers or employees outside of a company’s firewall connect to external servers. administrative). the administrator sets the NODE_TRUST_LEVEL 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. the system determines which responsibilities are valid for that user. The system returns only responsibilities appropriate for the Web server Trust Level. are considered secure and have full application access with few limitations. The system administrator access is described in the following table: Level Site Application Responsibility User Yes Yes Yes No Visible Allow Update Yes Yes Yes No The internal name for this profile option is APPL_SERVER_TRUST_LEVEL. 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).e. a server-based profile option.E-Business Suite Security 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. administrative 2. These have access to a small set of responsibilities. Three trust levels are supported: 1. The number 1 means administrative. For example. Setting the Server Trust Level for a Server To assign a trust level to a Web server. normal 3. If no value is set for NODE_TRUST_LEVEL. To restrict access to a responsibility. This indicates that only Web servers with the same or greater ordinal trust level may access that responsibility. Normal web servers are those used by employees within a company’s intranet and requiring non-administrative responsibilities. Restricting Access to a Responsibility When a user logs on to Oracle Applications via a Web server. To avoid having to set the NODE_TRUST_LEVEL for every single Web server. the Web server is assumed to have a trust level of 1 (i. which can be accessed from that particular Web server. but they cannot update it. administrative web servers are used exclusively by system administrators. A responsibility 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 . This option. Lastly. administrators may wish to set the NODE_TRUST_LEVEL profile to some default level of trust at the site level..

At this setting. responsibility selections and form accesses to APPLSYS. Profile Option Name SIGNONAUDIT:LEVEL Description Set at site-level to track actions starting when the user logs on. See Metalink Note 402116. Recommend Form MONITOR SYSTEM ACTIVITY WITH OAM Oracle Application Manager (OAM) provides screens for monitoring current and past system activity. OAM provides a framework extensible for running custom OAM reports. It provides an explanation of the features available. Monitoring features include current and historic user activity down to the page access level and current and historical Concurrent Manager activity. At site level. Regarding Page Access Tracking.E-Business Suite Security References For more information on how to enable and use the above security features. Properly configuring auditing and limiting auditing to appropriate tables should not have a measurable performance impact. APPLSYS. It tracks Web-based and Form-based accesses across technology stacks and correlates them for each user session. SET SIGN-ON AUDIT LEVEL The valid settings for the profile option SIGNONAUDIT:LEVEL are None.FND_LOGIN_RESP_FORMS. unsuccessful signon. it tracks Oracle Applications usage statistics non-intrusively and with negligible performance impact. configuration steps and best practices for auditing. Access these reports through the system administrator responsibility. respectively.FND_LOGIN_RESPONSIBILITIES and APPLSYS. Often. refer to Oracle Applications System Administrator's Guide. form usage and concurrent request usage. In addition. set this profile option to Form to enable as much auditing as possible. the system logs all user sign-ons. User. See OAM documentation for complete product information. Refer to the Oracle Applications System Administrator's Guide for more information. AUDIT This chapter describes how to configure and use Oracle E-Business Suite audit features. users and responsibilities to audit.1 for more detailed information about Page Access Tracking. responsibility usage. Signon Audit Concurrent Requests Signon Audit Forms Signon Audit Responsibilities Signon Audit Unsuccessful Logins Signon Audit Users 24 .FND_LOGINS. E-Business Suite deployments do not take advantage of the auditing features due to the perceived complexity and performance issues. Responsibility and Form. RETRIEVE AUDIT RECORDS USING REPORTS Oracle E-Business Suite ships standard reports to access signon. It also suggests which common application objects like foundation objects.

Nevertheless. Develop SQL scripts to query these tables to generate reports.FND_LOGIN_RESP_FORMS APPLSYS.E-Business Suite Security RETRIEVE AUDIT RECORDS USING SQL The system stores end-user access data in the following tables. To save the entire history of a row. enable Oracle E-Business Suite Audit Trail. Note. APPLSYS. The system stores this information in the following columns (known as “Who Columns”): Who Column Name CREATION_DATE CREATED_BY LAST_UPDATE_LOGIN LAST_UPDATE_DATE LAST_UPDATED_BY Description Date and Time row was created Oracle Applications user ID from FND_USER Login ID from FND_LOGINS Date and Time row as last updated Oracle Applications user ID from FND_USERS Join with FND_USERS and FND_LOGINS tables to identify the application user tracked in the audit record. Periodically archive and truncate the FND_SIGNON_xxxx tables. Run this concurrent program at least once a week and retain 14 to 90 days of records.FND_UNSUCCESSFUL_LOGINS FND_CONCURRENT_REQUESTS ICX. these audit records contain valuable information. Run this concurrent program between once a week and once a month. retaining 30 to 90 days of records. The current program purges all audit records older than a user supplied date. database rows are updated with the creation and last update information. This concurrent program purges the following tables: FND_LOGIN_RESP_FORMS FND_LOGIN_RESPONSIBILITIES FND_LOGINS FND_UNSUCCESSFUL_LOGINS Purge concurrent request data using the Purge Concurrent Request and/or Manager Data concurrent program.ICX_FAILURES PURGE AUDIT RECORDS Purge end-user access data using the Purge Signon Audit Data concurrent program. Who Columns For most E-Business Suite tables. only the last update to record is saved.FND_LOGIN_RESPONSIBILITIES APPLSYS. REVIEW DATA TRACKED (NO REPORTS AVAILABLE) Some data tracked by the system do not have associated reports.FND_LOGINS APPLSYS. 25 .

In addition. Limit auditing to non-transactional data. Navigate through Security -> AuditTrail -> Tables to set columns in tables to be audited 5.a table whose name is the instance table’s name appended with _A. Both the FND_UNSUCCESSFUL_LOGINS and ICX_FAILURES tables contain unsuccessful logins via the Personal Home Page (Self Service/Web Interface). Auditing transactional data may cause significant performance degradation. a concurrent program creates a shadow table and places triggers on the columns to be audited. When initialized. The ICX_FAILURES table holds more information than the FND_UNSUCCESSFUL_LOGINS. ADVANCED AUDIT Oracle E-Business Suite implements its own auditing mechanisms. This program creates triggers on each audited column in the original table. Set System profile option AuditTrail: Activate to True 2. it creates two views for each column with the names _AC# and _AV# where # is a sequential number. Plan and consult with a DBA before enabling Audit Trails. which activates auditing.FND_UNSUCCESSFUL_LOGINS and ICX. The triggers store column changes in the shadow table -. CONFIGURING AUDIT TRAIL To enable Audit Trail. Auditing database row changes is performance intensive. Navigate through Security -> AuditTrail -> Install to set schemas for auditing 3. Navigate through Security -> AuditTrail -> Groups to create audit groups and set tables to be audited. run the AuditTrail Update Tables concurrent program. Run AuditTrail Update Tables to activate auditing GENERATE AND IDENTIFY AUDIT TRAIL OBJECTS To create the shadow tables as explained in the auditing section above. This functionality cannot be disabled. Failed Forms logins are logged only to the FND_UNSUCCESSFUL_LOGINS table. Set audit group to Enabled Requested 4. Audit Trails. This feature keeps a complete history of changes made at a table and column level.ICX_FAILURES tables.E-Business Suite Security Unsuccessful Logins The system automatically stores unsuccessful logon attempts in the APPLSYS. Shadow Table Update Trigger Insert Trigger Delete Trigger Changes View Complete View = <table = <table = <table = <table = <table = <table name>_A name>_AU name>_AI name>_AD name>_AV# name>_AC# CHOOSE TABLES TO AUDIT Consider auditing some of the tables that control system security. Tables with more than a few changes an hour should not be considered for row level auditing. ALR_ALERTS FND_AUDIT_COLUMNS FND_AUDIT_GROUPS FND_AUDIT_SCHEMAS 26 . follow these steps: 1.

3. Use shadow tables and views for accessing the records. select Security -> Audit Trail -> Groups. Oracle does not ship Audit Trail reports. Select the Security Audit group and set the group state to Enable. 6. Select the Security Audit group and set the group state to Disable – Purge Table. Select Security -> Audit Trail -> Groups. As System Administrator. 5. Purge the data from the shadow table.1 – Troubleshooting (Audit Trail) Metalink Note 60828. Run the Audit Trail Update Tables Report. 4. 7. Use the following procedure to purge audit data: 1. 2. disable the Audit Trail. Run the Audit Trail Update Tables Report REFERENCES ON E-BUSINESS SUITE AUDITING Oracle10gR2 Administrator’s Guide – Auditing Database Use Oracle Applications System Administrator’s Guide – User and Data Auditing Metalink Note 105624. Prior to purging.1 – Overview of Oracle Applications AuditTrails Metalink Note 69660. PURGE AUDIT RECORDS Purge the audit trail information on a regular basis.E-Business Suite Security 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.1 – Understanding Data Auditing in Oracle Application Tables 27 .

E-Business Suite Security 28 .

SET POLICY FOR UNATTENDED PC SESSIONS People may attempt to access unattended workstation while the user is still logged into the system. check Microsoft website for the latest browser security patches (http://www. When using Internet Explorer: upgrade to at least Version 6. Also. they often include new security features.0“ for information about securing the desktop. 29 . Organizations should set a corporate policy for handling unattended PC sessions.com) TURN OFF AUTOCOMPLETE IN INTERNET EXPLORER For kiosk machines.1 “Recommended Browsers for Oracle Applications 12. UPDATE BROWSER Update browser when new versions are released. for privacy and security reasons this feature should be disabled. IE can automatically show previous values entered in the same form field. change Internet Explorer’s autocomplete settings.0.microsoft. click the AutoComplete button. To turn OFF the Auto Complete feature: 1. Although desirable for frequently accessed pages.Desktop Security Desktop Security DESKTOP TIER Web Browser Forms applet. 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. Sun Java This section contains security recommendations for the Desktop. HARDENING CONFIGURE BROWSER See Metalink Note 389422. 3. Navigate through Tools -> Internet Options -> Content 2. Uncheck "forms" and "User names and passwords on forms". Users are recommended to use the password-locked screen savers feature on all PCs. do not use the "remember password" function. Check browser for built-in safety features. this is a known security vulnerability. From the Content tab.

Desktop Security 30 .

4. Ensure that the owner. Set the permissions on $ORACLE_HOME/bin to 0751 or less. The directory $ORACLE_HOME/bin contains Oracle executables. Verify that set userid (SUID) and set group id (SGID) are not set on binaries. A typical mistake is to install the executables in user oracle’s directory but owned by root. Prevent remote login to the Oracle (and root) accounts. Note. In general. $chgrp -R <dba> $ORACLE_HOME $chown -R <oracle> $ORACLE_HOME 5. The following commands make this change. require that legitimate users connect to their own accounts and su to the Oracle account. Set all other directories in $ORACLE_HOME to 0750 or less. Better yet. Instead. Warning: If Concurrent Manager runs on the Database tier and using the BEQ adapter to avoid TCP cost.courtesan. 7. Review owners and groups when cloning a database. This section contains security recommendations for tightening Oracle file system security along with more general advice for overall system hardening.com/sudo. the SUID and/or SGID bit must be set on the Oracle database executable in $ORACLE_HOME/bin. 2. Protect the $ORACLE_HOME/rdbms/admin directory including catalog. use sudo to restrict access to executables.Operating Environment Security Operating Environment Security The environment in which Oracle Applications run contributes to or detracts from overall system security. the group and owner are for illustration only.sql.ora to 0644. 2. 3. 3. CLEANUP FILE PERMISSIONS Refer to the product installation documentation for the complete instructions on setting file permissions. the correct group and owner should be substituted.ora and sqlnet. Set file permissions for listener. Find more information about sudo at http://www. Note. The FAT/FAT32 file system provides no security. group and modes of the Oracle files created upon installation are set to allow minimum privilege. On Unix systems: 1. HARDENING CLEANUP FILE OWNERSHIP AND ACCESS 1. This may also apply for any third party products running on the db tier. Oracle recommends that the SUID and SGID bits to be removed from binaries shipped by Oracle. Secure scripts containing usernames and passwords. Check that the operating system owner of these executables matches the operating system user under which the files have been installed. 31 . catproc.ora to 0600. 6. 8.sql and backup scripts. Set file permissions for tnsnames. this limits access to the Oracle user and its groups (probably DBA). 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. On windows systems. NTFS must be used.

1. Disabling unused services reduces securing and monitoring work.conf. rcp and ftp. Application middle-tiers and web-tiers do not require an X server. This is required for outbound emails. It provides a point of resistance by protecting inside systems from external users. 3. Although not required by the E-Business Suite. 4. If possible. Do not assume that using Network Address Translation (NAT) substitutes for a firewall. Oracle Installer requires access to the X server which in turn may require access to an X font server.Operating Environment Security LOCKDOWN OPERATING SYSTEM LIBRARIES AND PROGRAMS The database and applications require that the underlying operating system provide certain services. Turn off unused services in /etc/inetd. turn off all RPC ports on the router. the following services may provide operational convenience: 1. A firewall machine can filter packets and/or be a proxy server. NTP (Network Time Protocol) – for synchronizing the clock on the UNIX hosts to provide accurate audit records and simplify trouble-shooting. b. On the internet or large network. limit access to services users need and make those services as secure as possible. If possible. Firewalls may be software or hardware based. restrict access to the operating system users who absolutely need the printing facility from the shell. opening only those ports known to be required. Better yet. rsh. use a firewall machine or router with firewalling capabilities. FILTER IP PACKETS IP filtering helps to prevent unwanted access. Remote Access Use secure shell (ssh) to access middle-tier and database hosts. On the host. Printers Applications may require access to printers – normally via the lpd interface on port 515/TCP. dedicate a machine to be the firewall. This replaces telnet. This means that there is no requirement to install X on any of the EBS servers if a remote X Display can be provided during installation. CRON – for operating system cleanup and log file rotation 3. For software solutions. typically notifications from the workflow system. restrict access to the operating system users who absolutely need the mail facility from the shell. implement a default OFF policy. Electronic Mail Applications may require access to a SMTP Mail Transfer Agent (SMTP MTA) typically sendmail or qmail on port 25/TCP. database and application components for health and security NETWORK To secure the network. 32 . Filtering out unused services at the firewall or router level stops infiltration attempts earlier in the process. create access control lists in /var/adm/inetd. A production Database does not require access to an X server.sec to limit which hosts can connect to the local machine. rlogin. X Server a. Unless running NFS between networks. A firewall machine sits between the internet and the intranet or the intranet and the internal servers. c. Monitoring agents – for monitoring operating system. 2. 2.

do not allow hosts. ELIMINATE FTP CONNECTIONS Unless required. children's names or a hobby. etc. only (specified in /etc/security).Operating Environment Security PREVENT SPOOFING To prevent hostname spoofing. MONITOR FOR ATTACKS Consider installing an Intrusion Detection System (IDS). AUTHENTICATION Good security requires secure accounts. On the system side.netrc files weaken security.netrc file permissions are 600. In addition. should not be used. VERIFY NETWORK CONFIGURATION Use scanning tools to find common security violations. turn off this service. To implement password security on HP systems use HP's trusted system package via SAM (if NIS or NIS+ is not running). verify that all . Limit root to console login. SSH provides encrypted traffic to prevent snooping. Add all networking patches. ELIMINATE TELNET CONNECTIONS Enforce the use of SSH (secure shell).rhost and . non-guessable password. Often. To ensure that the passwords are not guessable. The root password must be a strong.equiv or .rhosts. use the scp or sftp programs that come with ssh. see “Limit root access” below). the easier it is to track changes. To copy files.). Snort is a capable and free IDS system. If possible. In addition. people use passwords associated with them: license plate numbers. for this reason. Standard ftp sends passwords in clear text and. at least restrict telnet to a limited number of machines (via tcpwrappers or host firewalls) and turn off root login (except console. Automatically disable accounts after several failed login attempts. use crack or john-the-ripper (password cracking tools) on a regular basis. never leave root shells unattended. .equiv. Consider using a cron job to automatically check and enforce this. hosts. only use fully qualified hostnames or IP addresses in system files (NFS. If not possible. 33 . change the root password every three (3) months and whenever an administrator leaves company. A password tester may check for these. change passwords from time to time. Always logout of root shells. LIMIT ROOT ACCESS The fewer people with root access. If telnet must be used. CONFIGURE ACCOUNTS SECURELY Make sure that all OS accounts have a non-guessable password. turn off source routing and filter packets originating outside the network that have source IP address from the inside network. Consider using one-time passwords such as skey. For example.

DO NOT ALLOW GUEST ACCOUNTS It is hard to imagine what kind of guests should have access to a production EBS system. SECURE FILE ACCESS Create minimal writable file systems (esp. Verify user accounts . MANAGE USER ACCOUNTS Do not share user accounts. By using fully qualified hostnames. system files/directories). but often not practical.Operating Environment Security Root.delete or lock accounts no longer required. Require strong passwords and. For this reason do not allow guest access. To avoid trojan horse programs. and only root. Root should NEVER have “. Use setuid/setgid only where absolutely necessary. /dev/tty and /dev/console should be world writable but NEVER executable. Remove or disable user accounts upon termination. in some cases.*’ files for security holes. always use full pathnames including aliases. Use a checksum to verify they have not been altered. a restricted shell. Install latest operating system patches. MAINTENANCE Good security practice does not end after installation. SECURE EXECUTABLES Always get programs from a known source. lp. should have UID 0. use limited access flags when possible (such as readonly or nosuid). NEVER allow non-root write access to any directories in root's path. The minimal umask for root is 022 (rwxr-xr-x). daemon. A umask of 077 (rwx------) is best. adm). 34 . The root ‘.*’ files SHOULD have 700 or 600 permissions. Disable login for well known accounts that do not need direct login access (bin. When creating the /etc/exports file. Limit important file access to authorized personnel. Continued maintenance tasks include: Install the latest software patches. do not create root's temporary files in publicly writable directories. apply latest patches. uucp. If possible. Limit user file writes to their own directories and /tmp.” in path. sys. AUTHORIZATION SECURE NFS Only run NFS as needed. Run security software and review output. only the named host may access the file system. Check root ‘. Most other device files should be unreadable and unwritable by regular users. SECURE OPERATING SYSTEM DEVICES Device files /dev/null. Add directories for specific groups.

Test the system with tools like NESSUS (network security) and CRACK (password checker). sulog. etc. Consider setting up automatic email or paging to warn system administrators of any suspicious behavior.Operating Environment Security Keep up to date on security issues by subscribing to security mailing lists. 35 . Monitor log files including btmp. Implement trusted file systems like NIS. Also check the snort logs. syslog. Install Tripwire to detect changes to files. NIS+ or others such as HP-UX trusted system. reading security news groups and following the latest security procedures. wtmp.

Operating Environment Security 36 .

AppsPasswordValidation. this class must be loaded into the Application database using the loadjava command. CUSTOMIZE PASSWORD VALIDATION To customize password validation create a Java class that implements the oracle. cost of defense and value of data protected. String password This method takes a username and password.PasswordValidation Java interface. Patch 2128669 contains an example demonstrating how to write a custom event and/or additional subscriptions. Authentication: Identifies users. Oracle Advanced Security provides the following features: Data Integrity: Prevents data modification during transmission. 3. The option protects against threats to the security of distributed environments. and security protocols. hosts and clients securely and provides single sign-on. The interface requires three methods: 1. If the name of the Java class is yourco.e. public String getErrorStackMessageName() This method returns the name of the message to display when the user's password is deemed invalid (i.Extras for Experts Extras for Experts Security policy must balance risk of attack.security. and returns True or False.apps. 37 . This section contains recommendations that improve security. or process receives appropriate object access privileges. This functionality is disabled by default. The next user action returns the browser to a login screen indicating the session is invalid. but may not be appropriate for every deployment. public String getErrorStackApplicationName() This method returns the application short name for the aforementioned error message.security. the validate() method returns False). 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. the E-Business Suite raises a Workflow event when the same user has multiple. This renders the other sessions invalid. ADVANCED SECURITY/NETWORKING OPTION (ASO/ANO) Oracle Advanced Security provides a single source of integration with network encryption and authentication solutions. Data Privacy: Prevents data disclosure during transmission. DETECT AND PREVENT DUPLICATE USER SESSIONS When properly patched and configured. After writing the customized password validator. public boolean validate(String user. Note.AppsPasswordValidation". Specifically.fnd. respectively. User names appearing in the subscription's parameter list are excluded from this functionality. set profile option SIGNON_PASSWORD_CUSTOM to the full name of the class. Authorization: Ensure that a user. The subscription calls a rule function that updates the ICX_SESSIONS table setting the DISABLED_FLAG='Y' for all other sessions for the user. program.. 2. indicating whether the user's password is valid or invalid. then the value of SIGNON_PASSWORD_CUSTOM must be "yourco. open sessions. single sign-on services.security.

1 provides more information on using ASO/ANO to encrypt your Oracle E-Business Suite 11i network traffic. but use a port other than the one the Oracle Listener for the database is using. Configure the Oracle EXTPROC Listener with an IPC protocol address only. Enable Valid Node Checking and restrict access to those network clients requiring EXTPROC. Remove EXTPROC specific entries from the Oracle Database Listener configuration files. Modify the EXTPROC specific entry in $ORACLE_HOME/network/admin/tnsnames.ora files are located. Use a separate $TNS_ADMIN/sqlnet.ora and sqlnet.Extras for Experts Metalink Note 391248. On Windows platforms. 2. 6. Oracle Intermedia cartridges -. Restrict access to the Oracle Listener for PL/SQL EXTPROC only. do the following: a. Copy the listener. such as mathematical modeling or files system interactions. The following Oracle E-Business suite components use EXTPROC services: 1. c. 5. CONFIGURE LISTENER ON A NON-DEFAULT TCP PORT By default. Oracle Demand Planning Express implementation. To protect against some EXTPROC attack vectors: 1. this makes attacks more difficult..ora file for this Oracle Listener.InterMedia needs to be installed with 11i.” 4. b. If the Oracle Listener for PL/SQL EXTPROC has been configured with a TCP address.ora parameter 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 it contains the password. Before starting the Oracle Listener for PL/SQL EXTPROC. Oracle Email Center. set the TNS_ADMIN environment variable (or Windows Registry parameter) to specify the directory in which the new configuration files for PL/SQL EXTPROC are stored. If TCP connectivity is required. 3. the only limits on external procedures are the limits on what that account can do. configure a TCP protocol address. Create two Oracle TNS Listeners. Ensure that the Oracle Listener created for PL/SQL EXTPROC runs as an unprivileged operating system user (e.ora to reflect the correct port for the new Oracle Listener. Configure it to listen on another port number. Because the Listener runs with the privilege of the operating system user. This functionality exploits the ability of the Listener to issue operating system commands. Ensure that the file permissions on separate $TNS_ADMIN/listener. HARDENING EXTERNAL PROCEDURE (EXTPROC) SERVICES The Oracle database uses the external procedure service to call external C programs. Although not foolproof. “nobody” on Unix).g. Give this user the operating system privilege to “Logon as a service. The specification exists in the listener. the TNS Listener receives service requests on TCP port 1521. only the owner should read the file.ora with the configuration of the Oracle Listener for PL/SQL EXTPROC into this other directory as well. run the Oracle TNS Listener process as an unprivileged user and not as the Windows LOCAL SYSTEM user. This extends the functionality of PL/SQL to routines that can be written in C to perform complex calculations.ora are set to 600. 2. 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 38 . one for the Oracle database and one for PL/SQL EXTPROC. 3. The external procedures are supposed to issue the commands to the Listener on a special IPC pipe named EXTPROC. Store this file in any directory other than the one in which the database listener.

ora. This may be useful for customizations that involve addition of new schemas or customized PL/SQL code to be called as an external procedure service. VSEC1159_EXTPROC = (ADDRESS_LIST = (ADDRESS= (PROTOCOL= IPC)(KEY= EXTPROCVSEC1159)) 39 . the LISTENER NAME is VSEC1159_EXTPROC and ORACLE_SID is VSEC1159.ora. Replace $ORACLE_SID with the name of the Oracle database instance (SID). In it. $ORACLE_HOME with the value of ORACLE HOME directory for this Listener and $TNS_ADMIN with the directory location of the Listener parameter files. This step may not be applicable for default E-Business Suite implementations. EXTPROC LISTENER CONFIGURATION See below for the format of the dedicated EXTPROC Listener. 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. $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 = 0 CONNECT_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_EXTPROC TRACE_DIRECTORY_$ORACLE_SID_EXTPROC = $TNS_ADMIN TRACE_FILE_$ORACLE_SID_EXTPROC = $ORACLE_SID_EXTPROC The configuration below should appear in $TNS_ADMIN/tnsnames. The parameters appear in $TNS_ADMIN/listener. Replace the $ORACLE_SID with name of the Oracle database instance (SID).Extras for Experts privileges in the database (such as CREATE ANY LIBRARY).

text ) values ( 1.ora parameter that corresponds to EXTPROC Listener. Do the following to test whether InterMedia is working: 1.Extras for Experts ) SID_LIST_VSEC1159_EXTPROC = (SID_LIST = (SID_DESC = (SID_NAME = PLSExtProc) (ORACLE_HOME = /u01/oracle/vsec1159db/9.2. 3. 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.0.5/network/admin TRACE_FILE_VSEC1159_EXTPROC = VSEC1159_EXTPROC Example: The tnsnames.5/network/admin LOG_FILE_VSEC1159_EXTPROC = VSEC1159_EXTPROC TRACE_DIRECTORY_VSEC1159_EXTPROC = /u01/oracle/vsec1159db/9. 'The cat sat on the mat' ). insert into quick ( quick_id. insert into quick ( quick_id. varchar2(80) ). text ) values ( 2. ctxapp to textuser. Grant 'ctxapp' role to textuser: grant connect.5) (PROGRAM = extproc) ) ) STARTUP_WAIT_TIME_VSEC1159_EXTPROC = 0 CONNECT_TIMEOUT_VSEC1159_EXTPROC = 10 TRACE_LEVEL_VSEC1159_EXTPROC = OFF LOG_DIRECTORY_VSEC1159_EXTPROC = /u01/oracle/vsec1159db/9.2. create table quick ( quick_id constraint quick_pk text number primary key.0. 2. Create a user to work with InterMedia Text: create user textuser identified by <password> \ default tablespace users temporary tablespace temp.2. The EXTPROC Listener must be configured and working for InterMedia option to run. Connect as textuser and create required test objects: connect textuser/<password> drop table quick. 'The quick brown fox jumps over 40 .0. resource.

'The dog barked like a dog' ). text ) values ( 3. the InterMedia option is enabled and the EXTPROC Listener is properly configured.Extras for Experts the lazy dog' ). 'dog'.context. score(42) s from quick where contains ( text. col text format a45 col s format 999 select text. Cleanup the test user (textuser) created during this test. create index quick_text on quick ( text ) indextype is ctxsys. commit. insert into quick ( quick_id. 41 . 42 ) >= 0 order by s desc. If the above query works without any error.

Extras for Experts 42 .

end_date.function_id and fff. sysdate+1) and sysdate between fr. sysdate+1) union select distinct incrns. fnd_compiled_menu_functions fcmf.grant_flag = 'Y' and fcmf. wf_users wu.grantee_type in ('USER'.grantee_key = wur.name from fnd_grants fg.user_id = fu.function_id = fff.function_name = 'FND_FNDATDAG' and furg.responsibility_application_id = fr. fnd_responsibility fr.role_name = wr.function_id and fff.role_orig_system = wr.menu_id = fcmf. wf_user_roles wur.user_id and sysdate between fu. fnd_user_resp_groups furg.menu_id and fcmf. fnd_form_functions fff where furg.orig_system 43 . fnd_form_functions fff.end_date.menu_id and fcmf. wf_users incrns where fg.menu_id = fcmf.user_name from fnd_user fu.function_id = fff.application_id and fr. use the following query. select fu.function_name = 'FND_FNDATDAG' and fg. 'GROUP') and fg.Appendix A: Security Setup Forms Appendix A: Security Setup Forms Form Function FND_FNDATDAG FND_FNDATDAI FND_FNDATDAT FND_FNDFMFBF FND_FNDFMFUN FND_FNDMNMNU FND_FNDPOMPV FND_FNDRSGRP FND_FNDSCAUS FND_FNDSCPLS FND_FNDSCRSP XDP_FNDSCRSP Form Name FNDATDAG Audit Groups FNDATDAI Audit Installations FNDATDAT Audit Tables FNDFMFBF Forms FNDFMFUN Functions FNDMNMNU Menus FNDPOMPV Profile System Values FNDRSGRP Request Groups FNDSCAUS Users FNDSCPLS Web Enabled PL/SQL FNDSCRSP Responsibilities Table Name FND_AUDIT_GROUPS FND_AUDIT_SCHEMAS FND_AUDIT_TABLES FND_AUDIT_COLUMNS FND_FORM FND_FORM_FUNCTIONS FND_MENUS FND_MENU_ENTIRES FND_PROFILE_OPTION_VALUES FND_REQUEST_GROUPS FND_REQUEST_GROUP_UNITS FND_USER FND_USER_RESP_GROUPS FND_ENABLED_PLSQL FND_RESP_FUNCTIONS To find which users have a particular function (e. wf_roles wr.name and wur.responsibility_id = fr.start_date and nvl(fu.role_name and wur.g FND_FNDATDAG).responsibility_id and furg. fnd_compiled_menu_functions fcmf.start_date and nvl(fr.

expiration_date.end_date.name wur.start_date.start_date.orig_system in ('FND_USR'. sysdate+1) sysdate between nvl(wur.parent_orig_system_id incrns.Appendix A: Security Setup Forms and and and and and and and and and wur.start_date and nvl(fg. sysdate-1) and nvl(wur.role_orig_system_id = wr.parent_orig_system_id = incrns.orig_system_id wur. sysdate-1) and nvl(wr. sysdate+1) and sysdate between nvl(incrns.parent_orig_system wu.parent_orig_system = incrns.orig_system wur.expiration_date.user_orig_system = wu.user_orig_system_id = wu.expiration_date. sysdate-1) and nvl(wu. sysdate+1) and sysdate between nvl(wu.start_date. 'PER') sysdate between fg. sysdate+1) and sysdate between nvl(wr.user_name = wu. sysdate-1) and nvl(incrns.orig_system_id wu. sysdate+1). 44 .expiration_date.start_date.

Appendix B: Security Setup Forms That Accept SQL Statement Appendix B: Security Setup Forms That Accept SQL Statement Form Function ALR_ALRALERT FND_FNDCPMCP_SYS FND_FNDCPMPE FND_FNDFFMDC Form Name ALRALERT FNDCPMCP FNDCPMPE FNDFFMDC ALR_ALERTS Table Name FND_CONCURRENT_PROGRAMS FND_EXECUTABLES FND_DESCRIPTIVE_FLEXS FND_DESCR_FLEX_CONTEXTS FND_DESCR_FLEX_COLUMN_USAGES FND_FNDFFMVS FNDFFMVS FND_FLEX_VALUE_SETS FND_DESCR_FLEX_COL_USAGE FND_ID_FLEX_SEGMENTS FND_FLEX_VALIDATION_TABLES FND_FLEX_VALIDATION_EVENTS FND_FNDPOMPO FND_FNDSCAPP FND_FNDSCDDG FND_FNDSCMOU PSB_PSBSTPTY MSDCSDFN MSDCSDFA MSD_MSDAUDIT JTFRSDGR JTFBRWKB ONT_OEXPCFVT FNDPOMPO FNDSCAPP FNDSCDDG FNDSCMOU PSBSTPTY MSDCSDFN MSDCSDFA MSDAUDIT JTFRSDGR JTFBRWKB OEXPCFVT FND_PROFILE_OPTIONS FND_APPLICATION FND_DATA_GROUPS FND_DATA_GROUP_UNITS FND_ORACLE_USERID PSB_ATTRIBUTE_TYPES MSD_CS_DEFINITIONS MSD_CS_DEFINITIONS MSD_AUDIT_SQL_STATEMENTS JTF_RS_DYNAMIC_GROUPS_B JTF_RS_DYNAMIC_GROUPS_TL JTF_BRM_RULES_B OE_PC_CONSTRAINTS OE_PC_CONDITIONS OE_PC_ASSIGNMENTS OE_PC_VTMPLTS OE_DEF_ATTR_DEF_RULES JTF_OBJECTS_B JTF_OBJECTS_TL JTF_OBJECT_USAGES JTF_GRID_DATASOURCES_B JTF_GRID_COLS_B JTF_GRID_DATASOURCES_B JTF_GRID_COLS_B JTF_RS_RESOURCE_EXTNS JTF_RS_GROUPS_B JTF_RS_TEAMS_B ONT_OEXDEFWK. QP_OEXDEFWK JTFTKOBT OEXDEFWK JTFTKOBT JTF_GRID_ADMIN JTFGDIAG JTFGANTT JTFGRDMD JTFGDIAG JTFGANTT WMS_WMSRULEF QP_QPXPRFOR QP_QPXPTMAP GMAWFPCL_F WMSRULEF QPXPRFOR QPXPTMAP GMAWFPCL QP_PRICE_FORMULAS_B QP_ATTRIBUTE_SOURCING GMA_PROCDEF_WF 45 .

Appendix B: Security Setup Forms That Accept SQL Statement

GMAWFCOL_F AME_WEB_APPROVALS PERWSAPI FFXWSMNG FFXWSDFF FFXWSBQR PAYWSDAS PAYWSDYG

GMAWFCOL PERWSAPI FFXWSMNG FFXWSDFF FFXWSBQR PAYWSDAS PAYWSDYG

GMA_ACTDEF_WF AME_ATTRIBUTE_USAGES AME_APPROVAL_GROUPS N/A FF_FUNCTIONS FF_FUNCTIONS FF_QP_REPORTS HR_ASSIGNMENT_SET_CRITERIA PAY_TRIGGER_COMPONENTS PAY_TRIGGER_INITIALISATIONS PAY_TRIGGER_SUPPORT PER_SECURITY_PROFILES

PERWSSCP

PERWSSCP

46

Appendix C: Database Schemas Shipped with E-Business Suite

Appendix C: Database Schemas Shipped with E-Business Suite
Type
1 1 1 2 2 3 3 4 4 4 4 5 SYS SYSTEM DBSNMP SCOTT SSOSDK JUNK_PS, MDSYS, ODM_MTR, OLAPSYS, ORDPLUGINS, ORDSYS, OUTLN, OWAPUB PORTAL30_DEMO, PORTAL30_PUBLIC, PORTAL30_PS, PORTAL30_SSO_PUBLIC PORTAL30, PORTAL30_SSO CTXSYS EDWREP ODM APPLSYSPUB

Schemas

Change
Y Y Y Y Y Y Y Y Y Y Y N

Managed
N N N N N N N Y Y Y Y Y

Description
Initial schema in any Oracle database. Owns the sql data dictionary. Initial DBA User. Used for database status monitoring. Demo account delivered with RDBMS. Single Sign On SDK.

Oracle Portal and Portal Single Sign On, v3.0.9 Oracle Portal and Portal Single Sign On, v3.0.9 InterMedia schema used by Online Help and CRM service products for indexing knowledge base data. Embedded Data Warehouse Metadata Repository Oracle Data Manager Initial, pre-authentication user with minimal privileges to assist with APPS (FND) user authentication. Contains shared APPS foundation objects. Runtime user for E-Business Suite. Owns all of the applications code in the database. Optional, additional APPS schemas for the (now obsolete) Multiple Reporting Currencies feature. Defaults to APPS_MRC, but country code suffixes may be used, e.g. APPS_UK, APPS_JP. Used by Oracle Applications Manager (OAM) to monitor patching. These schemas belong to individual APPS base products. By default the password is the same as the SCHEMA name. Changing the password for these schemas does not affect any configuration files.

5 5 5

APPLSYS APPS APPS_mrc

Y Y Y

Y Y Y

5 6

AD_MONITOR ABM AHL AHM AK ALR AMF AMS AMV AMW AP AR ASF ASG ASL ASN ASO ASP AST AX AZ BEN BIC BIL BIM BIS BIV BIX BNE BOM BSC CCT CE CLN CN CRP CS CSC CSD CSE CSF CSI CSL CSM CSP CSR CSS CUA CUE CUF CUG CUI CUN CUP CUS CZ DDD DOM EAA EAM EC ECX EDR EGO ENG ENI EVM FA FEM FII FLM FPA FPT FRM FTE FUN FV GCS GL GMA GMD GME GMF GMI GML GMP GMS GR HR HRI HXC HXT IA IBA IBC IBE IBP IBU IBY ICX IEB IEC IEM IEO IES IEU IEX IGC IGF IGI IGS IGW IMC IMT INV IPA IPD ISC ITG IZU JA JE JG JL JTF JTM JTS LNS ME MFG MRP MSC MSD MSO MSR MST MWA OE OKB OKC OKE OKI OKL OKO OKR OKS OKX ONT OPI OSM OTA OZF OZP OZS PA PJI PJM PMI PN PO POA POM PON POS PRP PSA PSB PSP PV QA QOT QP QRM RG RHX RLA RLM SSP VEA VEH WIP WMS WPS WSH WSM XDO XDP XLA XLE XNB XNC XNI XNM XNP XNS XTR ZFA ZPB ZSA ZX

Y Y

N Y

47

Appendix C: Database Schemas Shipped with E-Business Suite

In the table on the previous page, Type refers to the categories listed in “Change default installation passwords” on page 10. Change means we recommend changing the default password for the listed schemas. Managed means that FNDCPASS should be used to change the passwords of the listed schemas. Note, SQL*Plus provides two methods to change a schema’s password: ALTER USER and PASSWORD syntax. To simplify these instructions, we have used the ALTER USER syntax. However, PASSWORD is often mentioned as the preferred method for changing a schema’s password due to the lack of an echo back to the terminal. The syntax for changing a schema password from within SQL*Plus is:
SQL> password <account> Changing password for <account> New password: <new-password> Retype new password: <new-password>

CATEGORY 1

SYS & SYSTEM Change the passwords for these schemas:
SQL> alter user SYSTEM identified by <NEW_SYSTEM_PASSWORD>; SQL> alter user SYS identified by <NEW_SYS_PASSWORD>;

CATEGORY 1

DBSNMP The DBSNMP schema is used by Oracle Enterprise Manager (EM) for monitoring and management purposes. If you are not using EM with your Applications database, follow database instructions for managing this account. If you are using Enterprise Manager with your Applications database, you should change the password for the DBSNMP schema using sqlplus and (re-)configure EM accordingly. Instructions to do this are dependent on the version of Oracle Enterprise Manager in use. When using Oracle Enterprise Manager Intelligent Agent, please refer to the following section of the Oracle Intelligent Agent User's Guide for instructions as well as Metalink note 317409.1:
http://download.oracle.com/docs/html/A96676_01/config.htm#621781

When using Oracle Enterprise Manager Grid Control, please refer to the following section of the Oracle Enterprise Manager Advanced Configuration document for instructions:
http://download.oracle.com/docs/cd/B16240_01/doc/em.102/b16242/emctl.htm#sthref224

CATAGORY 2

SCOTT & SSOSDK Change the password for SSOSDK:
SQL> alter user SYSTEM identified by <NEW_SSOSDK_PASSWORD>;

Lock the SCOTT schema:
SQL> alter user SCOTT account LOCK;

CATEGORY 3

JUNK_PS, MDSYS, ODM_MTR, OLAPSYS, ORDPLUGINS, ORDSYS, OUTLN & OWAPUB Change the passwords for these schemas:
SQL> alter user <SCHEMA> identified by <NEW_PASSWORD_PER_SCHEMA>;

48

9 installation.9 from E-Business Suite 11i.9 with E-Business Suite 11i as documented in OracleMetaLink Note 146469.0.0. Alternatively. then log into SQL*Plus with administrative privileges and lock these schema: SQL> SQL> SQL> SQL> alter alter alter alter user user user user PORTAL30_DEMO account lock. run AutoConfig as documented in Oracle MetaLink Note 165195.9 with E-Business Suite 11i as documented in Oracle MetaLink Note 146469." CATEGORY 4 PORTAL30 & PORTAL30_SSO If you are using Oracle Login Server and Portal 3. PORTAL30_SSO_PUBLIC account lock." For more information. you should change the passwords for PORTAL30_PUBLIC.1 "Remove Oracle Portal 3.9 with E-Business Suite 11i as documented in Oracle MetaLink Note 146469.1.0. PORTAL30_SSO_PS identified by <newpassword>.1 "Remove Oracle Portal 3.Appendix C: Database Schemas Shipped with E-Business Suite CATEGORY 3 PORTAL30_DEMO. you must use FNDCPASS to change the PORTAL30 and PORTAL30_SSO passwords $ FNDCPASS APPS/<apps_pwd> 0 Y SYSTEM/<system_pwd> ORACLE PORTAL30 <new_pwd> $ FNDCPASS APPS/<apps_pwd> 0 Y SYSTEM/<system_pwd> ORACLE PORTAL30_SSO <new_pwd> After you change the PORTAL30 and PORTAL30_SSO passwords. PORTAL30_SSO_PS account lock. 49 .1. which describes the Portal 3. if you are not using any PORTAL30 integration. PORTAL30_SSO_PS & PORTAL30_SSO_PUBLIC and lock the PORTAL30_DEMO schema: SQL> SQL> SQL> SQL> alter alter alter alter user user user user PORTAL30_DEMO account lock.0. then log into SQL*Plus with administrative privileges and lock these schema: SQL> alter user PORTAL30 account lock. PORTAL30_SSO_PS & PORTAL30_SSO_PUBLIC If you are using Oracle Login Server and Portal 3.0. you may remove the PORTAL30% schemas by following instructions in OracleMetaLink Note 312349.0.1. If you are not using Oracle Login Server and Portal 3.9 with E-Business Suite 11i as documented in OracleMetaLink Note 146469. PORTAL30_SSO_PUBLIC identified by <newpassword>.0. if you are not using any PORTAL30 integration. refer to ATG OracleMetaLink note 146469. PORTAL30_PUBLIC.1 "Using AutoConfig to Manage System Configurations with Oracle Applications 11i." CATEGORY 4 EDWREP & ODM Use FNDCPASS to change the password for these schemas: $ FNDCPASS APPS/<apps_pwd> 0 Y SYSTEM/<system_pwd> ORACLE <schema> <new_pwd> If not using Embedded Data Warehouse. PORTAL30_PUBLIC identified by <newpassword>.9 from E-Business Suite 11i. SQL> alter user PORTAL30_SSO account lock.1. you may remove the PORTAL30% schemas by following instructions in OracleMetaLink Note 312349. PORTAL30_PUBLIC account lock. lock and expire EDWREP schema.1. If you are not using Oracle Login Server and Portal 3. Alternatively.

CTXSYS password should be changed to a secure value using FNDCPASS. Use a long (12 or more characters). FND user).5 and prior versions. APPS and any additional APPS_mrc schemas share the same password. However. APPS_MRC is an obsolete account. FNDCPASS allows a one-step. $ FNDCPASS APPS/<apps_pwd> 0 Y SYSTEM/<system_pwd> ORACLE APPLSYSPUB <new_pwd> All application tier processes (apaches) must be restarted following the password change and password propagation. although it may be used in older versions of E-Business Suite. The SQL script $AD_TOP/patch/115/sql/admonusr. you must use FNDCPASS and run Autoconfig (or a manual procedure) to propagate the change to application tier configuration files. which includes running PL/SQL packages to verify the username/password combination and the privilege to record the success or failure of a login attempt. CATEGORY 5 APPLSYS. APPS is the shared runtime schema for all E-Business Suite products. There is no need to change the password for APPLSYSPUB.sql creates AD_MONITOR.k. mass change of all these passwords. the CTXSYS schema can be expired and locked by : SQL> alter user CTXSYS password expire account lock. All application tier processes (apaches. For E-Business Suite 11.a. ZX Change all of these product schema passwords. APPS & APPS_MRC APPLSYS.. $ FNDCPASS APPS/<apps_pwd> 0 Y SYSTEM/<system_pwd> ALLORACLE <NEW_PWD> 50 . forms server) must be restarted following the password change and password propagation. FNDCPASS knows the password must be synchronized across these schemas. secure password for these schemas.Appendix C: Database Schemas Shipped with E-Business Suite CATEGORY 4 CTXSYS E-Business Suite uses the CTXSYS schema. CATEGORY 5 AD_MONITOR Oracle Applications Manager uses this schema to monitor running patches. the schema is created locked and expired. $ FNDCPASS APPS/<apps_pwd> 0 Y SYSTEM/<system_pwd> SYSTEM APPLSYS <new_pwd> After changing the shared password for these schemas you must run Autoconfig to propagate the changed passwords into the application server configuration files. CATEGORY 5 APPLSYSPUB APPLSYSPUB schema has sufficient privileges to perform the authentication of an Applications User (a.5. Although the default password for AD_MONITOR is 'lizard'. should you choose to change this password. ccm. CATEGORY 6 ABM . FNDCPASS accepts a keyword ALLORACLE forcing a change of all managed schemas to the new password.

sh adformsrvctl.remote.Appendix D: Processes Used by E-Business Suite Appendix D: Processes Used by E-Business Suite Process Name tnslsnr httpd httpds java FNDLIBR FNDSM INVLIBR java java java opmn Description Applications RPC Listener process Apache Web Server Listener Script adalnctl. default in Release 12 is servlet mode 51 .sh java oracle.RemoteCommand Fulfillment Server process a.fm.sh adoacorectl.apps.sh Forms zone JVMs OA Core zone JVMs Web services zone JVMs Oracle Process Manager Forms Servera adformsctl.jtf.sh Concurrent Manager adcmctl.sh adoafmctl.sh jtffmctl.jtf.sh adopmnctl.processor.Processor java oracle.apps.engine. The forms server (socket mode) is optional.fm.sh adapcctl.engine.

Appendix D: Processes Used by E-Business Suite 52 .

It is either s_webport or s_websslport 11000 6100 6200 6500 2300023004 2350023504 2400024004 2450024504 2150021504 2200022004 2250022504 2500025004 2000020004 Fusion Middleware Oracle HTTP Server s_jtfuf_port s_ons_localport s_ons_remoteport s_ons_requestport s_oacore_jms_portrange s_forms_jms_portrange s_home_jms_portrange s_oafm_jms_portrange s_oacore_ajp_portrange s_forms_ajp_portrange s_home_ajp_portrange s_oafm_ajp_portrange s_oacore_rmi_portrange Applications Fusion Middleware Fusion Middleware Fusion Middleware Fusion Middleware Fusion Middleware Fusion Middleware Fusion Middleware Fusion Middleware Fusion Middleware Fusion Middleware Fusion Middleware Fusion Middleware JTF Oracle HTTP Server Oracle HTTP Server Oracle HTTP Server oc4j oc4j oc4j oc4j oc4j oc4j oc4j oc4j oc4j 53 . i.Appendix E: Ports Used by E-Business Suite Appendix E: Ports Used by E-Business Suite Variable Name s_dbport s_rpcport Description Port on the database server used by the Net8 Listener RPC port on the concurrent processing server that receives incoming Report Review Agent requests Port on the Forms server used by the Forms Listener MSCA Server Port Number MSCA Dispatcher Port Number Port on the webserver where http server listens for non-ssl requests Port on the webserver where http server listens for ssl requests Default Value Firewall Configuration Technology RDBMS Applications Component TNS Listener Concurrent processing Forms 1521 Port should be open on the second level firewall 1626 Internal application tiers assumed to be of same subnet. no firewall s_formsporta 9000 Port should be open on the first level firewall if forms server is used 10200 10300 80 Port should be open on the first level firewall 443 Port should be open on the first level firewall Forms 10 s_mwaPortNo s_mwaDispatcherPort s_webport s_webssl_port Applications Applications Fusion Middleware Fusion Middleware Mobile Mobile Oracle HTTP Server Oracle HTTP Server s_active_webport Value of this variable is set to value of s_webport when Listener is configured in non-ssl mode and to the value of s_webssl_port when ssl is configured JTF fulfilment server port Oracle Notification Service Oracle Notification Service Oracle Notification Service JMS for OACore zone JMS for Forms zone JMS for Home zone JMS for OAFM zone AJP for OACore zone AJP for OACore zone AJP for OACore zone AJP for OADFM zone RMI for OACore zone 80/443 This is not a separate port that we are opening.e.

54 . default is servlet mode.Appendix E: Ports Used by E-Business Suite s_forms_rmi_portrange s_home_rmi_portrange s_oafm_rmi_portrange RMI for Forms zone RMI for Home zone RMI for OAFM zone 2050020504 2100021004 2550025504 Fusion Middleware Fusion Middleware Fusion Middleware oc4j oc4j oc4j a. Forms server (socket mode) is optional in Release 12.

0. When using the ssh trick. CONFIGURE THE X SERVER To fulfill the requirement for an available X-server during installation you may use the one on the server itself or better yet. Customer experience may vary. INSTALL THE LINUX OPERATION SYSTEM Use standard install of Operating System including developer tools and ssh. Examples of outbound email include workflow generated messages and monitoring alerts.Appendix F: Sample Linux Hardening of the Application Tier Appendix F: Sample Linux Hardening of the Application Tier This section contains an example of how we hardened an Application Tier running the Linux Operating System. $ ssh -X oracle@dbs01 This will set the DISPLAY environment variable on the remote host (in this example the database host dbs01) to point back to the X-Server on the admin workstation.0. only.font-unix/fs7100 The only network accessible daemon running is the ssh daemon. 55 .1:25 servers) Foreign Address State PID/Program name 0.networked daemons in particular. stop (and disable) unnecessary daemons . After the installation of the Operating System and EBS. and user secure shell (ssh) with th eX option to log in to each of the servers where you need to install EBS.0. the servers on which EBS is being installed does not have to run a local X-Server and can remain in runlevel 3.0. Sendmail listens only on the localhost interface kept active for outbound mail. $ $ $ $ $ $ chkconfig chkconfig chkconfig chkconfig chkconfig chkconfig --level --level --level --level --level --level 3 3 3 3 3 3 sgi_fam off xinetd off nfslock off portmap off gpm off atd off With these changes and a runlevel change to 3. Rapid Install will then use the X-Server on the admin workstation during the installation process.0:* LISTEN 846/sshd 0.0. INSTALL E-BUSINESS SUITE Perform the EBS installation as a Rapid Install Vision multinode configuration with the functionality split onto separate hosts for database.0:* LISTEN 902/sendmail: accep Active UNIX domain sockets (only servers) Proto RefCnt Flags Type State I-Node PID/Program Path unix 2 [ ACC ] STREAM LISTENING 1215 969/xfs /tmp/. Web Service and Concurrent Manager service.0. Copy the context file generated during the installation of the database onto each middle-tier and run the rapid installation via NFS from a shared staging area.0. perform the installation from an X11-capable admin workstation.0. We provide this for illustration purposes. netstat on the Linux box is very short: $ netstat –lptuxn Active Internet connections (only Proto Recv-Q Send-Q Local Address tcp 0 0 0.0:22 tcp 0 0 127.

198.0.0:* 0.0.font-unix/fs7100 /var/tmp/.0:* 0.0:* 0.0:* 0.0.0.0.0.68.0..0.0.1:6500 152.0.0:* 0.0.198.68.0.1:25 0.26:6500 0.26:17060 Foreign Address 0.0.0:* 0..0. starting the EBS processes will open additional.0.0:1626 127.oracle/s#23574.0.Appendix F: Sample Linux Hardening of the Application Tier Running processes include: UID root root root root root root root root root root root root root root root root root root root root root root root root root root root root root xfs root root root root root root PID 14 13 12 11 10 9 8 7 6 1 2 3 4 5 15 23 150 151 152 153 154 659 664 846 1034 1035 1090 902 921 969 1026 1027 1028 1029 1030 1031 PPID 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 846 1034 1035 1 1 1 1 1 1 1 1 1 C 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 STIME 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:03 18:03 18:03 18:04 18:04 18:05 18:03 18:03 18:03 18:03 18:03 18:03 18:03 18:03 18:03 TTY ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? pts/0 pts/0 ? ? ? tty1 tty2 tty3 tty4 tty5 tty6 TIME 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:04 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 CMD [kupdated] [bdflush] [krefilld] [kreclaimd] [kswapd] [ksoftirqd_CPU3] [ksoftirqd_CPU2] [ksoftirqd_CPU1] [ksoftirqd_CPU0] init [keventd] [keventd] [keventd] [keventd] [mdrecoveryd] [kjournald] [kjournald] [kjournald] [kjournald] [kjournald] [kjournald] syslogd -m 0 klogd -2 /usr/sbin/sshd /usr/sbin/sshd -bash ps -eHf sendmail: accepting connections crond xfs -droppriv -daemon /sbin/mingetty tty1 /sbin/mingetty tty2 /sbin/mingetty tty3 /sbin/mingetty tty4 /sbin/mingetty tty5 /sbin/mingetty tty6 The above port and process views is of a host without the EBS processes running.0. WEB-TIER OPEN PORTS $ netstat –lptuxn Proto Recv-Q Send-Q tcp 0 0 tcp 0 0 tcp 0 0 tcp 0 0 tcp 0 0 tcp 0 0 tcp 0 0 tcp 0 0 tcp 0 0 tcp 0 0 tcp 0 0 .68.0.1:6100 152.68.0.0.0.0.0:4443 0.0:* 0. application specific ports on the various tiers.0:* 0.0:* 0.0.0:22 127.1 56 .0.0:8000 152.0:* State LISTEN LISTEN LISTEN LISTEN LISTEN LISTEN LISTEN LISTEN LISTEN LISTEN LISTEN PID/Program name 23574/tnslsnr 27358/opmn 27358/opmn 27358/opmn 27358/opmn 23391/httpd 23391/httpd 23408/java 23409/java Active UNIX domain sockets (only servers) Proto RefCnt Flags Type State I-Node PID/Program name unix 2 [ ACC ] STREAM LISTENING 1236 unix 2 [ ACC ] STREAM LISTENING 3360927 23574/tnslsnr Path /tmp/.198.0.0.0.0.0. Local Address 0.0.0:* 0.26:16060 152.0.26:6200 127.0.0.0.0.198.0.

0.0:22 127.0.font-unix/fs7100 /var/tmp/.0.0.0.1:25 0.0:1632 Foreign Address 0.0.0.0.0:* State LISTEN LISTEN LISTEN PID/Program name 1129/tnslsnr Active UNIX domain sockets (only servers) Proto RefCnt Flags Type State I-Node unix 2 [ ACC ] STREAM LISTENING 1215 unix 2 [ ACC ] STREAM LISTENING 313930 PID/Program name 1129/tnslsnr Path /tmp/.0.oracle/s#1129.Appendix F: Sample Linux Hardening of the Application Tier CONCURRENT MANAGER TIER OPEN PORTS Open the following ports for the Concurrent Manager and Report tier components: $ netstat -ltuxpn Proto Recv-Q Send-Q tcp 0 0 tcp 0 0 tcp 0 0 Local Address 0.0:* 0.0.0.1 57 .0:* 0.0.

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

Aaron Newman “Hackproofing Oracle Application Server (A Guide to Securing Oracle 9)”. “Oracle Security . Ltd.Appendix G: References & More Resources Appendix G: References & More Resources The table below contains references consulted in the preparation of this document as well as other resource material useful for securing E-Business Suite. Integrigy Corporation “Oracle Security Handbook : Implement a Sound Security Plan in Your Oracle Environment”.1 361482. Marlene L. Integrigy Corporation “Oracle Applications 11i Security Quick Reference”.1 391248.1 376811. Pete Finnigan Document Best Practices for Securing Oracle E-Business Suite Release 12 (this document) Best Practices for Securing Oracle E-Business Suite (11i version of this document) Oracle Default Password Scanner (scan for open schema accounts) Oracle E-Business Suite R12 Configuration in a DMZ (external deployment) Encrypting EBS 11i Network Traffic using Advanced Security Option / Advanced Networking Option Integrating Oracle E-Business Suite Release 12 with Oracle Internet Directory and Oracle Single Sign-On 59 . Next Generation Security Software.Step by Step”.1 189367.1 Document The Center for Information Security: Oracle Benchmark Tools “Effective Oracle Database 10g Security by Design”.1 380490. Theriault. DocID CIS DK IntA IntB MTAN NGSS PF MetaLink 403537. David Knox “Guide to Auditing in Oracle Applications”.

Appendix G: References & More Resources 60 .

You're Reading a Free Preview

Descarga
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->