Blind spoofing is a type of network attack that involves sending packets with a forged source IP address to a target system, without knowing the sequence number or acknowledgment number expected by the target system. The attacker hopes to guess the correct numbers and establish a connection with the target system, or cause a denial-of-service (DoS) attack by exhausting the target system's resources. Blind spoofing can be prevented by implementing an internet-facing router that is baselined/hardened according to approved configurations and settings. A baselined/hardened router is a router that has been configured with the minimum necessary services, protocols, and ports, and has been updated with the latest patches and security measures. A baselined/hardened router can filter out spoofed packets by checking the source IP address against a list of trusted or authorized addresses, or by using techniques such as ingress filtering, egress filtering, or reverse path forwarding. Media Access Control (MAC) flooding, SQL injection (SQLI), and ransomware are not attacks that can be prevented by implementing a baselined/hardened internet-facing router. MAC flooding is a type of attack that targets the switch's MAC address table by sending a large number of frames with different source MAC addresses, causing the switch to overflow its table and act as a hub, broadcasting all frames to all ports. SQL injection is a type of attack that targets the web application's database by injecting malicious SQL statements into the user input, causing the database to execute unauthorized commands or reveal sensitive data. Ransomware is a type of malware that encrypts the victim's files or locks the victim's system, and demands a ransom for the decryption key or the unlock code.

The International Organization for Standardization (ISO) 27000 family of standards/guidelines requires an Information Security Management System (ISMS) to be defined. An ISMS is a systematic approach to managing the security of information assets, such as data, systems, processes, and people. An ISMS includes policies, procedures, controls, and activities that aim to protect the confidentiality, integrity, and availability of information, as well as to comply with the legal and regulatory requirements. The ISO 27000 family provides best practices and guidance for establishing, implementing, maintaining, and improving an ISMS. The ISO 27001 standard specifies the requirements for an ISMS, while the other standards in the family provide more detailed or specific guidance on different aspects of information security

Applying the Secure Hash Algorithm 3 (SHA-3) to a file downloaded from the internet verifies the integrity of the file. SHA-3 is a cryptographic hash function that produces a fixed-length output, called a hash or a digest, from a variable-length input, such as a file. SHA-3 is designed to be resistant to various attacks, such as collision, preimage, and length extension. The integrity of a file is the property that ensures that the file has not been altered or corrupted, intentionally or unintentionally, from its original state. By applying SHA-3 to a file, the user can generate a hash value that uniquely identifies the file and its content. The user can then compare the hash value with the one provided by the source or the publisher of the file, and verify that they match. If they match, it means that the file has not been modified or tampered with, and its integrity is preserved. If they do not match, it means that the file has been changed or compromised, and its integrity is violated.

DNS updates are typically the longest process due to propagation time. When you change DNS records (such as updating the IP address of the web server or modifying the DNS server addresses), it can take anywhere from minutes to 48 hours for the changes to fully propagate across the internet. This delay occurs because DNS resolvers worldwide cache DNS records, and updates must propagate to all of them.
In a disaster recovery scenario, if you're recovering a website and need to point the domain to a new server, you'll have to wait for the DNS changes to propagate before users can reach the new web server. This is often the most time-consuming step in the recovery process.