Background We are migrating existing Lacework customers from our current
Lacework support portal (Zendesk) to the FortiCare support portal to
service all support requests for the Lacework FortiCNAPP product. This
migration doesn’t change how you acce...
Background We are migrating existing Lacework customers from our current
Lacework support portal (Zendesk) to the FortiCare support portal to
service all support requests for the Lacework FortiCNAPP product. We ask
all customers to start submitting s...
Description This article describes how to use FortiManager API.
FortiManager HTTPS API is JSON-RPC. Unlike the more famous REST API,
JSON-RPC does not pass any information in URL or HTTP Method.
Additionally, the Status code in the HTTP response does...
Description This article describes that in the context of an email
message delivery, 'relaying' refers to the operation when an email
message is being sent to a destination that is not 'local' (Gmail,
Yahoo, another company, etc.).By default, the For...
Hello Segla, First thing to say (putting aside the UDP filter for now)
is that if you want to list services that have TCP port either 443 or
80, you cannot use the filter you have, but you need to either use two
separate filters which are by default ...
Hi Eric, this is not the authoritative answer, but I tried to setup a
similar scenario and came to the conclusion that it is not possible -
broadcast and multicast are not supported in Azure, which means that
protocols like VRRP or FGCP cannot be use...
