PCI compliance --
PCI compliance failed.
Hi there experts,
A customer asked me to look at why their pci scan failed. The failing row shows TLS v.1.0, the public IP address, and 3389 port. Evidently it failed because of TLSv1 but I can't find the source of it. At first I thought port forwarding was enable on the router but it was not the case, then i checked to see if the server we added months ago had rdp enabled, it didn't. I then ran an nmap scan and and 3389 is not open on any host. My hypothesis is that a host (may be a laptop) with rdp enabled was connected to the network at the time of the scan but they told me that was not the case. I scheduled another scan but it won't run until tomorrow...
Has anyone dealt with something like this before? can the scan show that's a tls v1 on a port that's not enabled?
Hi there experts,
A customer asked me to look at why their pci scan failed. The failing row shows TLS v.1.0, the public IP address, and 3389 port. Evidently it failed because of TLSv1 but I can't find the source of it. At first I thought port forwarding was enable on the router but it was not the case, then i checked to see if the server we added months ago had rdp enabled, it didn't. I then ran an nmap scan and and 3389 is not open on any host. My hypothesis is that a host (may be a laptop) with rdp enabled was connected to the network at the time of the scan but they told me that was not the case. I scheduled another scan but it won't run until tomorrow...
Has anyone dealt with something like this before? can the scan show that's a tls v1 on a port that's not enabled?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
1) Can the firewall be managed remotely?
2) What is RDP in use for? RDP would fail for PCI compliance. Require that users connect to the VPN first, then RDP in. That way, you can close port 3389 open on your firewall.
3) Have you checked the registry on the Windows server? Scroll to the appropriate TLS version in this MS article: https://docs.microsoft.com