You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: UPGRADING.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,3 +81,12 @@ The following REST API changes are a direct result of this rework:
81
81
|`POST /plugins/org.graylog.plugins.securityapp.sigma/sigma/rules/import`| Moved to `POST /plugins/org.graylog.plugins.securityapp.sigma/sigma/import/bulk/import`|
82
82
|`POST /plugins/org.graylog.plugins.securityapp.sigma/sigma/rules/upload`| Moved to `POST /plugins/org.graylog.plugins.securityapp.sigma/sigma/import/bulk/upload`|
83
83
| All other `/plugins/org.graylog.plugins.securityapp.sigma/sigma/rules/...`| Deleted |
84
+
85
+
## Threat Coverage Percentages May Change After Upgrade
86
+
87
+
Due to the migration of Sigma rules to Event Definitions in 7.2, the percentages displayed in the Threat
88
+
Coverage widget may be different from what they were in 7.1. Coverage is now computed directly from Event
89
+
Definitions rather than from the previous Sigma rules. Every Event Definition with MITRE tactics/techniques
90
+
assigned is now included, and coverage reflects how many of them are enabled versus disabled (with no log
91
+
source check that was previously present for Sigma rules). Therefore, a tactic may show a higher or lower
92
+
percentage than it did in 7.1, without any change to the actual installed Event Definitions.
message = "Fix problem in `GET /messages/{index}/{messageId}`. Permission requirements introduced by previous security fix have been too strong, they have been relaxed."
0 commit comments