Security software should be clear about what it does and what it does not do.
Corvexa is being built around practical security principles: minimize sensitive data, make signals understandable, and only perform active testing against explicitly authorized scope.
Raw passwords are not the product
Corvexa is designed to use password-health and identity signals rather than collect or display employee plaintext passwords.
Authorized scope only
External testing must be limited to customer-authorized systems and scope. Security visibility should not create unauthorized testing risk.
Clear separation of signal and certainty
Corvexa should show what it knows, what needs attention, and where data is incomplete instead of pretending missing data means perfect security.
Built for remediation
The goal is not endless alert volume. Corvexa prioritizes a clear path from security signal to action.
Launch with claims you can support.
This page intentionally avoids claiming certifications, compliance attestations, or active integrations that have not been completed yet.
Does Corvexa store employee passwords?
The product direction is to use security and password-health signals, not store or display raw employee passwords.
Does Corvexa actively scan customer infrastructure?
Any active external testing should only be performed against scope explicitly authorized by the customer.
Which integrations are supported?
Integration capabilities should be listed here only after the corresponding connector is production-ready. The website package intentionally avoids pretending unsupported connectors are live.
Where will formal compliance documentation live?
This Security page can evolve into a full Trust Center as policies, subprocessor information, certifications, retention details and formal security documentation are finalized.