Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Introduction

The goal of this document is to furnish instructions for the Software as a Service (SaaS) onboarding process, applicable to both new customers and existing customers migrating to GYTPOL's SaaS platform.

Preliminary steps and ongoing onboarding

  1. User Access:

    • The customer will furnish a list of email addresses for UI access.

  2. Identity Provider (IDP) Integration:

    • Customers can integrate GYTPOL with their existing IDP, such as OKTA, AzureAD, and more.

  3. Access Levels:

    • Specify required access levels, e.g., Full Admin, Read for Windows Servers, Write for Linux Debian, etc.

  4. Operating System Support:

    • Ensure the target operating system is supported; refer to the provided list.

  5. SaaS Tenant Creation:

    • Upon SaaS tenant creation, GYTPOL will supply a username (email address) and an initial password, which must be changed upon the first login.

  6. Firewall Whitelisting:

    • GYTPOL will share a list of FW rules (allowing only port 443 to SaaS URLs) for whitelisting in case of blocks.

  7. Client Downloads:

    • GYTPOL will provide links to clients per OS (Windows MSIs, Linux, and macOS packages).

    • Clients can also be downloaded directly from the GYTPOL UI.

  8. Active Directory / GPO Data and CIS/NIST Benchmarks:

    • For customers wishing to view Active Directory/GPO data and CIS/NIST benchmarks:

New Customers (PoC or Production)

Deployment and Device Scanning Process:

  1. dsRequester Server Setup:

    • If needed, set up the dsRequester server as per the provided requirements.

  2. Firewall Rules and dsRequester Server Ready:

    • Ensure all necessary FW rules are configured.

    • Confirm the readiness of the dsRequester server.

  3. GYTPOL Client Deployment:

    • Deploy the GYTPOL client on a group of devices, adhering to licensing limitations.

    • Use any deployment tool (SCCM, BigFix, GPO) for deploying the new client.

  4. Scanning and Data Submission:

    • After deployment, initiate device scans.

    • Data collected during scans is transmitted to GYTPOL.

  5. Metrics Display in UI:

    • View and analyze metrics in the GYTPOL UI.

  6. Full Functionality and Remediation:

    • The software offers full functionality, including remediation capabilities.

  7. Exercise Caution with Remediations:

    • Exercise caution when choosing devices for remediations.

    • It is advisable to test remediations on a small scale before implementing them on a larger group of devices.

This process ensures a systematic deployment, scanning, and evaluation of device metrics within the defined licensing constraints.

SaaS Proof of Concept (PoC) Details:

  • The PoC license encompasses:

    • Limitation to 50 devices.

    • Validity for 21 days.

    • Full functionality, inclusive of all modules: detection, remediation, and revert functionality.

  • Meeting Schedule During PoC:

    1. Onboarding Session:

      • Overview of initial findings.

      • UI overview.

    2. Status Call:

      • Advanced and technical discussions.

    3. PoC Summary Call:

      • Review of findings.

      • Presentation of results to stakeholders and decision-makers.

      • Discussion of next steps.

These meetings are essential for a comprehensive understanding and evaluation of GYTPOL's capabilities during the PoC period.

Existing On-Prem Customers, migrating to SaaS

Deployment of New Client and Transition to SaaS:

  1. New Client Deployment:

    • GYTPOL will provide an updated client (higher version).

    • The new client will automatically update the existing installation, recreate configuration files, and redirect data to GYTPOL SaaS.

  2. Deployment Methods:

    • Use any deployment tool (SCCM, BigFix, GPO) or leverage GYTPOL's Auto-Update mechanism for deploying the new client.

  3. Data Submission to GYTPOL SaaS:

    • After deployment, scanned device data is sent to GYTPOL SaaS instead of the local server.

  4. Metrics in UI:

    • View and analyze metrics in the GYTPOL SaaS UI.

  5. Dual Visibility:

    • The updated device will report to the new GYTPOL SaaS.

    • It will remain visible in the old server for an additional 14 days (if GYTPOL's auto-update is used).

  6. Important Note on Migration:

    • Data migration is not possible.

    • Remediation tasks, Mutes, Roles, and Permissions must be recreated in the new UI.

This process facilitates a smooth transition to the updated GYTPOL SaaS environment, ensuring continued visibility of devices during the transition period.

Client installation guide and supported platforms

For in-depth client guides, detailed how-to instructions, and a comprehensive support matrix, please refer to the following link: GYTPOL Client Installation Documentation.

This resource provides step-by-step guidance and essential information for installing and configuring GYTPOL clients on various operating systems. Explore the documentation to ensure a smooth and effective implementation of GYTPOL's solutions.

  • No labels