FCP_FAZ_AN-7.4 Questions and Answers

In this exhibit, we observe a search query on the FortiAnalyzer interface displaying log data with details about the connection events, including fields like date, srcip, dstip, service, and dstintf. This setup allows for several functionalities within FortiAnalyzer.

Option A - Download Capability:

FortiAnalyzer provides the option to download search results and reports to a file in multiple formats, such as CSV or PDF, allowing for further offline analysis or archival. This makes it possible to save the search results shown in the exhibit to a file.

Conclusion: Correct.

Option B - Sorting and Customization:

The FortiAnalyzer interface allows users to sort and customize columns for search results. This helps in organizing and viewing the logs in a manner that fits the analyst's needs, such as ordering logs by time, srcip, dstip, or other fields.

Conclusion: Correct.

Option C - Availability in FortiView:

FortiView is a tool within FortiAnalyzer that visualizes data and provides analysis capabilities, including traffic and security event logs. Since these are traffic logs, they are typically available for visualization and analysis within FortiView.

Conclusion: Incorrect.

Option D - Text Mode Search:

The search displayed here appears to be in a structured format, which implies it might be utilizing filters rather than a free-text search. FortiAnalyzer allows both structured searches and text searches, but there's no indication here that text mode was used.

Conclusion: Incorrect.

Conclusion:

Correct Answer: A. They can be downloaded to a file. and B. They are sortable by columns and customizable.

These options are consistent with FortiAnalyzer's capabilities for managing, exporting, and customizing log data.

References:

FortiAnalyzer 7.4.1 documentation on search, export functionalities, and customizable views.

Option A - Purging Log Entries:

A SELECT query in SQL is used to retrieve data from a database and does not have the capability to delete or purge log entries. Purging logs typically requires a DELETE or TRUNCATE command.

Conclusion: Incorrect.

Option B - WHERE Clause Requirement:

In SQL, a SELECT query does not require a WHERE clause. The WHERE clause is optional and is used only when filtering results. A SELECT query can be executed without it, meaning this statement is false.

Conclusion: Incorrect.

Option C - Displaying Database Schema:

A SELECT query retrieves data from specified tables, but it is not used to display the structure or schema of the database. Commands like DESCRIBE, SHOW TABLES, or SHOW COLUMNS are typically used to view schema information.

Conclusion: Incorrect.

Option D - Usage in Macros:

FortiAnalyzer and similar systems often use macros for automated functions or specific query-based tasks. SELECT queries are typically not included in macros because macros focus on procedural or repetitive actions, rather than simple data retrieval.

Conclusion: Correct.

Conclusion:

Correct Answer: D. They are not used in macros.

This aligns with typical SQL usage and the specific functionalities of FortiAnalyzer.

References:

FortiAnalyzer 7.4.1 documentation on SQL queries, database operations, and macro usage.

In the exhibit, the playbook configuration shows the analyst working with the "Attach Data" action within a playbook. Here’s a breakdown of key aspects:

Incident ID: This field is linked to the "Playbook Starter," which indicates that the playbook will attach data to an existing incident.

Attachment: The analyst is configuring an attachment by selecting Run_REPORT with a placeholder ID for report_uuid. This suggests that the report’s UUID will dynamically populate as part of the playbook execution.

Analysis of Options:

Option A - Creating a Trigger Variable:

A trigger variable would typically be set up in the playbook starter or initiation configuration, not within the "Attach Data" action. The setup here does not indicate a trigger, as it’s focusing on data attachment.

Conclusion: Incorrect.

Option B - Creating an Output Variable:

The field Attachment with a report_uuid placeholder suggests that the analyst is defining an output variable that will store the report data or ID, allowing it to be attached to the incident. This variable can then be referenced or passed within the playbook for further actions or reporting.

Conclusion: Correct.

Option C - Creating a Report in the Playbook:

While Run_REPORT is selected, it appears to be an attachment action rather than a report generation task. The purpose here is to attach an existing or dynamically generated report to an incident, not to create the report itself.

Conclusion: Incorrect.

Option D - Creating a SOC Report:

Similarly, this configuration is focused on attaching data, not specifically generating a SOC report. SOC reports are generally predefined and generated outside the playbook.

Conclusion: Incorrect.

Conclusion:

Correct Answer: B. The analyst is trying to create an output variable to be used in the playbook.

The setup allows the playbook to dynamically assign the report_uuid as an output variable, which can then be used in further actions within the playbook.

References:

FortiAnalyzer 7.4.1 documentation on playbook configurations, output variables, and data attachment functionalities.

In the exhibit, we see a playbook in FortiAnalyzer designed to retrieve events based on specific criteria, create an incident, and attach relevant data to that incident. The "Get Event" task configuration specifies filters to match any of the following conditions:

Severity = High

Event Type = Web Filter

Tag = Malware

Analysis of Events:

In the FortiAnalyzer Event Monitor list:

We need to identify events that meet any one of the specified conditions (since the filter is set to "Match Any Condition").

Events Matching Criteria:

Severity = High:

There are two events with "High" severity, both with the "Event Type" IPS.

Event Type = Web Filter:

There are two events with the "Event Type" Web Filter. One has a "Medium" severity, and the other has a "Low" severity.

Tag = Malware:

There are two events tagged with "Malware," both with the "Event Type" Antivirus and "Medium" severity.

After filtering based on these criteria, there are four distinct events:

Two from the "Severity = High" filter.

One from the "Event Type = Web Filter" filter.

One from the "Tag = Malware" filter.

Conclusion:

Correct Answer: D. Four events will be added.

This answer matches the conditions set in the playbook filter configuration and the events listed in the Event Monitor.

References:

FortiAnalyzer 7.4.1 documentation on event filtering, playbook configuration, and incident management criteria.

In FortiAnalyzer's incident management system, analysts have the option to manually manage incidents, which includes attaching relevant reports to an incident for further investigation and documentation. This feature allows analysts to consolidate information, such as detailed reports on suspicious activity, into an incident record, providing a comprehensive view for incident response.

Let's review the other options to clarify why they are incorrect:

Option A: You can manually attach generated reports to incidents

This is correct. FortiAnalyzer allows analysts to manually attach reports to incidents, which is beneficial for providing additional context, evidence, or analysis related to the incident. This functionality is part of the incident management process and helps streamline information for tracking and resolution.

Option B: The status of the incident is always linked to the status of the attached event

This is incorrect. The status of an incident on FortiAnalyzer is managed independently of the status of any attached events. An incident can contain multiple events, each with different statuses, but the incident itself is tracked separately.

Option C: Severity incidents rated with the level High have an initial service-level agreement (SLA) response time of 1 hour

This is incorrect. While incidents have severity levels, specific SLA response times are typically set according to the organization’s incident response policy, and FortiAnalyzer does not impose a default SLA response time of 1 hour for high-severity incidents.

Option D: Incidents must be acknowledged before they can be analyzed

This is incorrect. Incidents on FortiAnalyzer can be analyzed even if they are not yet acknowledged. Acknowledging an incident is often part of the workflow to mark it as being actively addressed, but it is not a prerequisite for analysis.

References: According to FortiAnalyzer documentation, analysts can attach reports to incidents manually, making option A correct. This feature enables better tracking and documentation within the incident management system on FortiAnalyzer​.