Domain 8 - Software Development Security Flashcards
1
Q
System Development Life Cycle (SDLC)
A
Project initiation
Functional analysis and planning
System design specifications
Acceptance testing and implementation
System Life Cycle (SLC) (extends beyond SDLC)
Operations and maintenance
Revisions/ Disposal
2
Q
Project initiation
A
Feasibility, cost, risk analysis, Management approval, basic security objectives
3
Q
Functional analysis and planning
A
Define need, requirements, review proposed security controls
4
Q
System design specifications
A
Develop detailed design specs, Review support documentation, Examine security controls
5
Q
Software development
A
Programmers develop code. Unit testing Check modules. Prototyping, Verification, Validation
6
Q
Acceptance testing and implementation
A
Separation of duties, security testing, data validation, bounds checking, certification, accreditation , part of release control
7
Q
Operations and maintenance
A
release into production. Certification/accreditation
8
Q
Revisions/ Disposal
A
remove. Sanitation and destruction of unneeded data
9
Q
Change Management Process
A
Together, change and configuration management techniques form an important part of the software engineer’s arsenal and protect the organization from development-related security issues. The change management process has three basic components:
10
Q
Three basic components of the Change Management Process
A
Request Control
Change Control
Release Control
11
Q
Request Control
A
provides an organized framework within which users can request modifications, managers can conduct cost/ benefit analysis, and developers can prioritize tasks.
12
Q
Change Control
A
provides an organized framework within which multiple developers can create and test a solution prior to rolling it out into a production environment. Change control includes conforming to quality control restrictions, developing tools for update or change deployment, properly documenting any coded changes, and rest
13
Q
Release Control
A
Once the changes are finalized, they must be approved for release through the release control procedure.
14
Q
Configuration Management Process
A
This process is used to control the version( s) of software used throughout an organization and formally track and control changes
15
Q
Configuration Identification
A
administrators document the configuration of covered software products throughout the organization.
16
Q
Configuration Control
A
ensures that changes to software versions are made in accordance with the change control and configuration management policies. Updates can be made only from authorized distributions in accordance with those policies.
17
Q
Configuration Status Accounting
A
Formalized procedures are used to keep track of all authorized changes that take place.
18
Q
Configuration Audit
A
periodic configuration audit should be conducted to ensure that the actual production environment is consistent with the accounting records and that no unauthorized configuration changes have taken place.
19
Q
SDLC
A
Conceptual definition Functional requirements definition Control specifications development Design review Code review System test review Maintenance and change management
20
Q
Software Capability Maturity model (CMM)
A
Quality of software is a direct function of quality of development and maintenance
Defined by Carnegie Mellon University SEI (Software Engineering Institute)
Describes procedures, principles, and practices that underlie software development process maturity 1-2 REACTIVE, 3-5 PROACTIVE
21
Q
List the 5 steps of the Software Capability Maturity model (CMM).
A
- initiating – competent people, informal processes, adhoc, absence of formal process
- repeatable – project management processes, basic lifecycle management processes
- defined – engineering processes, presence of basic lifecycle management processes and reuse of code, use of requirements management, software project planning, quality assurance, configuration management practices
- managed – product and process improvement, quantitatively controlled
- Optimizing – continuous process improvement
Works with an IDEAL model.
Initiate begin effort, Diagnose perform assessment, Establish an action plan, Action implement improvements, Leverage reassesses and continuously improve
22
Q
Project Management Tools
A
Gantt Chart
PERT
23
Q
Gantt Chart
A
a type of bar chart that shows the interrelationships over time between projects and schedules. It provides a graphical illustration of a schedule that helps to plan, coordinate, and track specific tasks in a project. WBS a subpart
24
Q
PERT
A
Program Evaluation Review Technique is a projectscheduling tool used to judge the size of a software product in development and calculate the standard deviation (SD) for risk assessment. PERT relates the estimated lowest possible size, the most likely size, and the highest possible size of each component. PERT is used to direct improvements to project management and software coding in order to produce more efficient software.
25
DevOps
The DevOps approach seeks to resolve issues by bringing the three functions together in a single operational model.
The word DevOps is a combination of Development and Operations, symbolizing that these functions must merge and cooperate to meet business requirements. Integrates:
- Software Development,
- Quality Assurance
- IT Operations
NOT SECURITY
Software
26
Software Development Models
```
Simplistic model
Waterfall model
Waterfall including Validation and Verification (V&V)
Spiral model
Cleanroom
Cleanroom design
```
27
Simplistic model
This model was simplistic in that it assumed that each step could be completed and finalized without any effect from the later stages that may require rework
28
Waterfall model
Can be managed if developers are limited going back only one step. If rework may be done at any stage it’s not manageable. Problem: it assumes that a phase or stage ends at a specific time. System Requirements-> Software Requirements -> Analysis -> Program Design -> Coding -> Testing -> Operations & Maintenance
29
Waterfall including Validation and Verification (V&V)
Reinterpretation of the waterfall model where verification evaluates the product during development against specification and validation refers to the work product satisfying the real-world requirements and concepts. Verification=doing the job right Validation:= doing the right job
30
Spiral model
Angular = progress made Radial = cost
Lower left = development plans
Upper left = objectives of the plans, alternatives checked
Upper right = assessing alternatives, risk analysis Lower right = final development
Left horizontal axis = includes the major review required to complete each full cycle
31
Agile Software Development
Developers increasingly embraced approaches that placed an emphasis on the needs of the customer and on quickly developing new functionality that meets those needs in an iterative fashion.
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
WORKING SOFTWARE PRIMARY MEASURE OF SUCCESS
32
Database
general mechanism for defining, storing and manipulating data without writing specific programs
33
DBMS
refers to a suite of software programs that maintains and provides controlled access to data components store in rows and columns of a table
34
Types of Database Systems
- Hierarchical= tree (sons with only one parent), one to many relationship
- Network = tree (all interconnected)
- Mesh
- Object-orientated
- Relational – one-to-one relationships, has DDL and DML, has TUPLES and ATTRIBUTES (rows and columns)
- Key-Value Store - key-value database, is a data storage paradigm designed for storing, retrieving, and managing associative arrays, a data structure more commonly known today as a dictionary or hash.
35
DDL
Data definition language defines structure and schema
36
DML
Data manipulation language view, manipulate and use the database via VIEW, ADD, MODIFY, SORT and DELETE commands.
37
Degree of Db
–number of attributes (columns) in table
38
Tuple
row or record
39
DDE
Dynamic data exchange enables applications to work in a client/server model by providing the inter-process communications mechanism (IPC)
40
DCL
Data control language subset of SQL used to control access to data in a database, using GRANT and REVOKE statements
41
Semantic integrity
make sure that the structural and semantic rules are enforced on all data types, logical values that could adversely affect the structure of the database
42
Referential integrity
all foreign keys reference existing primary keys
43
Candidate Key
an attribute that is a unique identifier within a given table, one of the candidate keys is chosen to be the primary key and the others are alternate keys, A candidate key is a subset of attributes that can be used to uniquely identify any record in a table. No two records in the same table will ever contain the same values for all attributes composing a candidate key. Each table may have one or more candidate keys, which are chosen from column headings.
44
Primary Key
provide the sole tuple-level addressing mechanism within the relational model. Cannot contain a null value and cannot change or become null during the life of each entity. When the primary key of one relation is used as an attribute in another relation, it is the foreign key in that relation. Uniquely identify a record in a database
45
Foreign Key
represents a reference to an entry in some other table that is a primary key there. Link between the foreign and primary keys represents the relationship between the tuples. Enforces referential integrity
46
Main Components of a Db using Db
- Schemas; blueprints
- tables
- views
47
Incorrect Summaries
when one transaction is using an aggregate function to summarize data stored in a Db while a second transaction is making modifications to a Db, causing summary to include incorrect information
48
Dirty Reads
when one transaction reads a value from a Db that was written by another transaction that did not commit, Db concurrency issue
49
Lost Updates
when one transaction writes a value to the Db that overwrites a value needed by transactions that have earlier precedence
50
Dynamic Lifetime Objects
Objects created on the fly by software in an Object Oriented Programming environment. An object is preassembled code that is a self-contained module
51
ODBC
Open Database Connectivity is a database feature that allows applications to communicate with different types of databases without having to be directly programmed for interaction with each type. ODBC acts as a proxy
52
Multilevel security
it’s essential that admins and developers strive to keep data with different security requirements separate.
53
Database contamination
Mixing data with different classification levels and/ or need-to-know requirements and is a significant security challenge. Often, administrators will deploy a trusted front end to add multilevel security to a legacy or insecure DBMS.
54
Database partitioning
is the process of splitting a single database into multiple parts, each with a unique and distinct security level or type of content.
55
Polyinstantiation
occurs when two or more rows in the same relational database table appear to have identical primary key elements but contain different data for use at differing classification levels. It is often used as a defense against inference attacks
56
Database transactions
Four required characteristics: atomicity, consistency, isolation, and durability. Together, these attributes are known as the ACID model, which is a critical concept in the development of database management systems.
57
Atomicity
Database transactions must be atomic— that is, they must be an “all-or-nothing” affair. If any part of the transaction fails, the entire transaction must be rolled back as if it never occurred.
58
Consistency
All transactions must begin operating in an environment that is consistent with all of the database’s rules (for example, all records have a unique primary key). When the transaction is complete, the database must again be consistent with the rules, regardless of whether those rules were violated during the processing of the transaction itself. No other transaction should ever be able to use any inconsistent data that might be generated during the execution of another transaction.
59
Isolation
principle requires that transactions operate separately from each other. If a database receives two SQL transactions that modify the same data, one transaction must be completed in its entirety before the other transaction is allowed to modify the same data. This prevents one transaction from working with invalid data generated as an intermediate step by another transaction
60
Durability
Database transactions must be durable. That is, once they are committed to the database, they must be preserved. Databases ensure durability through the use of backup mechanisms, such as transaction logs.
61
Expert Systems
Expert systems seek to embody the accumulated knowledge of experts on a particular subject and apply it in a consistent fashion to future decisions. Every expert system has two main components: the knowledge base and the inference engine.
- Based on human reasoning
- Knowledge base of the domain in the form of rules
- If-then statements=called forward chaining
- Priority in rules are called salience
- Interference system = decision program
- Expert system = inference engine + knowledge base - Degree of uncertainty handled by approaches as Bayesian networks(probability of events), certainty factors(probability an event is true) or fuzzy logic(to develop conclusions)
- Two modes:
o Forward chaining: acquires info and comes to a conclusion
o Backward chaining: backtracks to determine IF a hypothesis is correct
62
Neural Networks
- Use complex computations to replace partial functions of the human mind
- Based on function of biologic neurons
- Works with weighted inputs
- If a threshold is exceeded there will be output
- Single-layer : only one level of summoning codes
- Multi-level: more levels of summoning codes
- Training period needed to determine input vectors
- adaptability (learning process)
63
Programming Language Generations
```
First-generation
Second-generation
Third-generation
Fourth-generation
Fifth-generation
```
64
First-generation languages (1GL)
include all machine languages
65
Second-generation languages (2GL)
include all assembly languages.
66
Third-generation languages (3GL)
include all compiled languages.
67
Fourth-generation languages (4GL)
attempt to approximate natural languages and include SQL, which is used by databases.
68
Fifth-generation languages (5GL)
allow programmers to create code using visual interfaces.
69
Compiler
Translates higher level program into an executable file
70
Interpreter
reads higher level code, one line at the time to produce machine instructions
71
Assembler
converts machine-code into binary machine instructions. Translate assembly language into machine language
72
Object Orientated Technology
Objects behave as a black box; they are encapsulated to perform an action. Can be substituted if they have compatible operations. It can store objects like video and pictures
73
Encapsulation (Data Hiding)
only data it needs, no accidental access to data
74
Message
communication to object to perform an action
75
Method
code that defines an action an object performs in response to a message
76
Behavior
results exhibited by an object in response to a msg.
77
Class
collection of methods that defines the behavior of objects
78
Instance
- objects are instances of classes that contain their methods
79
Inheritance
allows a subclass to access methods belonging to a superclass
80
Multiple Inheritance
class inherits characteristics from more than one parent class
81
Delegation
forwarding a request to another object Polymorphism: objects of many different classes that are related by some common super class. When different subclasses may have different methods using the same interfaces that respond differently
82
OORA, Requirements Analysis
defines classes of objects and their interactions
83
OOA, Analysis
understanding and modeling a particular problem Domain Analysis (DA) seeks to identify classes and objects that are common to all applications in a domain
84
OOD, Design
Objects are the basic units, and instances of classes
85
OOP, Programming
employment of objects and methods If class = airplane, objects like fighter plane, cargo plane, passenger plane can be created. Method would be what a plane would do with a message like: climb, dive, and roll.
86
ORBs, Object Request Brokers
middleware that acts as locators and distributors of the objects across networks.
87
CORBA, Common object request
broker architecture enables programs written in different languages and using different platforms and OS’s through IDL (Interface Definition Language)
88
COM, Common Object Model
support exchange of objects amongst programs. This used to be called OLE. DCOM is the network variant (distributed)
89
Conclusion
Object orientation (e.g. with C++ and Smalltalk) supports reuse of objects and reduces development risk, natural in its representation of real world entities.
90
Cohesion
ability to perform without use of other programs, strength of the relationship between the purposes of methods within the same class
91
High cohesion
without use of other modules
92
Low cohesion
must interact with other modules
93
Coupling
effect on other modules. Level of interaction between objects
94
High coupling
module largely affects many more modules
95
Low coupling
it doesn’t affect many other modules
| Technical
96
Technical Security Protection Mechanisms
```
Abstraction
Separation of privilege
Process isolation
Layering processes
Hardware segmentation
```
97
Abstraction
one of the fundamental principles behind objectoriented programming. It is the “black-box” doctrine that says that users of an object (or operating system component) don’t necessarily need to know the details of how the object works; they need to know just the proper syntax for using the object and the type of data that will be returned as a result
98
Separation of privilege
builds on the principle of least privilege. It requires the use of granular access permissions; that is, different permissions for each type of privileged operation. This allows designers to assign some processes rights to perform certain supervisory functions without granting them unrestricted access to the system.
99
Process isolation
requires that the operating system provide separate memory spaces for each process’s instructions and data. It also requires that the operating system enforce those boundaries, preventing one process from reading or writing data that belongs to another process.
- It prevents unauthorized data access. Process isolation is one of the fundamental requirements in a multilevel security mode system.
- It protects the integrity of processes.
100
Layering processes
you implement a structure similar to the ring model used for operating modes and apply it to each operating system process
101
Hardware segmentation
is similar to process isolation in purpose. Difference is that hardware segmentation enforces these requirements through the use of physical hardware controls rather than the logical process isolation controls imposed by an operating system.
102
Covert channels
Is a way to receive information in an unauthorized manner, information flood that is not protected by a security mechanism 2 types
Countermeasures: eal6 systems have less than eal3 systems because covert channels are normally a flaw in design.
103
Storage covert channel
processes communicate via storage space on the system
104
Covert timing channel
one process relays to another by modulating its use of system resources. Typing rhythm of Morse Code is an example
105
Mobile code
Java
| ActiveX
106
Java
sandboxes, no warnings, programs are compiled to bytecode
107
ActiveX
Authenticode, relies on digital signatures, annoying dialogs people click away
108
Virus
reproduces using a host application. It inserts or attaches itself to the file, spread thru infected media
109
Worm
reproduces on its own without host application
110
Logic Bomb/Code Bomb
executes when a certain event happens (like accessing a bank account or employee being fired) or a data/time occurs
111
Trojan Horse
program disguised as a useful program/tool
112
HOAXES
False warnings like: DON’T OPEN X SEND TO ALL YOUR COLLEGUES
113
RAT, Remote Access Trojan
remote control programs that have the malicious code and allow for unauthorized remote access Back orifice, sub seven, net bus )
114
Buffer Overflow
Excessive information provided to a memory buffer without appropriate bounds checking which can result in an elevation of privilege. If executable code is loaded into the overflow, it will be run as if it were the program. Buffer overflows can be detected by disassembling programs and looking at their operations. Buffer overflows must be corrected by the programmer or by directly patching system memory.
115
Trap Door
An undocumented access path through a system. This typically bypasses the normal security mechanisms and is to plant any of the malicious code forms
116
Backdoor
program installed by an attacker to enable him to come back on a later date without going through the proper authorization channels , maintenance hook for developers sometimes
117
Covert Channel
a way to receive information in an unauthorized manner. Information flood that is not protected by a security mechanism.
118
Covert Storage Channel
Writing to storage by one process and reading by another of lower security level.
119
Covert Timing Channel
One process relays to another by modulating its use of system resources.
120
LOKI
a tool used for covert channel that writes data directly after the ICMP header
121
Botnet
compromise thousands of systems with zombie codes can be used in DDOS attacks or spammers, send spam messages, conduct brute force attacks, scan for vulnerable systems
122
Directory Traversal Attack
attacker attempts to force the web application to navigate up the file hierarchy and retrieve a file that should not normally be provided to a web user
123
Macro Virus
Most common in office productivity documents .doc/.docx
124
MDM, Mobile device management
a software solution to manage the myriad mobile devices that employees use to access company resources. The goals of MDM are to improve security, provide monitoring, enable remote management, and support troubleshooting.
125
Collisions
two different files produce the same result from a hashing operation
126
Boot sector virus
moves or overwrites the boot sector with the virus code.
127
System infector virus
infects BIOS command other system files. It is often a memory resident virus
128
Phlashing virus
- a malicious variation of official BIOS or firmware is installed that introduces remote control or other malicious features into a device. UEFI – replacement for BIOS
129
Compression virus
appended to executables
130
Companion virus
A specific type of virus where the infected code is stored not in the host program, but in a separate ‘companion’ files. For example, the virus might rename the standard NOTEPAD.EXE file to NOTEPAD.EXD and create a new NOTEPAD.EXE containing the virus code. When the user subsequently runs the Notepad application, the virus will run first and then pass control to the original program, so the user doesn’t see anything suspicious. Takes advantage of search order of an OS
131
Stealth virus
hides modifications to files or boot records and itself
132
Multipart virus
infects both the boot sector and executable files; becomes resident first in memory and then infects the boot sector and finally the entire system, uses two or more propagation mechanisms
133
Self-garbling virus
attempts to hide by garbling its code; as it spreads, it changes the way its code is encoded
134
Polymorphic virus
this is also a self-garbling virus where the virus changes the "garble" pattern each time is spreads. As a result, it is also difficult to detect.
135
Macro virus
usually written in Word Basic, Visual Basic or VBScript and used with MS Office
136
Resident virus
Virus that loads when a program loads in memory
137
Master boot record /boot sector virus
- (MBR) virus attack the MBR— the portion of bootable media (such as a hard disk, USB drive, or CD/ DVD) that the computer uses to load the operating system during the boot process. Because the MBR is extremely small (usually 512 bytes), it can’t contain all the code required to implement the virus’s propagation and destructive functions. To bypass this space limitation, MBR viruses store the majority of their code on another portion of the storage media. When the system reads the infected MBR, the virus instructs it to read and execute the code stored in this alternate location, thereby loading the entire virus into memory and potentially triggering the delivery of the virus’s payload
138
Non-resident virus
attached to .exe
139
Signature based ANTI-Virus
cannot detect new malware
140
Heuristic ANTI-Virus
behavioral can detect new malware
141
Threats
Natural (Fires, explosions water, storm)
Man-made (bombing, strikes, toxin spills)
142
Protection domain
Execution and memory space assigned to each process
143
TRUSTED COMPUTER BASE
Combination of protection systems within a computer system, which include the hardware, software and firmware that are trusted to enforce the security policy.
144
Security Kernel
hardware, software, firmware, elements of TCB that implement the reference monitor concept — must be isolated from reference monitor (reference monitor: isolation, completeness and verifiability, that compares the security labels of subjects and objects)
145
Multistate systems
capable of implementing a much higher level of security. These systems are certified to handle multiple security levels simultaneously by using specialized mechanisms
146
Protection rings
(MIT’s MULTICS design) Ring 0 - Operating system kernel. The OS’ core. The kernel manages the HW (for example, processor cycles and memory) and supplies fundamental services that the HW does not provide.
Ring 1 - Remaining parts of the operating system Ring 2 - I/O drivers and utilities
Ring 3 - Applications and programs
Layers 1 and 2 contain device drivers but are not normally implemented in practice.
Layer 3 contains user applications.
Layer 4 does not exist.
147
CSRF (XSRF)
Cross site request forgery, attacks exploit the trust that sites have in a user’s browser by attempting to force the submission of authenticated request to third-party sites.
148
Cross-site Scripting
uses reflected input to trick a user’s browser into executing untrusted code from a trusted site
149
Session Hijacking
attempt to steal previously authenticated sessions but do not force the browser to submit request.
150
SQL Injection
directly attacks a database through a web app,, CARROT’1=1;-- quotation mark to escape out of input field
151
Blue Screen of Death
when a Windows system experiences a dangerous failure and enters a full secure state (reboot)
152
Hotfix, update, Security fix
– single patch, patches provide updates to operating systems and applications
153
Service Pack
collection of unrelated patches released in a large collection
154
Patch management system
prevents outages from known attacks by ensuring systems are patched. Patches aren’t available for new attacks. However, the patch management system doesn’t provide the updates. Ensuring systems are patched reduces vulnerabilities but it does not eliminate them
155
Code Review
peer-driven process that includes multiple developers, may be automated, may review several hundred lines of code an hour, done after code developed
156
Strong Passwords
social engineering best attack method to beat
157
Threat Modeling
reduce the number of security-related design and coding flaws, reduce severity of non-security related files, not to reduce number of threat vectors
158
Aggregate
summarize large amounts of data and provide only summary information as a result
159
Port Scan
attacking system sends connection attempts to the targets system against a series of commonly used ports
160
JavaScript
an interpreted language that does not make use of a complier to transform code into an executable state. Java, C, and C++ are all compiled languages
161
Open system
one with published APIs that allow third parties to develop products to interact with it
162
Closed system
one that is proprietary with no third-party product support, does not define if it’s code can be viewed
163
Open source
a coding stance that allows others to view the source code of a program, distributed free or for a fee
164
Closed source
an opposing coding stance that keeps source code confidential. can be reverse engineered or decompiled
165
API Keys
like passwords and should be treated as very sensitive information. They should always be stored in secure locations and transmitted only over encrypted communications channels. If someone gains access to your API key, they can interact with a web service as if they were you! Limit access to API
166
Nessus
a popular vulnerability scanner managed by Tenable Network Security, and it combines multiple techniques to detect a wide range of vulnerabilities. It uses port scans to detect open ports and identify the services and protocols that are likely running on these systems. Once Nessus discovers basic details about systems, it can then follow up with queries to test the systems for known vulnerabilities, such as if the system is up-to-date with current patches. Attacker can use to best identify vulnerabilities in a targeted syste
167
CASE
tool for development, if concerned about security
168
OWASP
Open Web Application Security Project, most authoritative source on web application security issues
169
Shadow Password File
- , /etc./ shadow. This file contains the true encrypted PWs of each user, but it is not accessible to anyone but the administrator. The publicly accessible /etc./ passwd file then simply contains a list of usernames without the data necessary to mount a dictionary attack. “x”
170
User Mode
processor mode used to run the system tools used by admins to make configuration changes to a machine
171
Kernel Mode
used by processor to execute instructions from OS
