This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
EDIM Needs Analysis Requirements Definition
EDIM Needs Analysis Requirements Definition

Version management

Difference between version and

At line 1 added 63 lines
!!!Business Requirements
* Current State: Business Process flows
* Future State Business Process flows
* Use Cases
!!!Determine the Existing IdM Infrastructure
* Identify, validate the client’s current infrastructure in detail
** What the "standard" operating system and version is implemented
* Identify the client’s current business process flows
* Understand how both the current infrastructure and business process will change with an IDM solution
* Identify and understand any policies currently in place that would need to be reflected in the future state (i.e.: user object naming policy, password creation policy)
* Identify and validate the current tree structure, number of user objects, etc.
* Attributes needed, at a minimum, to create and maintain user objects, as well as new attributes that would be required for downstream applications or new attributes that are being requested
!!!Determine Data Sources and Applications
* Identify the application type(s) and their infrastructure in detail
** [HR Applications|EIDM Check-list For HRSystem]
** [Active Directory|EIDM Check-list For Active Directory]
** Email
** [Password Considerations and Requirements]
** [Other Integrated Applications|EIDM Check-list for Other Integrated Applications]
* Identify the current business process flows
** How are new User's added
** How are users removed from Systems.
** When are they removed from Systems.
* Understand how both the current infrastructure and business process will change with an IdM solution
* Identify and understand any policies currently in place that would need to be reflected in the future state (i.e.: user object naming policy, password creation policy)
* Identify number and types of employees, non-employees, etc.
* Attributes available for consumption
* Attributes needed for consumption
!!!High Availability and Disaster Recovery Requirements
* What is the expected Availability of the IdM Architecture?
* What is the expected Disaster Recovery Requirements of the IdM Architecture?
!!!Security Requirements
Usually there are often pre-existing security requirements that the IdM Architecture will is expected to be compliant. Some often identified requirements are:
* [Password Considerations and Requirements]
* Data transport of Passwords (or other sensitive data)
* Location requirements of data repositories (Core DMZ etc)
!!!Auditing
Often there are auditing requirements within an organization that are required due to policy or compliance organizations.
* Policy Audit Requirements
* [Compliance Requirements|IDM Related Compliance Items]
* Identify Compliance Standards or Organizations
!!!System Reporting or Monitoring Systems
Organizations may have centralized Reporting or Monitoring Systems implementations that the IdM Architecture may need to integrate.
* Identity Any Reporting or Monitoring Systems
!!! Hardware Requirements
As the project moves forward and hardware requirements are determined the hardware procurement time should be considered and evaluated against the projected time-line for the project.
!!! Software Requirements
As the project moves forward and hardware requirements are determined the software procurement time should be considered and evaluated against the projected time-line for the project.
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop