Logging practices for security logging.

[misteryuku]

I would like to create log messages that would be used for log analysis using Splunk such as checking for occurence of Denial of Service attacks. What would be the best logging practices for that as in what are the most important information that i should be displaying in the log messages???

[elusive]

Hi. The link you have provided above does not work anymore. It seems like the pages has changed. Can you provide the link again? thanks!

[gjanders]

The common information model has it's own manual in particular you may wish to refer to using the CIM and the examples of using the CIM

[ziegfried]

This is a good place for getting started:

• http://dev.splunk.com/view/logging-with-splunk/SP-CAAADP5
• http://dev.splunk.com/view/logging-best-practices/SP-CAAADP6

In addition, naming field according to the CIM (Common Information Model) would be a good idea:

• http://docs.splunk.com/Documentation/ES/latest/CreateTA/CommonInformationModelFieldReference

[misteryuku]

Okay. i see...

[ziegfried]

something like allowed/blocked or success/failure. whatever is more reasonable.

[misteryuku]

What does the action field for the network protection/traffic represent? Does it represent the action of the packet??

[ziegfried]

Yup. Network Protection/Traffic might be the best choice.

[misteryuku]

Lets say if i want to monitor the traffic of the network as in detecting Denial of service attacks, the log message should contain the fields under the network protection category of the Common Information Model. Is that true?