Managing global rule configurations is a key part of RiskMinder management and optimization, and a key responsibility of GAs.
Note: The changes you make to the configuration globally or at the organization level are not applied automatically. You need to refresh all server instances to apply these configuration changes.
You can manage RiskMinder rule configurations at two levels:
Note: Although these rules are available to all organizations, they cannot be used as-is at the organization level. For example, even if you configure a Untrusted IP Check rule at the global level, individual organizations need to configure this rule either by copying from the global rule.
These configurations apply only to the specific organization where they were set.
Note: Although you can change the default rule configurations individually for every organization in the system, most of the organizations might be using the same configuration settings repeatedly. Also, setting rule configurations for individual organizations can be a cumbersome task if a large number of organizations are configured. In this case, you might want to set the global configurations for the rules so that Organization Administrators (OAs) do not need to specify the same setting every time.
This section discusses the configurations that GAs can set as a "template" for all current and future organizations in the system. These configurations include:
Note: These configurations are applicable for all organizations that are in the purview of the GA setting them. If you want to configure individual organizations, then you must log in as the Global Administrator (GA) or as the Organization Administrator (OA) of the target organization to do so.
See "Managing Organization-Specific RiskMinder Configurations" for more information.
In addition to these tasks, GAs can also:
|
Copyright © 2013 CA.
All rights reserved.
|
|