Operations and Maintenance
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 »
Difficulty
Intermediate
Video Transcription
00:00
>> Welcome back to Cybrary,
00:00
this of course, I'm your instructor, Brad Rhodes.
00:00
Let's jump into the fourth phase
00:00
of the system development life cycle,
00:00
that's operations and maintenance.
00:00
In this lesson,
00:00
similar to all the other ones in this module,
00:00
we're going to look at security activities
00:00
to talk about the linkages,
00:00
and we're going to define what operations/maintenance is.
00:00
Insecurity activities, what are we doing?
00:00
This is where we're reviewing
00:00
the system if it's ready to go or not.
00:00
We're doing configuration management here.
00:00
[LAUGHTER] The configuration change process,
00:00
that's what we're doing here, that's
00:00
what we're talking about.
00:00
We're instituting the processes and procedures.
00:00
We're going to the point where we want to get to
00:00
consistent execution with the system.
00:00
If we have a very complex system
00:00
with very complex security controls,
00:00
we as issues are responsible for documenting all of that,
00:00
ensuring we've got the procedures laid out
00:00
for everybody so that it's easy to follow,
00:00
easy to implement, and then we monitor that.
00:00
We're going to look at those security controls,
00:00
be the technical,
00:00
be the non-technical,
00:00
be the detective, preventive, whatever.
00:00
We are going to be monitoring those controls.
00:00
We do that continuous monitoring here and throughout.
00:00
Then obviously, we've talked about the fact that
00:00
we now deal with the risk management framework,
00:00
the RMS, and that is
00:00
a continuous reauthorization process.
00:00
It's very possible that with the RMS,
00:00
you could be reauthorizing a highly complex,
00:00
highly sensitive system every six months or sooner.
00:00
It's very important to keep that in mind,
00:00
and keep your poems prepped and ready to
00:00
go. Here's our linkages.
00:00
We've decided, again, we talked about previously,
00:00
and this is an important point to
00:00
remember what the SDLC,
00:00
is that we can always stop.
00:00
We can always say, "You know what?
00:00
I did my needs and determine where I was going to go.
00:00
I meet my requirements.
00:00
I went ahead and designed things, put it all together,
00:00
and then I get to the point where I go to
00:00
operations maintenance and I might say, You know what?
00:00
I'm done, I don't need
00:00
this system anymore. I need to move on."
00:00
One of the great things about these different pieces and
00:00
parts of this SDLC is
00:00
that each one of them is that decision point to
00:00
determine whether we're going to continue on with
00:00
the system or stop doing what we're doing.
00:00
Three key things here from a linkage perspective.
00:00
It's operational readiness,
00:00
configuration management, change control,
00:00
and then importantly, continuous
00:00
monitoring throughout the life cycle of the system.
00:00
The decision point that we get to
00:00
the end here of the operations and
00:00
maintenance phase is going to be
00:00
planned well before we got to this point,
00:00
and that's the decision whether we're going to
00:00
dispose or decommission our systems.
00:00
Operations and maintenance are two important things.
00:00
Operations is the continuous monitoring side,
00:00
and then maintenance if we're patching,
00:00
and patching it's probably
00:00
a little less descriptive here than it should be.
00:00
What I'm implying here with patching is
00:00
all the things that need to be done
00:00
to keep a system up-to-date,
00:00
and patching could be OS,
00:00
it could be firmware,
00:00
it could be software applications, it could be hardware.
00:00
Patching can be anything that
00:00
allows us to keep our systems up-to-date.
00:00
By the way, but keeping the systems up-to-date,
00:00
we're going to frustrate
00:00
the threat actors because up-to-date
00:00
systems are harder to break
00:00
into than systems that are not.
00:00
On the continuous monitoring side.
00:00
That's again, monitoring all of the controls throughout
00:00
the life cycle of our system wallets and operations.
00:00
That's looking at security controls,
00:00
that's looking at the functionality,
00:00
that's looking at everything,
00:00
and it's looking at everything from
00:00
the technical controls that we've put in place,
00:00
like say, nibs heads, all those kind of things.
00:00
To looking at the non-technical controls,
00:00
to determine, "Hey, do we have
00:00
the right procedures written?"
00:00
If we keep having a problem with, say,
00:00
a data loss prevention engine,
00:00
and it's because we didn't write the procedures right.
00:00
Well, guess what? That's something that we can fix
00:00
via that continuous monitoring process.
00:00
In this lesson, we looked at the security activities
00:00
in the operations, and maintenance phase.
00:00
We talked about the linkages as we've done previously.
00:00
Then in operation and maintenance,
00:00
we really looked at the fact
00:00
that this is called modern patching.
00:00
This is keeping our systems
00:00
up-to-date and then monitoring
00:00
all of our security controls. Will see you next time.
Up Next
Disposal
Module Summary
Objectives and Introducing NIST and Standards
NIST SP 800-160: Systems Security Engineering
NIST SP 800-53: Security and Privacy Controls for Federal Information Systems and Organizations
Similar Content
