From 2e3469b0af9d164947470a666ab90b8319d29dad Mon Sep 17 00:00:00 2001 From: mokaddem Date: Sun, 11 Oct 2020 15:08:27 +0200 Subject: [PATCH] fix: [blog] Event-report changed featured picture path --- _posts/2020-10-08-Event-Reports.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/2020-10-08-Event-Reports.md b/_posts/2020-10-08-Event-Reports.md index ccd6bfb..1b1d02f 100644 --- a/_posts/2020-10-08-Event-Reports.md +++ b/_posts/2020-10-08-Event-Reports.md @@ -1,7 +1,7 @@ --- title: Event Report - A convenient mechanism to edit, visualize and share reports layout: post -featured: /assets/images/misp/blog/event-report.png +featured: /assets/images/misp/blog/event-reports/report-modal.png --- # Event Report: A convenient mechanism to edit, visualize and share reports @@ -120,4 +120,4 @@ With the support of reports built-in in MISP, a new kind of knowledge can be use *Event reports* also offer a wide range of new possibilities that were not doable efficiently before. For example, Counter analysis on cases can be explained, resolution steps and recommendations can be supplied, and complete articles can be included inside an *event*. -Furthermore, it opens the door for new ways to create information in MISP. In the future, we could imagine doing it the other way around by extracting IoCs, threat actors and so on directly from the report. \ No newline at end of file +Furthermore, it opens the door for new ways to create information in MISP. In the future, we could imagine doing it the other way around by extracting IoCs, threat actors and so on directly from the report.