How seefor/bloxone-api works
Project type and purpose
• This is not a traditional “frontend/backend” application. It’s a set of Jupyter notebooks and configuration/data files that demonstrate automation against the BloxOne platform’s API—specifically Threat Defense and B1DDI.
• Its purpose is to serve as a demo toolkit: users launch notebooks, read in lists or CSVs, invoke the BloxOne API, and output demo data.
File structure
Top-level items:
• README.md – high-level description
• *.ipynb – several Jupyter notebooks (b1ddi-demo.ipynb, b1ddi_getting_started.ipynb, etc.)
• csp.ini – configuration (likely API credentials/environment)
• *.csv, *.txt – sample or generated data files (domain lists, test hosts)
• python_mods.txt – list of Python dependencies/modules
Patterns & implications:
• Notebooks act as clients/orchestrators
• Data files are inputs/outputs for demos
• csp.ini holds secrets/config for API calls
Insights from README
• Confirms these notebooks illustrate automation with BloxOne Threat Defense and B1DDI.
• No internal server or database—everything is either local (notebooks/data) or external (BloxOne APIs).