Difference between revisions of "Integrity (MU3)"

Revision as of 06:20, 24 September 2020

To complete this, need to ensure CCDA imports are brought in via the standard documents mechanism (now I think they are not), so then get hashed like other documents/imports.

All message digest hashing is using sha3-516 (able to use sha3 because of this: https://csrc.nist.gov/publications/detail/fips/180/4/final ).
Message digest of imported documents/records are created via sha3-516 to ensure integrity of records (note in above status that CCDA import may be bypassing this, which will research).

@@ Line 1: / Line 1: @@
-. All message digest hashing is using sha3-516 (able to use sha3 because of this: https://csrc.nist.gov/publications/detail/fips/180/4/final ).
+==Status==
-. Message digest of imported documents/records are created via sha3-516 to ensure integrity of records.
+:*To complete this, need to ensure CCDA imports are brought in via the standard documents mechanism (now I think they are not), so then get hashed like other documents/imports.
+==Notes==
+:*All message digest hashing is using sha3-516 (able to use sha3 because of this: https://csrc.nist.gov/publications/detail/fips/180/4/final ).
+:*Message digest of imported documents/records are created via sha3-516 to ensure integrity of records (note in above status that CCDA import may be bypassing this, which will research).