Domain 8 Test Notes Flashcards

Concepts I need to understand (47 cards)

1
Q

Scripted Transactions with known expected results. May be a part of DAST(Dynamic Application Security Testing)

A

Synthetic Transactions

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

Improving computer algorithms (rules and guidelines) by experience.

A

Machine Learning

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

Gives machines the ability to do things that a human can do better or allow a machine to perform tasks we previously thought required human intelligence

A

Artificial Intelligence

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

A collection or ledger of records, transactions, operations, or other events that are verified using hashing, timestamps, and transaction data

A

Blockchain

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

Is when every foreign key in a secondary table matches a primary key in the parent table. It is broken if not all foreign keys match the primary key

A

Referential Integrity

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

Each attribute value is consistent with the attribute data type

A

Semantic Integrity

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

Each row (tuple) has a unique primary value that is not null

A

Entity Integrity

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

is a relational database model that refers to four key properties that ensure reliable processing of database transactions. These properties together ensure data integrity and reliability in database systems.

A

ACID Model

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

All or nothing, if any part of the transaction fails, the entire transaction fails

A

Atomicity

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

The database must be consistent with the rules before and after the transaction

A

Consistency

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

A transaction must be completed before another transaction can modify the same data

A

Isolation

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

Once transactions are committed to the database, they must be preserved

A

Durability

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

A framework designed to scale agile practices across an entire enterprise efficiently and effectively. Adds the necessary layers to make Agile work in a large enterprise level context

A

Scaled Agile Framework (SAFe)

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

Emphasis on delivering value through respect for people, culture, flow optimization, innovation, and relentless improvement.

A

Lean Agile Principle (SAFe Principle)

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

Customer centric approach, releasing a continuous flow of valuable products and services

A

Agile Product Delivery (SAFe Principle)

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

Focus on building and sustaining large applications, networks, and systems needed for a large enterprise to function

A

Enterprise Solution Delivery (SAFe Principle)

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

Leaders’ understand and commitment to implementing Lean and Agile principles

A

Lean Leadership (SAFe Principle)

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

A prepared SQL statement that allows user input to be passed into the statement as carefully defined variables that do not allow the insertion of code. Can protect applications against injection attacks.

A

Parameterized Queries

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

A software solution that uses AI to automatically respond to some security incidents.

A

Security Orchestration, Automation, Response (SOAR)

20
Q

Documents and checklist that define the process for verifying and responding to a specific type of security incident

21
Q

the implementation of a playbook’s data and processes into an automated tool within the SOAR platform.

22
Q

Sophisticated attacks are likely affiliated with government agencies. Often have access to zero day exploits that are not known to software vendors.

A

Advanced Persistent Threat (APT)

23
Q

Provides a framework of process descriptions for describing the life cycle of systems created by humans. It defines a set of processes and associated terminology from an engineering viewpoint.

A

ISO/IEC/IEEE 15288

24
Q

provides a catalogue of architectural and design principles that can be used in the development of secure products, systems and applications together with guidance on how to use those principles effectively.

A

ISO/IEC 19249

25
Framework for managing software development. Designed for teams with approximately 10 individuals. Generally relies on 2 week development cycle (sprints) and short daily meetings
Scrum
26
Representing the product's stakeholders, the voice of the customer, and is accountable for ensuring that the team delivers value to the business.
Product Owner (Scrum Role)
27
Responsible for delivering the product at the end of each sprint.
Development Team (Scrum Role)
28
Facilitates and accountable for removing impediments to the ability of the team to deliver the product goals and deliverables. Ensure the scrum framework is followed
Scrum Master (Scrum Role)
29
a technique that is used to increase the difficulty of performing a buffer overflow attack that requires the attacker to know the location of an executable in memory.
Address space layout randomization (ASLR)
30
cooperation between development, operations, and Quality Assurance. Aligned with Agile, code is deployed rapidly, multiple times a day.
DevOps
31
Code is publicly released. Can be tested, improved and corrected. Allows attackers to find flaws.
Open Source
32
Software is released, but source code is kept a secret.
Closed Source
33
Software is protected by intellectual property and/or patents.
Proprietary Software
34
A security approach where only a specifically allowed items are permitted and everything else is blocked.
Positive Listing Strategy aka Whitelisting
35
Evaluates source code or compiled code for security vulnerabilities. It doesn't run the application. Usually involves the use of automate tools design to detect common software flaws such as buffer overflow
Static Application Security Testing (SAST)
36
Evaluates the security of software by running it in a runtime environment. Source code is not required.
Dynamic Application Security Testing (DAST)
37
Performs real time analysis of runtime behavior, application performance, HTTP/HTTPS traffic, frameworks, components, and backend connections.
Interactive Application Security Testing (IAST)
38
A tool that runs on a server and intercepts calls to and from an application and validates data requests.
Runtime Application Self Protection (RASP)
39
Dynamic testing technique that provides many different types of input to test the limits by providing invalid input to the software.
Fuzzing
40
takes previous input values and alters the characters of content, append strings, or performs other data manipulation techniques.
Mutation (Dumb) Fuzzing
41
develops data models and creates input from scratch based on known structures and formats.
Generational (Intelligent) Fuzzing
42
Assesses the performance of modules against the interface specifications to ensure that they will work together properly. Includes APIs, UI, and physical.
Interface Testing
43
Identifies and analyzes the open source and 3rd party components used in a software application for known vulnerabilities and licensing issues.
Sofware Composition Analysis (SCA)
44
Estimate the degree of testing conducted against the new software. Formula: Number of use cases tested/total number of use cases
Test Coverage Analysis
45
Branch: if statements Condition: logical test Function: Function test Loop: loop test Statement: Every line in code
Common Test Criteria
46
placeholders in SQL statements that allow you to substitute values at runtime. Used to pass data into or retrieve data from a database enhancing security performance and portability
Bind Variables
47
Used to clean up the data in a database table to make it logically concise, organized, and consistent. Removes redundant data and improves the integrity and availability of the database.
Data Normalization