📝 Network security management (9 MCQs)
📖 From Data Communication and Networks • 27. Network Management • 9 questions available
What is Network security management?
Network security management protects network resources from unauthorized access, attacks, and data breaches by implementing policies, firewalls, encryption, authentication, and continuous monitoring to safeguard confidentiality, integrity, and availability.
📝 All Network security management MCQs
Q1. What vulnerability arises from the server code’s lack of input validation when receiving data from a client?
📖 Explanation: The code increments the pointer and reduces the remaining length without confirming that the incoming bytes fit within the allocated buffer. This omission permits a buffer‑overflow attack, where an attacker can overwrite adjacent memory, potentially leading to arbitrary code execution or crashes. The absence of bounds checking is the root cause.
Q2. How do the security implications of using TCP versus UDP for an echo service differ?
📖 Explanation: TCP establishes a reliable, connection‑oriented session, which includes mechanisms like retransmission and ordering, reducing the chance of data loss or injection attacks. UDP lacks these safeguards, making it more vulnerable to packet loss and spoofing, while offering no native confidentiality or integrity guarantees.
Q3. Applying the principle of least privilege, how should the echo server process be configured on a production host?
📖 Explanation: Running the server under a dedicated, non‑privileged user limits the impact of any compromise, ensuring that even if an attacker gains control of the process, they inherit only minimal rights. This aligns with least‑privilege best practices and reduces the attack surface on the host.
Q4. If the server fails to close client sockets after each session, what is the most likely security consequence?
📖 Explanation: Leaving sockets open consumes file descriptors and memory, eventually exhausting system resources. Attackers can exploit this by opening many connections, causing the server to run out of descriptors and become unavailable to legitimate users, which is a classic denial‑of‑service scenario.
Q5. What effect does adding TLS to the echo server have on confidentiality and integrity of the transmitted data?
📖 Explanation: TLS encrypts the data stream, protecting it from eavesdropping (confidentiality), and incorporates MACs or AEAD ciphers that verify that the data has not been altered in transit (integrity). Therefore, wrapping the echo server with TLS addresses both security goals simultaneously.
Q6. Which comprehensive security policy best protects the echo server while maintaining usability?
📖 Explanation: A robust policy should record activity for forensic analysis (logging), verify client identity before allowing interactions (authentication), and limit the number of requests per client within a time window (rate‑limiting). This layered approach mitigates abuse, aids detection, and preserves service availability.
Q7. Given the code’s use of recv without checking for a zero return (client closed), which attack becomes most feasible?
📖 Explanation: If the server continues to allocate buffer space without recognizing that the client has closed the connection, an attacker can send a continuous stream of data, exhausting memory and CPU resources. This denial‑of‑service style resource exhaustion is facilitated by the missing zero‑length check.
Q8. When comparing this echo server to a stateless REST API that validates JSON payloads, which statement is most accurate?
📖 Explanation: A REST API typically parses structured JSON and can enforce schema validation, rejecting malformed or malicious inputs. In contrast, the raw echo server merely mirrors received bytes, lacking any validation, making the REST approach generally more resilient against injection and malformed‑data attacks.
Q9. Which security framework explicitly includes a control for regular patch management of network services like this echo server?
📖 Explanation: NIST Special Publication 800‑53 defines control CM‑11 (Information System Component Inventory) and related guidelines that mandate timely patching of software components, ensuring that known vulnerabilities in services such as an echo server are addressed promptly.