45 hours 38 minutes
Welcome to Cyber Aires. Video Siris on the comp Tia Security Plus S. Y +0501 certification and example
I'm your instructor Round Werner.
You can learn more about me in the first series of videos available through Cyber.
Please visit Cyber A Diet I t. To learn more about security, plus their certification as well as many other certifications.
This next series of videos talks about security risk management.
You see, security is all about managing risk.
The likelihood of an unexpected event that will impact an organization
managing risk require strong governance with an understanding of the goals of the organization, an understanding of critical functions performed within the organization and the comprehensive assessment of the risk the organization faces.
From this understanding, organizations come to develop appropriate policies, plans and procedures related to organizational security that are commensurate or equal to the goals of an acceptable risk, tolerance and threshold of the organization.
Don't worry. If the's terms seem kind of new to you,
we'll be going through each of them through this video.
The Fifth Security plus Domain Explorers risk management
how to manage corporate policies, assess business impacts, identify and analyze potential risks and enable appropriate business decisions.
This domain also covers incident response and forensics,
disaster recovery in business continuity
and the other effects of risks.
Lastly, we'll explore various types of security controls and methods for carrying out data security and privacy practices.
Section 5.1 requires you to explain the importance of policies, plans and procedures related to information security
to ensure that proper risk management is coordinated, update and communicated and maintained.
It is important to establish clear and detailed security policies
that are approved by organizational management and brought to the attention of all of the users through regular security awareness. Training
policies that the users do not know about are rarely effective, and those that lack management support can be unenforceable.
Several policies could support risk management within the organization.
I'll explain policies in more detail in this section.
This slide provides an overview of security policies, plans, procedures that different types of policy documents such a standards.
These are all explained in the Company of Security plus security certification exam objectives. I recommend you review that document prior to viewing this video. Siri's
in the next few minutes will be covering policy types such a standards, policies, guidelines, procedures,
a standard operating procedure or s o p.
Different types of agreements such as N d. A B p A s l A.
By the way, if you're not familiar with these terms, will be covering them in a moment.
We'll also talk about general security policies that you'll see in most organizations, such as a social media policy. Acceptably used policy. Maybe a policy on e mail
final part will talk about his personnel management howto handle people.
I get it.
Policies are a bore
you're working through somewhat of a technical security certification like Security. Plus, you're going. Why do we need to understand policies?
Let me tell you, policies are the foundation and the bedrock of a security program
very challenging to move security forward without a good set of policies, one that is understood by the organization that people accept and are following.
So, fortunately, documentation, documentation documentation is still key to a lot of what we do as security professionals.
that you have in your organization will define how I t
will approach security, how people within the organization should approach security and how certain situations will be handled
all of this needs to be documented because if it's not written down,
probably won't be followed consistently and constantly within an organization.
They're different types of policy documents you'll see within a standard organization.
Sometimes we'll use the word policies and refer to multiple types of statements or documents.
You can see on this slide that their policies, standards, guidelines, procedures that all fulfill the organizational goal.
thes air. The thou shout now shout shout rules for the organization. The must follow rules
that an organization will have.
These are the rules that, if not followed or violated or breached, can cause serious damage. Possible termination of employees who do violate a policy statement.
Second type of a policy document is a standard.
These tend to be more technical in nature and specify mandatory controls for example,
password or authentication standards, which couldn't and enable with back in technology, such as a security policy like a GPO. Within Microsoft,
the standard should be based on a specific policy.
The third type of policy document. You need to be familiar with our guidelines. These air they won't pay, try to do this,
but if they are not followed really doesn't cause a lot of damage to the organization.
Provide examples in a moment. Procedures. These are steps to take to fulfill a guideline, standard
So an incident response procedure there may be an incident response policy. For example, Response policy is
any incidents shall be documented and investigated.
The incident response plan or procedure
will provide those step by step instructions to follow When there is an incident,
a standard could come into play with incident response if you have a standard set of tools. So for any forensics investigation, we will always use this tool,
by the way, with policies you want to keep them. Technology agnostic should not specify technology.
What I've seen happen is that an organization had a policy about remote access that talked about dial up.
dial up like the old phone. We really don't use that much anymore, do we?
But that's what it was stated in The policy was the standard remote access for the organization, and when technology changed, they didn't update their policy. So kind of makes the policy worth worthless.
So review these different terms as they are very important, not only within the company of security plus example. But out there in the business world as well
as you are reviewing policies or even perhaps writing a policy for an organization,
there's certain common key elements that you'll find in each one of them,
for example, will be a scope statement,
an overview statement, a purpose statement, the target audience
definitions And, yes, definitions do matter, Because how I described an incident may be different. How you describe an incident
versions and implementation date.
Let me describe some of these First of all, overview.
Quick sentence. A tweet about what that policy is about
the purpose. What are the risks? The policy is fulfilling
scope. Who does the policy apply to?
Yeah, it's the entire company. Is it a specific area? Are specific technologies important to include that with the scope
target audience? The Who who needs to read and follow a policy
mentioned definition So any terms that are not commonly known
Set your definitions for your organization.
The version of the policy has your updating the policy
implementation date. When
that policy will be enforced, give your user sometime become used to that policy.
Don't write the policy and say what you need to follow it on day one. That's pretty rare.
Give that time to become familiar
compliance and exception. So if someone's noncompliant with your policy,
one of the ramifications, what's the effect?
Can that person be fired?
Exceptions to the policy. How do you handle exceptions?
And then, lastly, So this is all the beginning part, and then you go into your policy statements
specific statements about the rules for your company. All of this should be included in a standard policy document.
By the way, if you look up on the Internet, policy states a template, you'll find many are out there that follow this.
There are many common types of policies that you'll see within organizations. So this is just not only good to know for security plus exam,
but also to be a good security professional.
Number one will be an exceptional, exceptional acceptable use policy.
The acceptable use policy or a U. P. R. The rules around the use of computers.
What is acceptable.
Maybe Internet browsing would be included. The use of communications applications such as email, instant messaging, text how can we use company systems? What are we supposed to do and not supposed to do
all of those air included, except acceptable use policy
access policy. Those are the rules regarding access. It might also include authorization.
Let me give you a quick example. This is my policies should be kept short.
Policies are short. Go into more detail and other documents. My acceptable use policy associated with access control. It's very simple.
Users are responsible for their access.
You were responsible for securing the user. I d. And any authentication such the past were given to them.
If you want to include rules such as
sharing of passwords or writing down passwords, though should not be included on policy. Those air actually standards.
So the policy high level.
Because when you're writing a policy, consider how you're going to enforce it. How you gonna audit against that policy? Very important.
Let me tell you, I've seen so many policies that are completely unenforceable. And then really, what value do they have?
Okay, make sure your policies are enforceable and kept short.
This life shows many other common forms of policies review them. You'll see them throughout your cybersecurity career.
A standard operating procedure
is a term I've heard used with the Army. But some businesses use. Then
it's the standard set of instructions for workers to carry out
attacks. Cassette of operations,
so standard operating procedure. This is more set for common tasks. You don't necessarily see this with security, although it could include, say, patching
standard operating procedures for when you see an update is available as a general user here, the steps you need to follow
so you'll see eso peas in your career. So be familiar with this term for the comedy A Security Plus Exam.
The next area in our exploration of policies
recording for businesses, etcetera are the different types of agreements that are set
between an employee and an organization and then between organizations.
This is the alphabet soup portion. Be familiar with these again. I've seen these throughout my security and career.
The 1st 1 is an nd a non disclosure agreement.
I'll often have to sign these when I'm talking to an organization is part of a security assessment
what this is. This is protect sensitive information.
So I'm talking to an organization I find out of vulnerability.
I'm not allowed to
talk about this outside of the context of my assessment because of the nd A. It's a legally binding agreement.
It could be between an individual and an organization or organizations between each other.
The next type of typical business agreement is the B P. A. Or a business partner agreements.
This is regarding such as profit sharing. So I'm working with another business
and we're working together to grow. Our business is we've made a determination of how we're gonna do that. That's in the B p. A more of a financial document than a security agreement, but occasionally they will contain security statements.
S L. A
seen SL is forever service level agreements. What is the level of service you will provide,
for example, of hiring a security operation center?
How quickly do they need to provide me with an alert
or outsourcing? My i T.
What level of service. So what percentage should I expect for up time?
59 is a typical S L A variety. So it's 99.999% up time
is an A type of S l A.
Be familiar with this. It's the nature and level of service
provided by a vendor provider.
Other types you'll find our memory memorandum of understanding or memorandum of agreement.
This outlines the terms and details of the agreement. So we decided we're working together.
We want to make sure we have all of the details hashed out in an M. O, U or M Away
The interconnection security agreement.
Who my connecting to on my network, whether any third parties or vendors that we're working together,
we want to have a nice an interconnection security agreement or service agreement in place prior to connecting our networks. Just tow. Provide a certain level of security controls in place to protect both sides.
Review. These different pipes of agreements may see these unaccompanied of security plus exams, and you will see them out in the business world.
This nest next section is about personnel management.
How do we handle people
associated with security?
Security requires people to do their function, do their job to protect, to detect.
So this next section talks about different steps. Different ways to protect, detect and respond.
For example, mandatory vacation.
Why is this a policy? Why don't we require vacations? It's actually Detective Element.
So say I'm committing fraud
it requires me to log in every day.
Well, if I'm on vacation, I can't do that.
So, for example, for a financial organization from where I worked required us to take atleast seven consecutive days of vacation.
We're not allowed to log in. We're not allowed remote access. We had to step away to detect fraud.
switching out of jobs again to detect fraud. You have someone else do your job for a while. A good for cross training redundancy.
Hopefully, someone else with a job rotation will be able to confirm that you're doing your job
for people who have not been doing their job. That's how they've been caught. Someone else started doing their job while they're away or during a regular job irritation and detected
separation of duties. This is one of those key security tenants
So separate the duties. You don't have the same person who writes the check that in cash. The checks, for example. Same person who can service the servers. Someone else should check their work. So you have a separate person. Do the quality. Check
a clean desk policy for security being sure people aren't leaving out sensitive documents or other information.
Other steps for personnel management. Background checks normally accomplished through human resource is prior to employment.
Making sure people are doing ran have done what they said they've done.
Checking their financial background, legal background, criminal background sure that they're not gonna be influenced unduly, potentially harm your organization in their systems
on boarding. Also done within human resource is
normally there may be some security awareness training associated with on board.
You might be part of that. If you're part of a security group,
it's a great time to get in front of new employees. Get them thinking about cyber security
to make sure you're part of the security group is part of the on boarding process.
The terminations exit interviews.
I've been part of that to make sure people's access is removed immediately upon termination
that they can't get to the computer systems through a remote access channel VPN, for example, that any of their files are secured that they don't have any back doors into the systems or Trojans or time bombs on the systems of that happening.
Exit interviews to gain information about what the employee who's leaving has experienced security also need to be very involved with human resources.
The last portion of personnel management
is roll based awareness training. So conducting that regular awareness training don't just do it one time of year
but also focus it on the rolls
makes security personal for people. Great way to encourage them to be a part of the security program.
Systems administrators will have separate security training than a general user.
Maybe your application developers. They need their own security training day on a WASP. And if you're not familiar with the wops, go back to the previous session on application security and specific training available for application developers.
So it's based on their job responsibilities.
Then you want to make sure there's continuing education, continual learning for employees. This way, they're always part of the security solution.
These are many of the ideas behind personnel management, where security needs to be involved
to help you prepare for the company a security plus 5 +01 exam. Here's some questions for you.
Based on this session,
which of the following policies describes how the employees in an organization can use corporate resource is
Internet use policy, the service level agreement or S l. A.
See acceptable use policy
u P or the separation of duties policy.
What do you think the answer is?
The answer is C Acceptable use policy.
The next question for this section.
According to the Comedy of Security Plus Blueprint,
this is a personnel management practice of rotating administrative users between roles to ensure that fraudulent activity cannot be sustained.
Looking through the answer, she will see the answer is a job rotation.
Go through this and other exam questions and keep practicing
to gain a better understanding to help you pass your security plus exam and become a great security plus professional.
This ends section 5.1.
We need to be able to explain the importance of policies, plant policy plans and procedures related to organizational security.
I'm Ron were.
CompTIA Security+ SY0-501
The Practice Labs practice exam CompTIA Security+ SYO-501 practice test challenges the student to demonstrate ...
CompTIA Security+ 501
Empower yourself as a security professional by gaining the fundamental knowledge for securing a network ...