docmain.css" /> In this scenario - Evaluating Host Access Management and Security Server

2.1 In this scenario

A desktop administrator is tasked with setting up and using Management and Security Server to meet specific company requirements.

This scenario demonstrates the “before” and “after” effect of using Management and Security Server 12.6 to secure users’ access to the company’s mainframe applications.

2.1.1 Company requirements

  • The administrator can centrally manage the deployment of Micro Focus terminal emulation products to 1000 user workstations (in production).

    For this evaluation, the administrator will deploy to one user.

  • Only authorized users are allowed to access the mainframe applications.

  • All sessions are connected over a secure protocol.

  • Applications are locked down (hardened) to ensure company security mandates are enforced.

  • PCI compliance policies are enforced.

  • Implementing centralized management and security does not disrupt the end-user experience.

2.1.2 To meet these requirements

You will install Management and Security Server 12.6 and Reflection Desktop 16.2 on the same Windows workstation, provided you have both an administrator logon and a user logon.

(This approach is ok for testing, not for production.)

Then you will use Management and Security Server to:

  • assign sessions to only authorized users.

  • configure secure connections to host applications.

  • restrict users’ access to application settings.

See the Configuration Overview for a high-level view of the tasks.

2.1.3 Our assumptions

  • The company uses Reflection Desktop version 16.2.

  • The company uses a Windows 64-bit system environment with LDAP directory services. Users authenticate to the Windows domain.

  • The “domain user” in this scenario represents the end user.

  • The end users are accustomed to logging on before accessing their mainframe sessions.

Related topics: