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 3 Question 8 Discussion

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

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?

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:

Darnell
22 days ago
Haha, 'Within a group, the log field Malware Kame (mname> has 2 or more unique values'? Sounds like someone had a little too much fun with the question wording. I'll stick with option B, thanks.
upvoted 0 times
Dominga
1 days ago
I agree, that wording is a bit confusing. Option B seems like the most straightforward choice.
upvoted 0 times
...
...
Winifred
1 months ago
Ah, the old 'change the trigger condition' trick. Nice try, but I think option B is the way to go. Gotta love these certification exams, they really keep you on your toes!
upvoted 0 times
Rima
2 days ago
Yeah, those certification exams really make you think. Option B it is!
upvoted 0 times
...
Florinda
18 days ago
I agree, option B seems like the most logical choice in this scenario.
upvoted 0 times
...
Art
20 days ago
Option B is definitely the way to go. Certification exams can be tricky!
upvoted 0 times
...
...
Anthony
1 months ago
Option C is a bit weird, typing in that specific log filter text. Feels like a trick question, you know? I'm going to go with the safer option B.
upvoted 0 times
Elenora
3 days ago
I agree, option C does seem a bit strange. Option B seems like a safer choice.
upvoted 0 times
...
...
Rory
1 months ago
Hmm, looks like we need to configure a FortiSandbox data selector and add it to the event handler. Seems straightforward enough, but I wonder if there's a catch hidden in the details.
upvoted 0 times
...
Dorian
2 months ago
I'm not sure, but I think option A) changing the Log Type field to AntiVirus Log(malware) could also be a valid configuration change.
upvoted 0 times
...
Dannie
2 months ago
I agree with Orville, adding a FortiSandbox data selector seems like the right configuration change.
upvoted 0 times
...
Orville
2 months ago
I think the answer is B) Configure a FortiSandbox data selector and add it to the event handler.
upvoted 0 times
...

Save Cancel