Allow Safe Velocity At Scale: DevOps Automation With Identification

Ivan Dwyer, group product advertising supervisor with Okta, begins this digital session by acknowledging the challenges of safety professionals as an growing variety of organizations undertake cloud and DevOps options. Quick-paced, steady innovation is the secret in right now’s aggressive enterprise panorama. Safety practitioners are tasked with a troublesome ask: maintain the group safe with out disrupting productiveness. On the identical time, don’t compromise on safety for the sake of productiveness.

The Rising Pains Of Shifting To The Cloud

Subsequent, Ivan addresses the migration of deployments from on-prem to the cloud. Software program is being delivered by DevOps practices over the standard waterfall methodology. No matter a corporation’s dimension or sort, adopting cloud is a journey. The North star of this digital transformation is to have absolutely working, extremely automated functions and infrastructure within the cloud. Probably the most troublesome facets of such a colossal change is automating and scaling. This contains:

  • Adapting on-prem, handbook software program to work on the cloud
  • Shifting away from GUI-driven duties
  • Changing legacy programs
  • Onboarding and offboarding administrative customers

A cloud working mannequin is starting to emerge so as to tackle these ache factors, beginning with a SaaS deployment mannequin. Configuring and automating new builds in an API-first method ensures efficient scaling and easy testing strategies. Every cloud supplier gives its personal set of distinctive interface futures to help with scaling.

Zero Belief safety gives simply the precise safety structure for the trendy cloud. In the identical method a single sign-on authentication for internet works, the concept is to allow the identical for infrastructure. Okta is working on this house, and Ivan provides a glimpse into the software program firm’s innerworkings.

The Cloud Working Mannequin

Historic approaches to operations don’t work in a cloud context. Making use of legacy fashions to trendy environments results in messy, inefficient architectures. Stitching collectively a number of present entities within the cloud—suppose HR programs, governance programs, toolings, and interfaces—isn’t any straightforward activity.

That’s method the Cloud Working Mannequin gives a brand new method to operations. Declaring programs as code means the precise guardrails are in place when automation takes over at scale. Present instruments, akin to Terraform, Chef, Puppet, and Ansible, present declarative mechanisms for designing and automating large-scale, elastic infrastructure environments nearer to the code working mannequin. Subsequent, a GitOps workflow permits builders in new methods. Some distributors outline GitOps as “operations by pull request.”

Safety In A Totally Automated Future

Within the newest State of DevOps Report, safety is reported as a lagging operate. Ivan expresses his shock on the hole between the development of individuals and firm DevOps journeys and the unrealized safety ideally suited. Nevertheless, given what we all know concerning the stress to compete in fast-paced markets, it is smart that seemingly minor safety elements are compromised. In a world of customer-facing functions, safety is typically secondary to availability and reliability. Multicloud infrastructures are elastic, ephemeral assets. Getting a deal with on safety in such an surroundings isn’t straightforward.

Shift Safety Left

Within the context of DevOps and DevSecOps, shifting left means transferring towards a linear DevOps mannequin. Whether or not it’s software program improvement or infrastructure operations, mapping its lifecycle as a steady course of the place automation strikes by way of phases from left to proper ensures that the people who design the workflows can inject safety controls early on—as far left as doable. The purpose is that when the machine enters the workflow, the precise guardrails are already in place. Safety is just pretty much as good because the injected controls within the code, which is why shifting left is so crucial.


Ivan additional discusses the precise duties of builders, the operations staff, and the safety staff and why working in partnership, versus a hierarchy or in silos, results in higher safety outcomes.

Identification And DevOps Automation

For apparent causes, entry and identification is a crucial operate of DevOps. In writing utility and infrastructure code, this stuff get vetted and programmed manually. Nevertheless, the additional to the precise of the workflow we go, as automation takes over within the type of software program packages, manufacturing environments are given entry. That is the place a Zero Belief structure is crucial.

Ivan goes on to element a number of the challenges and options of identification in automation, together with:

  • Minimizing the publicity of delicate accounts and credentials
  • Decommissioning entry
  • Shifting away from static administrative credentials
  • Centralizing authentication and authorization
  • Finish-to-end automation of the lifecycle of accounts and insurance policies

Okta: The New Commonplace Of Identification For The New Means Of Work

Earlier than wrapping up with a little bit of Q&A, Ivan explains how his firm’s answer will help. Okta gives a workforce product line that gives identification and entry administration options for workers, contractors, and companions. They securely join individuals to assets by way of a set of merchandise that embrace single sign-on, multifactor authentication, and lifecycle administration, all of which Ivan explains intimately.

With the intention to get essentially the most of this session and to be taught extra about how Okta could also be best for you,please go to the Cyber Safety Digital Summit web page, register, after which comply with the hyperlink despatched to your inbox.