Domain 3 : Explain the importance of resilience and recovery in security architecture Flashcards
High Availability
A high-availability infrastructure is designed to not only withstand relentless cyberattacks but also possesses the technical sophistication to autonomously detect, mitigate, and heal vulnerabilities in real time
Least Utilized Host
The load balancer monitors the health of all web servers within the server farms and identifies the least utilized host (that is, the host with the lightest current workload) using a smart scheduling algorithm. This method is effective for applications where server load varies, and the goal is to optimize resource utilization.
DNS round robin
With DNS round robin, when the request comes in, the load balancer contacts the DNS server and rotates requests starting with the IP address that has the lowest number first. It rotates through Web 1, Web 2, and Web 3, and then keeps the sequence going by going back to Web 1 on a rotational basis, as illustrated by Figure 13.2:
Affinity
: Affinity is a technique in which the load balancer directs requests from the same client to the same backend server for the duration of a session. The client is identified by their IP address or another session attribute. When the load balancer is set to “Affinity”, the request is sent to the same web server based on the requester’s IP address. This is also known as session persistence or a sticky session, where the load balancer uses the same server for the session.
active/active load balancer configuration
load balancers function together as a dynamic array, actively managing incoming traffic. The configuration can include multiple load balancers and there must be at least two. They not only distribute traffic but also cache requests for enhanced efficiency. An interesting feature is that if a user returns to a website for a subsequent visit, they are directed to the same load balancer that handled their initial request
active/passive load balancer configuration
has one active load balancer and one or more passive load balancers. The active node is responsible for actively load-balancing incoming requests. Simultaneously, the passive node or nodes operate in standby mode, constantly monitoring the active node’s health and status. Should the active node encounter a failure or become unavailable, a passive node seamlessly takes over, ensuring uninterrupted service
Downtime
: time during which production is stopped especially during setup for an operation or when making repairs.
Clustering
clustering involves grouping multiple servers or nodes together to operate as a single system. Clustering involves an active node and a passive node that share a common quorum disk, reinforced by a witness server, heartbeat communication, and a VIP at the forefront.
Quorum Disk
: The quorum disk is a shared storage resource that members of the cluster share. It acts as a neutral arbiter, storing critical configuration and state information that both the active and passive nodes access. This shared resource serves as the backbone of decision-making within the cluster.
Witness server
Adding an additional layer of reliability, the witness server is an impartial entity that assists in determining the state of the cluster. The witness server helps prevent split-brain scenarios and ensures that the cluster operates smoothly.
Heartbeat communication
Communication between the active and passive nodes is facilitated through a heartbeat mechanism. This heartbeat—analogous to the rhythmic pulse of a living organism—involves regular exchanges of status updates, or a “node heartbeat.” The passive node continuously monitors the active node’s heartbeat. If it detects an absence or irregularity in the node heartbeat, it knows that the active node has failed.
Virtual IP (VIP):
: At the forefront of the clustering setup is the VIP. It’s the public-facing interface of the cluster, acting as the entry point for external requests. The VIP ensures that even if the active node experiences any failures, the cluster remains accessible to users without disruption.
Hot site
: A hot site is the best site for rapid recovery. It is a fully operational site that mirrors your primary data center or infrastructure. This site is up and running with staff loading data into the systems immediately as it is replicated. This immediate response capability makes hot sites the most expensive option to maintain but also the fastest to recover from downtime.
Warm site
: A warm site is fully functional, but data synchronization typically lags behind that of a hot site. Data may be sent to the warm site by courier or other means, resulting in a delay of 3–4 hours compared to the primary site. This setup allows for a reasonably swift recovery while being more cost-effective than a hot site.
Cold site
Where the budget is very limited, a cold site presents an economical choice. Unlike hot and warm sites, a cold site is essentially an empty shell. It provides essential infrastructure, such as a power and water supply, but lacks staff, equipment, and data
Geographic disperation
Geographic dispersion involves the strategic distribution of data centers, servers, and critical infrastructure across different geographical locations, often separated by significant distances. The primary objective is to enhance resilience by reducing the risk of a single point of failure.
Local Redundant Storage (LRS)
In LRS, three copies of your data are replicated within a single physical location or data center.