Chapter 5: Selection & Interfaces

Core product introduction, interface logic, connection diagrams, and feature comparison tables

5.1 Core Product Introduction

The log security system is composed of five core hardware and software product categories, each addressing a specific layer of the evidence chain. Product selection within each category should be driven by the capacity requirements established in Chapter 4, the compliance requirements identified in Chapter 3, and the interface compatibility requirements described in Section 5.2. The product overview image below shows the five core product categories in their typical physical form factors.

Core Product Overview
Figure 5.1: Core Product Overview — Five product categories: Log Collector Pro Series (2U), HSM-2000 hardware security module, Vault Storage Array (4U WORM), Ingest Gateway appliance, and Integrity Engine (1U with display)

1. Log Collector Pro Series

Zone Collector Appliance — 2U Rack Mount

The Log Collector Pro Series is a purpose-built appliance for log collection, buffering, and secure forwarding. It supports multiple input protocols (syslog/TLS, Beats, Fluentd, Windows Event Forwarding) and provides local disk buffering for store-and-forward operation during network outages. The appliance includes a TPM 2.0 chip for device identity binding and supports certificate-based mutual TLS authentication to the ingest gateway.

Up to 20,000 EPS 8-core CPU / 32GB RAM 4TB NVMe buffer 4× GbE + 2× 10G SFP+ TPM 2.0 Dual PSU

2. HSM-2000 Hardware Security Module

Key Management Appliance — 1U Rack Mount

The HSM-2000 provides FIPS 140-2 Level 3 certified key management for the log security system. It stores master keys for log encryption, signing keys for hash chain signatures, and key encryption keys for the KMS hierarchy. The HSM enforces dual-control key ceremonies and provides tamper-evident physical protection. All key operations are logged to an immutable internal audit store that cannot be cleared even by the HSM administrator.

FIPS 140-2 Level 3 RSA-4096 / ECC P-384 AES-256-GCM Dual-control ceremony Tamper-evident PKCS#11 API

3. Vault Storage Array

WORM-Capable Storage — 4U Rack Mount

The Vault Storage Array provides the physical storage layer for the Raw Log Vault. It supports WORM (Write Once Read Many) retention locks at the storage platform level, ensuring that immutability cannot be bypassed by software-level commands. The array supports both SnapLock (NetApp-compatible) and S3 Object Lock API modes, allowing integration with both on-premises and cloud-native architectures. Dual-parity RAID with hot spares ensures data durability during drive failures.

WORM / SnapLock S3 Object Lock API 12× 16TB drives RAID-6 + hot spare 10G iSCSI / NFS AES-256 at rest

4. Ingest Gateway Appliance

TLS Termination and Routing — 1U Rack Mount

The Ingest Gateway terminates mTLS connections from zone collectors, enforces the source allowlist, applies rate limiting, and routes log segments to the message queue. It is designed to be stateless and horizontally scalable — multiple gateway instances can be deployed behind a load balancer without coordination. The gateway validates the client certificate CN/SAN against the allowlist on every connection and rejects any sender not explicitly authorized.

mTLS 1.3 50,000 EPS throughput Source allowlist enforcement Rate limiting per source Stateless / scalable 4× 10G SFP+

5. Integrity Engine

Hash Chain and Verification Service — 1U Rack Mount

The Integrity Engine maintains the hash chain across all stored log segments, produces signed verification manifests, and runs scheduled verification jobs to detect any tampering or corruption. It uses SHA-256 for segment hashes and ECDSA P-384 for manifest signatures, with signing keys stored in the HSM-2000. The front-panel display shows real-time verification status, allowing operators to confirm integrity without logging into the management interface.

SHA-256 hash chain ECDSA P-384 signatures HSM-backed signing keys Scheduled verification Front-panel status display REST API for reports

5.2 Typical Interface and Connection Logic

The interface diagram below shows the rear panel of the Log Collector Pro Series appliance with all physical ports labeled and their logical connections to the network infrastructure. Understanding the interface layout is essential for correct cabling, firewall rule configuration, and network segmentation. Each interface serves a distinct security function and must be connected to the appropriate network segment.

Interface and Connection Logic Diagram
Figure 5.2: Collector Appliance Interface Logic — Rear panel showing ETH0–ETH3 (GbE), SFP+0/1 (10G fiber), USB HSM token, Console/RS-232, IPMI management port, and logical connections to Production Network (syslog/TLS 514), Ingest Gateway (mTLS 6514), Storage Network (10G iSCSI/NFS), and OOB Management
InterfaceTypeProtocol / PortConnected ToDirectionSecurity Notes
ETH0GbE RJ45Syslog/TLS 514, Beats 5044Production NetworkInbound onlyAllowlist source IPs; no outbound to production
ETH1GbE RJ45HTTPS 443, SSH 22Management NetworkBidirectionalRestrict to admin VLAN; MFA required
ETH2GbE RJ45mTLS 6514Ingest GatewayOutbound onlyClient cert required; no inbound from SecOps
ETH3GbE RJ45NTP 123NTP ServerOutbound onlyAuthenticated NTP; monitor drift
SFP+010G FiberiSCSI 3260 / NFS 2049Storage NetworkBidirectionalDedicated storage VLAN; no routing to other zones
SFP+110G FiberReserved for HA heartbeatCollector B (peer)BidirectionalDedicated HA VLAN; not routable
USB 3.0USB-APKCS#11HSM TokenLocal onlyPhysical HSM token for signing key access
ConsoleRS-232 DB9Serial consoleConsole serverBidirectionalOut-of-band access; requires physical presence
IPMIGbE RJ45IPMI 623, HTTPS 443OOB Management SwitchBidirectionalSeparate OOB network; change default credentials

5.3 Core Product Function Table

The function table below provides a comprehensive comparison of all five core products across the key functional dimensions of the evidence chain. Each cell indicates whether the product provides the function natively (Native), requires configuration (Config), depends on integration with another product (Integration), or does not provide the function (—). This table is intended to guide procurement decisions and integration planning.

Function Log Collector Pro HSM-2000 Vault Storage Array Ingest Gateway Integrity Engine
Multi-protocol input (syslog/Beats/WEF)Native
Local disk buffering (store-and-forward)Native
mTLS client authenticationNativeIntegrationNative
Source allowlist enforcementConfigNative
Rate limiting per sourceNative
WORM / Object Lock storageNative
AES-256 encryption at restConfigIntegrationNative
Hash chain maintenanceNative
Digital signature (ECDSA)NativeIntegration
Scheduled integrity verificationNative
FIPS 140-2 Level 3 key protectionNative
Dual-control key ceremonyNative
TPM device identity bindingNative
NTP drift monitoringNative
Evidence export with hash manifestConfigNative
Immutable admin audit logNativeConfigConfigConfig
REST API for integrationNativeNativeNativeNativeNative
← Chapter 4: Architecture Design Chapter 6: Security & Risks →