Cybersecurity Fundamentals II

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/57

flashcard set

Earn XP

Description and Tags

A comprehensive set of flashcards covering key vocabulary and concepts related to Software Security and Cybersecurity fundamentals.

Last updated 5:52 PM on 4/16/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai

No analytics yet

Send a link to your students to track their progress

58 Terms

1
New cards

Software Security

The practice of protecting software applications from security vulnerabilities.

2
New cards

Secure Software Development

A methodology that incorporates security at every stage of the software development lifecycle.

3
New cards

Insecure Interaction Between Components

A category of software error that occurs when software components do not securely interact with each other.

4
New cards

SQL Injection

A security vulnerability that allows an attacker to interfere with the queries that an application makes to its database.

5
New cards

Cross-Site Scripting (XSS)

A vulnerability that allows an attacker to inject malicious scripts into content from otherwise trusted websites.

6
New cards

Buffer Overflow

A vulnerability that occurs when a program writes more data to a block of memory than it can hold.

7
New cards

Injection Flaws

Security vulnerabilities that occur when an application fails to properly validate input.

8
New cards

Authentication Bypass

A flaw that allows users to gain unauthorized access to systems or data without proper credentials.

9
New cards

Race Condition

A situation where the outcome of a process is unexpectedly affected by the timing of events.

10
New cards

OWASP Top Ten

A list of the ten most critical security risks to web applications as identified by the Open Web Application Security Project.

11
New cards

Secure Design

Principles that guide the creation of secure software architectures.

12
New cards

Secure Programming

Programming practices that ensure the software is written with security in mind.

13
New cards

CWE/SANS Top 25

A list of the most dangerous software errors that can lead to security vulnerabilities.

14
New cards

Vulnerable Components

Librarie or parts of software that are known to have security vulnerabilities.

15
New cards

Plaintext Passwords

Storing passwords in a readable format without encryption.

16
New cards

Input Validation

The process of ensuring that a program only accepts input that is safe and valid.

17
New cards

Output Encoding

Transforms output data to ensure security, particularly in web applications.

18
New cards

Cryptographic Failures

Weaknesses in cryptographic methods that may compromise security.

19
New cards

Least Privilege

A security principle that dictates that users should only have the minimum levels of access— or permissions— needed to perform their job functions.

20
New cards

Error Handling

The process of responding to and recovering from error conditions.

21
New cards

Memory Leak

A failure in a program to release discarded memory, causing reducing memory availability.

22
New cards

Secure Program

A program designed to operate correctly in the presence of malicious inputs.

23
New cards

Data Integrity

The accuracy and consistency of stored data over its life cycle.

24
New cards

Error States

Conditions where a program cannot continue normal execution due to a problem.

25
New cards

Dynamic Memory Allocation

The process of allocating memory storage at runtime.

26
New cards

Environment Variables

Dynamic named values that can affect the behavior of running processes.

27
New cards

Testing and Validation

The processes to ensure that software meets specifications and requirements.

28
New cards

Security Logging

The process of keeping records of events that happen in a system.

29
New cards

Safe Temporary Files

Files created for temporary purposes that do not expose sensitive data.

30
New cards

Debugging

The process of finding and resolving defects or problems within a computer program.

31
New cards

Code Review

A systematic examination of computer source code.

32
New cards

Access Control

The process of limiting access to data and resources based on policies.

33
New cards

Application Security

The use of software, hardware, and procedural methods to protect applications.

34
New cards

Software Development Lifecycle (SDLC)

The process of planning, creating, testing, and deploying software.

35
New cards

Agile Development

An iterative approach to software development.

36
New cards

Waterfall Model

A linear and sequential approach to software development.

37
New cards

Secure Coding Standards

Best practices and guidelines for writing secure code.

38
New cards

Cross-Site Request Forgery (CSRF)

An attack that tricks the victim into submitting a request to a web application.

39
New cards

Impact of Vulnerabilities

The consequences of security weaknesses that can be exploited.

40
New cards

Coding Best Practices

Recommendations that help developers write software that is secure, maintainable, and efficient.

41
New cards

Privileged User

A user with special access or permissions to a computer system or network.

42
New cards

Secure Data Transmission

The use of encryption and other methods to protect data being sent over networks.

43
New cards

Penetration Testing

An ethical hacking technique used to evaluate the security of a computer system.

44
New cards

Fuzz Testing

A technique for discovering security loopholes and bugs by inputting random data.

45
New cards

Binary Interpretation of Inputs

How different types of data are read by the program based on the encoding.

46
New cards

Integrity Check

A process used to ensure data is not altered or tampered with.

47
New cards

User Authentication

The process of verifying the identity of a user.

48
New cards

Input Fuzzing

Using random data as input to check how well a program handles surprises.

49
New cards

Privacy Policy

A document that outlines how a company collects, uses, and protects user information.

50
New cards

Data Exposure

When sensitive information is accessible to unauthorized individuals.

51
New cards

Scripting Languages

Programming languages primarily used for writing scripts.

52
New cards

Computer Algorithm

A set of step-by-step instructions for performing a task.

53
New cards

Hard-coded Credentials

Storing sensitive information like usernames and passwords directly in the application's code.

54
New cards

Malicious Script

Code intentionally written to cause unwanted actions on a computer system.

55
New cards

User Input

Data provided by the user, potentially affecting program execution.

56
New cards

System Architecture

The conceptual model that defines the structure and behavior of a system.

57
New cards

Static Code Analysis

The analysis of source code without executing it to find bugs.

58
New cards

Security Assumptions

Beliefs that systems will behave in certain ways, which can lead to vulnerabilities.