In the Add IPs screen, select the Search and select from the existing IPs

10-56 Oracle Fusion Middleware Administrators Guide for Oracle Adaptive Access Manager

13. Click Cancel.

You are not sure which rule condition would apply for your business use case.

14. Click the Delete button in the upper-right corner.

An Unsaved Data Warning dialog appears with the message, You have unsaved data. Are you sure you want to continue?

15. Click Yes.

You are returned to the Rules page. 16. Click the Delete button in the upper-right corner again. You are returned to the Policies Search page.

17. In the Search Results table, click the policy you created.

The rule has not been created.

10.34.15 Use Case: Disable Trigger Combinations

Jim is a Security Administrator. He wants to inactivate his trigger combinations and enable them later, but he does not want to lose his settings. He can accomplish that by not setting the ScorePolicy, Actions, and Alerts for the combinations and they are automatically in disabled state. No action would be taken based on these combinations. To disable trigger combinations:

1. In the Navigation tree, select Policies. The Policies Search page is displayed.

2. Search for the policy which you want.

3. Click the policy name to open its Policy Details page.

4. Navigate to the Trigger Combinations tab.

5. Select 0 as the score or make sure no nested policy is specified.

6. Deselect the actions in the action group lists. 7. Deselect the alert sin the alert group lists.

8. In the Trigger Combinations tab, click Apply after making all your edits.

10.34.16 Use Case: Condition: Evaluate Policy

Jeff has two policies. One of the policies Policy B is like a pre-cursor to Policy A so this policy should be executed every time, no matter what the other rule evaluations turn out to be. Hence nesting this policy under Policy A may not work all the time. trigger combinations So Jeff decides to add a new rule condition to Policy A such that it executes Policy B every time.

1. Open Policy A.

2. In the Rules tab of the Policy Details page, click the Add Rule button.

3. Create a rule, Rule C.

4. In the Condition tab of the Rule Details page, click Add Condition.

5. Add System: Evaluation Policy condition.

Managing Policies, Rules, and Conditions 10-57

6. In Trigger Combination, select Policy B as action.

10.35 Best Practices

This section outlines some best practices for using policies, rules, and conditions.

10.35.1 Adding or Editing PoliciesRules

These general steps outline the process for adding or updating of policies or rules into a production environment:

1. Develop the new rule using your offline system a separate installation of Oracle

Adaptive Access Manager set up for testing or staging.

2. Test the rule to ensure that it is functioning as expected by running predictable

data through it using your offline system.

3. When you are satisfied that the policy is functioning as expected, migrate the

policy in pre-production where performance testing can be run. This is an important step since the new rule, or policy, or both can potentially have a performance impact. For example, if you define a new policy to check that a user was not using an email address that had been used before ever. If the customer has more than 1 billion records in the database, performing that check against all the records for every transaction has great impact on performance. Therefore, testing the policy under load is important.

4. Only when you are satisfied that your new rulepolicy is functioning as expected

and does not adversely affect performance should it be migrated into production.