You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Numerous sensors log in different formats.  The parser should normalize at least the following subset of fields to the following Metron JSON naming conventions:

 

DescriptionField NameField Value
Any field containing a source IP addressip_src_addrOctets (xxx.xxx.xxx.xxx)
Any field containing a destination IP addressip_dst_addrOctets (xxx.xxx.xxx.xxx)
Any field containing a source portip_src_portInteger
Any field containing a destination portip_dst_portInteger
Any field containing a protocolprotocol

String as a protocol, all caps.

So if protocol = 6, value should be TCP

TimestamptimestampEpoch timestamp (timestamp comes from sensor, not parser)
Message Typetypeyaf|snort|bro|etc...
  • No labels