IdAM is often treated as a project from the start, and often as a project that “just has to work”. This kind of thinking can lead to all kinds of problems when a solution is doomed to fail without the resources to support it.
When it comes to cybersecurity, it is important to view IdAM as a program to ensure that current security systems and processes are continuously and regularly updated with appropriate IdAM tools and practices to help protect the organization and the public sector. For this, organizations are already ill-prepared for a cyberattack, which is critical.
Today, there are still some divisions in the arena that are not participating “Whole of Government”, the IdAM system therefore cannot easily accept Whole of Government offers. In response to criticism of service initiatives such as domestic violence referrals, departments continue to plan and develop stand-alone solutions to meet the immediate need for access to sensitive data and ICT systems managed by other institutions. An important reason for the proliferation of multi-point solutions and high investment costs is the absence of a governing body, lack of mandatory policies, standards, systems and definitions, common and streamlined business processes/practices.
In parallel, new online systems were significantly developed and along with Cloud First policy, greater adoption of cloud-based Infrastructure as a Service (IaaS), software as a service (SaaS) and platform as a service (PaaS). Some of these distributions contain sensitive information and staff now have access to much of it programs and remember many logins and passwords. Single sign-on and multi-factor secure access is sorely lacking in many on-premise, legacy and cloud departments Public, SOD/IDAM/01 – Declaration of Personnel Identity and Access Management Address 8 based programs; contributes to poor user experience, reduced staff productivity and increased risk of harming the security of ICT systems and information.
There are new dangers in computing. As a result, the challenge of protecting passengers, flight crew and business partners is rapidly becoming more complex. An IBM study found that it takes up to 6 months to detect a data breach, giving hackers plenty of time to plan a breach.
How can you expect your IdAM solution to run smoothly if the fundamentals are flawed? Customization is a popular way to provide unique features, but too much can lead to maintenance issues and ultimately abandonment. Pareto’s law applies here with an 80/20 split. Only 20% of the functionality of an IdAM solution should be custom features and the rest should be standard product functionality. In addition, infrastructure can quickly become unsustainable, making the solution long-lived and difficult to keep up with the ever-changing landscape.
