Archive
Highlighted

Cisco App - Pix inbound vs outbound

Communicator

I have been looking at the Cisco Pix App and the transforms for src and dest ip. What I noticed is that the src and dest ip are extracted in the same position in both the outbound and inbound built messages.

From my understanding of the syslog messages, the location of src and dest ip flip depending on the inbound and outbound keyword in the built statement.

Is this correct and should i change the default behaviour for the [cisco-firewall-to_addr_port] and [cisco-firewall-from_addr_port]

As is:

[cisco-firewall-to_addr_port]
REGEX = \s+to (?:([\w-_]+):)?([^ /]*)(?:/(\S+))?\s*
FORMAT = dest_dom::$1 dest_ip::$2 dest_port::$3

To:

[cisco-firewall-inbound-to_addr_port]
REGEX =inbound.*\s+to (?:([\w-_]+):)?([^ /]*)(?:/(\S+))?\s*
FORMAT = dest_dom::$1 dest_ip::$2 dest_port::$3

and: [cisco-firewall-outbound-to_addr_port] REGEX = outbound\s+(?:from|for(?! user)) (?:([\w-_]+):)?([^ /])(?:/(\S+))?\s FORMAT = dest_dom::$1 dest_ip::$2 dest_port::$3

Tags (2)
0 Karma
Highlighted

Re: Cisco App - Pix inbound vs outbound

SplunkTrust
SplunkTrust

Can you provide sample events to go with this?

0 Karma
Highlighted

Re: Cisco App - Pix inbound vs outbound

Motivator
Highlighted

Re: Cisco App - Pix inbound vs outbound

Communicator

That works better, have a few tweaks to it but works much better than it did before.

thanks

0 Karma