WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:0

00:06.320 --> 00:14.500
All right, secure application,
develop environment.

00:14.520 --> 00:16.040
All right, protected environment with

00:16.040 --> 00:19.100
strategies from the design deployment
and maintenance are implemented.

00:19.130 --> 00:22.020
So you want to protect your
code, your code repositories.

00:22.050 --> 00:27.120
The secure application development
lifecycle, again, is development testing,

00:27.150 --> 00:31.320
staging, production, quality assurance,
it all goes round and round.

00:34.040 --> 00:37.420
All right, so the stages, development.

00:37.450 --> 00:39.840
Okay, programs are tested to guarantee the

00:39.870 --> 00:43.020
application software runs according to a
given piece of code

00:43.050 --> 00:46.300
defined change and version
controls at the development phase.

00:46.320 --> 00:47.060
Testing.

00:47.080 --> 00:50.580
Program is tested during the development
and staging process to guarantee the

00:50.610 --> 00:54.860
application or software accomplishes
given tasks without any complications.

00:54.890 --> 00:56.020
Staging.

00:56.040 --> 00:57.880
Problem is again tested in the staging

00:57.910 --> 01:00.340
phase to ensure the stability
of the application.

01:00.360 --> 01:01.860
In production, once the code is

01:01.890 --> 01:05.260
successfully tested,
it's deployed to a real time environment.

01:05.290 --> 01:06.700
Then quality assurance,

01:06.730 --> 01:10.480
testers perform quality checks and
deployed software to check whether end

01:10.510 --> 01:13.570
users face any issue in
accessing the application.

01:13.600 --> 01:16.680
A software is not ready to roll until you

01:16.710 --> 01:20.480
get that user acceptance testing
where they say, Yeah, roger that.

01:20.510 --> 01:23.440
This is exactly what we're looking for.

01:23.840 --> 01:26.400
Usually, it's never quite that smooth.

01:26.600 --> 01:29.020
Our resiliency and automation strategies.

01:29.050 --> 01:33.360
Systems that can be restored to their
usual operating conditions after facing an

01:33.390 --> 01:36.980
interruption or outage are
known as resilient systems.

01:37.010 --> 01:39.520
This goes back to recovery or corrective

01:39.550 --> 01:43.000
types of controls,
can be approved by adopting a proper

01:43.030 --> 01:47.210
configuration, snapshots, strengthening
the ability to return to a original state.

01:47.240 --> 01:50.920
And again, this is also part of
the testing and staging process.