Skip to main content

Successful Certification

Certification in identity management is generally used to confirm or revoke existing user accounts and HR information.  The focus being on existing accounts is used to distinguish between general access request approval workflows and post approval workflows.  During the access request phase a manager or IT owner will approve or reject whether someone should have additional access to a system.  This is not a new concept and was managed perfectly well, long before this process was automated using provisioning solutions.



Certification or attestation is more concerned with analysing users who have already been granted access to a current system.  This periodic post approval process is more to do with seeing if previous access request actions are still needed.  This also leads to other analytical steps such as identifying users who may have moved jobs, or left the organisation.  Another useful bi-product of analysing existing users is to locate what's known as 'orphan accounts'.  These 'orphans' are simply application accounts that can no longer be linked back to an actual HR record.  This is likely if the employee has been terminated but their access still exists.  Not only are these orphan accounts an un-managed security risk, they could also be wasting costly licenses if not being used.


A general approach to certification is to perform an initial identification of which business areas and applications need certifying.  Not all parts of the business may require the same level of analysis and only critical applications that face regulatory compliance may need attention.  Once the scope of analysis has been completed data from the users and systems involved needs collating, centralising and correlating.  Here we can identify orphan accounts, missing HR information and other data anomalies.

The actual certification process is generally performed by non-IT managers from the business.  As a result a clear training, messaging and internal marketing campaign is needed to make sure the correct stakeholders are involved and understand their role.  Escalation processes also need creating in order to develop process flows to make sure the certification cycle is complete accurately and on time.

The resulting rejection or certification of accounts also needs centralising and processing using a reporting and dashboard technique.  Good visibility of metrics such as number of certified users, time to complete, number of rejections, exceptions and so on needs to be available.

Once revoked user accounts have been identified a clear and understandable de-provisioning process needs to be created, managed and maintained.  This will require IT understanding of the systems in scope in order to develop a process to remove revoked users and entitlements.  This needs documenting, publishing and adhering with strong and realistic time scales for the actions to be performed.  Once performed, positive feedback is then needed in order to confirm the user accounts and their entitlements have been removed.

All in all, the process requires good messaging, inscope work packages, correct stakeholder buy in and regular performance management to enable the certifications to effective and create a tangible ROI.




Popular posts from this blog

Top 5 Security Predictions for 2016

It's that time of year again, when the retrospective and predictive blogs come out of the closet, just before the Christmas festivities begin.  This time last year, the 2015 predictions were an interesting selection of both consumer and enterprise challenges, with a focus on:


Customer Identity ManagementThe start of IoT security awarenessReduced Passwords on MobileConsumer PrivacyCloud Single Sign On
In retrospect, a pretty accurate and ongoing list.  Consumer related identity (cIAM) is hot on most organisation's lips, and whilst the password hasn't died (and probably never will) there are more people using things like swipe login and finger print authentication than ever before.

But what will 2016 bring?


Mobile Payments to be Default for Consumers

2015 has seen the rise in things like Apple Pay and Samsung Pay hitting the consumer high street with venom.  Many retail outlets now provide the ability to "tap and pay" using a mobile device, with many banks also offer…

Customer Data: Convenience versus Security

Organisations in both the public and private sector are initiating programmes of work to convert previously physical or offline services, into more digital, on line and automated offerings.  This could include things like automated car tax purchase, through to insurance policy management and electricity meter reading submission and reporting.

Digitization versus Security

This move towards a more on line user experience, brings together several differing forces.  Firstly the driver for end user convenience and service improvement, against the requirements of data security and privacy.  Which should win?  There clearly needs to be a balance of security against service improvement.  Excessive and prohibitive security controls would result in a complex and often poor user experience, ultimately resulting in fewer users.  On the other hand, poorly defined security architectures, lead to data loss, with the impact for personal exposure and brand damage.

The Role of Identity Management in the GDPR

Unless you have been living in a darkened room for a long time, you will know the countdown for the EU's General Data Protection Regulation is dramatically coming to a head.  May 2018 is when the regulation really takes hold, and organisations are fast in the act on putting plans, processes and personnel in place, in order to comply.

Whilst many organisations are looking at employing a Data Privacy Officer (DPO), reading through all the legalese and developing data analytics and tagging processes, many need to embrace and understand the requirements with how their consumer identity and access management platform can and should be used in this new regulatory setting.

My intention in this blog, isn't to list every single article and what they mean - there are plenty of other sites that can help with that.  I want to really highlight, some of the more identity related components of the GDPR and what needs to be done.

Personal Data On the the personal data front, more and more org…