Development principles
- Prefer primary sources.
- Distinguish evidence from inference.
- Distinguish security research from speculation.
- Cite standards accurately and check current status.
- Do not exaggerate ordinary ICS incidents into “digital twin attacks.”
- Identify uncertainty and scope.
- Record publication and review dates.
- Correct errors transparently.
- Treat vendor claims as claims unless independently substantiated.
- Focus on defensive security and useful engineering evidence.
Evidence labels
Widely accepted, directly supported by authoritative evidence, or a stable technical fact.
Backed by relevant sources or repeatable engineering reasoning, with scope or implementation dependence.
Plausible and increasingly discussed, but terminology, evidence, or practice is not settled.
A testable proposition offered for research rather than presented as fact.
An unresolved issue for which the lab does not claim a settled answer.
Classification discipline
A cyber-physical or ICS incident is not labeled a digital-twin compromise merely because a digital representation might have been relevant. Incident records must state the documented relationship and confidence.
Corrections and review
Substantial pages expose publication, review, author, evidence, and references. Revisions should correct the record directly and add a note when the change materially affects interpretation.
References
- NIST IR 8356: Security and Trust Considerations for Digital Twin TechnologyNIST · 2025 · Government research publication
Primary NIST treatment of digital-twin characteristics, cybersecurity, and trust considerations.
- NIST SP 800-160 Vol. 1 Rev. 1: Engineering Trustworthy Secure SystemsNIST · 2022 · Systems-security engineering guidance
Principles and life-cycle activities for engineering trustworthy secure systems.