MétaCan
Menu
Back to cohort
Record W2891411705 · doi:10.1109/jsyst.2018.2866465

Optimization of Trust Node Assignment for Securing Routes in Smart Grid SCADA Networks

2018· article· en· W2891411705 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueIEEE Systems Journal · 2018
Typearticle
Languageen
FieldEngineering
TopicSmart Grid Security and Resilience
Canadian institutionsUniversity of Ottawa
Fundersnot available
KeywordsSCADAComputer scienceSmart gridComputer networkNetwork packetDistributed computingSoftware deploymentNetwork topologyComputer securityEngineering

Abstract

fetched live from OpenAlex

The move toward a smart power grid has widened the range of cyber vulnerabilities in supervisory control and data acquisition (SCADA) systems. Specialized security hardening devices, such as the trust systems, are being developed to protect energy SCADA networks from possible cyberattacks. The trust systems are network security resources that monitor and act on malicious packets. A node is said to be a trust node when it is equipped with a trust system. This paper investigates the optimal security deployment problem in resource-constrained SCADA networks. It proposes two deployment schemes for inline security devices: 1) link coverage maximization; and 2) minimal path tolerance (MPT). The first scheme focuses on the overall monitoring coverage. It is formulated as a quadratic assignment problem. The second scheme focuses on the hop distance between consecutive trust nodes. It uses a heuristic approach that deploys trust nodes in a distributive manner. The proposed schemes are evaluated considering the IEEE test case topologies under various scenarios. Numerical results demonstrate that the proposed schemes are capable of achieving their primary goals. They also reveal a performance tradeoff between the proposed schemes in the highly resource-constrained scenarios where MPT offers a better distributiveness.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.741
Threshold uncertainty score0.421

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.010
GPT teacher head0.217
Teacher spread0.207 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it