Seguridad Oracle EBS 12.x

Secure Configuration Guide for Oracle E-Business Suite Release 12Oracle Corporation Version 1.1.0 Latest version of this document available under MOS Note 403537.1. Revision History Version 1.0.0 1.1.0 Release Date Feb 2007 Sep 2011 Updated for 12.0.x and 12.1.x Additional Applications Users, Additional Database Users, Additional Profile Settings, Refer to TDE & Audit Vault. AdminDesktop utility for creating DBC files. New Web-scanning appendix. Descriptions Initial version for Release 12.0, based on 11i version ML 189367.1 Copyright © 2007, 2011 Oracle. All rights reserved. Primary Authors: Erik Graversen, Eric Bing 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 Secure Configuration Guide for 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 Option/Networking Option (ASO/ANO) Advanced Security Option/Transparent Data Encryption (ASO/TDE) Practice Safe Cloning 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 31 33 34 35 36 36 37 37 38 38 38 38 Oracle TNS Listener Security...............................................................................................................................5 Oracle Database Security......................................................................................................................................9 Oracle Application Tier Security........................................................................................................................15 Oracle E-Business Suite Security .......................................................................................................................17 Desktop Security.................................................................................................................................................31 Operating Environment Security ........................................................................................................................33 Extras for Experts ...............................................................................................................................................37 Appendix A: Running Web Scanning Tools.......................................................................................................43 Appendix B: Sensitive Administrative Pages.....................................................................................................45 Appendix C: Database Schemas found in Oracle E-Business Suite...................................................................47 Appendix D: Processes used by Oracle E-Business Suite..................................................................................51 Appendix E: Ports used by Oracle 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 . 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 2 2 2 2 2 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 (only if required) 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 Secure audit records 9 9 9 9 10 10 11 11 11 11 11 12 13 13 13 13 13 14 14 v . Use this summary as a security reference guide or checklist. Security Checklist Oracle Application Tier Security Harden operating environment Harden Apache configuration Protect administrative web pages Configure logging 15 15 15 16 Oracle 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 Avoid Weak Ciphers and Protocols for SSL (HTTPS) 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 Switch to Hashed Passwords Tighten logon and session profile options Consider using Single-Sign-On Create new user accounts safely Create shared responsibilities instead of shared accounts Configure Concurrent Manager for safe authentication Configure Concurrent Manager for Start and Stop without the APPS password Activate Server Security Create DBC files securely Review and limit Responsibilities and Permissions 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 Retrieve audit records using SQL Purge audit records References on Oracle E-Business Suite auditing 17 17 18 18 18 18 18 19 19 21 21 21 21 21 22 22 23 23 24 24 25 26 26 26 27 27 27 28 28 28 29 29 29 vi . Security Checklist Desktop Security Configure browser Update browser Turn off AutoComplete Set policy for unattended PC sessions 31 31 31 31 Operating Environment Security Cleanup file ownership and access Cleanup file permissions Lockdown operating system libraries and programs Filter IP packets Prevent spoofing Eliminate telnet. rsh and ftp daemons Verify network configuration Monitor for attacks Configure accounts securely Limit root access Manage user accounts Secure NFS Secure operating system devices Secure executables Secure file access 33 33 34 34 35 35 35 35 35 35 36 36 36 36 36 Extras for Experts Detect and Prevent Duplicate User Sessions Customize Password Validation Encrypt Credit Cards Advanced Security/Networking Option (ASO/ANO) Advanced Security/Transparent Data Encryption (ASO/TDE) Practice Safe Cloning Hardening External Procedure (EXTPROC) Services EXTPROC Listener Configuration EXTPROC Testing Procedure 37 37 37 38 38 38 38 39 41 vii . Security Checklist Appendix A: Running Web-Scanning Tools Appendix B: Sensitive Administrative Pages Appendix C: Database Schemas found in Oracle E-Business Suite Appendix D: Processes used by Oracle E-Business Suite Appendix E: Ports used by Oracle E-Business Suite Appendix F: Sample Linux Hardening of the Application Tier Appendix G: References & More Resources viii . To that end. the E-Business Suite and individual desktops. administrative tools. JRE_TOP.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 section contains advice spanning five categories: Hardening Network Authentication Authorization Audit Covers hardening the file system. The last section “Extras for Experts” collects together advice that goes beyond the typical best practice. We follow this with advice for hardening operating systems including a sample Linux hardening (in the Appendix). the Application Server. application middle-tier and database) and fall into five categories (hardening. web pages. etc. data files. PORTAL_TOP. password management and other account related activities. JAVA_TOP. Covers physical topology. We cover security for the Database and Listener. Covers account management. IP restrictions at web server and database listener. Each organization determines its own correct balance. products and configuration. 1 . a properly secured computing infrastructure is critical. network security. on-going review and purging. cost of security and value of the information protected. firewalls. authentication. The recommendations that follow cross three tiers of machines (browser. we provide configuration guidance (practical advice) for securing Oracle’s E-Business Suite. a balance must be struck between risk of exposure. authorization and auditing). Covers configuration. When securing the infrastructure. Covers restrictions to executables. PRODUCT_TOPS ORACLE HOME Tools In today’s environment. programs. HTML_TOP. especially early on in an organization’s life cycle when people are few and work needs to be done quickly. which can be monitored and restricted. In addition. place a firewall between the middle-tier and the database. Each component within a system has some degree of monitoring capability.. Auditing and reviewing audit records address this third requirement. proper system configuration and system monitoring. etc.0 or later.Overview SYSTEM WIDE ADVICE Some advice applies to the entire E-Business deployment and the infrastructure in which it operates. we assume an E-Business Suite maintenance level of 12. for many reasons including good security practice. User privileges should be reviewed periodically to determine relevance to current job responsibilities. This cannot be emphasized enough. KEEP SOFTWARE UP TO DATE One of the principles of good security practice is to keep all software versions and patches up to date. MONITOR SYSTEM ACTIVITY System security stands on three legs: good security protocols. It also contains a patch set checker to assist with patch application. if necessary. often leaves a system wide open for abuse. The firewalls provide assurance that access to these systems is restricted to a known network route. RESTRICT NETWORK ACCESS TO CRITICAL SERVICES Keep both the E-Business application middle-tier and the database behind a firewall. roles. grants. Check this note yearly for revisions. Throughout this document. move to the latest version of Autoconfig and Patch Tools (AD). a firewall router substitutes for multiple. KEEP UP TO DATE ON LATEST SECURITY INFORMATION Oracle continually improves its software and documentation. 2 . As an alternative. The latest version of Autoconfig (TXK) configures a system following advice from this document. Over ambitious granting of responsibilities.0. Follow audit advice in this document and regularly monitor audit records. 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. independent firewalls. _0x a.2 (1.2 + Developer 6i OHS 1.2 Java Oracle_home: 10.1. See the “Oracle Application Concepts” guide from the installation DVD for more detail.0 JRE for Form applet: Sun JRE 1.0.1.1. modplsql is no longer required in Release 12 and is not configured b.2.x) Application Tier IAS 1.2 Reports 10.3.2.0.4 JDBC 9 or 10 Desktop Tier JRE for Forms applet: Oracle Jinitiator Release 12.2.0. the table below summarizes the changes in versions and highlights retired technology pieces.3 (1.0.2.1.2.2b Tools Oracle_home: 10.0. Updated Technology Stack Release 12 has updated the entire technology stack.2.3 JDBC 10.1.6 IAS Oracle_home: 8. 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.1.0 & 12.0) Fusion Middle Ware OHS 10.34 fork) oc4j -eliminated-a Forms 10.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 differences 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.6x.7.2. 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. 11i Database 9iR2 (9.19 fork) jserv modplsql Forms 6i Reports 6i Tools Oracle_home: 8. 3 .0.1 10gR2 (10.0.2. Overview 4 . toad. To enable Valid Node Checking. or ADI from a windows desktop is not recommended on production databases.X. discoverer. This section contains security recommendations for the database TNS Listener. concurrent managers.X. If the profile option “SQLNet Access” (FND_SQLNET_ACCESS) is set to “ALLOW_RESTRICTED” at the Site level when AutoConfig is run on the 5 . HARDENING HARDEN OPERATING ENVIRONMENT Follow the hardening instructions for “Operating Environment Security” on page 33. If implemented.. hostname.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.X. the desktop cannot use DHCP (unless the DHCP server is configured with address reservation).invited_nodes = ( X.. use of SQLNet desktop clients such as sqlplus. ) The first parameter turns on Valid Node Checking.ora: tcp. We recommend that only trusted servers be allowed to make direct database connections. We recommend using a whitelist of IP Addresses that are allowed to make a TCP connection to the database listener. set the following parameters in $TNS_ADMIN/sqlnet. . by default). When the Listener receives a connection request (tcp port 1521. Replace X. Note. central administrator machines and any remote monitoring tool that uses SQL*Net. terminal servers. AutoConfig supports automated configuration of this setting. NETWORK ADD IP RESTRICTIONS OR ENABLE VALID NODE CHECKING Valid Node Checking allows or denies access from specified IP addresses to Oracle services. sqldeveloper. The next parameter specify the IP addresses or hostnames that are permitted to make network connections to the database. forms servers.X. it starts up a new database process and establishes a connection between the client and the database.validnode_checking = YES tcp. Middle-tier applications include web servers.X.X with the middle-tiers’ IP addresses. Oracle TNS Listener Security database server.1 “Enabling SSL in Release 12“ contains the instructions on how enable this encryption. 6 . listener specific password. set the following parameter: CONNECT_TIMEOUT_$ORACLE_SID = 10 For example. For more information. However starting with database release 10g the listener password is no longer required as the listener implements OS-Authentication. MOS Note 376700. 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.or the Oracle Applications Concepts manual. AutoConfig will add IP restrictions to sqlnet. in seconds. Use the parameter CONNECT_TIMEOUT to specify the amounts of time. All client code already has the encryption code available. refer to MOS Note 387859.ora.ENCRYPTION_TYPES_SERVER= (AES256. SPECIFY CONNECTION TIMEOUT In $TNS_ADMIN/listener. for the Oracle Listener to wait for the connection from a client to complete. this means that the OS user that owns the software installation can start and stop the listener without requiring an additional.ENCRYPTION_SERVER = REQUIRED SQLNET. In Release 12 this is much simpler than in 11i.1: Using AutoConfig to Manage System Configurations with Oracle Applications Release 12 .ora. so we can simply make the database server require encryption and all the clients will follow. For example adding these 3 lines to $TNS_ADMIN/sqlnet_ifile. The list of host will be all those from the FND_NODES table that are registered as an EBS node. AES192. Note that network encryption is an optional (extra cost) database feature available as part of the Advanced Security Option.ora will do the trick: SQLNET.CRYPTO_SEED = somelongandrandomstringforyourdeploymentUpTo70characters We need to allow both the AES and the triple DES ciphers as the OCI and JDBC client side code varies in their cipher support. Setting a password prevented remove administration (shutdown) of the listener. For these database releases you should only set a password if remote admin access to the listener configuration is required. 3DES168) SQLNET. AUTHENTICATION ENABLE TNS LISTENER PASSWORD (ONLY IF REQUIRED) For terminal releases of the 9i database series setting a password for the Listener was one of the most important hardening procedures. CONNECT_TIMEOUT_PRD12 = 10 Where PRD12 is the value of the ORACLE_SID in this example. or set the autoconfig variable s_enable_listener_password to ON and run Autoconfig on the database server. LSNRCTL> set current_listener VIS12 Current Listener is VIS12 LSNRCTL> change_password Old password: -. This may “break” some monitoring and remote administration tools. if they do not expect to provide a password. then change the password.ora: #----ADDED BY TNSLSNR 13-JAN-2007 11:47:56--PASSWORDS_VIS12 = D911537D50B15546 #-------------------------------------------- To undo these steps: 1.2. secure password Reenter new password: -. 7 .ora and remove the PASSWORDS_<listener> line 3. These instructions assume that the listener name is VIS12.ora. set the following parameter: ADMIN_RESTRICTIONS_<listener>=ON For example. Listener Parameter File /x/db/tech_st/10. Edit listener.just hit return New password: -. Start the Listener control program: $ lsnrctl Set the current listener.new.Oracle TNS Listener Security If you decide to set a password for the listener follow the instructions below .new. Stop the tnslsnr process (using lsnrctl or use ps to find the pid and kill to kill it) 2. 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. password protecting the TNS Listener has the following effects: The Listener process requires a password to list SERVICES or STATUS.ora The command completed successfully This added the following lines to listener. AUTHORIZATION ENABLE ADMIN RESTRICTIONS In $TNS_ADMIN/listener.0/network/admin/VIS12_dbs01/listener. Restart the listener (using lsnrctl start) Note. The default listener name for oracle databases in general is “LISTENER” while for EBS databases it is set to the SID of the database. 2. 8 . AUDIT ENABLE TNS LISTENER LOGGING To enable logging. all the set commands in lsnrctl are disabled and the only way to change the configuration is to edit the listener. in $TNS_ADMIN/listener.0/network/admin/VIS12_dbs01 LOG_FILE_VIS12 = VIS12 Where VIS12 is the LISTENER_NAME. This is done by default in Release 12.Oracle TNS Listener Security ADMIN_RESTRICTIONS_VIS12=ON where VIS12 is the name of the listener (equal to ORACLE_SID in EBS) Note. when ADMIN_RESTRICTIONS is ON.ora file. LOG_STATUS = ON LOG_DIRECTORY_VIS12 = /u/db/tech_st/10. AutocConfig can set this if you set the AutoConfig variable s_admin_restrictions to ON and run AutoConfig on the database server.ora set the following parameters: LOG_STATUS = ON LOG_DIRECTORY_$ORACLE_SID = $TNS_ADMIN LOG_FILE_$ORACLE_SID = $ORACLE_SID For example. To disable XDB.dispatchers='(PROTOCOL=TCP) (SERVICE=sidXDB)' REVIEW DATABASE LINKS Review database links in both production and development environments and drop those that are not required in your environment. some of these settings may have been set by default and all you have to do in that case is verify that the settings are as described here.ora contains: REMOTE_OS_AUTHENT=FALSE 9 . Oracle E-Business Suite does not require these services. Make sure init. the TNS Listener process listens on two additional TCP ports: 2100 for ftp access and 8080 for http access.ora that reads *. AUTHENTICATION Middle-tier applications logon to the database through application schemas rather than end-user accounts. Some individuals (IT Administrators) may require direct access to the application database via their own schema. REMOVE OPERATING SYSTEM TRUSTED REMOTE LOGON This setting prevents the database from using an insecure logon protocol. they should be disabled. DISABLE XDB To support XDB. HARDENING HARDEN OPERATING ENVIRONMENT Follow the hardening instructions for “Operating Environment Security” on page 33.Oracle Database Security Oracle Database Security DATABASE TIER Listener RDBMS ORACLE HOME RDBMS This section contains security recommendations for the Database. and how you arrived at that version. remove or comment out the line in init. Note that depending on the version you are running. open schemas with default passwords.Oracle Database Security IMPLEMENT TWO PROFILES FOR PASSWORD MANAGEMENT The database provides parameters to enforce password management policies. 2. 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. some of the database password policy parameters could lock-out the E-Business Suite. especially for a database to be used in a production environment. For more information on profiles. This is really handy as there are more than 200 of them. see CREATE PROFILE in the Oracle SQL Reference documentation. 3. use standard database commands to change a password: SQL> alter user <SCHEMA> identified by <NEW_PASSWORD>. Patch 4926128 contains a SQL script that will list all open accounts with default password in your database. 10 . Default schemas come from different sources: 1. 5 and 6). and they should be changed. 5.sql script. 4. However. For the schemas in categories 4. category six (6) schema passwords may be changed en masse using FNDCPASS. CHANGE DEFAULT INSTALLATION PASSWORDS Following an installation. These accounts and corresponding passwords are well-known. 2 and 3. 5 and 6. run the AD adutconf. $ FNDCPASS APPS/<apps_pwd> 0 Y SYSTEM/<system_pwd> ALLORACLE <NEW_PWD> To determine which schemas are managed by E-Business Suite (categories 4. FNDCPASS accepts a keyword ALLORACLE forcing a change of all managed (category 6) schemas to the new password. use the application password change tool FNDCPASS or AFPASSWD: $ FNDCPASS APPS/<apps_pwd> 0 Y SYSTEM/<system_pwd> ORACLE <SCHEMA> <NEW_PWD> To save time. Assign middle-tier application schemas to the first profile and all accounts used by administrators to the second profile. 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. 6. “Appendix C: Database Schemas found in Oracle E-Business Suite” on page 47 contains a list of the schemas by category. Create two database profiles: one for middle-tier application schemas and one for human beings. instructions and notes for managing schema passwords. the application database instance contains default. we make specific recommendations for or against using certain management features depending upon schema type. Because of this. AFPASSWD is documented in the “Oracle E-Business Suite System Administrator’s Guide 12.ora parameter _TRACE_FILES_PUBLIC grants file system read access to anyone who has activated SQL tracing.Oracle Database Security Note that in 12.. False is the default for the 10g database. AUTHORIZATION RESTRICT ACCESS TO SQL TRACE FILES The init. the new utility does not require passwords on the commandlin. 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. AFPASSWD only prompts for the passwords required for the current operation. Oracle E-Business Suite maintains some disk files and needs this parameter set. Set this to its default value of False. allowing separation of duties between application administrators and database administrators.ora parameter REMOTE_OS_ROLES to False to prevent insecure remote roles.<dir2>.sql. UTL_FILE_DIR = <dir1>.2 a new command line utility AFPASSWD is available to replace FNDCPASS.. This also improves interoperability with Oracle Database Vault.1. APPLSYSPUB EXECUTE ON FND_DISCONNECTED EXECUTE ON FND_MESSAGE EXECUTE ON FND_PUB_MESSAGE EXECUTE ON FND_SECURITY_PKG 11 . 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. like FNDCPASS AFPASSWD is installed on the application tier and require the libraries from the tools Oracle home.<dir3>. O7_DICTIONARY_ACCESSIBILITY = FALSE REVOKE UNNECCESSARY GRANTS GIVEN TO APPLSYSPUB The following table lists the privileges that should be granted to the APPLSYSPUB schema. _TRACE_FILES_PUBLIC=FALSE REMOVE OPERATING SYSTEM TRUSTED REMOTE ROLES Set the init. These are set in <FND_TOP>/admin/sql/afpub.1”. AUDIT_FILE_DEST = /u01/logs/db/audit Restart the database for these parameters to take effect. Oracle automatically creates an operating system file as an audit record when a user logs in as SYSDBA or as INTERNAL. Consult with the Applications Database Administrator before setting this value to TRUE. the database places audit records in directory /u01/logs/db/audit. set AUDIT_TRAIL to DB. 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. In addition. 12 . you should understand the implications of privileges on custom objects granted to PUBLIC or a role. OS or TRUE. whether or not AUDIT_TRAIL is enabled. CONFIGURE THE DATABASE FOR AUDITING In init. Note. Release 12 Rapid Install has a clean APPLSYSPUB by default. the database generates some audit records by default.ora. When set to OS. AUDIT This section describes the auditing capabilities available in Oracle database for Oracle E-Business Suite. To revoke unnecessary privileges granted to APPLSYSPUB schema. For example. When not set. AUDIT_FILE_DEST defaults to $ORACLE_HOME/rdbms/audit. These recommendations should not have a measurable performance impact. In this example. see patch 3763612. login as SYSTEM and issue the following query: SELECT * FROM dba_tab_privs WHERE grantee ='APPLSYSPUB'.Oracle Database Security APPLSYSPUB 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 SELECT ON FND_LANGUAGES_VL SELECT ON FND_LOOKUPS SELECT ON FND_PRODUCT_GROUPS SELECT ON FND_PRODUCT_INSTALLATIONS To check permissions. CREATE ROLE by ACCESS. SYSTEM GRANT by ACCESS.AUD$ table. ALTER SYSTEM by ACCESS. enable three other audit events: create database link. Oracle E-Business Suite dynamically creates. ALTER ANY ROLE by ACCESS. alter system and system audit. PUBLIC DATABASE LINK. This file contains the operating system user and terminal ID. PUBLIC SYNONYM by ACCESS. To audit schema changes.Oracle Database Security 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. Auditing these other actions provides little meaningful information. SYSTEM AUDIT. retrieve audit records from the SYS. DROP ANY ROLE by ACCESS. these changes may indicate inappropriate or malicious activity. To audit the last three events. SYSOPER by ACCESS. By auditing database sessions. -------------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. password guessing attacks on an application schema).) on a regular basis. etc. alters and drops objects (tables. PROFILE by ACCESS. The contents can be viewed directly or via the following views: DBA_AUDIT_EXISTS DBA_AUDIT_OBJECT 13 . 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. To audit sessions. packages. The remaining audit options generate significant entries of little value. AUDIT OTHER ACTIVITIES To complete the recommended auditing. login through sqlplus as SYSTEM and issue the following command: SQL> audit user. SYSDBA by ACCESS. AUDIT DATABASE SCHEMA CHANGES Audit any changes to the standard Oracle E-Business Suite database schemas or creation of new schemas. If AUDIT_TRAIL is set to DB. review audit records stored in the file name in AUDIT_FILE_DEST. suspicious connections to highly privileged schemas may be identified. As rare events. REVIEW AUDIT RECORDS If AUDIT_TRAIL is set to OS. ALTER DATABASE by ACCESS. index. login through sqlplus as SYSTEM and issue the following command: SQL> audit session. 14 . Time the action occurred. Backup the audit file before purging. Consider storing audit records in a separate system for analysis and reporting. Restrict audit trail access appropriately. EXECUTE). DELETE. begin by focusing on the following: Username Terminal Timestamp Object Owner Object Name Action Name Oracle Username. SELECT. MAINTAIN AUDIT RECORDS Archive and purge the audit trail on a regular basis. UPDATE. Oracle’s Database Vault product can be used for this purpose. The name of the object that the user touched. SECURE AUDIT RECORDS Audit data may contain confidential or privacy related data. The database connection entries take up significant space. Machine from which the user originated. at least every 90 days. The action that occurred against the object (INSERT. The owner of the object that the user touched.Oracle Database Security 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. AUTHORIZATION Within Oracle Application Server. 15 . HARDEN APACHE CONFIGURATION In previous versions of this document this section provided advice on hardening the apache configuration including steps such as Remove Application Server Banner Remove Unnecessary Directives Remove Unnecessary Modules Prevent Search Engine Indexing (robots.conf to limit web page access to a list of trusted hosts. HARDENING HARDEN OPERATING ENVIRONMENT Follow the hardening instructions for “Operating Environment Security” on page 33. The trusted. these pages must be restricted or disabled in a production system. PROTECT ADMINISTRATIVE WEB PAGES Use the apache configuration file trusted. In previous versions of this document this section provided advice on restricting access to a number of pages that are really useful when you need them but should be restricted to a number of fixed IP addresses such as the application tiers themselves and the administrator’s fixed IP workstation.Oracle Application Tier Security Oracle Application Tier Security APPLICATION TIER Apache OC4J ORACLE HOME iAS This section contains security recommendations for the Application Server.txt) In Release 12 these steps have already been performed in the AutoConfig configuration templates. While useful for debugging. These pages offer information about various services.conf file contains the following content. a number of web pages provide administrative and diagnostics functionality. the server’s state and its configuration. however in current configuration files these have already been blocked in trusted. OHS also includes ModSecurity. you can add them to a customized version of the autoconfig template for trusted.conf or to custom. <Location "uri-to-protect"> Order deny. refer to MOS Note 387859.allow Deny from all Allow from localhost <list of TRUSTED IPs> </Location> The section listed a specific set or URLs to be so restricted. as is done by default.Oracle Application Tier Security Replace “uri-to-protect” with the path of the page you wish to protect The <list of TRUSTED IPs> is being replaced with the value of the AutoConfig variable s_admin_ui_access_nodes which you should set to the list of host machines from which administrators connect.1 “Using AutoConfig to Manage System Configurations with Oracle Applications Release 12”. When activated.conf. If you find other pages that you wish to place similar restrictions on. AUDIT CONFIGURE LOGGING Oracle Application Server respects Apache’s logging parameters. For more information. custom. This may be useful for diagnostics purposes but should not be done on production systems as the POST payload from login pages will include the username and password of the applications users.conf is a file for your own additions to the apache configuration. it will never be overwritten by AutoConfig. 16 . ModSecurity can be configured to log the requests including POST payloads.conf. the server logs data about all web access to the system. JAVA_TOP. JRE_TOP. PORTAL_TOP. HTML_TOP. STRIKE PASSWORDS FROM ADPATCH LOGS To stop adpatch from logging passwords.Oracle E-Business Suite Security Oracle 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. use the following flag: adpatch flags=hidepw 17 . PRODUCT_TOPS ORACLE HOME Tools This section contains security recommendations for the Oracle E-Business Suite. HARDENING HARDEN OPERATING ENVIRONMENT Follow the hardening instructions for “Operating Environment Security” on page 33. 2/forms/server/default. This document describes the role of DMZs. The UTIL_HTTP PL/SQL client in the database does not currently support TLS. In Release 12 the Forms parameters are set in the configuration file: /x/inst/apps/VIS12_dbs01/ora/10. 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. When set to N. refer to 376700. Basically that means avoid SSLv2 and all ciphers with a key size less than 128 bit. external responsibilities. email notifications contain an access key. This can be done by enabling these settings in httpd. refer to Oracle Workflow Administrator's Guide.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.1 for our advice for deploying external EBS products to the internet. 18 . URL firewall and reverse proxies in a secure external EBS deployment.Oracle E-Business Suite Security SET WORKFLOW NOTIFICATION MAILER SEND_ACCESS_KEY TO N When SEND_ACCESS_KEY is set to Y.1 “Enabling SSL for Oracle Applications Release 12”. The key allows the user to access the Notification Details web page directly without authenticating. AVOID WEAK CIPHERS AND PROTOCOLS FOR SSL (HTTPS) You should adjust the protocols and ciphers used by apache SSL to avoid weak ciphers and protocols. Set SEND_ACCESS_KEY to N to prevent inclusion of the key with the Notification Detail link. For more information. you should consult MOS Note 380490. external web-tiers.conf SSLProtocol -all +TLSv1 +SSLv3 SSLCipherSuite HIGH:MEDIUM:!aNULL:+SHA1:+MD5:+HIGH:+MEDIUM Whether you will need SSLv3 depends on the HTTPS clients that must be able to access the server. SET TOOLS ENVIRONMENT VARIABLES You should prevent forms users from using the enter-query feature on a production system. an unauthenticated user who clicks on the notification link must sign on before accessing the Notification Details web page. Secure Sockets Layer (SSL) and its sucessor Transport Layer Security (TLS) are features that provide encryption of network traffic between the users browser and the EBS webserver.1. Configure your EBS environment to use HTTPS (HTTP over SSL/TLS) For information on setting up SSL with the Oracle E-Business Suite. the workflow notification email bypasses the E-Business Suite sign-on process. or has physical access to the host. The challenge is to make the server running the client/server program a trusted server. If the end user is running with Administrator or Power-User privileges. “Activate Server Security” on page 23 and “Create DBC files securely” on page 23. “INVALID” or “INTERNAL USER-NOLOGIN“. If the client/server tool uses DBC files these DBC files must be protected from the user while ensuring that the program run by the user has read access to the DBC file. AUTHENTICATION CHANGE PASSWORDS FOR SEEDED APPLICATION USER ACCOUNTS Oracle ships seeded user accounts with default passwords. The application-tier servers then make the database connections. . In the table an ‘x’ in the NoPwd column indicates that the account ships with an “impossible password”. deploy a remote server environment based on Windows Server Terminal Services. In the table an ‘x’ in the EndDT column means the account ship end-dated. Citrix or Tarantella (now Oracle Secure Global Desktop). Do not disable the GUEST user account Do not disable the SYSADMIN user account until you have created other accounts with similar privilege Note that we ship a script fnddefpw. For example this SQL statement will list users with in impossible password: 19 . The majority of the E-Business Suite functionality available to end users does not require direct database access but is web based. If you have a well considered need to connect to the production database directly from a desktop. You can easily identify the users with an impossible password as the length of the impossible password is shorter than the encrypted or hashed password. You disable an application user account by setting the END_DATE for the account. Change the default passwords immediately. this means that the password column in FND_USER contains a clear text string that is never a valid encrypted or hashed password. Thus it is not possible to login as this user. if you run this script as APPS it will list the seeded accounts that still have the default password. Web browser sessions connect to application-tier servers running Oracle 10g Application Server.unless you change the password! The “impossible” value can be “DUMMY”. trusted servers rather than on end-user desktop machines.sql. it does not qualify as “trusted”. some seeded accounts may or may not be disabled.Oracle E-Business Suite Security USE TERMINAL SERVICES FOR CLIENT-SERVER PROGRAMS Deploy client/server components requiring direct connection to the E-Business Suite production database on secured. Further details are provided in these sections “Add IP Restrictions or enable Valid Node Checking” on page 5. Depending on product usage. END_DT.5.ENCRYPTED_USER_PASSWORD from FND_USER where length(ENCRYPTED_USER_PASSWORD) < 30 order by 1. b.5. Required for Mobile Sales.0.[0-9]. Required for Sales Application.x Account Desupported Portal 3. Account AME_INVALID_APPROVER ANONYMOUS APPSMGR ASADMIN ASGADM ASGUEST AUTOINSTALL CONCURRENT MANAGER FEEDER SYSTEM GUEST IBE_ADMIN IBE_GUEST IBEGUEST IEXADMIN INDUSTRY DATA INITIAL SETUP IRC_EMP_GUEST IRC_EXT_GUEST MOBILEADM MOBILEDEV OP_CUST_CARE_ADMIN OP_SYSADMIN ORACLE12. Service.0 PORTAL30 PORTAL30_SSO STANDALONE BATCH PROCESS SYSADMIN WIZARD XML_USER Product / Purpose AME WF migration 11. Required for iStore. 20 .Oracle E-Business Suite Security select USER_NAME.x Account FND/AOL Application Systems Admin AD – Application Implementation Wizard Gateway Change Y Y N N Y Y Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y N Y Y Y Y Y Y Disable Y Y Y Y Ya Yb Y Y Y N Yc Yc Yc Y Y Y Y Y Y Y Y Y N Y Y Y N Y Y NoPwd EndDT x x x x x x x x x x a.10 FND/AOL – Anonymous for non-logged users Routine maintenance via concurrent requests Application Server Administrator Mobile gateway related products Sales Application guest user AD FND/AOL: Concurrent Manager AD – Supports data from feeder system Guest application user iStore Admin user iStore Guest user iStore Guest user Internet Expenses Admin AD iRecruitment Employee Guest Login iRecruitment External Guest Login Mobile Applications Admin Mobile Applications Development Customer Care Admin for Oracle Provisioning OP (Process Manufacturing) Admin User Owner for release specific seed data Desupported Portal 3. and Mobile Core Gateway components. c.9 to 11.0. while the system tracks individual user actions. Starting with 12. account lockout after too many failed logons and session inactivity timeout. b.4 it is possible to switch the EBS system to store hashed versions of the passwords instead. TIGHTEN LOGON AND SESSION PROFILE OPTIONS For local application users.0. 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. If you set this profile option monitor the FND_FAILED_LOGINS table. refer to MOS Note 376811. see MOS Note 4567166. UMX uses workflow to drive the registration process once a request has been submitted. Note: this process is irreversible. for the actual command and a list of client/server components that will need an update to work with hashed passwords. For more information on Single Sign-On deployments.Oracle E-Business Suite Security SWITCH TO HASHED PASSWORDS Traditionally Oracle E-Business Suite has stored the password of the application users (FND_USERS) in encrypted form. the profile option settings below support strong passwords. Setting automatic account locking after N failed attempts make for a simple denial of service attack.1 “Integrating Oracle E-Business Suite Release 12 with Oracle Internet Directory and Oracle Single Sign-On”. See UMX Documentation for more details. If your corporate password policy cannot be expressed using the above parameters you may implement a custom password validation function and register it with EBS. Profile Option Name SIGNON_PASSWORD_LENGTH SIGNON_PASSWORD_HARD_TO_GUESS SIGNON_PASSWORD_NO_REUSE SIGNON_PASSWORD_CASE SIGNON_PASSWORD_FAILURE_LIMIT ICX_SESSION_TIMEOUT SIGNON_PASSWORD_CUSTOM Recommendation 8 YES 180 Sensitive 5a 30 implement b a. the system cannot identify which user performs a function. CONSIDER USING SINGLE-SIGN-ON Oracle E-Business Suite Release 12 support integration with a Single Sign-On (SSO). To switch EBS to use hashed passwords you must use the FNDCPASS command line utility in MIGRATE mode. 21 . CREATE SHARED RESPONSIBILITIES INSTEAD OF SHARED ACCOUNTS When users share one account. See “Customize Password Validation” in the “Extra for Experts” section. preventing accountability. Users share the same functions or permission sets.1 “FNDCPASS Utility New Feature: Enhance Security With Non-Reversible Hash Password”. the password may be intercepted.3 it is possible to create an applications user (FND User) with the responsibility ”Concurrent Manager Operator” and use this user’s username and password start and stop the application services.sh with the -secureapps option and the script will prompt for the Application users username and password rather than the APPS username and password. For example [applmgr@app01]$ adstrtal.Oracle E-Business Suite Security CONFIGURE CONCURRENT MANAGER FOR SAFE AUTHENTICATION Concurrent Manager passes the APPS schema password to concurrent programs on the command line. To prevent username/password from being passed. With this change. To prevent this.1.sh -secureapps Enter the Applications username: CONCOPER Enter the Applications password: 22 . Concurrent Manager does not pass the username/password to the program. CONFIGURE CONCURRENT MANAGER FOR START AND STOP WITHOUT THE APPS PASSWORD Traditionally the operator starting and stopping the application services needed to know the APPS username and password in order to start the application services on an application tier that was running the Concurrent Manager.and assign the ”Concurrent Manager Operator” responsibility to this user On the application tier update the following 4 variables in the auto config context file Auto Config Variable s_cp_user s_cp_password_type s_cp_resp_shortname s_cp_resp_name Run auto config on the application tier(s) AppsUser FND New Value CONCOPER (or the one you created) Concurrent Manager Operator Following this change the application tier services can be started and stopped by calling adstrtal. Concurrent Manager leaves argument $1 blank.say CONCOPER . Enter ENCRYPT in the Execution Options field of the Concurrent Programs window when defining a concurrent program using this executable.sh and adstpall. define the concurrent program executable as a HOST program in the Concurrent Program Executable form. This is implemented by Creating a new user . Because some Operating Systems allow all machine users to read a program’s command line arguments. enter SECURE in the Execution Options field. This of cause means that the program will have to get the database credentials some other way if it needs to connect to the database. Starting with Release 12. ENCRYPT signals Concurrent Manager to pass the username/password in the environment variable FCP_LOGIN. Appropriate for machines completely under an administrator’s control. Any program which makes a SQLNet connection to the Oracle Applications database needs to be trusted at some level.Oracle E-Business Suite Security 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.--------------AUTHENTICATION SECURE * CREATE DBC FILES SECURELY Previous versions of this document documented how to create DBC files for the EBS application tiers using the AdminAppServer utility. This setting is controlled by the autoconfig variable “s_appserverid_authentication”.------------. Discoverer. Forms. However when creating DBC files for use by desktop installations or for other. Release 12 already does this automatically via AutoConfig so you should never have to do this manually. Examples of such external hosts are a webservice host or a BPEL service host. see System Administrators Guide. The application servers include Apache JSP/Servlet. Equivalent to OFF from a security perspective. OK for development systems without production data. Application Server Security has three states: OFF Inactivates Server Security. For details. you must use the AdminDesktop utility to create the DBC file. The Server Security feature ensures that FNDLogin connections originate from trusted machines. Administering Server Security.SERVER_ADDRESS from FND_NODES where SERVER_ADDRESS = '*' . only registered application servers and trusted code modules may connect. Not recommended for production systems. 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.SERVER_ID. all you should do is verify that the setting is set to SECURE. ON SECURE Recommended. Another way to verify that server security is set to secure is to run the following sql query while connected as APPS: SQL> select NODE_NAME. Creating DBC files for these external. Setup Server Security The application server security feature is activated by default. non-EBS tiers involves running AdminDesktop on the EBS tiers to create the DBC file copying the DBC file to the external tier 23 . non-EBS application tiers that must connect to the EBS database. NODE_NAME SERVER_ID SERVER_ADDRESS -------------. Server and code IDs are not checked. When creating DBC files make sure to make them IP address specific and that the filepermissions are set to 600 (-rw-------). where availability should be limited to a very few trusted users. Java Authentication and Authorization Service. There are several types of these sensitive pages in Oracle E-Business Suite.1 “Sensitive Administrative Pages in Oracle E-Business Suite” lists these forms. AUTHORIZATION REVIEW AND LIMIT RESPONSIBILITIES AND PERMISSIONS Some forms and pages in Oracle E-Business Suite allow a user to modify the functionality of the applications by specifying values such as SQL statements. HTML strings. and Utilities for Oracle E-Business Suite".and documentation of any patches needed .1 "AppsDataSource. They can be grouped them into the following categories: Oracle Forms Controlled by Function Security HTML Pages Controlled by Function Security Functionallity Controlled by Profile Options Pages Controlled by JTF Permissions and Roles MOS Note 1334930.Oracle E-Business Suite Security configuring the external tier to use the DBC file as a data source Use of AdminDesktop . pages. and operating system commands or environment variables. profile options and includes a description of how to determine who has access by interactively using UMX User Management or by running SQL scripts. Most of these screens are accessible only from system administration menus and responsibilities. and they are controlled by different mechanisms.is can be found in MOS Note 974949. Profile Option AuditTrail:Activate Concurrent:Report Access Level Sign-On:Notification Utilities:Diagnostics FND:Diagnostics FND Validation Level FND Function Validation Level Framework Validation Level Restrict Text Input Profile Option Name AUDITTRAIL:ACTIVATE CONC_REPORT_ACCESS_LEVEL SIGNONAUDIT:NOTIFY DIAGNOSTICS FND_DIAGNIOSTICS FND_VALIDATION_LEVEL FND_FUNCTION_VALIDATION_LEVEL FRAMEWORK_VALIDATION_LEVEL FND_RESTRICT_INPUT Yes User Yes No No Error Error Error Y Suggested MOS Note 946372. You should eliminate or minimize access to these screens in a production system and know exactly which users have access to these screens. These screens may constitute a security risk if used in an unauthorized fashion. 24 . SQL fragments such as WHERE clauses. SET OTHER SECURITY RELATED PROFILE OPTIONS Refer to the table below and set the suggested values for the profile options.1 “Secure Configuration of E-Business Suite Profiles“ describes the Diagnostics and Validation profiles. e. 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). 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. the system determines which responsibilities are valid for that user. These have access to a small set of responsibilities. administrative 2. Setting the Server Trust Level for a Server To assign a trust level to a Web server. Three trust levels are supported: 1. as well. the Web server is assumed to have a trust level of 1 (i. This indicates that only Web servers with the same or greater ordinal trust level may access that responsibility. set the Application Server Trust Level profile option value for that responsibility to be the number 1. If no value is set for NODE_TRUST_LEVEL. administrative). The system returns only responsibilities appropriate for the Web server Trust Level. external Typically. customers or employees outside of a company’s firewall connect to external servers. Restricting Access to a Responsibility When a user logs on to Oracle Applications via a Web server.Oracle 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. which can be accessed from that particular Web server. and of those responsibilities. 2 means normal and 3 means external. Lastly. This option. 2 or 3. Users can see this profile option. 25 . To restrict access to a responsibility. are considered secure and have full application access with few limitations. The number 1 means administrative. but they cannot update it. the administrator sets the NODE_TRUST_LEVEL profile option. administrative web servers are used exclusively by system administrators. To avoid having to set the NODE_TRUST_LEVEL for every single Web server. Profile Option . 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). Normal web servers are those used by employees within a company’s intranet and requiring non-administrative responsibilities. normal 3.. 2 or 3. a server-based 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. administrators may wish to set the NODE_TRUST_LEVEL profile to some default level of trust at the site level. can be set to either 1. For example. RETRIEVE AUDIT RECORDS USING REPORTS Oracle E-Business Suite ships standard reports to access signon.1 “Oracle E-Business Suite R12 Configuration in a DMZ (external deployment)”. At site level. It tracks Web-based and Form-based accesses across technology stacks and correlates them for each user session. See MOS Note 402116. Responsibility and Form.1 for more detailed information about Page Access Tracking. It also suggests which common application objects like foundation objects. Signon Audit Concurrent Requests Signon Audit Forms Signon Audit Responsibilities Signon Audit Unsuccessful Logins Signon Audit Users 26 . Recommend Form MONITOR SYSTEM ACTIVITY WITH OAM Oracle Application Manager (OAM) provides screens for monitoring current and past system activity. At this setting. users and responsibilities to audit. Regarding Page Access Tracking.Oracle E-Business Suite Security References For more information on how to enable and use the above security features. See OAM documentation for complete product information. User. It provides an explanation of the features available. unsuccessful signon. it tracks Oracle Applications usage statistics non-intrusively and with negligible performance impact. Often. Profile Option Name SIGNONAUDIT:LEVEL Description Set at site-level to track actions starting when the user logs on. configuration steps and best practices for auditing. Monitoring features include current and historic user activity down to the page access level and current and historical Concurrent Manager activity. Refer to the Oracle Applications System Administrator's Guide for more information. responsibility usage.FND_LOGIN_RESPONSIBILITIES and APPLSYS. AUDIT This section describes how to configure and use Oracle E-Business Suite audit features. respectively.FND_LOGIN_RESP_FORMS. This feature is also used in setting up External Webtiers in a DMZ for intenet exposure. APPLSYS. SET SIGN-ON AUDIT LEVEL The valid settings for the profile option SIGNONAUDIT:LEVEL are None. Access these reports through the system administrator responsibility. responsibility selections and form accesses to APPLSYS. In addition. OAM provides a framework extensible for running custom OAM reports.FND_LOGINS. E-Business Suite deployments do not take advantage of the auditing features due to the perceived complexity and performance issues. form usage and concurrent request usage. the system logs all user sign-ons. refer to Oracle Applications System Administrator's Guide. Properly configuring auditing and limiting auditing to appropriate tables should not have a measurable performance impact. see MOS Note 380490. set this profile option to Form to enable as much auditing as possible. REVIEW DATA TRACKED (NO REPORTS AVAILABLE) Some data tracked by the system do not have associated reports.FND_LOGIN_RESPONSIBILITIES APPLSYS. Who Columns For most E-Business Suite tables.Oracle E-Business Suite Security RETRIEVE AUDIT RECORDS USING SQL The system stores end-user access data in the following tables. Run this concurrent program at least once a week and retain 14 to 90 days of records. Nevertheless. database rows are updated with the creation and last update information. only the last update to record is saved. 27 . retaining 30 to 90 days of records. Note. Periodically archive and truncate the FND_LOGIN% tables. enable Oracle E-Business Suite Audit Trail. 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. Develop SQL scripts to query these tables to generate reports. The current program purges all audit records older than a user supplied date. APPLSYS. Run this concurrent program between once a week and once a month.ICX_FAILURES PURGE AUDIT RECORDS Purge end-user access data using the Purge Signon Audit Data concurrent program. To save the entire history of a row.FND_UNSUCCESSFUL_LOGINS FND_CONCURRENT_REQUESTS ICX. 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. these audit records contain valuable information.FND_LOGIN_RESP_FORMS APPLSYS.FND_LOGINS APPLSYS. Set audit group to Enabled Requested 4. Auditing transactional data may cause significant performance degradation. This functionality cannot be disabled. Tables with more than a few changes an hour should not be considered for row level auditing.ICX_FAILURES tables. Audit Trails. it creates two views for each column with the names _AC# and _AV# where # is a sequential number.FND_UNSUCCESSFUL_LOGINS and ICX. Navigate through Security -> AuditTrail -> Tables to set columns in tables to be audited 5.Oracle E-Business Suite Security Unsuccessful Logins The system automatically stores unsuccessful logon attempts in the APPLSYS. Set System profile option AuditTrail: Activate to True 2. Auditing database row changes is performance intensive. Limit auditing to non-transactional data. ALR_ALERTS FND_AUDIT_COLUMNS FND_AUDIT_GROUPS FND_AUDIT_SCHEMAS 28 . Navigate through Security -> AuditTrail -> Install to set schemas for auditing 3. which activates auditing. Failed Forms logins are logged only to the FND_UNSUCCESSFUL_LOGINS table. Navigate through Security -> AuditTrail -> Groups to create audit groups and set tables to be audited. This feature keeps a complete history of changes made at a table and column level. In addition. 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. CONFIGURING AUDIT TRAIL To enable Audit Trail. run the AuditTrail Update Tables concurrent program. a concurrent program creates a shadow table and places triggers on the columns to be audited. ADVANCED AUDIT Oracle E-Business Suite implements its own auditing mechanisms. Plan and consult with a DBA before enabling Audit Trails.a table whose name is the instance table’s name appended with _A. The ICX_FAILURES table holds more information than the FND_UNSUCCESSFUL_LOGINS. This program creates triggers on each audited column in the original table. When initialized. Both the FND_UNSUCCESSFUL_LOGINS and ICX_FAILURES tables contain unsuccessful logins via the Personal Home Page (Self Service/Web Interface). The triggers store column changes in the shadow table -. follow these steps: 1. 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. 6. 4. Prior to purging. 5. Run the Audit Trail Update Tables Report. PURGE AUDIT RECORDS Purge the audit trail information on a regular basis. Purge the data from the shadow table. Select the Security Audit group and set the group state to Disable – Purge Table.Oracle 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 29 .1– Troubleshooting (Audit Trail) MOS Note 60828. Select Security -> Audit Trail -> Groups. Oracle does not ship Audit Trail reports. disable the Audit Trail.1 – Overview of Oracle Applications AuditTrails MOS Note 69660. 2. Run the Audit Trail Update Tables Report REFERENCES ON ORACLE E-BUSINESS SUITE AUDITING Oracle10gR2 Administrator’s Guide – Auditing Database Use Oracle11gR1 Administrator’s Guide – Auditing Database Use Oracle Applications System Administrator’s Guide – User and Data Auditing MOS Note 105624. 7. Use the following procedure to purge audit data: 1. select Security -> Audit Trail -> Groups. Select the Security Audit group and set the group state to Enable. 3. As System Administrator. Use shadow tables and views for accessing the records. Oracle E-Business Suite Security 30 . Desktop Security Desktop Security DESKTOP TIER Web Browser Forms Java applet This section contains security recommendations for the Desktop used to run web browsers that connect to Oracle E-Business Suite. or use a master password for the saved password store. 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. 31 . they often include security bug fixes. Check browser for built-in safety features. change the browser’s autocomplete settings. HARDENING CONFIGURE BROWSER See MOS Note 389422.including Java TURN OFF AUTOCOMPLETE For kiosk machines. Also consider disabling the “remember password” function. for privacy and security reasons this feature should be disabled.1 “Recommended Browsers for Oracle Applications 12. Although convenient for frequently accessed pages. Users are recommended to use the password-locked screen savers feature on all PCs.0“ for information about securing the desktop. SET POLICY FOR UNATTENDED PC SESSIONS People may attempt to access unattended workstation while the user is still logged into the system. UPDATE BROWSER Update browser when new versions are released. Organizations should set a corporate policy for handling unattended PC sessions. Update browser plugins . Desktop Security 32 . 8. 3. group and modes of the Oracle files created upon installation are set to allow minimum privilege. Protect the $ORACLE_HOME/rdbms/admin directory including catalog.sql.courtesan. Find more information about sudo at http://www. 5. Set file permissions for listener. $chown -R <oracle> $ORACLE_HOME $chgrp -R <dba> $ORACLE_HOME 6. Set file permissions for the database data files*. Oracle recommends that the SUID and SGID bits to be removed from binaries shipped by Oracle. the group and owner are for illustration only. Note. 2. the correct group and owner should be substituted. CLEANUP FILE PERMISSIONS Refer to the product installation documentation for the complete instructions on setting file permissions. HARDENING CLEANUP FILE OWNERSHIP AND ACCESS 1. Note. Set all other directories in $ORACLE_HOME to 0750 or less.Operating Environment Security Operating Environment Security The environment in which Oracle Applications run contributes to or detracts from overall system security. Better yet. Set the permissions on $ORACLE_HOME/bin to 0751 or less. This section contains security recommendations for tightening Oracle file system security along with more general advice for overall system hardening. Most operating systems now ship with sudo.ora to 0644. Instead. 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. Verify that set userid (SUID) and set group id (SGID) are not set on binaries. Another possibility is using Oracle Enterprise Manager with the EBS plugin. require that legitimate users connect to their own accounts and su to the oracle account. Prevent remote login to the oracle (and root) accounts.sql and backup scripts. Set file permissions for tnsnames. catproc. A typical mistake is to install the executables in user oracle’s directory but owned by root.ora and sqlnet. On the application tier ensure that the DBC files $FND_SECURE/*.dbc have mode 600. the SUID and/or SGID bit must be set on the Oracle database executable in $ORACLE_HOME/bin. In general. The directory $ORACLE_HOME/bin contains Oracle executables. use sudo to restrict access to executables.dbf to 0640. 33 . Ensure that the owner. 2. This may also apply for any third party products running on the db tier. Warning: If Concurrent Manager runs on the Database tier and using the BEQ adapter to avoid TCP cost.com/sudo. 3.ora to 0600. Check that the operating system owner of these executables matches the operating system user under which the files have been installed. The following commands make this change. On Unix systems: 1. 4. this limits access to the Oracle user and its group (probably DBA). 7. X Server a. A production Database does not require access to an X server. rcp and ftp. 1. block all RPC ports on the router. Oracle Installer requires access to the X server which in turn may require access to an X font server. 2.0. create access control lists in /etc/ssh/sshd. Printers Applications may require access to printers – normally via the lpd interface on port 515/TCP.conf to limit which users can connect to the local machine. E Mail Applications may require access to a SMTP Mail Transfer Agent (SMTP MTA) typically sendmail or qmail on port 25/TCP. FILTER IP PACKETS IP filtering helps to prevent unwanted access. 4. For software solutions. On the host. Firewalls may be software or hardware based. If possible. Disabling unused services reduces securing and monitoring work. Monitoring agents – for monitoring operating system. 2. use a firewall machine or router with firewalling capabilities. Do not assume that using Network Address Translation (NAT) substitutes for a firewall. This replaces telnet. rlogin. CRON – for operating system cleanup and log file rotation 3. opening only those ports known to be required. NTP (Network Time Protocol) – for synchronizing the clock on the UNIX hosts to provide accurate audit records and simplify trouble-shooting. Typically the administrator’s workstation can run the X Server and grant access to the EBS servers during installation.1). A firewall machine can filter packets and/or be a proxy server.conf. 3. Application middle-tiers and web-tiers do not require an X server. Although not required by the E-Business Suite. On the internet or large network. If only outbound email is required in your environment make the mail daemon listen on the localhost interface (127. Unless running NFS between networks. It provides a point of resistance by protecting inside systems from external users. typically notifications from the workflow system. Better yet. limit access to services users need and make those services as secure as possible. c. Filtering out unused services at the firewall or router level stops infiltration attempts earlier in the process.0. rsh. 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. Turn off unused services in /etc/inetd. restrict access to the operating system users who absolutely need the printing facility from the shell. database and application components for health and security NETWORK To secure the network. A firewall machine sits between the internet and the intranet or the intranet and the internal servers.Operating Environment Security LOCKDOWN OPERATING SYSTEM LIBRARIES AND PROGRAMS The database and applications require that the underlying operating system provide certain services. dedicate a machine to be the firewall. b. the following services may provide operational convenience: 1. This is required for outbound emails. Remote Access Use secure shell (ssh) to access middle-tier and database hosts. implement a default OFF policy. 34 . On the system side.Operating Environment Security PREVENT SPOOFING To prevent hostname spoofing. Always logout of root shells.*’ files SHOULD have 700 or 600 permissions. change the root password every three (3) months and whenever an administrator leaves company. do not create root's temporary files in publicly writable directories. but often not practical. the easier it is to track changes. A password tester may check for these. for this reason. To avoid trojan horse programs. The minimal umask for root is 022 (rwxr-xr-x). AUTHENTICATION Good security requires secure accounts. 35 . To ensure that the passwords are not guessable. Snort is a capable and free IDS system. rsh and ftp send the passwords in clear text and. MONITOR FOR ATTACKS Consider installing an Intrusion Detection System (IDS). NEVER allow non-root write access to any directories in root's path. never leave root shells unattended. For example. If possible. The root ‘. RSH AND FTP DAEMONS Enforce the use of SSH (secure shell). should have UID 0. turn off source routing and filter packets originating outside the network that have source IP address from the inside network. always use full pathnames including aliases. telnet. In addition. should not be used. change passwords from time to time. Limit root to console login. this reduces the dependency on DNS for the core system. The root password must be a strong. Root. SSH provides encrypted traffic to prevent snooping.*’ files for security holes. Root should NEVER have “. Often. CONFIGURE ACCOUNTS SECURELY Make sure that all OS accounts have a non-guessable password. VERIFY NETWORK CONFIGURATION Use scanning tools to find common security violations. and only root. In addition. A umask of 077 (rwx------) is best. ELIMINATE TELNET. children's names or a hobby. use crack or john-the-ripper (password cracking tools) on a regular basis.” in path. For the production system consider enumerating all hosts that are part of the EBS instance in the hosts file on each system. LIMIT ROOT ACCESS The fewer people with root access. Check root ‘. people use passwords associated with them: license plate numbers. only use fully qualified hostnames or IP addresses in system files. non-guessable password. only (specified in /etc/security). Automatically disable accounts after several failed login attempts. system files/directories). MAINTENANCE Good security practice does not end after installation. Monitor log files including btmp. Require strong passwords and.delete or lock accounts no longer required. When creating the /etc/exports file. etc. use limited access flags when possible (such as readonly or nosuid). Install Tripwire to detect changes to files. Keep up to date on security issues by subscribing to security mailing lists.Operating Environment Security MANAGE USER ACCOUNTS Do not share user accounts. sys. a restricted shell. Use a checksum to verify they have not been altered. Most other device files should be unreadable and unwritable by regular users. adm). 36 . wtmp. SECURE FILE ACCESS Create minimal writable file systems (esp. Run security software and review output. Add directories for specific groups. uucp. Consider setting up automatic email or paging to warn system administrators of any suspicious behavior. Verify user accounts . in some cases. syslog. Also check the snort logs. /dev/tty and /dev/console should be world writable but NEVER executable. Continuous maintenance tasks include: Install the latest software patches. SECURE EXECUTABLES Always get programs from a known source. Test the system with tools like NESSUS (network security) and CRACK (password checker). Install latest operating system patches. SECURE OPERATING SYSTEM DEVICES Device files /dev/null. reading security news groups and following the latest security procedures. Limit important file access to authorized personnel. AUTHORIZATION SECURE NFS Only run NFS as needed. daemon. Use setuid/setgid only where absolutely necessary. Remove or disable user accounts upon termination. Disable login for well known accounts that do not need direct login access (bin. Limit user file writes to their own directories and /tmp. sulog. lp. The interface requires three methods: 1. the validate() method returns False). Encryption of credit card numbers is one of many requirements for PCI PA-DSS compliance. indicating whether the user's password is valid or invalid. the E-Business Suite raises a Workflow event when the same user has multiple.security. The next user action returns the browser to a login screen indicating the session is invalid.Extras for Experts Extras for Experts Security policy must balance risk of attack.AppsPasswordValidation.1 “How to Implement (Signon Password Custom) Profile Option in Oracle Applications 11i / R12”. This functionality is disabled by default. If the name of the Java class is yourco. The feature is part of Release 12 but needs to be explicitly turned on. public String getErrorStackApplicationName() This method returns the application short name for the aforementioned error message.e.. set profile option SIGNON_PASSWORD_CUSTOM to the full name of the class. public boolean validate(String user. cost of defense and value of data protected. CUSTOMIZE PASSWORD VALIDATION If your corporate password policy cannot be expressed using the “Sign-On” parameters on page 21 you can implement a custom function for validating new passwords. 3.apps.security. 2. ENCRYPT CREDIT CARDS The Withe Paper in MOS Note 338756. then the value of SIGNON_PASSWORD_CUSTOM must be "yourco. this class must be loaded into the Application database using the loadjava command. After writing the customized password validator. DETECT AND PREVENT DUPLICATE USER SESSIONS When properly patched and configured. open sessions. This section contains recommendations that improve security. public String getErrorStackMessageName() This method returns the name of the message to display when the user's password is deemed invalid (i. but may not be appropriate for every deployment. Note. More details available in MOS Note 362663. To customize password validation create a Java class that implements the oracle.1 “Oracle Applications Credit Card Encryption“ describes the credit card encryption features available in Oracle E-Business Suite.PasswordValidation Java interface. The subscription calls a rule function that updates the ICX_SESSIONS table setting the DISABLED_FLAG='Y' for all other sessions for the user. User names appearing in the subscription's parameter list are excluded from this functionality.security.AppsPasswordValidation". Patch 2128669 contains an example demonstrating how to write a custom event and/or additional subscriptions. respectively.fnd. and returns True or 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. 37 . This renders the other sessions invalid. String password This method takes a username and password. Address. These copies are typically used for performance test by dbas or developers or to test upgrade/patching of the production database.1 should be incorporated in your local cloning procedures. ADVANCED SECURITY/TRANSPARENT DATA ENCRYPTION (ASO/TDE) Oracle Advanced Security Option provides transparent data encryption (TDE). See MOS 419475. such as mathematical modeling or files system interactions. This functionality exploits the ability of the Listener to issue operating system commands. MOS Note 376700.Extras for Experts ADVANCED SECURITY/NETWORKING OPTION (ASO/ANO) Oracle Advanced Security Option provides a single source of integration with network encryption.1 Using TDE Tablespace Encryption with Oracle E-Business Suite Release 12 Column level TDE has a number of restrictions related to data types and indexed columns. The steps in MOS 419475. The option protects the data a rest by encrypting the data stored in the database datafiles. Address. Oracle Advanced Security provides the following features: Data Integrity: Prevents data modification during transmission.1 Using TDE Column Encryption with Oracle E-Business Suite Release 12 828229.ora parameter file as (ADDRESS_LIST = (ADDRESS = (PRTOCOL = IPC) (KEY = EXTPROC)) 38 . HARDENING EXTERNAL PROCEDURE (EXTPROC) SERVICES The Oracle database uses the external procedure service to call external C programs. EBS Release 12 is certified with Column Encryption and Tablespace Encryption. PRACTICE SAFE CLONING In many production environments it is part of normal operational procedure to periodically create clones (copies) of production databases for various purposes. This extends the functionality of PL/SQL to routines that can be written in C to perform complex calculations. When these cloned copies of production databases are to be used outside the group of trusted production administrators there will be concerns about the confidentiality of the data contained in the database and data scrambling routines are typically run on the cloned copy before it is handed over to development The data scrambling protects the confidentiality of production data such as employee data (Name. To ensure the integrity of the production database you must also change all the passwords in the clone to ensure that it will not be possible to retrieve passwords from the cloned instance that could be used to compromise the production database either by gaining administrative access or by allowing someone to impersonate another user. Specifically. The option protects against threats to the security of distributed environments. Credit Card info) and other data considered confidential. Compensation details) customer data (Name. Data Privacy: Prevents data disclosure during transmission.1 “Removing Credentials from a Cloned EBS Production Database” for an example of how to remove production credentials and bootstrap new credentials in a cloned copy of your production database.1“Enabling SSL in Release 12” provides more information on using ASO/ANO to encrypt your Oracle E-Business Suite 12 network traffic. The external procedures are supposed to issue the commands to the Listener on a special IPC pipe named EXTPROC. See MOS Notes for details 732764. Tablespace TDE does not have these restrictions and does not increase the storage requirement. The specification exists in the listener. Social Security Number. Replace the $ORACLE_SID with name of the Oracle database instance (SID). the only limits on external procedures are the limits on what that account can do. Oracle Demand Planning Express implementation.ora to reflect the correct port for the new Oracle Listener.ora files are located. $ORACLE_HOME with the value of ORACLE HOME directory for this Listener and $TNS_ADMIN with the directory location of the Listener parameter files. 5. Give this user the operating system privilege to “Logon as a service.. c. Use a separate $TNS_ADMIN/sqlnet.ora file for this Oracle Listener. Oracle Email Center. Because it contains the password. If the Oracle Listener for PL/SQL EXTPROC has been configured with a TCP address.g. 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. one for the Oracle database and one for PL/SQL EXTPROC. The parameters appear in $TNS_ADMIN/listener. Modify the EXTPROC specific entry in $ORACLE_HOME/network/admin/tnsnames.ora and sqlnet. Because the Listener runs with the privilege of the operating system user. Before starting the Oracle Listener for PL/SQL EXTPROC. run the Oracle TNS Listener process as an unprivileged user and not as the Windows LOCAL SYSTEM user. Oracle InterMedia cartridges 2. 3. 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 privileges in the database (such as CREATE ANY LIBRARY). only the owner should read the file. 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.ora are set to 600.” 4.ora. but use a port other than the one the Oracle Listener for the database is using. To protect against some EXTPROC attack vectors: 1. $ORACLE_SID_EXTPROC = (ADDRESS_LIST = (ADDRESS= (PROTOCOL= IPC)(KEY= EXTPROC$ORACLE_SID)) ) SID_LIST_$ORACLE_SID_EXTPROC = (SID_LIST = (SID_DESC = 39 . 6. Create two Oracle TNS Listeners. b. EXTPROC LISTENER CONFIGURATION See below for the format of the dedicated EXTPROC Listener. Copy the listener. Remove EXTPROC specific entries from the Oracle Database Listener configuration files. On Windows platforms.Extras for Experts These external procedures operate by instructing the Listener to issue these operating system commands on their behalf. configure a TCP protocol address. Configure the Oracle EXTPROC Listener with an IPC protocol address only. The following Oracle E-Business suite components use EXTPROC services: 1. “nobody” on Unix).ora with the configuration of the Oracle Listener for PL/SQL EXTPROC into this other directory as well. 3. Restrict access to the Oracle Listener for PL/SQL EXTPROC only. Enable Valid Node Checking and restrict access to those network clients requiring EXTPROC. Store this file in any directory other than the one in which the database listener. If TCP connectivity is required. 2. This step may not be applicable for default E-Business Suite implementations. Ensure that the file permissions on separate $TNS_ADMIN/listener. Ensure that the Oracle Listener created for PL/SQL EXTPROC runs as an unprivileged operating system user (e. do the following: a. 0. Replace $ORACLE_SID with the name of the Oracle database instance (SID).5/network/admin LOG_FILE_VSEC_EXTPROC = VSEC_EXTPROC TRACE_DIRECTORY_VSEC_EXTPROC = /u01/oracle/vsecdb/10. VSEC_EXTPROC = (ADDRESS_LIST = (ADDRESS= (PROTOCOL= IPC)(KEY= EXTPROCVSEC)) ) SID_LIST_VSEC_EXTPROC = (SID_LIST = (SID_DESC = (SID_NAME = PLSExtProc) (ORACLE_HOME = /u01/oracle/vsecdb/10.0.2.2.5/network/admin TRACE_FILE_VSEC_EXTPROC = VSEC_EXTPROC 40 .2.5) (PROGRAM = extproc) ) ) STARTUP_WAIT_TIME_VSEC_EXTPROC = 0 CONNECT_TIMEOUT_VSEC_EXTPROC = 10 TRACE_LEVEL_VSEC_EXTPROC = OFF LOG_DIRECTORY_VSEC_EXTPROC = /u01/oracle/vsecdb/10.Extras for Experts (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.0. the LISTENER NAME is VSEC_EXTPROC and ORACLE_SID is VSEC.ora. In it. 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. 'dog'. 2. create index quick_text on quick ( text ) indextype is ctxsys. 'The cat sat on the mat' ). resource. 'The quick brown fox jumps over the lazy dog' ). col text format a45 col s format 999 select text. If the above query works without any error. commit. insert into quick ( quick_id. 42 ) >= 0 order by s desc. 3. Create a user to work with InterMedia Text: create user textuser identified by <password> default tablespace users temporary tablespace temp. 41 . the InterMedia option is enabled and the EXTPROC Listener is properly configured. Grant 'ctxapp' role to textuser: grant connect. score(42) s from quick where contains ( text. text ) values ( 1. text ) values ( 3. ctxapp to textuser. text ) values ( 2. Do the following to test whether InterMedia is working: 1. insert into quick ( quick_id. The EXTPROC Listener must be configured and working for InterMedia option to run. 'The dog barked like a dog' ). insert into quick ( quick_id. text varchar2(80) ). Cleanup the test user (textuser) created during this test. Connect as textuser and create required test objects: connect textuser/<password> drop table quick.ora parameter that corresponds to EXTPROC Listener. extproc_connection_data = (DESCRIPTION= (ADDRESS_LIST = (ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROCVSEC)) ) (CONNECT_DATA= (SID=PLSExtProc) (PRESENTATION = RO) ) ) EXTPROC TESTING PROCEDURE This section explains a procedure to test if EXTPROC is enabled.context.Extras for Experts Example: The tnsnames. create table quick ( quick_id number constraint quick_pk primary key. Extras for Experts 42 . %VALIDATION_LEVEL=ERROR Setting these to “Error” increases security by signing and validating many of the parameters that are not supposed to be modified on the client. you should first secure your EBS instance as described in this document. In this section we will share some of the experience we have gained through this process. the input scanner will check the input parameters for common malicious patterns and block the request if any are found. In particular you should ensure that the security settings that directly affect the web interface are set properly.1 “Secure Configuration of E-Business Suite Profiles“ describes the Diagnostics and Validation profiles in more detail. Profile Option Utilities:Diagnostics FND:Diagnostics FND Validation Level FND Function Validation Level Framework Validation Level Restrict Text Input Profile Option Name DIAGNOSTICS FND_DIAGNIOSTICS FND_VALIDATION_LEVEL FND_FUNCTION_VALIDATION_LEVEL FRAMEWORK_VALIDATION_LEVEL FND_RESTRICT_INPUT No No Error Error Error Y Suggested MOS Note 946372. PREPARING YOUR EBS SYSTEM FOR THE WEB SCAN To get the best value of the effort you invest in the pentest.Appendix A: Running Web-Scanning Tools Appendix A: Running Web-Scanning Tools Over the years Oracle has run web scanning tools such as AppScan and WebInspect against EBS and a number of our customers have also submitted reports generated by these tools. 43 . FND_DIAGNOSTICS=N If you set diagnostics to “Yes” you will receive numerous reported issues concerning “Information Leakage” this is because when in diagnostics mode EBS will return stack traces to the client to help in diagnosing problems. Refer to the table below and set the suggested values for the profile options. FND_RESTRICT_INPUT=Y Setting this to Y activates the input scanner. Another source of error is “that string cannot be decoded” seen when messing with submitted cookie values. we have yet to find a single confirmed example. The most common reason for reported 'potential SQL Injections' is that the tool recognizes a database error code in the response and concludes that there might be a 'potential SQL Injection'. Again a potential case of “Information Leakage” but not a SQL injection. 44 . The most common source of these 'database errors' is PL/SQL data type validation errors JDBC connect errors PL/SQL errors typically come from calling java or jsp URLs that call PLSQL APIs. Reflected XSS and Header splitting The tools are generally very good at finding these types of vulnerabilities and most reported issues are actual issues. not necessarily in an 'executable page context' and certainly not stored in the database. In this situation JDBC errors such as “read() returned -1” are thrown indicating that a database connection could not be made. In our experience the webscanning tools excel at finding certain types of vulnerabilities and have less success with other types. In this case the server-side code is executing in the database and any error reported is likely to be “a database error”. These PL/SQL errors may be indicative of “Information Leakage” but they are not SQL Injections. Typical errors are plsql data validation error such as “buffer too small” and “that's not an integer” of the ORA-06502 family. In some cases the connection pool between the application tier and the database gets exhausted and no more database connections can be made. These errors may trigger the tool to report “potential SQL Injection” issues as the error stack includes reference to jdbc. In the few cases we have seen the 'stored' claim was based on tainted input being carried between pages in a page flow.Appendix A: Running Web-Scanning Tools REVIEWING THE RESULTS The web scanning tool attempt to find vulnerabilities of various types. SQL-Injection Of the many 'potential SQL Injections' we have seen reported. ORA-06502: PL/SQL: character string buffer too small ORA-06502: PL/SQL: numeric or value error: number precision too large ORA-06502: PL/SQL: numeric or value error: hex to raw conversion error The JDBC connection errors are seen when the web scanning tool overwhelms the tested instance with a rapid fire of requests. Stored XSS Finding these are much harder and generally the accuracy is lower than for Reflected XSS. Appendix B: Sensitive Administrative Pages Appendix B: Sensitive Administrative Pages In previous revisions of this document Appendix A and Appendix B listed a number Forms that allowed security setup functions and forms that allowed entry of SQL statements or SQL statement fragments.1 “Sensitive Administrative Pages in Oracle E-Business Suite” has the same information including description of how to determine who has access by interactively using UMX User Management or by running SQL scripts. 45 . These tables have been removed from this document and a new MOS Note 1334930. Appendix B: Sensitive Administrative Pages 46 Appendix C: Database Schemas found in Oracle E-Business Suite Appendix C: Database Schemas found in Oracle E-Business Suite Type 1 1 1 2 2 3 3 4 4 SYS SYSTEM DBSNMP SYSMAN MGMT_VIEW 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 Schemas Change Y Y Y Y Y Y Y Y Y Managed N N N N N N N 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 Oracle Portal and Portal Single Sign On 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 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. 4 4 5 EDWREP ODM APPLSYSPUB Y Y N Y Y Y 5 5 APPLSYS APPS Y Y Y Y 5 APPS_mrc 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 DDR DNA DOM DPP EAA EAM EC ECX EDR EGO ENG ENI EVM FA FEM FII FLM FPA FPT FRM FTE FTP FUN FV GCS GL GMA GMD GME GMF GMI GML GMO GMP GMS GR HR HRI HXC HXT IA IBA IBC IBE IBP IBU IBW IBY ICX IEB IEC IEM IEO IES IEU IEX IGC IGF IGI IGS IGW IMC IMT INL INV IPA IPD IPM ISC ITA ITG IZU JA JE JG JL JMF JTF JTM JTS LNS ME MFG MRP MSC MSD MSO MSR MST MTH MWA OE OKB OKC OKE OKI OKL OKO OKR OKS OKX ONT OPI OSM OTA OZF OZP OZS PA PFT PJI PJM PMI PN PO POA POM PON POS PRP PSA PSB PSP PV QA QOT QP QPR QRM RG RHX RLA RLM RRS 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 found in Oracle 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 or AFPASSWD should be used to change the passwords of the listed schemas. Of the 2 commands to change a managed password, AFPASSWD is the newest and more compliant with security best practice, it is available as of 12.1.3, AFPASSWD is documented in the “Oracle E-Business Suite System Administrator’s Guide”. In the examples below we use FNDCPASS syntax as these can be shown on a single line. For trouble shooting issues with running FNDCPASS see MOS Note 1306938.1 “FNDCPASS Troubleshooting Guide For Login and Changing Applications Passwords”. 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, SYSMAN & MGMT_VIEW These schemas are used by Oracle Enterprise Manager (EM). The EM agent connects to DBSNMP for monitoring and management purposes. The EM application connects to SYSMAN. 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 these schemas using sqlplus and (re)configure EM accordingly. Instructions to do this are dependent on the version of Oracle Enterprise Manager in use. 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 49 . you may remove the PORTAL30% schemas by following instructions in MOS Note 312349.0.Appendix C: Database Schemas found in Oracle E-Business Suite CATEGORY 3 PORTAL30_DEMO. you may remove the PORTAL30% schemas by following instructions in MOS Note 312349. Alternatively.0.9 from E-Business Suite 11i”. lock and expire EDWREP schema. CATEGORY 4 CTXSYS E-Business Suite uses the CTXSYS schema. 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.1 “Remove Oracle Portal 3. PORTAL30_SSO_PUBLIC identified by <newpassword>. then log into SQL*Plus with administrative privileges and lock these schema: SQL> alter user PORTAL30 account lock. Alternatively. If you are not using Oracle Login Server and Portal 3. you should change the passwords for PORTAL30_PUBLIC. PORTAL30_PUBLIC identified by <newpassword>.1 “Remove Oracle Portal 3. if you are not using any PORTAL30 integration.1.1.9 with E-Business Suite 11i as documented in MOS Note 146469. 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. which describes the Portal 3.0. refer to ATG MOS Note 146469.9 from E-Business Suite 11i”. 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.1.9 with E-Business Suite 11i as documented in MOS Note 146469.1. PORTAL30_PUBLIC account lock.1. PORTAL30_SSO_PUBLIC account lock. SQL> alter user PORTAL30_SSO account lock. if you are not using any PORTAL30 integration.1 “Using AutoConfig to Manage System Configurations with Oracle Applications 11i”. PORTAL30_SSO_PS account lock.0. 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.9 with E-Business Suite 11i as documented in Oracle MOS Note 146469. PORTAL30_SSO_PS identified by <newpassword>.9 installation. If you are not using Oracle Login Server and Portal 3.0. run AutoConfig as documented in Oracle MOS Note 165195.0. PORTAL30_SSO_PS & PORTAL30_SSO_PUBLIC If you are using Oracle Login Server and Portal 3. PORTAL30_PUBLIC. CATEGORY 4 PORTAL30 & PORTAL30_SSO If you are using Oracle Login Server and Portal 3. For more information.9 with E-Business Suite 11i as documented in Oracle MOS Note 146469.0. All application tier processes (apaches. although it may be used in older versions of E-Business Suite. forms server) must be restarted following the password change and password propagation. APPS is the shared runtime schema for all E-Business Suite products. the schema is created locked and expired.k. secure password for these schemas. ccm. ZX Change all of these product schema passwords. FNDCPASS knows the password must be synchronized across these schemas. FNDCPASS allows a one-step. Although the default password for AD_MONITOR is 'lizard'. APPS & APPS_MRC APPLSYS. CATEGORY 5 AD_MONITOR Oracle Applications Manager uses this schema to monitor running patches. you must use FNDCPASS and run Autoconfig (or a manual procedure) to propagate the change to application tier configuration files. $ 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. FNDCPASS accepts a keyword ALLORACLE forcing a change of all managed schemas to the new password. mass change of all these passwords. CATEGORY 5 APPLSYS. APPS_MRC is an obsolete account. FND user). $ 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.. 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 APPLSYSPUB APPLSYSPUB schema has sufficient privileges to perform the authentication of an Applications User (a. should you choose to change this password.Appendix C: Database Schemas found in Oracle E-Business Suite The CTXSYS password should be changed to a non-default value using FNDCPASS. CATEGORY 6 ABM .sql creates AD_MONITOR.a. APPS and any additional APPS_mrc schemas share the same password. The SQL script $AD_TOP/patch/115/sql/admonusr. $ FNDCPASS APPS/<apps_pwd> 0 Y SYSTEM/<system_pwd> ALLORACLE <NEW_PWD> 50 . Use a long (12 or more characters). There is no need to change the password for APPLSYSPUB. However. sh adcmctl.processor.fm.sh adopmnctl.apps.jar -Doracle.remote.jar -Doracle.instancename=forms java -jar oc4j.oc4j.Appendix D: Processes used by Oracle E-Business Suite Appendix D: Processes used by Oracle E-Business Suite Process Name tnslsnr opmn Description Applications RPC Listener process Process Manager (starts httpd and JVMs used by httpd) Apache Web Server Listener Forms zone JVMs OA Core zone JVMs Web services zone JVMs Concurrent Manager Script adalnctl.engine.engine.jtf. default in Release 12 is servlet mode 51 .sh a.oc4j.jtf.sh httpd java -jar oc4j.oc4j.RemoteCommand adapcctl.sh adformsctl.sh adformsrvctl.sh Fulfillment Server process Forms Servera jtffmctl.Processor java oracle.jar -Doracle.instancename=oacore java -jar oc4j. The forms server (socket mode) is optional.sh adoafmctl.fm.apps.sh adoacorectl.instancename=oafm FNDSM FFTM RCVOLTM POXCON INTCM FNDCRM PALIBR MRCLIB FNDLIBR INVLIBR java oracle. Appendix D: Processes used by Oracle E-Business Suite 52 . e. 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 .Appendix E: Ports used by Oracle E-Business Suite Appendix E: Ports used by Oracle 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. i. no firewall 9000 Port should be open on the first level firewall if forms server is used 10200 10300 8000 Port should be open on the first level firewall 4443 Port should be open on the first level firewall s_formsporta 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 8000/ This is not a separate port 4443 that we are opening. default is servlet mode. 54 . Forms server (socket mode) is optional in Release 12.Appendix E: Ports used by Oracle 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. CONFIGURE THE X SERVER To fulfill the requirement for an available X-server during installation you may use one on the server itself or better yet. perform the installation from an X11-capable admin workstation. When using the ssh trick.0.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/. Sendmail listens only on the localhost interface kept active for outbound mail. Examples of outbound email include workflow generated messages and monitoring alerts.0. After the installation of the Operating System and EBS. We provide this for illustration purposes.0. $ 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. 55 .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. 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. INSTALL THE LINUX OPERATION SYSTEM Use standard install of Operating System including developer tools and ssh. INSTALL E-BUSINESS SUITE Perform the EBS installation as a Rapid Install multinode configuration with the functionality split onto separate hosts for database.0. and use secure shell (ssh) with the X option to log in to each of the servers where you need to install EBS. only. the servers on which EBS is being installed does not have to run a local X-Server and can remain in runlevel 3 for installation and runtime.0:22 tcp 0 0 127. 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. Rapid Install will then use the X-Server on the admin’s workstation during the installation process. $ $ $ $ $ $ chkconfig chkconfig chkconfig chkconfig chkconfig chkconfig --del --del --del --del --del --del sgi_fam xinetd nfslock portmap gpm atd With these changes and a runlevel change to 3.font-unix/fs7100 The only network accessible daemon running is the ssh daemon.1:25 servers) Foreign Address State PID/Program name 0.0.0.0:* LISTEN 846/sshd 0. stop (and disable) unnecessary daemons .0. Web Service and Concurrent Manager service.networked daemons in particular. Customer experience may vary.0. 1:6100 152.0.0.0.0:22 127.0.26:6200 127.0.0.0. Local Address 0.0.0.0..0.26:17060 Foreign Address 0.0:* 0.1 56 .0.198.1:25 0.0.0:* 0..68.0:1626 127.0.68.0:* 0.198.0.0:* 0.0.0.oracle/s#23574.0:* 0.68.0.0.0.26:6500 0.0.0.0.0:* 0.0.font-unix/fs7100 /var/tmp/.0.0:4443 0.198.0:* 0. application specific ports on the various tiers.0.0:* 0.26:16060 152.0:* 0.0.0.0.0.68.0.0.0.0:* 0. starting the EBS processes will open additional.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.0:8000 152.0.0.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/. 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 .1:6500 152.198. 0.0:* 0.oracle/s#1129.0.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.font-unix/fs7100 /var/tmp/.0.0:1632 Foreign Address 0.0:* 0.0.1:25 0.0:22 127.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.0.0.1 57 . Appendix F: Sample Linux Hardening of the Application Tier 58 . Marlene L. ISBN-13: 978-0-07-226276-6 Oracle E-Business Suite Controls: Application Security Best Practices.1 189367. Integrigy Corporation “Oracle Applications 11i Security Quick Reference”. Pete Finnigan Oracle E-Business Suite Security.1 419475. John Abel.1 376811. Jeffrey T. DocID CIS IntA IntB MTAN PF JA JTH Document The Center for Information Security: Oracle Benchmark Tools “Guide to Auditing in Oracle Applications”. ISBN13: 978-0-557-19313-4 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 database accounts) Oracle E-Business Suite R12 Configuration in a DMZ (external deployment) Enabling SSL in Release 12 (also covers encrypting database TNS traffic) Integrating Oracle E-Business Suite Release 12 with Oracle Internet Directory and Oracle Single Sign-On Removing Credentials from a Cloned EBS Production Database FNDCPASS Utility New Feature: Enhance Security With Non-Reversible Hash Password Secure Configuration of E-Business Suite Profiles AppsDataSource.1 59 .1 1306938. Java Authentication and Authorization Service. Hare. Aaron Newman “Oracle Security .1 457166. Integrigy Corporation “Oracle Security Handbook : Implement a Sound Security Plan in Your Oracle Environment”.1 361482.1 1334930.Step by Step”.1 974949. and Utilities for Oracle EBusiness Suite Using TDE Column Encryption with Oracle E-Business Suite Release 12 Using TDE Tablespace Encryption with Oracle E-Business Suite Release 12 How to Implement (Signon Password Custom) Profile Option in Oracle Applications 11i / R12 FNDCPASS Troubleshooting Guide For Login and Changing Applications Passwords Sensitive Administrative Pages in Oracle E-Business Suite MOS ID 403537.1 828229.1 362663.1 946372. Theriault.1 376700.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.1 380490.1 732764. Appendix G: References & More Resources 60 .