INNOVEXUS
Trust Center · Security

Security architecture.Public summary. Detailed report under NDA.

The summary below is the public-facing description of how Innovexus is built. The detailed security whitepaper, the most recent third-party penetration-test report, and any SOC 2-style evidence package are available on request under mutual NDA via the trust mailbox.

§ 01 / Public summary

Self-hosted appliance architecture

Innovexus is a single self-contained appliance you run on your own infrastructure — compute, storage, and network are entirely yours, not shared with anyone. The appliance hosts the credential vault, session broker, audit chain, and identity surface for your organisation, and it does not call home to any control plane.

Authentication and identity

FIDO2/WebAuthn hardware authentication (YubiKey-class devices) at the platform login. SAML 2.0 and OIDC SSO with any standards-compliant IdP (Okta, Azure AD, JumpCloud, Google Workspace). SCIM 2.0 provisioning. Local-username authentication available as a fallback against organisation-managed databases or AD/LDAP.

Credential vault

AES-256-GCM encryption at rest for all vaulted credentials. The appliance mints its own encryption key on first boot; it never leaves the appliance and is not shared across deployments, so one extracted image cannot decrypt another organisation's vault. Credential rotation is automated (default 24-hour cycle) and atomic with respect to the AAA decision point.

Session brokering

Engineer endpoints connect to the appliance; the appliance brokers the SSH, Telnet, console, RDP, or web-admin session to the target. It is the only authorised source for management connections to enrolled devices (IP allowlisting). Engineers never possess the device-side credential.

Audit chain integrity

Every audit event is hash-chained and signed by the appliance's signing key. Tampering with a session record breaks the signature chain and is detectable on audit. Audit retention default: 90 days for full session video, 7 years for signed audit metadata. Both retention windows are configurable.

Encryption in transit

TLS 1.3 with mutual authentication where supported. SSH protocol versions hardened to current OpenSSH defaults; legacy ciphers disabled. The certificate authority for ephemeral SSH cert issuance is local to your appliance; there is no cross-organisation CA trust.

Threat model — boundary diagram

The boundary diagram below is a public summary of the trust boundaries the detailed threat model treats in depth. Each boundary is the subject of a specific control set in the full whitepaper.

  • Engineer endpoint ↔ appliance: TLS 1.3, FIDO2 platform login, role-based device discovery
  • Appliance ↔ vault storage: AES-256-GCM, per-appliance keys, no plaintext at rest
  • Appliance ↔ target device: SSH/Telnet/console with rotated short-lived credentials, full session recording
  • Appliance ↔ external AI providers (only when you enable AI features with your own key): scoped prompts only, no vault contents, no full session bodies
  • Your administrators ↔ appliance: RBAC with least privilege, audited break-glass workflow, notification on every privileged session — all under your control, with no vendor access

Penetration testing

The Innovexus application undergoes third-party security review covering the application surface, authentication and session brokering layers, and audit-chain integrity. Because the software is open source, the code is also open to inspection by anyone. Fixes land in the published appliance images on the downloads page.

Vulnerability disclosure

We accept responsible vulnerability reports via [email protected]. PGP key available on request. Standard 90-day coordinated disclosure window. We do not pursue legal action against good-faith security researchers following the disclosure policy.

§ 02 / Available on request

Detailed evidence,on request under NDA.

  • Detailed security whitepaper

    Full architecture document covering control families, key custody specifics, threat model walkthrough, and incident response procedures. ~30-page PDF, shared under mutual NDA.

  • Third-party penetration test report

    Most recent annual pen-test report from our independent testing firm. Includes scope, methodology, findings, and remediation status. Shared under NDA after a brief security review of the requestor.

  • SOC 2-style evidence package

    Innovexus does not independently hold a SOC 2 Type II attestation (see /compliance), but the appliance produces an evidence package mapped to SOC 2 Trust Services Criteria for your own audit purposes — control descriptions and sample evidence you can export directly from the box.

  • Data handling

    Because you self-host, there is no data-processing agreement to sign with Innovexus — the software never receives your operational data. Your data handling is governed by your own environment and policies.

  • Disaster recovery posture

    Backup and recovery are yours to run against your own infrastructure. The appliance supports configuration and database backup so you can meet whatever RPO/RTO your environment requires.

Request the detailed package.NDA & response within 1 business day.

NDA REQUIREDSECURITY-REVIEW READY

Email the trust mailbox with a brief description of your use case (a sentence or two — vendor evaluation, security review, etc.). We'll send an NDA template and the requested artifacts within one business day.