EBS_SEC_1_1_1.pdf

May 24, 2018 | Author: dvarta | Category: Transport Layer Security, Oracle Database, Databases, Password, Computer Networking
Share
Report this link


Comments



Description

Secure Configuration Guide forOracle E-Business Suite Release 12 Oracle Corporation Version 1.1.1 Latest version of this document available under MOS Note 403537.1. Revision History Version Release Date 1.0.0 Feb 2007 Initial version for Release 12.0, based on 11i version ML 189367.1 Descriptions 1.1.0 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. 1.1.1 Oct 2012 Added Restriction on uploaded filetypes, Added Antisamy filter, added BEAST note (RC4), added MGDSYS, new appendix (G) “Security Check Scripts”, adressing review comments. Copyright © 2007 - 2012 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 2 3 Oracle TNS Listener Security...............................................................................................................................5 Hardening Network Authentication Authorization Audit 5 5 6 7 8 Oracle Database Security......................................................................................................................................9 Hardening Authentication Authorization Audit 9 9 10 12 Oracle Application Tier Security ........................................................................................................................15 Hardening Authorization Audit 15 16 16 Oracle E-Business Suite Security .......................................................................................................................17 Hardening Network Authentication Authorization Audit Advanced Audit 17 18 19 22 24 26 Desktop Security.................................................................................................................................................31 Hardening 31 Operating Environment Security ........................................................................................................................33 Hardening Network Authentication Authorization Maintenance 33 34 35 36 36 Extras for Experts ...............................................................................................................................................37 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 37 37 38 38 38 38 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: Security Check Scripts..................................................................................................................59 Appendix H: References & More Resources......................................................................................................63 iii Table of Contents iv . we provide configuration guidance (practical advice) for securing Oracle’s E-Business Suite. data files.Overview Overview DESKTOP TIER APPLICATION TIER DATABASE TIER Web Browser Forms applet Sun JRE Listener RDBMS Apache OHS oc4j ORACLE HOME ORACLE HOME AS / JAVA RDBMS Forms Discoverer TNS Listener Concurrent Manager Terminal Server APPL_TOP COMMON_TOP. HTML_TOP. the Application Server. To that end. programs. on-going review and purging. JAVA_TOP. 1 . web pages. We cover security for the Database and Listener. a balance must be struck between risk of exposure. PRODUCT_TOPS ORACLE HOME Tools In today’s environment. Covers configuration. application middle-tier and database) and fall into five categories (hardening. a properly secured computing infrastructure is critical. etc. authentication. JRE_TOP. The last section “Extras for Experts” collects together advice that goes beyond the typical best practice. authorization and auditing). cost of security and value of the information protected. Covers physical topology. products and configuration. PORTAL_TOP. Each organization determines its own correct balance. Covers restrictions to executables. password management and other account related activities. When securing the infrastructure. IP restrictions at web server and database listener. the E-Business Suite and individual desktops. network security. Each section contains advice spanning five categories:      Hardening Network Authentication Authorization Audit Covers hardening the file system. firewalls. The recommendations that follow cross three tiers of machines (browser. Covers account management. We follow this with advice for hardening operating systems including a sample Linux hardening (in the Appendix). administrative tools. often leaves a system wide open for abuse. It also contains a patch set checker to assist with patch application. KEEP UP TO DATE ON LATEST SECURITY INFORMATION Oracle continually improves its software and documentation. 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. move to the latest version of Autoconfig and Patch Tools (AD). grants. especially early on in an organization’s life cycle when people are few and work needs to be done quickly. The firewalls provide assurance that access to these systems is restricted to a known network route. Check this note yearly for revisions. KEEP SOFTWARE UP TO DATE One of the principles of good security practice is to keep all software versions and patches up to date. Throughout this document. if necessary. roles.. independent firewalls. a firewall router substitutes for multiple. proper system configuration and system monitoring. which can be monitored and restricted. In addition. MONITOR SYSTEM ACTIVITY System security stands on three legs: good security protocols. As an alternative. place a firewall between the middle-tier and the database. Follow audit advice in this document and regularly monitor audit records. Auditing and reviewing audit records address this third requirement. This cannot be emphasized enough. Over ambitious granting of responsibilities. for many reasons including good security practice. RESTRICT NETWORK ACCESS TO CRITICAL SERVICES Keep both the E-Business application middle-tier and the database behind a firewall. we assume an E-Business Suite maintenance level of 12. User privileges should be reviewed periodically to determine relevance to current job responsibilities.Overview SYSTEM WIDE ADVICE Some advice applies to the entire E-Business deployment and the infrastructure in which it operates. etc. The latest version of Autoconfig (TXK) configures a system following advice from this document. Each component within a system has some degree of monitoring capability. 2 .0.0 or later. 11i Release 12. This provides a cleaner separation of code directories and directories with instance specific and variable data.7.34 fork) jserv oc4j modplsql -eliminated-a Forms 6i Forms 10.4 Java Oracle_home: 10.1.0 & 12.1.0. modplsql is no longer required in Release 12 and is not configured b.0 Desktop Tier JRE for Forms applet: Oracle Jinitiator JRE for Form applet: Sun JRE 1.2 Reports 6i Reports 10.19 fork) OHS 10.1.2.0.0.1 Database 9iR2 (9.2.0.6x.3.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. See the “Oracle Application Concepts” guide from the installation DVD for more detail 3 .3 (1.6 Tools Oracle_home: 10.1. the table below summarizes the changes in versions and highlights retired technology pieces.0.1.2. Updated Technology Stack Release 12 has updated the entire technology stack.2b Tools Oracle_home: 8.0.0.0) Application Tier IAS 1. From a security perspective the most interesting point is the introduction of the INSTANCE_TOP which is a new directory that contains instance specific configuration files and log files.1.2.2 IAS Oracle_home: 8.2._0x a.2.2.2 + Developer 6i Fusion Middle Ware OHS 1.2 (1. ReportWriter10 is only called from Concurrent Managers in Release 12 (no longer invocable via the web interface) Modified Directory Structure Release 12 has changed the way the file systems are organized.x) 10gR2 (10.2.3.3 JDBC 9 or 10 JDBC 10. Overview 4 . Note. use of SQLNet desktop clients such as sqlplus. This section contains security recommendations for the database TNS Listener. central administrator machines and any remote monitoring tool that uses SQL*Net.X.X with the middle-tiers’ IP addresses. Middle-tier applications include web servers. The next parameter specify the IP addresses or hostnames that are permitted to make network connections to the database.. concurrent managers.ora: tcp.X. We recommend using a whitelist of IP Addresses that are allowed to make a TCP connection to the database listener.invited_nodes = ( X. AutoConfig supports automated configuration of this setting. Replace X. sqldeveloper.X.validnode_checking = YES tcp. NETWORK ADD IP RESTRICTIONS OR ENABLE VALID NODE CHECKING Valid Node Checking allows or denies access from specified IP addresses to Oracle services. . HARDENING HARDEN OPERATING ENVIRONMENT Follow the hardening instructions for “Operating Environment Security” on page 33. If implemented. set the following parameters in $TNS_ADMIN/sqlnet. When the Listener receives a connection request (tcp port 1521. To enable Valid Node Checking. hostname. forms servers.X. the desktop cannot use DHCP (unless the DHCP server is configured with address reservation). terminal servers. We recommend that only trusted servers be allowed to make direct database connections. discoverer.. toad. by default). it starts up a new database process and establishes a connection between the client and the database.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. or ADI from a windows desktop is not recommended on production databases. 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 . ) The first parameter turns on Valid Node Checking. 3DES168) 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. 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. For example adding these 3 lines to $TNS_ADMIN/sqlnet_ifile.ora.1: Using AutoConfig to Manage System Configurations with Oracle Applications Release 12 . set the following parameter: CONNECT_TIMEOUT_$ORACLE_SID = 10 For example. listener specific password. For these database releases you should only set a password if remote admin access to the listener configuration is required. Use the parameter CONNECT_TIMEOUT to specify the amounts of time. For more information. CONNECT_TIMEOUT_PRD12 = 10 Where PRD12 is the value of the ORACLE_SID in this example. Setting a password prevented remove administration (shutdown) of the listener. MOS Note 376700. In Release 12 this is much simpler than in 11i. AutoConfig will add IP restrictions to sqlnet. AES192.ENCRYPTION_TYPES_SERVER= (AES256. SPECIFY CONNECTION TIMEOUT In $TNS_ADMIN/listener.ora will do the trick: 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. in seconds. for the Oracle Listener to wait for the connection from a client to complete.Oracle TNS Listener Security database server. 6 . Note that network encryption is an optional (extra cost) database feature available as part of the Advanced Security Option.or the Oracle Applications Concepts manual. refer to MOS Note 387859. However starting with database release 10g the listener password is no longer required as the listener implements OS-Authentication. The list of host will be all those from the FND_NODES table that are registered as an EBS node.1 “Enabling SSL in Release 12“ contains the instructions on how enable this encryption. this means that the OS user that owns the software installation can start and stop the listener without requiring an additional. All client code already has the encryption code available. so we can simply make the database server require encryption and all the clients will follow.ora.ENCRYPTION_SERVER = REQUIRED SQLNET. AUTHORIZATION ENABLE ADMIN RESTRICTIONS In $TNS_ADMIN/listener.new. This may “break” some monitoring and remote administration tools.ora and remove the PASSWORDS_<listener> line 3. Edit listener.Oracle TNS Listener Security If you decide to set a password for the listener follow the instructions below .ora. The default listener name for oracle databases in general is “LISTENER” while for EBS databases it is set to the SID of the database. then change the password.ora: #----ADDED BY TNSLSNR 13-JAN-2007 11:47:56--PASSWORDS_VIS12 = D911537D50B15546 #-------------------------------------------- To undo these steps: 1. Stop the tnslsnr process (using lsnrctl or use ps to find the pid and kill to kill it) 2.or set the autoconfig variable s_enable_listener_password to ON and run Autoconfig on the database server. if they do not expect to provide a password. These instructions assume that the listener name is VIS12. LSNRCTL> set current_listener VIS12 Current Listener is VIS12 LSNRCTL> change_password Old password: -.0/network/admin/VIS12_dbs01/listener.just hit return New password: -.ora The command completed successfully This added the following lines to listener. 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. 7 . set the following parameter: ADMIN_RESTRICTIONS_<listener>=ON For example. Listener Parameter File /x/db/tech_st/10. Start the Listener control program: $ lsnrctl Set the current listener. secure password Reenter new password: -.2. password protecting the TNS Listener has the following effects:  The Listener process requires a password to list SERVICES or STATUS.new. Restart the listener (using lsnrctl start) Note. This is done by default in Release 12.2. when ADMIN_RESTRICTIONS is ON.Oracle TNS Listener Security ADMIN_RESTRICTIONS_VIS12=ON where VIS12 is the name of the listener (equal to ORACLE_SID in EBS) Note.ora file. 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. in $TNS_ADMIN/listener.0/network/admin/VIS12_dbs01 LOG_FILE_VIS12 = VIS12 Where VIS12 is the LISTENER_NAME. LOG_STATUS = ON LOG_DIRECTORY_VIS12 = /u/db/tech_st/10. all the set commands in lsnrctl are disabled and the only way to change the configuration is to edit the listener. AUDIT ENABLE TNS LISTENER LOGGING To enable logging. 8 . Oracle E-Business Suite does not require these services.ora that reads *. Some individuals (IT Administrators) may require direct access to the application database via their own schema. AUTHENTICATION Middle-tier applications logon to the database through application schemas rather than end-user accounts.ora contains: REMOTE_OS_AUTHENT=FALSE 9 . DISABLE XDB To support XDB. REMOVE OPERATING SYSTEM TRUSTED REMOTE LOGON This setting prevents the database from using an insecure logon protocol. HARDENING HARDEN OPERATING ENVIRONMENT Follow the hardening instructions for “Operating Environment Security” on page 33. and how you arrived at that version. the TNS Listener process listens on two additional TCP ports: 2100 for ftp access and 8080 for http access. they should be disabled. Note that depending on the version you are running. Make sure init. remove or comment out the line in init.Oracle Database Security Oracle Database Security DATABASE TIER Listener RDBMS ORACLE HOME RDBMS This section contains security recommendations for the Database.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. To disable XDB. 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. Oracle Database Security IMPLEMENT TWO PROFILES FOR PASSWORD MANAGEMENT The database provides parameters to enforce password management policies. the application database instance contains default. These accounts and corresponding passwords are well-known. However. 5 and 6). 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. category six (6) schema passwords may be changed en masse using FNDCPASS. 2. see CREATE PROFILE in the Oracle SQL Reference documentation. For the schemas in categories 4. instructions and notes for managing schema passwords. Assign middle-tier application schemas to the first profile and all accounts used by administrators to the second profile. some of the database password policy parameters could lock-out the E-Business Suite. and they should be changed. open schemas with default passwords. 4. Password Parameters Application Profile Administrator Profile FAILED_LOGIN_ATTEMPTS UNLIMITED 5 PASSWORD_LIFE_TIME UNLIMITED 90 PASSWORD_REUSE_TIME 180 180 PASSWORD_REUSE_MAX UNLIMITED UNLIMITED PASSWORD_LOCK_TIME UNLIMITED 7 PASSWORD_GRACE_TIME UNLIMITED 14 PASSWORD_VERIFY_FUNCTION Recommended Recommended Database profiles contain limits on database resources and password policies. “Appendix C: Database Schemas found in Oracle E-Business Suite” on page 47 contains a list of the schemas by category. 5 and 6. 5. Default schemas come from different sources: 1. Because of this. Create two database profiles: one for middle-tier application schemas and one for human beings. This is really handy as there are more than 200 of them. $ 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. For more information on profiles. we make specific recommendations for or against using certain management features depending upon schema type. especially for a database to be used in a production environment. 6. 2 and 3. run the AD adutconf. 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. 3. use standard database commands to change a password: SQL> alter user <SCHEMA> identified by <NEW_PASSWORD>.sql script. Patch 4926128 contains a SQL script that will list all open accounts with default password in your database. CHANGE DEFAULT INSTALLATION PASSWORDS Following an installation. 10 . False is the default for the 10g database. APPLSYSPUB EXECUTE ON FND_DISCONNECTED EXECUTE ON FND_MESSAGE 11 .ora parameter _TRACE_FILES_PUBLIC grants file system read access to anyone who has activated SQL tracing. UTL_FILE_DIR = <dir1>. Just like FNDCPASS. Set this to its default value of False.<dir3>. _TRACE_FILES_PUBLIC=FALSE REMOVE OPERATING SYSTEM TRUSTED REMOTE ROLES Set the init. 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.Oracle Database Security The SQL script was created for database versions 9i. These can be set by <FND_TOP>/admin/sql/afpub. AUTHORIZATION RESTRICT ACCESS TO SQL TRACE FILES The init.. AFPASSWD is documented in the “Oracle E-Business Suite System Administrator’s Guide 12. Oracle E-Business Suite maintains some disk files and needs this parameter set. Note that in release 12.1. AFPASSWD is installed on the application tier and require the libraries from the tools Oracle home.sql.that provides the same information.1”. This also improves interoperability with Oracle Database Vault.. AFPASSWD only prompts for the passwords required for the current operation.2 a new command line utility AFPASSWD is available to replace FNDCPASS.<dir2>. or fixed by <FND_TOP>/admin/sql/afpubfix. O7_DICTIONARY_ACCESSIBILITY = FALSE REVOKE UNNECCESSARY GRANTS GIVEN TO APPLSYSPUB The following table lists the privileges that should be granted to the APPLSYSPUB schema.sql. 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. newer databases (10g & 11g) have a view DBA_USERS_WITH_DEFPWD . the new utility does not require passwords on the command line. allowing separation of duties between application administrators and database administrators.ora parameter REMOTE_OS_ROLES to False to prevent insecure remote roles. Oracle automatically creates an operating system file as an audit record when a user logs in as SYSDBA or as INTERNAL. These recommendations should not have a measurable performance impact. whether or not AUDIT_TRAIL is enabled. For example. OS or TRUE. When set to OS. In addition. Release 12 Rapid Install has a clean APPLSYSPUB by default. set AUDIT_TRAIL to DB.ora. see patch 3763612. AUDIT This section describes the auditing capabilities available in Oracle database for Oracle E-Business Suite. CONFIGURE THE DATABASE FOR AUDITING In init. the database places audit records in directory /u01/logs/db/audit. you should understand the implications of privileges on custom objects granted to PUBLIC or a role. Consult with the Applications Database Administrator before setting this value to TRUE. When not set. login as SYSTEM and issue the following query: SELECT * FROM dba_tab_privs WHERE grantee ='APPLSYSPUB'. AUDIT_FILE_DEST defaults to $ORACLE_HOME/rdbms/audit. AUDIT_FILE_DEST = /u01/logs/db/audit Restart the database for these parameters to take effect. 12 . Note. the database generates some audit records by default.Oracle Database Security APPLSYSPUB EXECUTE ON FND_PUB_MESSAGE EXECUTE ON FND_SECURITY_PKG EXECUTE ON FND_SIGNON EXECUTE ON FND_WEBFILEPUB INSERT ON FND_SESSIONS INSERT ON FND_UNSUCCESSFUL_LOGINS SELECT ON FND_APPLICATION SELECT ON FND_APPLICATION_TL SELECT ON FND_APPLICATION_VL SELECT ON FND_LANGUAGES_TL SELECT ON FND_LANGUAGES_VL SELECT ON FND_LOOKUPS SELECT ON FND_PRODUCT_GROUPS SELECT ON FND_PRODUCT_INSTALLATIONS To check permissions. To revoke unnecessary privileges granted to APPLSYSPUB schema. 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 this example. SYSDBA by ACCESS. ALTER SYSTEM by ACCESS. Auditing these other actions provides little meaningful information. As rare events.AUD$ table. index. By auditing database sessions. suspicious connections to highly privileged schemas may be identified. The contents can be viewed directly or via the following views:   DBA_AUDIT_EXISTS DBA_AUDIT_OBJECT 13 . SYSTEM AUDIT. The remaining audit options generate significant entries of little value. AUDIT OTHER ACTIVITIES To complete the recommended auditing. password guessing attacks on an application schema). AUDIT DATABASE SCHEMA CHANGES Audit any changes to the standard Oracle E-Business Suite database schemas or creation of new schemas. -------------- 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. Oracle E-Business Suite dynamically creates. enable three other audit events: create database link. SYSOPER by ACCESS. To audit schema changes. PUBLIC DATABASE LINK.) on a regular basis. review audit records stored in the file name in AUDIT_FILE_DEST. login through sqlplus as SYSTEM and issue the following command: SQL> audit user. To audit sessions. etc. login through sqlplus as SYSTEM and issue the following command: SQL> audit session. ALTER DATABASE by ACCESS. login through sqlplus as SYSTEM and issue the following commands: SQL> SQL> SQL> SQL> SQL> SQL> SQL> SQL> SQL> SQL> SQL> SQL> SQL> AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT AUDIT DATABASE LINK. ALTER ANY ROLE by ACCESS. REVIEW AUDIT RECORDS If AUDIT_TRAIL is set to OS.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. alters and drops objects (tables. DROP ANY ROLE by ACCESS. If AUDIT_TRAIL is set to DB. This file contains the operating system user and terminal ID. CREATE ROLE by ACCESS. these changes may indicate inappropriate or malicious activity. To audit the last three events. PUBLIC SYNONYM by ACCESS. retrieve audit records from the SYS. SYSTEM GRANT by ACCESS. PROFILE by ACCESS. packages. alter system and system audit. Restrict audit trail access appropriately. at least every 90 days. Oracle’s Audit Vault product can be used for this purpose. SELECT. The database connection entries take up significant space. MAINTAIN AUDIT RECORDS Archive and purge the audit trail on a regular basis. begin by focusing on the following:       Username Terminal Timestamp Object Owner Object Name Action Name Oracle Username. The action that occurred against the object (INSERT. SECURE AUDIT RECORDS Audit data may contain confidential or privacy related data. Consider storing audit records in a separate system for analysis and reporting. The name of the object that the user touched. 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. Time the action occurred. 14 . Backup the audit file before purging. DELETE. UPDATE. EXECUTE). Machine from which the user originated. 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. The trusted. HARDENING HARDEN OPERATING ENVIRONMENT Follow the hardening instructions for “Operating Environment Security” on page 33. the server’s state and its configuration. a number of web pages provide administrative and diagnostics functionality. these pages must be restricted or disabled in a production system. While useful for debugging. 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. 15 .conf to limit web page access to a list of trusted hosts. AUTHORIZATION Within Oracle Application Server. PROTECT ADMINISTRATIVE WEB PAGES Use the apache configuration file trusted.txt) In Release 12 these steps have already been performed in the AutoConfig configuration templates. These pages offer information about various services.conf file contains the following content. For more information. as is done by default. OHS also includes ModSecurity. <Location "uri-to-protect"> Order deny.conf. If you find other pages that you wish to place similar restrictions on.conf is a file for your own additions to the apache configuration. ModSecurity can be configured to log the requests including POST payloads. custom. however in current configuration files these have already been blocked in trusted. you can add them to a customized version of the autoconfig template for trusted. When activated. 16 . the server logs data about all web access to the system.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.conf or to custom.allow Deny from all Allow from localhost <list of TRUSTED IPs> </Location> The section listed a specific set or URLs to be so restricted. 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. refer to MOS Note 387859.conf. AUDIT CONFIGURE LOGGING Oracle Application Server respects Apache’s logging parameters. it will never be overwritten by AutoConfig.1 “Using AutoConfig to Manage System Configurations with Oracle Applications Release 12”. HARDENING HARDEN OPERATING ENVIRONMENT Follow the hardening instructions for “Operating Environment Security” on page 33.Oracle E-Business Suite Security Oracle E-Business Suite Security APPLICATION TIER Apache OC4J ORACLE HOME DATABASE TIER Listener RDBMS ORACLE HOME iAS RDBMS Forms Discoverer TNS Listener Concurrent Manager Terminal Server APPL_TOP COMMON_TOP. PORTAL_TOP. JAVA_TOP. HTML_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. JRE_TOP. STRIKE PASSWORDS FROM ADPATCH LOGS To stop adpatch from logging passwords. see the profile option UPLOAD_FILE_SIZE_LIMIT (kb).. This allow upload of a sanitized version of HTML documents such as resumes for iRecruitment. The key allows the user to access the Notification Details web page directly without authenticating. For more information..COM. SET TOOLS ENVIRONMENT VARIABLES You should prevent forms users from using the enter-query feature on a production system. email notifications contain an access key.. When enabled it will by default restrict using a blacklist of the file extensions that Windows consider "executable" such as . See MOS Note 1357849. you may want to check the setting of the maximum allowed size of an uploaded attachment. the workflow notification email bypasses the E-Business Suite sign-on process.Oracle E-Business Suite Security SET WORKFLOW NOTIFICATION MAILER SEND_ACCESS_KEY TO N When SEND_ACCESS_KEY is set to Y.JS. See MOS Note 1357849. When set to N..WSH..1 "Security Configuration Mechanism in the Attachments Feature in Oracle EBusiness Suite" for details.EXE. refer to Oracle Workflow Administrator's Guide.WSF.2/forms/server/default.env Form Environment Variable FORMS_RESTRICT_ENTER_QUERY Value TRUE RESTRICT FILETYPES THAT MAY BE UPLOADED The Attachements feature may be configured to restrict the filetypes that may be uploaded (actually it restricts by file extension)..JSE. 18 . The Antisamy filter ensures that the HTML document only contains an allowed subset of HTML (no scripting or other “dangerous” tags are allowed).BAT..VBE. Profile Option Profile Option Name Recommended Attachment File Upload Restriction Default FND_SECURITY_FILETYPE_RESTRICT _DFLT N (whitelist) Upload File Size Limit UPLOAD_FILE_SIZE_LIMIT as needed ENABLE ANTISAMY HTML FILTER The Attachmet upload feature now includes the OWASP Antisamy HTML filter feature.VBS. In Release 12 the Forms parameters are set in the configuration file: /x/inst/apps/VIS12_dbs01/ora/10. an unauthenticated user who clicks on the notification link must sign on before accessing the Notification Details web page.MSC.1.. Set SEND_ACCESS_KEY to N to prevent inclusion of the key with the Notification Detail link.. This can be changed into a whitelist of allowed file extensions so you only allow those you actually use..CMD. While you are considering attachments.1 "Security Configuration Mechanism in the Attachments Feature in Oracle EBusiness Suite" for details. Oracle E-Business Suite Security The feature is on by default but can be turned off via a profile option listed below. Profile Option FND: Disable Antisamy Filter Profile Option Name FND_DISABLE_ANTISAMY_FILTER Recommended N NETWORK USE SSL (HTTPS) BETWEEN BROWSER AND WEB SERVER Information sent over the network and across the Internet in clear text may be intercepted. Secure Sockets Layer (SSL) and its sucessor Transport Layer Security (TLS) are features that provide encryption of network traffic between the users browser and the EBS webserver. Configure your EBS environment to use HTTPS (HTTP over SSL/TLS) For information on setting up SSL with the Oracle E-Business Suite, refer to 376700.1 “Enabling SSL for Oracle Applications Release 12”. 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. Basically that means avoid SSLv2 and all ciphers with a key size less than 128 bit. This can be done by enabling these settings in ssl.conf SSLProtocol -all +TLSv1 +SSLv3 SSLCipherSuite HIGH:MEDIUM:!aNULL:+SHA1:+MD5:+HIGH:+MEDIUM If you are concerned about the BEAST attack (CVE-2011-3389), you can change the SSLCipherSuites setting to use the RC4 stream cipher instead of a block cipher. The BEAST attack exposes a client side weakness in SSL v3 and TLS 1.0 when used with Block Ciphers in CBC mode. The following line will make the server prefer RC4 stream cipher SSLCipherSuite RC4-SHA:MEDIUM:!aNULL::!MD5:!ADH You will have to leave SSLv3 enabled as OHS 10.1.3.x uses nzlibs version 10 which do not support TLS. The UTL_HTTP PL/SQL client in the database also does not currently support TLS. USE EXTERNAL WEBTIER IF EXPOSING ANY PART OF EBS TO THE INTERNET If you expose any part of your EBS production system to the internet, you should consult MOS Note 380490.1 for our advice for deploying external EBS products to the internet. This document describes the role of DMZs, external web-tiers, external responsibilities, URL firewall and reverse proxies in a secure external EBS deployment. 19 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, trusted servers rather than on end-user desktop machines. The majority of the E-Business Suite functionality available to end users does not require direct database access but is web based. Web browser sessions connect to application-tier servers running Oracle 10g Application Server. The application-tier servers then make the database connections. If you have a well considered need to connect to the production database directly from a desktop, deploy a remote server environment based on Windows Server Terminal Services, Citrix or Tarantella (now Oracle Secure Global Desktop). 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, or has physical access to the host, it does not qualify as “trusted”. 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. Further details are provided in these sections “Add IP Restrictions or enable Valid Node Checking” on page 5, “Activate Server Security” on page 24 and “Create DBC files securely” on page 24. AUTHENTICATION CHANGE PASSWORDS FOR SEEDED APPLICATION USER ACCOUNTS Oracle ships seeded user accounts with default passwords. Change the default passwords immediately. Depending on product usage, some seeded accounts may or may not be disabled. You disable an application user account by setting the END_DATE for the account.   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.sql, if you run this script as APPS it will list the seeded accounts that still have the default password. In the table an ‘x’ in the EndDT column means the account ship end-dated. In the table an ‘x’ in the NoPwd column indicates that the account ships with an “impossible password”, 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, - unless you change the password! The “impossible” value can be “DUMMY”, “INVALID” or “INTERNAL USER-NOLOGIN“. 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. For example this SQL statement will list users with in impossible password: select USER_NAME,END_DATE,ENCRYPTED_USER_PASSWORD from FND_USER where length(ENCRYPTED_USER_PASSWORD) < 30 order by 1; 20 Oracle E-Business Suite Security Account Product / Purpose Change Disable NoPwd EndDT AME_INVALID_APPROVER AME WF migration 11.5.9 to 11.5.10 Y Y ANONYMOUS FND/AOL – Anonymous for non-logged users Y Y APPSMGR Routine maintenance via concurrent requests N Y x x ASADMIN Application Server Administrator N Y x x ASGADM Mobile gateway related products Y Ya ASGUEST Sales Application guest user Y Yb AUTOINSTALL AD Y Y CONCURRENT MANAGER FND/AOL: Concurrent Manager Y Y x FEEDER SYSTEM AD – Supports data from feeder system Y Y x GUEST Guest application user Y N IBE_ADMIN iStore Admin user Y Yc IBE_GUEST iStore Guest user Y Yc IBEGUEST iStore Guest user Y Yc IEXADMIN Internet Expenses Admin Y Y N Y INDUSTRY DATA INITIAL SETUP AD Y Y IRC_EMP_GUEST iRecruitment Employee Guest Login Y Y IRC_EXT_GUEST iRecruitment External Guest Login Y Y MOBILEADM Mobile Applications Admin Y Y MOBILEDEV Mobile Applications Development Y Y OP_CUST_CARE_ADMIN Customer Care Admin for Oracle Provisioning Y Y OP_SYSADMIN OP (Process Manufacturing) Admin User Y Y ORACLE12.[0-9].0 Owner for release specific seed data N N PORTAL30 Desupported Portal 3.0.x Account Y Y PORTAL30_SSO Desupported Portal 3.0.x Account Y Y STANDALONE BATCH PROCESS FND/AOL Y Y SYSADMIN Application Systems Admin Y N WIZARD AD – Application Implementation Wizard Y Y XML_USER Gateway Y Y x x x x a. Required for Mobile Sales, Service, and Mobile Core Gateway components. b. Required for Sales Application. c. Required for iStore. 21 Users share the same functions or permission sets. Starting with 12. UMX uses workflow to drive the registration process once a request has been submitted. CONSIDER USING SINGLE-SIGN-ON Oracle E-Business Suite Release 12 support integration with a Single Sign-On (SSO). while the system tracks individual user actions. 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. To switch EBS to use hashed passwords you must use the FNDCPASS command line utility in MIGRATE mode. If you set this profile option monitor the FND_FAILED_LOGINS table. account lockout after too many failed logons and session inactivity timeout. CREATE SHARED RESPONSIBILITIES INSTEAD OF SHARED ACCOUNTS When users share one account. b. preventing accountability. Profile Option Name SIGNON_PASSWORD_LENGTH Recommendation 8 SIGNON_PASSWORD_HARD_TO_GUESS YES SIGNON_PASSWORD_NO_REUSE 180 SIGNON_PASSWORD_CASE Sensitive SIGNON_PASSWORD_FAILURE_LIMIT 5a ICX_SESSION_TIMEOUT 30 SIGNON_PASSWORD_CUSTOM implement b a. Setting automatic account locking after N failed attempts make for a simple denial of service attack. 22 . For more information on Single Sign-On deployments. 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.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. see MOS Note 457166. TIGHTEN LOGON AND SESSION PROFILE OPTIONS For local application users. See “Customize Password Validation” in the “Extra for Experts” section. Note: this process is irreversible.0. the profile option settings below support strong passwords.1 “Integrating Oracle E-Business Suite Release 12 with Oracle Internet Directory and Oracle Single Sign-On”. the system cannot identify which user performs a function. refer to MOS Note 376811.4 it is possible to switch the EBS system to store hashed versions of the passwords instead. for the actual command and a list of client/server components that will need an update to work with hashed passwords.1 “FNDCPASS Utility New Feature: Enhance Security With Non-Reversible Hash Password”. See UMX Documentation for more details. To prevent this.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.say CONCOPER . enter SECURE in the Execution Options field. ENCRYPT signals Concurrent Manager to pass the username/password in the environment variable FCP_LOGIN. the password may be intercepted. To prevent username/password from being passed. This is implemented by   Creating a new user . pall.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. With this change. define the concurrent program executable as a HOST program in the Concurrent Program Executable form.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  New Value CONCOPER (or the one you created) s_cp_password_type AppsUser s_cp_resp_shortname FND s_cp_resp_name Concurrent Manager Operator Run auto config on the application tier(s) Following this change the application tier services can be started and stopped by calling adstrtal. Because some Operating Systems allow all machine users to read a program’s command line arguments. 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. Enter ENCRYPT in the Execution Options field of the Concurrent Programs window when defining a concurrent program using this executable. 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.sh with For example [applmgr@app01]$ adstrtal.sh and adstthe -secureapps option and the script will prompt for the Application users username and password rather than the APPS username and password. Starting with Release 12.1. Concurrent Manager does not pass the username/password to the program. Concurrent Manager leaves argument $1 blank.sh -secureapps Enter the Applications username: CONCOPER Enter the Applications password: 23 . Discoverer. Examples of such external hosts are a webservice host or a BPEL service host. Check Server Security Status Check the Server Security status using the STATUS command in the AdminAppServer utility before activating server security to ensure that all desired Application Servers have been registered. The Server Security feature ensures that FNDLogin connections originate from trusted machines. ON Equivalent to OFF from a security perspective. OK for development systems without production data. see System Administrators Guide. Application Server Security has three states: OFF Inactivates Server Security. Appropriate for machines completely under an administrator’s control. Creating DBC files for these external. However when creating DBC files for use by desktop installations or for other. only registered application servers and trusted code modules may connect. This setting is controlled by the autoconfig variable “s_appserverid_authentication”. non-EBS application tiers that must connect to the EBS database. Any program which makes a SQLNet connection to the Oracle Applications database needs to be trusted at some level. you must use the AdminDesktop utility to create the DBC file. Not recommended for production systems. Setup Server Security The application server security feature is activated by default.SERVER_ID.SERVER_ADDRESS from FND_NODES where SERVER_ADDRESS = '*' . all you should do is verify that the setting is set to SECURE.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. NODE_NAME SERVER_ID SERVER_ADDRESS -------------. non-EBS tiers involves    24 running AdminDesktop on the EBS tiers to create the DBC file copying the DBC file to the external tier configuring the external tier to use the DBC file as a data source . 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. Forms. SECURE Recommended.------------. Release 12 already does this automatically via AutoConfig so you should never have to do this manually. For details. The application servers include Apache JSP/Servlet. Administering Server Security. Server and code IDs are not checked. and they are controlled by different mechanisms. There are several types of these sensitive pages in Oracle E-Business Suite. 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. Profile Option Profile Option Name Suggested AuditTrail:Activate AUDITTRAIL:ACTIVATE Yes Concurrent:Report Access Level CONC_REPORT_ACCESS_LEVEL User Sign-On:Notification SIGNONAUDIT:NOTIFY Yes Utilities:Diagnostics DIAGNOSTICS No FND:Diagnostics FND_DIAGNIOSTICS No FND Validation Level FND_VALIDATION_LEVEL Error FND Function Validation Level FND_FUNCTION_VALIDATION_LEVEL Error Framework Validation Level FRAMEWORK_VALIDATION_LEVEL Error Restrict Text Input FND_RESTRICT_INPUT Y IRC: XSS Filter IRC_XSS_FILTER Enable 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. where availability should be limited to a very few trusted users. 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. pages.Oracle E-Business Suite Security Use of AdminDesktop .1 "AppsDataSource. HTML strings. 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.and documentation of any patches needed . When creating DBC files make sure to make them IP address specific and that the filepermissions are set to 600 (-rw-------). These screens may constitute a security risk if used in an unauthorized fashion. profile options and includes a description of how to determine who has access by interactively using UMX User Management or by running SQL scripts. Java Authentication and Authorization Service.1 “Sensitive Administrative Pages in Oracle E-Business Suite” lists these forms. and operating system commands or environment variables. and Utilities for Oracle E-Business Suite".1 “Secure Configuration of E-Business Suite Profiles“ describes the Diagnostics and Validation profiles. Most of these screens are accessible only from system administration menus and responsibilities.can be found in MOS Note 974949. 25 . administrative). are considered secure and have full application access with few limitations. 2 or 3. the system determines which responsibilities are valid for that user. For example. These have access to a small set of responsibilities. The system returns only responsibilities appropriate for the Web server Trust Level.. administrative 2. administrators may wish to set the NODE_TRUST_LEVEL profile to some default level of trust at the site level. external Typically. The system administrator access is described in the following table: Level Visible Allow Update Site Yes Yes Application Yes Yes Responsibility Yes Yes User No No The internal name for this profile option is APPL_SERVER_TRUST_LEVEL. customers or employees outside of a company’s firewall connect to external servers. Lastly. This option. This indicates that only Web servers with the same or greater ordinal trust level may access that responsibility. normal 3. 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). Normal web servers are those used by employees within a company’s intranet and requiring non-administrative responsibilities. To avoid having to set the NODE_TRUST_LEVEL for every single Web server. To restrict access to a responsibility. but they cannot update it. The number 1 means administrative.e. Users can see this profile option.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. 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). If no value is set for NODE_TRUST_LEVEL. set the Application Server Trust Level profile option value for that responsibility to be the number 1. Three trust levels are supported: 1. which can be accessed from that particular Web server. Restricting Access to a Responsibility When a user logs on to Oracle Applications via a Web server. can be set to either 1. the Web server is assumed to have a trust level of 1 (i. 2 or 3. 2 means normal and 3 means external. as well. a server-based profile option. Setting the Server Trust Level for a Server To assign a trust level to a Web server. 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. administrative web servers are used exclusively by system administrators. the administrator sets the NODE_TRUST_LEVEL profile option. 26 . and of those responsibilities. Refer to the Oracle Applications System Administrator's Guide for more information. At this setting. refer to Oracle Applications System Administrator's Guide. configuration steps and best practices for auditing. set this profile option to Form to enable as much auditing as possible. responsibility usage. respectively.Oracle E-Business Suite Security References For more information on how to enable and use the above security features. Access these reports through the system administrator responsibility. It provides an explanation of the features available.1 “Oracle E-Business Suite R12 Configuration in a DMZ (external deployment)”.FND_LOGINS. see MOS Note 380490. unsuccessful signon. SET SIGN-ON AUDIT LEVEL The valid settings for the profile option SIGNONAUDIT:LEVEL are None. the system logs all user sign-ons.FND_LOGIN_RESPONSIBILITIES and APPLSYS. it tracks Oracle Applications usage statistics non-intrusively and with negligible performance impact. APPLSYS. This feature is also used in setting up External Webtiers in a DMZ for intenet exposure. It also suggests which common application objects like foundation objects. Responsibility and Form.FND_LOGIN_RESP_FORMS. In addition. responsibility selections and form accesses to APPLSYS. RETRIEVE AUDIT RECORDS USING REPORTS Oracle E-Business Suite ships standard reports to access signon. See MOS Note 402116. Often.      Signon Audit Concurrent Requests Signon Audit Forms Signon Audit Responsibilities Signon Audit Unsuccessful Logins Signon Audit Users 27 . E-Business Suite deployments do not take advantage of the auditing features due to the perceived complexity and performance issues. Properly configuring auditing and limiting auditing to appropriate tables should not have a measurable performance impact. users and responsibilities to audit. Monitoring features include current and historic user activity down to the page access level and current and historical Concurrent Manager activity.1 for more detailed information about Page Access Tracking. form usage and concurrent request usage. Profile Option Name SIGNONAUDIT:LEVEL Description Set at site-level to track actions starting when the user logs on. Recommend Form MONITOR SYSTEM ACTIVITY WITH OAM Oracle Application Manager (OAM) provides screens for monitoring current and past system activity. OAM provides a framework extensible for running custom OAM reports. User. See OAM documentation for complete product information. Regarding Page Access Tracking. AUDIT This section describes how to configure and use Oracle E-Business Suite audit features. It tracks Web-based and Form-based accesses across technology stacks and correlates them for each user session. At site level.       APPLSYS.FND_LOGINS APPLSYS.FND_LOGIN_RESPONSIBILITIES APPLSYS. enable Oracle E-Business Suite Audit Trail. The current program purges all audit records older than a user supplied date. 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. 28 . Run this concurrent program between once a week and once a month. Who Columns For most E-Business Suite tables. database rows are updated with the creation and last update information. Note.FND_LOGIN_RESP_FORMS APPLSYS.FND_UNSUCCESSFUL_LOGINS FND_CONCURRENT_REQUESTS ICX. Run this concurrent program at least once a week and retain 14 to 90 days of records. To save the entire history of a row. only the last update to record is saved. Nevertheless. The system stores this information in the following columns (known as “Who Columns”): Who Column Name Description CREATION_DATE Date and Time row was created CREATED_BY Oracle Applications user ID from FND_USER LAST_UPDATE_LOGIN Login ID from FND_LOGINS LAST_UPDATE_DATE Date and Time row as last updated LAST_UPDATED_BY Oracle Applications user ID from FND_USERS Join with FND_USERS and FND_LOGINS tables to identify the application user tracked in the audit record.Oracle E-Business Suite Security RETRIEVE AUDIT RECORDS USING SQL The system stores end-user access data in the following tables. REVIEW DATA TRACKED (NO REPORTS AVAILABLE) Some data tracked by the system do not have associated reports. Develop SQL scripts to query these tables to generate reports. Periodically archive and truncate the FND_LOGIN% tables. retaining 30 to 90 days of records.ICX_FAILURES PURGE AUDIT RECORDS Purge end-user access data using the Purge Signon Audit Data concurrent program. these audit records contain valuable information. ICX_FAILURES tables.Oracle E-Business Suite Security Unsuccessful Logins The system automatically stores unsuccessful logon attempts in the APPLSYS. This feature keeps a complete history of changes made at a table and column level. This program creates triggers on each audited column in the original table. Tables with more than a few changes an hour should not be considered for row level auditing. Both the FND_UNSUCCESSFUL_LOGINS and ICX_FAILURES tables contain unsuccessful logins via the Personal Home Page (Self Service/Web Interface). Navigate through Security -> AuditTrail -> Install to set schemas for auditing 3.FND_UNSUCCESSFUL_LOGINS and ICX. Audit Trails. ADVANCED AUDIT Oracle E-Business Suite implements its own auditing mechanisms. Failed Forms logins are logged only to the FND_UNSUCCESSFUL_LOGINS table. Auditing database row changes is performance intensive. a concurrent program creates a shadow table and places triggers on the columns to be audited. Set audit group to Enabled Requested 4. Plan and consult with a DBA before enabling Audit Trails. When initialized. run the AuditTrail Update Tables concurrent program. The ICX_FAILURES table holds more information than the FND_UNSUCCESSFUL_LOGINS.a table whose name is the instance table’s name appended with _A.       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. Limit auditing to non-transactional data. Auditing transactional data may cause significant performance degradation. it creates two views for each column with the names _AC# and _AV# where # is a sequential number. The triggers store column changes in the shadow table -. 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. In addition.     ALR_ALERTS FND_AUDIT_COLUMNS FND_AUDIT_GROUPS FND_AUDIT_SCHEMAS 29 . which activates auditing. follow these steps: 1. This functionality cannot be disabled. Navigate through Security -> AuditTrail -> Groups to create audit groups and set tables to be audited. Navigate through Security -> AuditTrail -> Tables to set columns in tables to be audited 5. Set System profile option AuditTrail: Activate to True 2. Select Security -> Audit Trail -> Groups. Oracle does not ship Audit Trail reports.1 – Understanding Data Auditing in Oracle Application Tables . Run the Audit Trail Update Tables Report.1 – Overview of Oracle Applications AuditTrails MOS Note 69660. 5. disable the Audit Trail. Select the Security Audit group and set the group state to Disable – Purge Table. 6. Select the Security Audit group and set the group state to Enable. 3.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. Use shadow tables and views for accessing the records. Prior to purging. 7. As System Administrator. 4. Purge the data from the shadow table. Use the following procedure to purge audit data: 1. PURGE AUDIT RECORDS Purge the audit trail information on a regular basis.1– Troubleshooting (Audit Trail) MOS Note 60828. Run the Audit Trail Update Tables Report REFERENCES ON ORACLE E-BUSINESS SUITE AUDITING       30 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. select Security -> Audit Trail -> Groups. 2. 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. change the browser’s autocomplete settings. for privacy and security reasons this feature should be disabled. Check browser for built-in safety features. SET POLICY FOR UNATTENDED PC SESSIONS People may attempt to access unattended workstation while the user is still logged into the system. Users are recommended to use the password-locked screen savers feature on all PCs. Update browser plugins .1 “Recommended Browsers for Oracle Applications 12. they often include security bug fixes. Also consider disabling the “remember password” function. 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. UPDATE BROWSER    Update browser when new versions are released. or use a master password for the saved password store. Although convenient for frequently accessed pages. Organizations should set a corporate policy for handling unattended PC sessions.including Java TURN OFF AUTOCOMPLETE For kiosk machines. HARDENING CONFIGURE BROWSER See MOS Note 389422. 31 .0“ for information about securing the desktop. Desktop Security 32 . catproc. use sudo to restrict access to executables.dbf to 0640. the group and owner are for illustration only. 5.Operating Environment Security Operating Environment Security The environment in which Oracle Applications run contributes to or detracts from overall system security. Instead. Better yet. 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. require that legitimate users connect to their own accounts and su to the oracle account. Prevent remote login to the oracle (and root) accounts. This may also apply for any third party products running on the db tier.sql and backup scripts. Oracle recommends that the SUID and SGID bits to be removed from binaries shipped by Oracle. Set all other directories in $ORACLE_HOME to 0750 or less. HARDENING CLEANUP FILE OWNERSHIP AND ACCESS 1. On Unix systems: 1. Set file permissions for the database data files*. 2. Most operating systems now ship with sudo. CLEANUP FILE PERMISSIONS Refer to the product installation documentation for the complete instructions on setting file permissions.ora and sqlnet. Note. 8. $chown -R <oracle> $ORACLE_HOME $chgrp -R <dba> $ORACLE_HOME 6. On the application tier ensure that the DBC files $FND_SECURE/*. Note. the SUID and/or SGID bit must be set on the Oracle database executable in $ORACLE_HOME/bin. The following commands make this change. Another possibility is using Oracle Enterprise Manager with the EBS plugin.dbc have mode 600. Ensure that the owner.ora to 0600. 3. 3. this limits access to the Oracle user and its group (probably DBA). 7. This section contains security recommendations for tightening Oracle file system security along with more general advice for overall system hardening. 33 .courtesan. Verify that set userid (SUID) and set group id (SGID) are not set on binaries. Set file permissions for tnsnames. Find more information about sudo at http://www.ora to 0644. In general. The directory $ORACLE_HOME/bin contains Oracle executables. Set file permissions for listener.com/sudo. group and modes of the Oracle files created upon installation are set to allow minimum privilege. 2.sql. A typical mistake is to install the executables in user oracle’s directory but owned by root. the correct group and owner should be substituted. Set the permissions on $ORACLE_HOME/bin to 0751 or less. 4. Check that the operating system owner of these executables matches the operating system user under which the files have been installed. Protect the $ORACLE_HOME/rdbms/admin directory including catalog. Warning: If Concurrent Manager runs on the Database tier and using the BEQ adapter to avoid TCP cost. A firewall machine sits between the internet and the intranet or the intranet and the internal servers. Remote Access Use secure shell (ssh) to access middle-tier and database hosts. 34 . typically notifications from the workflow system. Typically the administrator’s workstation can run the X Server and grant access to the EBS servers during installation. For software solutions. Firewalls may be software or hardware based. Turn off unused services in /etc/inetd. rlogin. Oracle Installer requires access to the X server which in turn may require access to an X font server. Application middle-tiers and web-tiers do not require an X server. Monitoring agents – for monitoring operating system.0. It provides a point of resistance by protecting inside systems from external users. Printers Applications may require access to printers – normally via the lpd interface on port 515/TCP. limit access to services users need and make those services as secure as possible. A production Database does not require access to an X server.conf.Operating Environment Security LOCKDOWN OPERATING SYSTEM LIBRARIES AND PROGRAMS The database and applications require that the underlying operating system provide certain services. Filtering out unused services at the firewall or router level stops infiltration attempts earlier in the process. 4. If only outbound email is required in your environment make the mail daemon listen on the localhost interface (127. Disabling unused services reduces securing and monitoring work. Do not assume that using Network Address Translation (NAT) substitutes for a firewall. use a firewall machine or router with firewalling capabilities. FILTER IP PACKETS IP filtering helps to prevent unwanted access.0. X Server a. CRON – for operating system cleanup and log file rotation 3. the following services may provide operational convenience: 1. restrict access to the operating system users who absolutely need the printing facility from the shell. implement a default OFF policy. 1. This is required for outbound emails. Better yet. block all RPC ports on the router. 2. A firewall machine can filter packets and/or be a proxy server. database and application components for health and security NETWORK To secure the network.1). Unless running NFS between networks. dedicate a machine to be the firewall. On the host. 2. Although not required by the E-Business Suite. On the internet or large network. rcp and ftp. NTP (Network Time Protocol) – for synchronizing the clock on the UNIX hosts to provide accurate audit records and simplify trouble-shooting. opening only those ports known to be required. create access control lists in /etc/ssh/sshd. E Mail Applications may require access to a SMTP Mail Transfer Agent (SMTP MTA) typically sendmail or qmail on port 25/TCP. 3. 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. rsh. b. If possible. c.conf to limit which users can connect to the local machine. This replaces telnet. Often. telnet. change the root password every three (3) months and whenever an administrator leaves company. but often not practical. If possible. A password tester may check for these. For example. VERIFY NETWORK CONFIGURATION Use scanning tools to find common security violations. always use full pathnames including aliases. Limit root to console login. children's names or a hobby. AUTHENTICATION Good security requires secure accounts. people use passwords associated with them: license plate numbers. use crack or john-the-ripper (password cracking tools) on a regular basis. The root password must be a strong.*’ files for security holes. The minimal umask for root is 022 (rwxr-xr-x). ELIMINATE TELNET. LIMIT ROOT ACCESS        The fewer people with root access. and only root. To ensure that the passwords are not guessable. turn off source routing and filter packets originating outside the network that have source IP address from the inside network. this reduces the dependency on DNS for the core system. SSH provides encrypted traffic to prevent snooping. 35 . only use fully qualified hostnames or IP addresses in system files. Always logout of root shells. should not be used.Operating Environment Security PREVENT SPOOFING To prevent hostname spoofing. In addition. RSH AND FTP DAEMONS Enforce the use of SSH (secure shell). never leave root shells unattended. MONITOR FOR ATTACKS Consider installing an Intrusion Detection System (IDS). Root should NEVER have “. non-guessable password. Automatically disable accounts after several failed login attempts.*’ files SHOULD have 700 or 600 permissions. Check root ‘. change passwords from time to time. rsh and ftp send the passwords in clear text and. On the system side. For the production system consider enumerating all hosts that are part of the EBS instance in the hosts file on each system. The root ‘. the easier it is to track changes. NEVER allow non-root write access to any directories in root's path. do not create root's temporary files in publicly writable directories. Snort is a capable and free IDS system. should have UID 0. CONFIGURE ACCOUNTS SECURELY   Make sure that all OS accounts have a non-guessable password. To avoid trojan horse programs.” in path. In addition. Root. A umask of 077 (rwx------) is best. for this reason. only (specified in /etc/security). delete or lock accounts no longer required. Use setuid/setgid only where absolutely necessary. Consider setting up automatic email or paging to warn system administrators of any suspicious behavior. SECURE EXECUTABLES Always get programs from a known source. Most other device files should be unreadable and unwritable by regular users. Run security software and review output. Verify user accounts . uucp. wtmp. in some cases. Require strong passwords and. a restricted shell. sulog. /dev/tty and /dev/console should be world writable but NEVER executable. etc. Add directories for specific groups. Limit user file writes to their own directories and /tmp. . Keep up to date on security issues by subscribing to security mailing lists. Disable login for well known accounts that do not need direct login access (bin. Install Tripwire to detect changes to files. When creating the /etc/exports file. lp. AUTHORIZATION SECURE NFS Only run NFS as needed. syslog. Install latest operating system patches. use limited access flags when possible (such as readonly or nosuid). SECURE OPERATING SYSTEM DEVICES Device files /dev/null. MAINTENANCE Good security practice does not end after installation. Test the system with tools like NESSUS (network security) and CRACK (password checker). Also check the snort logs. Continuous maintenance tasks include:         36 Install the latest software patches. Monitor log files including btmp. Use a checksum to verify they have not been altered. Limit important file access to authorized personnel. SECURE FILE ACCESS Create minimal writable file systems (esp. reading security news groups and following the latest security procedures. daemon. system files/directories). Remove or disable user accounts upon termination. adm).Operating Environment Security MANAGE USER ACCOUNTS Do not share user accounts. sys. To customize password validation create a Java class that implements the oracle.1 “How to Implement (Signon Password Custom) Profile Option in Oracle Applications 11i / R12”.1 “Oracle Applications Credit Card Encryption“ describes the credit card encryption features available in Oracle E-Business Suite. This renders the other sessions invalid. respectively. ENCRYPT CREDIT CARDS The Withe Paper in MOS Note 338756. this class must be loaded into the Application database using the loadjava command. public String getErrorStackMessageName() This method returns the name of the message to display when the user's password is deemed invalid (i. set profile option SIGNON_PASSWORD_CUSTOM to the full name of the class. This section contains recommendations that improve security. String password This method takes a username and password..apps. 2.security. After writing the customized password validator.Extras for Experts Extras for Experts Security policy must balance risk of attack. The subscription calls a rule function that updates the ICX_SESSIONS table setting the DISABLED_FLAG='Y' for all other sessions for the user. 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.fnd.AppsPasswordValidation".security. indicating whether the user's password is valid or invalid. DETECT AND PREVENT DUPLICATE USER SESSIONS When properly patched and configured. open sessions. then the value of SIGNON_PASSWORD_CUSTOM must be "yourco. This functionality is disabled by default. Patch 2128669 contains an example demonstrating how to write a custom event and/or additional subscriptions. User names appearing in the subscription's parameter list are excluded from this functionality.e. public boolean validate(String user. The feature is part of Release 12 but needs to be explicitly turned on. Encryption of credit card numbers is one of many requirements for PCI PA-DSS compliance.security. More details available in MOS Note 362663. Note. The next user action returns the browser to a login screen indicating the session is invalid. and returns True or False. but may not be appropriate for every deployment. 3. CUSTOMIZE PASSWORD VALIDATION If your corporate password policy cannot be expressed using the “Sign-On” parameters on page 22 you can implement a custom function for validating new passwords. cost of defense and value of data protected. public String getErrorStackApplicationName() This method returns the application short name for the aforementioned error message. If the name of the Java class is yourco. 37 .PasswordValidation Java interface.AppsPasswordValidation. The interface requires three methods: 1. the validate() method returns False). the E-Business Suite raises a Workflow event when the same user has multiple. The external procedures are supposed to issue the commands to the Listener on a special IPC pipe named EXTPROC. The option protects the data a rest by encrypting the data stored in the database datafiles.1 Using TDE Column Encryption with Oracle E-Business Suite Release 12 828229. ADVANCED SECURITY/TRANSPARENT DATA ENCRYPTION (ASO/TDE) Oracle Advanced Security Option provides transparent data encryption (TDE). Address. HARDENING EXTERNAL PROCEDURE (EXTPROC) SERVICES The Oracle database uses the external procedure service to call external C programs. Specifically.Extras for Experts ADVANCED SECURITY/NETWORKING OPTION (ASO/ANO) Oracle Advanced Security Option provides a single source of integration with network encryption. Compensation details) customer data (Name. These copies are typically used for performance test by dbas or developers or to test upgrade/patching of the production database. The steps in MOS 419475. Social Security Number. such as mathematical modeling or files system interactions.1“Enabling SSL in Release 12” provides more information on using ASO/ANO to encrypt your Oracle E-Business Suite 12 network traffic. Credit Card info) and other data considered confidential.1 should be incorporated in your local cloning procedures.ora parameter file as (ADDRESS_LIST = (ADDRESS = (PRTOCOL = IPC) (KEY = EXTPROC)) 38 . Oracle Advanced Security provides the following features:   Data Integrity: Prevents data modification during transmission. See MOS Notes for details   732764. The option protects against threats to the security of distributed environments. 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.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. EBS Release 12 is certified with Column Encryption and Tablespace Encryption. See MOS 419475. The specification exists in the listener. This functionality exploits the ability of the Listener to issue operating system commands. This extends the functionality of PL/SQL to routines that can be written in C to perform complex calculations. MOS Note 376700. Tablespace TDE does not have these restrictions and does not increase the storage requirement. Data Privacy: Prevents data disclosure during transmission. 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. Address. 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.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. . Replace the $ORACLE_SID with name of the Oracle database instance (SID). configure a TCP protocol address. 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. If the Oracle Listener for PL/SQL EXTPROC has been configured with a TCP address.Extras for Experts These external procedures operate by instructing the Listener to issue these operating system commands on their behalf. Copy the listener. $ORACLE_HOME with the value of ORACLE HOME directory for this Listener and $TNS_ADMIN with the directory location of the Listener parameter files. The following Oracle E-Business suite components use EXTPROC services: 1. Modify the EXTPROC specific entry in $ORACLE_HOME/network/admin/tnsnames.ora files are located. If TCP connectivity is required. Restrict access to the Oracle Listener for PL/SQL EXTPROC only. Remove EXTPROC specific entries from the Oracle Database Listener configuration files. On Windows platforms. Oracle Email Center.” 4. Configure the Oracle EXTPROC Listener with an IPC protocol address only. one for the Oracle database and one for PL/SQL EXTPROC. 2.ora are set to 600. $ORACLE_SID_EXTPROC = (ADDRESS_LIST = (ADDRESS= (PROTOCOL= IPC)(KEY= EXTPROC$ORACLE_SID)) ) SID_LIST_$ORACLE_SID_EXTPROC = (SID_LIST = (SID_DESC = 39 . Store this file in any directory other than the one in which the database listener. do the following: a. EXTPROC LISTENER CONFIGURATION See below for the format of the dedicated EXTPROC Listener. Use a separate $TNS_ADMIN/sqlnet.ora and sqlnet.ora. 6.ora file for this Oracle Listener. b.ora to reflect the correct port for the new Oracle Listener. The parameters appear in $TNS_ADMIN/listener. Ensure that the file permissions on separate $TNS_ADMIN/listener. This step may not be applicable for default E-Business Suite implementations. Oracle Demand Planning Express implementation. but use a port other than the one the Oracle Listener for the database is using. To protect against some EXTPROC attack vectors: 1. Create two Oracle TNS Listeners. 3. Enable Valid Node Checking and restrict access to those network clients requiring EXTPROC. only the owner should read the file. Because it contains the password. run the Oracle TNS Listener process as an unprivileged user and not as the Windows LOCAL SYSTEM user. 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.g.ora with the configuration of the Oracle Listener for PL/SQL EXTPROC into this other directory as well. c. 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). “nobody” on Unix). Because the Listener runs with the privilege of the operating system user. Oracle InterMedia cartridges 2. the only limits on external procedures are the limits on what that account can do. Give this user the operating system privilege to “Logon as a service. 5. Ensure that the Oracle Listener created for PL/SQL EXTPROC runs as an unprivileged operating system user (e. Before starting the Oracle Listener for PL/SQL EXTPROC. 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.5/network/admin LOG_FILE_VSEC_EXTPROC = VSEC_EXTPROC TRACE_DIRECTORY_VSEC_EXTPROC = /u01/oracle/vsecdb/10. In it. Replace $ORACLE_SID with the name of the Oracle database instance (SID).ora.2.0.0.5/network/admin TRACE_FILE_VSEC_EXTPROC = VSEC_EXTPROC 40 .2. 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. the LISTENER NAME is VSEC_EXTPROC and ORACLE_SID is VSEC.2. 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.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. 'The dog barked like a dog' ).Extras for Experts Example: The tnsnames. Create a user to work with InterMedia Text: create user textuser identified by <password> default tablespace users temporary tablespace temp. 'dog'. the InterMedia option is enabled and the EXTPROC Listener is properly configured. The EXTPROC Listener must be configured and working for InterMedia option to run.ora parameter that corresponds to EXTPROC Listener. ctxapp to textuser.context. If the above query works without any error. col text format a45 col s format 999 select text. Grant 'ctxapp' role to textuser: grant connect. resource. create table quick ( quick_id number constraint quick_pk primary key. score(42) s from quick where contains ( text. insert into quick ( quick_id. insert into quick ( quick_id. 41 . text ) values ( 1. Cleanup the test user (textuser) created during this test. 'The cat sat on the mat' ). 42 ) >= 0 order by s desc. 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. 'The quick brown fox jumps over the lazy dog' ). text varchar2(80) ). commit. Connect as textuser and create required test objects: connect textuser/<password> drop table quick. text ) values ( 3. Do the following to test whether InterMedia is working: 1. text ) values ( 2. insert into quick ( quick_id. 3. 2. create index quick_text on quick ( text ) indextype is ctxsys. Extras for Experts 42 . 43 . you should first secure your EBS instance as described in this document. %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. In particular you should ensure that the security settings that directly affect the web interface are set properly.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. 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. PREPARING YOUR EBS SYSTEM FOR THE WEB SCAN To get the best value of the effort you invest in the pentest. FND_SECURITY_FILETYPE_RESTRICT_DFLT=N Setting this to “N” enables a whitelist of allowed file extensions rather than the default blacklist specified by “Y”. the input scanner will check the input parameters for common malicious patterns and block the request if any are found.1 “Secure Configuration of E-Business Suite Profiles“ describes the Diagnostics and Validation profiles in more detail. FND_RESTRICT_INPUT=Y Setting this to “Y” activates the input scanner. Profile Option Profile Option Name Suggested Utilities:Diagnostics DIAGNOSTICS No FND:Diagnostics FND_DIAGNIOSTICS No FND Validation Level FND_VALIDATION_LEVEL Error FND Function Validation Level FND_FUNCTION_VALIDATION_LEVEL Error Framework Validation Level FRAMEWORK_VALIDATION_LEVEL Error Restrict Text Input FND_RESTRICT_INPUT Y Attachment File Upload Restriction Default FND_SECURITY_FILETYPE_RESTRICT _DFLT N (whitelist) FND: Disable Antisamy Filter FND_DISABLE_ANTISAMY_FILTER N MOS Note 946372. In this section we will share some of the experience we have gained through this process. 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'. SQL-Injection Of the many 'potential SQL Injections' we have seen reported. 44 . In the few cases we have seen the 'stored' claim was based on tainted input being carried between pages in a page flow. Again a potential case of “Information Leakage” but not a SQL injection. Another source of error is “that string cannot be decoded” seen when messing with submitted cookie values.    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. Reflected XSS and Header splitting The tools are generally very good at finding these types of vulnerabilities and most reported issues are actual issues. Stored XSS Finding these are much harder and generally the accuracy is lower than for Reflected XSS. In this situation JDBC errors such as “read() returned -1” are thrown indicating that a database connection could not be made. These PL/SQL errors may be indicative of “Information Leakage” but they are not SQL Injections. 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.Appendix A: Running Web-Scanning Tools REVIEWING THE RESULTS The web scanning tool attempt to find vulnerabilities of various types. In this case the server-side code is executing in the database and any error reported is likely to be “a database error”. 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. not necessarily in an 'executable page context' and certainly not stored in the database. we have yet to find a single confirmed example. These errors may trigger the tool to report “potential SQL Injection” issues as the error stack includes reference to jdbc. In our experience the webscanning tools excel at finding certain types of vulnerabilities and have less success with other types. 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 . 47 . Owns the sql data dictionary.g. APPS_JP. Defaults to APPS_MRC. 1 DBSNMP SYSMAN MGMT_VIEW Y N Used for database status monitoring. additional APPS schemas for the (now obsolete) Multiple Reporting Currencies feature. 4 EDWREP Y Y Embedded Data Warehouse Metadata Repository 4 ODM Y Y Oracle Data Manager 5 APPLSYSPUB Y Y Initial. 5 APPS Y Y Runtime user for E-Business Suite. 5 APPS_mrc Y Y Optional. 2 SSOSDK Y N Single Sign On SDK. 2 SCOTT Y N Demo account delivered with RDBMS.Appendix C: Database Schemas found in Oracle E-Business Suite Appendix C: Database Schemas found in Oracle E-Business Suite Type Change Managed 1 SYS Schemas Y N Initial schema in any Oracle database. Owns all of the applications code in the database. 5 AD_MONITOR EM_MONITOR Y N Used by Oracle Applications Manager (OAM) or EM to monitor patching. pre-authentication user with minimal privileges to assist with APPS (FND) user authentication. 5 APPLSYS Y Y Contains shared APPS objects. e. Description 1 SYSTEM Y N Initial DBA User. Changing the password for these schemas does not affect any configuration files. 6 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 These schemas belong to individual APPS base products. 3 JUNK_PS MDSYS ODM_MTR OLAPSYS ORDPLUGINS ORDSYS OUTLN OWAPUB MGDSYS Y N 3 PORTAL30_DEMO PORTAL30_PUBLIC PORTAL30_PS PORTAL30_SSO_PUBLIC Y N Oracle Portal and Portal Single Sign On 4 PORTAL30 PORTAL30_SSO Y Y Oracle Portal and Portal Single Sign On 4 CTXSYS Y Y InterMedia schema used by Online Help and CRM service products for indexing knowledge base data. APPS_UK. but country code suffixes may be used. By default the password is the same as the SCHEMA name. OUTLN. SQL*Plus provides two methods to change a schema’s password: ALTER USER and PASSWORD syntax. Change means we recommend changing the default password for the listed schemas. The EM agent connects to DBSNMP for monitoring and management purposes. In the examples below we use FNDCPASS syntax as these can be shown on a single line. OLAPSYS.Appendix C: Database Schemas found in Oracle E-Business Suite In the table on the previous page. follow database instructions for managing this account. SQL> alter user SYS identified by <NEW_SYS_PASSWORD>. Note. 48 . 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>. ORDPLUGINS. MGDSYS Change the passwords for these schemas: SQL> alter user <SCHEMA> identified by <NEW_PASSWORD_PER_SCHEMA>. Lock the SCOTT schema: SQL> alter user SCOTT account LOCK. ODM_MTR.1 “FNDCPASS Troubleshooting Guide For Login and Changing Applications Passwords”. MDSYS. ORDSYS. If you are using Enterprise Manager with your Applications database. For trouble shooting issues with running FNDCPASS see MOS Note 1306938. OWAPUB. we have used the ALTER USER syntax. 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. Of the 2 commands to change a managed password. Managed means that FNDCPASS or AFPASSWD should be used to change the passwords of the listed schemas. AFPASSWD is the newest and more compliant with security best practice. you should change the password for these schemas using sqlplus and (re)configure EM accordingly. AFPASSWD is documented in the “Oracle E-Business Suite System Administrator’s Guide”.1. 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>. However. To simplify these instructions. it is available as of 12. If you are not using EM with your Applications database. SYSMAN & MGMT_VIEW These schemas are used by Oracle Enterprise Manager (EM). Type refers to the categories listed in “Change default installation passwords” on page 10. CATEGORY 3 JUNK_PS. The EM application connects to SYSMAN. CATEGORY 1 DBSNMP.3. 0.1.1. then log into SQL*Plus with administrative privileges and lock these schema: SQL> alter user PORTAL30 account lock. PORTAL30_PUBLIC identified by <newpassword>. If you are not using Oracle Login Server and Portal 3. you should change the passwords for PORTAL30_PUBLIC.9 with E-Business Suite 11i as documented in MOS Note 146469.1 “Using AutoConfig to Manage System Configurations with Oracle Applications 11i”. SQL> alter user PORTAL30_SSO account lock. 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. refer to ATG MOS Note 146469.9 with E-Business Suite 11i as documented in Oracle MOS Note 146469. PORTAL30_PUBLIC account lock. If you are not using Oracle Login Server and Portal 3.9 from E-Business Suite 11i”.0.0. 49 . 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. PORTAL30_SSO_PS & PORTAL30_SSO_PUBLIC If you are using Oracle Login Server and Portal 3. Alternatively. CATEGORY 4 CTXSYS E-Business Suite uses the CTXSYS schema.1 “Remove Oracle Portal 3.0.1 “Remove Oracle Portal 3. if you are not using any PORTAL30 integration.0. PORTAL30_PUBLIC. you may remove the PORTAL30% schemas by following instructions in MOS Note 312349. Alternatively. run AutoConfig as documented in Oracle MOS Note 165195.0. PORTAL30_SSO_PUBLIC identified by <newpassword>. 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. if you are not using any PORTAL30 integration.9 from E-Business Suite 11i”. CATEGORY 4 PORTAL30 & PORTAL30_SSO If you are using Oracle Login Server and Portal 3.1. 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.1.1.9 with E-Business Suite 11i as documented in Oracle MOS Note 146469. you may remove the PORTAL30% schemas by following instructions in MOS Note 312349. PORTAL30_SSO_PUBLIC account lock. PORTAL30_SSO_PS identified by <newpassword>. For more information.9 with E-Business Suite 11i as documented in MOS Note 146469.Appendix C: Database Schemas found in Oracle E-Business Suite CATEGORY 3 PORTAL30_DEMO. which describes the Portal 3. lock and expire EDWREP schema.0. PORTAL30_SSO_PS account lock.9 installation. secure password for these schemas. FNDCPASS allows a one-step. the schema is created locked and expired. APPS is the shared runtime schema for all E-Business Suite products. $ 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. CATEGORY 5 APPLSYSPUB APPLSYSPUB schema has sufficient privileges to perform the authentication of an Applications User (a. $ FNDCPASS APPS/<apps_pwd> 0 Y SYSTEM/<system_pwd> SYSTEM APPLSYS <new_pwd> After changing the shared password for these schemas you must run Autoconfig to propagate the changed passwords into the application server configuration files. CATEGORY 6 ABM . If you choose to change this password. FNDCPASS knows the password must be synchronized across these schemas.sql creates AD_MONITOR. APPS & APPS_MRC APPLSYS.a. CATEGORY 5 APPLSYS.. even if case sensitive passwords have been turned on (SIGNON_PASSWORD_CASE=Sensitive) . $ FNDCPASS APPS/<apps_pwd> 0 Y SYSTEM/<system_pwd> ALLORACLE <NEW_PWD> 50 . ccm. APPS_MRC is an obsolete account. All application tier processes (apaches. Although the default password for AD_MONITOR is 'lizard'. Note that the APPLSYSPUB password must be uppercase.k. APPS and any additional APPS_mrc schemas share the same password. mass change of all these passwords. ZX Change all of these product schema passwords. 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. although it may be used in older versions of E-Business Suite. FND user). CATEGORY 5 AD_MONITOR Oracle Applications Manager uses this schema to monitor running patches. Use a long (12 or more characters). forms server) must be restarted following the password change and password propagation. you must use FNDCPASS and run Autoconfig (or a manual procedure) to propagate the change to application tier configuration files. FNDCPASS accepts a keyword ALLORACLE forcing a change of all managed schemas to the new password.Appendix C: Database Schemas found in Oracle E-Business Suite The CTXSYS password should be changed to a non-default value using FNDCPASS. The SQL script $AD_TOP/patch/115/sql/admonusr. instancename=oacore OA Core zone JVMs adoacorectl.sh java -jar oc4j.jtf.Processor java oracle.engine.apps.engine. default in Release 12 is servlet mode 51 .oc4j.jar -Doracle.fm.remote.RemoteCommand Fulfillment Server process jtffmctl. The forms server (socket mode) is optional.processor.sh opmn Process Manager (starts httpd and JVMs used by httpd) adopmnctl.sh java oracle.sh httpd Apache Web Server Listener adapcctl.sh FNDSM FFTM RCVOLTM POXCON INTCM FNDCRM PALIBR MRCLIB FNDLIBR INVLIBR Concurrent Manager adcmctl.jtf.apps.jar -Doracle.jar -Doracle.fm.oc4j.instancename=oafm Web services zone JVMs adoafmctl.oc4j.sh Forms Servera adformsrvctl.sh java -jar oc4j.Appendix D: Processes used by Oracle E-Business Suite Appendix D: Processes used by Oracle E-Business Suite Process Name Description Script tnslsnr Applications RPC Listener process adalnctl.sh a.instancename=forms Forms zone JVMs adformsctl.sh java -jar oc4j. Appendix D: Processes used by Oracle E-Business Suite 52 . i. It is either s_webport or s_websslport Fusion Middleware Oracle HTTP Server s_jtfuf_port JTF fulfilment server port 11000 Applications JTF s_ons_localport Oracle Notification Service 6100 Fusion Middleware Oracle HTTP Server s_ons_remoteport Oracle Notification Service 6200 Fusion Middleware Oracle HTTP Server s_ons_requestport Oracle Notification Service 6500 Fusion Middleware Oracle HTTP Server s_oacore_jms_portrange JMS for OACore zone 2300023004 Fusion Middleware oc4j s_forms_jms_portrange JMS for Forms zone 2350023504 Fusion Middleware oc4j s_home_jms_portrange JMS for Home zone 2400024004 Fusion Middleware oc4j s_oafm_jms_portrange JMS for OAFM zone 2450024504 Fusion Middleware oc4j s_oacore_ajp_portrange AJP for OACore zone 2150021504 Fusion Middleware oc4j s_forms_ajp_portrange AJP for OACore zone 2200022004 Fusion Middleware oc4j s_home_ajp_portrange AJP for OACore zone 2250022504 Fusion Middleware oc4j s_oafm_ajp_portrange AJP for OADFM zone 2500025004 Fusion Middleware oc4j s_oacore_rmi_portrange RMI for OACore zone 2000020004 Fusion Middleware oc4j 53 .Appendix E: Ports used by Oracle E-Business Suite Appendix E: Ports used by Oracle E-Business Suite Variable Name Description Default Value Firewall Configuration Technology Component s_dbport Port on the database server used by the Net8 Listener 1521 Port should be open on the second level firewall RDBMS TNS Listener s_rpcport RPC port on the concurrent processing server that receives incoming Report Review Agent requests 1626 Internal application tiers assumed to be of same subnet.e. no firewall Applications Concurrent processing s_formsporta Port on the Forms server used by the Forms Listener 9000 Port should be open on the first level firewall if forms server is used Forms 10 Forms s_mwaPortNo MSCA Server Port Number 10200 Applications Mobile s_mwaDispatcherPort MSCA Dispatcher Port Number 10300 Applications Mobile s_webport Port on the webserver where http server listens for non-ssl requests 8000 Port should be open on the first level firewall Fusion Middleware Oracle HTTP Server s_webssl_port Port on the webserver where http server listens for ssl requests 4443 Port should be open on the first level firewall Fusion Middleware 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 8000/ This is not a separate port 4443 that we are opening. default is servlet mode.Appendix E: Ports used by Oracle E-Business Suite s_forms_rmi_portrange RMI for Forms zone 2050020504 Fusion Middleware oc4j s_home_rmi_portrange RMI for Home zone 2100021004 Fusion Middleware oc4j s_oafm_rmi_portrange RMI for OAFM zone 2550025504 Fusion Middleware oc4j a. 54 . Forms server (socket mode) is optional in Release 12. 0.0:22 tcp 0 0 127.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/. 55 .font-unix/fs7100 The only network accessible daemon running is the ssh daemon. INSTALL THE LINUX OPERATION SYSTEM Use standard install of Operating System including developer tools and ssh. We provide this for illustration purposes.0:* LISTEN 846/sshd 0. perform the installation from an X11-capable admin workstation. When using the ssh trick.0. netstat on the Linux box is very short: $ netstat –lptuxn Active Internet connections (only Proto Recv-Q Send-Q Local Address tcp 0 0 0.0. Rapid Install will then use the X-Server on the admin’s workstation during the installation process.1:25 servers) Foreign Address State PID/Program name 0. Sendmail listens only on the localhost interface kept active for outbound mail. stop (and disable) unnecessary daemons . 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. only. Customer experience may vary.networked daemons in particular. INSTALL E-BUSINESS SUITE Perform the EBS installation as a Rapid Install multinode configuration with the functionality split onto separate hosts for database.0. Web Service and Concurrent Manager service. Examples of outbound email include workflow generated messages and monitoring alerts. 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.0. $ $ $ $ $ $ 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.0. and use secure shell (ssh) with the X option to log in to each of the servers where you need to install EBS.0. Copy the context file generated during the installation of the database onto each middle-tier and run the rapid installation via NFS from a shared staging area.Appendix F: Sample Linux Hardening of the Application Tier Appendix F: Sample Linux Hardening of the Application Tier This section contains an example of how we hardened an Application Tier running the Linux Operating System. $ ssh -X oracle@dbs01 This will set the DISPLAY environment variable on the remote host (in this example the database host dbs01) to point back to the X-Server on the admin workstation. After the installation of the Operating System and EBS. 198.0.26:16060 152.0:* 0.0.0.0.0:* 0.1:25 0.0.26:6200 127.1:6100 152..0.26:6500 0.0:8000 152.0.0:* State LISTEN LISTEN LISTEN LISTEN LISTEN LISTEN LISTEN LISTEN LISTEN LISTEN LISTEN 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 56 PID/Program name 23574/tnslsnr 27358/opmn 27358/opmn 27358/opmn 27358/opmn 23391/httpd 23391/httpd 23408/java 23409/java Path /tmp/.0.0.0.0. starting the EBS processes will open additional.0:1626 127.0:22 127.68.0.0.font-unix/fs7100 /var/tmp/.0.0.0:* 0.0:* 0.0.0.0.68.0.0.0:* 0.Appendix F: Sample Linux Hardening of the Application Tier Running processes include: UID root root root root root root root root root root root root root root root root root root root root root root root root root root root root root xfs root root root root root root PID 14 13 12 11 10 9 8 7 6 1 2 3 4 5 15 23 150 151 152 153 154 659 664 846 1034 1035 1090 902 921 969 1026 1027 1028 1029 1030 1031 PPID 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 846 1034 1035 1 1 1 1 1 1 1 1 1 C 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 STIME 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:02 18:03 18:03 18:03 18:04 18:04 18:05 18:03 18:03 18:03 18:03 18:03 18:03 18:03 18:03 18:03 TTY ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? pts/0 pts/0 ? ? ? tty1 tty2 tty3 tty4 tty5 tty6 TIME 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:04 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 CMD [kupdated] [bdflush] [krefilld] [kreclaimd] [kswapd] [ksoftirqd_CPU3] [ksoftirqd_CPU2] [ksoftirqd_CPU1] [ksoftirqd_CPU0] init [keventd] [keventd] [keventd] [keventd] [mdrecoveryd] [kjournald] [kjournald] [kjournald] [kjournald] [kjournald] [kjournald] syslogd -m 0 klogd -2 /usr/sbin/sshd /usr/sbin/sshd -bash ps -eHf sendmail: accepting connections crond xfs -droppriv -daemon /sbin/mingetty tty1 /sbin/mingetty tty2 /sbin/mingetty tty3 /sbin/mingetty tty4 /sbin/mingetty tty5 /sbin/mingetty tty6 The above port and process views is of a host without the EBS processes running.1 .0.198.68. 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 .0. application specific ports on the various tiers.0.0:4443 0.0:* 0.0. Local Address 0.0.oracle/s#23574.198.0..26:17060 Foreign Address 0.0.198.0:* 0.0.0.0:* 0.0.68.0.0.0:* 0.0.0.0.0.1:6500 152.0:* 0. 0.0.0.0.0.0.0.font-unix/fs7100 /var/tmp/.0.oracle/s#1129.Appendix F: Sample Linux Hardening of the Application Tier CONCURRENT MANAGER TIER OPEN PORTS Open the following ports for the Concurrent Manager and Report tier components: $ netstat -ltuxpn Proto Recv-Q Send-Q tcp 0 0 tcp 0 0 tcp 0 0 Local Address 0.0:* 0.0.0.1:25 0.0.0:* 0.0.1 57 .0:1632 Foreign Address 0.0:* 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 State LISTEN LISTEN LISTEN PID/Program name 1129/tnslsnr PID/Program name 1129/tnslsnr Path /tmp/.0:22 127. Appendix F: Sample Linux Hardening of the Application Tier 58 . Encrypt Credit Card Data 12.just like this PDF file is an attachment to the note.1 Secure Configuration Guide for Oracle E-Business Suite Release 12 The checks implemented are              1. Implement IP address restrictions 6. Enable Application Tier Secure Socket Layer (SSL) 8.sql file per check .sql 2. Secure Configuration of Attachments 10. Use Secure Flag on DBC File 5. Secure APPLSYSPUB 4.zip which is an attachment to MOS Note 403537. Migrate to Password Hash 7.sql which is a driver that runs all (11) other SQL scripts.sql 3.sql EBSCheckUserPasswords. The EBSSecConfigChecks.sql script will call the following SQL scripts 1.sql EBSCheckProfileWarnings. Change Default Passwords   EBSCheckDBPasswords. Secure APPLSYSPUB 59 .except for EBSCheckModSecurity.sh which is a shell script and EBSSecConfigChecks.1 Secure Configuration Guide for Oracle E-Business Suite 403537.1 (this note) . Move Off of Client/Server Components 9. Separation of Duties: Review Access To “Sensitive Administrative Pages” These checks are mostly implemented as a single . Check Profile Settings    EBSCheckProfileErrors.Appendix G: Security Check Scripts Appendix G: Security Check Scripts With this version of this document we have included a set of scripts to verify the proper setting of many of the values recommended in this document. Change Default Passwords 3. It implements a selection of checks for the advice in the EBS Secure Configuration Guide documents found at   189367.sql EBSCheckApplsyspubPrivs. These scripts are the implementation of the security checks described in the Oracle Open World 2012 presentation CON9031: The Top 10 Things You Can Do to Secure Your Oracle E-Business Suite Instance The scripts can be found in the zip archive EBSSecConfigChecks. Check Profile Settings 2. Turn on ModSecurity 11. Migrate to Password Hash  EBSCheckHashedPasswords.no script 9.sql 4.zip [ora1213@cosdev12 ~]$ cd EBSSecConfigChecks/ RUNNING THE SQL SCRIPTS All the scripts are designed to run as APPS against the database.zip archive file unzip all the scripts to a new directory EBSSecConfigChecks. run from shell prompt 11. 60 .not run by default.no script 6.part of profile scripts 10.sql 8.sql -. Use Secure Flag on DBC File  EBSCheckServerSecurity.sql 5. output may be verbose INSTALLING THE SQL SCRIPTS The EBSSecConfigChecks. Move Off of Client/Server Components  -. Turn on ModSecurity  EBSCheckModSecurity.sql 7. Separation of Duties: Review Access To “Sensitive Administrative Pages”  EBSCheckSensitivePageAccess. Encrypt Credit Card Data  EBSCheckCCEncryption. You can install them on either the database server or on the app-tier. You can choose to initially have EBSSecConfigChecks. You can then fix any issues one by one and rerun just the script that pointed out the issue you are currently addressing.sql run all the sql scripts to get an idea of what tasks remain.Appendix G: Security Check Scripts  EBSCheckApplsyspubPrivs.sql 12.not run from sqlplus. they just need SQL*Net connection to the database. Enable Application Tier Secure Socket Layer (SSL)  EBSCheckSSL. Implement IP address restrictions  -. If you downloaded the zip to your home directory you can simply unzip it right there and the run from the new directory [ora1213@cosdev12 ~]$ unzip EBSSecConfigChecks. Secure Configuration of Attachments  -.sh -. 0 . Note that EBSSecConfigChecks.7. 61 . The EBSSecConfigChecks. Enter password: Connected to: Oracle Database 11g Enterprise Edition Release 11. 2008. All rights reserved.sql creates a spool file EBSSecConfigChecks.sql has an exit at the end. Review the results in EBSSecConfigChecks.sql and set them in sqlplus before running the scripts.0 . you may want to copy the column specs from EBSSecConfigChecks.Production on Mon Oct 1 13:29:13 2012 Copyright (c) 1982.0. so after providing the APPS password.. OLAP.1.sql SQL*Plus: Release 11.SQL This shows one way to run the script [ora1213@cosdev12 EBSSecConfigChecks]$ sqlplus APPS @EBSSecConfigChecks.Production With the Partitioning. If you rerun the individual "profile" scripts.0.7. the script runs to the end and sqlplus exits..txt. Oracle.1. Data Mining and Real Application Testing options *************************************************** * Check: Security Profiles: Configuration ERRORS *************************************************** .Appendix G: Security Check Scripts RUNNING EBSSECCONFIGCHECKS.txt in the current directory. Appendix G: Security Check Scripts 62 . 1 AppsDataSource. John Abel.1 Document Best Practices for Securing Oracle E-Business Suite Release 12 (this document) 189367.1 Oracle E-Business Suite R12 Configuration in a DMZ (external deployment) 376700.1 FNDCPASS Troubleshooting Guide For Login and Changing Applications Passwords 1334930.1 Using TDE Column Encryption with Oracle E-Business Suite Release 12 828229. Theriault. Aaron Newman PF “Oracle Security .1 Best Practices for Securing Oracle E-Business Suite (11i version of this document) 361482.1 Enhancing Oracle E-Business Suite Security with Separation of Duties 362663.1 FNDCPASS Utility New Feature: Enhance Security With Non-Reversible Hash Password 946372.1 Enabling SSL in Release 12 (also covers encrypting database TNS traffic) 376811.1 Integrating Oracle E-Business Suite Release 12 with Oracle Internet Directory and Oracle Single Sign-On 419475.1 Using TDE Tablespace Encryption with Oracle E-Business Suite Release 12 1091083. Integrigy Corporation IntB “Oracle Applications 11i Security Quick Reference”.1 Sensitive Administrative Pages in Oracle E-Business Suite 1357849.1 Secure Configuration of E-Business Suite Profiles 974949. Jeffrey T.Appendix H: References & More Resources Appendix H: 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. and Utilities for Oracle EBusiness Suite 732764.1 How to Implement (Signon Password Custom) Profile Option in Oracle Applications 11i / R12 1306938.Step by Step”. Integrigy Corporation MTAN “Oracle Security Handbook : Implement a Sound Security Plan in Your Oracle Environment”. Pete Finnigan JA Oracle E-Business Suite Security.1 Removing Credentials from a Cloned EBS Production Database 457166. Hare. ISBN-13: 978-0-07-226276-6 JTH Oracle E-Business Suite Controls: Application Security Best Practices.1 Security Configuration Mechanism in the Attachments Feature in Oracle E-Business Suite 63 .1 Oracle Default Password Scanner (scan for open database accounts) 380490. Marlene L. ISBN13: 978-0-557-19313-4 MOS ID 403537.1 Integrating Oracle E-Business Suite Release 12 with Oracle Database Vault 11gR2 950018. Java Authentication and Authorization Service. DocID Document CIS The Center for Information Security: Oracle Benchmark Tools IntA “Guide to Auditing in Oracle Applications”. Appendix H: References & More Resources 64 . Security Checklist Security Checklist This section contains a summary of this document’s best practice suggestions and their page locations. Use this summary as a security reference guide or checklist. 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 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 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 2 2 2 2 2 5 5 6 6 6 7 8 9 9 9 9 10 10 11 11 11 11 11 12 13 13 13 13 13 14 14 65 . Security Checklist Oracle Application Tier Security     Harden operating environment Harden Apache configuration Protect administrative web pages Configure logging Oracle E-Business Suite Security                                    66 Harden operating environment Strike passwords from adpatch logs Set Workflow notification mailer SEND_ACCESS_KEY to N Set Tools environment variables Restrict filetypes that may be uploaded Enable Antisamy HTML filter 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 15 15 15 16 17 17 18 18 18 18 19 19 19 20 20 22 22 22 22 22 23 23 24 24 25 25 26 27 27 27 28 28 28 29 29 29 30 30 30 . Security Checklist Desktop Security     Configure browser Update browser Turn off AutoComplete Set policy for unattended PC sessions Operating Environment Security                Cleanup file ownership and access Cleanup file permissions Lockdown operating system libraries and programs Filter IP packets Prevent spoofing Eliminate telnet. 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 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 31 31 31 31 33 33 34 34 35 35 35 35 35 35 36 36 36 36 36 37 37 37 38 38 38 38 39 41 67 . 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: Security Check Scripts    Installing the SQL scripts Running the SQL scripts Running EBSSecConfigChecks.sql Appendix H: References & More Resources 68 60 60 61 .
Copyright © 2024 DOKUMEN.SITE Inc.