Note that you have a fair bit of control over the types of baseline comparison information displayed in your report by using our Report Style Editor. The default is to display ALL test results in your current report, along with notes as to which results are different from the previous report.
|According to your current report style, baseline comparisons are:||Enabled|
|No audit could be found against which a comparison could be done according to the current baselining rules.|
|Denial of Service|
|Windows : User management|
Defined as a "Location Service" in RFC1060, pre-SP3 versions
of Windows NT were susceptible to a denial of service attack
on this port that would cause NT's rpcss.exe process to consume
all available CPU cycles. The (easiest) recovery from this
attack is to reboot your machine.
You should do one of several things: a) upgrade/patch your operating system to make sure it is not susceptible to this attack; b) firewall your system so that port 135 is not visible from the internet c) configure your router to block port 135; d) Install one of several monitoring packages on your PC that block this denial of service.
Port 139 is used on Windows machines for NetBios name resolution,
WINS, etc. A problem with older unpatched versions of Windows is that
they are susceptible to receipt of Out-Of-Band (OOB) data. This means
that someone can remotely send you OOB data on port 139 and can cause
numerous problems on your machine, including but not limited to
machine lockups, blue screens, loss of internet connection.
You should do one of several things: a) upgrade/patch your operating system to make sure it is not susceptible to this attack; b) firewall your system so that port 139 is not visible from the internet c) configure your router to block port 139; d) Install one of several monitoring packages on your PC that block this denial of service.
|Number of open ports found by port scan:2|