Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Fortinet Exam FCSS_SOC_AN-7.4 Topic 4 Question 12 Discussion

Actual exam question for Fortinet's FCSS_SOC_AN-7.4 exam
Question #: 12
Topic #: 4
[All FCSS_SOC_AN-7.4 Questions]

Refer to Exhibit:

A SOC analyst is creating the Malicious File Detected playbook to run when FortiAnalyzer generates a malicious file event. The playbook must also update the incident with the malicious file event data.

What must the next task in this playbook be?

Show Suggested Answer Hide Answer
Suggested Answer: B, D, E

Overview of Indicators of Compromise (IoCs): Indicators of Compromise (IoCs) are pieces of evidence that suggest a system may have been compromised. These can include unusual network traffic patterns, the presence of known malicious files, or other suspicious activities.

FortiAnalyzer's Role: FortiAnalyzer aggregates logs from various Fortinet devices to provide comprehensive visibility and analysis of network events. It uses these logs to identify potential IoCs and compromised hosts.

Relevant Log Types:

DNS Filter Logs:

DNS requests are a common vector for malware communication. Analyzing DNS filter logs helps in identifying suspicious domain queries, which can indicate malware attempting to communicate with command and control (C2) servers.


IPS Logs:

Intrusion Prevention System (IPS) logs detect and block exploit attempts and malicious activities. These logs are critical for identifying compromised hosts based on detected intrusion attempts or behaviors matching known attack patterns.

Web Filter Logs:

Web filtering logs monitor and control access to web content. These logs can reveal access to malicious websites, download of malware, or other web-based threats, indicating a compromised host.

Why Not Other Log Types:

Email Filter Logs:

While important for detecting phishing and email-based threats, they are not as directly indicative of compromised hosts as DNS, IPS, and Web filter logs.

Application Filter Logs:

These logs control application usage but are less likely to directly indicate compromised hosts compared to the selected logs.

Detailed Process:

Step 1: FortiAnalyzer collects logs from FortiGate and other Fortinet devices.

Step 2: DNS filter logs are analyzed to detect unusual or malicious domain queries.

Step 3: IPS logs are reviewed for any intrusion attempts or suspicious activities.

Step 4: Web filter logs are checked for access to malicious websites or downloads.

Step 5: FortiAnalyzer correlates the information from these logs to identify potential IoCs and compromised hosts.

Fortinet Documentation: FortiOS DNS Filter, IPS, and Web Filter administration guides.

FortiAnalyzer Administration Guide: Details on log analysis and IoC identification.

By using DNS filter logs, IPS logs, and Web filter logs, FortiAnalyzer effectively identifies possible compromised hosts, providing critical insights for threat detection and response.

Contribute your Thoughts:

Moon
25 days ago
You got that right, Shawn. But hey, if we can't handle a little playbook update action, how are we supposed to handle a real security incident? Bring it on!
upvoted 0 times
Noel
15 days ago
B) A local connector with the action Attach Data to Incident
upvoted 0 times
...
Thea
20 days ago
A) A local connector with the action Update Asset and Identity
upvoted 0 times
...
...
Shawn
1 months ago
Haha, I bet the exam writers are having a field day with these security playbook questions. They're really trying to trip us up, aren't they?
upvoted 0 times
Catrice
1 days ago
D) A local connector with the action Update Incident
upvoted 0 times
...
Karol
7 days ago
B) A local connector with the action Attach Data to Incident
upvoted 0 times
...
Gerald
22 days ago
A) A local connector with the action Update Asset and Identity
upvoted 0 times
...
Tawna
29 days ago
A) A local connector with the action Update Asset and Identity
upvoted 0 times
...
...
Macy
1 months ago
I agree with Sherly. Updating the incident is the essential step here, as the question specifically states that the playbook must update the incident with the malicious file event data.
upvoted 0 times
...
Sherly
1 months ago
The answer is clearly D. The playbook needs to update the incident with the malicious file event data, so the logical next step is to use a local connector with the action Update Incident.
upvoted 0 times
...
Merissa
2 months ago
I believe option B) Attach Data to Incident could also be a valid next task to ensure all relevant information is included.
upvoted 0 times
...
Jonelle
2 months ago
I agree with Alva, updating the incident with the malicious file event data is crucial.
upvoted 0 times
...
Alva
2 months ago
I think the next task should be D) Update Incident.
upvoted 0 times
...

Save Cancel