Go to the table of contents Go to the previous page You are at the end of the document View or print as PDF
Using TestLogServer for Web Security Troubleshooting : Understanding TestLogServer output
Understanding TestLogServer output
Topic 50333 | TestLogServer | Web Security Solutions | Version 7.7, 7.8 | Updated 19-Sept-2013
When you run TestLogServer, the output includes the following information, if available.
If you have installed Websense Multiplexer and enabled SIEM integration in TRITON - Web Security, an additional SIEM Results section appears in the TestLogServer output. The SIEM Results section includes the following information:
The output for each request looks something like this:
Log Source= Integration
Client Hostname= 10.201.136.35
SourceIp= 10.201.136.35
DestinationIp= 74.125.128.104
server= 10.201.136.130
time= Mon Mar 26 11:49:35 2012
version= 6
disposition= 1026 - Category Not Blocked
URL= http://www.google.com/
protocol= 1 - http
port= 80
networkDirection= Inbound
method= GET
contentType = text/html;
charset=UTF-8
category= 76 - SEARCH ENGINES AND PORTALS
categoryReason= 1 - Master Database: URL
bytes sent= 647
bytes received= 24041
file name=
True File Type= 6 - Text
roleId= 8
user= WinNT://QA/qauser
duration= 719 ms
scan duration= 0 ms
policyName= role-8**Default
SIEM Results
protocol version= 257
server status code= 200
proxy status code= 200
client source port=49372
client destination port= 8080
proxy source=10.201.136.130
proxy source port= 26615
user agent= Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
 

Go to the table of contents Go to the previous page You are at the end of the document View or print as PDF
Using TestLogServer for Web Security Troubleshooting : Understanding TestLogServer output
Copyright 2016 Forcepoint LLC. All rights reserved.