QAST
A ranked HNDL register
Exposure windows, harvestability, reachability, and Mosca assumptions stay visible beside the result.
RelixQ Enterprise
Run post-quantum migration as an evidence-backed operating program.
RelixQ connects application evidence, HNDL exposure, safe validation, the RelixQ Score, governance, reports, integrations, retests, and release controls for one Enterprise portfolio.
Product UI
Who it is for
One evidence chain, four enterprise rooms.
Each team gets the operating artifact it needs without creating a separate spreadsheet or losing the technical source behind the claim.
CISO office
Portfolio posture, HNDL trends, score drivers, owners, and board-ready evidence.
View solutionApplication security
Exact findings, context, recommendations, signed-RoE validation, and retest state.
View solutionPlatform engineering
APIs, pipelines, integrations, ownership routing, and release controls.
View solutionGRC and customer trust
Policies, exceptions, audit history, reports, and procurement material.
View solutionPilot scope and deliverables
A pilot should produce board evidence and engineering action.
Start with a bounded application portfolio, data class, TLS surface, and operating integration. Finish with artifacts teams can continue using.
Executive exposure brief
RelixQ Score, HNDL assets, attack paths, owners, assumptions, and priority remediation tracks.
Technical finding register
Code, dependency, TLS, certificate, and protocol evidence with severity, confidence, status, and migration target.
Safe validation package
Approved read-only validation behind a signed Rules of Engagement record, with explicit exclusions and proof boundaries.
Developer control plan
Baseline-aware gates, retests, exceptions, tickets, and integration paths that keep exposure from returning.
SaaS delivery and data handling
One managed service with explicit data boundaries.
RelixQ is delivered as SaaS. Connected sources, managed scans, submitted evidence, and customer-enabled integrations are governed by explicit processing, retention, and access boundaries.
Managed SaaS tenant
Organization-scoped application workflows, connected sources, reports, integrations, and administration are delivered through the RelixQ service.
Controlled source processing
Repository access, scan scope, evidence fields, retention, and deletion boundaries are agreed during evaluation and documented in the service terms.
Configuration-aware integrations
Source, identity, SIEM, ticketing, alerting, and AI-provider behavior depends on the customer-enabled connection.
Security and governance proof
Control the assessment and preserve the decision trail.
RelixQ is designed to make the authorization, assumptions, evidence, and outcome behind each action visible.
Authorization before active work
Signed project-specific Rules of Engagement, allowed scope, exclusions, rate ceilings, blackout windows, and emergency stop.
Evidence without impossible claims
Observed protocol posture and proven classical breaks stay separate from modeled quantum risk. No decryption claim.
Procurement with honest status
The Trust Center labels controls as product capability, verification required, planned, or not claimed.
Coverage, integrations, and alerts
Meet the estate where it is—and move posture into the systems that run it.
RelixQ connects the source and delivery systems that produce evidence, covers the languages and infrastructure in the portfolio, and routes ownership and state changes into the operating stack.
Source and delivery
GitHub, GitLab, Bitbucket, Azure Repos, CI pipelines, CLI, REST API, SBOM import, and runtime telemetry.
Identity and provisioning
Microsoft Entra ID, Okta, Ping Identity, and standards-based OIDC, SAML 2.0, and SCIM 2.0 connections.
Security operations
Splunk, Microsoft Sentinel, Elastic Security, CrowdStrike, OCSF, and generic webhooks.
Observability
Datadog, OpenTelemetry, Dynatrace, New Relic, Grafana, and metric/change-event delivery.
Work, incidents, and alerts
ServiceNow, Jira, Azure Boards, Linear, PagerDuty, Opsgenie, Slack, Teams, email, and other chat destinations.
Evaluation process
A credible first 30 days.
Start passive and bounded. Add active validation only after authority and scope are recorded. Finish by wiring the evidence into ongoing controls.
- 01
Sign up
Request Enterprise access and tell us which QAST, RelixQ Score, PR gate, or reporting workflow you want to evaluate.
- 02
Scope pilot
Pick one app portfolio, data class, TLS surface, and integration path for a controlled assessment.
- 03
Run assessment
Start passive HNDL mapping, then add signed-RoE active validation only for approved targets.
- 04
Operationalize
Turn results into score tracking, tickets, SIEM events, retests, and engineering release gates.
Enterprise FAQ
Questions that should be answered before procurement.
What is QAST?
QAST means Quantum Application Security Testing. In RelixQ, it is the workflow that turns cryptography inventory into HNDL exposure windows, attack paths, safe validation, score impact, reports, and release gates.
Is QAST the same as a quantum penetration test?
No. RelixQ does not claim to decrypt quantum-vulnerable ciphertext. QAST proves exposure, reachability, classical breaks, and modeled quantum risk boundaries.
How is RelixQ different from crypto inventory?
Inventory finds cryptography. RelixQ adds data lifetime, harvestability, attack paths, safe validation, RelixQ Score impact, retests, alerts, tickets, and developer gates.
Request a demo
Scope the portfolio, proof, and operating path.
Tell us whether the evaluation should lead with QAST, the RelixQ Score, inventory, PQC Lab, governance, developer gates, or integrations.
Before you submit
- • Do not send source code, credentials, secrets, or scan evidence.
- • Use the Trust Center document request for procurement material.
- • Active assessment scope is agreed separately through signed Rules of Engagement.