Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Computer Security > Midterm > Flashcards

Midterm Flashcards

1
Q

Threat

A

Potential dangers to a system’s security

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Exploit

A

Method of attack to cause harm to a system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Vulnerability

A

Weakness in a system that can be exploited

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Controls

A

Measures implemented to mitigate risks

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Motives

A

Why they do it, money, power, control, fame, etc.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Arms Races

A

Constant battle between attackers and defenders in the cybersecurity realm. Attackers develop new methods to breach security, defenders respond with countermeasures.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Chicken/Egg

A

Which should come first; implementing security measures or responding to security threats.
You can’t trust software because its pretty hard to make every single component yourself.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Existence of Absolutes

A

In computer security nothing is absolute. Vulnerabilities can exist even in the most secure systems, and attackers continuously find new ways to exploit them.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Confidentiality

A

Ensures that data is only accessible to to authorized users

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Integrity

A

Ensures that data is accurate and unaltered

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Availability

A

Ensures that data is accessible any time when needed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

The Three Goals of Cybersecurity

A

Confidentiality, integrity, and availability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Confidentiality Examples

A

Encryption, authentication(passwords, biometrics), NDA policy

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Integrity Examples

A

Offline backups, blockchain, digital signatures, hashing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Availability Examples

A

load balancing, backups, hot sites

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

SetUid Model

A

Allows users to execute a program with the permissions of the program’s owner. Useful for programs/tasks that change password or file accesses, without needing to grant them full administrative access.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Purpose of Bounds Checking

A

Ensures that data stays within the boundaries of allocated memory

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Arrays

A

More efficient but have fixed sizes. This makes them vulnerable to buffer overflows, off by ones, etc. Lack of runtime bounds checking in some languages. So they can be exploited to read data outside the array’s memory.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Dynamic Memory

A

Some bounds checking done as part of the allocation process. Pointers unlikely to point at anything ripe to change.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Inheritance

A

Can propagate vulnerabilities from parent classes to child classes if not properly managed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Security Through Obscurity

A

Security by means of hiding implementation details. Flawed way of thinking. Bad actors always have the time and drive.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Policy Based Security

A

Defining rules and regulations that dictate how data, software, and infrastructure of a system should be accessed, used, and protected within an organization.

23
Q

Policy Based Security Examples

A

Coding policy/guide, use dynamic arrays if possible, proactively keep and check array bounds for fixed arrays, peer reviews, code reuse, code audits

24
Q

Fortress Defense

A

Makes it difficult and time consuming for attackers to breach in the system. Primarily focused on access controls.

25
Q

Fortress Defense Examples

A

Host configuration, ACLs, authentication, role-based access controls, sandboxing, firewalling, MAC, DAC, domain type enforcement

26
Q

Host Configuration

A

Refers to the setup and configuration of a system such as settings, permissions, installed programs, and etc.

27
Q

Firewalling

A

A firewall is an application/device that monitors and controls incoming and outgoing network traffic. They inspect data and determine if the data us allowed or blocked depending on rules set.

28
Q

ACL

A

Access control list. Rules or criteria that determine whether an entity is allowed or denied access to a resource or service. Filesystem ACL and Network ACL.

29
Q

Authentication

A

Verify identity of a user. Can use passwords, multi factor authentication (MFA), certificates, and etc.

30
Q

Role Based Access Controls

A

Assigns permissions to users based on their role within an organization.

31
Q

Sandboxing

A

Running applications or processes in a controlled environment (such as a VM) to limit their access to system resources.

32
Q

MAC

A

Mandatory Access Controls. A security model where access controls are determined by the owner of the information. Access controls are immutable. Access control info travels with user and data.

33
Q

DAC

A

Discretionary Access Controls. Alterable access controls. Typically in a filesystem level, API level. You have to trust users because they can make copy of data with new ACLs

34
Q

Domain Type Enforcement

A

Often called capabilities. Access controls at the programming interface level. Detailed divison of labor, roles, and duties. Can add a level of protection against software bugs.
Example: only shells and certain processes can fork or execute

35
Q

Fortress Defense Evasion Techniques

A

Encapsulation, spoofing (using another’s address or identity), breach of physical security, extortion, exploit encoding and encapsulation and fragmentation

36
Q

Time-Based Defense

A

To detect and react appropriately. Involves implementing measures to detect and prevent security breaches in real time.

37
Q

Anti-Virus Software

A

Detect and remove malicious software such as bugs, worms, trojans, etc. Works by scanning files and comparing them against a database of known malware signatures, mire advanced forms use behavior detection.

38
Q

Network Intrusion Detection/Prevention

A

NIDS/NIPS. Monitors lots of network traffic and identifies anomalies which are then blocked. Can be evaded by cryptography.

39
Q

Host Based(Time Based Defense)

A

Ability to monitor and identify many system-level events.

40
Q

Time Based Defense Evasion Techniques

A

Cryptography, encapsulation, fragmentation

41
Q

Denial of Service

A

Many forms: disrupt services by overwhelming the target system with excessive requests, input validation problems

42
Q

Good Defense Plan

A

Careful planning, fortress defense tactics, detection and reaction capabilities

43
Q

Offense: Enumeration

A

Gathering information about your targets.

44
Q

Passive Enumeration

A

Stealth: Web searching, public directories, packet sniffers, social engineering

45
Q

Active Enumeration

A

Directly interact with victim, can be traced/alerted: Ping-sweeps, port-scanners, get OS version, use client software

46
Q

Offense Strategies

A

Privilege escalation, memory corruption, remote code execution/injection DoS

47
Q

Vulnerabilities of a System

A

Buffer overflows, oversights in design, input validation failures, race conditions, hardware, lack of access controls, lack of encryption, misconfigurations

48
Q

Buffer Overflows and Underflows

A

Allows memory corruption of same process memory, can be used to inject code or elevate privileges

49
Q

Injecting code/shellcode

A

Injecting malicious code into a system using vulnerabilities like buffer overflows, SQL injections, etc.

50
Q

Oversights

A

Mistakes during development or configuration in a system that can add vulnerabilities. Examples: no input validation, not applying security patches, etc.

51
Q

Input Validation Problems

A

When applications fail to properly validate user input.
Ex: SQL injections, script injections, buffer overflows

52
Q

Race Conditions

A

When the outcome of a system’s event depends on time or sequence, it can lead to vulnerabilities.

53
Q

Hardware Security Holes Examples

A

Cosmic rays, memory tightly packed leading to leaks, adjusting CPU frequency can make you see data or tamper with higher levels of execution

54
Q

Misconfigurations

A

When a system is not properly configured to enforce security rules. Blame is on the new or poorly trained person

Computer Security (2 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions