User Acceptance Test (UAT)
User Acceptance Testing (UAT) is a pivotal phase in the deployment’s lifecycle, ensuring the product aligns with user needs and project objectives. In this high-level summary, we'll introduce the essential steps involved in conducting UAT for AppGate SDP. By following these steps, you can ensure that AppGate SDP is thoroughly tested and ready to meet your organization's needs.
Validate Project Objective
Begin by revisiting and validating the project's primary objective. Ensure the goals and expectations are clear and aligned with the desired outcomes of implementing AppGate SDP.
Review technical project design and planning to ensure alignment with defined objectives.
Have the technical objectives and project goals been documented accurately?
Are there any technical constraints or dependencies that may affect project objectives?
Validate the technical feasibility of the project objectives based on the current network architecture.
Do you know if the technical objectives align with the existing technical network infrastructure and security Policies?
Are there any technical considerations that need to be addressed, such as network segmentation or firewall rules?
Engage in technical discussions with stakeholders to clarify any ambiguities related to project objectives.
Are there any technical uncertainties or questions regarding the alignment of AppGate SDP with the defined objectives?
How do technical stakeholders perceive the expected technical benefits and impact on the network?
Example: A Success Criteria or objective was set during the implementation design.
Imagine your company wants to enhance network security while granting easy, secure access to remote employees. Your goal is to implement AppGate SDP to be able to achieve this balance.
Analyze Requirements
Thoroughly analyze the project requirements related to the implementation of AppGate SDP. Understand the specific needs and functionalities essential to achieving the project objective.
Translate technical requirements into specific access control policies and encryption configurations.
What are the technical details of access control requirements, including user roles and policies?
How are technical encryption and tunneling protocols defined to meet security requirements?
Assess the technical dependencies and integration points of AppGate SDP with existing systems.
Are there technical integrations with identity providers, such as Active Directory, LDAP, or SAML?
How do technical requirements impact the existing technical authentication and authorization mechanisms?
Example: Think of AppGate SDP as a tool to manage who accesses what in your company. You might need it to control access to sensitive servers like:
Customer information or financial records inside your main office.
Cloud services for office software.
Printers in remote branches
While validating these requisites, you could identify any missing user configuration.
Identify Test Scenarios
Identify and create test scenarios based on the analyzed requirements that encompass various user cases and functionalities. These scenarios will serve as the basis for testing the system.
Develop technical scenarios that encompass common use cases for AppGate SDP.
What technical scenarios are designed to validate access control, secure remote access, and network segmentation?
Do technical scenarios account for diverse user roles and access requirements?
Define technical data and user profiles specific to each scenario.
How is technical test data generated, including user accounts, permissions, and attributes?
Are technical data sets tailored to simulate various technical user roles and personas?
Recommended: Prepare technical environments that mirror the production network, including AppGate SDP components.
What technical configurations are applied to replicate the production network conditions in the test environment?
Have technical access control policies and routing configurations been mirrored for testing?
Example: Picture the scenarios employees working from -
Home needs secure access to confidential files stored on the company server.
While traveling, being connected from public networks within a specific region.
In these scenarios, you also need to identify who would be the test subject, to which the recombination would be a friendly user group that is willing to participate and is in the different places needed. To install the AppGate SDP Client, you can follow the steps in the admin guide:
Adjust for Test Execution
Modify and adjust the test scenarios as needed to ensure they align with the specific execution environment. Tailor the scenarios to suit the unique context in which the UAT will be conducted.
Customize technical scenarios to align with the roles and responsibilities of the testing team.
How are technical scenarios adjusted to reflect the daily activities and access requirements of the testing team?
Are there technical roles and permissions defined for testers within the scenarios?
Validate the technical feasibility of executing each scenario within the defined test environment.
Are there any technical limitations or technical barriers that may hinder the successful execution of scenarios?
How are technical dependencies and prerequisites managed for scenario execution?
Example: Customize the scenario to your team's reality. Perhaps the employee uses Mac computer instead of Windows, Mobile device and/or Personal devices not secured by the company IT team. You want to make sure AppGate SDP works seamlessly on all devices.
While working on the adjustments, you could define some missing Conditions; in case this needs to be set, you can follow the instructions in our admin guide here.
Analyze Data
Analyze the data collected during the test execution phase.
Evaluate the results, identify any discrepancies, and assess the
Example: Test the different scenarios by accessing the resources and considering the adjustment needed for each scenario.
Home needs secure access to confidential files stored on the company server.
Mac computer instead of Windows - Validate that the user can connect from its house network.
Mobile device - Validate that the user is connected from its house network.
Personal devices not secured by the company IT team - Should not be allowed under this Scenario.
While traveling, being connected from public networks within a specific region.
Mac computer instead of Windows - Validate from an external network, probably tethering from a mobile device or Wi-Fi from a coffee shop.
Mobile device - The user should be able to connect from the mobile device network and from a non-controlled environment like a coffee shop's Wi-Fi.
Personal devices not secured by the company IT team - Validate from an external network, probably tethering from a mobile device or Wi-Fi from a coffee shop.
Validate Result
Validate the test results against the predefined criteria and acceptance standards. Ensure that the product meets the expectations and is ready for a successful deployment of clients.
Example: Compare the results with what you expected. If AppGate SDP provided secure access to the server without any hiccups and limited access to the intended assets, it passed the test!
If the test doesn't work, please validate how the access was granted.
If the failed result happens the second or third time you run the test, and after the rules have been confirmed to be correctly configured, the advice is to validate any changes regarding the network.