1. Security Governance Commitment
Security is foundational to the ChargeMesh architecture. As an open-source EV charging interoperability platform handling real-time hardware telemetry (OCPP), financial ledger transactions, and driver location data, we enforce rigorous DevSecOps benchmarks across our entire codebase and cloud infrastructure.
ChargeMesh is developed and governed by KalaKirtiHub with active community review on GitHub.
2. Coordinated Vulnerability Disclosure (CVD)
We welcome security researchers, white-hat ethical hackers, and community developers to audit our platform. If you discover a potential vulnerability or security concern in any ChargeMesh application or API service, please notify us responsibly.
Do not submit public GitHub issues for undisclosed security vulnerabilities.
Official Security Contact:
Email: security@chargemesh.com
Carbon Copy (Lead Maintainer): abhayksingh614@gmail.com
GitHub Security Advisory (Private Vulnerability Reporting): Available via the repository security tab.
3. Vulnerability Response SLAs
We commit to the following strict response service-level agreements:
| Stage | Timeline | Action Taken |
|---|---|---|
| Initial Acknowledgment | Within 48 Hours | Confirm receipt of report and assign an internal tracking ticket. |
| Triage & Severity Assessment | Within 14 Business Days | Reproduce issue, assign CVSS v3.1 rating, and assess operational impact. |
| Patch Release & Deployment | Within 30 Calendar Days | Develop hotfix, pass CI test regression suites, deploy to production, and release patched version. |
| Public Advisory & Credit | Post-Deployment | Publish CVE/GHSA advisory and credit the researcher in release notes (unless anonymity is requested). |
4. Safe Harbor for Ethical Researchers
KalaKirtiHub considers security research conducted under this policy to be authorized. We will not pursue legal action against researchers who:
- Make a good-faith effort to avoid privacy violations, data destruction, and interruption of live charging sessions.
- Refrain from accessing, downloading, or modifying data belonging to other users or charging operators.
- Provide reasonable time for our engineering team to remediate the vulnerability before public disclosure.
- Do not perform Denial of Service (DoS/DDoS) attacks against production infrastructure or physical charging hardware.
5. DevSecOps Standards & Secret Scanning
ChargeMesh enforces defense-in-depth engineering practices:
- Zero Secrets in Version Control: All source files, documentation, commit messages, and example configs are scanned with automated secret scanners in GitHub Actions CI to prevent accidental credential leakage.
- Role-Based Access Control (RBAC): Strict separation between EV driver endpoints, CPO operational portals, and administrative protocol gateways.
- Statutory CERT-In Incident Reporting: In compliance with the Cyber Security Directions issued by the Indian Computer Emergency Response Team (CERT-In) under Section 70B of the IT Act, 2000, any reportable cybersecurity incident is notified to CERT-In within 6 hours of confirmation.
