1 / 19

Security Model Working Group

Security Model Working Group. TACDFIPSFKMI - WG 2 October 15, 1997. Primary Security Components. General System Requirements End User Product Requirements Key Recovery Agent Security Registration Agent Security APKS Security. General System. General Requirements Confidentiality

harmon
Download Presentation

Security Model Working Group

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. Security Model Working Group TACDFIPSFKMI - WG 2 October 15, 1997

  2. Primary Security Components • General System Requirements • End User Product Requirements • Key Recovery Agent Security • Registration Agent Security • APKS Security

  3. General System General Requirements • Confidentiality Keys should not be disclosed unduly. • Policy It must be possible to decide if, when, where, and how escrowing is to be done. • Strength Key recovery should not weaken the system.

  4. General System Configurable Capability • Robustness There should be no single point of failure.

  5. General System Optional Capabilities • Non-disclosure of KRA Users may be able to hide the identities of their recovery agents. • Interoperability Policy validation is available.

  6. End User General Requirements • Confidentiality Keys should not be disclosed unduly. • Policy When system policy permits, users should have the ability to decide when, where, and how escrowing is to be done.

  7. End User Configurable Capability • Robustness There should be no single point of failure.

  8. End User Optional Capabilities • Non-disclosure of KRA Users may be able to hide the identities of their recovery agents. • Non-repudiation Receipts available for KRA communication. • Interoperability Policy validation is available.

  9. Key Recovery Agent General Requirements • Confidentiality Keys should not be disclosed unduly. • Policy It must be possible to decide if, when, where, and how escrowing is to be done.

  10. Key Recovery Agent Configurable Capabilities • Robustness There should be no single point of failure. • Confidentiality Users should neither view their own keys nor know of recoveries by certain requestors. • Integrity Integrity of recovered data should be proven.

  11. Key Recovery Agent Configurable Capabilities (continued) • Authentication Authentication of requestors is required. • Non-repudiation Receipts available for all communication. • Auditing All significant events can be audited.

  12. Key Recovery Agent Optional Capabilities • Granularity Requestors may have different capabilities. • Non-disclosure of users KRAs may be able to hide the identities of their subscribers. • Non-reputation Receipts available for KRA communication.

  13. Registration Agent General Requirements • Integrity Integrity of vendor-specific information should be provable. • Non-repudiation Receipts should be available for communications with this agent.

  14. Authentic PK Source General Requirements • Confidentiality Keys should not be disclosed unduly. • Policy It must be possible to decide if, when, where, and how an APKS key is to be used.

  15. Authentic PK Source Configurable Capabilities • Robustness There should be no single point of failure. • Confidentiality Users should neither view their own keys nor know of recoveries by certain requestors. • Integrity Integrity of recovered data should be proven.

  16. Authentic PK Source Configurable Capabilities (continued) • Authentication Authentication for access is required. • Auditing All significant events can be audited.

  17. Authentic PK Source Optional Capability • Granularity A single authentic public key source may support multiple capabilities for different cryptographic key recovery systems.

  18. Licensing Agent General Requirement • Non-repudiation Receipts should be available for communications with this agent.

  19. Reserve Clause In no case shall any of the requirements enumerated in this section be construed as limiting the policy options delineated in section 1.4 of this document.

More Related