脆弱性マッピングノート
理由 : 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/