Luminate Secure Access Cloud (TM) is a Software-as-a-Service platform for providing secure and managed access to corporate applications and services for corporate employees. Performing an effective proof-of-concept is an easy process that doesn't require any changes in the organization's IT infrastructure, can be kicked-off in a matter of minutes and can deliver substantial value to its user from its first day.
As an organization, Luminate puts the value of our solution for our customers and customer satisfaction as topmost priorities. To deliver on that promise, we have designed an effective proof-of-concept process template that is allowing the organization to try the functionality of our solution in real-life environment, without overhead and complexities, while seeing the real benefit of the solution, before purchasing the service.
The below diagram depicts the steps of the suggested process:
This is done at a call or a frontal meeting with Luminate representatives. Based on our experience, best POC processes always have concrete goals, particularly in the following areas:
Applications / Resources that will be accessed and their location - what corporate services will be accessed during the POC. What types of "resources" - web applications, SSH servers, RDP servers, REST/SOAP API servers, etc.... For each resource, it is important to define its location (corporate datacenter, hosting/co-location, Infrastructure-as-a-Service, ...)
Users that will be accessing the above resources - what groups of users will be accessing the above "resources" during the duration of the POC. It is important to consider how these users will be authenticated (connection to a corporate IdP as an option, Multi-Factor Authentication as an option) and whether an SSO functionality (into corporate applications) is expected
Explicit definition of additional critical success factors - depending on the specific requirements of every organization, additional critical requirements should be discussed and defined on this stage. Below list contains some suggestions:
End-user satisfaction with the access experience
End-user satisfaction with the speed of access to the resources
Administrator satisfaction with the on-boarding experience
Administrator satisfaction with product functionality
Security owners satisfaction with the security value of the product
This is done at the same day as the goals definition discussion (could be done in parallel or even before the discussion). This stage includes defining a "Luminate tenant" for the organization performing the POC, and setting it up for the organizational use. Following steps are usually performed:
Defining a tenant - definition of a tenant for a POC consists of a tenant name (will affect the URLs structure - https://<tenant_name>.luminatesec.com) and the region. In POCs, the testing of the system is performed in a certain region, such as US-WEST, EU-WEST, etc...
Defining administrator users - once a tenant is available, the first administrator can log in and create administrative accounts for other relevant users. The relevant information is to have email addresses for the relevant administrators
Connecting to Identity Provider - an optional step that allows the organization to connect its Luminate tenant to an organizational IdP (Active Directory, Azure Active Directory, Okta, OneLogin, Google Apps, ...) in order to allow organizational users to use Luminate services. In order to perform this step the organization performing the POC will need to involve an administrator of its Identity Provider / IAM solution.
This step can begin on the same day as the environment set-up. Luminate representatives will provide either a step-by-step guide for on-boarding or will do first steps on a webcast session with the representatives of the organization performing the POC. Activities that are usually performed during this stage are:
Deploying Luminate connectors - the organization performing the POC should deploy Luminate connectors in the datacenter locations hosting the corporate applications and services that are being accessed via Luminate Secure Access Cloud (TM) during the POC. Luminate connectors can be deployed on Linux or Windows Servers located in the customer environment, or on Container Management services provided by Infrastructure-as-a-Service vendors. As a pre-condition to this stage, the organization should define where and how the connectors will be deployed.
Configuring applications / services for access - during this step the administrator should configure corporate applications or services for access via Luminate Secure Access Cloud (TM)
Based on our experience, the period for trying out the system shouldn't be too brief, but also should not be too long. 3 weeks duration allows various corporate role-players to access their applications from various locations and devices, making sure that the experience is satisfactory.
During this period of time the Luminate team will have weekly check-up calls to make sure that the organization has everything that it requires in order to assess the Luminate solution properly. Naturally, our team will be available to provide all the required assistance throughout the whole period of evaluation.
Summary and Closure
After completing the 3 weeks of evaluation, Luminate team will set up a summary and closure call with the organization performing the proof of concept. During this meeting we usually analyze the success criteria that were set early in the process and decide on the next steps.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe