WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!
Questions on windows ports
We are using Comodo Internet Security Premium version 8.4.0.5076. Recently we were recommended to close all unused ports in each PC; we only needed the ports opened such as:
- Port 53 (for DNS)
- Port 80 (for Http)
- Port 443 (for SSL secure browsing)
- Port 8080 (for secondary port)
And close all other ports as follows:
- Block 0-52
- Block 53-79
- Block 81-443
- Block 444-8079
- Block 8081-65535
That seems to make sense but we have these questions about apps used in some computers, such as:
- Port 53 (for DNS)
- Port 80 (for Http)
- Port 443 (for SSL secure browsing)
- Port 8080 (for secondary port)
And close all other ports as follows:
- Block 0-52
- Block 53-79
- Block 81-443
- Block 444-8079
- Block 8081-65535
That seems to make sense but we have these questions about apps used in some computers, such as:
Remote Desktop
SQL
Google Drive
OneDrive
Mega cloud
DropBox
Box
iCloud
Hyper-V
SQL
Google Drive
OneDrive
Mega cloud
DropBox
Box
iCloud
Hyper-V
What do EE recommend as to the open and closed ports?
Is the recommendation of closing non-used ports a good one?
Finally, based on the list of apps, what ports do these apps uses so we can open them?
Is the recommendation of closing non-used ports a good one?
Finally, based on the list of apps, what ports do these apps uses so we can open them?
Asked:
-
6
4
3
3 Solutions
LVL 20
Windows Remote Desktop uses port 3389 by default. SQL Server uses port 1433 by default. If you have additional SQL Server instances then they will use a different, randomly selected port. Hyper-V doesn't use any ports in and of itself. I'm not 100% certain about the other services but I believe those are mostly outbound connections. To enhance your system's security you need only create inbound rules which shouldn't affect cloud services.
A recommendation to block outbound traffic is usually too much, unless you need to create a fully controlled network. As said above, you block inbound traffic first. Then you should know which ports are used - if someone needs to RDP into a machine, that (target) machine needs to have RDP opened for inbound. If there is no need to at any time (even for administrative tasks), the port should be blocked inbound.
In general, if you provide a service on a machine (RDP etc.), open the inbound port. Don't block outbound, unless there is a specific need.
In general, if you provide a service on a machine (RDP etc.), open the inbound port. Don't block outbound, unless there is a specific need.
Great info!
As for the apps:
Based on your recommendation, how can we determine inbound ports for the above apps or connections?
As for the apps:
- Remote Desktop
- SQL
- Google Drive
- OneDrive
- Mega cloud
- DropBox
- Box
- iCloud
- Hyper-V
- SQL
- Google Drive
- OneDrive
- Mega cloud
- DropBox
- Box
- iCloud
- Hyper-V
Based on your recommendation, how can we determine inbound ports for the above apps or connections?
What about hyper-v (especially if we connect to one outside our PC and also if we have one in our PC)
Hyper-V doesn't inherently use any ports. The virtual machines that Hyper-V hosts may use ports. However the host firewall doesn't apply to the hosted VMs.
But if from within the VM there is malicious code and the VM has access to host or the PC connected to it, wouldn't that also infect the host? For example, we have a VM that you can ping the host or the PC you connecting from and in additional, the VM from within has access to the host drives. That said, the ports are not considered here?
A VM is just like any other computer. It has no more access to the host machine than you give it. If you configure the VM to use the host's network adapter then it is as if the VM is on the same network and is subject to the same network rules as any other machine.
If it helps, for the purpose of networking thing of a VM as another physical computer sitting next to the current one and connected to the same network. That's the extent of it.
If it helps, for the purpose of networking thing of a VM as another physical computer sitting next to the current one and connected to the same network. That's the extent of it.
Understood.
To close the question, and going back to the original question, should we set as closed the following ports in our firewall apps?:
- Block 0-52 - (leave 53, dns open)
- Block 54-79 - (leave 80, http open)
- Block 81-442 - (leave 443, ssl open)
- Block 444-1432 - (leave 1433, sql open)
- Block 1434-3388 - (leave 3389, rdp open)
- Block 3390-8079 - (leave 8080, alt,port open)
- Block 8081-65535
(we have updated the list of "open" ports [SQL port 1433 and RDP port 3389] with EE comments placed)
To close the question, and going back to the original question, should we set as closed the following ports in our firewall apps?:
- Block 0-52 - (leave 53, dns open)
- Block 54-79 - (leave 80, http open)
- Block 81-442 - (leave 443, ssl open)
- Block 444-1432 - (leave 1433, sql open)
- Block 1434-3388 - (leave 3389, rdp open)
- Block 3390-8079 - (leave 8080, alt,port open)
- Block 8081-65535
(we have updated the list of "open" ports [SQL port 1433 and RDP port 3389] with EE comments placed)
No port should be open unless you have a need for it.
Port 53 should be open only if the machine is a DNS server.
Ports 80 and 443 should only be open if the machine is hosting a website.
Port 1433 should only be open if the machine is hosting a SQL Server instance.
Port 3389 should only be open if the machine needs to accept Windows RDP requests.
Port 8080 should only be open if you need to host an additional website on this port.
Side note, it's generally considered poor security to host a SQL Server instance on the same machine as a website. If you must do this and the SQL Server instance is consumed only by the website then there is no need to open port 1433 since the IP address will be local (127.0.0.1) which should never be blocked.
Port 53 should be open only if the machine is a DNS server.
Ports 80 and 443 should only be open if the machine is hosting a website.
Port 1433 should only be open if the machine is hosting a SQL Server instance.
Port 3389 should only be open if the machine needs to accept Windows RDP requests.
Port 8080 should only be open if you need to host an additional website on this port.
Side note, it's generally considered poor security to host a SQL Server instance on the same machine as a website. If you must do this and the SQL Server instance is consumed only by the website then there is no need to open port 1433 since the IP address will be local (127.0.0.1) which should never be blocked.
This question we have placed in EE is for a computer that the we need to connect to via Remote Desktop (when in LAN) and connect to via TeamViewer (outside our LAN, i.e. From our home).
When we are connected to this computer via RDP or Teamviewer, we want to use it's MSSQL apps, some VMs and cloud services it has. These services are used when we sit down front of the PC or when connected.
Based on your comment, we can close all ports except 3389?
When we are connected to this computer via RDP or Teamviewer, we want to use it's MSSQL apps, some VMs and cloud services it has. These services are used when we sit down front of the PC or when connected.
Based on your comment, we can close all ports except 3389?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!
Tackle projects and never again get stuck behind a technical roadblock.
Join Now