Domain: 7 Security Operations 13% Flashcards

1
Q

Administrative Security

A

Provides the means to control people’s operational access to data.

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

Least Privilege

A

We give employees the minimum necessary access they need, no more, no less.

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

Need to know

A

Even if you have access, if you do not need to know, then you should not access the data.

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

Separation of duties

A

More than one individual in a single task is an internal control intended to prevent fraud and error. We do not allow the same person to enter the purchase order and issue the check.

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

Job rotation

A

Job rotation to detect errors and frauds. Makes it easier to detect fraud and there is less chance of collusion btw individuals if we use job rota

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

Mandatory vacations

A

Done to ensure one person is not always performing the same task, someone else has to cover and it can keep fraud from happening or help us detect it. Their accounts are locked and an audit is prfrmd on the accnt.

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

NDA (non disclosure agreement)

A

Can be btw employees and the org. Or btw two orgs.

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

Background check

A

references, degrees, employment history, certifications, criminal history, credit history. For sensitive pos the bckgrnd chck is an ongoing process.

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

Privilege monitoring

A

The more access and privilege an employee has the more we keep an eye on their activity. We continually audit and monitor what they access. This is normally automated.

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

Digital (comp) forensics

A

Focuses on the recovery and investigation of material found in digital devices, often in relation to comp crime. Forensics is based on gathering and protecting the evidence, where incidents responses are how we react in an event breach. We preserve the crime scene and the evidence, we can prove the integrity of it at a later needed time,oftn court.

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

The forensic process:

A
  • Id the potential evidence, acquire the evidence, anayze the evidence, make a report.
  • be aware of how we gather our forensic evidence, attckrs are cvring their tracks, deleting the evdnc and logs.
  • This can be through malware that is only in volatile mem, if pwr is shut off (to preserve the crime scene), the malware is gone and the evidence is lost.
  • Disconnect sys from ntwrk adn take bit by bit copies of the mem, drives, running processes & ntwrk cxn data.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

The evidence

A

we collect must be accurate, complete, authentic, convincing, admissible.

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

Identification

A

Id the evidence, what is left behind.

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

Preservation

A

Evrythng is documented, chain of custody: Who had it when? What was done? When did they do it? Pull the og, put it in write protected machine, we make a hash. We ony do examinations and analysis on bit level copies, we confirm they have the same hash as the og before and after examination.

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

Collection

A

We examine and analyze the data, again we document evrythng. We handle the evidence as little as possible. Work from most volatile to least volatile, starting with the RAM and ending with the hard disks.

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

Incidence response plan

A

can include getting our HR and Legal dept involved. Ensure evidence is acquired in a legal manner remember US Cons 4th amendment.

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

Examination

A

find the facts and document them, collecting the data.

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

Analysis

A

look at the data and look for meaning or reason

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

Presentation in court

A

we present our findings and any other evidence.

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

Decision

A

The court rules on the case.

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

Forensic data

A

is normally obtained from binary images of secondary storage, portable storages devices: hard drives, flash drvs, CDs, DVDs, cell phone, mp3 players. We use binary or bit stream image copy to ensure ew get an exact copy of the device, and not just a copy of certain sectors.

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

Real Evidence

A

Tangible adn physical objects, in IT Sec: hd, usb -NOT the data on them.

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

Evidence Integrity

A

It is vital the evidences integrity cannot be questioned, we do this with hashes. Any forensics is done on copies and never the originals, we check hash on both original and copy before and after the forensics. Heresay, but admissible due to Law 803.

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

Chain of Custody

A

Chain of custody form, this is done to prove the integrity of the data. No tampering is done. Who handled it? When did they handle it? What did they do with it? Where did they handle it?

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

Allocated space

A

The portions of the disk that are marked as actively containing data.

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

Unallocated space

A

The portions of the disk that does not contain active data. This is parts that have never been allocated and previously allocated parts that have been marked unallocated. When a file is deleted, the parts of the disk that held the deted file are marked as unallocated and made avaialble for use. So that data is there unit ovrwrtten

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

Slack space

A

data is stored in specific size chunks known as clusters (clusters = sectors or blocks). A cluster is the minimum size that can be allocated by a file system. If a particular file, or final portion of a file, does not require the use of the entire cluster then some extra space will exist within the cluster. This leftover space is known as slack space: it may contain old data, or can be used intentionally by the attackers to hide information.

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

Bad blocks/clusters/sectors

A

HD end up with sectors that cannot be read due to some physical defect. The sectors marked as bad will ignored by the OS since no data could be read in those defective portions. Attackers can mark sectors or clusters as being bad in order to hide data within this portion of the disk.

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

Network forensics

A

we look at monitoring and analysis of computer network traffic for the purposes of information gathering, legal evidence, or intrusion detection. Network investigations deal with volatile and dynamic info. Network traffic is transmitted and then lost, so network forensics is often a pro-active investigation.

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

The first type

A

monitoring a network for anomalous traffic and id intrusions (IDS/IPS). An attacker might be able to erase all log files on a compromised host, a network-based evidence might be the only evidence available for forensic analysis.

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

The second type

A

relates to law enforcement. In this case analysis of captured network traffic can include tasks such as reassembling transferred files, searching for keywords and parsing human comm such as emls or cht sessions

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

Catch-it-as-you-can

A

All packets passing through a certain traffic point are captured and written to storage with analysis beind done subsequently in batch mode. This approach requires large amounts of storage.

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

Stop, look and listen

A

each packet is anlyzed in a basic way in memory and only certain fino is saved for future analysis. The approach requires a faster process to keep up with incoming traffic.

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

Catch-it-as-you-can

A

All packets passing through a certain traffic point are captured and written to storage with analysis being done subsequently in batch mode. This approach requires large amounts of storage.

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

Stop, look and listen

A

each packet is anlyzed in a basic way in memory and only certain info is saved for future analysis. This approach requires a faster processor to keep up with incoming traffic.

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

Forensic software analysis

A

Comparing and/or reverse engineering software. REverse engineering malware is one of the most common examples. Investigators often have a binary copy of a malware program, and try to deduce what it does. Common tools are disassembers and debuggers.

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

Embedded device forensics

A

SSD’s, GPS’, cell phones, PDA. They contain a lot of info, but how we safely retrieve it while keeping the integrity of the data. IOT can be a sec concern. Where does the GPS say the car, phone or person was at a certain time? When did the AC turn on? Can we assume someone was home at that time?

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

Incident management

A

Involves the monitoring and detection of security sevents on our systems, and how we react in those events. The primary purpose is to have a well understood and predictable reponse to events and computer intrusions. We have very clear processes and a responses, and our teams are trained in them and know what to when an even occurs.

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

Incidents and events can generally be categorized in 3 classes

A

Natural: Hurricanes, flds, earthquakes, blizzards, anything that is caused by nature. Human: Done intentially or unintentionally by humans, these are by far the most common. Enviromental: The pwr grid, the Internet cxns, hwd failure, sftwr flaws.

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

Event

A

An observable change in state, this is neither negative nor positive, it is just something has changed.

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

Alert

A

Triggers warnings if certain event happens.

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

Incident

A

Multiple adverse events happening on our systems or network, often caused by people.

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

Problem

A

Incidence with an unknown cause, we would follow similar steps to incidence reponse. More time would be spent on root cause analysis, we need to know what happened so we can prevent it from happening again.

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

Inconvenience (non-disasters)

A

Non-disruptive failures, hd failure, 1 server in a cluster is down.

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

Emergency (Crisis)

A

Urgent, event with the potential for loss of life or property.

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

Diaster

A

Our entire facility is unusable for 24 hrs or +

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

Diaster

A

Our entire facility is unusable for 24 hrs or +. Yes, a snowstorm can be a disaster.

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

Incident management, 7-step lifecycle

A
  1. Prep (left out in exam). 2. Detection (Id). 3. Response (Containment). 4 Mitigation (Eradication). 5 Reporting. 6. Recovery. 7 Remediation. 8 Lessons Learned (Post-incident activity, post mortem, or reporting)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
49
Q
  1. Preparation
A

We write the policies, procedures, we train our staff, we procure the detection sft/hrdwr, we give our incidence response team the tools they need to respond to an incident.

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

Events are analyzed to determine if they might be a security incident. IDS’ can help us detect, IPS’ can help us detect and prevent further compromise. SIEM = security incident event manager, collects everything from everything all alerts,logs, event, incident.

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

When the incident response team begins interacting with affected systems and attempts to keep further damage from occurring as a result of the incident. Isolate the sys, network/traffic. Make bit level copies of sys

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

When the incident response team begins interacting with affected systems and attempts to keep further damage from occurring as a result of the incident. Isolate the sys, network/traffic. Make bit level copies of sys Stop it from spreading

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

Understanding the cause of the incident that the sys can be reliably cleaned and restored to operational status later in the recovery phase.

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

begins with the detection, and we start reporting immediately when twe detect malicious activity. Reporting has 2 focus areas technical and non-technical. The incident handling team reports the tech details of the incident as they start the incident handling process, but they also notify management of serious incidents. The procedures and policies will outline when which level of managment needs to be informed and involved.

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

We carefully restore the sys/s to operational status. We closely monitor the rebuilt sys incase a backdoor was left.

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

Remediation happens during the mitigation phase, where vulnerabilities on teh impacted system/s are mitigated. Patching all sys with the same vulnerability or change how the org authenticates.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
57
Q
  1. Lessons Learned
A

Problem there has been fixed, what was compromised, what are the vulnerabilities, how did the team react, which part of our plans worked and which didn’t.

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

Root-cause analysis

A

We need to fix the vulner on the sys/s that were effected, but also on any system in the organization that has the particular vulnerability or set of vulnerability.

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

IDS and IPS

A

can be categorized into 2 types and with 2 different approaches to identifying malicious traffic.

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

Network based

A

placed on a network segment (a switch port in promiscuous mode)

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

Host based

A

on a client, normally a server or workstation

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

Signature (pattern) matching

A

similar to antivirus, it matches traffic against a long list of known malicious traffic patterns

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

Heuristic (Behavioral) based

A

uses a normal traffic pattern baseline to monitor for abnormal traffic.

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

SIEM (Security Info and Event Management)

A

gives you a full picture views and data correlation.

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

IDS (Intrustion Detection Sys)

A

They are passive, they monitor, but they take no action other than sending out alerts.

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

IPS (Intrusion Prevention System)

A

Similar to IDS, but they also take action to malicious traffic, what they do with the traffic is determined by configuration. Events trigger an action.

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

IDS/IPS

A

Part of our layered defense. Basically they are packet sniffers with analysis engines.

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

Network based

A

placed on a network segment (a switch port in promiscuous mode). Inspects hostdestination ports, IP’s, protocols, content of traffic, but can obviously not look at in encrypted traffic. Can protect against DDOS, Port scans, brute force attacks, Deployed on 1 switch, port and NIC must be promiscuous and port must be a span port.

69
Q

Host based

A

on a client, normally a server or workstation. We only look at a single sys. Who is using the sys, the resource usage, traffic. It can be app specific if needed. Certain attacks turn off HIDS/HIPS.

70
Q

Signature based

A

looks for known malware signatures. Faster since they just check traffic against malicious signatures. Vulnerable to 0 day attacks

71
Q

Heuristic (Behavioral) based

A

Looks for abnormal behaviro -can produce a lot of false positives. We build a baseline of what normal network traffic looks liek and all traffic is matched to that baseline.

72
Q

Hybrid based

A

combines both are more used now and check for both signatures and abnormalities.

73
Q

Ways attackers

A

attempt to avoid detection

74
Q

Fragmentation

A

sending fragmented packets, the attack can avoid teh detection systems’s ability to detect the attack signature

75
Q

Avoiding defaults

A

TCP port utilized by a proto does not always provide an indication to the proto which is being transported. Attackers can send malware over an unexpected port.

76
Q

Low-bandwidth coordinated attacks

A

a number of attackers (agents) allocate different ports or hosts to different attackers making it difficult for the IDS to correlate the captured packets and deduce that a network scan is in progress. Address spoofing/proxying

77
Q

Pattern change evasion

A

The attacker changes the data used in the attack slightly, which may avoid detection.

78
Q

Alerts on IDS’/IPS’ can like

A

biometrics be one of 4 categories:

79
Q

True positive

A

an attack is happening and the sys detects it and acts.

80
Q

True negative

A

normal traffic on the network and teh system detects it and does nothing

81
Q

Falso Positive

A

normal traffic and the sys detects it and acts

82
Q

False Negative

A

an attack is happening and the sys does not detect it and does nothing.

83
Q

SIEM (Security info and event management)

A

Gathers from all our systems and looks at everything. Centralizes the storage and interpretation of logs, traffic and allows near real-time automated id, analysis and recovery of security events.

84
Q

Application whitelisting

A

we allow our users to run these apps on our enviroments, but it can also be compromised. White list against a trusted digital cert, a known hash or path and name.

85
Q

Removable media controls

A

lock down USB ports, CD Drives, memory card ports

86
Q

Honeypots

A

System looking like a real system, but with the sole purpose of atracting attackers. They are used to learn about our vulnerabilities and how attackers would circumvent our security measures. Talk to the Legal Dept. before deploying honeypots.

87
Q

Honeynets

A

a network of honeypots, can be a full server farm simulated with applications, OS’ and fake data.

88
Q

Configuration Management

A

Harden sys before we deploy them. Close network ports, services to disable, accounts to delete, missing patches. We do this for any device on our network. Pre introduction into our production enviro we run vulnerability scans against the system to ensure we didn’t miss anything.

89
Q

Patch Management

A

apply patches on a reg basis. Make sure you update network equip, array updates, IOT updates and so on.

90
Q

Change Mangement

A

Our formalized process on how we handle changes to our enviroments. If done right we will have full documentation, understanding and we communicate changes to appropriate parties. The change review board should be compromised of both IT and other operational units from the org. The board can have senior leadership on itt.

91
Q

Change management flow

A
  1. ID the change 2. Propose the chng 3. Assessing rsks, impcts and bnfts of implementing and not imple 4. Provisional change approval 5. Testing the change 6. Scheduling the change 7. Change notification for impacted parties 8. Implementing the change. 9 Post implementation reporting of the actual change impact.
92
Q

Change control

A

the parts where we control the change.

93
Q

0 day vulnerabilities

A

Vulner not generally known or discovered. Protect against this with defense in depth.

94
Q

0 day exploit

A

code that uses the 0 day vulnerability.

95
Q

Fault tolerance

A

To ensure our internal SLA’s and provides as high availability as possible we use as high degree of redundancy and resiliency as makes sense to that particular sys and data set.

96
Q

Backups

A

For backups we use Full, Incremental, Diff and Copy backups.

97
Q

Full backup

A

This backs everything up, the entire database (most often), or the system. A full backup clears the all archive bits.

98
Q

Incremental backup

A

Backs up everything that has changed since the last backup. Clears the archive bits. The downside to them is if we do montly full backup and daily incrementals, we would have 30 tapes to restore.

99
Q

Differential backup

A

backs up everything since the last Full backup. Does not clear the archive bit. Faster to restore since we just need 2 tapes for a full restore, the full and the differential.

100
Q

Copy backup

A

Full backup that doesn’t clear the archive bit. Often used before we do sys updates, patches and similar upgrades.

101
Q

Archive bit

A

For Win NTFS has an archive bit on files, it indicates if the file was changed since the last Full or Incremental backup

102
Q

RAID

A

(Redundant Array of Independent Disks)

103
Q

Disk mirroring

A

Writing the same data across multiple hd, slower, because the controller has to write everything twice.

104
Q

Disk striping

A

Writing the data simultaneoulsy across mult disks providing higher write speed. Uses at least 2 disks. No redundency unless you use parity, but you nd 3 hd.

105
Q

RAID 0

A

Striping with no mirroring or parity, no fault tol, only provides faster read/write speed, req at least 2 hd

106
Q

RAID 1

A

Mirror set, 2 hd with identical data, and write function is written to both disks simultaneously.

107
Q

RAID 5

A

block level striping with distributed parity, req at least 3 disks. Combined speed with redundancy.

108
Q

Redundant parts

A

PSU, fans, NICS, disk controllers

109
Q

System redundancy

A

load balancing and clustering. Geographically dispersed.

110
Q

Database shadowing

A

exact real time copy of the DB or files to another location. It can be another disk in the same server, but best practices dictates another geograph loc, often on a different media.

111
Q

Electonic vaulting (e-vaulting)

A

Using a remote backup service, backups are sent off-site elec at a certain interval or when files change.

112
Q

Remote jounaling

A

Sends transaction log files to a remote location, not the files themselves. The transactions can be rebuilt from the logs if we lose the original files.

113
Q

BCP (Business Continuity Plan)

A

the process of creating the long-term strategic business plans, policies and procedures for continued operation after a disruptive event. It is for the entire org, everything that could be impacted, not just IT. Lists a range of disaster scenarios and the steps the org must take in any particular scenario to return to regular ops.

114
Q

BCP’s often contain:

A

COOP, Crisis Comm Plan, Critical Infr Prot Plan, Cyber Incident Res Pln, DRP,

115
Q

DRP (Diaster Recovery Plan)

A

This is the process of creating the short-term plans, policies, procedures and tools to enable the recovery or continuation of vital IT sys in a diaster. It focuses on the IT sys supporting critical business func, and how we get those back up after a disaster. DRP is a subset of our BCP

116
Q

Most common reason for a disruptive events are internal employees.

A

often called errors and omissions.

117
Q

DRP should answer at least 3 basic questions:

A

What is the objective and purpose? Who will be the people or teams who will be responsible in case any disruptions happen? What will these people do (our procedures) when the disaster hits? *Inform every who should know of what has happened.

118
Q

Mitigation (pre-disaster)

A

reduce the impact, and likeliness of a disaster

119
Q

Preparation

A

build programs, procedures and tools for our response

120
Q

Response

A

how we react in a disaster, following the procedures.

121
Q

Recovery

A

reestablish basic functionality and get back to full production.

122
Q

Older v of NIST 800-34 had these steps as a framework for building our BCP/DRP

A

Project Initiation, Scope of Project, Business Impact Analysis, Id Preventitive Controls, Recovery Strategy, Plan Design and Development, (Implementation, Training, and Testing) BCP/DRP Maintenance

123
Q

Rescue team (activation/notification)

A

responsible for dealing w/ the disaster as it happens. Evacute employees, notifies the appropriate personnel, pull the network from teh infected server/shutdown sys

124
Q

Recovery team (failover)

A

responsible for getting the alternate site up and running as fast as possible or for getting the sys rebuilt. We get most critical sys up first.

125
Q

Salvage team

A

responsible for returning our full infrastructure, staff and ops to our primary site or a new facility if the old site was destroyed.

126
Q

BIA (Business impact analysis)

A

Ids critical and non-critical org sys, fnc, activities. Critical is where disruption is considered unacceptable, the acceptability is also based on the cost of recover. A fnc may also be considered if dictated by law.

127
Q

Each critical sys, function or activity has two values assigned to them

A

RPO and MTD

128
Q

RPO (Recovery Point Objective)

A

The acceptable amount of data that can not be recovered. The recovery point objective must ensure that the maximum tolerable data loss for each system, function or activity is not exceeded.

129
Q

MTD (Max Toler Dwntime)

MTD>=RTO+WRT

A

The time to rebuild the sys and config for reinsertion into prod must be less than or equal to our MTD. The total time a sys can be inoperable before our org is severely impacted.

130
Q

RTO (Recovery Time Obj)(hardware)

A

The amnt of time to restore the sys (hardware). The recovery time obj must ensure that the MTD for each sys, func or activity is not exceeded.

131
Q

WRT (Work Recovery Time)(software)

A

How long does it take us to the time required to configure a recovered sys.

132
Q

Redundant site

A

Complete identical site to our prod, receives a real time copy of our data. Expensive.

133
Q

Hot site

A

only houses critical app and sys. We may have to manually fail traffic over, but a full switch can take an hour or less. Near or real-tiem copies of data.

134
Q

Warm site

A

Similar to the hot site, but not with real or near-real time data, often restored with backups. A smaller but full data center. We manually fail traffic over, a full switch and restore can take 4-24 hrs.+

135
Q

Cold site

A

a smaller but full data center. No hardware or backups are at the cold site, they require sys to be acquired, conf and applications loaded and config. This is the cheapest, but also longeste recovery option, can be weeks+

136
Q

Reciprocol Agreement site

A

your org has a contract w/ another org that they will give you space in their data center in a disaster even and vice versa.

137
Q

Mobile site

A

Basically a data center on wheels, often a container or trailer that can be moved whereever by a truck.

138
Q

Subscription/cloud site

A

We pay someone else to have a minimal or full replica of our production enviro up and running within a certain number of hours (SLA)

139
Q

COOP (Continuity of Operations Plan)

A

How we keep operating in a disaster, how do we get staff to alternate sites, what are all the operational things we need to ensure we function even if at reduced capacity for up to 30 days.

140
Q

Cyber Incident Response Plan

A

How we respond in cyber events, can be part of the DRP or not.

141
Q

OEP (Occupant Emergency Plan)

A

How do we protect our facilities, our staff and the enviroment in a disaster event. Focuses on safety and evacutation, details how we evacuate, how often we do drills and the training staff should get.

142
Q

BRP (Business Recovery Plan)

A

Lists the steps we need to restore normal business operations after recovering from a disruptive event.

143
Q

Continuity of Support Plan

A

Focuses narrowly on support of specififc IT sys and apps. Also called the IT Contigency Plan, emphasizing IT over general business support.

144
Q

CMP (The Crisis Management Plan)

A

Gives us effective coordination among the managment of the org, in the event of an emergency or disruptive event. Details what manag must take to ensure that life and safety of personnel and property are immediately protected in case of a disaster.

145
Q

Crisis Comm Plan

A

A subplan of the CMP. How we comm inter and ext during a disaster

146
Q

Call Trees

A

Each user in the tree calls a sml # of users.

147
Q

Off site copies and plans

A

We keep both digital and phy copies of all our plans at offsite locations.

148
Q

EOC (Emergency Operations Center)

A

A central temporary command and control facility responsible for our emergency management or disaster management functions at a strategic level during an emergency.

149
Q

MOU/MOA (Memorandum of Understanding/Agreement

A

Staff signs a legal document ack they are responsible for a certain activity.

150
Q

Executive Succession Planning

A

Senior leadership often are the only ones who can decalre a disaster. Our plans should clearly outline who should declasre a disaster, if they are not available.

151
Q

Employee redundancy

A

We should have as high degree of skilled employee redundancy, just like we have on our critical hardware. Can be mitigated with training and job rotation.

152
Q

DRP review

A

Team members wo are part of the DRP team review the plan quickly looking for glaring omissions, gaps or missing sections in the plan.

153
Q

Read-through (checklist)

A

Managers and functional areas go through the plan and check a list of components needed for in the recovery process.

154
Q

Walk/Talk-through (tabletop or structured walkthrough)

A

a group of managers and critical personnel sit down and talk through the recovery process. Can often expose gaps, omissions or just technically inaccurracies that would prevent the recovery.

155
Q

Simulated Test (Walkthrough Drill)

A

Similar to the walkthrough (but different, do not confure them). The team simulates a disaster and teh teams respond with their pieces from the DRP.

156
Q

Parallel processing

A

we bring critical components up at a secondary site using backups and compare to the same sys at the primary site

157
Q

Partial Interruption

A

We interrupt a single app and fail it over to our secondary facilities, often done off hours.

158
Q

Full Interruption

A

We interrupt all app and fail it over to our secondary facilities, always done off hours. Both partial and full are mostly done by fully redundant orgs.

159
Q

Testing

A

to ensure the plan is accurate, complete and effective, happens before we implement the plan

160
Q

Drills (exercises)

A

Walkthroughs of the plan, main focus is to train staff, and improve employee response (think fire drills)

161
Q

Auditing

A

A 3rd party ensure that the plan is being followed, understood and the measures in the plan are effective.

162
Q

We train staff to raise the awareness

A

awareness is their ability to do a task in the DRP.

163
Q

The plans need to be continually updated

A

it is an iterative process. Plans should be reviewed and updated at least every 12 months. When we update the plans older copies are retrieved and destroyed, and current versions are distributed.

164
Q

After a disruption

A

we only use our BCP/DRP’s when our other countermeasures have failed.

165
Q

NIST 800-34

A

Provides instructions, recommendations, and considerations for federal information system contingency planning. Contingency planning refers to interim measures to recover information sys services after a disruption.

166
Q

ISO 22301

A

Societal security, Business continuity management sys, specifies a management sys to manage an orgs business continuity plan, supported by ISO 27031.

167
Q

ISO/IEC-27031

A

Societal security, business continuity management sys - guidance, which provides more pragmatic advice concerning business continutiy managment.

168
Q

BCI (Business Continuity Institute)

A

6 step process of Good Practice Guidelines (GPG) the independent body of knowledge for Business Continuity.