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...

FAQ: How to log HTML Repaired transactions?

Expand / Collapse


  • Question
    One of the most valuable services provided by Finjan Vital Security for Web appliances is the ability to track the processed information in the logs.

    By default, VSOS 8.5.0 and above provides the following logging policies:

       - Log All Protective Actions;

       - Log All Protective Actions and Web Pages;

       - Logging everything except Image files;

    The extended logging policy, logging everything except Image files, provides detailed information. However, it has very important constraint causing huge I/O load to the system.

    The HTML Repair feature causes malicious scripts on an HTML page to be automatically detected and repaired, and the HTML page is sent on to the end-user in a transparent manner. 
    Note: The HTML Repair feature is enabled by default.

    Ability to log HTML repaired transcations is one of the reasons users might consider using this logging policy instead of any other alternative.

    This article describes how to create new logging policy that combines the flexibility of the data being logged with the minimal load caused to the system.


  • Answer
    1. Browse to the Policies section of the management console of Finjan VSOS 8.5.0 and expand the logging policies node.

    2. Highlight the default, Log All Protective Actions, logging policy and click Duplicate button on the top as shown below:

    3. Set Log Defaults and HTML Repaired Transactions for this new logging policy:

    4.  Highlight new logging policy and click New Rule button:

    5. Rule editor windows pops up. Set this rule conditions as shown below and click OK.

    (Set send to archive/log/report/syslog options according to your preferrences)

    5. Decide what should be the place/priority of this rule and move it down with the up/down icons.

    Save the policy before you commit these changes.

    6. Commit these changes.

    7. Browse to the Users section and set this logging policy for specific user(s) or group(s):

    8. Apply and commit the changes.

  • Software Version
    8.5.0

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

    To contact LevelBlue 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
    .