AtlasAvailable

Readiness intelligence

AetherQ Atlas

Move from cryptographic visibility to controlled migration.

Request an enterprise pilot
Readiness intelligenceMove from cryptographic visibility to controlled migration.
WHAT ATLAS CAN DO TODAY

Evidence-led control from discovery to selected execution.

Coverage and execution remain bounded by approved access, configured connectors, target qualification, customer permissions, and the agreed scope.

Cryptographic discovery

Atlas can collect approved cryptographic metadata from:

  • Certificates and TLS endpoints
  • Windows certificate stores
  • Certificate and configuration files
  • Approved IIS, Apache, Nginx, and Tomcat paths
  • Java keystore references
  • Selected cloud and infrastructure connectors
  • VMware environments
  • Supported database connectors
  • Customer-provided ownership and business context
Atlas does not imply complete enumeration of every cryptographic component in an enterprise environment.

Evidence-based assessment

Atlas evaluates:

  • Certificate validity and expiry
  • Cryptographic algorithms and key sizes
  • Private-key exposure indicators
  • Trust-store context
  • Encryption configuration
  • Ownership and business context
  • Operational criticality and dependencies
  • External exposure
  • Confidentiality requirements

Results distinguish current operational problems, classical cryptography vulnerable to future quantum attacks, detected PQC or hybrid candidates, and unknown or insufficient evidence.

Readiness results support planning. They are not compliance certification or predictions of when cryptographically relevant quantum computers will arrive.

Migration planning

Asset-level recommendations and migration records can contain:

  • Proposed targets
  • Priority and ownership
  • Environment and dependencies
  • Prerequisites and compatibility evidence
  • Recovery requirements
  • Approval responsibilities and change windows
  • Exceptions and ticket references
  • Go/no-go decisions
Approved plans remain linked to the evidence and revisions that informed them. Approval of a plan does not automatically authorise execution.

Selective migration execution

Current engineering paths include:

  • Selected Nginx certificate replacement workflows
  • Java JKS and PKCS12 alias-replacement workflows
  • Opt-in IIS HTTPS-binding workflows subject to customer-environment qualification

Every live change requires appropriate permissions, target qualification, exact-change approval, validation requirements, and recovery safeguards.

Unsupported applications, source-code changes, consumer trust distribution, CA transitions, shared-binding coordination, and unsupported cloud or infrastructure changes remain engineering-led activities.

Validation and recovery evidence

Depending on the qualified adapter, Atlas can verify:

  • Resulting certificate or alias
  • Expected fingerprint and hostname
  • Trust chain and TLS connectivity
  • HTTP or service health
  • Subsequent rediscovery
  • Before-and-after evidence and drift
  • Acceptance status and recovery results
Validation is adapter-specific. A successful service response does not prove that every dependent application remains compatible.
PRODUCT EVIDENCE

Evidence that remains connected to the decision.

Atlas provides working views and exports across the controlled migration lifecycle.

Request an evidence walkthrough ↗
  • Cryptographic inventory
  • Findings and assessment
  • Risk and readiness
  • Standards-oriented evidence
  • Migration planning and waves
  • Execution readiness
  • Connector health and scan history
  • Approval and change records
  • Verification results
  • Pilot and handover packages
  • Atlas-format CBOM attestations
DEPLOYMENT MODEL

Deployed within the customer’s environment.

The initial Atlas model uses a dedicated installation hosted within the customer’s approved infrastructure.

The customer controls

  • Infrastructure
  • Operating system
  • Networking
  • Backups
  • Credentials
  • Collection scope
  • Schedules
  • Change approvals

AetherQ provides

  • Installation assistance
  • Configuration guidance
  • Atlas releases
  • Product security fixes
  • Documentation
  • Upgrade guidance
  • Troubleshooting
  • Pilot analysis and reporting

Customer hosting does not transfer responsibility for Atlas product defects to the customer.

COLLECTION ARCHITECTURE

Customer-controlled access and approved metadata.

Managed endpoint collectors initiate outbound HTTPS connections to Atlas and do not open inbound listening ports on the endpoint.

Network TLS discovery, cloud connectors, database connectors, and migration validation require approved connectivity to their relevant targets.

Collectors send approved discovery metadata such as hostnames, approved paths, certificate attributes, algorithms, key sizes, fingerprints, resource identifiers, configuration observations, collection status, and supplied ownership context.

Ordinary discovery is designed not to upload private-key contents. Separately approved migration workflows may handle protected key material. Configured integrations may store credentials and therefore require their own data-flow and security review.

AUTHENTICATION AND ACCESS

Access aligned to the customer environment.

  • Local account authentication
  • Role-based access
  • Session controls
  • Login-abuse protection
  • Microsoft Entra integration using an authorisation-code flow with PKCE
  • MFA enforcement through the customer’s Entra policy, subject to configuration and qualification

Atlas does not currently claim general SAML support, universal OIDC-provider support, or independently isolated shared-SaaS tenants.

Atlas is available for controlled enterprise pilots.

Request an enterprise pilot