Home/Platform

One operating layer for enterprise cryptography.

Qinsight Atlas brings discovery, inventory, dependency mapping and policy findings into one cryptographic posture management platform. Understand what your services rely on, investigate exposure and plan post-quantum change.

Atlas dashboard showing governed objects, priority exposures, policy evaluation changes and discovery health
Atlas dashboard · Example environment View larger

Cryptographic discovery

Connected inventory & CBOM

Dependency investigation

Classical & quantum exposure

Discover cryptography across the estate.

Start with the sources you already have. Atlas combines network observation, read-only integrations and imported evidence to bring cryptographic signals into one assessed scope.

Networks & endpoints

Protocol negotiation, certificates and service configuration from supported network discovery.

Cloud & infrastructure

Cloud APIs, workloads, databases and appliances, including configuration context.

HSMs & PKI

Cryptographic metadata from key managers, hardware security modules and certificate systems.

Code, files & existing tools

Source and library evidence, keystores, imported CBOMs, CMDBs and security integrations.

Connect technical discovery to business context.

CMDB enrichment adds CI names, ownership and criticality to help teams identify the right systems and people.

How discovery works

One inventory. Technical detail and business context.

Normalize observations across sources, resolve duplicates and retain provenance. Review cryptographic objects alongside the enterprise assets that use them.

Cryptographic objects

Keys, certificates, algorithms, protocols, protocol configurations and libraries.

Enterprise context

Assets, applications, endpoints, workloads and business services.

Atlas algorithm inventory showing key exchange and signature algorithms, strength, post-quantum classification and status
Atlas inventory · Algorithms viewView larger

Keep the original observations attached, so a normalized record can still be traced back to its source.

Explore inventory & CBOM

Follow the chain
from either end.

Graph Explorer connects cryptographic objects to the services they support. Start with a technical exposure or a business question, then follow the known relationships.

Start with a weak algorithm, key, certificate or priority exposure. Trace its known relationships back to endpoints, applications and business services to help scope investigation and change.

Atlas Graph Explorer with SHA-1 selected and known relationships to endpoints, applications and business services
SHA-1 selected · Known paths to business services · Identifiers redactedView larger

Focus the investigation

Filter by source or severity. Expand relationships and isolate a selected chain.

Inspect the object

Review properties and relationships, then open the underlying inventory record.

Keep the business in view

Connect technical exposure to known applications, workloads and service dependencies.

See how dependency context supports security decisions

Evaluate the evidence.
Investigate what matters.

Review the discovered estate against versioned policies for cryptographic hygiene and post-quantum exposure. Keep findings connected to severity, evaluation results and the evidence behind them.

Exposure that matters today

Weak or disallowed algorithms, legacy protocols, certificate expiry and certificate trust issues.

Dependencies to review for PQC

Quantum-vulnerable cryptography and the known systems that need to be considered in migration planning.

Atlas policy catalogue with versions, severity, latest results and evaluation snapshot context
Atlas policies · Versioned policy catalogueView larger

Give the next team
the context to act.

Bring cryptographic evidence, affected systems and service context into reviews, incident investigation and change planning.

CBOMs for the scope under review

Review an application, endpoint, workload or business service through its connected inventory and Cryptographic Bill of Materials (CBOM) evidence. Retain the assessed scope and known relationships alongside the export.

Evidence that retains its origin

Keep source observations and evaluation context available when teams review a finding or plan a cryptographic change.

Exports & read-only APIs

Use CycloneDX CBOMs, inventory exports and API access to carry context into existing security and governance processes.

In development

ServiceNow ticketing and remediation workflows will extend this context into the change process.

Explore a business-service CBOM

Collect locally.
Connect the evidence in Atlas.

Collection runs in your environment. Cryptographic metadata is brought into Atlas for normalization, relationship mapping and assessment.

Your environment

Discovery & integrations

Network collectors
Read-only APIs
Files, code & imported evidence

MetadataNo private key material
Atlas platform

One connected record

Canonical inventory
Evidence & dependency graph
Policy evaluation & exports

See Atlas against
your own estate.

Choose one business service. Connect a practical set of evidence sources. Agree on what the pilot needs to prove before collection begins.