Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Stephen McLaughlin 0003

dblp:29/4916-3 · DBLP profile ↗
← Back
2ranked-venue papers
2as first author
0since 2021 · last 2016
0000-0002-9558-8294ORCID · corroborated

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 1 · 1 first-authorApplied, interdisciplinary, general and emerging computing · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Network and information security
2 papers
Cyber-physical and IoT security · 40% Systems and software security · 35% Network security · 12%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Embedded and real-time systems · 100%

Topics — the 5 heaviest of 6, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Cyber-physical and IoT security
industrial control system security
0.212016
The Cybersecurity Landscape in Industrial Control Systems · Proc. IEEE 2016
Network security › intrusion detection and prevention
intrusion detection
0.112016
The Cybersecurity Landscape in Industrial Control Systems · Proc. IEEE 2016
Cryptographic primitives and cryptanalysis
security analysis
0.112016
The Cybersecurity Landscape in Industrial Control Systems · Proc. IEEE 2016
Embedded and real-time systems
cyber-physical system platforms
0.112015
Blocking unsafe behaviors in control systems through static and dynamic policy enforcement · DAC 2015
Embedded and real-time systems › cyber-physical system platforms
programmable logic controllers
0.112015
Blocking unsafe behaviors in control systems through static and dynamic policy enforcement · DAC 2015

Methods — techniques the papers use, named apart from their topics

static policy enforcement · 0.4dynamic policy enforcement · 0.4
YearPublicationVenuePosition
2016 The Cybersecurity Landscape in Industrial Control Systems
abstract
Industrial control systems (ICSs) are transitioning from legacy-electromechanical-based systems to modern information and communication technology (ICT)-based systems creating a close coupling between cyber and physical components. In this paper, we explore the ICS cybersecurity landscape including: 1) the key principles and unique aspects of ICS operation; 2) a brief history of cyberattacks on ICS; 3) an overview of ICS security assessment; 4) a survey of “uniquely-ICS” testbeds that capture the interactions between the various layers of an ICS; and 5) current trends in ICS attacks and defenses.
Stephen McLaughlin 0003, Charalambos Konstantinou, Lucas Davi, Ahmad-Reza Sadeghi, Michail Maniatakos, Ramesh Karri
Proc. IEEE1
2015 Blocking unsafe behaviors in control systems through static and dynamic policy enforcement
abstract
One of the most universally accepted practices in computer security is the use of security policy enforcement. Under a policy enforcement regime, users and programs can only perform actions for which they are authorized by the security policy. Unfortunately, modern control systems fail to make effective use of policy enforcement. In many cases, privilege in control systems is binary--a single password is sufficient to gain most or all privileges within the system. In this paper, we consider the benefits and challenges of enforcing security policies for code running on Programmable Logic Controllers (PLCs). We first summarize two of our previous approaches, which place no trust in the PLC to behave correctly. While these approaches show promise, especially for current PLC architectures, they are lacking in comparison to approaches based on a trustworthy PLC design. Thus, we argue that future PLCs should implement a Trusted Computing Base (TCB). Such a TCB is a small set of trusted hardware and software that is sufficient for enforcing policies directly on the PLC. We also propose a method of doing policy enforcement on PLCs supporting a small TCB, and argue that it is the simpler and more effective means of doing policy enforcement for PLCs. We conclude that future PLCs should support a small TCB.
Stephen McLaughlin 0003
DAC1