This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject

NetWitness Community

  • Home
  • Products
    • NetWitness Platform
      • Advisories
      • Documentation
        • Platform Documentation
        • Known Issues
        • Security Fixes
        • Hardware Documentation
        • Threat Content
        • Unified Data Model
        • Videos
      • Downloads
      • Integrations
      • Knowledge Base
    • NetWitness Cloud SIEM
      • Advisories
      • Documentation
      • Knowledge Base
    • NetWitness Detect AI
      • Advisories
      • Documentation
      • Knowledge Base
    • NetWitness Investigator
    • NetWitness Orchestrator
      • Advisories
      • Documentation
      • Knowledge Base
      • Legacy NetWitness Orchestrator
        • Advisories
        • Documentation
  • Community
    • Blog
    • Discussions
    • Events
    • Idea Exchange
  • Support
    • Case Portal
      • Create New Case
      • View My Cases
      • View My Team's Cases
    • Community Support
      • Getting Started
      • News & Announcements
      • Community Support Forum
      • Community Support Articles
    • Product Life Cycle
    • Support Information
    • General Security Advisories
  • Training
    • Blog
    • Certification Program
    • Course Catalog
    • New Product Readiness
    • On-Demand Subscriptions
    • Student Resources
    • Upcoming Events
  • Technology Partners
  • Trust Center
Sign InRegister Now
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
NetWitness Discussions
Announcement Banner

Users are unable to open Netwitness Support Cases via email. Please open support cases via portal or by phone

View Details
  • NetWitness Community
  • Discussions
  • How many characters does Netwitness query filtering able to afford? 
  • Options
    • Subscribe to RSS Feed
    • Mark Topic as New
    • Mark Topic as Read
    • Float this Topic for Current User
    • Bookmark
    • Subscribe
    • Mute
    • Printer Friendly Page

How many characters does Netwitness query filtering able to afford? 

XueYQ
XueYQ Beginner
Beginner
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

‎2020-01-20 01:58 AM

My rules is to check for hits from the list, which the list might contains quite a huge data. 

For example the rule is: ip.dst = $

    List: 1.1.1.1, 2.2.2.2,......, etc.

    When I drill in to particular hits, the query should be: (ip.dst = 1.1.1.1, 2.2.2.2, ....... +2000 character).

    But it end up to be: (ip.dst = 1.1.1.1, 2.2.2.2, ......., 56.56.56.56

    It stops half way. And having issues of syntax error, which in this case is due to the "(".

    • Community Thread
    • Discussion
    • Forum Thread
    • NetWitness
    • NW
    • NWP
    • Query Issue
    • query-syntax
    • RSA NetWitness
    • RSA NetWitness Platform
    0 Likes
    Share
    Reply
    • All forum topics
    • Previous Topic
    • Next Topic
    1 REPLY 1

    JohnSnider
    Trusted Contributor JohnSnider Trusted Contributor
    Trusted Contributor
    Options
    • Mark as New
    • Bookmark
    • Subscribe
    • Mute
    • Subscribe to RSS Feed
    • Permalink
    • Print
    • Email to a Friend
    • Report Inappropriate Content

    ‎2020-01-20 11:43 AM

    if you are doing this query in RE, then you need to tag the IP's first using a feed, lists should not exceed about 100 entries).  Create a feed from the list to tag the IP addresses in a metakey (I usually create a couple of custom metakeys for my customers, like "customer.info" and "customer.alert" (the "customer" part is usually the Company initials, or a Security team code like CIRC or SOC) and use the .info key for putting values in from rules tagging data for use in alerts of RE/ESA rules) so in your case, create an ip.dst feed to match the list of IP's and create a value in "customer.info" that relates to the rule, like "watchlist_ip", then your RE rule would be: customer.info = 'watchlist_ip'

    2 Likes
    Share
    Reply
    Powered by Khoros
    • Blog
    • Events
    • Discussions
    • Idea Exchange
    • Knowledge Base
    • Case Portal
    • Community Support
    • Product Life Cycle
    • Support Information
    • About the Community
    • Terms & Conditions
    • Privacy Statement
    • Acceptable Use Policy
    • Employee Login
    © 2022 RSA Security LLC or its affiliates. All rights reserved.