Skip to content

Security: sandesh-s-hegde/digital_capacity_optimizer

Security

SECURITY.md

Security Policy

Supported Versions

As this Decision Support System (DSS) is both an active research artifact and a production-grade proof-of-concept, security maintenance and patches are prioritized for the current major release tree.

Version Supported
5.0.x
4.2.x ⚠️ (Critical patches only)
< 4.2

Reporting a Vulnerability

This project utilizes strict environment variable management (dotenv) to secure all credentials, cloud databases, and API keys.

If you discover a security vulnerability (e.g., SQL injection risks, exposed endpoints, or AI prompt injection vulnerabilities), please do not open a public GitHub issue.

Instead, please report it via email directly to the repository owner at s.sandesh.hegde@gmail.com. We will acknowledge receipt of the vulnerability within 48 hours and strive to issue a patch within 5 business days.

Architecture Security Considerations

When deploying or reviewing this artifact, please note the following security implementations:

  • Decoupled Authentication: The system uses distinct, strictly-scoped API keys for geospatial mapping (GOOGLE_API_KEY), AI reasoning (GEMINI_API_KEY), and telemetry to prevent cross-service privilege escalation and billing attacks.
  • Zero-Trust Secrets: No keys or database credentials are ever committed to this repository. Users must supply their own keys via a local .env file or a cloud secrets manager (e.g., Streamlit Secrets / Render Environment Variables).
  • Database Encryption: The PostgreSQL network twin enforces sslmode=require for all cloud connections, ensuring logistics and inventory data remain encrypted in transit.
  • Input Sanitization & Context Security: User inputs passed through the Streamlit UI and location search boxes are sanitized. Furthermore, the v5.0.0 semantic data compression pipeline ensures that raw, unbound time-series data does not overflow into the LLM context, mitigating prompt injection and token-exhaustion risks.
  • Denial of Service (DoS) Mitigation: The v5.0.0 AI pipeline implements exponential backoff and retry logic (max 3 attempts) to gracefully handle HTTP 429 rate limits, preventing application crashes from API exhaustion attacks.

There aren't any published security advisories