-
Notifications
You must be signed in to change notification settings - Fork 35
/
json-input.map
77 lines (58 loc) · 4.75 KB
/
json-input.map
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
# Sagan json-input.map.rules
# Copyright (c) 2009-2020, Quadrant Information Security <www.quadrantsec.com>
# All rights reserved.
#
# Please submit any custom rules or ideas to [email protected] or the sagan-sigs mailing list
#
#*************************************************************
# Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
# following conditions are met:
#
# * Redistributions of source code must retain the above copyright notice, this list of conditions and the following
# disclaimer.
# * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
# following disclaimer in the documentation and/or other materials provided with the distribution.
# * Neither the name of the nor the names of its contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES,
# INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
# DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
# SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
# USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
#*************************************************************
# If your named pipe (FIFO) is being feed JSON data, this is where you'll want to "map"
# it so Sagan understands it.
# ------------------------------------------
# Standard syslog-ng template.
# ------------------------------------------
{"software":"syslog-ng","syslog-source-ip":".SOURCEIP","facility":".FACILITY",".level":".PRIORITY","priority":".PRIORITY","time":".DATE","date":".DATE","program":".PROGRAM","message":".MESSAGE"}
# ------------------------------------------
# Various rsyslog formats
# ------------------------------------------
{"software":"rsyslog","syslog-source-ip":".fromhost-ip","facility":".syslogfacility","level":".syslogseverity","priority":".pri","tags":".syslogtag","time":".timereported","date":".timereported","program":".programname","message":".msg"}
{"software":"rsyslog-alt","syslog-source-ip":".fromhost-ip","facility":".syslogfacility-text","level":".syslogseverity-text","priority":".pri","tags":".syslogtag","time":".time","date":".date","program":".programname","message":".msg"}
# ------------------------------------------
# nxlog
# ------------------------------------------
{"software":"nxlog","syslog-source-ip":".MessageSourceAddress","facility":".SyslogFacility","level":".SyslogSeverity","priority":".Severity","time":".EventTime","date":".EventTime","program":".SourceName","message":".Message"}
{"software":"nxlog-straight","syslog-source-ip":".HOST_FROM","facility":".Severity","level":".Severity","priority":".Severity","time":".EventReceivedTime","date":".EventReceivedTime","program":".SourceName","message":".Message","event_id":".EventID"}
# ------------------------------------------
# journald
# ------------------------------------------
# This is for journald support. When the command "sudo journalctl -f -o json", journald will output JSON. This JSON
# can be redirected to a named pipe and Sagan and analyze incoming data. Unforunately, I don't see a way to display
# ISO8601 timestamps in JSON
{"software":"journald","hostname":"._HOSTNAME","facility":".SYSLOG_FACILITY","level":".PRIORITY","priority":".PRIORITY","time":".__REALTIME_TIMESTAMP","date":".__REALTIME_TIMESTAMP","program":"._COMM","message":".MESSAGE"}
# ------------------------------------------
# Microsoft Office365 API
# ------------------------------------------
{"software":"msapi", "program":".Workload", "time":".CreationTime", "date":".CreationTime", "message":"%JSON%", "src_ip":".ClientIP|.SenderIp", "dst_ip":".ClientIP|.SenderIp"," username":".UserId" }
# ------------------------------------------
# Custom formats
# ------------------------------------------
{"software":"quadrant", "syslog-source-ip":".src", "facility":".facility", "level":".level", "priority":".priority", "time":".receive_date", "date":".receive_date","program":".program","message":".message"}
{"software":"quadrant1","syslog-source-ip":".src","facility":".facility","level":".level","priority":".priority","time":".eventdate","date":".eventdate","program":".program","message":".message"}