Skip to main content

LevelBlue Named Official Cybersecurity Advisor of the PGA of America. Learn more

LevelBlue Named Official Cybersecurity Advisor of the PGA of America. Learn more

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
PGA of America Partnership
Secure What's Next
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

INFO: Why does Security Reporting Center only analyze the 'messages' and 'connections' logs of a Borderware firewall?

Expand / Collapse


This article applies to:

  • Security Reporting Center 2.1

Question:

Why does Security Reporting Center only analyze the 'messages' and 'connections' logs of a Borderware firewall?

Information:

Security Reporting Center (SRC) only analyzes the 'connections' and 'messages' logs from Borderware. It does this because the other logs that the Broderware firewall generates generally contain duplicate data unnecessary for SRC reporting. For example, the Borderware generated security logs are a packet by packet log of the data coming through the firewall. SRC does not support this granular level of data. However, for each set of packets for a given IP, there is a corresponding log line in the 'connections' log that summarizes the whole transfer.  This data is reported on by SRC. 

There is no usable valid data for SRC in any of the other Borderware logs. In most cases SRC needs a time, source IP, destination IP, and port to generate valid reports, however, there are exceptions with other proprietary log formats like Cisco PIX.

This article was previously published as:
NETIQKB46819

To contact LevelBlue about this article or to request support:


Rate this Article:
     
Tags:

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.