1 / 5

Document Encryption Profile

This document evaluates the considerations for the Document Encryption profile, focusing on actor and dynamic behavior requirements, algorithm support, encryption and decryption process responsibilities, key management, and other aspects seen in related profiles. The evaluation includes criteria such as functional soundness, encryption functionality, key management hooks, crypto algorithm support, maturity and availability, standard openness, efficiency, architectural fit, consistency with other IHE profiles, embedding with XD*, generic payload, and well-defined package. Work in progress.

thenry
Download Presentation

Document Encryption Profile

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Document Encryption Profile Considerations for the February meeting Paul Koster, Martin Rosner January, 2011

  2. Profile type

  3. Benefits of transaction profile over content profile • Actor and dynamic behavior requirements • Algorithm support (e.g. design for future backwards compatibility) • Encryption and decryption process and responsibilities (e.g. ensure proper and secure handling) • Key management (e.g. like password derivation requirements in PDI) • Above aspects are also seen in e.g. PDI, ATNA and XUA

  4. Base technologies • Criteria • Functional soundness • Encryption functionality • Key management hooks • Crypto algorithm support • … • Maturity and availability • Standard (openness) • Efficiency • Architectural fit • Consistency with other IHE profiles • Embedding with XD* • Generic payload (no bias for document type) • Well-defined package • …

  5. Base Technologies evaluation X X (work in progress)

More Related