DEV Flashcards
1
Q
set of best practices for programmers to seek in all application or database design: Atomicity, Consistency, Isolation, Durability
A
ACID test
2
Q
Authenticode, relies on digital signatures, annoying dialogs people click away
A
Active X
3
Q
a library of commands maintained by a system for other programs to use, provides consistency and integrity for the programs
A
Application Programming Interface
4
Q
is the tool that converts a high level language into machine language
A
Assembler
5
Q
Converts machine-code into binary machine instructions. Translate assembly language into machine language.
A
Assembler - DEV
6
Q
low-level programming language with a few simple operations this code is harder to maintain, less readable, and has the potential to be substantially longer
A
Assembly Code
7
Q
indivisible, data field must contain only one value that either all transactions take place or none do
A
Atomicity
8
Q
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
A
Backdoor
9
Q
Results exhibited by an object in response to a msg
A
Behavior
10
Q
Most significant byte is stored first. SPARC uses this architecture.
A
Big Endian
11
Q
When a Windows system experiences a dangerous failure and enters a full secure state (reboot)
A
Blue Screen of Death
12
Q
Moves or overwrites the boot sector with the virus code
A
Boot sector
13
Q
Attacks the MBR - the portion of bootable media that the computer uses to load the operating system during the boot process. MBR viruses store the majority of their code on another portion of the storage media
A
boot sector infector
14
Q
organized group of compromised computers
A
Botnet
15
Q
an area of memory allocated with a fixed size. It is commonly used as a temporary holding zone when data is transferred between two devices that are not operating at the same speed or workload.
A
Buffer
16
Q
Occurs when an area that has been allocated a specific storage space has more data copied to it than it can handle. Two classes include heap and stack overflow.
A
Buffer Overflow
17
Q
program code that is in between the high level language code understood by humans and machine code read by computers.
A
Byte Code
18
Q
An attribute that is a unique identifier within a given table, one is chosen to be the primary and the others are alternate. 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. Each table may have one or more, which are chosen from column headings.
A
Candidate Key
19
Q
Tool for development, if concerned about security
A
CASE
20
Q
a business managers and software engineer’s process to protect the organization from development-related issues. Has three components: Request, Change, and Release Control
A
Change Management Process
21
Q
part of a transaction control for a database which informs the database of the last recorded transaction
A
Checkpoint
22
Q
OOP concept of a template that consist of attributes and behaviors
A
Class
23
Q
converts source code to an executable
A
compiler
24
Q
Write code correctly first time, quality thru design
A
Cleanroom
25
Is an opposing coding stance that keeps source code confidential. Can be reverse engineered or decompiled
Closed source
26
Is one that is proprietary with no third-party product support, does not define if it's code can be viewed
Closed system
27
Peer-driven process that includes multiple developers, may be automated, may review several hundred lines an hour, done after it's developed
Code Review
28
Ability to perform without use of other programs, strength of the relationship between the purposes of methods within the same class
Cohesion
29
Support exchange of objects amongst programs. This used to be called OLE. DCOM is the network variant (distributed)
COM, Common Object Model
30
infected code is stored not in the host program, but in a separate files. Takes advantage of search order of an OS
Companion virus
31
converts source code to an executable
Compiler
32
Translates higher level program into an executable file
Complier - DEV
33
Appended to executables
Compression
34
Periodic, should be conducted to ensure that the actual production environment is consistent with the accounting records and that no unauthorized changes have taken place.
Configuration Audit
35
Ensures that changes to software versions are made in accordance with policies. Updates can be made only from authorized distributions in accordance with those policies.
Configuration Control
36
Administrators document covered software products throughout the organization.
Configuration Identification
37
Used to control the version( s) of software used throughout an organization and formally track and control changes
Configuration Management Process
38
property that data is represented in the same manner at all times
Consistency
39
Broker architecture enables programs written in different languages and using different platforms and OS’s through IDL (Interface Definition Language)
CORBA, Common object request
40
Effect on other modules. Level of interaction between objects
Coupling
41
Is a way to receive information in an unauthorized manner, information flood that is not protected by a security mechanism
Covert channels
42
Processes communicate via storage space on the system; Writing to storage by one process and reading by another of lower security level.
Covert Storage Channel
43
One process relays to another by modulating its use of system resources. Typing rhythm of Morse Code is an example
Covert timing channel
44
malware that uses the trust on a website to redirect users to untrusted websites which captures data or installs more malware
Cross Site Scripting
45
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.
CSRF (XSRF)
Cross Site Request Forgery
46
false memory reference
Dangling pointer
47
a description of a database
Data Dictionary
48
malware that makes small random changes to many data points
Data Diddler
49
a feature of object oriented programming languages. Classes and variables may be marked private, which restricts outside access to the internal workings of a class.
Data Hiding
50
small data warehouse
Data marts
51
specifies the way data will be stored in memory
Data Type
52
z-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
Database Contamination
53
Process of splitting a single database into multiple parts, each with a unique and distinct security level or type of content
Database Partitioning
54
a copy of transaction data, designed for querying and reporting
Data warehouse
55
a collection of information designed to reduce duplication and increase integrity
Databases
56
Schemas, blueprints; tables, views
DB main components
57
Refers to a suite of software programs that maintains and provides controlled access to data components stored in rows and columns of a table
DBMS
58
subset of SQL used to control access to data in a database, using GRANT and REVOKE statements
DCL - Data Control Language
59
enables applications to work in a client/server model by providing the inter-process communications mechanism (IPC)
DDE - Dynamic Data Exchange
60
defines structure and schema
DDL - Data Definition Language
61
a condition in which neither party is willing to stop their activity for the other to complete
Deadlock
62
Forwarding a request to another object
Delegation
63
an availability attack, to consume resources to the point of exhaustion
Denial of Service
64
a combination of Development and Operations, symbolizing that these functions must merge and cooperate to meet business requirements
DevOps
65
Attempt 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
Directory Traversal Attack
66
When one transaction reads a value from a Db that was written by another transaction that did not commit, Db concurrency issue
Dirty Reads
67
software tool is used to convert compiled programs in machine code to assembly code
Disassembler
68
an availability attack, to consume resources to the point of exhaustion from multiple vectors
Distributed Denial of Service
69
view, control and use the database via VIEW, ADD, MODIFY, SORT and DELETE commands
DML - Data Manipulation Language
70
what is will remain, persistence
Durability
71
Created on the fly by software in an Object Oriented Programming environment. Preassembled code that is a self-contained module
Dynamic Lifetime Objects
72
a programming component that runs on Win32 systems and contains functionality that is used by many other programs
DLL - Dynamic Link Library
73
a feature of object-oriented programming, provides a logical structure to a program and allows for easy methods of inheritance
Encapsulation
74
Seek to embody accumulated knowledge on a particular subject and apply it in a consistent fashion to future decisions. Has two main components: the knowledge base and the inference engine.
Expert Systems
75
causes a software vulnerability to be triggered and leveraged by the attacker
Exploit
76
Allow programmers to create code using visual interfaces
Fifth-Generation Languages (5GL)
77
Include all machine languages
First-Generation Languages (1GL)
78
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 Main Components of a Db using Db - Schemas; blueprints - tables - views
Foreign Key
79
Attempt to approximate natural languages and include SQL, which is used by databases
Fourth-Generation Languages (4GL)
80
a miniature program
Function
81
Define need, requirements, review proposed security controls
Functional Analysis and Planning
82
Bar type; shows the interrelationships over time between projects and schedules. Graphical illustration of a schedule that helps plan, coordinate, and track specific project tasks. WBS a subpart
Gantt Chart
83
Is similar to process isolation in purpose. Difference is this enforces these requirements through the use of physical hardware controls rather than the logical process isolation controls imposed by an operating system
Hardware segmentation
84
an area of memory utilized by an application and is allocated dynamically at runtime. Static variables are stored on the stack along with data allocated using the malloc interface.
Heap
85
Behavioral can detect new malware
Heuristic ANTI-Virus
86
Module largely affects many more modules
High coupling
87
False warnings
HOAXES
88
Single patch, patches provide updates to operating systems and applications
Hotfix, update, Security fix
89
uncheck data input which results in redirection
HTTP Response Splitting
90
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 incorrect information
Incorrect Summaries
91
to jump to a conclusion
Inference
92
object-oriented organization and encapsulation allow programmers to easily reuse previously written code. It saves time since programmers do not have to recode previously implemented functionality.
Inheritance
93
OOP concept of an object at runtime
Instance
94
in the case of unsigned values, this occurs when an overly large unsigned value is sent to an application that "passes" the integer back to zero or a small number
Integer Wrapping
95
line by line translation from a high level language to machine code
Interpreter
96
Reads higher level code, one line at the time to produce machine instructions
Interpreter - DEV
97
another subject cannot see an ongoing or pending update until it is complete
Isolation
98
modern, object oriented programming language. It combines a similar syntax to C and C++ with features such as platform independence and automatic garbage collection.
Java
99
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
JavaScript
100
Used by processor to execute instructions from OS
Kernel Mode
101
Implement a structure similar to the ring model used for operating modes and apply it to each operating system process
Layering processes
102
the least significant byte is stored first
Little Endian
103
a program that waits for a condition or time to occur that executes an inappropriate activity
Logic bomb
104
Executes when a certain event happens (like accessing a bank account or employee being fired) or a data/time occurs
Logic Bomb/Code Bomb
105
Tool used for covert channel that writes data directly after the ICMP header
LOKI
106
When one transaction writes a value to the Db that overwrites a value needed by transactions that have earlier precedence
Lost Updates
107
the hardware address of a particular computer system
MAC
108
program instructions based upon the CPU’s specific architecture
Machine language
109
Most common in office productivity documents .doc/.docx
Macro Virus
110
inappropriate data
Malformed input
111
a function call dynamically allocates n number of bytes on the heap. Many vulnerabilities are associated with the way this data is handled.
malloc
112
Bombing, strikes, toxin spills
Man-made Threats
113
Software solution to manage the myriad mobile devices that employees use to access company resources. Goals are to improve security, provide monitoring, enable remote management, and support troubleshooting
MDM - Mobile device management
114
a function call is used to fill a heap buffer with a specified number of bytes of a certain character
Memset
115
Communication to object to perform an action
Message
116
information about data or records
Metadata
117
another name for a function in languages such as Java and C#. It may be thought of as a miniature program.
Method
118
Essential to keep data with different requirements separate
Multilevel Security
119
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
Multipart virus
120
Class inherits characteristics from more than one parent class
Multiple Inheritance
121
Capable of implementing a much higher level of security. These systems are certified to handle multiple security levels simultaneously by using specialized mechanisms
Multistate systems
122
Fires, explosions, water, storms
Natural Threats
123
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 it 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 system
Nessus
124
Use complex computations to replace partial functions of the human mind, Based on function of biologic neurons, Works with weighted inputs
Neural Networks
125
Attached to .exe
Non-resident virus
126
a term used to describe a programming variable which has not had a value set, this value is not necessarily the same as a value of “” or 0.
NULL
127
design philosophy and a type of programming language, which breaks a program into smaller units. Each unit has it’s own function.
Object Oriented Programming
128
unclear buffers or media
Object reuse
129
programs are organized into classes. Instances of classes contain data and methods which performs actions on that data.
Object-oriented
130
feature that allows applications to communicate with different types of databases without having to be directly programmed for interaction with each type. Acts as a proxy
ODBC - Open Database Connectivity
131
a bug is present when a buffer is set up with size n and somewhere in the application a function attempts to write n+1 bytes to the buffer. This often occurs with static buffers.
Off-by-one
132
Objects are the basic units, and instances of classes
OOD, Design
133
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
OOP, Programming
134
Is a coding stance that allows others to view the source code of a program, distributed free or for a fee
Open source
135
Is one with published APIs that allow third parties to develop products to interact with it
Open system
136
Release into production. Certification/accreditation
Operations and Maintenance
137
Middleware that acts as locators and distributors of the objects across networks
ORBs, Object Request Brokers
138
business and technical process of applying security software updates in a regulated periodic way
Patch Management
139
Prevents outages from known attacks by ensuring systems are patched. Patches aren’t available for new attacks. However, it doesn’t provide the updates. Ensuring systems are patched reduces vulnerabilities but it does not eliminate them
Patch Management system
140
final purpose or result
Payload
141
project-scheduling tool used to judge the size of a software product in development and calculate the standard deviation (SD) for risk assessment. Relates the estimated lowest possible size, the most likely size, and the highest possible size of each component. Used to direct improvements in project management and software coding to produce more efficient software
PERT - Program Evaluation Review Technique
142
Malicious variation of official BIOS or firmware is installed that introduces remote control or other malicious features into a device. UEFI – replacement for BIOS
Phlashing
143
idea that program code can run on different systems without modification or recompilation
Platform Independence
144
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
PolyInstantiation
145
This is also a self-garbling where it changes the “garble” pattern each time it spreads. As a result, it is also difficult to detect
Polymorphic virus
146
objects or programming that looks different, but act the same. More accurately: 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
Polymorphism
147
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
Primary Key
148
LIBC function for outputting data to a command-line interface
Printf
149
may be viewed as a sequence of instructions, where data at certain memory locations are modified at each step
Procedural Language Programs
150
collection of commands that are understood by a computer system and may be written in a high-level language, such as Java or C, or in a low-level assembly language
Program
151
Feasibility, cost, risk analysis, Management approval, basic security objectives
Project Initiation
152
Execution and memory space assigned to each process
Protection domain
153
(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
Protection Rings
154
a state where two subjects can access the same object without proper mediation
Race condition
155
Extortion via the internet, typically encrypting victim’s data and files
ransomeware
156
Remote control programs that have the malicious code and allow for unauthorized remote access Back orifice, sub seven, net bus )
RAT, Remote Access Trojan
157
All foreign keys reference existing primary keys
Referential Integrity
158
an area on the processor used to store information. Intel architecture: eax, ebx, ecx, edx, esi, and edi.
Register
159
Once the changes are finalized, they must be approved through procedure
Release Control
160
Provides an organized framework within which users can request modifications, managers can conduct cost/ benefit analysis, and developers can prioritize tasks
Request Control
161
Loads when a program loads in memory
Resident virus
162
Remove. Sanitation and destruction of unneeded data
Revisions/Disposal
163
transaction controls for a database, a return to a previous state
Rollback
164
malware that subverts the detective controls of an operating system
Rootkit
165
malware that makes many small changes over time to a single data point or system
Salami
166
a construct used to control code execution. Code executed cannot affect outside systems. This is particularly useful for security when a user needs to run mobile code, such as Java applets.
Sandbox
167
Include all assembly languages
Second-generation language (2GL)
168
Attempts to hide by garbling its code; as it spreads, it changes the way its code is encoded
Self-garbling virus
169
Make sure that rules are enforced on all data types, logical values that could adversely affect the structure of the database
Semantic Integrity
170
Builds on the principle of least privilege. 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
Separation of privilege
171
Collection of unrelated patches released in a large collection
Service Pack
172
used by devices to communicate with software. It is normally written by the manufacturer of a hardware device to communicate with the operating system.
Service Provider Interface
173
byte code that executes a shell or the code that is executed when an exploit is successful
Shellcode
174
Cannot detect new malware
Signature based ANTI-Virus
175
Assumed each step could be completed and finalized without any effect from the later stages that may require rework
Simplistic Model
176
unused storage capacity
Slack space
177
Quality is a direct function of quality of development and maintenance.
Procedures, principles, and practices that underlie development process maturity. 5 Levels:
initiating – competent people, informal processes, ad-hoc, absence of formal process
repeatable – project management processes, basic life-cycle management processes
defined – engineering processes, presence of basic life-cycle 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
Software Capability Maturity Model (CMM)
178
Programmers create code. Unit testing Check modules. Prototyping, Verification, Validation
Software Development
179
a design methodology which addresses risks early and often
Spiral
180
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
Spiral Model
181
program that inappropriately collects private data or activity
Spyware
182
a type of malformed input that takes advantage of an appropriate true conditional logic statement adding a request for data that is against the security policy
SQL Injection
183
an area of memory used to hold temporary data. It grows and shrinks throughout the duration of a program’s runtime.
Stack
184
occurs when a buffer has been overrun in the stack space. When this happens, the return address is overwritten, allowing for arbitrary code to be executed.
Stack Overflow
185
Hides modifications to files or boot records and itself
Stealth virus
186
LIBC function call is more commonly misimplemented because it copies data from one buffer to another without any size limitation
strcpy
187
Social engineering best attack method to beat
Strong Passwords
188
Database systems commands used to create, access, and modify data
SQL - Structured Query Language
189
Develop detailed design specs, Review support documentation, Examine security controls
System Design Specifications
190
Contaminates BIOS command other system files. It is often a memory resident virus
System infector
191
project management process with following phases: design and development, production, distribution, operation, maintenance, retirement, and disposal
System Life Cycle
192
include all compiled languages
Third-Generation Languages (3GL)
193
Reduce the number of security-related design and coding flaws, reduce severity of non-security related files, not to reduce number of threat vectors
Threat Modeling
194
a race condition where the security changes during the object’s access
Time of Check/Time of Use
195
(Backdoors) (maintenance hooks) a programming device used in development to circumvent controls.
Trapdoors
196
a program with an inappropriate second purpose
Trojan horse
197
Pretend to do one thing while performing another
Trojans
198
Row or record
Tuple
199
a software simulation of a platform that can execute code. It allows code to execute without being tailored to the specific hardware processor.
Virtual Machine
200
independent malware that requires user interaction to execute
Virus
201
an exposure that has the potential to be exploited. Most are specific software bugs or logic errors.
Vulnerability
202
Reinterpretation 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
Waterfall including Validation and Verification (V&V)
203
a design methodology which executes in a linear one way fashion
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
Waterfall
204
autonomous malware that requires a flaw in a service
Worm
205
a family of computer architectures commonly associated with Intel
x86
206
meant to describe an exploit that has been released on or before the corresponding vulnerability has been publicly released
0day
207
a distributed system’s transaction control that requires updates to complete or rollback
2-phase commit
208
a fundamental principle behind object-oriented programming, users of an object only need to know the proper syntax for using an object and the type of data that will be returned as a result
Abstraction
209
Separation of duties, security testing, data validation, bounds checking, certification, accreditation, part of release control
Acceptance Testing and Implementation
210
unsolicited advertising software
Adware
211
Summarize large amounts of data and provide only summary information as a result
Aggregate
212
Emphasis on customer needs for new functionality that quickly 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
Agile Software Development
213
a covert storage channel on the file attribute, also File system forks
Alternate Data Streams
214
a unique identifier and a secret token for authentication, generally have a set of access rights on the API associated with it
API Keys
215
Initiation
Development/Acquisition
Implementation/Assessment
Operations and Maintenance
Disposal
800-64
216
I Plan and Set Projects to Categorize Information Systems And Assess Engineering
Initiate Project - Security Planning
Categorize Information System
Assess Business Impact
Assess Privacy Impact
Ensure Secure System Development
800-64 Initiation
217
Outputs - Supporting Documents, Common Understanding of Security Expectations, Initial Schedule of Security Activities or Decisions
Initiate Project - Security Planning
218
Outputs - Security Categorization, High-Level Security Requirements, Level of Effort or Rigor Estimates
Categorize Information System
219
Outputs - Linkage to Business Drivers, Core System Components, Initial Recovery Time and Point Objectives
Assess Business Impact
220
Output - Privacy Impact Assessment
Assess Privacy Impact
221
Outputs - Security Training for Development Team, Quality Assurance Plans, Development and Coding Standards
Ensure Secure System Development
222
Doctor’s Assistant’S SCissoRs needed for Preparation of Surgery Room which is FAR from Rest Medical Room
Determine Acquisition Strategy
System Concept Review
Performance Specification Review
Financial Approval or Review
Risk Management Review
800-64 Initiation Phase Control Gates
223
ARchitect designS
inSpector Documents Silly Codes
interior Designer Selects Artwork
Environment Is not Safe in DC
so Determine Security Domains
and ConTinue building
Assess Risk to System
Select and Document Security Controls
Design Security Architecture
Engineer in Security and Develop Controls
Develop Security Documentation
Conduct Testing
800-64 Development/Acquisition
224
Outputs - Risk Assessment
Assess Risk to System
225
Outputs - System Security Plan
Select and Document Security Controls
226
Outputs - List of Shared Services and Shared Risk, Schematic of Security Integration, Identification of Common Controls
Design Security Architecture
227
Outputs - Documented in Place Security Control Specification, List of Variations from Plan, Potential Test Scenarios
Engineer in Security and Develop Controls
228
Output - Additional Security Documentation
Develop Security Documentation
229
Output - Test Results and Implications
Conduct Testing
230
Agent of Dteam Reads Player’s Rating For TomoRrow Rowing Match Race
Architecture or Design Review
Performance Review
Functional Test Review
Risk Management Review
800-64 Development/Acquisition Phase Control Gates
231
IS Enterprise or Starship ASSimilated
Integrate Security into Environments or Systems
Access System Security
800-64 Implementation/Assessment
232
Outputs - Verified List of Operational Security Controls, Completed System Documentation
Integrate Security into Environments or Systems
233
Outputs - Security Assessment Report, Input for POA&M
Access System Security
234
Some Tablets are Ready for Roaming like
anDRRoid
Finish Please Soon and Fund Riches so
I can Travel to Delaware or CAlifornia
System Test Readiness Review
Deployment Readiness Review
Final Project Status and Financial Review
IT Deployment or Connection Approval
800-64 Implementation/Assessment Phase Control Gates
235
Review OR Pass Configuration to Management Committee in CC e-Mail
Review Operational Readiness
Perform Configuration Management and Control
Conduct Continuous Monitoring
800-64 Operations and Maintenance
236
Output - Evaluation of Security Implications due to Changes
Review Operational Readiness
237
Outputs - CCB Decisions, Updated Security Documentation, Security Evaluations
Perform Configuration Management and Control
238
Outputs - POA&M Review, Documented Results of Continuous Monitoring, Revised Security Authorization Package, Security Reauthorization Decision
Conduct Continuous Monitoring
239
Operational Readiness Review for
Change Control Board to conduct
Plan Of Actions and Milestones Review to determine Authorization Decision
Operational Readiness Review
Change Control Board
POA&M Review
Authorization Decision
800-64 Operations and Maintenance Phase Control Gates
240
BE Determined Troll
even though you are SMall
Ensure IP for DHS and CS
Build and Execute Disposal or Transition Plan
Sanitize Media
Ensure Information Preservation
Dispose of Hardware and Software
Close System
800-64 Disposal
241
Output - Disposal/Transition Plan
Build and Execute Disposal or Transition Plan
242
Output - Media Sanitization Records
Sanitize Media
243
Outputs - Index of Information, Location, Retention Attributes
Ensure Information Preservation
244
Disposition Records for Hardware and Software
800-64 Dispose of Hardware and Software
245
Documentation Verifying System Closure
Close System
246
Some Clean Rooms for
Clowns, CowBoys are
Sure to be Ready for their Coming
System Closure Review
Change Control Board
Security Review of Closure
800-64 Disposal Phase Control Gates
247
System Security Engineering
800-160 SSE
248
System Life Cycle Processes
Agreement Processes
Organizational Project-Enabling Processes
Technical Management Processes
Technical Processes
249
Agreement Processes
Acquisition
Supply
250
Organizational Project-Enabling Processes
our prince Leaves Monarchy In Frustration.
Please May Harry Ride Quickly Maybe Kissing Meghan.
LM Life Cycle Model Management
IF Infrastructure Management
PM Portfolio Management
HR Human Resource Management
QM Quality Management
KM Knowledge Management
251
Technical Management Processes
Tech Managers Configure and PRIMP for Dairy Queen
CM Configuration Management
PL Project Planning
RM Risk Management
IM Information Management
MS Measurement
PA Project Assessment and Control
DM Decision Management
QA Quality Assurance
252
Technical Processes
BAss SNeaks SR ARound
DEan SAys IP INsults
VEry TRicky VAlues OPen MAd DShield
Business or mission analysis (BA)
Stakeholders needs and requirements (SN)
System requirements definition (SR)
Architecture definition (AR)
Design definition (DE)
System Analysis (SA)
Implementation (IP)
Integration (IN)
Verification (VE)
Transition (TR)
Validation (VA)
Operation (OP)
Maintenance (MA)
Disposal (DS)
253
Security Design Principles
Security Architecture and Design
Security Capability and Intrinsic Behavior
Life Cycle Security
254
Security Architecture and Design
Clear Abstractions
Hierarchical Trust
Least Common Mechanisms
Inverse Modification Threshold
Modularity and Layering
Hierarchical Protection
Partially Ordered Dependencies
Minimized Security Elements
Efficiently Mediated Access
Least Privilege
Minimized Sharing
Predicate Permission
Reduced Complexity
Self-Reliant Trustworthiness
Secure Evolvability
Secure Distributed Composition
Trusted Components
Trusted Communication Channels
255
Security Capability and Intrinsic Behavior
Continuous Protection
Secure Failure and Recovery
Secure Metadata Management
Economic Security
Self-Analysis
Performance Security
Accountability and Traceability
Human Factored Security
Secure Defaults
Acceptable Security
256
Life Cycle Security
Repeatable and Documented Procedures
Secure System Modification
Procedural Rigor
Sufficient Documentation
257
Identify
Develop viewpoints
Harmonize models, views, and secure function
Relate views to design
Select
Manage
ARchitecture definition
258
Prepare
Establish characteristics for system element
Assess alternatives
DEsign definition
259
Identify problem that requires analysis
Identify and validate assumptions of analysis
Record results of analysis
System Analysis
260
Build or adapt system elements
Develop training materials
Record results and any anomalies
Maintain traceability
Implementation
261
Identify training
Demonstrate achievement of security aspects
Commission for operation
Record security aspects of transition and anomalies encountered
Transition
262
Define maintenance strategy
Review incident reports to identify maintenance needs
Implement restoration after failure
Identify when maintenance is required
Perform logistics support
Manage maintenance and logistics
MAintenance
263
Initiation - Stakeholders Needs, Verification
Development/Acquisition - Architecture, Design, Verification
Implementation/Assessment - System Analysis, Implementation
Operations/Maintenance - Transition, Maintenance
800-64 to 800-160 map
264
A1
Injection flaws, such as SQL, NoSQL, OS, and LDAP injection, occur when untrusted data is sent
to an interpreter as part of a command or query. The attacker’s hostile data can trick the
interpreter into executing unintended commands or accessing data without proper authorization.
Controls: Parameterize queries, Validate all inputs
Threat Injection
265
A2
Application functions related to authentication and session management are often implemented
incorrectly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit
other implementation flaws to assume other users’ identities temporarily or permanently.
Controls: Implement identity and authentication controls
Threat Broken Authentication
266
A3
Many web applications and APIs do not properly protect sensitive data, such as financial,
healthcare, and PII. Attackers may steal or modify such weakly protected data to conduct credit
card fraud, identity theft, or other crimes. Sensitive data may be compromised without extra
protection, such as encryption at rest or in transit, and requires special precautions when
exchanged with the browser.
Controls: Implement appropriate access controls, Protect data, Encryption protection of sensitive data, Error and exception handling
Threat Sensitive Data Exposure
267
A4
Many older or poorly configured XML processors evaluate external entity references within XML
documents. External entities can be used to disclose internal files using the file URI handler,
internal file shares, internal port scanning, remote code execution, and denial of service attacks.
Controls: Validate all inputs
Threat XML External Entities (XXE)
268
A5
Restrictions on what authenticated users are allowed to do are often not properly enforced.
Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access
other users’ accounts, view sensitive files, modify other users’ data, change access rights, etc.
Controls: Enforce access controls
Threat Broken Access Control
269
A6
Security misconfiguration is the most commonly seen issue. This is commonly a result of insecure
default configurations, incomplete or ad hoc configurations, open cloud storage, misconfigured
HTTP headers, and verbose error messages containing sensitive information. Not only must all
operating systems, frameworks, libraries, and applications be securely configured, but they must
be patched and upgraded in a timely fashion.
Controls: Web server configuration hardening
Threat Security Misconfiguration
270
A7
XSS flaws occur whenever an application includes untrusted data in a new web page without
proper validation or escaping, or updates an existing web page with user-supplied data using a
browser API that can create HTML or JavaScript. XSS allows attackers to execute scripts in the
victim’s browser which can hijack user sessions, deface web sites, or redirect the user to
malicious sites.
Controls: Encode data
Threat Cross Site Scripting (XSS)
271
A8
Insecure deserialization often leads to remote code execution. Even if deserialization flaws do not
result in remote code execution, they can be used to perform attacks, including replay attacks,
injection attacks, and privilege escalation attacks.
Controls: Verify for security early and often
Threat Insecure Deserialization
272
A9
Components, such as libraries, frameworks, and other software modules, run with the same
privileges as the application. If a vulnerable component is exploited, such an attack can facilitate
serious data loss or server takeover. Applications and APIs using components with known
vulnerabilities may undermine application defenses and enable various attacks and impacts.
Controls: Take advantage of security frameworks and libraries
Threat Using Components with Known Vulnerabilities
273
A10
Insufficient logging and monitoring, coupled with missing or ineffective integration with incident
response, allows attackers to further attack systems, maintain persistence, pivot to more systems,
and tamper, extract, or destroy data. Most breach studies show time to detect a breach is over
200 days, typically detected by external parties rather than internal processes or monitoring.
Controls: Error and exception handling, Implement logging and intrusion detection
Threat Insufficient Logging and Monitoring
274
Software configuration management (SCM) should primarily address which of the following questions?
What constitutes a software product at any point in time?
275
The security-planning document developed in the development/acquisition phase of a system development life cycle contains what?
Configuration management plan
Contingency plan
Incident response plan
Plan of actions and milestones
System interconnection agreements
Security tests and evaluation results
Rules of behavior
Risk assessment
Security awareness and training plan
276
Boundary-value analysis is conducted in which of the following phases of a system development life cycle (SDLC)?
Implementation
277
Which of the following application settings used to prevent malware incidents will help stop phishing and spyware delivery?
Blocking Web browser pop-up windows
Filtering spam
Filtering website content
278
In a distributed computing environment, replicated servers could have negative impact on what?
Scalability
279
Which of the following security principle balances various variables such as cost, benefit, effort, value, time, tools, techniques, gain, loss, risks, and opportunities involved in a successful compromise of security features?
Work factor
280
Which of the following is similar to security certification and accreditation?
Quality control
281
What is true when dealing with security principles for securing an application environment?
Data-hiding techniques should be practiced during program testing and software maintenance.
Design for protection mechanisms should be simple and small in size.
Information security functions should be isolated from non-security functions.
282
Big bang software application testing approach
a testing approach where all the individual components or modules of a software application are tested together, often in a single, comprehensive testing phase. Unlike other testing methods that involve incremental integration and testing of components, Big Bang Testing focuses on evaluating the entire system’s functionality as a whole.
This approach is typically employed after the individual units or modules have undergone unit testing. Once these units are ready for integration, they are combined in a “big bang,” and testing is carried out on the complete system.
283
Finite State Machines are used in what phase?
Initiation
