Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

A quick comparison chart for EBS and Fusion Application Security Models

Posted on November 6th, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

If you are coming from EBS then this post will help you to understand the difference of security model in these two application.

here is quick comparison chart all the major security features of Oracle Application (EBS) and Fusion Application side by side.

E-Business Fusion Application
Authentication

FND_USER

OID/OSSO/OAM

FMW OAM/LDAP
Authorization AOL security model
RBAC (This is optional add-on)
FMW OPSS (this is same as RBAC)
Security platform Proprietary FMW OPSS
Segregation Of Duties (SOD) No explicit functionality Predefined SOD policies
Application Access Controls
Governor (AACG)
Technology Prepackaged eBiz specific
configuration and management
FMW 11g
Management of security
(Roles/Responsibilities)
Proprietary forms OIM
APM
Proprietary forms
HR specific data security Security Groups Security Groups

Posted in Fusion Application, Security | No Comments »

Oracle IAM and Oracle Fusion Applications

Posted on October 19th, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Oracle Identity Management is major security infrastructure component of Oracle Fusion Applications .

Oracle Fusion Applications leverage Oracle Identity Management for foundation security services; identity administration (identity life cycle management, self-service account request and password management, enterprise role management); authentication and trust management (single sign-on, identity federation, privacy); access control (risk-based authorization, fine-grained entitlements, web services security); identity and access governance (audit and compliance reporting, segregation of duties, conflict-resolution management, attestation, role mining and engineering, identity and fraudprevention analytics); and directory services (persistent storage, identity virtualization,synchronization, and database-user security).

For detailed explanation of Oracle Identity Mangements integration with Oracle Fusion Applications refer this whitepaper published by Oracle.

Posted in Fusion Application, Security | No Comments »

Oracle Access Manager – Consultant Note

Posted on October 16th, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Friend of mine working in retail sector asked some queries on Oracle Access Manager usage, quickly revisited one of training note when working in health care, both the sectors extensively using these products.This Post is collection is high level overview for Oracle Access manager.

dgreybarrow What is Oracle Access Manager

Oracle Access Manager (OAM) is IAM solution for web access management and user identity administration. Oracle Access Manager is designed to support complex, heterogeneous enterprise environments. Oracle Access Manager consists of two tightly integrated components:

  • the Access
  • Identity Systems

The Identity System provides delegated administration of user profiles and workflow for creating, updating, and deleting these profiles. It also provides applications for user self registration, password management and dynamic group management. The Access System provides access control and single sign-on to Web applications and J2EE resources (EJBs, servlets, etc.) running on a variety of Web and Application servers.

dgreybarrow Two Products and there Generally Available (GA) dates

  • Identity Manager – since 1991
  • Access Manager – since 1996

dgreybarrow Components

Oracle Access Manager consists of tightly coupled Identity and Access Systems. These two systems are integrated, so that a profile change made via the Identity System takes effect instantaneously for access evaluation by Access the System. The Access and Identity Systems also include web server agents namely, WebGate and WebPass, for all leading Web and Application servers. The following components are shipped with Oracle Access Manager:

  1. Identity Server
  2. WebPass :A WebPass is a web server plug-in that passes information back and forth between the web server and the Identity Server over the Oracle Identity Protocol (formerly Netpoint or COREid Identity Protocol). Hence, WebPass is the presentation tier of the Identity System. By default, WebPass renders its content as HTML so that it can be accessed through a browser. But in addition, it provides a Web Service interface, known as IdentityXML, which SOAP-based clients can leverage to programmatically interact with the Identity System. The idea behind IdentityXML is that it allows the integration of business logic governing identity administration process to be available and easily integrated with existing applications in a SOA environment
  3. Access Server
  4. WebGate :WebGate is an out-of-the-box access client for enforcing access policy on HTTP based resources; hence it is the Access System's web Policy Enforcement Point or PEP. The WebGate client runs as a plug-in or module on top of most popular web servers, and intercepts HTTP requests for web resources and forwards them to the Access Server where access control policies are applied. WebGates are optimized to work on web server environments, as are streamlined for the HTTP protocol, and understand URLs, session cookies, HTTP redirects, secure sessions (HTTPS); and also implement policy caches that improve WebGate's performance and allow for scalability in highly trafficked sites
  5. Policy Manager :Access Manager's Policy Manager is a browser-based graphical tool for configuring resources to be protected and well as creating and managing access policies, so it is the Access System's Policy Management Authority or PMA The Policy Manager provides the login interface for the Access System, communicates with the directory server to manage policy data, and communicates with the Access Server over the Oracle Access Protocol to update the Access Server cache when policies are modified.

dgreybarrow Get Clarified on -Oracle Access Manager differ from OracleAS Single Sign-on

They are similar products in that both perform user authentication. However Oracle Access Manager also provides powerful policy-based authorization functionality to web and J2EE resources, which OracleAS Single Sign-on does not. They are currently separate products and can be used together in a single environment if required. Oracle Access Manager access also provides integrations with a broad set of non-Oracle products and platforms.

dgreybarrow 2 factor authentication(including RSA SecurID, X.509 certificates)...etc [Adopted from oracle Documentation]

The Oracle solutions supports 2 factor and X.509 authentication for user authentication with Oracle Access Manager.

  • RSA SecurID Authentication: Oracle Access Manager supports RSA Security features and provides the SecurID authentication plug-in and components needed to integrate a native SecurID authentication scheme into Oracle Access Manager policy domains for Web single sign-on. See "Integrating the RSA SecurID Authentication Plug-In" for details.
  • Smart Card Authentication: Oracle Access Manager supports smart card authentication with Active Directory and IIS Web servers using ActivCard Cryptographic Service Provider (CSP) for Windows 2000, ActivCard Gold utilities, and ActivCard USB Reader v2.0 in homogeneous Windows environments. See "Integrating Smart Cards" for details.

Posted in Security | No Comments »

What is Sensitive Administrator Functionality in EBS?

Posted on October 7th, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

dgreybarrow What is Sensitive Administrator Functionality?

These are Administrator / Developer Functionality.Some of Oracle EBS forms and pages allow a user to modify the functionality of the applications by specifying values such as

  • SQL statements or fragments
  • HTML fragments
  • OS commands

These are designed-in SQL injections or XSS injections.

These screens may constitute a security risk if used in an unauthorized fashion and should be disabled, controlled, and audited in production environments.

There are several types of these sensitive pages in EBS, and they are controlled by different mechanisms. These are typically grouped into the following categories:

  1. Oracle Forms Controlled by Function Security
  2. HTML Pages Controlled by Function Security
  3. Pages and Forms Controlled by Profile Options
  4. Pages Controlled by JTF Roles and Permissions Profiles

#3 as,Pages and Forms Controlled by Profile Options , typically Includes:

1) for the feature OA Framework Personalization

Profile Code :FND_CUSTOM_OA_DEFINTION ("Personalize Self service Defn")

Recommended Settings :No

If this profile option is set to Yes, the user can perform "Admin Personalization" for OA Framework-based pages.

2) for the feature Form Personalization/Examine

Profile Code :Combination of profiles:FND_HIDE_DIAGNOSTICS and DIAGNOSTICS

Recommended Settings :

  • FND_HIDE_DIAGNOSTICS: Yes
  • DIAGNOSTICS : No

These profiles control the Help->Diagnostics->Examine choice on the pulldown menu of Oracle Forms-based forms. The default value of FND_HIDE_DIAGNOSTICS (Hide Diagnostics menu entry) profile option is Yes, meaning the Diagnostics menu entry is hidden. If it is set to No, the Diagnostics menu entry is visible to the user.

If DIAGNOSTICS (Utilities:Diagnostics) is set to Yes, then users can automatically use these features. If Utilities:Diagnostics is set to No, then users must enter the password for the APPS schema to use the Diagnostics features.

dgreybarrow Wrap-up

You can refer to metalink note #1334930.1 and use the same SQL queries(sensitive_page_access.sql ) to determine who has access to these

  • SQL scripts drive off of page and form names (not functions)
  • Slower, but ensures we pick up custom functions that include these

You should reduce and eliminate access to these pages by admins.

You need to use Fine Grained Auditing to audit the tables associated with these pages.

Posted in Security | No Comments »

R12 Features > Proxy User

Posted on September 23rd, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

There is "Proxy User" functionality you have in R12. Proxy User allows a user to specify a proxy who can act on their behalf.Such typical example are executive who can designate an assistant/admin staff as a proxy, allowing that assistant to Create, edit or approve transactions on behalf of that executive.This have Integration with Internal Controls Manager for preventive enforcement of Separation of Duties (SoD) constraints

Once you have enabled:

  • No need to share your password!
  • Grant limited auditable access
  • Gives all or nothing delegation ability
  • In Proxy Mode, Page Access Tracking (PAT ) is automatically turned on, to audit the pages visited by the user
  • Can be used to solve the concurrent request scheduling problem

Posted in Security | No Comments »

Secuity : Oracle Application Module Security with R12

Posted on August 28th, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

This post is more on revisiting EBS Application Module Security.

1. HRMS Security

In HRMS there are two major Securities concept

  • Standard
  • Security Groups Enabled

Standard HRMS Security is a simple security used within a single legislation and a single business group. In this model, typically a Security Profile is created for each distinct group of employees and it is assigned to a responsibility.Its very simple.

For enabling Standard HRMS Security, Security Profile screen (US Super HRMS Manager -> Security -> Profile) can be used to create a Security Profile.

In Security Groups Enabled Security a single responsibility can be assigned to more than one business group and so users can access records from multiple business groups. In this model, multiple security profiles can be assigned to a single responsibility.

Typical example you can understand in this way : an HR Manager and Assistant HR Manager can use the same responsibility, but will be able to view different data.

For Security Groups Enabled Security, use Global Security Profiles window.

2. Multi Organization Access Control (MOAC)

This means Role based access to Operating Units.

Single installation of EBS can support different types of organizations and this feature is ability to access multiple organizations from a single responsibility, which is avaiable in majority of Oracle application modules.

Typical example of MOAC may be similar to senario listed here:

  • Limit users to their relevant organizations through security profiles.
  • Assign inventory organizations to inventory users.
  • Enter Purchase Orders in one organization and receive goods into any other organization.
  • Internal Requisitions from one organization and ship from another organization, with Intercompany invoicing.

Now, I’m going to explain how to define a security profile. Using Oracle HRMS, you can define your security profile using two forms: The Security Profile form or the Global Security Profile form that is shown here. Both forms look almost identical.

The Security Profile Form allows you to select operating units from only one Business Group. The Global Security profile Form allows you to select operating units from multiple Business Groups.

The decision on which form to use is really up to you and depends on your HR implementation and how you want to partition data. All you need to do is enter a name, and select the Security Type called “Secure organizations by organization hierarchy and/or organization list”. This allows you to assign multiple OUs. When assigning operating units, first select classification Operating Unit, and then select the organization or Operating Unit name. You can assign as many operating units as you want.

MOAC

moac2

3 Bank Account Security

Bank Account Maintenance security secures the creation and update of bank accounts, whereas Bank Account Access security secures the use of bank accounts.

Bank Account Maintenance Security, which secures the creation and update of bank accounts, grants user the access to one or more legal entities. Users can create and update the bank accounts whose owner legal entity is registered in the Bank Account Maintenance Security.

Users can create Bank accounts for which the list of legal entities in Bank Account Owner LOV will be restricted by this security. Users can query and update only those bank accounts whose owner is registered in this security.

The security setup is done in a wizard called “Bank Account Security Management”.

Define bank account use and link organization for every account.
Navigation: Cash management Superuser (R) -> Setup -> Banks -> Bank Accounts -> Click Account Access (T).

Bank security1

Assign organization (Operating Units, Ledger Entities and Business Groups) and bank account use to a Role.

Navigation: User Management ( R) -> Roles & Role Inheritance -> Security Wizards -> CE UMX Security wizard.

Bank Security

Bank Account Access security rule is composed of 2 parts :

  1. Bank Account Access Setup => Bank Account Access setup defines organizations that can use existing bank account
  2. Cash Management Security Profiles => Cash Management Security Profiles provide a list of organizations where an user has access to.

4. Purchasing Security

Purchasing documents can have 4 levels of security:

  • Public: Any user may access these documents.
  • Private: Only the document owner and subsequent approvers can access the document.
  • Purchasing: Document owner, subsequent approvers and users listed as buyers can access.
  • Hierarchy: Document owner, team members, approvers and others in the security hierarchy higher than document owner.

Purchasing

 

5.iSupplier Security

If you have created custom responsibilities that will be assigned to supplier users,securing attributes must be included in your custom responsibility definition.

There are three securing attributes that can be used to control access. These attributes are all seeded with the pre-defined Oracle iSupplier Portal responsibilities that are released with the product:

  • ICX_SUPPLIER_ORG_ID - Identifier for the supplier.
  • ICX_SUPPLIER_SITE_ID - Identifier for the supplier site.
  • ICX_SUPPLIER_CONTACT_ID - Identifier for the supplier contact

You can enable them from Navigation: System Administrator ( R) -> Security -> Responsibility -> Define.

isuuplier

6.Flexfield Security Rules

Flexfield Value Security gives you the capability to restrict the set of values a user can use during data entry. With easy-to-define security rules and responsibility level control, you can quickly set up data entry security on your flexfield segments and report parameters.

Flexfield Value Security lets you determine who can use flexfield segment values and report parameter values. Based on your responsibility and access rules that you define, Flexfield Value Security limits what values you can enter in flexfield pop-up windows and report parameters.

Security rules for the Accounting Flexfield also restrict query access to segment values in the Account Inquiry, Funds Available, and Summary Account Inquiry windows. In these windows, you cannot query up any combination that contains a secure value. However in all other forms, you will be able to query up a value even if it is restricted to the user.

In order to use, you just need to define Security Rules window to define value security rules for ranges of flexfield and report parameter values.

Navigation: Application -> Validation -> Security -> Define.

Use Assign Security Rules window to assign the flexfield security rules to an application responsibility.

Navigation: Application -> Validation -> Security -> Assign.

7.Fixed Assets Security

You can manage your Asset Book Security, as mention in one of previous post.This Functionality you can understood as:

  • Secure access to each depreciation book / Ledger
  • Create a flexible hierarchy of asset organizations
  • Associate a responsibility with one or more depreciation books

Asset Book Security allows multiple asset books/registers to be manage/administered independently

Fixed Assets responsibility can be secured by linking a Fixed Asset Book / Ledger, by executing the following steps:

  • Link an Asset organization to the Fixed Asset Set of Book/Ledger.
  • Establish an Organization hierarchy for the asset organization.
  • Navigation: Fixed Assets Manager ( R) -> Setup -> Security -> Organization -> Description -> Query Asset Organization -> Select ‘Asset
  • Organization’ -> Click ‘Others’ -> Assign FA Book.

8. Oracle Projects Security

Oracle Projects provides several integrated security mechanisms to help you define user access to organization, project, and resource information, as well as a variety of Oracle Projects functions. These mechanisms are all based on function security, which is the foundation of Oracle Applications security.

Using these integrated security mechanisms, you can define Oracle Projects security at the following levels:

  • Responsibility level, across projects.
  • Project level, using project roles.
  • Organization level, using predefined organization authority roles.

9. Inventory Organization Access

Inventory organizations can be assigned to responsibilities with inventory screens, thereby restricting the access to only those inventory organizations.

Navigation: Inventory ( R) -> Setup -> Organizations -> Organization Access.

Inventory

It is a very straight forward Form that you can assign which Inventory Organization(s) available to a responsibility. The Rule behind this Form is that once a responsibility is used, the default is that this responsibility does not allow to access all Inv. Org., unless you explicitly assign it. The good side is that this setting is effective immediately; no need to submit what-is-the-name-again process, setup all-look-like-the-same profile options

10. Manufacturing Organization Access

Manufacturing organizations can be assigned to responsibilities with manufacturing screens, thereby restricting the access to only those organizations.

your Navigation is: Advanced Planning Administrator ( R) -> Admin -> Organization Security.

11. Shipping Grants & Warehouse Access

Shipping roles can enable or disable access to individual functions within Shipping.

Navigation: Order Management ( R) -> Setup -> Shipping -> Grants and Role Definitions -> Define Roles.

shipping execution

Then you can assocaite shipping roles then can be assigned to individual users.

Navigation: Order Management ( R) -> Setup -> Shipping -> Grants and Role Definitions -> Grants.

12. Order Holds

In Order Management, when further processing has to be prevented on an order, a hold can be placed and released later.
Navigation: Order Management ( R) -> Setup -> Orders -> Holds.
Order Book

13. Advance pricing

Pricing security enables you to restrict pricing activities such as updating and viewing pricing entities to users who are granted specific access privileges. Pricing entities include price lists, pricing agreements, and modifiers.

Pricing security can be set up and maintained in the HTML user interface by a user who is assigned the Oracle Pricing Administrator responsibility. The Oracle Pricing Administrator has the authorization to access and update all pricing entities for all functional users.

With pricing security, you can implement a higher level of control by:

  • Assigning pricing entities to operating units: A pricing entity can be assigned ownership to a specific operating unit. You can restrict usage to one operating unit or by all operating units.
  • Assigning privileges that control which grantee (Global, Operating Unit, Responsibility, or User level) can view or maintain the specified entity: You can use security privileges to control user's access to pricing entities in the following ways:
    • Grant view-only or maintain access privileges to functional users at the Global, Operating Unit, Responsibility, or User level.
      Assign or reassign Operating Unit ownership to price lists and modifiers and control which operating units can use them for pricing transactions.
    • Create entity sets (a set consists of grouped pricing entities) and assign access privileges to the entire set. The Entity Set function is available only with license to Advanced Pricing.
  • Setting default rules for security access for new pricing entities.

Take a Note , before turning on pricing security, you must create privileges for existing pricing entities.

Navigate (N) Oracle Pricing Administrator Setup --> Security --> Privileges

advance

Hope this post will surly help you in address some of security and audit need for Clients/Customer.

dgreybarrow Suggested Reading

Posted in Security | No Comments »

What are the Security Attributes?

Posted on August 27th, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Securing attributes are used by some Oracle HTML-based applications to allow rows (records) of data to be visible to specified users or responsibilities based on the specific data (attribute values) contained in the row.

You may assign one or more values for any of the securing attributes assigned to the user.

If a securing attribute is assigned to both a responsibility and to a user, but the user does not have a value for that securing attribute, no information is returned for that attribute.

Isupplier, iexpense have using these feature, but still you can take advantage by creating your own depending upon the need.

dgreybarrow Defining new/Custom

Here are the steps to define Security Attributes

  1. Navigate to the Summary Security/Text.
  2. Select the security type from the drop down list. The valid values are:
    • Group: This specifies contract group security
    • User: This specifies user security
  3. Select the Group or User Name from the list of values, depending on the security type.
  4. Select the security level appropriate to the security type. The valid values are:
    • Modify: This allows update access to given contract.
    • Read Only: This allows on display or read access to the given contract.
  5. Save your changes

Posted in Security | No Comments »

Oracle Advanced Security – TDE (Transparent Data Encryption )

Posted on August 26th, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

This is one of the advance feature of security, where Encryption is done automatically when written to the database file and transparently decrypts the data when accessed inside the database.

Files are secure from unauthorized access at the OS level, discarded disk drives and off-site backup media.[Adopted from Oracle Documentation]

Network encryption transparently encrypts all SQL*Net traffic between the Oracle EBS and the database.

Oracle Advanced Security supports both industry standard Secure Sockets Layer (SSL) encryption and an Oracle native encryption capability for customers that do not want to deploy X509 Public Key Infrastructure (PKI) certificates.

Traditional access controls including those enforced by Database Vault, Label Security and Virtual Private Database (VPD) also apply and so data will not be decrypted until the users are authenticated to the Oracle database.

TDE column encryption can be used to protect individual columns in application tables containing credit card numbers or other personally identifiable information (PII).
TSE

dgreybarrow Scenarios

You are told to explore the options for implementing Oracle Advanac Security Option(ASO) in Oracle financial application. Probally you might have these questions in mind?

  • What tool or function , should needed and how this handle with advance options?
  • Does this tool encrypt the table column in the database at all time and only decrypt the table column?
  • Is that needed through Oracle Financial or any OracleApps UI or is sitting standalone inside/outside application?
  • Is there any different treatment for some sensetive data like Credit card, Bank Account and or SSN values ?

In above senarios , you might have a similar requirement to encrypt the SSN value in an Oracle table at all time and only make it viewable(decrypted) when a authorized user via Oracle financial application tries added or update a record to database.

If you already aware about TDE , then you should not have much issue in doing fitment . Fundamentally the TDE have functionality is the same irrespective of the application. It's encrypts the column data at rest meaning in the storage it is kept encrypted, to protect the data in the event of stolen storage or when someone has direct access to the storage disks. Database automatically decrypts the data for whoever got privilege to access to this data, say SELECT privilege.

The best place is to start with Oracle documentation and get the details/

If you are doing with existing data value of Oracle Financial ref to these note in metalink that will be helpful.

  • Doc ID 862708.1 : R12 - Customer's Taxpayer ID and SSN On Customers Form Need To Be Encrypted
  • Doc ID 403537.1 : Best Practices For Securing Oracle E-Business Suite Release 12
  • Doc ID 828229.1 : Using TDE Tablespace Encryption with Oracle E-Business Suite Release 12
  • Doc ID 863053.1 : How To Encrypt Credit Card Data In Release 12
  • Doc ID 732764.1 : Using TDE Column Encryption with Oracle E-Business Suite Release 12
  • Doc ID 1301337.1 : How To Enable Oracle Payments Data Encryption Functionality

If you are looking the for the possiblity to encrypt and decrypt data using triggers or some other database object without changing an application, then probally you can use the the dbms_obfuscation_ toolkit within a trigger.

Posted in Oracle Application, Security | No Comments »

Security : Oracle Database Vault

Posted on August 20th, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Oracle Database Vault restricts access to specific areas in an Oracle database from any user, including users who have administrative access. For example, you can restrict administrative access to employee salaries, customer medical records, or other sensitive information.

This enables you to apply fine-grained access control to your sensitive data in a variety of ways. It hardens your Oracle Database instance and enforces industry standard best practices in terms of separating duties from traditionally powerful users.

Oracle Database Vault this addresses common regulatory compliance requirements and reduces the risk of insider threats like.

  • Preventing highly privileged users (DBA) from accessing application data.
  • Enforcing separation of duty (DBA can’t create users, view data).
  • Providing controls over who, when, where and how applications, data and databases can be accessed.
  • Can be added to existing application environments without changes to the existing application code.

For Consulting people, lets try to understand three most important concept required from security .

1) Realms - These are boundaries within the Oracle database that act like a firewall to prevent privileged users from using their special privileges to access application data.

The realms can be used to protect an entire application or a specific set of tables within an application, providing highly flexible and adaptable security enforcement.

Look at the following diagram the DBA has been denied access to view the application data, in spite of the special privileges.

Oracle Databse Vault

2) Command Rules - Security rules that can be created for creating, dropping and altering tables inside the database and decide whether to block a command.

Factors - It can also reference out-of-the-box factors such as IP address, authentication method and program name.

In the diagram below, Database Vault has denied access as the applications are accessed either through wrong IP address or tool.

Oracle Audit Vault-2

3) Separation of duty - Oracle Database Vault systematically separates DBA duties to strengthen security controls and helps satisfy requirements found in many regulations.

Out-of-the-box, Database Vault creates following 3 distinct responsibilities within the database

  • Account Management :A user with account management responsibility can create, drop, or modify database users
  • Security Administration :A security administrator can manage realms, command rules, factors etc., but prevented from self-authorizing access to secured business data
  • Database Administration :Database administration responsibility enables a user to continue performing normal management and maintenance, such as backup and recovery without having access to secured business data

Therefore, Oracle Database Vault is an integral component of your enterprise.Typically companies configure Oracle Database Vault to manage the security of an individual Oracle Database instance.

Posted in Security | No Comments »

Security Profile Options in Managing a Secure Oracle Applications Environment

Posted on July 31st, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

These Profile are recomended by Oracle strongly in secureing configuration of Oracle E-Business Suite production systems.

  • FND Validation Level : Provides in depth defense against parameter and URL tampering.

Recommended Setting: ERROR

  • ICX: Session Timeout :Idle Session Timeout. The numeric value greater than 4 (in minutes) that a SSWA session can be idle before expiring. A 0/NULL will disable timeout.

This profile option determines the length of time (in minutes) of inactivity in a user's form session before the session is disabled. Once session is disabled , the user is provided the opportunity to re-authenticate and re-enable their timed-out session. If the reauthentication is successful, the disabled session is re-enabled and no work is lost. Otherwise, the session is terminated without saving pending work.

Recommended Setting: 30 min

  • ICX: Limit Time :Absolute maximum length of time (in hours) of any user session, active or inactive.

This profile defines the maximum connection time for a connection – regardless of user activity.
If 'ICX:Session Timeout' is set to NULL, then the session will last only as long as 'ICX: Limit Time', regardless of user activity.

  • Signon Password Failure Limit :A positive integer to limit maximum number of logon attempts before the user's account is disabled.
  • Restrict text Input :Detects Cross Site Scripting(XSS) and other HTML injection attacks by hackers which gives access to your website and database.

Recommended Setting: Yes

  • Utilities:Diagnostics :Value determines whether diagnostic utilities, such as Help -> Tools -> Examine, may be used.

Set to No, to disable a user to view any internal form field.

Posted in Oracle Application, Security | No Comments »

Page 1 of 212

« Previous Entries