At HashOps, protecting your infrastructure and operational data is our highest priority. We employ a defense-in-depth approach, ensuring security is integrated at every layer of our architecture.
1.Tunneling & Encryption in Transit
All communications between the infrastructure and our control plane utilize secure tunnels via SSTP over Port 443, enforced with industry-standard AES-256 encryption.
2.Data at Rest Encryption
All sensitive operational data, account credentials, and system logs stored within the HashOps databases are encrypted at rest using strong cryptographic algorithms to prevent unauthorized offline access.
3.Network Isolation
Each Farm managed by a Reseller operates on a strictly isolated /24 subnet. This strict segmentation ensures zero overlapping NATs and completely prevents cross-tenant data leakage.
4.Split Tunneling Architecture
HashOps operates exclusively on operational data. Only hardware monitoring telemetry (e.g., temperature, fan speed, hash-rate status) is routed to our control plane. Heavy computational mining traffic flows directly from the ASIC hardware to the designated mining pool, completely bypassing HashOps infrastructure.
5.Strict Access Control & Support Interventions
Routine access to the management panel is secured via mandatory strong authentication protocols. Furthermore, HashOps support personnel have zero default access to customer environments. Support interventions are strictly handled via customer-initiated, time-bound, and tokenized "Temporary Support Access" links.
6.API Security & Authentication
For plans including API access, all endpoint interactions require secure, uniquely generated API keys. HashOps employs automated rate-limiting and continuous monitoring to mitigate abuse, DDoS attempts, or unauthorized automated access.
7.Audit Trails & Accountability
HashOps maintains immutable, timestamped audit logs of critical administrative actions (e.g., configuration changes, reboot commands). This ensures full transparency and accountability for actions taken by Resellers within their authorized subnets.
8.Shared Responsibility & Physical Security
HashOps utilizes a shared responsibility model. For cloud-hosted plans, physical data center security is maintained by strictly vetted, ISO-certified infrastructure providers (e.g., Hetzner, Leaseweb). For Enterprise "On-Premises" deployments, hardware, network perimeter, and physical security are the sole responsibility of the Customer.