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 at the moment’s aggressive enterprise panorama. Safety practitioners are tasked with a tough ask: hold 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 Transferring 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 measurement or kind, 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. Essentially the most tough facets of such a colossal change is automating and scaling. This consists of:

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

A cloud working mannequin is starting to emerge as a way to handle 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 provides its personal set of distinctive interface futures to help with scaling.

Zero Belief safety provides simply the fitting safety structure for the fashionable cloud. In the identical manner a single sign-on authentication for internet works, the concept is to allow the identical for infrastructure. Okta is working on this area, and Ivan offers 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 fashionable environments results in messy, inefficient architectures. Stitching collectively a number of current entities within the cloud—assume HR methods, governance methods, toolings, and interfaces—isn’t any simple process.

That’s manner the Cloud Working Mannequin provides a brand new strategy to operations. Declaring methods as code means the fitting guardrails are in place when automation takes over at scale. Present instruments, resembling 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 allows builders in new methods. Some distributors outline GitOps as “operations by pull request.”

Safety In A Absolutely Automated Future

Within the newest State of DevOps Report, safety is reported as a lagging perform. 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 in regards to the strain 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 usually secondary to availability and reliability. Multicloud infrastructures are elastic, ephemeral sources. Getting a deal with on safety in such an atmosphere isn’t simple.

Shift Safety Left

Within the context of DevOps and DevSecOps, shifting left means shifting towards a linear DevOps mannequin. Whether or not it’s software program growth 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 aim is that when the machine enters the workflow, the fitting 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 important.


Ivan additional discusses the particular 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 perform of DevOps. In writing utility and infrastructure code, these items get vetted and programmed manually. Nevertheless, the additional to the fitting 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
  • Transferring 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 Manner Of Work

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

With a view to get probably the most of this session and to study 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.