Section 10 Secure Software Development Flashcards

1
Q
  1. Planning and analysis
  2. Software/Systems Design
  3. Implementation
  4. Testing
  5. Integration
  6. Deployment
  7. Maintenance
A

SDLC Phasing

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

Software development is performed in time boxed or small increments to allow more adaptivity to change.

A

Agile

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

Software development and information technology operations.

A

Dev Ops

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

Applications should be deployed using code signing to ensure the program is not changed inadvertently or maliciously prior to delivery to an end user.

A

Authenticity and Integrity

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

Layering of security controls is more effective and secure than relying on a single control.

A

Defense in Depth

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

Any input that is received from a user should undergo input validation prior to allowing it to be utilized by an application.

A

Never Trust User Input

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

Users and processes should be run using the least amount of access necessary to perform a given function.

A

Least Privilege

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

Default installations should include secure configurations instead of requiring an administrator or user to add in additional security.

A

Secure Defaults

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

Applications should be coded to properly conduct error handling for exceptions in order to fail securely instead of crashing.

A

Fail Security

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

If a vulnerability is identified, then it should be quickly and correctly patched to remove the vulnerability.

A

Fix Security Issues

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

SDK’s must come from trusted sources to ensure no malicious code is being added.

A

Rely on Trusted SDK’s

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

Occurs when a tester is not provided with any information about the system or program prior to conducting the test.

A

Blackbox Testing

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

Occurs when a tester is provided full details of a system including the source code, diagrams, and user credentials in order to conduct the test.

A

Whitebox Testing

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

A mix of blackbox and whitebox testing where the tester is given some amount of information about he system, but conducts his testing as if he doesn’t have full access to it.

A

Graybox Testing

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

Provides control over what the application should do when faced with a runtime or syntax error.

A

Structured Exception Handling (SEH)

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

Application verify that information received from a user matches a specific format or range of values.

A

Input Validation

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

Source code of an application is reviewed manually or with automatic tools without running with code.

A

Static Analysis

18
Q

Analysis and testing of a program occurs while it is being executed or run.

A

Dynamic Analysis

19
Q

Injection of randomized data into a software program in an attempt to find system failures, memory leaks, error handling issues, and improper input validation.

A

Fuzzing

20
Q

Code placed in computer programs to by pass normal authentication and other security mechanisms.

A

Backdoors

21
Q

Method of accessing unauthorized directories by moving through the directory structure on a remote server.

A

Directory Traversal

22
Q

Occurs when an attacker is able to execute or run commands on a victim computer.

A

Arbitrary Code Execution

23
Q

Attack against a vulnerability that is unknown to the original developer or manufacture.

A

Zero Day

24
Q

Occurs when a process stores data outside the memory range allocated by the developer.

A

Buffer overflow

25
Q

A temporary storage area that a program uses to store data.

A

Buffer

26
Q

Reserved area of memory where the program saves the return address when a function call instruction is received.

A

Stack

27
Q

Occurs when an attacker fills up the buffer with NOP so that the return address may hit a NOP and continue on until it finds the attacker’s code to run.

A

“Smash the Stack”

28
Q

Method used by programmers to randomly arranges the different address spaces used by a program or process to prevent buffer overflow exploits.

A

Address Space Layout Randomization

29
Q

Occurs when an attacker embeds malicious scripting commands on a trusted website.

A

Cross-site Scripting (XSS)

30
Q
  1. Stored/Persistent
  2. Reflected
  3. DOM-Based
A

3 Types of XSS

31
Q

Attempt to exploit the victim’s web browser.

A

Document Object Model (DOM) - based

32
Q

Occurs when an attacker forces a user to execute actions on a web server for which they are already authenticated.

A

Cross-site Request Forgery (XSRF/CSRF)

33
Q

Attack consisting of the insertion or injection of an SQL query via input data from the client to a web application.

A

SQL Injection

34
Q

Insertion of additional information or code through data input from a client to an applicaiton.

A

Injection Attack

35
Q
  1. SQL
  2. HTML
  3. XML
  4. LDAP
A

Common Injections

36
Q

XML encodes entities that expand the exponential sizes, consuming memory on the host and potentially crashing it.

A

XML Bomb (Billion Laughs Attack)

37
Q

An attack that embeds a request for a local resource.

A

XML External Entity (XEE)

38
Q

A software vulnerability that occurs when the code attempts to remove the relationship between a pointer and the thing it points to.

A

Dereferencing

39
Q

A software vulnerability when the resulting outcome from execution processes is directly dependent on the order and timing of certain events, and these events fail to execute in the order and timing intended by the developer.

A

Race condition

40
Q

The potential vulnerability that occurs when there is a change between when an app checked a resource and when the app used the resource.

A

Time of Check to Time of Use (TOCTTOU)

41
Q

Any program that does not properly record or log detailed enough information for an analyst to perform their job.

A

Insufficient Logging and Monitoring