How itamar-raanan/sec360 works
SEC360 is a self-hosted security visibility, posture-management, and audit platform. Analysts use its React interface to authenticate and inspect correlated identity, endpoint, compliance, risk, activity, vulnerability, DLP, Linux audit, proxy-policy, and network-topology data; administrators configure integrations and settings. Backend collection and evaluation persist inventory and evidence in PostgreSQL, with optional SIEM delivery. The repository also includes an on-premises Network Map collector and a read-only MCP interface. Relationships for unsampled feature modules follow README descriptions; omitted source details limit more specific call-flow claims.
Main entry points: database.py PostgreSQL state · scheduler.py Collection scheduler · client.ts API client · routes Feature APIs
Components 20
Analyst interface
- Web application
frontend/src/App.tsx - API client
frontend/src/api/client.ts
Backend API
- Authentication
backend/app/api/routes/auth.py - Authorization layer
backend/app/api/deps.py - Feature APIs
backend/app/api/routes - Integration management
backend/app/api/routes/integrations.py
Collection and analysis
- Collection scheduler
backend/app/collectors/scheduler.py - Integration collectors
backend/app/collectors - Correlation engine
backend/app/engines/correlation.py - Compliance engine
backend/app/engines/compliance.py - Risk engine
backend/app/engines/risk.py - Network Map service
backend/app/network_map/service.py
State and audit
- PostgreSQL state
backend/app/core/database.py - Inventory and evidence
backend/app/models - SIEM delivery
backend/app/services/siem.py
Optional interfaces
- On-prem collector
collector/sec360_collector/main.py - Read-only MCP server
mcp-server/sec360_mcp/server.py
Other components
- Analyst
- SIEM endpoint
- Network devices
Connections 21
- Analyst → Web application: uses
README.md - Web application → API client: requests data
- API client → Authentication: refreshes session
frontend/src/api/client.ts - API client → Feature APIs: calls API
- Feature APIs → Authorization layer: authorizes requests
backend/app/api/deps.py - Integration management → Collection scheduler: starts sync
- Collection scheduler → Integration collectors: runs collectors
README.md - Integration collectors → PostgreSQL state: stores collected data
README.md - Collection scheduler → Correlation engine: runs correlation
README.md - Collection scheduler → Compliance engine: evaluates compliance
README.md - Collection scheduler → Risk engine: calculates risk
README.md - Correlation engine → PostgreSQL state: updates inventory
README.md - Compliance engine → PostgreSQL state: stores results
README.md - Risk engine → PostgreSQL state: stores scores
README.md - PostgreSQL state → Inventory and evidence: persists
backend/app/core/database.py - Network devices → On-prem collector: provides snapshots
README.md - On-prem collector → Network Map service: pushes snapshots
README.md - Network Map service → PostgreSQL state: installs snapshot
backend/app/network_map/service.py - PostgreSQL state → SIEM delivery: queues audit events
backend/app/api/deps.py - SIEM delivery → SIEM endpoint: forwards events
README.md - Read-only MCP server → Feature APIs: queries read-only API