Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.

Encryption Design Deliverable Template

From MIKE2.0 Methodology

Jump to: navigation, search
Under review.png
This article is a stub. It is currently undergoing major changes as it is in the very early stages of development and is only a placeholder. Please help improve MIKE2.0 by adding to this article.
This deliverable template is used to describe a sample of the MIKE2.0 Methodology (typically at a task level). More templates are now being added to MIKE2.0 as this has been a frequently requested aspect of the methodology. Contributors are strongly encouraged to assist in this effort.
Deliverable templates are illustrative as opposed to fully representative. Please help add examples to this template that are representative of the proposed output.

Cryptographic control processes go across each of the above tasks. Cryptographic design involves putting additional controls in place so that only appropriate users are able to read information, even if a non-authenticated user is able to access it. Cryptography may take place during access management stages by encrypting data that goes across the network. Encryption is also often applied within an information store so that even an administrator cannot see the data, such as password, credit card details or classified government content.

The design process defines the most appropriate encryption technique and technologies to be used. It also defines the approach for how it will be applied specifically to the information in scope.


Example 1 - Encryption Design

Wiki Contributors
Collapse Expand Close