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

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 : Oracle Audit Vault

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

In security series, lets know another product.

Oracle Audit Vault is a security product that automates the consolidation of audit data into a secure repository, enabling efficient monitoring and reporting. This makes Oracle Audit Vault is a powerful solution providing a secure repository, built-in reporting, event alerting.This uses Oracle data security to protect audit data end-to-end. It helps to:

  • Consolidate and secure audit data from multiple instances of these databases – Oracle, Microsoft SQL Server, Sybase, IBM DB2.
  • Oracle Audit Vault is having out-of-the box compliance reports such as SOX, PCI and HIPAA requirements.
  • This also have entitlement reports for Oracle database to showing users, privileges and roles.
  • Policies can be created for SQL statements, schema objects, database privileges like alter, create, drop, grant etc.
  • Oracle Audit Vault raise alerts for suspicious activity on sensitive data like employee salaries, credit card numbers etc.
  • This have feature to capture before/after data value changes from Oracle database transaction logs.
  • Audit Vault can be administered and managed separately through Audit Vault server and Console

Oracle Audit Vault

Read the rest of this entry »

Posted in Oracle Application | 2 Comments »

Secuity : Oracle Internal Controls Manager

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

Do you know , Oracle Internal Controls Manager (OICM) is a comprehensive tool for executives, controllers, internal audit departments, and public accounting firms to document and test internal controls and monitor ongoing compliance. This tool is based on COSO (Committee of Sponsoring Organizations) standards.

Read the rest of this entry »

Posted in Oracle Application | No Comments »

Security : User Management Roles (UMX)

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

Oracle User Management (UMX) enables organizations to define administrative functions and manage users based on specific requirements such as job role or geographic location.

A Role in UMX schema can be best understood as a job function within the context of an organization with associated semantics regarding the authority and responsibility conferred on the user assigned to the role .

Typical characteristics of Role are - Navigation menus and Access permissions can be separate, and Roles are hierarchical. Because of which responsibilities can be shared with multiple roles and Roles can be built on top of each other, with minimal effort.

Oracle Role Based Access Control (RBAC) and Data Security enables permission assignments to secure a subset of data on the database objects such as vendors, projects, customers, application users etc which can be easily done by creating data security policies .

Typically if you combine all key component, the best it can be described as fig below:

EBS Security UMX

Delegated and Local administrators can be given administrative privileges with a subset of users and people to manage. They can be given different set of administrator privileges. The delegated administrator privileges can be implemented by selecting the Role to which it can be assigned.

You can Navigate the security Wizard as :

Run Wizard (I) of “User Management: Security Administration Setup” -> User Administration (T) -> Add More Rows (B).

The User Management: Security Administration Setup wizard is a security function that defines the administration privileges for administrators that assign/revoke user accounts and roles.

This wizard has 3 sub-tabs:

  • User Administration,
  • Organization Administration
  • and Role Administration

UMX also comes with pre-defined Self-service Registration tasks for users to request new accounts and additional access to the system.

Last but the least, there is Proxy user functionality available in R12 that provides a user with the ability to delegate his/her functions to individuals, to act on behalf of the delegator. How this sounds :)

Posted in Oracle Application | No Comments »

Security :Oracle User Management

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

Oracle User Management (OUM) is an extension to the core Oracle E-Business Suite Access Controls Model. It introduces a number of features to streamline and improve the security of user administration.

dgreybarrow What is Oracle User Management?

This is available from EBS 11.5.10 onward as part of the license,Oracle User Management is an extension to the core Oracle E-Business Suite Security Access Controls model which enables organizations to manage users based on specific requirements such as job role or geographic location.

Companies having large number of User base utilizing Oracle’s self service based application such as iProcurement,iExpenses and self-service HR managing user account is always a resource intensive activity, which can be enhanced by usage of this.Let understand the core component of OUM.

dgreybarrow Security & Key components

The key features of Oracle User Management can be divided into two main areas: Core Security and Administrative features.

Oracle User Management leverages the existing Application Security features, Function and Data Security, while providing the additional layer of role based access control. These Core Security layers provide the basis for Oracle User Management's administrative features: Delegated Administration, Registration Processes, and Self Service Requests & Approvals.Details are herewith:

  1. Core Security - Oracle's function and data security mechanisms constitute the base layers of this system, and contain the traditional system administrative capabilities. Organizations can optionally add more layers to the system depending on the degree of flexibility they require.

    (1 ) Function Security - The base layer of access control within Oracle Applications is Function Security. Function Security restricts user access to the individual menus and menu options within the system.

    (2) Data Security - The second layer represents Data Security. Working in conjunction with Function Security, Data Security provides additional access control on the data a user can see and what actions a user can perform on that data, within Oracle Applications. Using Data Security, for example, you could control access to the set of orders that an order administrator can update within the Order Management application.

    (3) Role Based Access Control (RBAC) - The third layer represents Role Based Access Control (RBAC). The RBAC model augments the existing access control model in Oracle Applications by providing additional methods to organize data security policies and existing function security (via roles).

  2. Administrative Featured

(4) Delegated Administration – This enables access controls administrative duties to be delegated to ‘local’ employees. This allows administrators with knowledge of local access requirements to perform simple user administration.

(5) Registration Processes – allows an organization to configure the self-service user account provisioning and access assignment processes to support their specific business requirements.

(6) Self-Service Requests and Approvals – users can select automated workflow processes to request the creation of a new user account, request additional access or reset their password.

These 6 key feature can be best described as Fig below.

Oracle User Management

Thats means user Management could reduce the cost of supporting your Oracle E-Business Suite Environment. Processes such as self-service password reset and self service account creation could enhance the operational efficiency and addresses your security and controls risks.

dgreybarrow Other similar Post

Posted in Oracle Application | 1 Comment »

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 »

ADVANCED AUDIT

Posted on July 18th, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Oracle E-Business Suite implements its own auditing mechanisms, Audit Trails.

Auditing database row changes is performance intensive. Limit auditing to non-transactional data. Auditing transactional data may cause significant performance degradation. Tables with more than a few changes an hour should not be considered for row level auditing. Plan and consult with a DBA before enabling Audit Trails.

This feature keeps a complete history of changes made at a table and column level. When initialized, a concurrent program creates a shadow table and places triggers on the columns to be audited. The triggers store column changes in the shadow table (a table whose name is the instance table’s name appended with _A)

dgreybarrow CONFIGURING AUDIT TRAIL

To enable Audit Trail, follow these steps:

  1. Set System profile option AuditTrail: Activate to True
  2. Navigate through Security -> AuditTrail -> Install to set schemas for auditing
  3. Navigate through Security -> AuditTrail -> Groups to create audit groups and set tables to be audited. Set audit group to Enabled Requested
  4. Navigate through Security -> AuditTrail -> Tables to set columns in tables to be audited
  5. Run AuditTrail Update Tables to activate auditing

dgreybarrow PURGE AUDIT TRAIL RECORD

Purge the audit trail information on a regular basis. Prior to purging, disable the Audit Trail. Use the following procedure to purge audit data:

  1. As System Administrator, select Security -> Audit Trail -> Groups.
  2. Select the Security Audit group and set the group state to Disable – Purge Table.
  3. Run the Audit Trail Update Tables Report.
  4. Purge the data from the shadow table.
  5. Select Security -> Audit Trail -> Groups.
  6. Select the Security Audit group and set the group state to Enable.
  7. Run the Audit Trail Update Tables Report

Posted in Oracle Application | No Comments »

Page 3 of 71234567

« Previous Entries Next Entries »