Security

Last updated: July 22, 2026

Security is part of what Chuev Research does for clients, so we hold this Site and our own infrastructure to the same standard. This page covers how we secure reslab.pro and how to report a vulnerability if you find one.

How we secure this Site

• Encryption in transit. The Site is served exclusively over HTTPS/TLS.
• Hardened WordPress core. Core, theme, and plugin updates are applied on a routine schedule; the admin surface is restricted and not indexed.
• Anti-abuse on forms. The contact form is protected by Google reCAPTCHA (v3, score-based) plus server-side rate limiting and keyword filtering, to keep spam and automated abuse out without adding friction for real visitors.
• Least-exposure principle. The Site collects the minimum data needed to operate — see our Privacy Policy — which limits what’s at risk in the first place.
• Backups. The Site and its database are backed up on a routine schedule, independent of the hosting platform’s own snapshots.

How we approach infrastructure security more broadly

Beyond this Site, infrastructure security is one of our service lines — see Production Infrastructure on the homepage. The principles we apply there, for our own systems and for clients, include:

• Infrastructure as Code. Environments are defined in Terraform / OpenTofu and Ansible, not hand-configured — every change is reviewed, versioned, and reproducible.
• GitOps delivery. Changes to running systems flow through version-controlled pipelines rather than direct, untracked access.
• Secrets management. Credentials and keys are handled through the HashiCorp Vault ecosystem rather than stored in plaintext config or repos.
• Network segmentation. Cilium (eBPF-based) enforces workload-level network policy inside Kubernetes clusters, rather than relying on perimeter security alone.
• Backup & recovery. Database backup and point-in-time recovery (e.g. via CloudNativePG for PostgreSQL) are treated as a first-class part of the architecture, not an afterthought.
• High availability & monitoring. Production systems are designed for HA where the engagement calls for it, with resource and health monitoring in place to catch issues before they become incidents.

Specific security controls for a client engagement are always scoped to that engagement’s contract — this section describes our general approach, not a guarantee for any particular system.

Reporting a vulnerability

If you believe you’ve found a security vulnerability affecting reslab.pro or its infrastructure, we want to know. Please report it responsibly:

• Email contact@reslab.pro with a description of the issue, steps to reproduce, and any relevant proof-of-concept.
• Give us a reasonable window to investigate and remediate before any public disclosure.
• Avoid actions that could degrade the Site for other visitors — no automated scanning at disruptive volume, no denial-of-service testing, no accessing or exfiltrating data beyond what’s needed to demonstrate the issue, no social engineering of us or our contacts.

We’ll acknowledge good-faith reports within a few business days and keep you posted as we work through them. Testing conducted in good faith, within the scope above, will not be treated as a violation of our Terms of Use.

Scope

This policy covers reslab.pro and infrastructure we directly operate for it. It does not extend to third-party services we link to or rely on (e.g. Google reCAPTCHA, font/CDN providers) — please report issues in those services directly to their operators. It also does not cover client production systems, which are governed by that client’s own security policy and engagement terms.

Contact

Security reports and questions: contact@reslab.pro.