HXLABZ Logo
HXLABZ
SECURITY DIRECTIVE

Security Architecture & Vulnerability Disclosure

EFFECTIVE DATE: August 26, 2024
LAST REVISED: August 26, 2026
STATUS: ACTIVE & AUDITED

01.Security Architecture & Defense-in-Depth

HXLABZ engineers foundational AI and computational systems with mathematical determinism and defense-in-depth principles. Our web platforms and waitlist infrastructure implement robust safeguards:

Transport & Data Layer

Enforced TLS 1.3 encryption across all public ingress endpoints. HSTS (HTTP Strict Transport Security) enabled. Ephemeral data isolation across container instances.

API & Abuse Defense

Automated in-memory IP rate limiting across waitlist signups, public roster queries, and token status verifications to prevent denial-of-service and credential scraping.

02.Cryptographic Status Token Architecture

Our waitlist status verification mechanism is engineered specifically to prevent user enumeration and data leakage:

  • Entropy: Tokens are 48-character strings drawn from a 62-symbol alphanumeric alphabet (62^48 ≈ 1.34 × 10^86 possibilities), rendering brute-force guessing mathematically intractable.
  • One-Way Hashing: Raw tokens are never stored in our primary database. We store only cryptographic SHA-256 hashes.
  • Constant-Time Verification: Token verification executes using crypto.timingSafeEqual to prevent side-channel timing analysis attacks.
  • Masked Data Exposure: The status endpoint returns only the assigned public sequence ID, active status state, and heavily masked email address (m***a@gmail.com).

03.Vulnerability Disclosure Policy (VDP)

We believe that coordinated vulnerability disclosure is an essential component of internet resilience. We welcome responsible security reports from independent researchers, ethical hackers, and academic institutions.

04.Coordinated Disclosure & Safe Harbor

SAFE HARBOR GUARANTEE

HXLABZ will not pursue civil lawsuits or criminal complaints against security researchers who conduct testing in good faith, adhere strictly to the rules below, and coordinate disclosure privately with our security team prior to public disclosure.

Guidelines for Safe Harbor compliance:

  • Do not access, modify, or destroy another user's data or token.
  • Do not execute volumetric denial of service attacks against production infrastructure.
  • Allow our engineering team 90 days to remediate before public disclosure.

05.In-Scope & Out-of-Scope Systems

IN-SCOPE TARGETS:
  • • hxlabz.com & primary web APIs
  • • Token hashing & timing verification flaws
  • • Authentication & authorization bypass
  • • Server-side request forgery (SSRF)
  • • Remote code execution vulnerabilities
OUT-OF-SCOPE:
  • • Volumetric network DDoS / Flooding
  • • Social engineering / Phishing of HX staff
  • • Physical security attacks
  • • Missing SPF/DKIM flags with no exploitability

06.Submission Protocol & Security Contact

Please send encrypted vulnerability reports containing reproduction steps and proof-of-concept payloads to:

Security Operations: info@hsworks.cc.cd

Privacy & Compliance: privacy@hsworks.cc.cd

Direct Lead Escalation: saranmatsa0@gmail.com

Triage SLA: Initial human acknowledgment within 24 hours