LGL-05 · Legal & Compliance

Security & Vulnerability Disclosure Policy

RFC 9116 machine-readable disclosure framework, OWASP ASVS v4.0 L2 transport hardening, CERT-In readiness, and safe-harbor guidelines for ethical security researchers.

DOC NO
LGL-05
REV
0.0.7.1
DATE
2026-11-10
STATUS
ACTIVE POLICY
ENTITY
Astrake India (Proprietorship)
DIVISIONS
Orina · Auruvi · Arenea · Drisva

1. RFC 9116 Security Policy & Endpoints

Astrake India (operating product divisions Orina, Auruvi, Arenea, and Drisva) maintains a machine-readable security disclosure endpoint adhering strictly to RFC 9116 at /.well-known/security.txt. We welcome responsible disclosures from security researchers, PSU infrastructure auditors, and enterprise CERT teams.

2. Transport Layer Hardening & Active Controls

Our public web platform implements defense-in-depth security controls aligned with OWASP ASVS v4.0 Level 2 benchmarks and CERT-In Directions (April 28, 2022):

  • Strict Content Security Policy (CSP): Dynamic 128-bit cryptographic per-request nonces, zero un-nonced inline scripts, zero unsafe-eval execution, and restricted form actions.
  • HTTP Strict Transport Security (HSTS): Enforced with 2-year duration (max-age=63072000), includeSubDomains, and preload.
  • Subresource Integrity (SRI): All vendored JavaScript primitives, compiled stylesheets, and variable WOFF2 fonts are cryptographically locked with SHA-256 and SHA-384 digests in lumora-lock.json.
  • Zero-Trust Permissions Policy: All 25 W3C sensor and hardware APIs (camera, microphone, geolocation, USB, serial, HID) are explicitly disabled on the web portal.

3. Response Targets & Triage SLAs

When a vulnerability report is submitted through our authorized channels, Astrake India commits to the following operational targets:

TABLE 01 // VULNERABILITY TRIAGE ENVELOPE
Triage Phase Service Level Target Operational Objective
Acknowledgment Within 24 Hours Initial receipt verification and reference ticket generation.
Severity Triage Within 72 Hours Reproduction, CVSS scoring, and root-cause isolation.
Remediation Window 7 to 30 Calendar Days Deployment of verified patch prioritized by severity and CERT-In 6-hour incident reporting readiness where applicable.

4. Authorized Reporting Channels

To ensure secure transmission of vulnerability details:

  • Primary Channel: Submit findings through our first-party Secure Vulnerability Disclosure Form.
  • Statutory & Fallback Channel: Email reports directly to office@astrake.com with subject prefix [SECURITY DISCLOSURE - DRISVA].
  • Registered Address: Ground Floor, Shop 3, 13B Bireswar Dhole Lane, Kolkata-700035, West Bengal, India.

5. Safe Harbor Covenants

Astrake India considers security research conducted in good faith under this policy to be authorized. We will not pursue legal action under computer crime statutes against researchers who:

  • Avoid causing denial-of-service, disruption, or destruction of production data.
  • Refrain from accessing, downloading, or exfiltrating data beyond the minimum proof-of-concept.
  • Provide reasonable time for remediation before any coordinated public disclosure.

Found a potential security vulnerability?

Report a security finding under our RFC 9116 coordinated vulnerability disclosure policy.

Report a security issue