이름: Weaknesses Addressed by the Top 20 Secure PLC Coding Practices

CWE entries in this view (graph) are fully or partially eliminated by following the guidance presented in the Top 20 Secure PLC Coding Practices, as published by the Secure PLC Programming project in 2021.

CWE 구성원

CWE-1120: Excessive Code Complexity 기본

CWE-128: Wrap-around Error 기본

CWE-129: Improper Validation of Array Index 기본

CWE-1320: Improper Protection for Outbound Error Messages and Alert Signals 기본

CWE-190: Integer Overflow or Wraparound 기본

CWE-345: Insufficient Verification of Data Authenticity 기본

CWE-353: Missing Support for Integrity Check 기본

CWE-354: Improper Validation of Integrity Check Value 기본

CWE-369: Divide By Zero 기본

CWE-653: Improper Isolation or Compartmentalization 기본

CWE-754: Improper Check for Unusual or Exceptional Conditions 기본

CWE-778: Insufficient Logging 기본

CWE-787: Out-of-bounds Write 기본

CWE 뷰 정보

취약점 매핑 메모

근거 : This entry is a View. Views are not weaknesses and therefore inappropriate to describe the root causes of vulnerabilities.
댓글 : Use this View or other Views to search and navigate for the appropriate weakness.

메모

The relationships in this view were determined based on specific statements within the rules from the practices. Not all rules have direct relationships to individual weaknesses, although they likely have chaining relationships in specific circumstances.
Some of the rules in the guide did not have clear relationships to existing CWE entries. This suggests that there might be gaps in CWE, or some of the practices in the PLC Top 20 are not specific to weaknesses.

대상

이해관계자	설명
Software Developers	By following the practices in the list, PLC developers will be able to fully or partially prevent the weaknesses that are identified in this view. In addition, developers can use a CWE coverage graph to determine which weaknesses are not directly addressed by the guide, which will help identify and resolve remaining gaps in training, tool acquisition, or other approaches for reducing weaknesses.
Product Customers	If a developer claims to be following these practices, then customers can search for the weaknesses in this view in order to formulate independent evidence of that claim.
Educators	Educators can use this view in multiple ways. For example, if there is a focus on teaching weaknesses, the educator could link them to these practices.

제출

이름	조직	날짜	출시일	Version
CWE Content Team	MITRE	2026-10-07 +00:00	2026-10-28 +00:00	5.0

참고 자료

REF-1550

Secure PLC Coding Practices: Top 20 List
Secure PLC Programming project.
https://plc-security.com/

CWE-1460 뷰 상세 정보

CWE-1460