Where DevOps collides with identity security

Where DevOps collides with identity security



DevOps is fast becoming a central part of enterprise IT. For entirely understandable reasons, too. As organisations mature and grow, unintended IT silos often prevent the innovation of new products and services from taking flight. DevOps represents the unification of Development and Operations teams and, within that, huge gains for productivity, efficiency and innovation in the world of software development.


DevOps automates much of the labour and time intensive processes that historically burdened software development teams by streamlining the cooperation between app development and their IT counterparts.


Innovations like this are rightly welcomed within enterprise IT. However, sometimes they’re ushered in too quickly – without forethought or consideration. And without proper consideration, titanic changes will always find an iceberg.


IoT is a perfect example of innovation moving too fast. Many IoT products and services suffered from well documented and widespread security risks because they were not done holistically with the prerequisites from IT. But it’s not just a security problem – these kinds of hasty adoptions risk undoing the very benefits you want to gain from the innovation itself.


DevOps comes with its own sets of considerations, especially when it comes to identity security. In fact, DevOps has accelerated so quickly that Identity security teams often struggle with the growth of apps and data that DevOps permits.


Identity initiatives are often stretched to their limits, trying to accommodate the speed of that growth. Normally, a new app or service would be brought into an enterprise existing identity ecosystem through centralised authentication services. However, the sheer speed which DevOps permits often finds Identity teams weighed down with more requests than they can handle.


At the same ..

Support the originator by clicking the read the rest link below.