Use Case

The SKADI Cyberdefense huntress icon which represents Frostbow™ SKADI’s autonomous defense platform.
University Research Laboratory

Federally Funded Research Facility — Air-Gapped and Campus-Connected Segments

The Environment

A federally funded research laboratory conducts sensitive dual-use research with national security implications. The network architecture is segmented by design: a campus-connected segment for researcher laptops and collaboration tools, and an air-gapped research workstation cluster for sensitive data and instrumentation, with a controlled data transfer mechanism between them. Specialized lab instruments — oscilloscopes, spectrum analyzers, portable imaging units — are connected to the internal lab network and expose simple web interfaces but cannot run agents. Collaborating institutions exchange data via encrypted file transfer. The institution’s central IT security team has limited visibility into the isolated research segment.

Frostbow Deployment

Frostbow was deployed in a hybrid architecture suited to the segmented environment. A full instance on the campus network covered researcher laptops and collaboration infrastructure. A lightweight read-only log collector on the isolated research segment transferred normalized event summaries across a data diode to the campus instance — no raw data and no external connectivity was required for the isolated segment. Lab instruments were monitored passively via a network tap on the internal switch. The two instances correlated events across the segment boundary, providing a unified view of cross-segment activity.

The Scenario: Insider Threat — Staged Data Exfiltration

A researcher with legitimate access to the air-gapped cluster had accepted an external position and was preparing to depart. In the days before leaving, they began systematically copying research datasets to a personal encrypted USB drive during evening hours, then transferring summary files through the controlled data transfer mechanism to the campus network, where they were exfiltrated via a personal cloud storage account.

How Frostbow Responded

The isolated cluster’s log collector observed USB mount events for a device not previously registered on that workstation. Alone, this was a low-confidence alert — USB activity is common in lab environments — and Frostbow correctly did not act on it in isolation.

The escalation came from the campus-side instance. Fourteen minutes after a controlled transfer completed, the same researcher’s account authenticated to a cloud sync service from their campus laptop. The combination — after-hours activity, unregistered USB on the isolated segment, followed by cloud upload — correlated across both instances and matched a multi-stage concept Frostbow had developed: DataStagingAndExfiltrationChain.

Frostbow blocked the cloud sync connection, flagged the researcher’s campus account for review, and generated an incident timeline spanning both network segments. Because the block occurred mid-upload, only partial files were transferred to the cloud; the most sensitive datasets remained on the isolated cluster.

Key Deployment Characteristics

  • Hybrid deployment across air-gapped and campus network segments
  • Data diode support: normalized summaries only, no raw data crossing the boundary
  • Passive network tap monitoring for instruments without agent capability
  • Cross-segment event correlation between isolated and campus instances
  • Insider threat detection through behavioral baseline divergence over time
Share the Post: