Now in order for us to have that new piece of code or programming or
implementation within our actual cloud environment,
it does require development.
And that's where we're covering continuous development.
And again, this is going to follow the software development lifecycle model
that we've already covered previously.
As it tied into continuous integration, this focuses more on the actual first
part of SDLC.
But if it had to be broken down to which parts continuous development covers, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But if it had to be broken down to which parts continuous development covers,
this would be focused on the planning and design portion.
Yes, we're going to utilize the entire SDLC model when it comes to continuous
integration and continuous development.
And specifically when we develop new products and features for our cloud
environment, but the stuff we develop isn't going to be implemented right away.
This could be a portion where we develop security patches and updates and be
able to configure them automatically through the continuous development
pipeline of planning and making sure that the integration inside of the actual WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
pipeline of planning and making sure that the integration inside of the actual
environment is suitable for that patch.
And we want to make sure that we're testing inside of our sandbox mode as much
as possible before we actually send it to a production environment.
But we also take this time in the development continuous development process to
take a look at vulnerability management and integrate vulnerability scanning
tools like maybe nexus into the continuous development pipeline to detect and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
tools like maybe nexus into the continuous development pipeline to detect and
mitigate vulnerabilities before the actual deployment of things that are going
to be sent out in continuous integration.
This is a constant deploy and test configuration method inside of our sandbox
environment. And again, if we don't have a sandbox environment available,
something as close to it as possible without running the risk of possibly
sending out a patch or development that is not fully ready for live production.
Now there are plenty of different compliance checks that we can do inside of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now there are plenty of different compliance checks that we can do inside of
the continuous development model. And we can incorporate things like NIST,
especially the NIST Cybersecurity Framework ISO 27001. And we can even get into
some of our regulatory stuff like PCI at the SS to make sure that we're meeting
skylines and standards for things like PII or personally identifiable
information.
Now you may be wondering how we monitor all this and I'm glad you asked because
of the next portion of the skill. I'm going to introduce you to something else WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
of the next portion of the skill. I'm going to introduce you to something else
inside of our DevNet sandbox to be able to get a little bit more eyes on.