Pass the Fortinet Fortinet Network Security Expert NSEI_OTS_AR-7.6 Questions and answers with CertsForce

The correct answer is A . Policy ID 8 contains the Supervisors user group, so authentication is required for traffic matching that policy. However, policy ID 9 permits traffic to PLC-1 without a user or user-group authentication requirement. Fortinet explains that when an authentication policy is followed by a fall-through policy that does not require authentication , traffic can match the fall-through policy and proceed without generating a login prompt. This is particularly relevant because the default CLI setting is auth-on-demand implicitly. Under the default implicitly behavior, FortiGate does not trigger active authentication when a matching unauthenticated fall-through policy exists. Setting auth-on-demand always, or requiring authentication on all potentially matching policies, changes that behavior. Therefore, HTTPS succeeds without prompting because authentication was not configured on firewall policy ID 9 .

The correct answer is C. Industrial Control System (ICS) . The study guide states that “ICS is a main component of OT” and “consists of systems used for monitoring and controlling industrial processes.” It also explains that ICS includes various devices, systems, controls, and networks that manage industrial processes, and that the most common types are SCADA and distributed control systems (DCS) . This makes ICS the primary OT component for monitoring and controlling industrial processes.

The other options are related OT components, but they are not the best answer to this wording. SCADA collects real-time data and helps visualize and control the OT environment, but it is described as a system within the broader ICS structure. PLC devices collect and transmit real-time data and connect sensors and RTUs to SCADA, while IIoT refers to sensors, actuators, and other connected field devices. Therefore, the overarching main OT component for monitoring and controlling industrial processes is ICS .

The correct answer is A . The study guide describes all three protocols as supporting deterministic or real-time industrial communication. Ethernet/IP uses standard Ethernet and TCP/IP with an application-layer mechanism that can provide real-time communication when deployed within an appropriate limited range. EtherCAT explicitly provides real-time communication in a primary-secondary architecture and achieves its performance by skipping OSI layers 3 through 6. POWERLINK is also explicitly defined as a real-time communication protocol used mainly for transmitting process data. They do not all follow the complete OSI model because EtherCAT bypasses several layers and POWERLINK primarily uses layers 2 and 7. Client-server behavior is specifically associated with Modbus , and star/ring topology characteristics relate to redundancy mechanisms such as PRP, MRP, and HSR rather than these three industrial protocols collectively.

================

The correct answer is C. The output of the CLI command get rule otvp status . In the Virtual Patching section, the study guide shows the workflow where FortiGate queries FortiGuard for device-specific vulnerabilities, receives OT virtual patching signatures, maps them to the device MAC address, and then explicitly displays the CLI verification command get rule otvp status together with fields such as Rule-name , Vuln_type , and Cve . This is the direct confirmation mechanism shown in the guide for checking whether OT devices have virtual patching rules associated with them.

The other options are less accurate for confirmation. The OT View page is for Purdue-level visualization, and the Asset Identity List page shows device and asset information, but neither is presented in the guide as the command or control used to verify virtual patching status. The study guide specifically uses get rule otvp status as the status check tied to virtual patching behavior.

According to the OT Security 7.6 Architect study guide section on Asset Management , specifically regarding FortiNAC Visibility :

Layer 2 Polling Data : Because each physical address is unique, FortiNAC identifies hosts as they connect to the network. The information gathered during this process fills in the physical address and location information in the database.

Visibility Components : The guide states that the physical address learned , the time it was learned , and where it was learned from provide the foundation of endpoint visibility in the form of " what, where, and when " information. This confirms that Where it was learned (Option A) and The time it was learned (Option D) are correct.

Exclusions :

Layer 3 Polling : The MAC-to-IP correlation (Option B) is explicitly defined as a function of Layer 3 polling , where the correlated IP address is added to the database record for the corresponding MAC address.

DHCP Fingerprinting : The host name or system name (Option C) and the operating system are gathered via DHCP fingerprinting , not layer 2 polling.

Industrial Protocol

Correct Characteristic

POWERLINK

Mainly used for the transmission of process data

EtherCAT

Offers real-time data transmission in a primary-secondary configuration

Modbus

Uses client/server communication

Ethernet/IP

Based entirely on Ethernet standards

The correct mappings follow the industrial Ethernet characteristics defined in the OT Security 7.6 curriculum. Ethernet/IP is the industrial protocol based entirely on Ethernet standards and adapts to the standard Ethernet/TCP-IP architecture. EtherCAT is designed for deterministic real-time communication and specifically operates in a primary-secondary configuration while bypassing OSI layers 3 through 6. POWERLINK is an open real-time industrial Ethernet protocol that uses OSI layers 2 and 7 and is mainly intended for transmitting process data. Modbus , by contrast, uses a client/server communication model in which the server responds only after receiving a request from a client; it is not considered a real-time transmission protocol. These distinctions uniquely determine all four drag-and-drop placements.

The correct answers are B. The Datasets library and D. The Chart library .

The study guide explains that a FortiAnalyzer report is built from charts, and that charts consist of two elements: datasets and format . It states: “A FortiAnalyzer report is a set of data organized in charts” and “Charts consist of two elements: Datasets … and Format.” It then goes further in the Customizing Reports section and explicitly says “By default, the Chart Library contains more than 300 charts” and “By default, the Datasets library contains almost 400 datasets.” It also states that you can clone and edit both charts and datasets, and create new ones , which is exactly how you enhance and customize an existing report.

The other options are not the best answers for this question. FortiView can export a chart into a report chart, and Log View can help build a custom dataset and chart from search results, but the question asks which options you can use to enhance the report itself. The study guide identifies the actual report-customization components as the Chart Library and Datasets library . Dashboard library is not presented as a FortiAnalyzer report customization library in this section.

The verified answer is C. The Fabric settings . The study guide ties FortiAnalyzer-triggered actions to the Security Fabric relationship with FortiGate, not to playbook tasks or standalone event handlers alone. It explains that “within the Security Fabric environment, FortiAnalyzer is a key element in the creation of automation stitches” and shows the flow where a downstream FortiGate sends logs to FortiAnalyzer, then FortiAnalyzer parses the logs and notifies the root FortiGate , after which the root FortiGate triggers the action . This shows that FortiAnalyzer must be configured so it can communicate with FortiGate through the Security Fabric.

The guide also states that FortiAnalyzer is the foundation of the Security Fabric , providing logging, reporting, analytics, and automation for Fabric devices and endpoints. It further explains that the FortiAnalyzer Fabric connector consolidates the traffic logs within the Security Fabric. This confirms that the automation workflow depends on proper Security Fabric integration. A playbook task is used for automated SOC actions, and an event handler is used to generate events from logs, but neither one alone establishes the direct communication path needed between FortiAnalyzer and FortiGate. Therefore, the required configuration on FortiAnalyzer is the Fabric settings .

Based on the provided exhibits from the FortiAnalyzer playbook engine:

Playbook Trigger Condition : The Partial Playbook configuration exhibit shows that the playbook is set to trigger based on a condition where the Basic Handler Name is Equal To IPS_Attack_Handling.

Event vs. Log : In FortiAnalyzer, the field Basic Handler Name is a property of an Event record, indicating the specific Event Handler that generated it. A playbook configured with this condition is triggered by an Event , not directly by a raw log.

Playbook Execution Flow : The Partial Playbook Monitor view shows the execution sequence:

Event_Trigger (Starter) : This is the entry point of the playbook, which matches the condition defined in the configuration.

IPS_Attack_Incident : The first task executed after the trigger.

Run_Report : The task in question, which is executed as part of the automated workflow initiated by the starter.

Conclusion : Since the playbook ' s " Starter " is defined by the IPS_Attack_Handling handler name, an event produced by that handler is the root trigger for the entire playbook execution, including the Run_Report task.

Therefore, the Run_Report task was triggered (as part of the playbook) by an IPS_Attack_Handling event .

The correct answer is D . The exhibit shows the IPS event with the status Mitigated . Fortinet defines a Mitigated event as one where the security risk has been blocked or dropped ; an IPS log whose action is block or drop is the explicit example given in the OT Security 7.6 study guide. A Contained status instead indicates that the risk source has been isolated, such as an antivirus quarantine action. An Unhandled status indicates that the risk remains open—for example, an IPS event where the action is pass. The Web.Client application-control entry in the exhibit has a blank status, so it cannot correctly be described as either Unhandled or Contained based solely on the displayed information. Therefore, the definitive conclusion from the Event Monitor is that the corresponding IPS action was block or drop .

================