--- title: "pGTI integration with Intelligent Virtual Execution - Server" slug: "pgti-integration-with-intelligent-virtual-execution-server-1" tags: ["Product Usage", "FX 10.x", "AX 10.x", "NX 10.x", "Network Security"] updated: 2026-08-24T20:40:08Z published: 2026-08-24T20:40:08Z canonical: "docs.trellix.com/pgti-integration-with-intelligent-virtual-execution-server-1" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # pGTI integration with Intelligent Virtual Execution - Server Private Global Threat Intelligence (pGTI) is a private cloud server utilized by Trellix security platforms. It stores URL and file reputation data for submissions made by these platforms. The reputation score is derived from the analysis conducted by Trellix appliances. pGTI communicates using REST APIs and uses certificates and private key for authentication. Integrating pGTI with IVX allows to: - Fetch verdicts for URL and file submissions from the pGTI server. - Use the the private GTI database to validate submissions. You must have Trellix certificates installed on all Intelligent Virtual Execution - Server nodes. Contact [Support](https://supportm.trellix.com/webcenter/portal/supportportal/pages_home) for more information. **Before you begin:** - **Upload certificates** - The root certificate, private key, and CA chain certificates must be uploaded. Certificate access is restricted for Administrator users only and is disabled for Operator users. 1. CA Chain certificates: - Upload the CA Chain certificates to the appliances using the following CLI: ``` crypto certificate name public-cert pem ``` 2. pGTI server certificates - upload the pGTI server certificates to the appliances using the following CLIs: ``` crypto certificate name public-cert pem crypto certificate name private-key pem ``` You must ensure that the PEM string is correctly formatted as listed below: - Double quotation marks and a new line - Begin delimiter string and a new line - ASCII block and new line - End delimiter string and a new line - Double quotation (" ") **To enable the pGTI service:** 1. Go to CLI configuration mode. ``` hostname > enable hostname # configure terminal ``` 2. Store the URL address of the pGTI server using ``` mvx analysis pgti baseurl ``` 3. Generate API key for communicating with the PGTI server using the API ``` mvx analysis pgti apikey certificate ca-list ``` This command validates the certificates, then generates and stores the API key and certificate name in the configuration. > [!NOTE] > Note > > Upon generation, the API Key will always be in a **PENDING** state. You must send this API key to the PGTI team for approval. 4. Enable the IVX integration with the pGTI server using ``` mvx analysis pgti enable ``` > [!NOTE] > Note > > pGTI configuration is allowed only when the VX node is part of a cluster. If the node is detached from the cluster, the pGTI configuration will be automatically removed from that node. If the entire cluster is deleted, the pGTI configuration will also be removed. You must reconfigure pGTI when re-creating the cluster. 5. Verify the configuration status using ``` show mvx analysis pgti ``` **To disable the pGTI service:** 1. Go to CLI configuration mode. ``` hostname > enable hostname # configure terminal ``` 2. Disable the integration using ``` no mvx analysis pgti enable ``` 3. Verify the configuration status using ``` show mvx analysis pgti ``` Other CLIs used are: - Delete the URL address of the pGTI server using ``` no mvx analysis pgti base url ``` - Delete the pGTI API key using ``` no mvx analysis pgti apikey ```