Intigua 3.7 is installed within the customer’s organizational network, and is accessed via a web interface. Intigua 3.7 is available either as RPMs to be installed on CentOS or RHEL, or as a virtual appliance running on CentOS (compatible with Red Hat Enterprise Linux). The virtual appliance can be patched like any other such Linux, and can be protected with standard management tools.
The Intigua server uses an external PostgreSQL database, which can be clustered. A high-availability solution for the Intigua server itself is also available.
Intigua 3.7 connects directly to VMware vSphere, AWS EC2, and MS Azure environments for endpoint discovery.
Upon initial deployment to each endpoint, Intigua 3.7 establishes a channel to the endpoint by deploying the Intigua connector client service via SMB (Windows) or SSH (Linux).
For ongoing agent provisioning, registration, control, and monitoring, Intigua 3.7 communicates with endpoints and management servers via HTTPS sessions from the endpoints to Intigua 3.7; If HTTPS communications are unavailable, Intigua 3.7 falls back to using SMB or SSH for these ongoing operations as well. In accordance with commands from Intigua 3.7, the connector on endpoints runs, stops, and monitors managed agents, and the connector on third-party management servers performs per-endpoint registration and configuration tasks.
When preferred protocols are unavailable, Intigua 3.7 can communicate with vCenter VMs via the hypervisor channel (supported for vSphere 5.1 and above). In that case, for ongoing communications Intigua 3.7 continues to periodically try HTTPS at gradually increasing intervals up to a maximum interval of 24 hours. This default behavior is configurable.