tibet-soc — Security Operations Center with TIBET Provenance
Unified threat detection, event correlation, and incident response for the TIBET ecosystem. Every SOC decision is recorded as a TIBET token — an audit trail for the auditor.
What It Does
tibet-soc is the central nervous system of TIBET security. It aggregates signals from every TIBET tool and correlates them into actionable alerts:
| Source | Signal Type |
|---|---|
| tibet-audit | Compliance violations, policy |
| tibet-db | Data access anomalies, tampering |
| tibet-edge | Boundary crossings, perimeter |
| tibet-mirror | Supply chain integrity failures |
| tibet-snap | State deviations, rollback events |
| tibet-nis2 | NIS2 compliance incidents |
| inject-bender | Injection attacks, exploit probes |
Event Correlation
Multiple low-severity events can indicate a high-severity attack:
- Brute Force — 3+ auth failures from same source in 5 minutes
- APT Attack — data breach combined with privilege escalation
- Supply Chain Compromise — supply chain event from tibet-mirror
- Insider Threat — anomaly + policy violation from same asset
Playbook-Driven Response
Automated response actions based on threat type:
isolate_asset— quarantine the compromised assetsnapshot_state— capture state via tibet-snap for forensicsblock_source— block the offending source at the perimeternotify_team— alert the security teamescalate_nis2— trigger NIS2 incident reporting workflow
TIBET Provenance
Every SOC decision produces a TIBET token:
- ERIN: event/alert/decision details
- ERAAN: correlated events, source tools,
jis:identity - EROMHEEN: SOC node, analyst, timestamp
- ERACHTER: correlation pattern or playbook execution context
Installation
pip install tibet-soc
With optional integrations:
pip install tibet-soc[full] # rich CLI + tibet-nis2/snap/db
CLI
tibet-soc info # Concept overview
tibet-soc demo # Full demo: ingest, correlate, detect, respond
tibet-soc playbooks # List default playbooks
tibet-soc status # SOC dashboard stats
Python API
from tibet_soc import SOCEngine, SecurityEvent, Playbook
# Create SOC engine
soc = SOCEngine()
# Ingest events from multiple sources
soc.ingest(SecurityEvent(
source="inject-bender",
severity="HIGH",
event_type="intrusion",
description="SQL injection attempt blocked",
asset_id="web-server-01",
))
soc.ingest(SecurityEvent(
source="tibet-db",
severity="CRITICAL",
event_type="data_breach",
description="Unauthorized bulk data export",
asset_id="db-primary",
))
# Correlate events and detect patterns
alerts = soc.correlate()
for alert in alerts:
print(f"[{alert.severity}] {alert.title}")
# Execute playbook for alert
soc.execute_playbook(alerts[0])
# Dashboard stats
print(soc.stats())
License
MIT — Humotica / J. van de Meent
Credits
Designed by Jasper van de Meent. Built by Jasper and Root AI as part of HumoticaOS.
Stack-positie: Groep safety · Bootstrap = OSAPI-handshake naar tibet + jis (fail → snaft-rule + tibet-pol-rapport) · ← tibet-audit · tibet-report → · See STACK.md · See demo/golden-path/ for the spine end-to-end.
Enterprise
For private hub hosting, SLA support, custom integrations, or compliance guidance:
| Enterprise | enterprise@humotica.com |
| Support | support@humotica.com |
| Security | security@humotica.com |
See ENTERPRISE.md for details.
Metadata
Release files for tibet-soc 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tibet_soc-0.1.1.tar.gz | 14.1 kB | Without provenance | Details for tibet_soc-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tibet_soc-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for tibet_soc-0.1.1-py3-none-any.whl |
Total release size: 29.5 kB
Release files / tibet_soc-0.1.1.tar.gz
| Download URL | tibet_soc-0.1.1.tar.gz |
|---|---|
| Size | 14.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
65dcd60f4cacc178e9649bc2524ec73dbcdef78dc8d5ca711e7bf329e45e2a23
|
|
BLAKE2b-256 checksum How to use checksums |
4375ba1a57b126823fd4447e3d62ce795e36dae3154ae2c3f5cf8f3e6b3acf49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / tibet_soc-0.1.1-py3-none-any.whl
| Download URL | tibet_soc-0.1.1-py3-none-any.whl |
|---|---|
| Size | 15.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00e8904de0bf5d334b2111b8f2434cb8bc65986fae1dc2bd9ee2538ca07e9145
|
|
BLAKE2b-256 checksum How to use checksums |
db8aec5aaec9803b8ba475b9e0d2af4c960d82028d9bb6e37e8c3659ada3dc1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for tibet-soc 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.