2018 International Conference on Computer and Applications (ICCA) 2018
DOI: 10.1109/comapp.2018.8460287
|View full text |Cite
|
Sign up to set email alerts
|

PLC Code-Level Vulnerabilities

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4

Citation Types

0
12
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
3
2

Relationship

1
4

Authors

Journals

citations
Cited by 19 publications
(12 citation statements)
references
References 3 publications
0
12
0
Order By: Relevance
“…By that operators would not notice the problem since a malicious code is going stealthy and unnoticed way; i.e. recognizing threats after the damage occurs [17]. • Fake outcomes: occurs when PLC code skips certain rungs or parameters; e.g.…”
Section: Plc Code Vulnerabilitiesmentioning
confidence: 99%
See 4 more Smart Citations
“…By that operators would not notice the problem since a malicious code is going stealthy and unnoticed way; i.e. recognizing threats after the damage occurs [17]. • Fake outcomes: occurs when PLC code skips certain rungs or parameters; e.g.…”
Section: Plc Code Vulnerabilitiesmentioning
confidence: 99%
“…8, if they are duplicated in more than one rung, their values will be unpredictable, affecting the logic code and the process controlled by it. Also, that will make it harder to debug the code and find or identify the problem [17]. • Unused tags: defining tags in the controller database that are not used in the logic could increase the level of threats; especially if the tags are not driven by a well-defined ladder logic.…”
Section: Plc Code Vulnerabilitiesmentioning
confidence: 99%
See 3 more Smart Citations