Papers for

network security operators

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

Connectedness influences operator load and oversight in cyber defense

Connectedness, Cognitive Load, and Human-AI Oversight in Cyber Operations

Abstract: AI-assisted cyber situational awareness triggers machine-generated reasoning traces (step-by-step justifications for anomaly classifications) that a human operator is expected to review. Because cyber signals and their traces arrive faster than any operator can process, human review is the limiting constraint on oversight. The standard approach is to identify the riskiest cyber events for review using model-side signals such as confidence or uncertainty. That framing ignores the operator's cognitive capacity which varies sharply with the operational environment. We propose an alternative where the system's environmental and connectivity telemetry serves as an available, non-invasive proxy for operator load. That same telemetry determines whether the human-AI partnership can reach the broader collective for support. In a maritime platform, environmental and connectivity attributes including depth, number of active communications paths, density of the tracked contact picture, and operational tempo all carry this signal. Need for operator oversight becomes a decision that materializes as a combination of both risk and environment-derived operator capacity. We present a reference architecture for a connectedness-aware oversight engine, demonstrating everyday use cases alongside its intended incorporation into the submarine cyber-defense toolkit. Two themes emerge: 1) the operator's environmental state is itself a connectedness measurement, and 2) connectedness drives the cognitive load and defines a collective boundary in human-AI cyber operations.

Thu 1 OctHuman-Computer Interaction
The gist
Cybersecurity systems help humans spot threats by showing step-by-step reasons for alerts. But there are too many alerts coming in too fast for someone to check them all. The authors suggest using clues from the environment and communication links to guess how busy or stressed the human operator is. This helps decide when humans should review alerts, not just based on risk but also on the operator’s current ability to handle work. This method was designed for submarines but could apply wherever conditions affect human attention and connectedness.
Open → 2610.02384v1

Measurement reveals exposed Ollama AI model endpoints growing online

Ollama in the Wild: A Longitudinal Measurement of Exposed Ollama LLM Endpoints at Internet Scale

Abstract: Self-hosted large language model (LLM) serving is emerging as a distinct category of Internet service, but we still know little about how these deployments appear and change on the public Internet. We present a 365-day longitudinal measurement of exposed Ollama endpoints (port 11434) from February 2025 to February 2026, combining daily active probing with GeoIP/ASN enrichment, PTR and port-443 host observations, and survival analysis. Across 362 observation days and approximately 4.8 million IP$\times$day observations, 26.4% of the 152,137 cumulative IPs appear for a single day; across five selected CVEs, only 0.43-2.90% of below-fix IPs upgraded in place; the top five countries/regions account for over 70% of weighted observations; and cloud and hosting providers dominate the top ASNs. These results characterize exposed Ollama as a structural exposure surface: persistent, growing, and heavily concentrated. At the same time, old versions, common model choices, cloud and hosting ASNs, PTR categories, and TLS certificate patterns remain visible across the year, indicating recurring insecure deployment practices in cloud infrastructure and the potential reach of provider-level mitigation.

Mon 7 SeptNetworking and Internet Architecture
The gist
Ollama is a service for running large language AI models on private servers, but many of these servers are exposed openly on the Internet. The authors studied these exposed servers over a year, tracking how many appeared, where they were located, and whether they kept outdated or vulnerable software versions. They found many such servers persistently exposed, mostly hosted in cloud environments, often running older versions that could be insecure. This shows a common pattern of insecure deployment practices that could be addressed by cloud providers.
Open → 2609.07115v1