SDVOSB NetStable, LLC · Service-Disabled Veteran-Owned Small Business
PKI Hierarchy v1 · Operational
NetStable / Public Key Infrastructure

Secure Production Architecture · Hierarchy v1

Trust roots,
distribution,
verification keys.

This is the public face of NetStable's PKI. Every certificate signed by NetStable chains to the root listed below, and every signed artifact — container image, Helm chart, SBOM, license, code release — can be verified against a key published here.

Hardware-rooted trust. End-to-end accountability. All seventeen signing keys are HSM-backed (FIPS 140-2 Level 3, Google Cloud HSM); no private key material exists outside the hardware boundary.

Status

Operational

Hierarchy

v1 · 2026

HSM keys

17

Trust roots

1

00

Generation v2 — current

One NetStable chain for every product. Artifacts are signed by dedicated HSM signer keys whose certificates chain to this root, and time-stamped by the NetStable Timestamp Authority. Policy: CP/CPS (draft).

NetStable, LLC Root CA v2

SHA-256 7b5834c61086dfd79f9402e95579741ff0e3c5f2f3944e3f2453daf1deaf7a83

Algorithm ECDSA P-384 / SHA-384 Validity 20 years (to 2046) Protection Cloud HSM, FIPS 140-2 L3 Policies PEN 48431
netstable-root-ca-v2.crt

Intermediate v2 · Code Signing CA v2 · Document Signing CA v2 · Timestamping CA v2 · Licensing CA v2

Signers: NetStable Image · Heliopolis Image · NetStable Document · Heliopolis Document

NetStable signers moved to P-256 keys on 2026-09-27 (same identities). Their P-384 predecessors (image, document) are retired from signing and stay published so earlier signatures keep verifying.

cosign: trusted_root.json · signing_config.json · Timestamps: tsa.netstable.io

$ cosign verify --trusted-root trusted_root.json \
    --certificate-identity https://pki.netstable.io/signers/netstable-image-signer \
    --certificate-oidc-issuer-regexp '.*' --insecure-ignore-tlog --insecure-ignore-sct \
    artifacts.netstable.io/netstable/<image>@sha256:<digest>

Generation v1 below remains trusted until its retirement date.

01

The root

Anchor of every NetStable trust chain. Add this certificate to a system or application trust store to validate any chain we publish.

NetStable, LLC Root CA v1

The single anchor under which the Corporate and Heliopolis trust domains both chain. Self-signed, ceremonial only — never used at runtime to issue end-entity certificates.

Algorithm ECDSA P-384 / SHA-384 Validity 25 years pathLen 2 Protection FIPS 140-2 L3 HSM
netstable-llc-root-ca-v1.crt

02

Intermediates

Trust-domain anchors. Customers usually only need the root, but bundling the matching intermediate alongside a leaf cert lets clients validate without an AIA fetch.

  • Corporate Intermediate CA v1

    corporate-intermediate-ca-v1.crt · ECDSA P-384 · 12y · pathLen 1

  • Heliopolis Intermediate CA v1

    heliopolis-intermediate-ca-v1.crt · ECDSA P-384 · 12y · pathLen 1

03

Issuing CAs & cosign keys

Each artifact NetStable signs uses a role-scoped issuing CA. The same KMS-backed key serves both X.509 chain signing (Track A) and raw cosign signature verification (Track B). Public keys for cosign verification live under /verify/.

Corporate · 4 keys

  • Corporate Code Signing Issuing CA v1

    corporate-code-signing-issuing-ca-v1

  • Corporate Document Signing Issuing CA v1

    corporate-document-signing-issuing-ca-v1

  • Corporate Timestamping Issuing CA v1

    corporate-timestamping-issuing-ca-v1

  • Corporate OCSP Issuing CA v1

    corporate-ocsp-issuing-ca-v1

Heliopolis · 9 keys

  • Heliopolis Code Signing Issuing CA v1

    heliopolis-code-signing-issuing-ca-v1

  • Heliopolis Image Signing Issuing CA v1

    heliopolis-image-signing-issuing-ca-v1

  • Heliopolis Chart Signing Issuing CA v1

    heliopolis-chart-signing-issuing-ca-v1

  • Heliopolis SBOM Signing Issuing CA v1

    heliopolis-sbom-signing-issuing-ca-v1

  • Heliopolis Model Signing Issuing CA v1

    heliopolis-model-signing-issuing-ca-v1

  • Heliopolis Licensing Issuing CA v1

    heliopolis-licensing-issuing-ca-v1

  • Heliopolis Document Signing Issuing CA v1

    heliopolis-document-signing-issuing-ca-v1

  • Heliopolis Timestamping Issuing CA v1

    heliopolis-timestamping-issuing-ca-v1

  • Heliopolis OCSP Issuing CA v1

    heliopolis-ocsp-issuing-ca-v1

04

Verifying signatures

Two flows. Adapt to your toolchain.

Add NetStable's root to your trust store
# RHEL / Rocky / Fedora
$ sudo curl -fsSL https://pki.netstable.io/certs/netstable-llc-root-ca-v1.crt \
    -o /etc/pki/ca-trust/source/anchors/netstable-root.crt
$ sudo update-ca-trust

# Debian / Ubuntu
$ sudo curl -fsSL https://pki.netstable.io/certs/netstable-llc-root-ca-v1.crt \
    -o /usr/local/share/ca-certificates/netstable-root.crt
$ sudo update-ca-certificates

# macOS
$ sudo security add-trusted-cert -d -r trustRoot \
    -k /Library/Keychains/System.keychain netstable-llc-root-ca-v1.crt
Verify a Heliopolis container image with cosign
$ cosign verify \
    --key https://pki.netstable.io/verify/heliopolis-image-signing-issuing-ca-v1.pub \
    --insecure-ignore-tlog=true \
    harbor.netstable.io/heliopolis/gateway:rc1

05

Revocation

Two channels. CRL is HTTP per RFC 5280; OCSP is HTTP per RFC 6960. Both bypass HTTPS upgrade by design.

  • Certificate Revocation Lists

    http://crl.netstable.io/ · renewed 16h · cached 24h

  • OCSP Responder

    http://ocsp.netstable.io/ · per-chain · OCSP stapling recommended