Skip to content

Commit dd7a491

Browse files
committed
Severity field in IDF
Severity is expected in IntelMQ for a long time and partially, it's already used by e.g. ShadowServer reports. This implementation is based on their understanding of the field, but with explicit mentioning that operators could adjust it based on their knowledge. This is not intended to be an ultimate severity classification, but a help for first triage of recived events. Close #2365
1 parent aadc887 commit dd7a491

File tree

2 files changed

+9
-0
lines changed

2 files changed

+9
-0
lines changed

CHANGELOG.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,9 @@ Please refer to the [NEWS](NEWS.md) for a list of changes which have an affect o
2121

2222
### Data Format
2323

24+
- added `severity` field to help with triaging received events (PR# by Kamil Mańkowski).
25+
To allow saving the field in PostgreSQL database in existing installations, the following schema update is necessary: `ALTER TABLE events ADD severity varchar(10);`.
26+
2427
### Bots
2528
#### Collectors
2629

intelmq/etc/harmonization.conf

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -362,6 +362,12 @@
362362
"tlp": {
363363
"description": "Traffic Light Protocol level of the event.",
364364
"type": "TLP"
365+
},
366+
"severity": {
367+
"description": "Severity of the event, based on the information from the source, and eventually modified by IntelMQ during processing. Meaning of the levels may differ based on the event source.",
368+
"type": "LowercaseString",
369+
"regex": "^(critical|high|medium|low|info|undefined)$",
370+
"length": 10
365371
}
366372
},
367373
"report": {

0 commit comments

Comments
 (0)