All right, secure application, develop environment.
All right, protected environment with
strategies from the design deployment and maintenance are implemented.
So you want to protect your code, your code repositories.
The secure application development lifecycle, again, is development testing,
staging, production, quality assurance, it all goes round and round.
All right, so the stages, development.
Okay, programs are tested to guarantee the
application software runs according to a given piece of code
defined change and version controls at the development phase.
Testing.
Program is tested during the development and staging process to guarantee the
application or software accomplishes given tasks without any complications.
Staging.
Problem is again tested in the staging
phase to ensure the stability of the application.
In production, once the code is
successfully tested, it's deployed to a real time environment.
Then quality assurance,
testers perform quality checks and deployed software to check whether end
users face any issue in accessing the application.
A software is not ready to roll until you
get that user acceptance testing where they say, Yeah, roger that.
This is exactly what we're looking for.
Usually, it's never quite that smooth.
Our resiliency and automation strategies.
Systems that can be restored to their usual operating conditions after facing an
interruption or outage are known as resilient systems.
This goes back to recovery or corrective
types of controls, can be approved by adopting a proper
configuration, snapshots, strengthening the ability to return to a original state.
And again, this is also part of the testing and staging process.