What Should Be Done First Before a Web Server Goes Live?
Short answer
A Harden the virtual host first by removing unnecessary services and applying secure baseline configurations before the new web server goes live, ahead of WAF rules and NIDS.
Question
Key Takeaways
It tests secure deployment order: the exam wants the broad host-hardening baseline first, while the trap is treating patch management as a standalone first step.
This SY0-701 scenario asks for the first security action before a new web server is exposed; the correct choice is to harden the virtual host (A), not to start with WAF rules, NIDS, or patch management.
Common mistake: Option D, apply patch management, is the plausible wrong answer because patching removes known vulnerabilities and is part of secure builds; however, it is a narrower task within hardening and 'apply patch management' describes an ongoing process, not the first host-level action before go-live.
Expert Analysis
Why the patch-first answer is tempting Option D, apply patch management, is the most attractive wrong answer because it sounds like the most concrete way to remove known vulnerabilities before exposure. It satisfies the 'new server' part of the stem and the desire to eliminate known CVEs, but it stops being correct at 'first': it assumes the host's secure configuration baseline already exists. Learners defending D describe a patch-then-harden sequence, and that has practical merit: a new server should not go live with missing OS or web-server patches. The question asks what the security team should do first, however, and CompTIA treats patching as one task inside the broader host-hardening baseline, not as the baseline itself. 'Apply patch management' also names an ongoing program rather than the immediate build action.
Why A is the first action Option A, harden the virtual host, covers disabling unnecessary services and default accounts, tightening permissions, removing unused ports, and applying secure configuration. That reduces the server's own attack surface before it can receive production traffic. WAF rules (B) and network intrusion detection (C) are layered filtering and monitoring controls around an already-built host; they do not make the virtual host secure first. Learners supporting A make the same distinction: patching is necessary, but it is a subset of hardening.
Exam takeaway The correct choice is A. When the stem emphasizes before go-live, select the host-level baseline that establishes a secure configuration. Do not let a narrow but operationally important task such as patching displace the broader first control.
Official Reference
These links open the official vendor documentation in a new tab.
Exam Strategy
When a question asks what to do 'first' before exposure, eliminate controls that monitor or filter traffic, because they assume the host is already built. Also separate a broad baseline action from a component: patching is a hardening task, but 'apply patch management' describes an ongoing program rather than the initial host build. Choose the option that reduces the server's own attack surface before it can receive production traffic.
Frequently Asked Questions
Why isn't patch management the first step before a new web server goes live?
When should WAF rules and network intrusion detection be enabled?
What does hardening a virtual host include?
Discussion 16 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 16
-
Anyio 👍 11 Answered AThe correct answer is: A. Harden the virtual host. Explanation: Hardening the virtual host is the first step a security team should take before a new web server goes live. This involves securing the server by removing unnecessary services, applying secure configurations, and minimizing potential attack surfaces. Hardening ensures the server is in a secure state before it is exposed to potential threats. Create WAF rules (B) is important but should be done after the server is hardened, as the Web Application Firewall (WAF) rules depend on the server's configuration and applications. Enable network intrusion detection (C) is a broader network security measure and should be implemented after the server itself is secured. Apply patch management (D) is critical but is part of the ongoing maintenance process and should follow initial hardening. Thus, hardening the virtual host is the first and most critical step to ensure the web server is secure before it goes live.
-
tomahawk117 👍 5 Answered DThe question says nothing about a a virtual host. After setting a new web server you'll want to make sure its patched.
-
jbmac 👍 3 Answered DThe correct answer is: D. Apply patch management. Explanation: Before a new web server goes live, the first thing the security team should do is ensure that the server is patched. Patch management ensures that all known vulnerabilities in the operating system, software, and web server components are addressed. This is crucial to minimize the attack surface and prevent exploitation of known vulnerabilities. Applying the latest patches is a foundational step in securing any system before it is exposed to the internet.
-
5a5837f 👍 3 Answered DLol, I discussed with ChatGPT because it doesn't follow its own rules sometimes. I support D. Here is why: - Apply patches is also part of the more general hardening terminology. - Apply patches is literally the first thing you should do to secure (not just maintenance). - CompTIA often rewards the answer that is the most direct operational control for the stated risk (apply patches), not the broad umbrella term that contains it (hardening your shi). May the universal chaos fall in your favor.
-
Fourgehan 👍 3 Answered ABefore a new web server goes live, the first step should be to harden the virtual host, which involves securing the server by: Disabling unnecessary services and ports. Configuring secure protocols. Setting strong authentication and authorization policies. Ensuring file permissions and directory structures are appropriately configured. Hardening ensures that the server's baseline security posture is strong and minimizes vulnerabilities that attackers could exploit
Show 11 more comments
-
Cocopqr 👍 3 Answered DD. Apply patch management. Patching the server first ensures it's up-to-date and less vulnerable to attacks.
-
Fhaddad81 👍 3Why not b Create WAF rules.?
-
Empath 👍 2 Answered AAnswer: A. Harden the virtual host. Reasoning: Before exposing a new web server to the internet, the first step is to ensure the system itself is hardened — removing unnecessary services, disabling default accounts, enforcing least privilege, securing configurations, and tightening permissions. Hardening reduces the attack surface so that even if later controls fail, the server itself is less vulnerable. B. Create WAF rules — important, but WAFs protect against application-layer attacks; they should be added after the server itself is secured. C. Enable network intrusion detection — helps detect threats but doesn’t prevent vulnerabilities from being exploited. D. Apply patch management — critical, but patching is a subset of hardening. Hardening encompasses patching plus many other baseline security steps. ✅ So the first action is to harden the virtual host.
-
78834d6 👍 2 Answered DCorrect answer is D. n secure system deployment, the correct order is: - Patch (remove known vulnerabilities) - Harden (reduce attack surface) - Configure WAF/NIDS (monitor and block threats) - Test and validate (ensure everything works securely)
-
LavaBoi 👍 2 Answered AApplying patch management doesn’t fit with what the question is asking. Applying patch management is the process of setting up the patch management instead of running the patch. Therefore, the correct answer is hardening the virtual host.
-
Clau95 👍 2Ran the same question and according to chat GPT the correct answer is D - Apply patch management
-
kippedwards8 👍 2 Answered AA. Harden the virtual host This is the correct answer according to chat GPT
-
danielbadasu 👍 1Explanation: Hardening the virtual host is the first step a security team should take before a new web server goes live. This involves securing the server by removing unnecessary services, applying secure configurations, and minimizing potential attack surfaces. Hardening ensures the server is in a secure state before it is exposed to potential threats. Create WAF rules (B) is important but should be done after the server is hardened, as the Web Application Firewall (WAF) rules depend on the server's configuration and applications.
-
Segunmx 👍 1 Answered AA. Harden the virtual host. Explanation: Before a new web server goes live, hardening the virtual host should be the first step. Hardening involves configuring the server to reduce vulnerabilities and enhance security.
-
MarysSon 👍 1 Answered AHarden the virtual host is more logical. While applying patches is necessary, the activity is a subset of hardening the host. Patches defend against commonly known vulnerabilities, but hardening does more
-
pchuu 👍 1 Answered APatching is a subset of hardening. Answer is A
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SY0-701 Questions
Access 100 questions with complete answers and detailed explanations.
View Full SY0-701 Practice Test →