Description This article describes how to fix the SSL
CERTIFICATE_VERIFY_FAILED error when configuring the Generic Log API
Poller (HTTPS Advanced). The Generic Log API Poller (HTTPS_Advanced)
Integration permits the FortiSIEM to poll any server using...
Description This article describes how to allow FortiSIEM in Azure Entra
ID to access mail statistics using OAUTH. The Office365 integration
allows FortiSIEM to fetch audit logs from Office365 and Exchange. After
following the steps outlined in the M...
Description This article describes the different API endpoints that can
lead to a failure in dynamic address update from the awsd process (Aws
sdn connector). Scope FortiGate, SDN Connector, AWS, IAM, STS. Solution
To see the actual error, it is nece...
Description This article describes how to query from the command line
the FortiSIEM API using curl or get. A simple query will be processed on
the FortiSIEM CMDB to get the monitored devices in an XML payload
format. FortiSIEM API uses basic authenti...
Description Remediation script on FortiSIEM for FortiMail provides a
remediation action on incident. This article describes the configuration
on FortiMail and in FortiSIEM. Scope FortiMail, FortiSIEM, Remediation.
Solution In FortiSIEM it is necessar...
Hi all,Starting from 7.0.13, the FortiOS enforces strong cryptographics.
Therefore you have collateral fine tuning on the 3rd party tools that
still uses weak crypto. You may refer to that documentation for the
changes :We have disabled strong cypher...
Dear Meng, Thank you for your answer. Yes you have to lock the adom,
make your changes and the commit the changes and then unlock the adom.
This must be done in the script so that you don't hit the error. Even if
you do not see it locked in the GUI, ...
Hello, This error code -10147 is usually when you are trying to add or
modify an object on locked adom, when using the Fortimanager in
workspace mode normal. I just did the test and it gives me same error,
when locking the root Adom by another admini...