Prerequisites
There are five requirements for registering a SIP instance with Insights: two version checks, a firewall rule, a license, and an email address on every account that will register or sign in.
| Requirement | Detail |
|---|---|
| SIP version | 2024.5 or later. |
| Insights plugin version | 2024.5.7 or later. |
| Outbound HTTPS | Your SIP application server must reach two FireMon hostnames on TCP 443. See below. |
| A licensed customer account | A dedicated customer account with a valid license in FireMon User Center. An evaluation license works. |
| An email address on every user | The SIP user who registers, and every user who signs in to Insights afterwards, needs a valid email address on their SIP account. Insights builds each account from the address SIP sends, so a user without one can't be created. |
Network access
Your SIP installation makes both connections outbound, and both are required. Neither needs an inbound rule, because Insights never opens a connection to your network. The plugin connects out and holds that connection open, and everything the cloud asks for travels back down it.
| Hostname | Port | What it carries |
|---|---|---|
insights.prod.firemon.cloud | TCP 443 | Registration, and the plugin's other calls to the Insights API — renewing its credentials, syncing your SIP users, and handing a user over when they open Insights from the module menu |
ws.insights.prod.firemon.cloud | TCP 443 | The persistent connection the plugin holds open. The daily metric collection and every AI feature run over it, with Insights querying your SIP through the channel rather than your SIP pushing data out |
Open both before you register. Registration itself only needs the first hostname, so allowing one and not the other leaves you with an installation that registers successfully and then stays empty.
If your rules allow hostnames rather than addresses, check they name ws.insights.prod.firemon.cloud. The older ws.insights.firemon.cloud is deprecated, and a rule still written against it won't match. An outbound proxy in the path needs both hostnames too.
Admin users on systems without Policy Planner
Policy Planner is a separately licensed SIP add-on. On a system without one, an admin user who opens Administration > Settings > Security Manager is logged out immediately. This affects admin users signing in locally, and through SAML, LDAP and similar.
There are two ways around it. Run FMOS 2025.1.4 or 2025.2.2, or use the default firemon admin account created during installation to register and to sign in to Insights.