How myabyss000/vigiledge-collage-project works
Project type and purpose
• By examining the file tree and README, this is a full-stack Python web application (“VigilEdge”) that provides a web application firewall (WAF) layer, vulnerability testing harnesses, dashboards, and logging. It bundles a Flask-style web server (templates/, static/, api/routes.py), a core engine (core/waf_engine.py, core/security_manager.py), middleware (security_middleware.py), and both SQLite and MongoDB back-ends.
File structure
• Top level:
• VigilEdge/
– templates/ & static/ → UI layer
– api/routes.py → HTTP API layer
– middleware/ → request interception (WAF enforcement)
– core/ → business logic (security rules, WAF engine)
– config/waf_rules.yaml → WAF policy definitions
– vulnerable_app*.py → demo vulnerable web apps for testing
– setup, launch scripts → deployment automation (Windows/.ps1)
– requirements.txt → Python dependencies
– vulnerable.db / vulnerable_backup.db → SQLite storage
– scripts to spin up MongoDB variant (launch_mongodb.*)
– tests/ → automated unit and integration tests
• logs/ → central log file
• Patterns: layered MVC (templates UI, Flask routes, core engine), middleware pipeline, pluggable WAF engine, dual-DB support for testing vs production.
README for additional insights
• README is minimal (“my Collage project”) but other docs under VigilEdge/ (WAF_INTEGRATION_GUIDE.md, TESTING_README.md) indicate:
• It integrates with external WAF appliances/services
• Provides testing harnesses to validate WAF rules
• Supports analytics dashboards for event_logs, blocked_ips, threat_detection, etc.