2.5 - Implement Cybersecurity Resilience Flashcards
1
Q
Redundancy
A
- Duplicate parts of the system
- If a part fails, the redundant part can be used
- Usually a reaction to some sort of failure that has occured
- Goal is for an organization to continue to be up and running
- Ex: Hardware (mother board fails)
- Ex: Software (bug in software that causes service to crash)
- Need to maintain up time and services
- Building networks where the network stays up and running even when part of the network may fail
2
Q
Geographic Dispersal
A
- Bad things can happen in a local area
- Ex: Hurricane, tornados, natural disaster
- Disperse technologies to different geographic
- Use multiple data centers in different locations
- May be part of normal operations (ex: East and West coast operation centers)
- Or it may be part of a disaster recovery plan (Ex: If Florida is hit, fire up Denver)
3
Q
Disk Redundancy
A
- Multipath I/O (input / output)
- Allows us to create multiple routes on the network for work arounds
- Especially useful for network - based storage sub systems
- Ex: Multiple fibre channel interfaces with multiple switches
4
Q
RAID
A
- Redundant Array of Independent Disks
- Example of Disk Redundancy
- Most redundancy comes from using multiple disks for a single array
- You have separate pieces of array data on other disks
- System admins will replace bad drive behind the scenes, users usually don’t know
5
Q
RAID 0
A
- “Striping without parity”
- High performance, no fault tolerance
- No redundancy
- Good performance to read/write to array, but if something happens, there is no redundancy
- Most companies don’t use this
- This is a type of redundancy
6
Q
RAID 1
A
- “Mirroring”
- Take 1 physical drive and duplicated it on another physical drive
- Duplicates data for fault tolerance, but requires twice the disk space
- Most companies will start with this as a bare minimum
- This is a type of redundancy
7
Q
RAID 5
A
- “Striping with parity”
- Fault tolerant, only requires an additional disk for redundancy
- Putting pieces of information on other drives and then parity of information on the last drive
- If you lose anything it will rebuild based on the parity on last drive
- This is a type of redundancy
8
Q
Combination RAIDS
A
- Can combine RAID types and customize redundancy to be prepared for drive failures
9
Q
Load Balancing
A
- Balance loads b/n multiple servers
- Person makes a server request and the load balancer decides which server will answer request
- Some servers are active (others are on standby)
- Always sending hello messages to check in
- If an active server fails, the load balancer will decide to use a standby (passive) server
- Many load balancers will remember which server a particular user used, and if the user sends another request, the load balancer will route them to the same server
10
Q
Active Servers
A
- In a load balancing, these servers will actively respond to request once passed through the load balancer
11
Q
Standby servers
A
- In a load balancing, up and running, but are waiting, load balancer won’t send any traffic to them
12
Q
NIC Teaming
A
- Even if you don’t have a load balancer, you can provide redundancy to a server using multiple network interface cards
- allows us to use multiple connections to a server, but instead of having a primary and standby connection, you can use both together and aggregate the bandwidth
- this increases the throughput and a way to have redundant paths should one path
- On the server, this usually involves installing multiple network interface cards on the server, the cards are bound together to look like one
- Configure the switch side of things so that any traffic going in b/n the connections is labeled as ‘NIC teamed’ in the server
- NICs talk to each other (like load balancers send hello messages), usually over multicast connection
- if a connection becomes unavailable, the server will recognize that the card is not responding and it will administratively turn it off and use another NICs to provide redundancy (you can then configure these NICS to talk to two different switches to provide more redundancy)
- aka Load Balancing / Fail Over (LBFO)
13
Q
LBFO
A
- Load Balancing / Fail Over
- aka NIC Teaming
- allows us to use multiple connections to a server, but instead of having a primary and standby connection, you can use both together and aggregate the bandwidth
- this increases the throughput and a way to have redundant paths should one path
- Another way to provide redundancy without a load balancer
14
Q
UPS
A
- Uninterruptible Power Supply
- Has batteries inside and if power goes, it goes to batteries (temporary power source)
- Perhaps the primary resource we need to operate computers, laptops, mobile devices is power
- during brown outs
- Useful tools for temp power outages
15
Q
UPS Types
A
- Uninterruptible Power Supply
- Offline/ Standby UPS
- Line-interactive UPS
- On-line/ Double-conversion UPS
- These three get more expensive as you go down the list
- Different devices have different models (ex: auto shutdown, battery capacity, outlets, phone line suppression)
16
Q
Offline / Standby UPS
A
- Simplest, cheapest
- Not normally enabled unless power is lost
- Therefore, short lag time frame when the time is lost to when it switches to UPS
17
Q
- Line-interactive UPS
A
- If voltage is slowly diminishing, then the UPS can slowly ramp up
- During brown outs, it can fill in the difference
- “midway option” b/n the UPS’s
18
Q
- On-line/ Double-conversion UPS
A
- Top of the line, always online and providing power to devices
- no lag time b/c you’re already on battery powered
19
Q
Generator
A
- Long-term power backup
- Fuel storage required
- Can often power entire buildings or a number of outlets (usually marked to show they can provide power during an outage)
- Usually a 10 or 15 sec wait when generator will wait to see if power is restored
- During this 10 sec lag, need some other system
- Might combine UPS + Generator to close the gap
20
Q
Dual- power supplies
A
- This creates redundancy
- Internal server power supplies
- external power circuits
- Might want to have a server that has multiple power supplies (where you can plug in multiple power sources)
- Designed so that each individual power supply can support the power for the entire power for the server 100%
- If you plug in both, then each power supply provides 50%
- Often hot-swappable, so if one fails, you can pull one out and plug another one in