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:
|No audit could be found against which a comparison could be done according to the current baselining rules.
|Fedora Local Security Checks
|SuSE Local Security Checks
|Web application abuses
|Debian Local Security Checks
|Ubuntu Local Security Checks
|Huawei EulerOS Local Security Checks
|CentOS Local Security Checks
|Red Hat Local Security Checks
|Mandrake Local Security Checks
|Windows : Microsoft Bulletins
|Gentoo Local Security Checks
|FreeBSD Local Security Checks
|Denial of Service
|Oracle Linux Local Security Checks
|Amazon Linux Local Security Checks
|Slackware Local Security Checks
|Conectiva Local Security Checks
|Mageia Linux Local Security Checks
|Turbolinux Local Security Tests
|Mac OS X Local Security Checks
|Gain a shell remotely
|Nmap NSE net
|Trustix Local Security Checks
|JunOS Local Security Checks
|F5 Local Security Checks
|Remote file access
|Gain root remotely
|SSL and TLS
|AIX Local Security Checks
|CGI abuses : XSS
|VMware Local Security Checks
|Palo Alto PAN-OS Local Security Checks
|FortiOS Local Security Checks
|Citrix Xenserver Local Security Checks
|Windows : User management
|Peer-To-Peer File Sharing
|HP-UX Local Security Checks
|Brute force attacks
|Solaris Local Security Checks
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.
|No description available for this port at this time.
|Number of open ports found by port scan:3
Finally, please note that this list is dependent on the audit you ran. If you come back in a month and run the same audit again, it is likely that this supplement will change, since additional tests will have probably been added to the test suite. Each audit report we produce has its own copy of this supplement that reflects the test suite available at the time this audit was run.
Because of the large size of this report, it may take several minutes for it to be displayed properly on some browsers once the complete report is downloaded (e.g. Netscape). Be patient, it will come up eventually.