OIA will take into consideration the aggregated risk-based factors and determine the risk summary based on the highest value based on these factor. The result will provide the risk level.
The risk factors are based on 3 areas
1. The specific items, which reviews the metadata of the application or the true value of the application access
2. The provisioning Scenario, which reviews how the access was provisioned
3. The internal OIA Scenario, which review any Identity Auditing Violations or previous certification actions
So within OIA I have configured
Based risk level - Based on the metadata of the application or the risk assigned to the application value
Provisioning Scenarios -
Internal OIA Actions - Last Certified Action or via Audit Violations
Risk Levels with OIA are calculated bases on either.
1. The pre-defined risk levels you associate to the metadata of the Application or Role once created...
2. The data values of the data feeds OIA receives (such as the HR data or the Account information)
If you don't assign the pre-defined risk levels, you can allow to predefine the risk level once you onboard new Applications and Roles
Best Practice for risk levels
Some quick notes regarding risk levels
- Allow OIA to assign risk levels unless the application is considered a known application
- You typically use high-level risks for pre-defined object for highly-restrictive privileges.
- OIA will calculate the risk-summary level based on the highest value from the available attributes associated to the user
HOW to configure risk Summary Maintenance job
scheduling.context.xml -- line 190 & 230
jobs.xml -- Risk line 1116
0 0/1 * * * ? -- Every 1 minute
About the author
Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
Comments
Other Posts
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...
Tags
Recent Posts
Monthly Activity
Group by date