NSE6_FSM_AN-7.4 Fortinet NSE 6 - FortiSIEM 7.4 Analyst Questions and Answers

The FortiSIEM Study Guide defines a nested query as a query that has another query embedded within it, where the embedded query is known as the subquery. The FortiSIEM 7.4 User Guide lists the supported nested search scenarios: Outer CMDB Query, Inner Event Query ; Outer Event Query, Inner Event Query ; and Outer Event Query, Inner CMDB Query . These supported combinations prove that the inner or subquery can be either an Event Query or a CMDB Query. LDAP Query and SNMP Query are not listed as supported nested analytics subquery types. LDAP may be used for user discovery or authentication, and SNMP may be used for monitoring or discovery, but neither is referenced as a nested analytics query type. The User Guide also explains that the outer query uses Select from Report to reference the saved inner query and that the matching attribute data types must align between the outer query and the selected display column in the inner query.

The correct answer is D. ZTNA tags. FortiSIEM 7.4 includes FortiEMS endpoint tagging integration. The FortiSIEM 7.4 User Guide states that FortiSIEM supports discovery of FortiEMS servers by using the FortiEMS Management Server API with basic username/password authentication. It also explains that after FortiEMS discovery, FortiSIEM can tag or untag a host by using classification tags on the FortiEMS server. In a ZTNA deployment, those tags are imported by member Fortinet devices, especially FortiGate firewalls, and are referenced in ZTNA firewall rules. The guide gives a common use case in which a host is tagged as suspicious or potentially compromised so firewall rules can isolate it or allow only minimal traffic. Host software versions, FortiSIEM license information, and host login credentials are not the FortiEMS API information relevant to this ZTNA tagging workflow. The API integration supports retrieving FortiEMS-managed host context and using classification/ZTNA tags for automated response and policy enforcement.

To detect three failed login attempts within three minutes, you must set the aggregate count to 3 in the subpattern and the time window to 180 seconds in the rule condition. This ensures the rule triggers only if three or more failed logins occur in that timeframe.

The correct answer is A because three minutes equals 180 seconds, and the aggregate threshold must be set to three matching events. The FortiSIEM Study Guide explains that rule conditions specify event attributes and thresholds that trigger the rule and create an incident. It further states that the time window defines the period within which the subpattern must match for the rule condition to be satisfied. The Study Guide’s single-subpattern rule example shows the same principle: the condition has a configured time window, and the Aggregate section uses a function such as COUNT(Matched Events) to require a minimum number of matching events. In this question, the analyst wants the rule to trigger when three failed login attempts happen within three minutes . Therefore, the rule condition time window must be 180 seconds , and the aggregate count must be 3 . A 90-second window would detect only events inside one and a half minutes, not the required three minutes. An aggregate count of 2 would trigger too early because the requirement is three failed attempts.

FortiSIEM supports both global thresholds and per-device/per-device-object thresholds for some performance events. The Study Guide states that FortiSIEM can define “per-device-object thresholds or global thresholds” for performance events, and separately explains that global thresholds are referenced by the rules engine by default. Therefore, the correct statement is that FortiSIEM uses global and per-device thresholds for performance metrics. Options A, B, and D are too restrictive or false because FortiSIEM does not use only one fixed threshold model.

The correct answer is B because the analyst is searching for events to either of two destination IP addresses, but the filter uses the wrong Boolean relationship. The FortiSIEM Study Guide explains structured searches with multiple conditions and states that “when you use multiple conditions, you must specify the next logical operator between conditions.” It gives a direct example: when searching for events from two specific devices, the first condition is one IP address, the second condition is another IP address, and “the next logical operator between the two conditions is an OR operator, because the search is for events from condition 1 OR condition 2.” The same logic applies here. A single event cannot usually have Destination IP equal to 10.10.1.1 and Destination IP equal to 192.168.1.1 at the same time. Using AND requires both conditions to be true simultaneously, so no results are returned. The correct operator between the two Destination IP conditions is OR.

The best matching analytics search is Username CONTAIN smit. The FortiSIEM Analytics lesson explains keyword and attribute matching by using the CONTAIN operator for searching values inside raw logs or attributes. The Study Guide gives a direct example of FortiSIEM translating keyword logic into a condition such as “Raw Event Log CONTAIN TCP.” That shows the operator is designed for substring-style matching rather than full-value equality. For a user such as JSmith, the string fragment smit is contained inside the username value, so the condition can match events where the username appears as JSmith, jsmith, or possibly in a longer identity string such as a domain-qualified username. Option A is wrong because smith is not the complete username and uses an equality-style comparison. Option B is wrong because it excludes usernames ending in jsmith. Option C uses the wrong operator form for this context. Therefore, the practical FortiSIEM analytics condition that can match the target failed-login event is Username CONTAIN smit.

The correct answer is D because Server A satisfies the rule’s threshold and count requirements, while Server B does not. The Study Guide explains that a FortiSIEM subpattern consists of Filter , Aggregate , and Group By components. It also states that the Aggregate function defines how many or what metric values must match during the time window, while Group By controls how the matching events are grouped into rows. The performance metrics lesson explains that FortiSIEM collects performance and availability data, converts polling results into logs, and uses those metrics for performance, availability, resource utilization, and baselining. In the exhibit, the aggregate evaluates CPU utilization against the device’s CPU critical threshold and also requires a matched-event count of at least two within the 10-minute window. Server A has CPU values above its critical threshold enough times in the window, so it generates one incident. Server B has a lower configured threshold but its collected CPU values do not satisfy the required aggregate condition for the grouped server. Therefore, only Server A generates an incident.

The rule is triggering on successful RDP connection events because the Next operator between the two subpatterns is set to OR . The FortiSIEM Study Guide explains that multiple subpattern rules are used when patterns must occur within a specific time period or when one of several patterns proves that an incident condition exists. It lists the OR operator as: “Subpattern X OR Subpattern Y occurred within the Time Window.” The same Study Guide further explains that if multiple patterns are used, FortiSIEM requires a next operator, and in the OR example, “an event that matches either” subpattern will trigger. It also states that because the next operator is OR, the constraint between the two subpatterns is not enforced.

In the exhibit, Subpattern 1 matches RDP traffic on TCP/UDP port 3389 from FortiGate traffic-forward events, while Subpattern 2 matches logon failure events with COUNT(Matched Events) > = 3. Because the rule uses OR, FortiSIEM can trigger when only the RDP connection subpattern matches, even if the failed-logon subpattern does not match. The correct logic should require both subpatterns to match with the intended relationship constraints, not either subpattern independently.

The verified answer is D. Five . FortiSIEM grouping is based on unique combinations of the selected Group By fields. The Study Guide explains this behavior clearly: if multiple events have the same selected Group By values, “they are grouped together in one row,” and the count column tracks the number of events for each row. In this question, the selected fields are User and Count . The six raw rows contain these combinations: Mike/4, Bob/3, Alice/2, Alice/2, Bob/6, and Mike/5. Because Alice/2 appears twice, those two rows are grouped into a single result. The remaining combinations are unique. So FortiSIEM displays five grouped results, not six. Six would be correct only if every row had a unique User-and-Count combination, or if grouping included another differentiating attribute such as Source IP. Since the question specifically groups only by User and Count, duplicate User/Count pairs collapse into one row. Therefore, the correct result count is five .

The operator is set to " = " , which performs an exact match on the entire raw event log, not a substring search. To find logs that contain the keyword " udp " , the analyst should use the CONTAIN operator instead. This will return all logs where " udp " appears anywhere in the raw log message.

The correct answer is D because the analyst is trying to search for raw logs that contain the keyword udp, but the filter uses the equality operator. The FortiSIEM Study Guide explains keyword searches in terms of Raw Event Log CONTAIN logic. In the keyword phrase search section, the guide states that without quotes, FortiSIEM searches raw event logs by using conditions such as Raw Event Log CONTAIN TCP OR Raw Event Log CONTAIN connection . Another analytics example explains that searching for TCP or UDP events uses the raw event log containing the keyword tcp or udp and that the search returns case-insensitive results for TCP and UDP. This directly eliminates option C. The time range is already set to the last two hours, which is correct for historical raw log searching. The problem is the operator. To find a keyword anywhere inside a raw log message, the analyst should use CONTAIN , not =.

The correct answer is A . In FortiSIEM machine learning training, the Train factor controls how much of the prepared dataset is used for training and how much is reserved for testing. The FortiSIEM 7.4 User Guide states in the regression training procedure that the analyst must choose the Train factor and that it “should be greater than 70%.” It also explains the meaning of the value: 70% of the data is used for training and 30% is used for testing. This directly supports option A. Option B is incorrect because the supported running modes include Local, Local Auto, and AWS; “ML” is not the required run mode. Option C is incorrect because regression can use multiple fields for prediction; the guide instructs the user to choose the fields to use for prediction and the field to predict. Option D is incorrect because prediction input fields and target field should not be the same. Regression builds a model to predict a target field based on other fields, so the configuration must use a valid Train factor rather than matching predictor and target fields.