SecDNS Automation Portal Build
Budget: $750 – $1,500 USD
I need a web-based frontend that sits in front of PowerDNS (recursor + authoritative), Pi-hole, Maltrail, and OpenCTI/MISP and turns them into a single, cohesive security-focused DNS platform. While the backend stack is already chosen, the missing piece is an interface that gives me full automation capabilities without losing visibility or fine-grained policy control.
My top priority is automation. In practical terms that means:
• Centralised creation, editing, and distribution of RPZ / DNS policy rules across PowerDNS and Pi-hole.
• Automatic conversion of CTI (OpenCTI/MISP) feeds into actionable RPZ entries.
• Near-real-time anomaly detection and correlation, fed by Maltrail data and reflected instantly in the UI and metrics.
I expect the finished portal to provide:
1. A clean, responsive web UI with role-based access.
2. A robust API so external systems can trigger or retrieve policy changes.
3. Documentation that covers setup, API usage, and integration steps for each backend component.
4. Docker-compose or similar deployment scripts so I can spin the whole stack up reliably.
Please send a concise yet detailed project proposal explaining architecture choices, language/framework selection, and how you plan to wire automation between the tools mentioned above. A short timeline with major milestones will help me gauge feasibility.
If you have shipped something similar—especially around RPZ management, CTI ingestion, or DNS analytics—highlight that experience in your proposal. I look forward to seeing how you would bring SecDNS to life.
My top priority is automation. In practical terms that means:
• Centralised creation, editing, and distribution of RPZ / DNS policy rules across PowerDNS and Pi-hole.
• Automatic conversion of CTI (OpenCTI/MISP) feeds into actionable RPZ entries.
• Near-real-time anomaly detection and correlation, fed by Maltrail data and reflected instantly in the UI and metrics.
I expect the finished portal to provide:
1. A clean, responsive web UI with role-based access.
2. A robust API so external systems can trigger or retrieve policy changes.
3. Documentation that covers setup, API usage, and integration steps for each backend component.
4. Docker-compose or similar deployment scripts so I can spin the whole stack up reliably.
Please send a concise yet detailed project proposal explaining architecture choices, language/framework selection, and how you plan to wire automation between the tools mentioned above. A short timeline with major milestones will help me gauge feasibility.
If you have shipped something similar—especially around RPZ management, CTI ingestion, or DNS analytics—highlight that experience in your proposal. I look forward to seeing how you would bring SecDNS to life.