AI-Secured SQLite & Kafka Auto PKI
Budget: $250 – $750 USD
I need to harden the Votrite platform by adding three layers of protection to the embedded SQLite store—encryption at rest and in transit, fine-grained access control, and AI-driven anomaly detection—while simultaneously wiring in a fully automated public-key infrastructure for our Kafka brokers and clients. All certificates must be issued, renewed, and revoked without manual touch-points.
Here is the flow I’m aiming for:
• Every write to SQLite is transparently encrypted (AES-256 or stronger).
• Role-based and, where possible, row-level access rules are enforced inside the database engine.
• A lightweight ML model monitors query patterns and flags anomalies in real time.
• An Auto-PKI service holds root and intermediate CAs, stores metadata in SQLite, and pushes certificates to Kafka nodes via mTLS. Issuance, renewal, and revocation must all run on a schedule or event trigger with zero downtime.
Deliverables
1. Source code (Go, Rust, or Python preferred) that plugs into our existing Docker stack.
2. Configuration scripts for initializing encrypted SQLite and spinning up the PKI service.
3. A concise README and demo showing successful certificate rotation and an anomaly alert.
Acceptance will be based on:
• Verified encryption keys, working RBAC tests, and a simulated breach detected by the model.
• Kafka brokers reconnecting seamlessly after an automated certificate roll-over.
If you have hands-on experience with SQLite internals, Kafka security, and lightweight ML anomaly detection, I’d love to see a brief outline of your approach and timeline.
Here is the flow I’m aiming for:
• Every write to SQLite is transparently encrypted (AES-256 or stronger).
• Role-based and, where possible, row-level access rules are enforced inside the database engine.
• A lightweight ML model monitors query patterns and flags anomalies in real time.
• An Auto-PKI service holds root and intermediate CAs, stores metadata in SQLite, and pushes certificates to Kafka nodes via mTLS. Issuance, renewal, and revocation must all run on a schedule or event trigger with zero downtime.
Deliverables
1. Source code (Go, Rust, or Python preferred) that plugs into our existing Docker stack.
2. Configuration scripts for initializing encrypted SQLite and spinning up the PKI service.
3. A concise README and demo showing successful certificate rotation and an anomaly alert.
Acceptance will be based on:
• Verified encryption keys, working RBAC tests, and a simulated breach detected by the model.
• Kafka brokers reconnecting seamlessly after an automated certificate roll-over.
If you have hands-on experience with SQLite internals, Kafka security, and lightweight ML anomaly detection, I’d love to see a brief outline of your approach and timeline.