Security + Chapter 11 Security And Vulnerability In The Network

Front 1

Penetration Testing

Back 1

Simulate an attack and look for holes
that exist in order to be able to fix them.

Front 2

Penetration Testing Steps

Back 2

1. Verify a Threat Exists

2. Bypass Security Controls

3. Actively Test Security Controls

4. Exploit Vulnerabilities

Front 3

Verify a Threat Exists

Back 3

You need to find the threats that the system is vulnerable to which can include such things as open ports, unpatched software, weak passwords, and so on.

Front 4

Bypass Security Controls

Back 4

Check to see if it is possible to get around the security that you think is there.

Front 5

Actively Test Security Controls

Back 5

Security controls need to be constantly tested to verify that they catch/stop what they should.

Front 6

Exploit Vulnerabilities

Back 6

Once a vulnerability is found, it is imperative to ascertain the extent to which it can be exploited.

Front 7

Vulnerability Scanning

Back 7

looking for weaknesses in networks, computers, or even applications.

 

Ex. Nessus, Retina

Front 8

5 Major Tasks

Back 8

1. Passively Testing Security Controls

2. Interpreting Results

3. Identifying Vulnerability

4. Identifying Lack of Security Controls

5. Identifying Common Misconfigurations

Front 9

Passively Testing Security Controls

Back 9

The vulnerability scanner can test the security controls without doing any actual harm.

 

It looks only for the openings that are there and reports them back to you.

Front 10

Interpreting Results

Back 10

Interpret the results of their fi ndings and deliver a report that can be shared with management.

Front 11

Identifying Vulnerability

Back 11

Just knowing that the port is open means little unless you canassociate it with the vulnerability tied to it.

 

Ex. port 23 being open is a problem since it is commonly associated with Telnet.

Front 12

Identifying Lack of Security Controls

Back 12

You want to know not just what is weak, but what is missing altogether.

Front 13

Identifying Common Misconfigurations

Back 13

Applications and services are improperly configured in which those misconfigurations
can allow more users to access an application than should, cause the application to
crash, or introduce any of a number of other security concerns.

Front 14

Ethical Hacking

Back 14

Identifying vulnerabilities that exist in a system for which they have authorization

Front 15

Black Box Testing

Back 15

Administrator acts as if they have no prior knowledge of the network in which they do not know what safeguards are in place, systems used, or any related information.

 

Blind

Front 16

White Box Testing

Back 16

Premise of knowing something about the
network and systems in place—just as a malicious insider would in which they try to find a weakness armed with information about the source code, the routing, and so on.

 

Full disclousure

Front 17

Gray Box Testing

Back 17

Between black box and white box testing. 

 

The usual scenario trying to be re-created is that an outsider is working in conjunction with an insider who has given them some information.

 

Partial disclosure

Front 18

Risk

Back 18

What is the actual danger under consideration?

 

Likelihood of an attack being successful.

Front 19

Threat

Back 19

What are the likely causes associated with the risk?

 

The means and source of the potential attack.

Front 20

Vulnerability

Back 20

Where is the system weak?

 

Identify the flaws, the holes, the areas of
exposure, and perils.

Front 21

Baseline Reporting

Back 21

Checks to make sure things are operating status quo, and change detection is used to alert when modifications are made.

Front 22

Code Review

Back 22

Look at all custom written code for holes that may exist.

 

Opportunities for injection to occur (SQL, LDAP, code, etc.), crosssite request forgery, and authentication.

Front 23

Determine Attack Surface

Back 23

Those who are authenticated and more importantly those who are not.

 

It can include the services, protocols, interfaces, and code.

Front 24

Architecture

Back 24

Involves using a control framework to focus on the foundational infrastructure.

 

WAN, the extranet, the Internet, and the intranet.

Front 25

Design Review

Back 25

Examines the ports and protocols used, the rules, segmentation, and access control.

Front 26

Rule-Based Management

Back 26

The access is granted to the object based on both the object’s sensitivity label and the user’s sensitivity label.

 

Ex. Top Secret, Secret, etc. 

Front 27

Port Security

Back 27

1. MAC Limiting and Filtering

2. 802.1X

3. Disable Unused Ports

Front 28

Working With 802.1X

Back 28

Port-based security for wireless network access control.

Front 29

Flood Guards and Loop Protection

Back 29

Flood guard is a protection feature built into many firewalls that allow the administrator
to tweak the tolerance for unanswered login attacks.

 

Loop protection is a similar feature that works in layer 2 switching configurations and is
intended to prevent broadcast loops.

Front 30

Network Bridging

Back 30

Occurs when a device has more than one network adapter card installed and the opportunity presents itself for a user on one of the networks to which the device is attached to jump to the other.

Front 31

Preventing Network Bridging

Back 31

you can configure your network such that when bridging is detected, you shut off/disable that jack.

 

You can also create profiles that allow for only
one interface.

Front 32

Log Analysis

Back 32

Crucial to identifying problems that occur related to security as an administrator,
you have the ability to turn on logging at many different locations and levels.

Front 33

Manual Bypassing of Electronic Controls

Back 33

Failsafe, the application stops all work, reports an error, and closes out/exits.

 

Failopen, is for the application to stop running and let you know that it encountered the unexpected character.

Front 34

 Monitoring System Logs

Back 34

These are event logs, security logs, access logs and audit logs.

Front 35

Security Logs/Access Logs

Back 35

The Security Logs are accessed beneath Windows Logs in Event Viewer, and each event is preceded by either a key (audit success) or a lock (audit failure).

Front 36

Audit Logs

Back 36

You want to verify not only that the program is running but also that the defi nition
file(s) being used is current.

Front 37

Security Posture

Back 37

The security posture is the approach a business takes to security. 

 

Planning phase to implementation and everything in between: hardware, software,
settings, and so on.

Front 38

Initial Baseline Configuration

Back 38

The starting point needs to always be documented and used as the basis from which to begin making changes.

 

Examination of access controls, cryptography controls, integrity/auditing/monitoring controls, privacy policy, application standards, security policies, and configuration management.

Front 39

Continuous Security Monitoring

Back 39

Taking a snapshot of the situation at a moment in time fails to give sufficient authority, and it is important to always monitor the current environment.

Front 40

Remediation

Back 40

Identify the solutions to those problems and act on them.

Front 41

Reporting

Back 41

Almost every department generates
its own reports and uses what they find as a dashboard for action.

Front 42

Alarms

Back 42

Indications of a problem currently going on; think of a siren sounding when someone kicks in the door to a home.

Front 43

Alerts

Back 43

These are issues that you need to pay attention to but are not bringing the system to its knees at this very moment. 

Front 44

Trends

Back 44

By focusing on trends, you can identify weaknesses in your system and areas where you need to devote more resources to
head off future problems.