Hello.
I use ISS product but can't find on product documentation / KB information on the new features mentioned.
On 31/12/2004 10.16, Maynor, David (ISS Atlanta) wrote:
The oldest phase captured the data and wrote to the sensors disk. TheWhere can I find documentation on this new features (I use ISS product and still use the "old methods")? What ISS product can benefit this features? Can I have the PCAP file that triggered a specific attack (not a big PCAP file with all the capture of all the attack detected with the log packet enabled)?
file was stored in a "Sniffer" format or could be configured to use
tcpdump format. This could eat up a lot of space and could become a
performance/maintenance nightmare.
The current method in use improves the original method by allowing the captures to be sent to the management console.
When is it planned and on which ISS product (proventia A/G/M Series, Linux 100 Network Sensor, Linux Gigabit Network sensor)?The newest method which should be released soon has adopted a modified libpcap interface. This allows an admin to ssh to a sensor and grab the packets with something like tcpdump or tethereal.
[...]The initial version of TRONS sat outside of PAM. Per Rob Graham, the performance sucked. It was designed to use with less than 50 rules and because it was outside of the main PAM module rule processing was severely impacted.
Luckily that version is dead and gone.
The latest version of TRONS is integrated into PAM and has done away
with the originals performance problems.
The actual format has changed very little. Where as before a user would do something like:
trons.rule=alert tcp any any -> any ...
The new version is a simple change like:
pam.trons.rule=alert tcp any any -> any ...
Where can I find documentation for this new way of defining trons rules? On ISS KB I can still find a document of 2 years ago about the "classic trons".
Is the ACE Engine and Event Propagation posssibile on this new type of trons event? Do you support the Thresholding features of snort in Trons? (something that limit the number of event written on the DB is very useful not to DOS the DB and the management platform in case of worm).
Best Regards,
Massimo
_______________________________________________
ISSForum mailing list
[email protected]TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo/issforum
To contact the ISSForum Moderator, send email to [EMAIL PROTECTED]
The ISSForum mailing list is hosted and managed by Internet Security Systems, 6303 Barfield Road, Atlanta, Georgia, USA 30328.
