Report Styles   Administrator | Executive Summary | Unbranded Exec. Summary
Desktop Security Audit (Sample)    
SAMPLE: SecuritySpace Audited Web Site
Report ID3
View Created On:Jan 1, 1970 00:00 GMT
Host Address(es):X.X.X.X
Report Contents
1. Risk Classification Summary
Vulnerabilities are classified according to the risk they present to the network/host on which they are found. The following chart summarizes how the 0 different issues we found are spread across the different risk classes. For a detailed explanation of how vulnerabilities are classified, see Appendix A: Risk Definitions
0,0,0,0
2. Baseline Comparison Control
Baselining allows you to compare the results of an audit to the results received in a previous audit. This provides for an easy way to see what is changing from one audit to the next. This section documents which audit was used as a baseline, allows you to select a different audit to use as a baseline, and allows you to mark the current audit as something that should be used when running future baseline comparisons.

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.

3. Vulnerability Category Summary
The vulnerability category summary shows how the various issues that were reported are distributed across the different test categories.

CategoryHigh  Med  Low  Other  
Denial of Service     
Windows     
Backdoors     
Misc.     
Windows : User management     
Firewalls     
Totals:0  0  0  0  

4. Vulnerability Title Summary
5. Vulnerability Details
6. Open Ports - X.X.X.X
Port   Protocol   Probable Service  
135  TCP loc-srv
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.

 
139  TCP netbios-ssn
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
 
Appendix A: Risk Definitions
Users should note that test classifications are subjective, although we do our best to make appropriate classifications. If you spot an inconsistency, please let us know so that we can make the appropriate corrections.

AppendixB: CVE Versioning
CVE identifiers, an industry standard way of identifying tests, are maintained by Mitre. The current mapping of CVE/CAN identifiers to Test IDs is based on CVE Version Number 20211016, and CAN Version Number 20211016. These were verified on October 16, 2021 as being the latest available.


© 1998-2024 E-Soft Inc. All rights reserved.