Domain 8: Software Development Security Flashcards

1
Q

Message

A

communication to or input of an object

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

Method

A

internal code that defines the actions an object performs in response to a message

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

Behavior

A

results or output exhibited by an object

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

Class

A

collection of the common methods from a set of objects that defines the behavior of those objects

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

Instance

A

example

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

Inheritance

A

methods from a class are inherited from a subclass

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

Delegation

A

forwarding of a request by an object to another object

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

Polymorphism

A

the characteristic of an object that allows it to respond with different behaviors to the same message or method because of changes in external conditions

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

Cohesion

A

strength of the relationship between the purposes of the methods within the same class

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

Coupling

A

level of interaction between objects

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

Assurance procedures

A

formalized processes by which trust is built into the life cycle of a system

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

Input Validation

A

verifies that the values provided by the user match the programmers expectation

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

Should Input Validation occur on the Server or Client side?

A

Server

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

Conceptual Defenition

A

create the basic concept statement for a system

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

Functional Requirements Determination

A

specific system functionalities are listed

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

Control Specification Development

A

analyze the system from a security perspective

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

Code Review Walk Through

A

look for logical or security flaws

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

Waterfall Model

A

step by step life cycle model, can only go back one phase

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

Spiral Model

A

multiple iterations of a waterfall style process

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

Agile Software Development

A

iterative software development process

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

Highest Priority in the Agile Manifesto

A

Satisfy the customer through early and continuous delivery of valuable software

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

SW-CMM

A

SW Capability Maturity Model - all orgs move through a variety of maturity phases in sequential fashion

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

IDEAL Model

A

Initiating, Diagnosing, Establishing, Acting, Learning

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

SW-CMM Levels

A

Initiating, repeatable, Defined, Managed, Optimized

25
Q

White-box Testing

A

examines the internal logical structures of a program and steps through the code line by line

26
Q

Black-box Testing

A

examines from a user perspective by providing different inputs

27
Q

Gray-Box Testing

A

most popular, combines both testing forms

28
Q

Code Repositories

A

a central storage point for developers to place their source code

29
Q

Hierarchical Database

A

one to many - think of an org chart

30
Q

Distributed Databased

A

data in more than one database but all logically connected

31
Q

Relational Databases

A

flat, two-dimensional tables

32
Q

Fields (Relational Databases)

A

attributes

33
Q

Tuple (Relational Databases)

A

record

34
Q

Cardinality (Relational Databases)

A

number of rows

35
Q

Degree (Relational Databases)

A

number of columns

36
Q

Domain (Relational Databases)

A

set of allowable values

37
Q

Candidate Keys

A

subset of attributes that can be used to uniquely identify any record in a table

38
Q

Primary Keys

A

selected from the set of candidate keys for a table to be used to uniquely identify the records in a table

39
Q

Foreign Key

A

enforce relationships between two tables

40
Q

What are the 4 required characteristics of all database transactions?

A

Atomicity, Consistency, Isolation, Durability

41
Q

Atomicity

A

all or nothing affair

42
Q

Consistency

A

transactions must operate in an environment that is consistent with all of the database’s rules

43
Q

Isolation

A

transactions operate separately from each other

44
Q

Durability

A

transactions are preserved once they are committed to the database

45
Q

Concurrency

A

edit control - ensures that info in the database is always correct (I&A is protected)

46
Q

DSS

A

Decision Support System - help desk

47
Q

Virus

A

spreads from system to system, must have a host and does not self propogate

48
Q

Master Boot Record Viruses

A

virus that attacks the bootable media

49
Q

File Infector Viruses

A

.exe and .com extensions

50
Q

Macro Viruses

A

viruses in VBA

51
Q

Service Injection Viruses

A

inject themselves into trusted runtime processes of the OS

52
Q

Multiparite Viruses

A

use more than one propogation technique

53
Q

Stealth Viruses

A

hide themselves by tampering with the OS

54
Q

Polymorphic Viruses

A

modify their own code

55
Q

Encrypted Viruses

A

use cryptographic techniques to avoid detection

56
Q

Worms

A

propagate themselves without human intervention

57
Q

Lost Update

A

One transaction writes a value to the database that overwrites a value needed by transactions that have earlier precendence, causing those transactions to read an incorrect value

58
Q

Dirty Read

A

One transaction reads a value from a database that was written by another transaction that did not commit

59
Q

Incorrect Summaries

A

One transaction is using an aggregate function while a second is making modifications