When accessing the FortiSASE portal for the first time, an administrator must select data center locations for the following FortiSASE components:
* Endpoint Management:
* The data center location for endpoint management ensures that endpoint data and policies are managed and stored within the chosen geographical region.
* Points of Presence (PoPs):
* Points of Presence (PoPs) are the locations where FortiSASE services are delivered to users.
Selecting PoP locations ensures optimal performance and connectivity for users based on their geographical distribution.
* Logging:
* The data center location for logging determines where log data is stored and managed. This is crucial for compliance and regulatory requirements, as well as for efficient log analysis and reporting.
References:
* FortiOS 7.2 Administration Guide: Details on initial setup and configuration steps for FortiSASE.
* FortiSASE 23.2 Documentation: Explains the importance of selecting data center locations for various FortiSASE components.

If the daily summary report generated by FortiSASE contains very little data, one possible explanation is that the "Log allowed traffic" setting is configured to log only "Security Events" for all policies. This configuration limits the amount of data logged, as it only includes security events and excludes normal allowed traffic.
* Log Allowed Traffic Setting:
* The "Log allowed traffic" setting determines which types of traffic are logged.
* When set to "Security Events," only traffic that triggers a security event (such as a threat detection or policy violation) is logged.
* Impact on Report Data:
* If the log setting excludes regular allowed traffic, the amount of data captured and reported is significantly reduced.
* This results in reports with minimal data, as only security-related events are included.
References:
* FortiOS 7.2 Administration Guide: Provides details on configuring logging settings for traffic policies.
* FortiSASE 23.2 Documentation: Explains the impact of logging configurations on report generation and data visibility.

For a customer looking to upgrade their legacy on-premises proxy to a cloud-based proxy for a hybrid network, the combination of Secure Web Gateway (SWG) and Inline Cloud Access Security Broker (CASB) features in FortiSASE will provide the necessary capabilities.
* Secure Web Gateway (SWG):
* SWG provides comprehensive web security by inspecting and filtering web traffic to protect against web-based threats.
* It ensures that all web traffic, whether originating from on-premises or remote locations, is inspected and secured by the cloud-based proxy.
* Inline Cloud Access Security Broker (CASB):
* CASB enhances security by providing visibility and control over cloud applications and services.
* Inline CASB integrates with SWG to enforce security policies for cloud application usage, preventing unauthorized access and data leakage.
References:
* FortiOS 7.2 Administration Guide: Details on SWG and CASB features.
* FortiSASE 23.2 Documentation: Explains how SWG and inline-CASB are used in cloud-based proxy solutions.

To configure a Secure Private Access (SPA) solution to share endpoint information between FortiSASE and a corporate FortiGate, you need to take the following steps:
* Add the FortiGate IP address in the secure private access configuration on FortiSASE:
* This step allows FortiSASE to recognize and establish a connection with the corporate FortiGate.
* Use the FortiClient EMS cloud connector on the corporate FortiGate to connect to FortiSASE:
* The EMS (Endpoint Management Server) cloud connector facilitates the integration between FortiClient endpoints and FortiSASE, enabling seamless sharing of endpoint information.
* Register FortiGate and FortiSASE under the same FortiCloud account:
* By registering both FortiGate and FortiSASE under the same FortiCloud account, you ensure centralized management and synchronization of configurations and policies.
References:
* FortiOS 7.2 Administration Guide: Provides details on configuring Secure Private Access and integrating with FortiGate.
* FortiSASE 23.2 Documentation: Explains how to set up and manage connections between FortiSASE and corporate FortiGate.