MISP
/
misp-website
mirror of https://github.com/MISP/misp-website
2
0
Fork 0
Code Issues Releases Wiki Activity

minor grammar fixes

pull/14/head
iglocska 2019-08-31 13:39:24 +02:00
parent aa6a1c40e2
commit 075d9bd148
No known key found for this signature in database
GPG Key ID: BEA224F1FEF113AC
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
_posts/2019-08-31-MISP.2.4.114.released.md
View File

@ -11,7 +11,7 @@ A new version of MISP ([2.4.114](https://github.com/MISP/MISP/tree/v2.4.114)) wi
## Letting the world know about your community
One of the most common requests we get from users is whether we can point them to a community that would fit their profile and needs. This is something that often leaves as stumped. Being an open source project, we only really know the part of our user-base that we directly interact with and even if they do, the question of whether we should point users in their directions in the first place is often a puzzling one.
One of the most common questions we get from users is whether we can point them to a community that would fit their profile and needs. This is something that often leaves as stumped. Being an open source project, we only really know the part of our user-base that we directly interact with and even if they do, the question of whether we should point users in their directions in the first place is often a puzzling one.
We've decided to make everyone's life just a tad bit easier. By incorporating an in-application registry of known communities, we not only allow organisations that run an ISAC or other sharing community to let potential new community members know that they exist in the first place, but also we also allow anyone with a MISP installation to conveniently send requests to communities for access.
@ -33,7 +33,7 @@ Added a new diagnostic tool that allows administrators to keep track of the data
## Taxonomies improved with the addition of an Industrial control systems and operational technology (ICS/OT) Taxonomy
Industrial control systems and operational technology (ICS/OT) are often target of threats, intrusions and attacks. The [FIRST.org Cyber Threat Intelligence SIG](https://www.first.org/global/sigs/cti/) did a tremendous work of documenting ICS/OT into a series of taxonomies. To support and actively test the use of the ICS/OT taxonomy, the [ics taxonomy](https://www.misp-project.org/taxonomies.html#_ics) is now part of default MISP taxonomies. We also encourage any ICS/OT operators to contribute back to the [ics taxonomy JSON file](https://github.com/MISP/misp-taxonomies/blob/master/ics/machinetag.json) to improve the taxonomy based on their experience. By being a taxonomy in MISP, it allows all ICS/OT users to directly tag and contextualise information shared within MISP instances and communities to describe their incidents, reports or industrial threat intelligence.
Industrial control systems and operational technologies (ICS/OT) are often the target of threats, intrusions and attacks. The [FIRST.org Cyber Threat Intelligence SIG](https://www.first.org/global/sigs/cti/) did a tremendous work of documenting these into a series of taxonomies. To support and actively test the use of the ICS/OT taxonomy, the [ics taxonomy](https://www.misp-project.org/taxonomies.html#_ics) is now part of the default MISP taxonomy library. We also encourage any ICS/OT operators to contribute back to the [ics taxonomy JSON file](https://github.com/MISP/misp-taxonomies/blob/master/ics/machinetag.json) in order to improve the taxonomy based on their experiences. By being a taxonomy in MISP, this allows all ICS/OT users to directly tag and contextualise information shared within MISP instances and communities to describe their domain specific incidents and reports along with the related industrial threat intelligence.
## Fixes and improvements
@ -49,7 +49,7 @@ We would like to thank all the [contributors](/contributors), reporters and user
Special shout-outs to Jakub Onderka ([@JakubOnderka](https://github.com/JakubOnderka)) for the tireless work around tuning the warninglist systems and fixes all around, to Pierre-Jean Grenier ([@zaphodef](https://github.com/zaphodef)) for the massive list of fixes ensuring that our APIs behave more sanely and Beckhalo Evgeny ([@4ekin](https://github.com/4ekin)) for taming the beast that is PostgreSQL support.
We would like also make a special dedication to the funding support of [CIRCL](https://twitter.com/circl_lu) and [INEA](https://twitter.com/inea_eu) under the CEF Telecom [2016-LU-IA-0098 grant](https://ec.europa.eu/inea/sites/inea/files/cef_telecom_supported_actions_november_2018.pdf).
We would also like to make a special dedication to the funding support of [CIRCL](https://twitter.com/circl_lu) and [INEA](https://twitter.com/inea_eu) under the CEF Telecom [2016-LU-IA-0098 grant](https://ec.europa.eu/inea/sites/inea/files/cef_telecom_supported_actions_november_2018.pdf).
As always, a detailed and [complete changelog is available](https://www.misp-project.org/Changelog.txt) with all the fixes, changes and improvements.