Trustwave and Cybereason Merge to Form Global MDR Powerhouse for Unparalleled Cybersecurity Value. Learn More

Trustwave and Cybereason Merge to Form Global MDR Powerhouse for Unparalleled Cybersecurity Value. Learn More

Services
Managed Detection & Response

Eliminate active threats with 24/7 threat detection, investigation, and response.

Co-Managed SOC (SIEM)

Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.

Advisory & Diagnostics

Advance your cybersecurity program and get expert guidance where you need it most.

Penetration Testing

Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.

Database Security

Prevent unauthorized access and exceed compliance requirements.

Email Security

Stop email threats others miss and secure your organization against the #1 ransomware attack vector.

Digital Forensics & Incident Response

Prepare for the inevitable with 24/7 global breach response in-region and available on-site.

Firewall & Technology Management

Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.

Solutions
BY TOPIC
Microsoft Security
Unlock the full power of Microsoft Security
Offensive Security
Solutions to maximize your security ROI
Rapidly Secure New Environments
Security for rapid response situations
Securing the Cloud
Safely navigate and stay protected
Securing the IoT Landscape
Test, monitor and secure network objects
Why Trustwave
About Us
Awards and Accolades
Trustwave SpiderLabs Team
Trustwave Fusion Security Operations Platform
Trustwave Security Colony
Partners
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Trustwave PartnerOne Program
Join forces with Trustwave to protect against the most advance cybersecurity threats
Loading...
Loading...

INFO: Logging Policy not logging certain traffic

Expand / Collapse


  • Description
    A customized logging policy designed to log certain traffic might still not catch that traffic.

  • Symptoms
    When a customized logging policy is created to log certain traffic, in certain situations, there is no logging of the expected traffic.  

  • Cause
    The logging policy is dependant on the Conditions (based on Finjan Content Processors) used in the Security Policy.
    Like in the Security Policy, the conditions in the Log Policy rules are based on the same Content Processors. 
    If a specific Content Processor, e.g., "Direction", was not used during the inspection of the request then a Log Policy rule using that specific Content Processor will not be triggered.

    For example: you create a Logging Policy to log all FTP traffic, but in the Logs, not all FTP traffic is displayed (see screenshot below).

    This is caused by the fact that the Security Policy did not use the "Protocol" Content Processor to inspect the request/response. Therefore, because this Content Processor was not used, the Log Policy using that same Content Processor was not triggered and this traffic was not logged.


  • Solution
    Make sure you that the conditions you use in your logging policy rules are the same as the conditions used in the security policy rules. .
    If you would like to log everything (not advised in production environments), you could use a logging policy that has two rules as follows:

  • Software Version
    8.3.x
    8.4.x
    8.5.0

  • This article applies to:
    NG 1000
    NG 5000
    NG 8000
    This article was previously published as:
    Finjan KB 1480

    To contact Trustwave about this article or to request support:


    Rate this Article:
         

    Add Your Comments


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