Authentication (Process - IAM)

Manage MFA

1.0

IAM

• Improved User Experience Information Security Resilience (IAM Goal)

  Status
  colour Green title +++

• Costs Efficiency Compliance Assurance (IAM Goal)

  Status
  colour Green title ++

• Information Security Resilience Establish Trust between Parties (IAM Goal)

  Status
  colour Green title ++

• Productivity Gains Optimal Risk (IAM Goal)

  Status
  colour Green title ++

Streamline the authentication process by enabling reuse of authentication results across multiple systems thus enhancing user experience, reducing efforts from relying parties and strengthening security …

• Organization policies

• IT Systems

• IT Change Management

• IT Project Management

• Design MFA

• Deploy MFA

• Maintain MFA

• Optimize MFA

IT Systems that reuse centralized or federated authenticationrequire MFA

• MFA Deployment Level

• MFA Deployment Ratio

At the level of an organization entity, program or project, the process scope may be defined using the scope dimensions listed below. But at the organization level, the scope must be embraced holistically to effectively manage revocation risks and consider all of these scope dimensions .

• User populations: permanent employees, contractors, partners, customers, consumers, authorities

• Identity categories: humans, robots, processes

• Principal categories: user accounts, technical accounts, service accounts

• Access type: logical, physical (/wiki/spaces/QUOT/pages/67568001)

• IT Systems (business applications, infrastructure, …)

• Organizational scope (region, division, unit, …)

• The deployment of SSO reinforces security, even though it may marginally increase risk in certain circumstances, e.g. when an identity is compromised (/wiki/spaces/QUOT/pages/76021898). This risk is typically offset by the concomitant implementation of MFA.Sloppily implemented SSO may weaken security.