Security Architecture 3.4 Flashcards
High Availability
Reducing downtime, always on, always available, High availability almost always means higher cost. Upgraded power, higher quality server components.
Load Balancing
Maintains and distributes traffic/load across multiple servers. The load balancer adds or removes devices. May remove any server which is not responding.
Server Clustering
Combine two or more servers appears to operate as a signal large server. Easily increase capacity and availability.
There is often a shared storage between the servers.
Site resiliency
Recovery site is prepped. Data is synchronised at the recovery site and the business processes failover to the alternate processing site.
A hot site
An exact replica of the data centre. Applications and software are constantly updated - automated replication. Anything purchased in the normal base of operation must also be purchased and put into the hot site.
A cold site
Has no hardware, no data and no people. You have to bring in all of the infrastructure to run the site in the event of a site wide failure. A cold site would be used if risk of failure is very rare.
A geographic dispersion.
The site should be in completely different areas. If a tornado or flood disrupts production of a primary location the the secondary site shouldn’t be impacted.
Warm site
Somewhere between cold and hot site.
Platform Diversity
Different vulnerabilities exist within different operating systems. Spreading your operation over multiple operating systems will help to mitigate the risk.
Multi-cloud systems
There are many could providers.
Amazon Web service, Microsoft Azure, Google Cloud
Continuity of operations planning.
A fail back method. Non technical way to provide the same service. Manual transaction, paper receipts, phone call for transactions approvals.
Capacity Planning
Match supply to the demand.
Considerations:
Having enough people
Technology - Use of load balancers to increase servers if demand suddenly increases. Additional cloud services.
Recovery Testing
Test yourself before an actual event. Use of well-defined rules of engagement. Very specific scenario.
Can be very expensive.
Fail over (test)
Back up systems would be engaged to back up infrastructure to perform the fail over.
Simulation
Test with a simulated event. Phishing attack, password requests, data breaches.
Create a phishing email attack, send to your actual user community.
Does the phishing email get past the filter.