Book Convention

Convention Used in This Book

code block or value

  • Used for variable, function or menu names in MISP.

The MISP name

MISP is a recursive acronym: it stands for the MISP Intelligence Sharing Platform. The project was first named the Malware Information Sharing Platform, but as it grew to cover every kind of threat intelligence — not just malware — the name was redefined recursively, in the spirit of GNU (“GNU’s Not Unix”). Throughout this book, MISP refers to the MISP Intelligence Sharing Platform.

Language

The language in this book is American English. All the screenshots and examples are in English.

Code of Conduct

The same code of conduct applies to this book as to the main MISP project. Because documentation often reflects the spirit of a software project, please treat the book with the same care and consideration. You can read the Code of Conduct here.

Example install

The examples and screenshots provided in this book have been created with the MISP Autogenerated VM.

To get a copy of the latest VM click here

MISP Instance

In general when talking about a network of inter-connected MISP servers, each server is a MISP instance. Whilst we have no strong feelings towards anyones naming schemes, as a rule of thumb try to have a scheme that makes everyday use easy when analysts need to talk about remote MISP instances.

The hostname used for the instance in this book is misp.local and we will henceforth refer to it either by name or as local MISP instance.

Example Organisations

As MISP is a platform to support information sharing, example organisations are often used within this book.

A set of users and organisations are used in the different examples.

The following two organisations are regularly used as example:

  • Setec Astronomy with UUID 58d38339-7b24-4386-b4b4-4c0f950d210f
  • Acme Finance with UUID 58d38326-eda8-443a-9fa8-4e12950d210f

Starting from MISP 2.4.71, the example organisations with the above mentioned UUID are blocklisted to avoid large distribution of sample events while testing a MISP instance. If you want to test your distribution, the sample organisation blocklisting can be removed in Administration/Manage Org blocklists (this menu is only available when the MISP.enableOrgBlocklisting setting is turned on).

Example IOCs

As with the example organisations, we want to make this book as useful as possible by using real life examples.

The following IOC examples have been used:

  • Sirefef (aka ZeroAccess) Sample Event ID: #31337
  • WannaCry Sample Event ID: #42
  • Dridex Sample Event ID: #23