Domain 2 - Security Operations Flashcards
1
Q
What is a baseline?
A
A detailed configuration standard that includes specific security settings.
2
Q
Some examples of Security Guidelines?
A
- Method for selecting a strong password.
- criteria for evaluating new security technology
- Suggest training curricula for staff.
3
Q
What is a standard?
A
A formal, documented requirement that set uniform criteria for a specific technology, configuration, nomenclature, or method.
4
Q
What helps organizations help maintain consistency in the way security risks are addressed?
A
Standards, baselines, procedures, and even guidelines.
5
Q
What is a procedure?
A
Step-by-step instructions for performing a specific task or set of tasks.
6
Q
What are the typical components of a procedure?
A
Purpose Applicability Steps Figures Decision Points
7
Q
What is release management?
A
A software engineering discipline that controls the release of applications, updates, and patches to the production environment.
8
Q
What is the goal of release management?
A
To provide assurance that only tested and approved application code is promoted to production or distributed for use.
9
Q
Code Signing?
A
Assists users in validating that the application was issued by a trust source.
Typically used for web apps running Java or ActiveX
10
Q
Smoke Tested?
A
High-level, scripted testing of the major application components and interfaces to validate the integrity of the application before making it available.
11
Q
Systems Assurance?
A
Process of validating that existing security controls are configured and functioning as expected.
12
Q
Change Control?
A
Process adopted by an organization to ensure that all changes to system and application software are subject to the appropriate level of management control.
13
Q
Change Control Process?
A
Request Submission Recording Analysis/Impact Assessment Decision Making and Prioritization Approval Status Tracking
14
Q
CM
A
CONFIGURATION MANAGEMENT
Discipline that seeks to manage configuration changes so that they are appropriately approved and documented.
“Technical and Administrative’ Process
15
Q
Typical Steps in the configuration management process.
A
Change Request Approval Documentation Testing Implementation Reporting
16
Q
Four Operational Aspects of CM
A
Identification
Control
Accounting
Auditing
17
Q
CMBD
A
CONFIGURATION MANAGEMENT DATABASE
Holds information about the structure of the system.
18
Q
CI
A
CONFIGURATION ITEM
Component of each system listed in the CMBD using a name, number, and version ID.
19
Q
Security Impact Assessment
A
Analysis conducted by qualified staff within an organization to determine the extent to which changes to the information system affect the security posture of the system.
20
Q
Interoperability
A
Describe the extent to which systems and devices can exchange data and interpret that shared data.
21
Q
Syntactical Interoperability
A
Two or more systems that are capable of communicating and exchanging data.
22
Q
Patch Management Process
A
- Acquisition - Find Patch
- Testing - Test Patch before installation
- Approval - Approve for deployment
- Packaging - Package or configure for OS.
- Deployment
- Verification
23
Q
SSCP Domains
A
Access Controls Analysis and Monitoring Cryptography Malicious Code Networks & Telecom Risk, Response, & Recovery Security operations and administration
24
Q
BMS
A
BALANCED MAGNETIC STRIP
Device that uses a magnetic strip to determine if an alarm signal is initiated.
25
PIR
PASSIVE INFRARED SENSORS
Common interior intrusion detection sensors.
ex. Occ Sensor
26
Electric Locks vs Electric Strikes
Electric Locks use the doors physical locks.
Electric Strikes - bolts remains the same, but strike is changed.
27
Anti-Passback
Strategy where a person must present a credential to enter an area and again to leave.
28
'Mantrap"
When a person opens a door, and for the next door to open, the one just enter must securely close.
29
Rim Lock
Lock (or latch) typically mounted on the surface of a door.
Ex - dead bolt
30
Mortise Lock
Lock (or latch) that is recessed into the edge of a door rather than on the surface.
Ex - Handle + Lock in single package.
31
Locking Cylinders
Pin Tumbler cylinder is composed of circular pin tumblers that fit into matching circular holes on two internal parts of the lock.
32
Cipher Lock
Controlled by a mechanical key pad.
Think of front door handle with PIN pad on it.
33
Vaults - Class M
One 1/4 hour
34
Vaults - Class 1
One 1/2 hour
35
Vaults - Class 2
One hour
36
Vaults - Class 3
Two hours
37
Classified Container
Reinforced Filing Cabinet that can store proprietary and sensitive information.
38
Cable Plant Management
Design, Documentation, and management of layer 1 in the OSI model, the Physical Layer.
39
MTBF
MEAN TIME BEFORE FAILURE
40
Two-Person Rule
Strategy where two people must be in an area together, making it impossible for a person to be in the area alone.
41
Two main categories of smoke detectors
1. Optical (Photoelectric)
| 2. Physical (Ionization)
42
Three Types of Fire Detectors
1. Flame Detectors
2. Smoke Detectors
3. Heat Detectors
43
Two Types of Flame Detectors
1. IR
| 2. UV
44
Four Groups of Sprinkler Systems
1. Wet Systems - Constant supply of water
2. Dry Systems - Releases when value is stimulated by excess heat.
3. Pre-Action - No water until detectors in the area are activated. Removes 'False Alarms'.
4. Deluge - Same as pre-action, but all sprinkler heads are in the open position.
45
2 Types of Gas Suppression
1. Aero-K: Uses aerosol of potassium
| 2. FM-200: Colorless, liquefied compressed gas.
46
6 Aspects in the Change Control Policy Document
1. Request Submission
2. Recording
3. Analysis/Impact Assessment
4. Decision Making & Prioritization
5. Approval
6. Status Tracking
47
Operational Aspects of CM?
Identification, Control, Accounting, Auditing
48
Systems Certification Process?
Method of validating adherence to security requirements.
49
Dual Control
Antifraud measure that requires two people to complete a transaction.
50
Waterfall Model
Development method that follows a linear sequence of steps.
51
What two things are used to accomplish non-repudiation?
Digital Signatures
| Public Key Infrastructure
52
What are the elements that make up IS risks?
Threat, Vulnerability, Impact
Risk = Threat + Vulnerability + Impact
53
Remote Attestation
Form of integrity protection that makes use of a hashed copy of hardware and software configuration to verify that configurations have not been altered.
54
4 Tenets of the Code of Ethics
1. Protect Society, commonwealth, and infrastructure
2. Act honorably
3. Provide Diligent service to principals
4. Advance/Protect Profession
55
Confidentiality
Property of information in which it is only made available to those who have a legitimate need to know.
56
Integrity
Property of information whereby it is recorded, used, and maintained in a way that ensures its accuracy.
57
RAID
REDUNDANT ARRAY OF INDEPENDENT DISKS
ex. Controllers, UPS, Backup and recovery
58
Non-repudiation
Service that ensures the sender cannot deny a message was sent and the integrity of the message is intact.
59
(ISC)2 Code of Ethics
1. Protect Society, commonwealth, and infrastructure
2. Act honorably, honestly, justly, responsibly, and legally. 3. Provide diligent and competent service to principals 4. Advance and protect the profession.
60
Donn Parker's 5 Ethical Principles
1. Informed Consent
2. Higher ethic in the worst case
3. Change of Scale Test
4. Owner's conservation of ownership
5. , User's conservation of ownership
61
C-I-A Triad
Confidentiality
Integrity
Availability
62
Confidentiality
Property of information in which it is only made available to those who have a legitimate need to know.
63
Methods for Maintaining a level of Confidentiality
Authorization
Identity
Access Management Encryption and Disclosure controls
64
DLP
Data Leakage Prevention
65
Integrity
Property of information whereby it is recorded, used, and maintained in a way that ensures it's completeness, accuracy, internal consistency, and usefulness for a stated purpose.
66
Systems Integrity
Maintenance of a known good configuration and expected operational function.
67
Sarbanes-Oxley Act of 200
Mandates certain controls over the integrity of financial reporting.
68
SLA
Service Level Agreement
Specify percentage of uptime as well as support procedures and communication for planned outages.
69
RTO
Recovery Time Objectives Specify the acceptable duration of an unplanned outage due to catastrophic system non-availability.
70
Non-repudiation
Service that ensures the sender cannot deny a message was sent and the integrity of the message is intact.
71
Security Architecture
The practice of designing a framework for the structure and function of information security systems and practices in the organization.
72
Essential Best Practices Include:
```
Defense-in-depth
Risk-based controls
Least Privilege
Authorization
Accountability
Separation of Duties
```
73
Calculate Risk Equation
IMPACT + VULNERABILITY + THREAT = RISK
74
LUA
"Least User Access "
"Least Privilege"
75
Difference Categories of Controls
1. Management - Controls concerning risk (Policy and Procedures)
2. Technical - Executed in hardware,software, and firmware.
3. Operational - Primarily implemented and executed by people.
76
NIST SP 800-88
NIST Matrix for Determining Requirements for Clearing and Sanitizing Media
77
Oersteds
Unit of measurement for the intensity of the magnetic energy a disk or tape can store.
78
Degaussing
A technique of erasing data on disk or tape that ensures that there is insufficient magnetic remanances to reconstruct data.
79
IRM
Information Rights Management
Functions to assign specific properties to an object such as how long the object may exist, what users can access it, and if any notifications should be sent if any changes occur.
80
Data Scrubbing
aka Data Sanitization
Obfuscate sensitive data in such a way that the actual data values cannot be deduced or derived from the sanitized data itself.
81
DeDupication
Process that scans the entire collection of information looking for similar chucks of data that can be consolidated.
82
ITAM
IT Asset Management
Entails collecting inventory, financial, and contractual data to manage the IT Asset throughout its life cycle.
83
Session Management
Includes timing out inactive sessions, deleting session information after timeout, not passing credentials in URL strings, and using salted hashes to protect session IDs.
84
CSRF
Cross Site Request Forgery
Forces a logon victim's browser to send a forged HTTP request, including the victim's session cookie and any other authentication information, to a vulnerable web app. Allows attacker to force the victim's browser to generate requests the vulnerable application thinks are legitimate requests from the victim.
85
Missing Function Level Access Control
While most web apps verify function-level access rights before making that functionality visible in the UI, apps need to perform the same AC checks on the server when each function is accessed. If not verified, attackers will be able to forge requests in order to access functionality without proper authorization.
86
Insecure Direct Object References
Direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key. Attacker can manipulate these reference to access unauthorized data.
87
XSS
Cross Site Scripting
Flaws that occur whenever an application takes untrusted data and sends it to a web browser without proper validation and escaping. Allows attackers to execute script in the victim's browser, which can hijack user sessions, deface websites, or redirect the user to malicious sites.
88
Injection
SQl, OS, and LDAP Injections, occur when untrusted data is sent to an interpreter as part of a command or query. Attacker's hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization.
89
OWASP Top 10
1. Injection
2. Broken Authentication & Session Management
3. XSS - Cross Site Scripting
4. Insecure Direct Object References
5. Security Misconfiguration
6. Sensitive Data Exposure
7. Missing Function Level AC
8. CSRF (Cross Site Request Forgery)
9. Using Components with Known Vulnerabilities
10. Un-validated Redirects and Forwards
90
OWASP
Open Web Application Security Project
Free, available listing of the top vulnerabilities found in web applications.
91
Agile
Example of Iterative Development Model.
Relies on feedback from application users and development teams as their primary control mechanism.
92
RAD
Rapid Application Development
Leverage modern development environments that make it possible to quickly build UI components as requirements are gathered.
PROS? Quick and typically catches issues early.
CONS? Can suffer from 'Scope Creep', as new requirements are continually added and teams lose sight of the end goal.
93
Spiral Model
Similar to the Waterfall Development Cycle, but adds a repeated PDCA (Plan-Do-Check-Act) sequence at the end of each stage.
94
What phase is Web App design is the Software programming completed?
Implementation
95
Who participates in the design phase of a Web App?
Security Architect or administrator.
96
The general designed document, once refined to produce specifications for the....
Detailed design.
97
Where the design may first be laid out?
General Design Document
98
"Who signs off the 'Requirements Gathering and Analysis"
Project Sponsor and stakeholders
99
The Waterfall Model
6 Steps for developmental software applications as safely and securely as possible.
1. Requirement Gathering and Analysis
2. System Design
3. Implementation
4. Integration
5. Deployment
6. Maintenance
100
UML
Unified Modeling Language
Documentation of the sequences of actions called uses cases.
101
Authorization Official or Approver
Senior executive or manager with the authority to assume full responsibility for the system covered in the system security plan.
102
Security Officer
Responsible for coordinating development, review, and acceptance of security plans and for IDENTIFICATION, IMPLEMENTATION, ADMINISTRATION, and ASSESSMENT.
103
Information Owner
Has overall authority for the information stored, processed, or transmitted by the system. Responsible for specifying policies for appropriate use of information and security requirements for protecting information in the system.
104
System Owner
Responsible for decisions regarding system procurement or development, implementation and integration, and operation and ongoing maintenance.
105
System Security Plan
Comprehensive document that details the security requirements for a specific system, the controls established to meet those requirements, and the responsibilities and expected behaviors of those administering and accessing the system.
106
AC (Security Control)
Access Control
Technical
107
AT (Security Control)
Awareness Training
Operational
108
AU (Security Control)
Audit and Accountability
Technical
109
CA (Security Control)
Security Assessment and Authorization
Management
110
CM (Security Control)
Configuration Management
Operational
111
CP (Security Control)
Contingency Planning
Operational
112
IA (Security Control)
Identification and Authentication
Technical
113
IR (Security Control)
Incident Response
Operational
114
MA (Security Control)
Maintenance
Operational
115
MP (Security Control)
Media Protection
Operational
116
PE (Security Control)
Physical & Environmental Protection
Operational
117
PL (Security Control)
Planning
Management
118
PM (Security Control)
Project Management
Management
119
PS (Security Control)
Personnel Security
Operational
120
RA (Security Control)
Risk Assessment
Management
121
SA (Security Control)
System and Services Acquisition
Management
122
SC (Security Control)
System and Communications Protection
Technical
123
SI (Security Control)
System and Information Integrity
Operational
124
Directive (Controls)
Designed to specify acceptable rules of behavior within an organization.
125
Deterrent (Controls)
Designed to discourage people from violating security directives.
126
Preventive (Controls)
Prevent a security incident or information breach.
127
Compensating (Control)
Implemented to substitute for the loss of primary controls and mitigate risk down to an acceptable level.
128
Detective (Control)
Designed to signal a warning when a security control has been breached.
129
Corrective (Control)
Implement to remedy circumstance, mitigate damage, or restore controls.
130
Recovery (Control)
Implemented to restore conditions to normal after a security incident.
131
System Security Plan
Comprehensive document that details the security requirements for a specific system, the controls established to meet those requirements, and the responsibilities and expected behaviors of those administering and accessing the system.
132
System Owner
Responsible for decisions regarding system procurement or development, implementation and integration, and operation and ongoing maintenance.
133
Information Owner
Has overall authority for the information stored, processed, or transmitted by the system. Responsible for specifying policies for appropriate use of information and security requirements for protecting information in the system.
134
Security Officer
Responsible for coordinating development, review, and acceptance of security plans and for IDENTIFICATION, IMPLEMENTATION, ADMINISTRATION, and ASSESSMENT.
135
Authorizing Official or Approver
Senior executive or manager with the authority to assume full responsibility for the system covered in the system security plan.
