mirror of https://github.com/MISP/misp-book
18 lines
1.3 KiB
Markdown
18 lines
1.3 KiB
Markdown
|
<!-- toc -->
|
||
|
|
|
||
|
|
## Automation
|
||
|
|
|
||
|
|
Automation functionality is designed to automatically generate signatures for intrusion detection systems. To enable signature generation for a given attribute, Signature field of this attribute must be set to Yes. Note that not all attribute types are applicable for signature generation, currently we only support NIDS signature generation for IP, domains, host names, user agents etc., and hash list generation for MD5/SHA1 values of file artifacts. Support for more attribute types is planned. To to make this functionality available for automated tools an authentication key is used. This makes it easier for your tools to access the data without further form-based-authentication.
|
||
|
|
|
||
|
|
### Automation key
|
||
|
|
|
||
|
|
The authentication of the automation is performed via a secure key available in the MISP UI interface. Make sure you keep that key secret as it gives access to the entire database! The API key is available in the event actions menu under automation.
|
||
|
|
|
||
|
|
Since version 2.2 the usage of the authentication key in the url is deprecated. Instead, pass the auth key in an Authorization header in the request. The legacy option of having the auth key in the url is temporarily still supported but not recommended.
|
||
|
|
|
||
|
|
The authorization is performed by using the following header:
|
||
|
|
|
||
|
|
~~~~
|
||
|
|
Authorization: YOUR API KEY
|
||
|
|
~~~~
|