Active API Keys
API Requests
System Status
Data Encrypted
Recent Activity
API Key Management
Live System Health
Response Time
Error Rate
Throughput
Active Connections
Discovered Systems
Download Discovery Agent
Scan your infrastructure for cryptographic assets
Quick Install (Linux/macOS)
curl -sSL https://api.pqcrypta.com/stream/downloads/discovery-agent/install.sh | bash
π This is not blind curl | bash: the script fails closed β it verifies the binary's Ed25519 signature (against a key pinned in the script) and its SHA-256 checksum before it ever marks the file executable. Every release is hybrid-signed β classical Ed25519 and post-quantum ML-DSA-65 (NIST FIPS 204). Verify by hand or on an air-gapped host: see Verify Your Download. Manifest & signatures: SHA256SUMS Β· .sig Β· .mldsa.sig
Configuration Presets
Pick your system's role, add your API key, run with --config. The agent is fully config-driven: --config makes that file's paths authoritative; with no --config it falls back to the same built-in per-OS defaults you can download below as full catalogs and edit. Exclusions are opt-in — a run skips nothing unless your config lists excluded_paths: the role presets ship a sensible set active, the full catalogs leave it commented for you to enable (recommended before a --full-disk-scan).
nginx / Apache / HAProxy / Caddy β Let's Encrypt, server cert dirs, SSH, plus a live check of the certificate served on :443
# PQCrypta Enterprise Discovery Agent Configuration
# This file controls the behavior of the crypto asset discovery agent
# API endpoint configuration
api_url = "https://api.pqcrypta.com"
api_key = "your-api-key-here"
# Filesystem paths to scan for certificates, keys, and SSH keys
# (SSH host/user keys are picked up automatically from .ssh directories,
# even without a matching file extension)
scan_paths = [
"/etc/ssl/certs",
"/etc/pki",
"/usr/local/share/ca-certificates",
"/root/.ssh",
"/opt/",
]
# Enable deep scanning (slower but more thorough)
deep_scan = false
# Paths to exclude from scanning
excluded_paths = [
"/proc",
"/sys",
"/dev",
"/tmp",
]
# Source-code trees to scan for weak-crypto API calls (CBOM: MD5, SHA-1, DES,
# RC4, ECB mode, undersized RSA key generation). Off by default.
code_scan_paths = []
# Database connections to scan (optional β uncomment to enable). Reads actual
# column values for columns matching %cert%/%key%/%pem% and attempts to parse
# them; never stores the raw value, only structural metadata.
# [[database_connections]]
# name = "Production PostgreSQL"
# db_type = "postgres"
# dsn = "postgres://user:password@localhost/dbname"
database_connections = []
# Network services to inspect for live TLS certificates β reflects what's
# actually being served right now, not just files sitting in a cert store.
[[network_targets]]
host = "example.com"
port = 443
# Network appliances (F5 BIG-IP / Citrix NetScaler) β scanned agentlessly over
# their management API from any host that can reach it. A READ-ONLY account is
# enough (F5 Auditor role / NetScaler read-only command policy). Beyond the cert
# store this also records device facts and which virtual server serves each cert
# (or flags it an unbound spare). Uncomment and fill in to enable.
# [[appliance_targets]]
# name = "F5 BIG-IP Production"
# appliance_type = "f5" # "f5" or "netscaler"
# mgmt_url = "https://f5-mgmt.example.com"
# username = "readonly-user"
# password = "your-password-here"
# verify_tls = true # false only for a self-signed mgmt cert
# ββ Run modes (pick one; not config keys β command-line flags) ββββββββββββββββ
# Submit to dashboard : ./pqcrypta-discovery --config agent-config.toml
# Raw JSON file : ./pqcrypta-discovery --config agent-config.toml --output results.json
# Offline / air-gap : ./pqcrypta-discovery --config agent-config.toml --offline-report ./assessment
# (report.html + cbom.json + inventory.json, ZERO network β no api_url/api_key needed)
Quick Start Guide
- Download the agent for your platform above
- Make executable (Linux/macOS):
chmod +x pqcrypta-discovery - Run with your API key:
./pqcrypta-discovery \ --api-url https://api.pqcrypta.com \ --api-key YOUR_API_KEY
Common Options
What It Scans
| Hostname | Operating System | IP Addresses | Subnets | Gateway | Interfaces | Security Score | TPM | Secure Boot | Last Scan | Actions |
|---|---|---|---|---|---|---|---|---|---|---|
|
Loading systems data... |
||||||||||
API Requests
Active Keys
Assets Inventoried
Scans (30d)
Policy Violations
PQC Readiness Trend
View as table
Discovery Activity β Last 30 Days
View as table
API Request Volume
View as table
API Latency
View as table
Top Endpoints
Inventory Growth
View as table
API Requests by Key
View as table
Compliance Status
Risk Level
Certificate Expiry β Next 12 Months
View as table
Assets by Device
Top Algorithms
Open Violations by Severity
Recent Discovery Scans
IP Allowlist Management
Restrict API access to specific IP addresses or CIDR blocks. Leave empty to allow all IPs.
API Key IP Restrictions
Configure per-key IP restrictions for enhanced security
Active Sessions
Recent Security Events
Migration Status
Total Assets
Total Devices
Compliant Assets
Legacy Assets
Deprecated Assets
Forbidden Assets
Quantum Readiness
Organization Controlled
Vendor Controlled
Last Scan Duration
Discovery Coverage
By Remediation Owner
| Owner | Actionable | Total Assets | Compliant | Legacy/Non-Compliant | What To Do |
|---|---|---|---|---|---|
Certificate Lifecycle
Click a row to see exactly those assets in the inventory below.
By Expiration
| Window | Assets |
|---|---|
By Age (Issued)
| Window | Assets |
|---|---|
Compliance Status by Algorithm
| Algorithm | Total Assets | Compliant | Legacy | Critical Risk | Status |
|---|---|---|---|---|---|
Urgent Migrations Required
| Location | Device | Algorithm | Risk Level | Recommendation | Expires |
|---|---|---|---|---|---|
Asset Inventory
Certificate Bundles
| # | Bundle Path β | Device β | Certificates β | Actions |
|---|---|---|---|---|
Keystores
JKS, JCEKS, PKCS#12 / PFX, NSS and other key-storage containers — each certificate inside is also its own inventory asset. Click a row to drill into its entries. NSS cert9.db certificates are read directly; a container marked locked is protected by a non-default password — configure the agent's keystore passwords (inline, a secrets file, or a Vault/AWS/1Password command) to open it, all resolved on the host.
| # | Keystore Path | Device | Type | Encrypted | Certificates | Actions |
|---|---|---|---|---|---|---|
Compliance Report Builder
Build a report on exactly the data you need: combine any filters, pick the columns each row shows, group by device or keep a flat list, then export as a print-ready PDF, CSV, or JSON. Filters use the same semantics as the Compliance inventory — the same criteria always select the same assets.