{"id":6831,"date":"2023-09-15T14:04:32","date_gmt":"2023-09-15T11:04:32","guid":{"rendered":"https:\/\/support.withsecure.com\/?post_type=announcement&p=6831"},"modified":"2026-10-19T13:06:37","modified_gmt":"2026-10-19T10:06:37","slug":"network-addresses-for-withsecure-on-premise-products","status":"publish","type":"announcement","link":"https:\/\/support.withsecure.com\/en\/announcements\/network-addresses-for-withsecure-on-premise-products\/","title":{"rendered":"Network addresses for WithSecure on-premise products"},"content":{"rendered":"

UPDATE 2026-01-12: <\/strong>The list of network addresses has been updated to reflect the current requirements<\/p>\n

UPDATE 2024-09-06: <\/strong>Added a note to highlight that product functionality can be affected if access to these network addresses is not allowed<\/p>\n

UPDATE 2024-01-25:<\/strong> Updated references to aspam.sp.f-secure.com<\/p>\n

For many customers, WithSecure products will function correctly without needing to know which servers the products connect to.<\/p>\n

However, some administrators tightly control which network addresses they allow their clients to connect to (\u201cEgress control\u201d or \u201coutbound connections\u201d), and it is mandatory<\/strong> that they allow connections to the following addresses. WithSecure cannot guarantee the functionality of the products if access to these addresses is blocked.<\/p>\n

The product may not function correctly if access to these network addresses is not allowed. <\/strong><\/p>\n

In addition, WithSecure Linux Security 64 and WithSecure Atlant can use an offline mode, which can help in isolated environments. Please note that this will limit some functionality. Please check the user guides for more information<\/p>\n

Please note that all the following require outbound connections to TCP\/443 unless otherwise stated.<\/p>\n

Additionally, any products listed in this document also includes F-Secure branded versions of the same products.<\/p>\n

Recommendations<\/strong><\/h2>\n

WithSecure recommends, where possible, that administrators allow outbound access to all address under the withsecure.com and fsapi.com domains. We do appreciate that this is not always possible due to firewall configuration limitations, or even from an operational perspective, so we are publishing an explicit list of server addresses.<\/p>\n

Please note that we do not guarantee<\/strong> this list of addresses is complete or will stay unchanged, so we strongly recommend bookmarking these articles for future reference. We will update these articles whenever needed.<\/p>\n

WithSecure Business Suite<\/strong><\/h2>\n

Business Suite includes:<\/p>\n

    \n
  • WithSecure Policy Manager (Windows & Linux)<\/li>\n
  • WithSecure Policy Manager Proxy (Windows & Linux)<\/li>\n
  • WithSecure Client Security (including Premium, Mac)<\/li>\n
  • WithSecure Server Security (including Premium)<\/li>\n
  • WithSecure Linux Security 64<\/li>\n<\/ul>\n

    For environments that only connect to the internet via the Policy Manager, it is enough to ensure that the Policy Manager (or Policy Manager Proxy) can reach these services.<\/p>\n

    Business Suite 16 onwards <\/h3>\n

    corp-reg.fsapi.com<\/strong><\/p>\n

      \n
    • This server is used by Policy Manager for license registration. Blocking this server will prevent license validation.<\/li>\n<\/ul>\n

      guts2.fsapi.com <\/strong>(also TCP\/80)<\/p>\n

        \n
      • This server is used to deliver updates for scanning engines and detection rules, and for some products updates to the software itself. Blocking this server will completely stop security updates.<\/li>\n<\/ul>\n

        a.karma.sc2.fsapi.com<\/strong><\/p>\n

        restmc.mind.sc2.fsapi.com<\/strong><\/p>\n

        mind-failover.sc2.fsapi.com<\/strong><\/p>\n

        api.doorman.fsapi.com<\/strong><\/p>\n

          \n
        • Backend services needed for Security Cloud functionality<\/li>\n<\/ul>\n

          api.prd.glb.us-prd.fsapi.com<\/strong><\/p>\n

            \n
          • Used to control updates for Linux Security 64<\/li>\n<\/ul>\n

            download.fsapi.com<\/strong><\/p>\n

              \n
            • Used for the hotfix update mechanism for Linux Security 64<\/li>\n<\/ul>\n

              WithSecure Email and Server Security<\/strong><\/h2>\n

              While WithSecure Email and Server Security is not part of Business Suite, the network addresses needed are the same as for Business Suite, with the addition of an extra address<\/p>\n

              ESS version 16 onwards<\/h3>\n

              aspam.fsapi.com<\/strong><\/p>\n

                \n
              • Used to check email content for Spam in the ESS product.<\/li>\n<\/ul>\n

                WithSecure Atlant<\/strong><\/h2>\n

                Versions 1.0.319 onwards<\/h3>\n

                guts2.fsapi.com <\/strong>(also TCP\/80)<\/p>\n

                  \n
                • This server is used to deliver updates for scanning engines and detection rules, and for some products updates to the software itself. Blocking this server will completely stop security updates.<\/li>\n<\/ul>\n

                  api.prd.glb.us-prd.fsapi.com<\/strong><\/p>\n

                    \n
                  • Used to control updates for WithSecure Atlant<\/li>\n<\/ul>\n

                    aspam.fsapi.com<\/strong><\/p>\n

                      \n
                    • Used to check email content for Spam in the Atlant product.<\/li>\n<\/ul>\n

                      a.karma.sc2.fsapi.com<\/strong><\/p>\n

                      restmc.mind.sc2.fsapi.com<\/strong><\/p>\n

                      mind-failover.sc2.fsapi.com<\/strong><\/p>\n

                      baseguard.doorman.fsapi.com<\/strong><\/p>\n

                        \n
                      • Backend services needed for Security Cloud functionality<\/li>\n<\/ul>\n

                        provisioning.ew1.entitlements.fsapi.com<\/strong><\/p>\n

                        api.disobus.fsapi.com<\/strong><\/p>\n

                          \n
                        • These services are only used when license key is used for Atlant. They are not required when a license file is used<\/li>\n<\/ul>\n

                          download.fsapi.com<\/strong><\/p>\n

                            \n
                          • Used for the hotfix update mechanism<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"

                            UPDATE 2026-01-12: The list of network addresses has been updated to reflect the current requirements UPDATE 2024-09-06: Added a note to highlight that product functionality can be affected if access…<\/p>\n","protected":false},"template":"","announcement_category":[143],"class_list":["post-6831","announcement","type-announcement","status-publish","hentry"],"acf":{"source_system":"vanilla-import","import_hash":"54db650eff2fe5bb3ed708b3d7da77c420a8baf1","vanilla_article_id":31208,"legacy_author":"AndyF_WS","vanilla_url":"https:\/\/community.withsecure.com\/announcements-en\/kb\/articles\/31208-network-addresses-for-withsecure-on-premise-products","vanilla_category_id":226,"machine_translated":false},"_links":{"self":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement\/6831","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement"}],"about":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/types\/announcement"}],"version-history":[{"count":1,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement\/6831\/revisions"}],"predecessor-version":[{"id":8200,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement\/6831\/revisions\/8200"}],"wp:attachment":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/media?parent=6831"}],"wp:term":[{"taxonomy":"announcement_category","embeddable":true,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement_category?post=6831"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}