aclaus225
asked on
PCI DSS Compliance is Failing
Greetings to you. As a business that accepts credit cards we have to get scanned by Control Scan for our PCI DSS compliance.
We are currently failing compliance, but I am not sure how to resolve the problem. My Remote Desktop is the only service running on the IP address and it is on a Windows 2012 server. Most of my errors seem to be generated for systems I do not have, so I am wondering what the problem is. I am running a pfSense router and a Cisco 2900 series router in addition to the W2k12 Remote instance if that helps solve the problem in anyway. As far as I know my computer is fully updated.
Failure areas:
We are currently failing compliance, but I am not sure how to resolve the problem. My Remote Desktop is the only service running on the IP address and it is on a Windows 2012 server. Most of my errors seem to be generated for systems I do not have, so I am wondering what the problem is. I am running a pfSense router and a Cisco 2900 series router in addition to the W2k12 Remote instance if that helps solve the problem in anyway. As far as I know my computer is fully updated.
Failure areas:
Buffer overflow in RegAPI.DLLCVE-2000-1149
used by Windows NT 4.0
Terminal Server allows remote
attackers to execute arbitrary
commands via a long
username, aka the "Terminal
Server Login Buffer Overflow"
vulnerability.
Remote Data Protocol (RDP)CVE-2002-0863 (When I looked, the version that I am at is 6.3.9600.17415).
version 5.0 in Microsoft
Windows 2000 and RDP 5.1 in
Windows XP does not encrypt
the checksums of plaintext
session data, which could allow
a remote attacker to determine
the contents of encrypted
sessions via sniffing, aka
"Weak Encryption in RDP
Protocol."
The RC4 algorithm, as used inCVE-2015-2808
the TLS protocol and SSL
protocol, does not properly
combine state data with key
data during the initialization
phase, which makes it easier
for remote attackers to conduct
plaintext-recovery attacks
against the initial bytes of a
stream by sniffing network
traffic that occasionally relies
on keys affected by the
Invariance Weakness, and
then using a brute-force
approach involving LSB values,
aka the "Bar Mitzvah" issue.
The RC4 algorithm, as used inCVE-2013-2566
the TLS protocol and SSL
protocol, has many single-byte
biases, which makes it easier
for remote attackers to conduct
plaintext-recovery attacks via
statistical analysis of ciphertext
in a large number of sessions
that use the same plaintext.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER