mirror of https://github.com/MISP/misp-book
- Changed titlte of chapter to Various administration tips and tricks
- Added comment for Apache webserver config - Added paragraph on support and feature requests - Added paragraph on adding IOCs from PDF reportspull/7/head
parent
ae522fc935
commit
9b4eee564d
|
@ -267,7 +267,7 @@ Apart from off-loading long-lasting jobs to the background workers, there is a s
|
|||
![Site administrators can schedule reccuring tasks on this page.](figures/schedule.png)
|
||||
|
||||
|
||||
### Various administration tricks
|
||||
### Various administration tips & tricks
|
||||
|
||||
#### Default sharing level
|
||||
|
||||
|
@ -292,6 +292,7 @@ If you already made sure that you copied the config file under the cakeresque di
|
|||
|
||||
#### How to redirect HTTP to HTTPS
|
||||
|
||||
Here is a sample configuration for Apache webserver.
|
||||
```
|
||||
<VirtualHost *:80>
|
||||
ServerAdmin misp@misp.misp
|
||||
|
@ -330,6 +331,24 @@ If you already made sure that you copied the config file under the cakeresque di
|
|||
ServerSignature Off
|
||||
</VirtualHost>
|
||||
```
|
||||
Taken from [Koen Van Impe's blog](http://www.vanimpe.eu/2015/05/31/getting-started-misp-malware-information-sharing-platform-threat-sharing-part-3/)
|
||||
|
||||
(Taken from http://www.vanimpe.eu/2015/05/31/getting-started-misp-malware-information-sharing-platform-threat-sharing-part-3/)
|
||||
#### Support & feature requests
|
||||
|
||||
The preferred method for support & feature requests is to use the [GitHub ticketing system](https://github.com/MISP/MISP/issues).
|
||||
|
||||
If you want to discuss about something related to MISP, want help from the community, etc... You have
|
||||
the [MISP Users mailing list](https://groups.google.com/forum/#!forum/misp-users) and the [MISP developers mailing list](https://groups.google.com/forum/#!forum/misp-devel).
|
||||
|
||||
A number of companies are also offering custom development, consulting, and support around MISP, please check [the support page of the MISP Project website](http://www.misp-project.org/#support).
|
||||
|
||||
#### More information in the notification emails about new events
|
||||
|
||||
The setting MISP.extended_alert_subject allows you to have an extended subject. One word of warning though. If you’re using encryption : the subject will not be encrypted. Be aware that you might leak some sensitive information this way. Below is an example how the two subject types look like. First with the option disabled, then with the option enabled.
|
||||
```
|
||||
Event 7 - Low - TLP Amber
|
||||
Event 8 - OSINT - Dissecting XXX... - Low - TLP Amber
|
||||
```
|
||||
|
||||
Taken from [Koen Van Impe's blog](http://www.vanimpe.eu/2015/05/31/getting-started-misp-malware-information-sharing-platform-threat-sharing-part-3/)
|
||||
|
||||
|
|
|
@ -128,6 +128,10 @@ You can also import the data from a ThreatConnect export csv file. The following
|
|||
|
||||
The result will be a list of attributes that get added to the currently selected event, each of which will be marked with a comment that indicates that its origin being from a ThreatConnect import.
|
||||
|
||||
### Adding IOCs from a PDF report
|
||||
|
||||
You can You can use a generic script called [IOC parser](https://github.com/armbues/ioc_parser) or use a script published by Palo Alto to convert IOC parser output to a MISP event: [report_to_misp] (https://github.com/PaloAltoNetworks-BD/report_to_misp/).
|
||||
|
||||
### Publish an event:
|
||||
|
||||
![Only use publish (no email) for minor changes such as the correction of typos.](figures/publish.png)
|
||||
|
@ -621,3 +625,5 @@ The respone from requesting an invalid page
|
|||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue