Effective Date: 1 January 2025 • Last Updated: 30 October 2026
Staff Mitr operates on zero-trust and defense-in-depth principles to protect biometric facial templates, banking details, and payroll data from unauthorized access, cross-tenant leakage, and cyber threats.
Every database query, API endpoint, and cache lookup is strictly constrained to the authenticated tenant's organization_id. Cross-tenant request spoofing (e.g. manipulating X-Organization-ID or employee IDs) is blocked by server-side query filtering and returns HTTP 403 Forbidden.
EncryptedJSONField with AES-128-CBC and HMAC-SHA256 (Fernet specification). Runtime assertion blocks application boot if default or weak keys are detected.secure_media_gate, an internal reverse proxy that validates active session credentials and tenant authorization before releasing files.HTTP 429 Too Many Requests and a 300-second lockout cooldown.VIEW, CREATE, EDIT, DELETE, APPROVE) with branch/department data scoping and strict anti-self-approval blocks on leaves, reimbursements, and loans.In compliance with the CERT-In Directions (April 2022) and Section 8(6) of the DPDP Act, any confirmed cybersecurity incident or unauthorized database access is escalated and formally reported to CERT-In (incident@cert-in.org.in) within 6 hours of detection. Impacted customer organizations are notified within 24 hours.
If you discover a security vulnerability, report it to security@staffmitr.in. Provide reproduction steps and allow 30 days for remediation. Staff Mitr will not take legal action against security researchers acting in good faith under these guidelines.