Security Configuration Guide
Contents
1. sssssseen emm 5 1 5 3 Securing the WebLogic Server installation 5 1 5 3 1 Network perimeter protection esses 5 1 5 3 2 Operating System Users and Groups sse 5 1 5 8 3 File System Access to OS Users sss 5 2 5 3 4 Usage of Protected Ports esse aenean eda 5 2 5 3 5 Choice of the SSL Cipher suite ssssssssssss seen 5 2 5 3 6 Usage of WebLogic Connection Filters sss 5 3 5 3 7 Usage of Domain wide Administration Port for Administrative Traffic esses 5 3 5 3 8 Secure the Embedded LDAP port sse 5 4 9 3 9 Precautions when using SNMP 5 4 5 4 Securing the WebLogic Security Service ssssssee en 5 4 5 4 1 Enable SSL but avoid using Demonstration Certificates 5 4 9 4 2 Enforce Security Constraints on Digital Certificates ssssuss 5 4 5 4 8 Ensure that Host Name Verification is Enabled sss 5 5 5 44 Impose Size and Time Limits on Messages ssssenes 5 5 5 4 5 Restrict the Number of Open Sockets ssssssssssseees 5 5 5 4 6 Configure WebLogic Server to Manage Overload ssssusss 5 6 5 4 7 User Lockouts and Login Time Limits essen 5 6 9 4 8 Enable Configuration Auditing sss 5 6 5 49 System2. Most server operating systems allow auditing file and directory access Oracle Financial Services recommends enabling this feature in order to track file system access violations It is not recommended to enable audit for normal file access operations audits should preferably contain records of violations to reduce the amount of noise in the logs Administrators should ensure sufficient disk space for the audit log Additionally administrators should factor the increase on server load due to auditing being enabled Separation of Concerns It is not recommended to perform development of any kind on a production machine The standard practice is to establish a separate development environment for developers isolated from the testing staging and production environments Additional environments can be created for other purposes for instance a post production support environment Backup Controls Back ups should be taken regularly This will minimize downtime if there is an emergency Access to the application areas should not be at the operating system level On line archival of redologs should be set up from the date of going live It is recommended that e Backup of all database related files viz data files control files redologs archived files init ora config ora etc should be taken at the end of the day e The tape can be recycled every week by having day specific tapes e On line backup of archived redo log files onto a me
3. ORACLE Security Configuration Guide April 2013 Version 14 0 0 0 0 Oracle Financial Services Software Limited Oracle Park Off Western Express Highway Goregaon East Mumbai Maharashtra 400 063 India Worldwide Inquiries Phone 91 22 6718 3000 Fax 91 22 6718 3001 www oracle com financialservices Copyright 1998 2013 Oracle and or its affiliates All rights reserved Oracle and Java are registered trademarks of Oracle and or its affiliates Other names may be trademarks of their respective owners U S GOVERNMENT END USERS Oracle programs including any operating system integrated software any programs installed on the hardware and or documentation delivered to U S Government end users are commercial computer software pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplication disclosure modification and adaptation of the programs including any operating system integrated software any programs installed on the hardware and or documentation shall be subject to license terms and license restrictions applicable to the programs No other rights are granted to the U S Government This software or hardware is developed for general use in a variety of information management applications It is not developed or intended for use in any inherently dangerous applications including applications that may create a risk of personal injury
4. e Browsers should be upgraded whenever newer versions are released for they often include new security features Additionally in built security features of browsers should not be turned off e Security patches issued by the Operating System vendor should be applied regularly e Updates to anti virus software and anti spyware programs should be applied regularly e Security Updates to other environmental software like Microsoft Core XML Services MSXML should be applied regularly Additionally it is recommended that major upgrades such as browser upgrades and Operating System service packs be tested for impact on business continuity Hardening Microsoft Internet Explorer OFSLL is certified for usage in Microsoft Internet Explorer version 8 and 9 Microsoft has provided guidance for enhancing Internet Explorer security in the following documents for the respective versions of the browsers e Internet Explorer 8 Desktop Security Guide e Internet Explorer 9 Desktop Security Guide Customers are encouraged to employ the recommendations provided by Microsoft in the above mentioned guides Among the guidelines provided in these documents Oracle Financial Services specifically recommends the following settings to all customers of OFSLL e Certificate Security e Ensure the usage of SSL 3 0 and TLS 1 0 Disable SSL 2 0 as it is an insecure protocol e Privacy Settings e Set Form autocomplete options to Disabled This will prevent inadv
5. User ID Password An incorrect user ID or password was entered is wrong Display Print User Profile This function provides an on line display print of user profiles and their access rights The information includes e The user responsibility e The log in user company and branch e The time of the last login Clear User Profile A user ID can get locked into the system due to various reasons like an improper logout or a system failure The user can be reset by enabling the user through Weblogic Console Change User Password Users can use this function to change their passwords A user password should contain a minimum of eight characters parameterizable It should be different from the current and two previous passwords The program will prompt the user to confirm the new password when the user will have to sign on again with the new password There s no provision of auto generating password as per password policy maintained and emailing it to the customer with the user id Password should be created by the administrator and conveyed to the user manually just as it s given to the new employees of a company Users need to change it during their first login List of Logged in Users The user can run this program to see which users are in use within OFSLL at the time the program is being run The information includes the following e The ID of the terminal e The ID of the user e The login time ice ORACLE
6. Administrator Accounts sss 5 6 5 5 Securing the OFSLL Application ssssssssesseeeeeee eene 5 6 5 5 1 Enforce the Usage of SSL eee nnn ian 5 7 5 5 2 security constraint Ensure the Servlet Servlet is Disabled 5 7 Desktop Security eee itrestetesstieptus pio eee RAE EP luae iden 6 1 6 1 Application of Security Patches sssssssssssssseseeeeeee nennen 6 1 6 2 Hardening Microsoft Internet Explorer sssseee eem 6 1 6 3 Terminal Lockout Policy a E O T eem ennemis 6 2 Oracle Financial Services Lending and Leasing Controls 7 1 meu 7 1 7 2 Disable Eogging ciini eadeni rc det ade e veda s d 7 1 7 3 c Audit Teall ReDOT oe ene rt eed ia uae e e Diete ire 7 1 7 4 Security Violation Report sesenta hn nen R nhan ene anh n hne 7 1 TAI Sign on Messages ereer eenn eE gees beatae bhi ase edict pais 7 2 7 5 Display Print User Profile eterne nnns 7 2 7 6 X Clear User Profile eiiis edidi co ede edid dde o EE e dv 7 2 7 7 Change User PasSword ceeccccccesseneeeeeceeneeeeeeacaneeeeseaaaneeeneeceneeeeeeedunaseeceeneneeeees 7 2 7 9 Listof Eogged Ir Users ii te p e o e IU td HS REDE 7 2 1 About this Manual Introduction This document describes the various measures and practices to be adopted with a deployment of Oracle Financial Services Lending and Leasing to aid in securing the day
7. Configure WebLogic Server to start with a privileged account bind to protected ports and then change the user account to an unprivileged user account For this purpose Oracle WebLogic Server on UNIX needs to be configured to have a post bind user ID or group ID For additional details refer to the section Create and configure machines to run on UNIX in the Administration Console Online Help Choice of the SSL cipher suite Oracle WebLogic Server allows for SSL clients to initiate a SSL connection with a null cipher suite The null cipher suite does not employ any bulk encryption algorithm thus resulting in transmission of all data in clear text over the wire The default configuration of Oracle WebLogic Server is to disable the null cipher suite Ensure that the usage of the null cipher suite is disabled preventing any client from negotiating an insecure SSL connection Furthermore for installations having regulatory requirements requiring the use of only high cipher suites Oracle WebLogic Server can be configured to support only certain cipher suites The restriction can be done in config xml of the WebLogic domain Provided below is an 9 ORACLE 5 3 6 5 3 7 example config xml restricting the cipher suites to those supporting 128 bit symmetric keys or higher and using RSA for key exchange lt ssl gt lt enabled gt true lt enabled gt lt ciphersuite gt TLS RSA WITH AES 256 CBC SHA lt cipher
8. OS Users Access rights to the Oracle Home WebLogic Server product directory and the WebLogic domain directories should be provided only to the WebLogic Owner user Privileged users will anyway have access to the WebLogic Server installation by default Users in the Others category can be restricted from reading the afore mentioned directories Ensure that the following files in the WebLogic installation are available only to the WebLogic owner e The security LDAP database which is usually located in the WL_HOME user_projects domains DOMAIN_NAME servers SERVER_NAME data ldap ldapfiles directory e The keystore used in the keystore configuration of the server s e The Root Certificate Authority keystore Oracle WebLogic Server provides persistent stores for several subsystems some of which are utilized by OFSLL Ensure that access to the persistent file stores based on files is restricted to the WebLogic owner OS user The default persistent file store is located in the path DOMAIN_HOME lt domain gt servers lt servername gt data store default directory If custom user defined persistence stores have been created the same restrictions should be applied on the files and directories used by such stores Usage of Protected Ports In the case of Oracle WebLogic Server e Operate WebLogic Server using an unprivileged account bind to unprotected ports and use NAT to map protected ports to the unprotected ports e
9. not recommend the use of self signed certificates in production Consider avoiding the use of certificates with a MD5 signature usage of certificates with SHA 1 signatures is recommended Most root and intermediate CAs have begun phasing out the use of MD5 for signing certificates Enforce Security Constraints on Digital Certificates Oracle WebLogic Server performs certificate validation whenever it establishes an outbound SSL connection or when a two way SSL connection is established As part of certificate validation WebLogic Server checks if the certificate contains the Basic Constraints extension Ensuring the presence of the Basic Constraints extension will prevent attackers from generating new certificates to aid in website spoofing 94 ORACLE 5 4 3 5 4 4 5 4 5 Ensure the check for Basic Constraints extension is enabled by verifying whether the following line is absent in the WebLogic Server startup command Dweblogic security SSL enforceConstraints off Also verify if any messages have been logged at WebLogic server boot providing information about the presence of certificates that could be rejected by clients Ensure that Host Name Verification is Enabled Oracle WebLogic Server implements host name verification when it acts as a SSL client this prevents man in the middle attacks from being performed against SSL itself It should be noted that the OFSLL application deployed on WebLogic Server will establ
10. to day operations of the system The document also describes in detail the security and audit features of Oracle Financial Services Lending and Leasing Audience The documentis a prescriptive guide for application implementers system administrators and related IT personnel Organization of the document The document addresses the areas of installation configuration deployment and operation of Oracle Financial Services Lending and Leasing in the below described manner About this Manual gives information on the intended audience It also lists Chapter the various chapters covered in this User Manual Data Center Practices prescribes generally accepted practices for install Chapter 2 ing configuring and operating the software components of Oracle Finan cial Services Lending and Leasing in a data center Oracle Database Security describes the measures to be undertaken to Chapters harden and secure the Oracle Database Server in the OFSLL installation Chapter 4 Application Server Security describes the measures to be undertaken to P harden and secure the Oracle WebLogic Server in the OFSLL installation Desktop Security provides information about practices to be employed for Chapter 5 client workstations Chapter 6 Oracle Financial Services Lending and Leasing Controls provides infor mation about controls within the product t1 ORACLE 2 1 2 2 2 3 2 4 2 5 2 Data C
11. Backups RMAN secure backup should be used to ensure that the backups stolen from your system cannot be restored in another remote system Additionally data masking a feature offered by Oracle Enterprise Manager can be used to move data from your production environment to a test environment Both these are very crucial steps towards securing confidential customer data The database backups should be stored for the required period as per the regulations and bank s history retention policies These backups should be securely stored and access should be controlled to authorized users only Separation of Roles It is vital to ensure that roles and responsibilities of database administrators and application users administrators are clearly segregated Database administrators should not be allowed to view or access customer data Oracle Database vault helps to achieve this separation of duty by creating different realms factors and rule sets It can enforce policies that prevent a DBA from accessing an application realm The product has a set of configuration policies that can be directly implemented with database vault Implementation specific requirements can be imposed over and above these Securing Audit Information Oracle Audit vault is an audit solution that consolidates detects monitors alerts and reports n audit data for security auditing an compliance Oracle Audit vault provides mechanisms to collect audit data from vari
12. CONCerNS isinin eeii taada aikanaan eene neret nennen nnne 2 3 2 14 Backup Controls ere tiet een toe tte aget e ud e te Haa ee RA RRRR S aan es 2 3 Oracle Database Security cceeeccceccceeeeeeeeeseeeeeeeeseseeeeeeeceeeeeeeeeeeeeeees 3 1 9 1 TOVOIVIGW dar xot ueste dtf utet emu 3 1 92 Hatrdernling c sec eaaet DP eee ages 3 1 3 3 A thenticatlofi rider anced ie ia ead ra gate eee da ege iaa ra Ra e de erence 3 1 3 4 s A thotriZatiOn sects e to e ttd cae eer ap isse kde e tete a eae ce HA se Ded 3 1 3 5 Adis iiic Ee Pede ec eR heated Te re Ro c EYE Eee ais e Ea ee e ted eee 3 2 3 6 Secure Database Ba kU pS a a aa a a a a a aeaa aa nnn 3 4 3 7 Separation Of Roles eene errem eret enne nnne 3 4 3 8 Securing Audit Information a a aai EAEE TEE eene 3 4 3 9 Advanced Security ied ex dete E ede it lati ease ede eos 3 4 Database Operating Environment Security 4 1 41 WOVEIVICW etre ate ete otitis eck betae fet tks it meret d 4 1 42 Bardenihg nieto Ee en In Mia pee 4 1 4 3 Authentication e e Ut dite ege laete biais t Mast 4 2 4 4 Authorization iii e RR ett tao E e dts 4 2 4 5 Maintenance 5 5 e HE toe EE P Y eae d bb Deva la ev dida gua eae 4 3 Application Server Security ccccccccceeeceeeeeeeeneneeeeeeeeeeeeeeeeeeeeeeeeeeeeaaes 5 1 5 1 OVeDVIeW occi er mie Eno tyr E tee e DLE he a ERR PERSA 5 1 5 2 Installation of Oracle WebLogic Server
13. If you use this software or hardware in dangerous applications then you shall be responsible to take all appropriate failsafe backup redundancy and other measures to ensure its safe use Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitted in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify license transmit distribute exhibit perform publish or display any part in any form or by any means Reverse engineering disassembly or decompilation of this software unless required by law for interoperability is prohibited The information contained herein is subject to change without notice and is not warranted to be error free If you find any errors please report them to us in writing This software or hardware and documentation may provide access to or information on content products and services from third parties Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content products and services Oracle Corporation and its affiliates will not be responsible for any loss costs or damages incurred due to your a
14. Security Configuration Guide Oracle Financial Services Lending and Leasing Release 14 0 0 0 0 April 2013 Oracle Part Number E51531 01 ORACLE FINANCIAL SERVICES Table of Contents About this Manual 5 i iret ce sven decctvccsernscectcacsce eacnce rax E EU e Cr EDU en E 1 1 1 1 Introduction tier th e urere atero Par ap rasa o send deanna MEA ea EIER ert Renee 1 1 JAEN Ule 1 1 1 38 Organization of the document sssssssssssseene nennen nennen nnns 1 1 Data Center Practices induce Eid iade Eie I aces opri teenies 2 1 2 1 Ove W sarah Ais eT at ed Tee eee sade ele eee ae ao eau eda ce 2 1 2 2 Physical System Security anirnar e a e ar E AN aF 2 1 2 3 Minimize the Server Footprint nemen 2 1 2 4 Operating System Users and Groups sse ee 2 1 2 5 Restrict File System ACCESS epre anria o a netten seh itane nn dn then nnn nnn 2 1 2 6 Network Perimeter Protection ssssssssssssssseseeee eem eene 2 2 2 7 Network Service Protection sssssssssseseseeeeeeeem eee 2 2 2 8 Usage of Protected Ports ssssssssssssssss eene eee nnne 2 2 2 9 Installation of Software in Production Mode ssee 2 2 2 10 Software Updates and Patches ssssssssssssssssseemereennene enn 2 2 2 11 Usage of Security Appliances and Software sssssseeen 2 3 2 12 Configure Security Auditing iaar ra ena aE EER eene 2 3 2 13 Separation of
15. Server cluster restrict access to the embedded LDAP server port only to machines in the WebLogic Server cluster through the user of connection filters Precautions when using SNMP It is recommended to refer the WebLogic SNMP Management Guide to configure SNMP agents in Oracle WebLogic Server Due care must be observed over the usage of SNMP v1 and v2 since passwords are sent over clear text in these older version of the protocol Additional steps required for securing SNMP v3 communication are outlined in the guide Oracle Financial Services recommends that changes once done in this regard be tested thoroughly for impact on business continuity Securing the WebLogic Security Service You need to ensure the following Enable SSL but avoid using Demonstration Certificates Enable the use of SSL so that the servers can be accessed via the SSL listen ports for all supported protocols including HTTPS Oracle WebLogic Server includes demonstration private keys certificates and trusted certificate authorities that are not intended for use in production Usage of these keys in production is a security risk due to the free availability of private keys anyone who has a copy of the WebLogic Server has knowledge of the private keys and can compromise SSL TLS traffic Therefore e Use a local CA to issue certificates or e Use a root or intermediate CA like VeriSign Thawte etc to issue certificates Oracle Financial Services does
16. abase which is not required for production usage Securing the WebLogic Server installation Once installed the measures listed below can be employed to secure the WebLogic Server installation Network perimeter protection It is highly recommended to employ the use of a firewall as hardware or software to lockdown the network access to the WebLogic cluster For additional information on planning the firewall configuration for a WebLogic Cluster refer to the section Security Options for Cluster Architectures in the Using Clusters guide of the Oracle WebLogic Server documentation Operating System Users and Groups It is highly recommended to run the WebLogic Server as a limited user process The root user account in Unix Linux and the Administrator account in Windows should not be used to run WebLogic Server since they are privileged user accounts Other privileged accounts should also not be used to run the WebLogic server Hence it is preferable to create a limited user account say WebLogic Owner for running the application server Additional user accounts are not recommended in the eventuality that an additional account is required say if the WebLogic owner account is locked out one of the system administrator accounts can be used to remedy the situation Having two system administrator accounts is recommended as it always ensures backup al ORACLE 5 3 3 5 3 4 5 3 5 File System Access to
17. ally lockout unattended PC sessions after a certain duration This is primarily because OFSLL will not lock out the browser session although it does expire the browser session after certain period of inactivity Users may however be able to access unattended sessions while the OFSLL user is still logged in Hence organizations are expected to set a corporate policy for handling unattended PC sessions it is recommended to enable the feature to lock workstations or to enable password protected screen savers o ORACLE 7 Oracle Financial Services Lending and Leasing Controls 7 1 Overview This chapter describes the various programs available within OF SLL to help in the maintenance of security Access to the system is possible only if the user logs in with a valid ID and the correct password The activities of the users can be reviewed by the Security Officer in the Event Log and the Violation Log reports 7 2 Disable Logging It is recommended that the debug logging facility of the application be turned off once the system is in production This is achieved by configuring the ADF Logging from Oracle Fusion Middleware Enterprise Management Console The above described practice does not disable logging performed by the application in the database tier This can be disabled by running the lockdown scripts provided The lockdown scripts will disable logging across all modules and across all users in the system 7 3 Audit Trai
18. are not set on binaries In general Oracle recommends that the SUID and SGID bits to be removed from binaries shipped by Oracle On windows systems NTFS must be used The FAT FAT32 file system provides no security The database and applications require that the underlying operating system provide certain services e Electronic Mail OFSLL may require access to a SMTP Mail Transfer Agent SMTP MTA typically send mail This is required for outbound emails typically notifications from OFSLL if this feature is desired by the financial institution If possible restrict access to the operating system users who absolutely need the mail facility from the shell 4 ORACLE 4 3 4 4 e Remote Access Use secure shell ssh to access middle tier and database hosts This replaces telnet rsh rlogin rcp and ftp The following services may provide operational convenience e NTP Network Time Protocol for synchronizing the clock on the UNIX hosts to provide accurate audit records and simplify trouble shooting e CRON for operating system cleanup and log file rotation Authentication Good security requires secure accounts e Make sure that all OS accounts are hard to guess To ensure that the passwords are not guessable use crack or john the ripper password cracking tools on a regular basis Use password cracking tools on a regular basis to ensure password complexity Often people use passwords associated with them lic
19. ccess to or use of third party content products or services
20. dia to achieve to the point recovery in case of crash shutdown etc recycled every day e Complete export of database and softbase should be done atleast once in a week and this can be stored off site media can be recycled in odd and even numbers e Complete backup of the Oracle directory excluding the database related files to be taken once in a month This media can be recycled bimonthly e When the database is huge incremental exports and on line tablespace backups are recommended The above strategy may be improvised by the Oracle DBA depending on the local needs The backup operations are to be logged and tapes to be archived in fireproof storages xs ORACLE 3 1 3 2 3 3 3 4 3 Oracle Database Security Overview This section contains security recommendations for the Database Hardening Review database links in both production and development environments Unwanted links need to be dropped Authentication Middle tier applications logon to the database through application schemas rather than end user accounts Some individuals IT Administrators may require direct access to the application database via their own schema This setting prevents the database from using an insecure logon protocol Make sure init ora contains REMOTE OS AUTHENT FALSE Following an installation the application database instance contains default open schemas with default passwords These accounts and corresponding pas
21. e tested thoroughly for impact on business continuity the definition of an overload condition depends on the system capabilities therefore overload conditions are bound to be defined differently for machines of differing capabilities User Lockouts and Login Time Limits The Oracle WebLogic Server guide on Securing a Production Environment has a section on configuring user lockouts and login time limits to prevent attacks on user accounts In general OFSLL utilize the WebLogic Security Service for managing OFSLL user accounts Therefore changes recommended by the WebLogic Server guide should be applied after assessing the impact on production The changes applied would be suitable for accounts managed by Oracle WebLogic Server Note that the WebLogic Server Online Console guide will reference Compatibility Security which is deprecated in Oracle WebLogic Server 10 3 Enable Configuration Auditing Configuration auditing can be enabled to ensure that changes to any WebLogic resource configuration in the WebLogic domain are audited Enabling this option also allows for auditing of management operations performed by a user on any WebLogic resource For additional details refer to the Administration Console Online Help and the Configuring WebLogic Security Providers section in the Securing WebLogic Server guide of the Oracle WebLogic Server documentation Note that enabling configuration auditing will affect the performance
22. em For this reason do not allow guest access Authorization Run NFS only as needed apply latest patches When creating the etc exports file use limited access flags when possible such as readonly or nosuid By using fully qualified hostnames only the named host may access the file system Device files dev null dev tty and dev console should be world writable but NEVER executable Most other device files should be unreadable and non writable by regular users 2 ORACLE 4 5 Always get programs from a known source Use a checksum to verify they have not been altered Create minimal writable file systems esp system files directories Limit user file writes to their own directories and tmp Add directories for specific groups Limit important file access to authorized personnel Use setuid setgid only where absolutely necessary Maintenance Good security practice does not end after installation Continued maintenance tasks include Install the latest software patches Install latest operating system patches Verify user accounts delete or lock accounts no longer required Run security software and review output Keep up to date on security issues by subscribing to security mailing lists reading security news groups and following the latest security procedures Implement trusted file systems like NIS NIS or others such as HP UX trusted system Test the system with tools like NESSUS network security a
23. ense plate numbers children s names or a hobby A password tester may check for these In addition change passwords from time to time e Automatically disable accounts after several failed login attempts e _ netrc files weaken security e The fewer people with root access the easier it is to track changes e The root password must be a strong hard to guess In addition change the root password every three 3 months and whenever an administrator leaves company Always logout of root shells never leave root shells unattended e Limit root to console login only specified in etc security e Root and only root should have UID 0 e Check root files for security holes The root files SHOULD have 700 or 600 permissions e umask for root is 022 rwxr xr x A umask of 077 rwx is best but often not practical e To avoid trojan horse programs always use full pathnames including aliases Root should NEVER have in path e NEVER allow non root write access to any directories in root s path e f possible do not create root s temporary files in publicly writable directories Do not share user accounts Remove or disable user accounts upon termination Disable login for well known accounts that do not need direct login access bin daemon sys uucp Ip adm Require strong passwords and in some cases a restricted shell It is hard to imagine what kind of guests should have access to a production syst
24. enter Practices Overview The following guidelines are recommended to secure the host servers Application Server Database Server and others in an installation of OFSLL Physical System Security It is highly recommended to operate servers in a secured data center to prevent unauthorized users or operating personnel from tampering with the machines Minimize the Server Footprint Each logical software component Application Server Database Server etc in the installation should preferably operate in a dedicated server It is not recommended to operate multiple services like mail FTP LDAP etc on the same server unless absolutely necessary It is preferable to customize the operating system installation so that only the minimum set of software components is installed Development tools should not be installed on the production servers In cases where a software package should be compiled and built before installation it is advisable to perform the build process on a separate machine following which installation of the binary can be performed on the server Samples and demos should not be deployed on a production server since they are bound to be developed without considering security Any bugs in such software can be exploited by an attacker resulting in a security incident Operating System Users and Groups It is recommended to minimize the number of user accounts on the host for easier auditing and management Be
25. ertent caching of data keyed by users In addition to the above it is recommended to enable the popup blocker with a specific rule to disable popup blocking for the OFSLL web application Application of the following guidelines from Microsoft is not recommended e Privacy Settings e Empty Temporary Internet Files Folder When Browser is closed OFSLL relies heavily on client side caching performed by Internet Explorer using this folder The application will behave slowly after this setting is enabled since the browser will download resources from the server after every browser restart Hence it is not recommended to enable this setting It should be noted that the details of transactions performed by the OFSLL users are not cached in the Temporary Internet Files folder irrespective of this setting e Other Security Recommendations 91 ORACLE 6 3 e Do not Save encrypted pages to disk By default Internet Explorer stores both encrypted and unencrypted content in the Temporary Internet Files folder Enabling this setting is bound to cause performance issues especially when OFSLL is accessed over HTTPS since the browser will no longer cache resources As stated before details of transactions performed by users will not be cached in the Temporary Internet Files folder irrespective of this setting Terminal Lockout Policy Oracle Financial Services recommends that a terminal lockout policy be put in place to automatic
26. esource collection gt lt web resource name gt images lt web resource name gt lt url pattern gt faces skins lt url pattern gt lt url pattern gt faces images lt url pattern gt lt web resource collection gt lt security constraint gt lt security constraint gt lt web resource collection gt lt web resource name gt OFSLL lt web resource name gt lt url pattern gt faces lt url pattern gt lt web resource collection gt lt user data constraint gt transport guarantee CONFIDENTIAL transport guarantee user data constraint 5 5 2 lt security constraint gt Ensure the Servlet Servlet is Disabled OFSLL does not use the ServletServlet to create default mappings for servlets All servlets are directly mapped to the required URLs Ensure that the following code snippet or a similar one that uses the weblogic servlet ServletServlet does not exist in the web xml of the OFSLL web application lt servlet gt lt servlet name gt ServletServlet lt servlet name gt lt servlet class gt weblogic servlet ServletServlet lt servlet class gt lt servlet gt servlet mapping lt servlet name gt ServletServlet lt servlet name gt url pattern myservlet url pattern lt servlet mapping gt ai ORACLE 6 1 6 2 6 Desktop Security Application of Security Patches Oracle Financial Services highly recommends the following
27. ish outbound SSL connections in certain scenarios for instance when requests are made to the Oracle BI Publisher server In such an event Oracle WebLogic Server will behave as a SSL client Oracle WebLogic Server will behave as a SSL client in several scenarios besides the outbound SSL requests made by applications deployed on Oracle WebLogic Server For instance managed servers will establish SSL connections with the Admin server at boot time Hence it is recommended to ensure that host name verification is enabled in Oracle WebLogic Server which happens to be the secure default Oracle Financial Services highly recommends the usage of certificates that will pass verification Oracle Financial Services also recommends against the usage of demonstration certificates in production It should be noted that usage of demonstration certificates in a testing or development environment containing a multi server WebLogic cluster will result in boot failures for managed servers Impose Size and Time Limits on Messages Consider enforcing constraints on size and on the amount of time taken for a message to arrive at the server This will ensure protection against denial of service attacks against WebLogic Server Additional details are provided in the Oracle WebLogic Server documentation in the guide Securing a Production Environment and also in the Administration Console Online Help Oracle Financial Services recommends that changes
28. issue the following command SQL gt audit user To complete the recommended auditing enable three other audit events create database link alter system and system audit The remaining audit options generate significant entries of little value To audit the other events login through sqlplus as SYSTEM and issue the following commands SQL AUDIT DATABASE LINK Audit create or drop database links SQL AUDIT PUBLIC DATABASE LINK Audit create or drop public database links SQL AUDIT SYSTEM AUDIT Audit statements themselves SQL gt AUDIT ALTER ANY ROLE by ACCESS Audit alter any role statements SQL gt AUDIT ALTER DATABASE by ACCESS Audit alter database statements SQL gt AUDIT ALTER SYSTEM by ACCESS Audit alter system statements T ORACLE SQL gt AUDIT CREATE ROLE by ACCESS Audit create role statements SQL gt AUDIT DROP ANY ROLE by ACCESS Audit drop any role statements SQL gt AUDIT PROFILE by ACCESS Audit changes to profiles SQL gt AUDIT PUBLIC SYNONYM by ACCESS Audit public synonyms statements SQL gt AUDIT SYSDBA by ACCESS Audit SYSDBA privileges SQL gt AUDIT SYSOPER by ACCESS Audit SYSOPER privileges SQL gt AUDIT SYSTEM GRANT by ACCESS Audit System grant privileges Connections to the database as well as SYSDBA and SYSOPER actions instance startup shutdown are always logged to the directory SORACLE HOME rdbms audit unless AUDIT FILE DEST property is overridden Thi
29. l Report A detailed Audit Trail is maintained by the system on all the activities performed by the user from the moment of login This audit trail lists all the functions invoked by the user along with the date and time The program reports the activities beginning with the last one It can be displayed or printed The records can be optionally purged once a printout is taken This program should be allotted only to the Security Officer 7 4 Security Violation Report This program can be used to display or print the Violation Report The report gives details of exceptional activities performed by a user during the day The difference between the Violation Report and the Audit Trail is that the former gives details of all the activities performed by the users during the day and the latter gives details of exceptional activities for e g forced password change unsuccessful logins enabled through Weblogic server User already logged in etc The details given include e Time e The name of the operator e The name of the function e The ID of the terminal e A message giving the reason for the login The system gives the Security reports a numerical sequence The Security Report includes the following messages f ORACLE 7 4 1 7 5 7 6 T T 7 8 Sign on Messages Message Explanation User Already The user has already logged into the system and is attempting a Logged In login through a different terminal
30. nce impact In init ora set AUDIT TRAIL to DB OS or TRUE Consult with the Applications Database Administrator before setting this value to TRUE When set to OS 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 By default the operating system files are in the SORACLE BASE admin ORACLE SID adump directory for both UNIX and Windows systems AUDIT FILE DEST opt app oracle admin ORCL adump Restart the database for these parameters to take effect Note The database generates some audit records by default whether or not AUDIT TRAIL is enabled For example Oracle automatically creates an operating system file as an audit record when a user logs in as SYSDBA or as INTERNAL Monitoring and auditing database sessions provides valuable information on database activity and is the only way to identify certain types of attacks for example password guessing attacks on an application schema By auditing database sessions suspicious connections to highly privileged schemas may be identified To audit sessions login through sqlplus as SYSTEM and issue the following command SQL audit session Audit any changes to the standard OFSLL database schema or creation of new schemas As rare events these changes may indicate inappropriate or malicious activity To audit schema changes login through sqlplus as SYSTEM and
31. nd CRACK password checker Install Tripwire to detect changes to files Monitor log files including btmp wtmp syslog sulog etc Consider setting up automatic email or paging to warn system administrators of any suspicious behaviour Also check the snort logs The environment in which Oracle Applications run contributes to or detracts from overall system security This section contains security recommendations for tightening Oracle file system security along with more some generaladvice guidelines for overall system hardening Te ORACLE 5 1 5 2 5 3 5 3 1 5 3 2 5 Application Server Security Overview This section describes how to secure the Oracle WebLogic Server production environment that hosts the Oracle Financial Services Lending and Leasing environment Installation of Oracle WebLogic Server By default Oracle WebLogic Server is installed with a JDK and several development utilities These are not required in a production environment The installation footprint of Oracle WebLogic Server can be reduced via the following measures e During installation of Oracle WebLogic Server customize the components to be installed The following components are not required by Oracle Financial Services Lending and Leasing in a production environment e Oracle WebLogic Workshop e Web 2 0 HTTP Pub Sub Server e Third Party JDBC Drivers for MySQL and Sybase e WebLogic Server examples e Delete the Pointbase dat
32. of the system even though auditing may be enabled for auditing a few events including configuration changes System Administrator Accounts Create at least two system administrator accounts WebLogic user accounts for administration of the WebLogic server The first administrator account will be created when the WebLogic domain is created Create the second account with the Admin security role Provide unique names to the administrator accounts that cannot be easily guessed Oracle Financial Services discourages naming the WebLogic administrator account as weblogic with a password of weblogic Again having two system administrators ensures that at least one system administrator has access to the WebLogic server in the event of the other being locked out Securing the OFSLL Application The following guidelines serve to secure the OFSLL application deployed on Oracle WebLogic Server 9 ORACLE 5 5 1 Enforce the Usage of SSL The OFSLL Installer allows a deployer to configure OFSLL such that all HTTP connections to the OFSLL application are over SSL TLS In other words all HTTP traffic will be prohibited only HTTPS traffic will be allowed It is highly recommended to enable this option is in a production environment especially when WebLogic Server acts as the SSL terminator Ensure that the following snippet of code is present in the web xml file of the OFSLL web module security constraint lt web r
33. once done in this regard be tested thoroughly for impact on business continuity it is quite possible that WebLogic Server receive valid messages that are large enough to be considered as an attack when such is not the case Restrict the Number of Open Sockets Consider limiting the number of sockets opened by WebLogic Server to prevent some forms on denial of service attacks Further details are available in the Oracle WebLogic Server documentation in the guide Securing a Production Environment and also in the Administration Console Online Help Oracle Financial Services recommends that changes once done in this regard be tested thoroughly for impact on business continuity the number of sockets opened is dependent entirely on system load which is bound to vary across time and also across installations v9 ORACLE 5 4 6 5 4 7 5 4 8 5 4 9 5 5 Configure WebLogic Server to Manage Overload Oracle WebLogic Server can be configured to detect avoid and recover from overload conditions Configuring WebLogic Server to manage overload conditions allows for WebLogic Server administrators to connect to it and take remedial actions Further details on this topic are available in the Oracle WebLogic Server documentation in the guide Securing a Production Environment and also in the Administration Console Online Help Oracle Financial Services recommends that changes once done in this regard b
34. ous oracle database It helps to consolidate audit data from multiple Systems into a single centralized repository Thus DBA s of individual systems will not be able to tamper with audit information of their respective databases Advanced Security Oracle Advanced Security provides industry standards based data privacy integrity authentication single sign on and access authorization in a variety of ways Sensitive information that is stored in your database or that travels over enterprise networks and the Internet can be protected by encryption algorithms An encryption algorithm transforms information into a form that cannot be deciphered without a decryption key Oracle Advanced Security supports multiple industry standard encryption algorithms such as RC4 DES3 and Triple DES To ensure the integrity of data packets during transmission Oracle Advanced Security can generate a cryptographically secure message digest using MD5 or SHA 1 hashing algorithms and include it with each message sent across a network x ORACLE 4 1 4 2 4 Database Operating Environment Security Overview The environment in which Oracle Applications run contributes to or detracts from overall system security This section contains security recommendations for tightening Oracle file system security along with more general advice for overall system hardening Hardening e The directory ORACLE_HOME bin contains Oracle executables Check that the opera
35. re that only certain machines in the data center can access the WebLogic Server services like HTTP LDAP RMI IIOP etc Usage of Domain wide Administration Port for Administrative Traffic When Oracle WebLogic Server is configured to enable administrative access via the administration port data is exchanged over SSL preventing any attacker from sniffing sensitive information about the WebLogic Server configuration Furthermore once the Administration port is enabled WebLogic Server will serve administration requests on a dedicated port with dedicated resources A denial service attack mounted on the HTTP HTTPS channels will not prevent administrators from logging into the WebLogic Server administration console to take corrective actions Hence it is recommended to enable the use of the administration port Additionally employ firewall rules or WebLogic Connection Filters to restrict access to the Administration Port to trusted machines from where administrators can log in s ORACLE 5 3 8 5 3 9 5 4 5 4 1 5 4 2 Do note that the Administration Port requires that SSL be enabled and also on every Managed Server Additionally the administration port will be common across all managed servers in the domain Further details on configuring the administration port can be found in the Administration Console Online Help guide in the Oracle WebLogic Server documentation Secure the Embedded LDAP port In a WebLogic
36. s For example Oracle WebLogic Server should be installed in the production mode as opposed to the default of development mode The Oracle Database Server should be installed with options required for production usage for instance do not install the sample schemas Moreover it is highly recommended to refer to the manuals and documentation provided by the software supplier for installing and operating such software securely in a production environment Software Updates and Patches It is recommended to subscribe to security bulletins and advisories published by software vendors to ensure that critical servers are always up to date e ORACLE 2 11 2 12 2 13 2 14 Oracle Financial Services recommends that patches be tested to ensure that they do not conflict with the normal operation of the system Usage of Security Appliances and Software Consider the usage of security appliances and software to monitor and ensure that the production environment continues to be secure after the process of server preparation Intrusion Detection Systems can be employed to monitor for security sensitive changes in the system and alert personnel Antivirus scanners can be used to prevent the server s from being compromised Note that although UNIX like operating systems may have better defenses against viruses and other malware consider running antivirus scanners on servers regardless of the OS Configure Security Auditing
37. s file contains the operating system user and terminal ID If AUDIT TRAIL is set to OS review audit records stored in the file name in AUDIT FILE DEST If AUDIT TRAIL is set to DB retrieve audit records from the SYS AUD table The contents can be viewed directly or via the following views e DBA AUDIT EXISTS e DBA AUDIT OBJECT e DBA AUDIT SESSION e DBA AUDIT STATEMENT e DBA AUDIT TRAIL e DBA OBJ AUDIT OPTS e DBA PRIV AUDIT OPTS e DBA STMT AUDIT OPTS The audit trail contains a lot of data begin by focusing on the following e Username Oracle Username e Terminal Machine from which the user originated e Timestamp Time the action occurred e Object Owner The owner of the object that the user touched e Object Name The name of the object that the user touched e Action Name The action that occurred against the object INSERT UPDATE DELETE SELECT EXECUTE Archive and purge the audit trail on a regular basis at least every 90 days The database connection entries take up significant space Backup the audit file before purging Audit data may contain confidential or privacy related data Restrict audit trail access appropriately It must be noted that auditing features can impose a significant performance overhead Auditing should thus be limited to the set of items outlined above Auditing application schema objects should be strictly avoided ORACLE 3 6 3 7 3 8 3 9 Secure Database
38. sides it reduces the risk of unauthorized personnel accessing the server It is recommended to create user accounts with names that are hard to guess There should be at least two system administrator accounts for a server to ensure backup in the eventuality of one account being locked Passwords for all accounts should be strong passwords this should be enforced by the operating system for instance via the pam configuration in UNIX Passwords should not be easy to guess and neither should they be stored in an insecure media or written down for easy remembrance Passwords should be set to expire periodically 60 90 days is the recommended period Passwords for privileged accounts may have a shorter lifecycle Restrict File System Access It is recommended to use a file system that allows maintenance of access rights e ORACLE 2 6 2 7 2 8 2 9 2 10 In Windows NTFS allows for ACLs to be maintained at the most granular level however due care should be exercised when granting file system privileges to the Everyone group Similarly in UNIX like operating systems privileges should not be granted to the Nobody user and group unless absolutely required Network Perimeter Protection Firewall rules should be established to ensure that only a required set of services is accessible to machines outside the data center Network access can be further restricted to ensure that only certain subnets with tr
39. suite gt lt ciphersuite gt TLS RSA WITH AES 128 CBC SHA lt ciphersuite gt lt ciphersuite gt TLS RSA WITH RC4 128 SHA lt ciphersuite gt lt ciphersuite gt TLS RSA WITH RC4 128 MD5 lt ciphersuite gt ssl Note Configuration of WebLogic Server to support the above defined cipher suites might also require an additional command line argument to be passed to WebLogic Server so that a FIPS 140 2 compliant crypto module is utilized This is done by adding Dweblogic security SSL nojce true as a JVM argument Therestriction on cipher suites needs to be performed for every managed server The order of cipher suites is important Oracle WebLogic Server chooses the first available cipher suite in the list that is also supported by the client Cipher suites with RC4 are enabled despite it being second best to AES This is primarily for older clients that do not support AES for instance Microsoft Internet Explorer 6 7 and 8 on Windows XP Cipher suites using Triple DES 3DES are not listed since the maximum effective security provided by the algorithm is 112 bits Usage of WebLogic Connection Filters Although firewalls restrict the ability of machines to communicate with the WebLogic Server machines in the data center can still access network services provided by the WebLogic Server Configure the Oracle WebLogic Server installation to use connection filters to ensu
40. swords are well known and they should be changed especially for a database to be used in a production environment Use database command to change a password SQL PASSWORD or SQL gt PASSWORD USERNAME Always password command should be used because the password is sent unencrypted over the net without Advanced Security Option if the alter user syntax is used Metalink Patch note 4926128 contains a SQL script that will list all open accounts with default password in your database In addition the password to the default accounts like SYS SYSTEM etc should be complex and securely stored by the bank Authorization The init ora parameter TRACE FILES PUBLIC grants file system read access to anyone who has activated SQL tracing Set this to its default value of False TRACE FILES PUBLIC FALSE Set the init ora parameter REMOTE OS ROLES to False to prevent insecure remote roles REMOTE OS ROLES FALSE Set O7 DICTIONARY ACCESSIBILITY to False to prevent users with Select ANY privilege from reading data dictionary tables False is the default value The O7 DICTIONARY ACCESSIBILITY initialization parameter controls restrictions on system privileges when you upgrade from Oracle Database release 7 to Oracle8i and later releases O7 DICTIONARY ACCESSIBILITY FALSE s ORACLE 3 5 Audit This section describes the auditing capabilities available in Oracle database These recommendations should not have a measurable performa
41. ting system owner of these executables matches the operating system user under which the files have been installed A typical mistake is to install the executables in user oracle s directory but owned by root e Prevent remote login to the Oracle and root accounts Instead require that legitimate users connect to their own accounts and su to the Oracle account Better yet use sudo to restrict access to executables Refer to the product installation documentation for the complete instructions on setting file permissions On UNIX systems e Set the permissions on 0RACLE_HOME bin to 0751 or less Set all other directories in O0RACLE_HOME to 0750 or less Note this limits access to the Oracle user and its groups probably DBA e Set file permissions for listener ora and sqinet ora to 0600 e Set file permissions for tnsnames ora to 0644 e Ensure that the owner group and modes of the Oracle files created upon installation are set to allow minimum privilege The following commands make this change Note the group and owner are for illustration only the correct group and owner should be substituted chgrp R dba ORACLE HOME chown R oracle ORACLE HOME e Review owners and groups when cloning a database e Protect the SORACLE HOME rdbms admin directory including catalog sql catproc sql and backup scripts e Secure scripts containing usernames and passwords e Verify that set user id SUID and set group id SGID
42. usted machines and not all machines can access machines in the data center Oracle Financial Services does not recommend exposing the application server hosting OFSLL to the Internet Network Service Protection Network services installed on the server should be enabled only to serve the primary business function s that the server must provide Disable all services that are not needed to serve a justified business need Review the network services like mail and directory services running on the servers to ensure that they are adequately protected from abuse by an attacker Also review and limit the network file shares on the servers to reduce the risk of an attack on the file system It is recommended to share files and directories on servers only to trusted machines in the network Usage of Protected Ports It is not recommended to execute long processes like application servers and database servers under the root account since a compromise of such processes will result in an attacker gaining elevated privileges Therefore limit the use of protected ports port numbers less than 1024 on UNIX like operating systems since they require the use of a privileged user account in most cases this is only the root account Consider the use of NAT to map protected ports to unprotected ones Installation of Software in Production Mode It is highly recommended to install production builds of any software on production server
Download Pdf Manuals
Related Search