What is recertification?
...
...
...
...
For its apps, databases, and other resource access, the organization has a periodic recertification procedure in place. As a result of recertification, a manager or responsible party, or system owner certifies users' access to a system to guarantee that they only have access to what they require.
Recertification is a part of an organization’s governance risk and compliance activity. Recertification or attestation are different terms for the same thing. GRC (governance, risk, and compliance) is a collection of rules and procedures that enable firms to achieve their business goals, deal with uncertainty, and behave with integrity. The goal of the recertification is to present the system data to the auditors and to ensure that there are no nonconformity findings during audits.
...
...
...
Why recertification is needed?
The implementation of a recertification procedure can safeguard a corporation from potential security breaches and fines. Recertification is already mandated by law in the IAM context.
...
...
...
...
...
Therefore, to minimize the risk, for all the risky accesses, we should be able to certify and recertify on a regular basis that the access is still needed. For example, is this user account still needed? if a user has already resigned from the company, the user account should not be active. These kinds of potential risks are checked and minimized with the help of recertification at regular intervals.
What is a recertification audit?
The review of user access rights to see if they are proper and correspond to the organization's internal rules and compliance standards is known as access recertification audit. The recertification is often implemented as an audit.
An audit can be considered as a project with a start date and end date. We might want to audit or certify multiple items using an audit. For example, in a Q1 audit we might want to certify, an external partner identity as well as attest a member of certain high-risk management roles. These items are specified in one or more recertification policies. EmpowerID maintains an audit trail of these access snapshots and the decisions made concerning the access. EmpowerID recertification audits can be scheduled to run periodically, such as on a quarterly or monthly basis, weekly, daily, or at will.
What is the recertification policy?
...
...
...
...
...
...
...
EmpowerID provides a collection of useful recertification policy types.
Recertification in EmpowerID
EmpowerID provides a powerful attestation and recertification platform that gives any organization the ability to take a more proactive approach to rectify potential security issues before they occur through crafting EmpowerID audits and recertification policies. The combination of recertification policies with EmpowerID's robust reporting capabilities allows organizations to create a more thorough and effective resource management strategy.
Auditors can also designate audit as either one-time or ongoing audit. A snapshot of user access and entitlements is obtained when the initial audit begins. This first snapshot creates an irreversible record of your company's security at the moment. Business requests are produced as a result of this, and EmpowerID's process-driven approach keeps both users and the work required moving forward in order to ensure timely completion and correct outcomes of the audit.
The primary building blocks of recertification is depicted in the below overview diagram.
...
For recertification to work in EmpowerID following steps are needed.
Pre-requisite jobs should be started and running - The recertification engine jobs must be running for the recertification to complete successfully.
Create recertification policy - The frequency with which users must validate their requirement for a resource or membership is defined by a recertification policy. The policy also specifies what happens if the receiver refuses or does not reply to the request for recertification. Recertification policies employ a set of alerts to kick off the recertification process's workflow operations.
Add target(s) to recertification policy - The targets of recertification policy defines the scope of the recertification. Recertification policies may target many resources and memberships. For example, whether this recertification audit covers employees of a perticular city or entire organization.
Create recertification audit - An audit is nothing but an end to end implementation of recertification.
Add recertification policy(s) to recertification audit - An audit needs a recertification policy and its targets so that compilation of audit can generate at least one business requests.
Enable and compile the audit - The recertification engine requires the created audit to be enabled so that it can be compiled.
Check business requests are generated - There must be at least one business request generated as a result of compilation of a recertification audit.
Check fulfillment is done - The completion of decision made related to access in EmpowerID systems based on an audit outcome is known as fulfilment.
Verify the result of recertification - Need to verify that the end result of the recertification is correct.
| Page Properties | ||
|---|---|---|
| ||
To maintain the integrity of recertification reviews, users cannot recertify themselves. In other words, a user who can create a recertification policy cannot certify that policy. The EmpowerID admin user is prohibited from participating in the review process by this feature. |
...
...
The auditors can identify and address any discrepancies or issues with user access rights and ensure that access rights comply with company policies, regulations, and industry standards. Each access generates a business request item which is presented as a task to auditors to help recertify discrepancies and provide access revocation. The data generated in an audit about access are snapshots, meaning the data represents the state it was captured, which will not change. EmpowerID maintains an audit trail of these access snapshots and the decisions made concerning the access.
The recertification policy defines the rules and procedures for reviewing access rights. In contrast, the recertification audit is the actual review of access rights against the company policies and regulations. Since the Recertification of the access is a continuous process, EmpowerID recertification audits can be scheduled to run periodically, such as on a quarterly or monthly basis, weekly, daily, or at will.
Recertification Architecture
This diagram describes the Recertification Architecture of EmpowerID. Detailed information about each process is described below the diagram.
The first step in Recertification in EmpowerID is to create recertification policies, which are reusable definitions or rules that allow you to configure who and what types of access should be audited. These policies can be configured based on organizational rules, including the type, scope, and people. They can be used in multiple audits, saving time and effort compared to defining them each time.
Create a Recertification Policy: Create a recertification policy that defines the type of policy and enables it for audit. You can also configure what should be done if any access recertification is unattended by the auditors.
Add Target to Recertification Policy: Adding a target to a recertification policy configures who or what will be recertified. Recertification policies can target multiple resources and objects, such as a specific location, group, or resource type.
Add Item Type Scope (Data) to Recertification Policy: The Item Type Scope in a Recertification Policy allows users to configure what data will be collected for Recertification. The item scope enables users to tailor the recertification process to meet their specific needs, such as specifying the collection of data only for a person's access to a group as a member.
Once the policy is defined, Audits will be created by the user. An audit is an end-to-end recertification implementation, meaning the data is collected and certified during an audit.
Create Recertification Audit: In EmpowerID, an audit is a logically named user-defined object for identifying or grouping business requests and running the Recertification policies that generate them. EmpowerID recertification audits can be scheduled to run periodically, such as on a quarterly or monthly basis, weekly, daily, or at will.
Add Recertification Policy to Recertification Audit: An audit can have multiple recertification policies enabling you to granularly configure to collect different types of access data in a single audit.
The EmpowerID recertification engine runs the audit on provided schedule, automatically collecting access data and saving it as snapshots, meaning the data represents the state it was captured, which will not change.
The collected data is used to create Business Requests and Their items. In EmpowerID, each access recertification is a Business Request Item or an automatically generated task request which is presented to auditors as a Business request. The background job Attestion Policy Compiler does the collection of data and generation of business requests. You can follow the instructions in Verify Business Requests are Generated to see if the audit generates the requests.
Auditors and responsible managers provide decisions to Certify, Revoke, and other actions in the business requests. Instruction to Provide Business Requests Decisions These business requests contains details about the access for the person that needs to be certified.
Once the auditors provide the decisions on the business request, the fulfillment workflow picks the decision and fulfills it. The background job Business Request Fulfillment does the fulfillment task based on business decisions.
| Div | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
IN THIS ARTICLE
|
| Macrosuite divider macro | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|