Software Security Testing Flashcards

1
Q

A measure of the system’s ability to protect data and information from unauthorized access while still providing access to people and systems that are authorized

A

Security

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

An action taken against a computer system with the intention of doing harm is called an ____

A

Attack

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

CIA approach to security

A
  • Confidentiality
  • Integrity
  • Availability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are other security characteristics?

A
  • Authentication
  • Nonrepudiation
  • Authorization
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Data or services are protected from unauthorized access

A

Confidentiality

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

Data or services are not subject to unauthorized manipulation

A

Integrity

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

The system will be available for legitimate use

A

Availability

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

Verifies the identities of the parties to a transaction and checks if they are truly who they claim to be

A

Authentication

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

Guarantees that the sender of a message cannot later deny having sent the message, and that the recipient cannot deny having received the message

A

Nonrepudiation

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

Grants a user the privileges to perform a task

A

Authorization

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

Human or another system which may have been previously certified (either correctly or incorrectly) or may be currently unknown. A human attacker may be from outside the organization or from inside the organization

A

Source

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

Unauthorized attempt is made to display data, change or delete data, access system services, change the system’s behavior, or reduce availability

A

Stimulus

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

T/F Software design reviews can evaluate security

A

T

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

T/F Data flows (and therefore data flow diagrams) can not be used for security analysis

A

F, they can

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

T/F Reused and off-the-shelf software components should meet the same security requirements as new software

A

T

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

T/F Construction languages and their implementations (for example, compilers) are not serious contributors to security vulnerabilities

A

F

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

Special form of random testing aimed at breaking the software often used for security testing

A

Fuzz testing

18
Q

T/F Security, in terms of access control and the backup facilities, is a key aspect of library management

A

T

19
Q

Builds security in software by following a set of established and/or recommended rules and practices in software development

A

Secure software development

20
Q

T/F A generally accepted view concerning software security is that it is much better to design security into software than to patch it in after software is developed

A

T

21
Q

T/F Security faults and loopholes can be and often are introduced during maintenance

A

T

22
Q

Deals with the clarification and specification of security policy and objectives into software requirements

A

Software requirements security

23
Q

Specific functions that are required for the sake of security

A

Software requirements

24
Q

Possible ways that the security of software is threatened

A

Threats/risks

25
Q

What type of requirements are security requirements?

A

“Shall not” requirements

26
Q

T/F It is possible to define this unwanted behavior as simple constraints to be checked by the system

A

F

27
Q

T/F It is impossible to prove that a system does not do something

A

T

28
Q

Can you derive requirements for an unknown type of attack?

A

No

29
Q

Deals with the design of software modules that fit together to meet the security objectives specified in the security requirements

A

Software design security

30
Q

T/F Factors considered may include frameworks and access modes that set up the overall security monitoring/enforcement strategies, as well as the individual policy enforcement mechanisms

A

T

31
Q

Concerns the question of how to write actual programming code for specific situations such that security considerations are taken care of

A

Software construction security

32
Q

T/F When an error occurs, the program should restore the state of the software to the state it had before the process began, and then terminate

A

T

33
Q

T/F The error status of every function does not need to be checked

A

F

34
Q

Should your program share objects in memory with any other program?

A

No

35
Q

Security concerns during software development may necessitate one or more software processes to protect the security of the development environment and reduce the risk of malicious acts

A

Adding security processes

36
Q

Evaluate the degree to which a test item and its associated data are protected so that unauthorized persons or systems cannot use, read, or modify them and authorized persons or systems are granted required access to them

A

Security testing

37
Q

T/F Security requirements are concerned with the ability to protect the data and functionality of a test item from unauthorized users and malicious use

A

T

38
Q

Involves attempted access to a test item (including
its functionality and/or private data) by a tester that is
mimicking the actions of an unauthorized user

A

Penetration testing

39
Q

Involves attempted access to private data and verification of the audit trail (i.e., trace) that is left behind when users access private data

A

Privacy testing

40
Q

A type of static testing in which a tester inspects, reviews, or walks through the requirements and code of a test item to determine whether any security vulnerabilities are present

A

Security auditing

41
Q

Involves the use of automated testing tools to scan a

test item for signs of specific known vulnerabilities

A

Vulnerability scanning