Skip to content
This repository has been archived by the owner on Jan 18, 2024. It is now read-only.

Usage of alert_fwsam module in barnyard.config #142

Open
alligatorwine opened this issue Mar 18, 2015 · 1 comment
Open

Usage of alert_fwsam module in barnyard.config #142

alligatorwine opened this issue Mar 18, 2015 · 1 comment

Comments

@alligatorwine
Copy link

Hi everyone,
I am running Snort in passive mode and I would like it to communicate with my Cisco ASA 5510. I know that Snortsam should do the job, but it looks like Snortsam code is now directly integrated in Barnyard (alert_fwsam module in barnyard.config).
Does anyone know how to configure it?
Thanks in advance.

Antonella

@binf
Copy link
Collaborator

binf commented Mar 19, 2015

Greetings,

The basic documentation can be found here
https://github.com/firnsy/barnyard2/blob/master/doc/README.snortsam

The sid-block.map or sid-fwsam.map need to be in the config directory
specified by command line for the configuration file.

So in a way you need to have snortsam setup somewhere that would interract
with your fw
and by2 would communicate with snortsam the later who would act on the fw
devices.

For the record the good documentation about the snortsam "agent" it self
can be found here.

http://doc.emergingthreats.net/bin/view/Main/SnortSamDocumentation
Refered from : http://www.snortsam.net/docs.html

Hope this helps.
(by2 only provide the alerting bridge from unified2 processing)

-elz

On Wed, Mar 18, 2015 at 4:54 AM, Antonella Angelini <
notifications@github.com> wrote:

Hi everyone,
I am running Snort in passive mode and I would like it to communicate with
my Cisco ASA 5510. I know that Snortsam should do the job, but it looks
like Snortsam code is now directly integrated in Barnyard (alert_fwsam
module in barnyard.config).
Does anyone know how to configure it?
Thanks in advance.

Antonella


Reply to this email directly or view it on GitHub
#142.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants