Re: Backup issue after upgrade to 7.0.14

vschmitt_FTNT · 04-04-2025

Description This article describes why the Subscription Usage for vCPU may appear empty when using Lacework Organizations. Scope Lacework, FortiCNAPP, Organization, vCPU, Subscription Usage. Solution The three subscription packages Lacework FortiCNAP...

vschmitt_FTNT · 04-02-2025

Description This article explains why newly created compliance policies sometimes do not appear under the compliance folder. Scope FortiCNAPP, Lacework, Compliance policy, Framework. Solution Every custom policy is invisible to Compliance UI until it...

vschmitt_FTNT · 03-07-2025

Description This article describes how to troubleshoot the Recorded Future health check failing with an Invalid endpoint or credentials. Scope Recorded Future v2.0.0. Solution The Recorded Future health check will trigger the API endpoint 'https://ap...

vschmitt_FTNT · 03-06-2025

Description This article describes how to investigate and remediate the error 'Datasource cannot be used by compliance policy'.During the creation of a custom compliance policy, the administrator needs to define the datasource that will serve as a so...

vschmitt_FTNT · 03-06-2025

Description When checking the overall risk of an IAM account under the CIEM dossier, the overall risk is sometime not the highest risk of its component.This article will explain why and in which case this overall risk is calculated to be higher. Scop...

vschmitt_FTNT · 02-29-2024

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...

vschmitt_FTNT · 11-29-2022

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, ...

vschmitt_FTNT · 11-28-2022

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...

User Statistics

User Activity

Troubleshooting Tip: Why the vCPU usage is not populated in subscription usage of the Lacework FortiCNAPP account

Troubleshooting Tip: Newly created compliance policies do not appear under the compliance folder

Troubleshooting Tip: Recorded Future health check failing on Invalid endpoint or credentials

Troubleshooting Tip: Fix the 'Datasource cannot be used by compliance policy' error when creating custom policies

Technical Tip: Overall risk in the CIEM folder can display higher risk score than the highest risk score of its elements