Question 1

Refer to the exhibit.
A FortiSIEM administrator wants to group some attributes for a report, but is not able to do so successfully. As shown in the exhibit, why are some of the fields
highlighted in red?

Accepted Answer

The red highlighting in the exhibit indicates attributes that cannot be grouped together due to their unique nature. These unique attributes includeEvent Receive
Time,Reporting IP,Event Type,Raw Event Log, andCOUNT(Matched Events).
Attribute Characteristics:
 Event Receive Timeis unique for each event.
 Reporting IPandEvent Typecan vary greatly, making grouping them impractical in this context.
 Raw Event Logrepresents the unprocessed log data, which is also unique.
 COUNT(Matched Events)is a calculated field, not suitable for grouping.
References: FortiSIEM 6.3 User Guide, Reporting section, explains the constraints on grouping attributes in reports.

Question 2

Which FortiSIEM components are capable of performing device discovery?

Accepted Answer

Explanation
Device Discovery in FortiSIEM: Device discovery is the process by which FortiSIEM identifies and adds devices to its management scope.
Role of Collectors: Collectors are responsible for gathering data from network devices, including discovering new devices in the network.
 Functionality: Collectors use protocols such as SNMP, WMI, and others to discover devices and gather their details.
Capability: While agents (Windows and Linux) primarily gather data from their host systems, the collectors actively discover devices across the network.
References: FortiSIEM 6.3 User Guide, Device Discovery section, which details the role of collectors in discovering network devices.

Question 3

If a performance rule is triggered repeatedly due to high CPU use, what occurs in the incident table?

Accepted Answer

Explanation
Incident Management in FortiSIEM: FortiSIEM tracks incidents and their occurrences to help administrators manage and respond to recurring issues.
Performance Rule Triggering: When a performance rule, such as one for high CPU usage, is repeatedly triggered, FortiSIEM updates the corresponding incident
rather than creating a new one each time.
Incident Table Updates:
 Incident Count: The Incident Count value increases each time the rule is triggered, indicating how many times the incident has occurred.
 First Seen and Last Seen Times: These timestamps are updated to reflect the first occurrence and the most recent occurrence of the incident.
References: FortiSIEM 6.3 User Guide, Incident Management section, explains how FortiSIEM handles recurring incidents and updates the incident table
accordingly.

Question 4

Which command displays the Linux agent status?

Accepted Answer

Explanation
Linux Agent in FortiSIEM: The FortiSIEM Linux agent is responsible for collecting logs and metrics from Linux devices and forwarding them to the FortiSIEM
system.
Command for Checking Status: The correct command to check the status of the FortiSIEM Linux agent isservice fortisiem-linux-agent status.
This command queries the status of the FortiSIEM Linux agent service, showing whether it is running, stopped, or encountering issues.
Usage: Properly checking the agent status helps ensure that data collection from Linux devices is functioning as expected.
References: FortiSIEM 6.3 User Guide, Linux Agent Installation and Management section, which includes commands for managing the Linux agent.

Question 5

When configuring collectors located in geographically separated sites, what ports must be open on
a front end firewall?

Accepted Answer

FortiSIEM Architecture: In FortiSIEM, collectors gather data from various sources and send this
data to supervisors and workers within the FortiSIEM architecture.
Communication Requirements: For collectors to effectively send data to the FortiSIEM system, specific communication channels must be open.
Port Usage: The primary port used for secure communication between the collectors and the FortiSIEM infrastructure is HTTPS (port 443).
Network Configuration: When configuring collectors in geographically separated sites, the HTTPS port must be open for the collectors to communicate with both
the supervisor and the worker upload settings addresses. This ensures that the collected data can be securely transmitted to the appropriate processing and
analysis components.
References: FortiSIEM 6.3 Administration Guide, Network Ports section details the necessary ports for communication within the FortiSIEM architecture.

Question 6

Refer to the exhibit.

From SurePassExam
https://www.surepassexam.com/NSE5_FSM-6.3-exam-dumps.html (0 New Questions)
Which section contains the sortings that determine how many incidents are created?

Accepted Answer

Incident Creation in FortiSIEM: Incidents in FortiSIEM are created based on specific patterns and conditions defined within the system.
Group By Function: The "Group By" section in the "Edit SubPattern" window specifies how the data should be grouped for analysis and incident creation.
Impact of Grouping: The way data is grouped affects the number of incidents generated.
Each unique combination of the grouped attributes results in a separate incident.
Exhibit Analysis: In the provided exhibit, the "Group By" section lists "Reporting Device," "Reporting IP," and "User." This means incidents will be created for each
unique combination of these attributes. References: FortiSIEM 6.3 User Guide, Rule and Pattern Creation section, which details how grouping impacts incident
generation.

Question 7

Refer to the exhibit.
What do the yellow stars listed in the Monitor column indicate?

Accepted Answer

Monitor Column Indicators: In FortiSIEM, the Monitor column displays the status of various metrics applied during the discovery process.
Yellow Star Meaning: A yellow star next to a metric indicates that the metric was successfully applied during
Successful Data Collection: This visual indicator helps administrators quickly identify which metrics are active and have data available for analysis.
References: FortiSIEM 6.3 User Guide, Device Monitoring section, which explains the significance of different icons and indicators in the Monitor column.

Question 8

An administrator wants to search for events received from Linux and Windows agents.
Which attribute should the administrator use in search filters, to view events received from agents only.

Accepted Answer

Search Filters in FortiSIEM: When searching for specific events, administrators can use various attributes to filter the results.
Attribute for Agent Events: To view events received specifically from Linux and Windows agents, the attribute External Event Receive Agents should be used.
Function: This attribute filters events that are received from agents, distinguishing them from events received through other protocols or sources.
Search Efficiency: Using this attribute helps the administrator focus on events collected by FortiSIEM agents, making the search results more relevant and
targeted.
References: FortiSIEM 6.3 User Guide, Event Search and Filters section, which describes the available attributes and their usage for filtering search results.

Question 9

Refer to the exhibit.
An administrator is trying to identify an issue using an expression bated on the Expression Builder settings shown in the exhibit however, the error message shown
in the exhibit indicates that the expression is invalid.
Which is the correct expression?

Accepted Answer

Expression Builder in FortiSIEM: The Expression Builder is used to create expressions for analyzing event data.
Correct Syntax: The correct syntax for counting matched events is COUNT(Matched Events).
Function: COUNT is a function that takes a parameter, in this case, 'Matched Events,' to count the number of occurrences.
Common Errors: Incorrect syntax, such as reversing the order or using parentheses improperly, can lead to invalid expressions.
References: FortiSIEM 6.3 User Guide, Expression Builder section, which explains the correct syntax and usage for creating valid expressions for event analysis.

Question 10

If an incident's status is Cleared, what does this mean?

Accepted Answer

Incident Status in FortiSIEM: The status of an incident indicates its current state and helps administrators track and manage incidents effectively.
Cleared Status: When an incident's status is 'Cleared,' it means that a specific condition set to clear the incident has been satisfied.
Clear Condition: This is typically a predefined condition that indicates the issue causing the incident has been resolved or no longer exists.
Automatic vs. Manual Clearance: While some incidents may be cleared automatically based on clear conditions, others might be manually cleared by an operator.
References: FortiSIEM 6.3 User Guide, Incident Management section, detailing the various incident statuses and the conditions that lead to an incident being
marked as 'Cleared.'