FCSS_SASE_AD-25 FCSS - FortiSASE 25 Administrator Questions and Answers

SSO users can be imported into FortiSASE and added to user groups.

SSO is recommended only for agent-based deployments.

SSO overrides any other previously configured user authentication.

SSO identity providers can be integrated using public and private access types.

Remote users must upgrade the FortiClient manually.

FortiSASE automatically upgrades FortiClient when a new version is released.

The FortiSASE administrator must assign endpoint groups to an endpoint upgrade rule.

The FortiSASE administrator will upload the desired FortiClient version to the FortiSASE portal and push it to endpoints.

FortiSASE runs a ping from the endpoint to calculate the TTL to the SaaS application.

FortiSASE runs SNMP traps to the endpoint using the DEM agent to verify the SaaS application health status.

FortiSASE runs a netstat from the endpoint to the SaaS application to see if ports are open.

FortiSASE runs a trace job on the endpoint using the DEM agent to the Software-as-a-Service (SaaS) application.

Windows-AD is excluded from FortiSASE management.

The FortiClient version installed on Windows AD does not match the expected version on FortiSASE.

The device posture for Windows-AD has changed.

The remote VPN user on Windows-AD no longer matches any VPN policy.

It provides end-to-end network visibility from all the FortiSASE security PoPs to a specific SaaS application.

It gathers all the vulnerability information from all the FortiClient endpoints.

It is used for performing device compliance checks on endpoints.

It monitors the FortiSASE POP health based on ping probes.

Identity & access management (IAM)

Points of presence

Endpoint management

Logging

Sandbox

Configure a steering bypass tunnel firewall policy using Google Maps FQDN to exclude and redirect the traffic.

Add the Google Maps URL in the zero trust network access (ZTNA) TCP access proxy forwarding rule.

Add the Google Maps URL as a steering bypass destination in the endpoint profile.

Exempt Google Maps in URL filtering in the web filter profile.

Certificate inspection is not being used to scan application traffic.

Deep inspection is not being used to scan traffic.

The private access policy must be to set to log Security Events.

The inline-CASB application control profile does not have application categories set to Monitor.

The logs are deleted from FortiSASE.

The logs are indexed and can be stored in a SQL database.

The logs are backed up on FortiCloud.

The logs are compressed and archived.

Objects support two-way synchronization.

Objects created on FortiSASE can be retrieved on FortiManager.

Objects that are only flow-based are supported.

Objects are considered read-only on FortiSASE.

application control with inline-CASB

data loss prevention (DLP) with Microsoft Purview Information Protection (MPIP)

web filter with inline-CASB

DNS filter with domain filter

For user access control to FortiSASE

For allocation and assignment of unique IP addresses to remote users

For regulatory compliance

For isolation and identification