FCSS_SOC_AN-7.4 Exam Questions and Answers

QUESTION: 6

Refer to the exhibits.

What can you conclude from analyzing the data using the threat hunting module?

Spearphishing is being used to elicit sensitive information.
DNS tunneling is being used to extract confidential data from the local network.
Reconnaissance is being used to gather victim identity information from the mail server.
FTP is being used as command-and-control (C&C) technique to mine for data.

Answer(s): B

Explanation:

Understanding the Threat Hunting Data:
The Threat Hunting Monitor in the provided exhibits shows various application services, their usage counts, and data metrics such as sent bytes, average sent bytes, and maximum sent bytes. The second part of the exhibit lists connection attempts from a specific source IP (10.0.1.10) to a destination IP (8.8.8.8), with repeated "Connection Failed" messages.
Analyzing the Application Services:
DNS is the top application service with a significantly high count (251,400) and notable sent bytes (9.1 MB).
This large volume of DNS traffic is unusual for regular DNS queries and can indicate the presence of DNS tunneling.
DNS Tunneling:

DNS tunneling is a technique used by attackers to bypass security controls by encoding data within DNS queries and responses. This allows them to extract data from the local network without detection.
The high volume of DNS traffic, combined with the detailed metrics, suggests that DNS tunneling might be in use.
Connection Failures to 8.8.8.8:
The repeated connection attempts from the source IP (10.0.1.10) to the destination IP (8.8.8.8) with connection failures can indicate an attempt to communicate with an external server. Google DNS (8.8.8.8) is often used for DNS tunneling due to its reliability and global reach.
Conclusion:
Given the significant DNS traffic and the nature of the connection attempts, it is reasonable to conclude that DNS tunneling is being used to extract confidential data from the local network.
Why Other Options are Less Likely:
Spearphishing (A): There is no evidence from the provided data that points to spearphishing attempts, such as email logs or phishing indicators.
Reconnaissance (C): The data does not indicate typical reconnaissance activities, such as scanning or probing mail servers.
FTP C&C (D): There is no evidence of FTP traffic or command-and-control communications using FTP in the provided data.

Reference:

SANS Institute: "DNS Tunneling: How to Detect Data Exfiltration and Tunneling Through DNS Queries" SANS DNS Tunneling
OWASP: "DNS Tunneling" OWASP DNS Tunneling
By analyzing the provided threat hunting data, it is evident that DNS tunneling is being used to exfiltrate data, indicating a sophisticated method of extracting confidential information from the network.

Reveal Solution Next Question

QUESTION: 7

Refer to the exhibits.

You configured a spearphishing event handler and the associated rule. However. FortiAnalyzer did not generate an event.
When you check the FortiAnalyzer log viewer, you confirm that FortiSandbox forwarded the appropriate logs, as shown in the raw log exhibit.
What configuration must you change on FortiAnalyzer in order for FortiAnalyzer to generate an event?

In the Log Type field, change the selection to AntiVirus Log(malware).
Configure a FortiSandbox data selector and add it tothe event handler.
In the Log Filter by Text field, type the value: .5 ub t ype ma Iwa re..
Change trigger condition by selecting. Within a group, the log field Malware Kame (mname> has 2 or more unique values.

Answer(s): B

Explanation:

Understanding the Event Handler Configuration:
The event handler is set up to detect specific security incidents, such as spearphishing, based on logs forwarded from other Fortinet products like FortiSandbox.
An event handler includes rules that define the conditions under which an event should be triggered.
Analyzing the Current Configuration:

The current event handler is named "Spearphishing handler" with a rule titled "Spearphishing Rule 1".
The log viewer shows that logs are being forwarded by FortiSandbox but no events are generated by FortiAnalyzer.
Key Components of Event Handling:
Log Type: Determines which type of logs will trigger the event handler. Data Selector: Specifies the criteria that logs must meet to trigger an event. Automation Stitch: Optional actions that can be triggered when an event occurs. Notifications: Defines how alerts are communicated when an event is detected.
Issue Identification:
Since FortiSandbox logs are correctly forwarded but no event is generated, the issue likely lies in the data selector configuration or log type matching.
The data selector must be configured to include logs forwarded by FortiSandbox.
Solution:
B . Configure a FortiSandbox data selector and add it to the event handler:
By configuring a data selector specifically for FortiSandbox logs and adding it to the event handler, FortiAnalyzer can accurately identify and trigger events based on the forwarded logs.
Steps to Implement the Solution:
Step 1: Go to the Event Handler settings in FortiAnalyzer.
Step 2: Add a new data selector that includes criteria matching the logs forwarded by FortiSandbox (e.g., log subtype, malware detection details).
Step 3: Link this data selector to the existing spearphishing event handler. Step 4: Save the configuration and test to ensure events are now being generated.
Conclusion:
The correct configuration of a FortiSandbox data selector within the event handler ensures that FortiAnalyzer can generate events based on relevant logs.

Reference:

Fortinet Documentation on Event Handlers and Data Selectors FortiAnalyzer Event Handlers Fortinet Knowledge Base for Configuring Data Selectors FortiAnalyzer Data Selectors By configuring a FortiSandbox data selector and adding it to the event handler, FortiAnalyzer will be able to accurately generate events based on the appropriate logs.

Reveal Solution Next Question

QUESTION: 8

While monitoring your network, you discover that one FortiGate device is sending significantly more logs to FortiAnalyzer than all of the other FortiGate devices in the topology. Additionally, the ADOM that the FortiGate devices are registered to consistently exceeds its quota.

What are two possible solutions? (Choose two.)

Increase the storage space quota for the first FortiGate device.
Create a separate ADOM for the first FortiGate device and configure a different set of storage policies.
Reconfigure the first FortiGate device to reduce the number of logs it forwards to FortiAnalyzer.
Configure data selectors to filter the data sent by the first FortiGate device.

Answer(s): B,C

Explanation:

Understanding the Problem:

One FortiGate device is generating a significantly higher volume of logs compared to other devices, causing the ADOM to exceed its storage quota.
This can lead to performance issues and difficulties in managing logs effectively within FortiAnalyzer.
Possible Solutions:
The goal is to manage the volume of logs and ensure that the ADOM does not exceed its quota, while still maintaining effective log analysis and monitoring.
Solution A: Increase the Storage Space Quota for the First FortiGate Device:
While increasing the storage space quota might provide a temporary relief, it does not address the root cause of the issue, which is the excessive log volume.
This solution might not be sustainable in the long term as log volume could continue to grow. Not selected as it does not provide a long-term, efficient solution. Solution B: Create a Separate ADOM for the First FortiGate Device and Configure a Different Set of Storage Policies:
Creating a separate ADOM allows for tailored storage policies and management specifically for the high-log-volume device.
This can help in distributing the storage load and applying more stringent or customized retention and storage policies.
Selected as it effectively manages the storage and organization of logs. Solution C: Reconfigure the First FortiGate Device to Reduce the Number of Logs it Forwards to FortiAnalyzer:
By adjusting the logging settings on the FortiGate device, you can reduce the volume of logs forwarded to FortiAnalyzer.
This can include disabling unnecessary logging, reducing the logging level, or filtering out less critical logs.
Selected as it directly addresses the issue of excessive log volume. Solution D: Configure Data Selectors to Filter the Data Sent by the First FortiGate Device:
Data selectors can be used to filter the logs sent to FortiAnalyzer, ensuring only relevant logs are forwarded.
This can help in reducing the volume of logs but might require detailed configuration and regular updates to ensure critical logs are not missed.
Not selected as it might not be as effective as reconfiguring logging settings directly on the FortiGate device.
Implementation Steps:
For Solution B:
Step 1: Access FortiAnalyzer and navigate to the ADOM management section. Step 2: Create a new ADOM for the high-log-volume FortiGate device. Step 3: Register the FortiGate device to this new ADOM. Step 4: Configure specific storage policies for the new ADOM to manage log retention and storage.
For Solution C:
Step 1: Access the FortiGate device's configuration interface.
Step 2: Navigate to the logging settings.
Step 3: Adjust the logging level and disable unnecessary logs.
Step 4: Save the configuration and monitor the log volume sent to FortiAnalyzer.

Reference:

Fortinet Documentation on FortiAnalyzer ADOMs and log management FortiAnalyzer Administration Guide
Fortinet Knowledge Base on configuring log settings on FortiGate FortiGate Logging Guide By creating a separate ADOM for the high-log-volume FortiGate device and reconfiguring its logging settings, you can effectively manage the log volume and ensure the ADOM does not exceed its quota.

Reveal Solution Next Question

QUESTION: 9

Refer to the Exhibit:

An analyst wants to create an incident and generate a report whenever FortiAnalyzer generates a malicious attachment event based on FortiSandbox analysis. The endpoint hosts are protected by FortiClient EMS integrated with FortiSandbox. All devices are logging to FortiAnalyzer.
Which connector must the analyst use in this playbook?

FortiSandbox connector
FortiClient EMS connector
FortiMail connector
Local connector

Answer(s): A

Explanation:

Understanding the Requirements:
The objective is to create an incident and generate a report based on malicious attachment events detected by FortiAnalyzer from FortiSandbox analysis.
The endpoint hosts are protected by FortiClient EMS, which is integrated with FortiSandbox. All logs are sent to FortiAnalyzer.
Key Components:
FortiAnalyzer: Centralized logging and analysis for Fortinet devices. FortiSandbox: Advanced threat protection system that analyzes suspicious files and URLs. FortiClient EMS: Endpoint management system that integrates with FortiSandbox for endpoint protection.
Playbook Analysis:
The playbook in the exhibit consists of three main actions: GET_EVENTS, RUN_REPORT, and CREATE_INCIDENT.

EVENT_TRIGGER: Starts the playbook when an event occurs.
GET_EVENTS: Fetches relevant events.
RUN_REPORT: Generates a report based on the events.
CREATE_INCIDENT: Creates an incident in the incident management system.
Selecting the Correct Connector:
The correct connector should allow fetching events related to malicious attachments analyzed by FortiSandbox and facilitate integration with FortiAnalyzer.
Connector Options:
FortiSandbox Connector:
Directly integrates with FortiSandbox to fetch analysis results and events related to malicious attachments.
Best suited for getting detailed sandbox analysis results.
Selected as it is directly related to the requirement of handling FortiSandbox analysis events.
FortiClient EMS Connector:
Used for managing endpoint security and integrating with endpoint logs.
Not directly related to fetching sandbox analysis events.
Not selected as it is not directly related to the sandbox analysis events.
FortiMail Connector:
Used for email security and handling email-related logs and events.
Not applicable for sandbox analysis events.
Not selected as it does not relate to the sandbox analysis.
Local Connector:
Handles local events within FortiAnalyzer itself.
Might not be specific enough for fetching detailed sandbox analysis results. Not selected as it may not provide the required integration with FortiSandbox.
Implementation Steps:
Step 1: Ensure FortiSandbox is configured to send analysis results to FortiAnalyzer. Step 2: Use the FortiSandbox connector in the playbook to fetch events related to malicious attachments.
Step 3: Configure the GET_EVENTS action to use the FortiSandbox connector. Step 4: Set up the RUN_REPORT and CREATE_INCIDENT actions based on the fetched events.

Reference:

Fortinet Documentation on FortiSandbox Integration FortiSandbox Integration Guide Fortinet Documentation on FortiAnalyzer Event Handling FortiAnalyzer Administration Guide By using the FortiSandbox connector, the analyst can ensure that the playbook accurately fetches events based on FortiSandbox analysis and generates the required incident and report.

Reveal Solution Next Question

QUESTION: 10

Your company is doing a security audit To pass the audit, you must take an inventory of all software and applications running on all Windows devices
Which FortiAnalyzer connector must you use?

FortiClient EMS
ServiceNow
FortiCASB
Local Host

Answer(s): A

Explanation:

Requirement Analysis:
The objective is to inventory all software and applications running on all Windows devices within the organization.
This inventory must be comprehensive and accurate to pass the security audit.
Key Components:
FortiClient EMS (Endpoint Management Server):
FortiClient EMS provides centralized management of endpoint security, including software and application inventory on Windows devices.
It allows administrators to monitor, manage, and report on all endpoints protected by FortiClient.
Connector Options:
FortiClient EMS:
Best suited for managing and reporting on endpoint software and applications.
Provides detailed inventory reports for all managed endpoints.
Selected as it directly addresses the requirement of taking inventory of software and applications on Windows devices.
ServiceNow:
Primarily a service management platform.
While it can be used for asset management, it is not specifically tailored for endpoint software inventory.
Not selected as it does not provide direct endpoint inventory management.
FortiCASB:
Focuses on cloud access security and monitoring SaaS applications.
Not applicable for managing or inventorying endpoint software.
Not selected as it is not related to endpoint software inventory.
Local Host:
Refers to handling events and logs within FortiAnalyzer itself.
Not specific enough for detailed endpoint software inventory.
Not selected as it does not provide the required endpoint inventory capabilities.
Implementation Steps:
Step 1: Ensure all Windows devices are managed by FortiClient and connected to FortiClient EMS. Step 2: Use FortiClient EMS to collect and report on the software and applications installed on these devices.
Step 3: Generate inventory reports from FortiClient EMS to meet the audit requirements.

Reference:

Fortinet Documentation on FortiClient EMS FortiClient EMS Administration Guide By using the FortiClient EMS connector, you can effectively inventory all software and applications on Windows devices, ensuring compliance with the security audit requirements.

Reveal Solution Next Question

Fortinet FCSS_SOC_AN-7.4 Exam (page: 2) Fortinet FCSS - Security Operations 7.4 Analyst Updated on: 12-Feb-2026

QUESTION: 6

Explanation:

Reference:

QUESTION: 7

Explanation:

Reference:

QUESTION: 8

Explanation:

Reference:

QUESTION: 9

Explanation:

Reference:

QUESTION: 10

Explanation:

Reference:

Fortinet FCSS_SOC_AN-7.4 Exam (page: 2)
Fortinet FCSS - Security Operations 7.4 Analyst
Updated on: 12-Feb-2026