<p align="center"><img src=" width="400px"></p>
<p align="center"> <i>Create <u><b>actionable data</b></u> from your scans </i> </p>
<p align="center" style="width:400px"><img src=" style="width:400px"></p>
is a management tool and report aggregator. will pull all the reports from the different scanners and create a file with a unique filename for each one, using that data later to sync with Jira and feed Logstash. Jira does a closed cycle full Sync with the data provided by the Scanners, while Logstash indexes and tags all of the information inside the report (see logstash files at /resources/elk6/pipeline/). Data is then shipped to ElasticSearch to be indexed, and ends up in a and searchable format in Kibana with already defined dashboards.
is an open-source community funded project. currently works but is due for a documentation o and code review. This is on the roadmap for the next month or two (February or March of 2022 - hopefully). Please note, crowd funding is an option. If you would like help getting up and running, are interested in new features, or are looking for paid support (for those of you that require commercial support contracts to implement open-source solutions), please reach out to .
![Build Status]()
![GitHub license]()
![Twitter]()
Currently Supports
-----------------
Getting Started
===============
1) Follow the install requirements
2) Fill out the section you want to process in <a href=" file</a>
3) [JIRA] If using Jira, fill Jira config in the config file mentioned above.
3) [ELK] Modify the IP settings in the <a href=" files to accommodate your en</a> and import them to your logstash conf directory (default is /etc/logstash/conf.d/)
4) [ELK] Import the <a href=" </a>
5) Run
Need assistance or just want to chat? Join our slack channel
Requirements
-------------
####
* Python 2.7
* Scanner
* Reporting System: Jira / ElasticStack 6.6
<a id="installreq">Install Requirements-(may require sudo)</a>
--------------------
Install OS packages requirement dependencies (Debian-based distros, CentOS don't need it)
(Optional) Use a python to not mess with host python libraries
Install python libraries requirements
(Optional) If using a proxy, add proxy URL as en to PATH
Now you're ready to pull down scans. (see <a href="#run">run section</a>)
Configuration
-----
There are a few configuration steps to setting up :
* Configure Ini file
* Setup Logstash File
* Import ElasticSearch Templates
* Import Kibana Dashboards
<a href=" file</a>
<p align="left" style="width:200px"><img src=" style="width:200px"></p>
<a id="run">Run</a>
-----
To run, fill out the configuration file with your scanner settings. Then you can execute from the command line.
If no section is specified (e.g. -s nessus), will check on the config file for the modules that have the property enabled=true and run them sequentially.
<p align="center" style="width:300px"><img src=" style="width:400px"></p>
Next you'll need to import the into Kibana and setup your logstash config. You can either follow the sample setup instructions here or go for the docker-compose solution we offer.
Docker-compose
-----
ELK is a whole world by itself, and for newcomers to the platform, it requires basic Linux skills and usually a bit of troubleshooting until it is deployed and working as expected. As we are not able to provide support for each users ELK problems, we put together a docker-compose which includes:
The docker-compose just requires specifying the paths where the data will be saved, and where the config files reside. If ran directly after git clone, with just adding the Scanner config to the config file (/resources/elk6/.ini), it will work out of the box.
It also takes care to load the Kibana Dashboards and automatically through the API, which needs to be done manually otherwise at Kibana's startup.
For more info about the docker-compose, check on the docker-compose wiki or the FAQ.
Getting Started
===============
Our current Roadmap is as follows:
On top of this, we try to focus on fixing bugs as soon as possible, which might delay the de. We also very welcome PR's, and once we have the new standard implemented, it will be very easy to add compatibility with new scanners.
The Standard will initially be a new simple one level JSON with all the information that matches from the different scanners having standardized names, while maintaining the rest of the as they are. In the future, once e is implemented, we will e moving to an existing standard like ECS or AWS Schema; we prioritize functionality o.
Video Walkthrough -- Featured on ElasticWebinar
----------------------------------------------
<a href="
" target="_blank"><img src="
alt="Elastic presentation on " border="10" /></a>
Authors
------
- Austin Taylor ()
- Justin Henderson ()
Contributors
------------
- Quim Montal ()
-
-
AS SEEN ON TV
-------------
<p align="center" style="width:400px"><a href=" src=" style="width:400px"></a></p>
开发语言:Python
Star 数:1397
该项目属于漏洞知识库方向的开源资源,代码结构清晰,适合安全研究人员学习参考。项目围绕Create actionable data from your Vulnerability Scans展开,提供了可运行的实现,对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。
从技术实现角度看,此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论,梳理项目的初始化流程、核心模块职责与数据流转,逐步掌握其中的技术细节与设计思路。
1. 下载源码压缩包,解压到本地环境。
2. 根据项目类型准备对应的运行环境与依赖。
3. 按照 README 中的步骤完成配置与部署。
4. 在隔离的测试环境中运行验证,避免影响生产系统。
本资源来源于开源社区,仅供安全研究、技术学习与合法授权范围内的攻防演练使用,请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。
| 资源标题 | VulnWhisperer - Create actionable data from your Vulnerability Sca |
| 所属分类 | 漏洞知识库 |
| 发布作者 | admin |
| 发布时间 | 2026-10-06 01:00:44 |
| 下载权限 | 免费下载 |
| 附件数量 | 2 个下载链接 |
| 浏览次数 | 297 |
| 讨论数量 | 0 |
| 主题状态 | 正常讨论中 |