- Community Home
- >
- Networking
- >
- Legacy
- >
- TippingPoint
- >
- Converting Snort rules to tipping point filters wi...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2014 06:13 PM
02-27-2014 06:13 PM
Converting Snort rules to tipping point filters with dv converter
I have had a few filters when converted had a content section fail the conversion because content was empty. Snort ID 21070 for example. When I add this rule to the converter it fails conversion because it doesn't have at least one string content set to match. In order to fix this based on the examples in the help, I am supposed to add something from the payload to match. Based on glancing at this rule I believe I should add "?spl=2" to the string match content so that the conversion tool is happy. Am I right or am I wrong?
Question 2:
What should we do to solve the issue of matching less than 5 characters in a string content match? There are certain rules that have 3 or 4 characters to match against in the snort rule.