GYTPOL POC Journey: Requirements and Initial Steps

Owned by Yury Kissin
Last updated: Oct 01, 2024 by Mark Zuk
4 min read

POC Process 

Initial Meeting (45 minutes) – POC Kickoff: In this session, we'll initiate the Proof of Concept by deploying GYTPOL to a subset of the designated devices. We'll offer a hands-on demonstration of the deployment process. Following this, your team will take over to extend the GYTPOL deployment to the remaining devices within the specified scope, covering up to 50 devices, with a preference for privileged users and critical servers.

Follow-up Meeting (30 to 45 minutes) – Mid-Evaluation Sync: We will convene to assess the data generated by GYTPOL. One of the advantages of GYTPOL is its rapid results, often available within the hour of deployment. This meeting aims to contextualize the findings and provide recommendations on best practices. Emphasis will be placed on identifying quick wins, initiating remediation efforts that guarantee minimal impact. The primary goal is to leverage GYTPOL to swiftly address vulnerabilities and enhance overall security.

Final Meeting (45 minutes to 1 hour) – End of Evaluation Review: Similar to the previous session, we will conduct a comprehensive review of all gathered data, implemented remediations, and address any questions or concerns you may have. This meeting serves as a platform for finalizing the evaluation phase, ensuring a thorough understanding of GYTPOL's impact and addressing any outstanding queries.

POC Pre-Reqs 

At GYTPOL, we provide two POC options: a Software as a Service (SaaS) deployed in the cloud and an on-premises installation. To determine the most suitable approach for your needs, we recommend consulting with a GYTPOL representative.

For those interested in the SaaS option, the process is straightforward, and a detailed information on requirements and installation process, can be found in the GYTPOL SaaS on-boarding document. Feel free to review this document and reach out to our representative for further assistance in selecting the POC approach that aligns best with your requirements.

To initiate the on-premises POC for GYTPOL, follow the steps to prepare a Windows Server/VM, according to specifications outlined in the System Requirements for On-Premises Deployment of GYTPOL document. This process includes additional configurations beyond a standard Windows Server installation:

  1. Review System Requirements: Refer to the document to understand the specific hardware and software specifications required for the on-premises deployment.

  2. Prepare Windows Server/VM: Set up a Windows Server or virtual machine adhering to the server sizing specifications outlined for up to 5,000 devices, as detailed in the document.

  • Ensure that all hardware and software prerequisites are met based on the sizing recommendations for optimal performance during the POC.

  • It's important to note that there is no requirement to install a SQL server for this POC, simplifying the setup process.

  1. Create a Domain User for GYTPOL: Establish a dedicated domain user account exclusively for GYTPOL. This user account will be utilized for secure integration and access management.

Please refer to the documentation and ensure that the created domain user is granted with the relevant permissions and group memberships as outlined. Follow the guidelines in the documentation to grant the necessary access rights to guarantee a smooth functioning of GYTPOL with the associated user account. This step is crucial for maintaining security and enabling GYTPOL to perform its functions seamlessly within the established environment.

  1. Create a DNS CNAME Entry: Generate a Canonical Name (CNAME) DNS entry to associate a domain alias with the GYTPOL server. This ensures seamless domain resolution and accessibility.

  2. Configure Firewall Ports: Open the designated firewall ports as specified in the documentation. These ports are essential for facilitating communication with GYTPOL. Follow the documented guidelines to configure the firewall settings accurately.

By meticulously adhering to these steps, you'll effectively prepare the Windows Server/VM for GYTPOL on-premises deployment, encompassing the additional requirements outlined in the system requirements documentation.

  1. Run Pre-Checker Tool: Refer to the same document for detailed instructions on how to execute the pre-checker tool. This tool is crucial for verifying that the server has been set up correctly in accordance with our provided instructions.

    • After running the pre-checker tool, carefully review the results to identify any issues or discrepancies. Address and rectify any necessary configurations based on the tool's output.

    • Click on the "Export results" option within the pre-checker tool and promptly email the generated output to your GYTPOL representative. This information is essential for our team to assess the setup and send you the required packages in preparation for the kickoff meeting and installation.

    • Once we receive the pre-checker tool results, we will provide you with the necessary packages to download, ensuring a streamlined process for our upcoming kickoff meeting and installation.

Install MSI & POC Kickoff Meeting

Upon successful completion of the preceding steps, our team will dispatch the requisite packages for installation on your designated machines.

The Sensor installation process can be carried out through various methods, detailed instructions can be found in the UI2 - Sensor Deployment and Management Guide guide. Ensure that you follow the guidelines precisely to guarantee a smooth and effective installation.

To facilitate this process, we will organize a kickoff meeting where our team will actively assist you in navigating through the installation steps. This collaborative session is designed to address any queries, provide real-time support, and ensure a seamless deployment of GYTPOL on your targeted machines.

Be prepared to engage in the kickoff meeting, as it serves as a valuable opportunity to enhance your understanding of the installation process and address any specific requirements or concerns that may arise during the deployment.