Benefits of Integrating GRC into Your Identity Management Program
How to Incorporate GRC into your Identity Management Program
In most organizations the Governance, Risk, and Compliance (GRC) team operates entirely separate from the Identity and Access Management (IAM) team, and for good reason. An effective GRC team is responsible for identifying risks and making sure the right business processes and controls are in place to mitigate risk and meet compliance requirements. The IAM team ensures the right people have the appropriate access to technology resources. Maintaining their independence prevents any conflict of interest and any perceived conflict.
However, there are a few use cases where it makes sense for the IAM and GRC teams to work closely together to ensure organizations efficiently manage access control risks.
Improve Business Process Efficiency
Many IAM business processes can be more efficient by leveraging insight from the GRC team and/or utilizing the following GRC tools and methods:
- Integrate a Segregation of Duties (SoD) check into the user provisioning process
- Leverage an IGA solution to identify sensitive or mission critical access within an organization
- Conduct regular reviews of SOD rulesets to ensure they still apply and include any new risks to the business
- Incorporate risk signatures into the user access review process(s)
- Send control evidence automatically from the IGA system to provide documentation to auditors within your enterprise GRC platform(s)
- Implement solutions to identify sensitive data within your environment that may impact regulatory compliance
- Leverage key data points from your Identity Management systems to further improve the Enterprise Risk Management processes
- Incorporate key risk insights from the GRC team to prioritize applications for inclusion into an IGA program
- If a request contains a critical SoD violation it can be automatically rejected
- If a request contains a high-risk SoD violation, it can be routed for additional approvals. A common workflow example is manager approval followed by Data Owner (or Role Owner) for additional approval. If the request contains an SoD risk, it can be routed to the compliance team for an additional check and to apply any mitigating controls.
- If the request does not contain any risk violations, Saviynt can simply route the request to the Manager. Once approved, we automatically provision the access.
- Identifying exceptions for Orphaned Accounts and critical pieces of information i.e.; who approved them and the business reason for their continued existence
- Evidence of Quarterly User Access Reviews for Sarbanes Oxley or other compliance requirements
- SoD’s and Sensitive Access violation reviews and mitigating control assignments
- Privileged Account Reviews
- Service Account Reviews