An engineer recently deployed a group of 100 web servers in a cloud environment. Per the security policy, all web-server ports except 443 should be disabled.
Which of the following can be used to accomplish this task?
An engineer recently deployed a group of 100 web servers in a cloud environment. Per the security policy, all web-server ports except 443 should be disabled.
Which of the following can be used to accomplish this task?
To accomplish the task of disabling all web-server ports except port 443, a host-based firewall is the appropriate solution. A host-based firewall operates on individual servers and can be configured to block all ports except those explicitly allowed. In this case, it would be configured to allow only port 443, which is used for secure HTTPS communication, while disabling all other ports. This method is effective for applying such security policies to each of the 100 deployed web servers.
Not A or D. Was not sure whether it should be B or C until I read the definition of SWGs in the official guide from CompTIA. "An on-premises SWG is a proxy-based firewall, content filter, and intrusion detection/prevention system that mediates user access to Internet sites and services"
So must be B, same result, but you can not configure 100 host-based firewall as C
Why not? It's so common and easy with cloud orchestration tools.
No. A secure web gateway protects users going out to the internet. You can easily configure the host-based firewall through GPO and apply it to all machines at once.
Except these servers are not on-premises they are all on the cloud, meaning they are IaaS and virtualized, and thus there are not hosts to base these firewalls on. Secure Web Gateway works on OSI Layer 4, which blocks ports https://www.ibm.com/products/secure-gateway#:~:text=The%20Secure%20Gateway%20service%20represents,server%2Dside%20and%20mutual%20authentication.
This one asks which one is used for port blocking in WEB SERVERS. SWG is primarily used to protect USERS from accessing or being infected by web threats. I'll go with firewalls to explicitly allow 443.
I did this as a part of my job; it's C. You make a baseline configuration that disables all ports except 443 and spawns all of them at once.
To accomplish the task of disabling all web-server ports except 443, the most suitable option would be a host-based firewall. A host-based firewall can be configured to allow only specific ports, such as port 443 for secure web traffic, while blocking all other ports. This helps enforce the security policy and restrict access to the web servers. So, the correct answer is C. Host-based firewall. While a Secure Web Gateway (SWG) can provide security features like URL filtering and malware protection, it may not be the best choice for this specific task of disabling web-server ports. SWGs are typically used for monitoring and securing web traffic, rather than controlling access to specific ports on individual servers. In this case, a host-based firewall would be more appropriate for the task at hand. Hope that clarifies things for you all.
Both can do the same. However, SWG can be on premise as well as cloud based. "Cloud enviroment" is the clue.
The correct answer is "C." You can allow or deny specific ports using a host-based firewall. For example in Linux, "sudo ufw allow 443" would allow port 443 (https), and you can substitute with "allow" with "deny" for ports you want to deny.
C. Host-based firewall To accomplish the task of disabling all web-server ports except 443, a host-based firewall can be used. A host-based firewall operates at the individual server level, allowing administrators to define rules and restrictions on incoming and outgoing network traffic for specific hosts. In this scenario, the host-based firewall on each of the 100 web servers can be configured to block traffic on all ports except port 443. This ensures that only traffic on port 443 (commonly used for secure HTTPS communication) is allowed, in accordance with the security policy. The other options are not directly related to the task at hand
Secure Web Gateways (SWG) provide more customized and granular control over web traffic and user activity. This includes setting policies, filtering content, and managing access. Firewalls, on the other hand, have limited control over web traffic and user activity and are mainly focused on controlling network access.
How can a HOST based firewall be a solution for cloud servers not 1 or 2 but 100. dont see HOST based firewall covering the issue
Right Answer is B as SWG is deployed in CLOUD Environments where as host based firewall is Deployed on HOSTS
SWG can help you force policies that can deny/allow traffic on a huge scale instead of configuring 100 firewalls one by one.
imagine configuring 100 Host based firewalls instead of configuring one cluster of reverse proxies to accept and pass the traffic on port 443 to 100 web servers. SWG can be the correct answer here
A secure web gateway (SWG) is a security solution that prevents unsecured internet traffiic from entering an organization's internal network
Key factors to consider: Network size and complexity: SWGs often suit larger, more intricate networks with diverse web traffic. Security priorities: If granular web control and advanced threat protection are paramount, an SWG might be more suitable. Budget and resources: SWGs typically involve additional costs and management overhead compared to host-based firewalls. A network with 100 or more web servers would generally be considered larger and more intricate than networks with fewer servers.
I feel like you're overthinking it
Get full questions with correct answers contact at <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="d3a7bbb6b2fda0bebaa7bbe1e393bca6a7bfbcbcb8fdb0bcbe">[email protected]</a>
Host-based firewall (or personal firewall)—implemented as a software application running on a single host designed to protect that host only. As well as enforcing packet filtering ACLs, a personal firewall can be used to allow or deny software processes from accessing the network. SWG-A software application or gateway that filters client requests for various types of internet content (web, FTP, IM, and so on).
Secure Web Gateway (SWG) is a security solution that prevents unsecured internet traffic from entering an organization's internal network. Cloud-based proxy that enforces standards on URL filtering. I am going with B https://www.comptia.org/blog/sase-secure-access-service-edge
A Secure Web Gateway (SWG) is typically used to protect the network at a perimeter level and focuses on filtering web traffic for security threats, content filtering, and enforcing security policies for outbound web traffic.