Skip to content

Commit

Permalink
[V1.1.0] Update ELK stack and multiple improvements to the ingestor s…
Browse files Browse the repository at this point in the history
…ervice
  • Loading branch information
Lancini, Marco authored and Marco Lancini committed Jun 20, 2019
1 parent b854e64 commit 9202506
Show file tree
Hide file tree
Showing 2 changed files with 49 additions and 23 deletions.
29 changes: 29 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
# Change Log
All notable changes to this project will be documented in this file.
This project adheres to [Semantic Versioning](http://semver.org/).



## [1.1.0] - 2019-06-20
#### Added
- Update ELK stack: v6.3.0 -> v7.1.1
- Multiple modifications to the ingestor service:
* Move ingestor to `extensions` folder
* Modify VulntoES to record MAC addresses, if present
* Update ingestor container from python2.7 to python3.7
* Semplify call method: `docker-compose run ingestor`
* Minor refactoring to `VulntoES.py`
#### Fixed
- Time pattern now available
#### Removed
- Remove extensions/logspout


## [1.0.1] - 2018-10-17
#### Fixed
- Modify VulntoES to only ingest open ports


## [1.0.0] - 2018-07-16
#### Added
- First Public Release
43 changes: 20 additions & 23 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ A full walkthrough that led me to this setup can be found at: [https://www.marco
```
❯ git clone https://github.com/marco-lancini/docker_offensive_elk.git
```
2. Create the `_data` folder and ensure it is owned by your own user:
2. Create the `_data` folder (if not present) and ensure it is owned by your own user:
```
❯ cd docker_offensive_elk/
❯ mkdir ./_data/
Expand All @@ -25,27 +25,8 @@ A full walkthrough that led me to this setup can be found at: [https://www.marco
docker-elk ❯ docker-compose up -d
```
4. Give Kibana a few seconds to initialize, then access the Kibana web UI running at: http://localhost:5601.
5. During the first run, [create an index](#create-an-index).
6. [Ingest nmap results](#ingest-nmap-results).


### Create an Index

1. Create the `nmap-vuln-to-es` index using curl:
```bash
❯ curl -XPUT 'localhost:9200/nmap-vuln-to-es'
```
2. Open Kibana in your browser ([http://localhost:5601](http://localhost:5601)) and you should be presented with the screen below:
<img src="https://www.marcolancini.it/images/posts/blog_elk_index1.png">

3. Insert `nmap*` as index pattern and press "_Next Step_":
<img src="https://www.marcolancini.it/images/posts/blog_elk_index2.png">

4. Choose "_I don't want to use the Time Filter_", then click on "_Create Index Pattern_":
<img src="https://www.marcolancini.it/images/posts/blog_elk_index3.png">

5. If everything goes well you should be presented with a page that lists every field in the `nmap*` index and the field's associated core type as recorded by Elasticsearch.
<img src="https://www.marcolancini.it/images/posts/blog_elk_index4.png">
5. Start [ingesting your nmap results](#ingest-nmap-results).
6. During the first run, [create an index](#create-an-index).



Expand All @@ -55,7 +36,7 @@ In order to be able to ingest our Nmap scans, we will have to output the results
Once done with the scans, place the reports in the `./_data/nmap/` folder and run the ingestor:

```bash
❯ docker-compose run ingestor ingest
❯ docker-compose run ingestor
Starting elk_elasticsearch ... done
Processing /data/scan_192.168.1.0_24.xml file...
Sending Nmap data to Elasticsearch
Expand All @@ -64,3 +45,19 @@ Sending Nmap data to Elasticsearch
Processing /data/scan_192.168.3.0_24.xml file...
Sending Nmap data to Elasticsearch
```



### Create an Index

1. Open Kibana in your browser ([http://localhost:5601](http://localhost:5601)) and you should be presented with a screen similar to the one below:
![elk_index_1](.github/elk_index_1.jpg)

2. Insert `nmap*` as index pattern and press "_Next Step_":
![elk_index_2](.github/elk_index_2.jpg)

3. In the "_Time Filter_" field name choose "`time`", then click on "_Create Index Pattern_":
![elk_index_3](.github/elk_index_3.jpg)

4. If everything goes well you should be presented with a page that lists every field in the `nmap*` index and the field's associated core type as recorded by Elasticsearch.
![elk_index_4](.github/elk_index_4.jpg)

0 comments on commit 9202506

Please sign in to comment.