I just performed a policy update for a v2.6 sensor from BleedingThreats. When I uploaded the policy, Snort failed to restart because all of the rules I had disabled, the ones beginning with "bleeding" and having "BLOCK" in their name, got re-enabled and "fwsam" is not being used. I'm using IDSPM v2.1.0.15.
I disabled them all and uploaded the policy again. This time all was well. Any idea why it re-enabled those disabled alerts?
Also, I changed the "redalert" Custom Rule Type configuration, which required me to create a new database output and delete the old one. When I went to upload the policy using "fast" nothing happened. I had to change it to "update". It's like "fast" isn't checking to see if the snort.conf file was changed.
It also would be very nice if I could double-click the Custom Rule Type output statement and modify the existing one instead of having to create a duplicate, slightly modified, and then delete the original.
Thanks,
Ray