How nim4/dbshield works
DBShield is a SQL-aware database proxy: an application connects through it, and it forwards database protocol traffic while learning query patterns or checking them in protect mode. The main path runs from configuration and listener dispatch through a database-specific protocol handler, query classification, and forwarding or configured action. A local Bolt database stores learned patterns and abnormal-query records; a separate authenticated web interface exposes query counters. README documents support for DB2, MariaDB/MySQL, Oracle, PostgreSQL, and SQL Server. Some startup/listener wiring is omitted from the excerpts, so uncertain links are dashed.
Main entry points: dbshield/utils.go Connection dispatch · dbms/utils.go Query processing · training.go Learning and checks · dbshield.go Proxy lifecycle
Components 22
Proxy runtime
- Configuration
dbshield/config/config.go - Proxy lifecycle
dbshield/dbshield.go - Connection dispatch
dbshield/utils.go
Database protocols
- MySQL / MariaDB
dbshield/dbms/mysql.go - PostgreSQL
dbshield/dbms/postgres.go - DB2
dbshield/dbms/db2.go - Oracle
dbshield/dbms/oracle.go - SQL Server
dbshield/dbms/mssql.go
Learning and policy
- Query processing
dbshield/dbms/utils.go - SQL patterns
dbshield/sql/sql.go - Learning and checks
dbshield/training/training.go - Configured action
dbshield/utils/action.go - Pattern store
dbshield/training/training.go - Abnormal records
dbshield/training/training.go
Management and status
- CLI entry point
main.go - Pattern management
dbshield/dbshield.go - Web interface
dbshield/httpserver/server.go - Logging
dbshield/logger/log.go
Other components
- Application server
- Backend database
- CLI operator
- Web UI user
Connections 32
- CLI operator → CLI entry point: runs
main.go - CLI entry point → Proxy lifecycle: starts
main.go - Proxy lifecycle → Configuration: parses
- Proxy lifecycle → Connection dispatch: accepts connections
- Connection dispatch → Backend database: opens backend connection
dbshield/utils.go - Connection dispatch → MySQL / MariaDB: dispatches
dbshield/utils.go - Connection dispatch → PostgreSQL: dispatches
dbshield/utils.go - Connection dispatch → DB2: dispatches
dbshield/utils.go - Connection dispatch → Oracle: dispatches
dbshield/utils.go - Connection dispatch → SQL Server: dispatches
dbshield/utils.go - Application server → Connection dispatch: sends SQL traffic
README.md - MySQL / MariaDB → Backend database: forwards protocol traffic
dbshield/dbms/mysql.go - PostgreSQL → Backend database: forwards protocol traffic
dbshield/dbms/postgres.go - DB2 → Backend database: forwards protocol traffic
dbshield/dbms/db2.go - Oracle → Backend database: forwards protocol traffic
dbshield/dbms/oracle.go - SQL Server → Backend database: forwards protocol traffic
dbshield/dbms/mssql.go - MySQL / MariaDB → Query processing: processes query
dbshield/dbms/mysql.go - PostgreSQL → Query processing: processes query
dbshield/dbms/postgres.go - DB2 → Query processing: processes query
dbshield/dbms/db2.go - Oracle → Query processing: processes query
dbshield/dbms/oracle.go - SQL Server → Query processing: processes query
dbshield/dbms/mssql.go - Query processing → Learning and checks: checks or learns
dbshield/dbms/utils.go - Learning and checks → SQL patterns: normalizes queries
dbshield/training/training.go - Learning and checks → Pattern store: reads and writes
dbshield/training/training.go - Learning and checks → Abnormal records: records anomalies
dbshield/training/training.go - Query processing → Configured action: invokes on rejection
dbshield/dbms/utils.go - Web UI user → Web interface: views status
dbshield/httpserver/server.go - Web interface → Learning and checks: reads counters
dbshield/httpserver/server.go - CLI entry point → Pattern management: runs management commands
main.go - Pattern management → Pattern store: lists or removes patterns
- Proxy lifecycle → Web interface: starts interface
- Query processing → Logging: logs events