SECURITY ARCHITECTURE

Understand the cryptographic and network boundaries of TrustNode.

TrustNode is fundamentally designed around the principle of data locality. The security engine operates inside your infrastructure, ensuring that sensitive source code and operational credentials remain under your control.

THE TRUSTNODE BOUNDARY

Below is a diagram illustrating the flow of data across the TrustNode architectural boundary.

PRIVATE ENVIRONMENT
─────────────────────────────────────────────────────────────
[ Repositories ] [ Credentials ] [ Scan Engine ] [ Queue ]
       ↓                ↓               ↓             ↓
[ Database ]     [ Findings ]    [ Reports ]     [ Core ]
─────────────────────────────────────────────────────────────
                             ↓
              TRUSTNODE SECURITY BOUNDARY
                             ↓
─────────────────────────────────────────────────────────────
EXTERNAL SERVICES
[ Git Provider ] [ License Validation ]

DATA ISOLATION

TrustNode only communicates with the external network under strictly defined conditions:

• License Validation: Cryptographically verifies the installation token via outbound HTTPS.
• Release Updates: Securely fetches signed engine updates.
• Git Operations: Pulls from external Git providers if configured (e.g., GitHub, GitLab).