Minimise exposure
Secrets, internal paths, debug output, backups and administrative interfaces must not be unnecessarily reachable from the public web.
Trust and security
VEQTOR approaches security as an ongoing responsibility across architecture, development, deployment, access and product governance.
Secrets, internal paths, debug output, backups and administrative interfaces must not be unnecessarily reachable from the public web.
Role-based permissions should provide only the access needed for a person's responsibility, with high-impact actions kept under human authority.
Important changes, reports and moderation decisions should be auditable. Security must not create unaccountable power to conceal or destroy evidence.
Public forms and submission systems require bot protection, validation, rate limits and processes for handling malicious behaviour.
Updates, backups and recovery procedures should reduce the risk of extended downtime or permanent information loss.
No platform is described as invulnerable. We distinguish deployed safeguards from planned improvements and respond to discovered risks responsibly.
Public website baseline
✓Cloudflare Turnstile with mandatory server-side Siteverify validation
✓CSRF protection, honeypot checks and submission timing controls
✓Rate limiting without storing raw visitor IP addresses
✓Strict input validation and output escaping
✓Content Security Policy and defensive browser headers
✓Secrets loaded outside the public document root
✓Front-controller routing with directory listing disabled
✓No public upload facility, database or administrative login
Human authority
VEQTOR platforms may increasingly use automation and intelligent assistance, but consequential decisions should remain visible, reviewable and subject to authorised human judgement.
Where a platform affects safety, finances, access, evidence or a person's rights, convenience must not replace accountability.