0002061: Security for XML documents

ID	Project	Category	View Status	Date Submitted	Last Update

0002061	10000-006: Mappings	Spec	public	2012-05-30 08:59	2023-06-21 14:49

Reporter	Wolfgang Mahnke	Assigned To	Randy Armstrong
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	no change required

Summary	0002061: Security for XML documents
Description	As we added a standard XML format for information modelling it might be interesting to have a mechanism to secure the content of the XML document. That can for example make sure that an export from a server was not modified by someone else. The IEC starts working on this issue in a different domain. Power systems management and associated information exchange – Data and communications security – Part 11: Security for XML Files (future IEC 62351-11) We should investigate the results and apply or adapt to our environment or create something else (if needed).
Tags	No tags attached.

Commit Version
Fix Due Date

Jim Luth 2013-09-10 17:00 administrator ~0004984	Maybe use "XML Signature"

Jim Luth 2015-10-09 08:20 administrator ~0006330	Wolfgang will look into the status of the IEC work.

Jim Luth 2016-03-08 17:30 administrator ~0006782	IEC work still not released.

Jim Luth 2022-07-19 16:33 administrator ~0017157	We should do this the way AutomationML does by using Open Packaging Conventions.

Randy Armstrong 2022-12-20 07:16 administrator ~0018328	This issue has been addressed as part of FLC and does not need updates to Part 6.

Wolfgang Mahnke 2022-12-21 16:30 developer ~0018333	This is a very old requirement, and not solving it would be OK for me. But I am not 100% sure what the reference to FLC is supposed to be. Are you talking about the offline engineering? We could use the same solution, but as far as I know FLC offline engineering uses AutomationML, not a UaNodeSet. So that is no solution to have a signed UaNodeSet in a cloud library, etc. (although we might just use the same solution having a signed zip file). In general, the solution should work without applying FX offline engineering.

Randy Armstrong 2023-06-20 11:50 administrator ~0019553	No longer needed.

Jim Luth 2023-06-21 14:49 administrator ~0019597	Agreed to no fix in Virtual F2F.

Date Modified	Username	Field	Change
2012-05-30 08:59	Wolfgang Mahnke	New Issue
2012-07-17 17:40	Jim Luth	Status	new => acknowledged
2013-09-10 17:00	Jim Luth	Note Added: 0004984
2015-10-09 08:20	Jim Luth	Note Added: 0006330
2016-03-08 17:30	Jim Luth	Note Added: 0006782
2022-07-19 16:33	Jim Luth	Note Added: 0017157
2022-07-19 16:35	Jim Luth	Project	Feature Requests => 10000-006: Mappings
2022-07-19 16:35	Jim Luth	Category	(No Category) => Api Change
2022-07-19 16:36	Jim Luth	Assigned To	=> Randy Armstrong
2022-07-19 16:36	Jim Luth	Status	acknowledged => assigned
2022-07-19 16:36	Jim Luth	Category	Api Change => Spec
2022-07-19 16:36	Jim Luth	Target Version	=> 1.05.03 RC1
2022-12-20 07:16	Randy Armstrong	Status	assigned => resolved
2022-12-20 07:16	Randy Armstrong	Resolution	open => no change required
2022-12-20 07:16	Randy Armstrong	Note Added: 0018328
2022-12-21 16:30	Wolfgang Mahnke	Status	resolved => feedback
2022-12-21 16:30	Wolfgang Mahnke	Resolution	no change required => reopened
2022-12-21 16:30	Wolfgang Mahnke	Note Added: 0018333
2023-06-06 18:07	Jim Luth	Target Version	1.05.03 RC1 => ?.??
2023-06-06 18:08	Jim Luth	Target Version	?.?? =>
2023-06-20 11:50	Randy Armstrong	Status	feedback => resolved
2023-06-20 11:50	Randy Armstrong	Resolution	reopened => no change required
2023-06-20 11:50	Randy Armstrong	Note Added: 0019553
2023-06-21 14:49	Jim Luth	Status	resolved => closed
2023-06-21 14:49	Jim Luth	Note Added: 0019597