mirror of https://github.com/MISP/misp-website
fix: wrong file committed before...
parent
77b4f91305
commit
a7aab0466c
|
@ -4,43 +4,45 @@ layout: post
|
|||
featured: /assets/images/misp/blog/ss7-example.png
|
||||
---
|
||||
|
||||
# MISP 2.4.141 released
|
||||
# MISP 2.4.142 released
|
||||
|
||||
MISP 2.4.141 released including many improvements from email notification, UI, API and installation scripts.
|
||||
MISP 2.4.142 released including many new features, a security fix and a long list of quality of life improvements.
|
||||
|
||||
# User-Interface
|
||||
# Correlation changes
|
||||
|
||||
- [UI] Render galaxy cluster description as markdown.
|
||||
- [UI] Show threat level icons on event index.
|
||||
- [eventgraph:viewPicture] Allow access to saved picture from the eventgraph history.
|
||||
- [eventGraph] Improved object coloring strategy.
|
||||
- [UI] fix debugon for debug = 1. fix #7131.
|
||||
- [UI] Show number of items in freetext feed.
|
||||
- [UI] Make feed event preview nicer.
|
||||
- [UI] It is 2021! Removed -moz and -webkit specific CSS properties.
|
||||
- [UI] Make some parts of MISP nicer.
|
||||
- [UI] Nicer pivots.
|
||||
- [UI] Simplify keyboard-shortcuts.js.
|
||||
- [UI] Use Page Visibility API.
|
||||
One of the most annoying bottlenecks in how we use MISP currently is caused by low quality correlations, both in terms of usability and having a clear view on relevant relationships among data-points. These very often come from either sub-optimal strategies chosen on data creation/ingestion for certain types of attributes, but very often also on edge cases.
|
||||
|
||||
and many more updates check the [changelog for details](https://www.misp-project.org/Changelog.txt).
|
||||
With the current release we've included two main tools to combat this:
|
||||
|
||||
# Email notification
|
||||
### Correlation exclusions
|
||||
|
||||
Email notification has been significantly improved and now support HTML emails.
|
||||
We can now remove individual values from ever correlating again, so if you come across some typical noisy values (such as empty file hashes, registry values of 000000, internal IPs recurringly encoded by your sandbox), you can add those to the exclusion list.
|
||||
|
||||
- [email] New setting `MISP.event_alert_metadata_only`.
|
||||
- [email] Command for testing generated alert email.
|
||||
- [email] Allow to set email subject from template.
|
||||
- [email] Back-end support for sending HTML emails.
|
||||
Once added, you can execute the cleaning of the existing correlations, to retroactively execute your exclusion rules. This is a background processed task and depending on the amount of correlations you have may take quite some time (it took us around 10 minutes on 25M correlations), so just fire it off and check back later whether the job has completed.
|
||||
|
||||
This release includes many updates in the local and translation of the user-interface.
|
||||
You can also comment your reason for removing an entry. In the future we plan on publishing community maintained default exclusion lists.
|
||||
|
||||
New default feeds were included in MISP such as the newest [DataPlane.org feeds](dataplane.org).
|
||||
### Top correlations
|
||||
|
||||
# Installation scripts and guides
|
||||
List the most correlating values in your instance - in order to evaluate which the most problematic correlations are, simply have a look at the most noisy correlations. We've had some surprising entries in our communities, so perfect time to do some spring cleaning.
|
||||
|
||||
Many improvement in the RHEL7, 7.9 and CentOS8Stream. We thank all the users reporting issues with RHEL.
|
||||
Just hit the delete button on a correlation and it will add a rule to your correlation exclusion list - just don't forget to run the historic cleanup from the correlation exclusion index to remove already existing correlatins matching your newly added rules.
|
||||
|
||||
# Server sync rule management rework
|
||||
|
||||
One of the more painful aspects of managing servers has been the historically bad UI used to manage filter rules. This has now been completely revamped, both with a new look but familiar look and feel as well as some clever new tools to make it more usable.
|
||||
|
||||
For example, when creating pull filters, your instance will now attempt to contact the remote instance to retrieve a list of available tags, so that you no longer have to manually enter all of the filters when creating pull rules. The JSON rule field allowing custom fielters now also uses a handy JSON parsing text entry, allowing you to avoid potential mistakes.
|
||||
|
||||
# New dashboard widgets
|
||||
|
||||
Thanks to Jeroen Pinoy, we have some new dashboard widgets meant to give you better oversight over how your instance is being used, showing some usage statistics as well as tools to monitor the growth of the userbase of the community.
|
||||
|
||||
# A bunch of other fixes including security fixes
|
||||
|
||||
We have also a security issue (CVE-2021-31780) causing a potential misalignment of sharing groups on synced attributes, so we highly encourage everyone to update their MISP instance.
|
||||
|
||||
Besides that we have introduced a long list of quality of life improvements as well as ug fixes.
|
||||
|
||||
# Acknowledgement
|
||||
|
||||
|
|
Loading…
Reference in New Issue