Security
Security deserves more than a checkbox.
Testing touches source code, credentials, and production-critical logic. Below are the principles guiding BXVTech's design. Items are marked as planned until implemented and independently verifiable. We hold no security certifications or third-party audits at this time.
Access and permissions
Role-based access and workspace-scoped permissions, so people only see and run what their role requires. Planned
Credential management
Test credentials stored as managed secrets, injected at execution time, and excluded from logs, screenshots, and generated reports. Planned
Test environment boundaries
Tests run against explicitly configured environments. Targeting live systems should require deliberate configuration and approval. Design principle
Execution controls
Control who can trigger runs, which environments they target, and whether proposed test repairs require approval before being applied. Repairs change test code only — never application code. Planned
Logging and auditability
Traceable records of executions, approved changes, and relevant administrative actions. Planned
Data handling
Collect only the evidence needed to investigate failures, and give teams control over retention. Specific storage locations and encryption details will be documented once finalized; we don't make guarantees we can't yet verify.
Vulnerability reporting
If you believe you've found a security issue, please reach out through our contact form with “Vulnerability report” in the subject. Please avoid accessing data that isn't yours.
Security questions
Have a security questionnaire or specific requirements? Tell us about them and we'll respond with what's in place today and what's planned.