AWS healthimaging documentation change
Summary
Added details about video codec validation and IFRC checksum verification for video data integrity
Security assessment
The changes enhance documentation about data integrity verification mechanisms (CRC32 checksums) and codec validation. While this relates to data integrity assurance, there's no indication of addressing a specific security vulnerability. The updates provide better documentation of existing security controls for data validation.
Diff
diff --git a/healthimaging/latest/devguide/pixel-data-verification.md b/healthimaging/latest/devguide/pixel-data-verification.md index 9f2f45abe..cfecc7382 100644 --- a//healthimaging/latest/devguide/pixel-data-verification.md +++ b//healthimaging/latest/devguide/pixel-data-verification.md @@ -59 +59,5 @@ For images stored in HTJ2K Lossless with RPCL, the `FrameSizeInBytes` indicates - 4. To verify pixel data, access the [ Pixel data verification](https://github.com/aws-samples/aws-healthimaging-samples/tree/main/pixel-data-verification) procedure on GitHub and follow the instructions in the`README.md` file to independently verify lossless image processing by the various [HTJ2K decoding libraries](./reference-htj2k.html) that are utilized by HealthImaging. After the full image is loaded, you can compute the IFRC for raw input data on your end and compare it with the IFRC value provided in the HealthImaging metadata to verify the pixel data. + 4. For instances containing video, HealthImaging performs a lightweight codec validation that verifies the transfer syntax specified in the DICOM metadata matches the video codec. + +HealthImaging computes an IFRC checksum value on the original video object using the CRC32 algorithm. The IFRC checksum value is recorded to the `job-output-manifest.json`, and persisted in the HealthImaging metadata. As with images stored in their original transfer syntax (described above), the `MinPixelValue` and `MaxPixelValue` will not be available. The FrameSizeInBytes indicates the size of the original frame. + + 5. HealthImaging verify pixel data, access the [ Pixel data verification](https://github.com/aws-samples/aws-healthimaging-samples/tree/main/pixel-data-verification) procedure on GitHub and follow the instructions in the`README.md` file to independently verify lossless image processing by the various [HTJ2K decoding libraries](./reference-htj2k.html) that are utilized by HealthImaging. After the full image is loaded, you can compute the IFRC for raw input data on your end and compare it with the IFRC value provided in the HealthImaging metadata to verify the pixel data.