Chapter 6 Flashcards

1
Q

SDLC (Software Development Life Cycle)

A

The steps in a model for software development throughout its life.

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

Feasibility Phase

A

Initial investigations into whether the effort should occur are conducted.

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

Analysis/Requirements Phase

A

Customer input is sought to determine what the desired functionality is.

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

Design Phase

A

Design for functionality, architecture, integration, and any other elements that require design consideration.

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

Development Phase

A

Coding the of the application.

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

UAT (User Acceptance Testing)

A

Testing that ensures that the users of the software are satisfied.

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

Testing/Integration Phase

A

Formal testing with customers or others outside the development team.

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

Maintenance Phase

A

Patching, updating, minor modifications, and other work that goes into daily support.

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

Disposition Phase

A

The end of a products life, is sometimes shutdown.

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

Waterfall Model

A

A sequential development model in which each phase is followed by the next.

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

Spiral Model

A

A development model that uses linear concepts from the Waterfall model and adds an iterative process that revisits phases multiple times throughout the development cycle.

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

Agile Model

A

A development model that is iterative and incremental rather than linear.

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

Continuous Integration

A

A development practice that checks code into a shared repository on a consistent basis.

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

OWASP

A

Define Security Requirements
Leverage Security Frameworks
Secure Database Access
Encode and Escape Data
Validate All Inputs
Implement Digital Identity
Enforce Access Controls
Protect Data Everywhere
Implement Logging and Monitoring
Handle all Errors and Exceptions

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

API (Application Programming Interface)

A

Interfaces between clients and servers or applications and operating systems that define how the client should ask for information from the server and how the server will respond.

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

Pair Programming

A

An Agile software development technique that places two developers at one workstation.

17
Q

Over-the-Shoulder

A

Relies on a pair of developers and requires one developer to explain the code to the other.

18
Q

Pass-around Code Review

A

A form of manual peer review done by sending completed code to reviewers who check the code for issues.

19
Q

Tool-assisted

A

Relies on software based tools to conduct code reviews.

20
Q

Fagan Inspection

A

A structured formal code review intended to find a variety of problems during the development process.

21
Q

Static Code Analysis

A

Reviewing the source code for an application.

22
Q

Dynamic Code Analysis

A

Executing the code and using inputs to test the software.

23
Q

Fuzz Testing

A

Sending invalid or random data to an application to test its ability to handle unexpected data.

24
Q

Injection Vulnerabilities

A

An attacker supplies some type of code to a web application as input to trick the web server into executing the code or supplying it to another server to execute.

25
Q

Session Hijacking

A

Stealing an existing authenticated session with a website.

26
Q

Directory Traversal Attack

A

AN attack that uses a security misconfiguration to navigate directory structures to access files that should remain secure.

27
Q

File Inclusion Attack

A

Uses directory traversal to actually execute the code contained in a file.

28
Q

XSS (Cross-Site Scripting)

A

Attackers perform an HTML injection by inserting their own HTML code into a web page.

29
Q

Request Forgery Attack

A

Exploit trust relationships and attempt to have users unwittingly execute commands against a remote server.

30
Q

XSRF or CSRF (Cross-site Request Forgery)

A

An attack that exploits the trust that a user has in a website to execute code on the user’s computer.

31
Q

SSRF (Server-side Request Forgery)

A

An attack that tricks a server into visiting a URL based on user-supplied input.

32
Q

WAF (Web Application Firewall)

A

A “firewall” that works at the Application Layer and receives all network traffic headed to that server. It then perform input validation before passing that info on to the server.

33
Q

Database Normalization

A

A Set of design principle that database designers should follow when building and modifying databases.

34
Q

Code Signing

A

Provides developers a way to confirm the authenticity of their code to end users.

35
Q

SWG (Secure Web Gateway)

A

Protects users working in the office or outside the office who are accessing resources from the internet.

36
Q

OWASP (Open Web Application Security Project)

A

Provides a regularly updated list of proactive controls regarding security threats to web applications.

37
Q

CI/CD (Continuous Integration/Continuous Delivery)

A

Ensures that code vulnerabilities can be patched and updated code placed into production as quickly as possible.

38
Q
A