-
-
Notifications
You must be signed in to change notification settings - Fork 748
BBOT 3.0 - blazed_elijah #2007
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
BBOT 3.0 - blazed_elijah #2007
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## dev #2007 +/- ##
=======================================
- Coverage 93% 92% -1%
=======================================
Files 400 425 +25
Lines 33202 34426 +1224
=======================================
+ Hits 30693 31381 +688
- Misses 2509 3045 +536 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
New Module: MongoDB Output
New Module: Elastic Output
…ements BBOT server improvements
…ements BBOT server improvements
…ements Pydantic updates
📊 Performance Benchmark Report
📈 Detailed Results (All Benchmarks)
🎯 Performance Summary✅ No significant performance changes detected (all changes <10%) 🐍 Python Version 3.11.13 |
Summary
BBOT 3.0 "
blazed_elijah
" contains changes needed to store BBOT data in a persistent database. The idea is to release it alongside BBOT server, a tiny CLI-only database. This will be paired with a series of blog posts showing how BBOT server can be used on the command line to script out bug bounty hunting, threat intel, and ASM (i.e. running scheduled scans, exporting to CSV, diffing results over time, etc.).Together, BBOT 3.0 and BBOT server will give us a solid foundation to build a bunch of other useful tooling, like asset inventory. Sometime in the future, it may also be useful to frontend.
Breaking changes
1.
.data
and.data_json
event fieldsThe main breaking change in BBOT 3.0 is that the name of the
.data
field is different based on whether it's astr
ordict
..data
: string.data_json
: dictionaryThe
siem_friendly
option has been removed, since BBOT data is now SIEM-friendly by default.2. Generic names for findings + vulnerabilities
A
name
field has been added to findings and vulns, which holds a generic description common to all vulns of the same type. This makes it easier to collapse and categorize them.Features
Potential changes