Security Posture
Built for defense, aerospace, energy, and critical infrastructure. Security by architecture, not bolt-on features.
Security Properties at a Glance
Security Architecture
Single-Port Ingress
All browser traffic enters through one HTTPS port (443). No additional ports, protocols, or VPN tunnels required. The attack surface is a single, well-understood entry point.
No Client-Side Data at Rest
The browser is a rendering surface, not a data store. SammiWeb streams real-time data over WebSocket. When the tab closes, no controlled information remains on the device. No CUI to protect on operator endpoints.
Encrypted Transport
All data in transit is protected by TLS 1.2 or higher. WebSocket connections (WSS) inherit the same encryption as HTTPS. No unencrypted data crosses the network between the appliance and operator browsers.
On-Premise — No Cloud
SammiWeb runs entirely on-premise behind your firewall. No cloud services, no phone-home telemetry, no external dependencies at runtime. No outbound internet access required to operate.
Network Architecture
Operator Network (Browsers)
|
| HTTPS / WSS (Port 443 only)
v
+----------------------------------+
| SammiWeb Appliance |
| |
| TLS 1.2+ Termination |
| Centralized Authentication |
| RBAC Enforcement (32-bit) |
| Audit Logging |
| WebSocket Gateway |
+----------------------------------+
|
| Internal RPC / Shared Memory
v
Operational Network (Data Sources) Operator and data-source networks can be physically or logically separated. The appliance bridges them with authentication and authorization at the boundary.
Authentication & Access Control
Centralized Authentication
All operator authentication is handled by the SammiWeb Gateway — a single authentication point. Operators log in once, receive a JWT session token, and that token is validated on every WebSocket message.
| Property | Implementation |
|---|---|
| Password storage | bcrypt hash (cost factor 10+) — no plaintext |
| Session tokens | JSON Web Tokens (JWT) with configurable expiration |
| Session enforcement | Server-side — Gateway validates every message |
| Session revocation | Immediate — admin can terminate any active session |
| Inactivity timeout | Configurable per-user automatic termination |
| Logon time windows | Configurable per-user time-of-day restrictions |
Role-Based Access Control (RBAC)
- - Security classes — up to 255 named classes, each defining a 32-bit permission mask
- - Per-user class assignment — each operator is assigned to a security class
- - Per-format access levels — individual displays can require specific security levels
- - Command authorization — the Gateway enforces permission masks before any command reaches the runtime. Unauthorized commands are rejected server-side.
- - Dual enforcement — Gateway enforces server-side (authoritative) and RuntimeWeb enforces client-side (hides/disables unauthorized controls). Both layers operate.
Audit & Logging
SammiWeb logs operator actions for post-incident analysis and compliance evidence. All logs are written server-side on the appliance. No audit data is stored on or accessible from client browsers.
| Event Type | Logged |
|---|---|
| Login success / failure | Yes |
| Session start / end | Yes |
| Command execution (operator, timestamp, target) | Yes |
| Configuration changes | Yes |
| Session lifecycle (timeout, revocation, disconnect) | Yes |
Deployment Security
Minimal Attack Surface
- Two RPM packages on RHEL 8/9
- Dedicated service account — no interactive login shell
- No internet access required at runtime
- No database server — file-based configuration
- Minimal dependency footprint
Network Segmentation
- Appliance sits at the network boundary
- Operator and data-source networks can be separated
- Authentication and authorization at the boundary
- No lateral access from browser to data sources
NIST SP 800-171 Alignment
NIST SP 800-171 defines 110 security requirements across 14 control families for protecting Controlled Unclassified Information (CUI). SammiWeb's architecture directly supports requirements in the following control families:
| Control Family | Requirement | How SammiWeb Supports |
|---|---|---|
| 3.1 Access Control | Limit system access | RBAC security masks, per-user sessions, least-privilege, single ingress |
| 3.3 Audit & Accountability | Create and retain audit records | Command audit trail, session logging, action records, server-side storage |
| 3.4 Configuration Mgmt | Baseline configurations | Centralized server config, no client software, versioned RPM deployments |
| 3.5 Identification & Auth | Authenticate users | Centralized Gateway auth, bcrypt hashing, password policy, JWT sessions |
| 3.8 Media Protection | Protect CUI on media | No client-side data at rest — browser is view-only, no CUI on endpoints |
| 3.13 System & Comm Protection | Protect communications | TLS 1.2+ on all connections, single port 443, network segmentation |
SammiWeb supports and aligns with NIST SP 800-171 technical controls through its architecture. Full compliance also requires organizational policies, procedures, and processes that are the responsibility of the deploying organization. Kinesix Software has completed a NIST SP 800-171 self-assessment and can support customers in understanding how SammiWeb fits within their security boundary.
CMMC Framework Alignment
The Cybersecurity Maturity Model Certification (CMMC) framework builds on NIST SP 800-171 and applies to Department of Defense contractors.
| CMMC Level | Requirements | Assessment | SammiWeb Alignment |
|---|---|---|---|
| Level 1 | 17 basic practices (FAR 52.204-21) | Self-assessment | Exceeds requirements |
| Level 2 | 110 controls (= NIST SP 800-171) | Self or C3PAO | Technical controls supported |
| Level 3 | 800-171 + 800-172 enhanced | Government-led | Architecture supports; enhanced controls org-dependent |
Security: Build vs. Buy
Organizations that build custom web-based HMI systems inherit the full security burden of that software.
| Concern | Custom-Built Web HMI | SammiWeb |
|---|---|---|
| Security patching | Your team owns it | Vendor-managed updates |
| Penetration testing | Your team funds it | 30 years of hardening |
| Supply chain risk | Every dependency is a vector | Minimal footprint, vendor-audited |
| Audit trail | Must be built | Built-in logging |
| Authentication | DIY — vulnerabilities likely | Production RBAC + JWT |
| Compliance evidence | Generated from scratch | Self-assessment completed |
Security Questions?
Contact us to request the full NIST SP 800-171 self-assessment summary or discuss how SammiWeb fits within your security boundary.