From MIKE2.0 Methodology
|
| 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.
|
Identity and Access Management ensures that the user accessing the system is who they claim to be, thereby protecting systems from incorrect usage. It also protects users by informing them through:
- Stating how their personal information will be used
- Only using user information in the fashion that is stated
- By protecting user information from dissemination to other entities without stated permission
Authentication is generally the key design feature from a technical perspective. It may involve use of simple password logins or more advanced forms of authentication such as the use of security tokens or biometrics so it goes across network, host, application and data security. The authentication design may involve single-sign on across a federated systems environment.
Examples
Example 1 - Identity and Access Management Design
