Introduction to Shifting Security to the Left
Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or
Already have an account? Sign In »
Video Transcription
00:00
>> [MUSIC] Welcome to this session
00:00
>> on CloudGuard shift left.
00:00
>> In this session we'll explore
00:00
CloudGuard's shift left solution for
00:00
shifting security to the left and how it is deployed.
00:00
By the end of this session,
00:00
you will be able to describe why
00:00
CloudGuard's shift left is needed and how it works,
00:00
and you'll be able to perform
00:00
a basic deployment of CloudGuard shift left.
00:00
Now that we've discussed deployment and
00:00
configuration of the various
00:00
container protection components,
00:00
which relate to run time.
00:00
Let's discuss the importance of shifting
00:00
left and how CloudGuard's shift left enables this.
00:00
Shifting left refers to moving
00:00
security sooner in the development process.
00:00
Instead of only protecting assets and run time,
00:00
shifting your security to
00:00
the left preempts misconfigurations and
00:00
vulnerabilities in your asset
00:00
during the CICD pipeline process,
00:00
before it is deployed.
00:00
CloudGuard solution for shifting
00:00
left is called shift left and it brings
00:00
the CloudGuard security abilities to detect and prevent
00:00
risks in Cloud deployments while in the CICD pipeline.
00:00
Shift left scans infrastructure
00:00
as code templates for risk,
00:00
checks software for known vulnerabilities and
00:00
scans container images for security issues.
00:00
It also provides a single interface
00:00
for multiple CICD security steps.
00:00
Instead of being forced to fixing production,
00:00
developers are notified of issues immediately.
00:00
Shift left runs a pre-configured security policy rule
00:00
set or rule sets to examine the destination of choice,
00:00
build in infrastructure as code template,
00:00
such as a Telephone template,
00:00
the software being developed and all container images.
00:00
Shift left can be executed either
00:00
on-demand or automatically as
00:00
part of the pipeline execution.
00:00
The end result of executing shift
00:00
left is a stop-go action in the pipeline.
00:00
The pipeline's execution moves
00:00
to the next step upon a shift left,
00:00
okay, and if everything passes,
00:00
the pipeline is completed.
00:00
Otherwise, depending on the instructions,
00:00
the execution will stop and
00:00
the relevant developer will be
00:00
alerted about the failure and it's cause.
00:00
With this in mind, let's take a look at
00:00
the process of deploying shift left.
Up Next
Instructed By
Similar Content
