Part 1 identifies a threat model consisting of named threat actors, attack vectors and reference incidents. This section maps each to the control layer in BifrostConnect that addresses it.
Part 1 names five classes of threat actor relevant to OT third-party access. Nation-state APTs (e.g. Volt Typhoon, Sandworm) pursue strategic pre-positioning in critical infrastructure. Ransomware operators monetise disruption and exfiltration. Hacktivists target utilities for political messaging. Malicious insiders abuse authorised access. Supply-chain attackers weaponise the vendor relationship itself.
| Threat actor (Part 1) | How BifrostConnect reduces the remote-access attack surface for this actor |
|---|---|
| Nation-state actors (e.g. Volt Typhoon, Sandworm) | Removes the always-on remote-access tunnel that LOTL-style intrusions reuse. Hardware trust boundary, no local web services, signed firmware only, OTA-only updates, and non-reversible fuse-enforced secure boot reduce the Unit’s own exploitable surface. Does not address SOHO-router compromise, spear-phishing, or other entry vectors these actors are known to use. |
| Ransomware groups targeting OT (e.g. ALPHV/BlackCat) | Closes the always-on remote-access path that ransomware operators have used to reach OT (Colonial Pipeline pattern). No persistent tunnel, no broad network access, session-based teardown. SessionGuard provides post-incident reconstruction when deployed and active. Does not address phishing, IT-side compromise, or backup destruction; ransomware response requires a complete IR programme. |
| Insider threat (authorised user acting beyond scope) | Individual identity (no shared accounts), session recording where SessionGuard or AccessGuard is deployed, SIEM forwarding (Dedicated Cloud tier), JIT time-boxing, and least-privilege role model in Bifrost Manager raise the cost and traceability of insider misuse during the approved session window. Does not prevent misuse during a legitimately approved session; that residual risk is addressed in the Part 1 residual-risk section through procedural controls. |
| Compromised vendor (supply chain) | Physical broker isolates vendor PC from OT network. For KVM sessions, vendor PC has no network access to OT at all. For IP tunnel sessions, vendor PC IP never appears on the OT LAN; masquerading enforces address translation. Does not address compromise inside the vendor session itself (e.g. malicious code already present on the vendor laptop being executed during a legitimate session); SessionGuard recording supports detection and forensics, not prevention. |
| Opportunistic external scanner | Endpoints never exposed to the internet; endpoint IP addresses hidden; port scans through Bifrost interface are impossible because no inbound port is open. |
The attack vectors that recur across published OT incidents cluster into five patterns: exposed remote access (VPN or RDP left reachable), credential theft and reuse, supply-chain compromise via vendor tooling, unpatched OT endpoints exploited through living-off-the-land techniques, and shared bastion or jump hosts that become persistent footholds. Each vector is addressed below.
| Attack vector (Part 1) | Bifrost mitigation |
|---|---|
| Credential theft / reuse | Mandatory MFA (Auth0); TOTP tied to the Bifrost Unit in attended mode; no credentials pass through the Bifrost Service in the clear. |
| Lateral movement from vendor PC | For KVM: no network-layer connectivity exists. For IP tunnels: operator PC does not receive a local IP on the OT network – masquerading translates source addresses. Subnet mappings are scoped to specific endpoints. |
| Persistent access paths / forgotten tunnels | Direct Native Access sessions terminate on browser close; Direct Tunnel Access subnet mappings can be configured as time-bound on the Advanced plan and Dedicated Cloud tier. No standing IP path exists by default. |
| Man-in-the-middle on transport | TLS for signalling, DTLS-SRTP end-to-end for WebRTC, WireGuard encryption for Direct Tunnel; private keys never leave the client. |
| Living-off-the-Land techniques in OT | Session recording captures all vendor tool usage regardless of whether the tool is ‘legitimate’. Protocol-level detection requires OT-IDS co-deployment (see Co-deployment categories). |
| Untracked vendor software on OT station | AccessGuard is designed to scope which applications the vendor can launch; session video captures all activity regardless of application. |
Five publicly documented incidents illustrate the failure modes that Part 1’s framework is designed to prevent: Colonial Pipeline (2021, exposed credential on a legacy VPN); TRITON / TRISIS (2017, safety-system compromise via engineering workstation); Oldsmar water treatment (2021, attribution disputed, shared TeamViewer credential); Ukrainian grid (2015, BlackEnergy against utilities via phishing and VPN abuse); and the Danish energy-sector campaign (SektorCERT, attacks May 2023, public report November 2023; 22 energy companies impacted across two waves via Zyxel firewall vulnerabilities, CVE-2023-28771 and the zero-days CVE-2023-33009 and CVE-2023-33010). Part 1 highlights three of these (Colonial Pipeline, the SektorCERT campaign, and TRITON / TRISIS) as its core reference incidents; Part 2 expands the set to five to cover the failure modes most often raised in OT procurement and audit reviews.
| Incident class (Part 1) | What Bifrost would have constrained |
|---|---|
| Oldsmar, Florida (2021, attribution disputed) | Individual accounts, MFA, closed-by-default, session video would have given a named operator, a recording, and a bounded window – none of which existed. |
| Pipeline incident via exposed credentials | No persistent credential path; sessions require TOTP; SIEM export would have flagged anomalous authentication attempts in real time. |
| Supply chain malware via vendor laptop | For KVM sessions: vendor PC never has network access to OT assets. For IP tunnel sessions: vendor PC IP never appears on the OT network. |
| Engineering station compromise via shared admin password | AccessGuard is designed to enforce individual accounts and mandatory MFA; the architecture is designed so shared admin credentials cannot be configured. |
| Danish energy sector attack (2023, 22 companies via firewall vulnerabilities) | Bifrost Unit does not require inbound firewall rules on the OT network. The attack exploited exposed firewall management interfaces; the Bifrost Unit exposes none. |