NSE7_OTS-7.2 Fortinet NSE 7 - OT Security 7.2 Questions and Answers

The first condition on the SubPattern filter must use the OR logical operator.

The attributes in the Group By section must match the ones in Fitters section.

The Aggregate attribute COUNT expression is incompatible with the filters.

The SubPattern is missing the filter to match the Modbus protocol.

Planning a threat hunting strategy

Implementing strategies to automatically bring PLCs offline

Creating disaster recovery plans to switch operations to a backup plant

Evaluating what can go wrong before it happens

It can be used for IoT device detection.

It can be used for industrial intrusion detection and prevention.

It can be used for network micro-segmentation.

It can be used for device profiling.

Edge

Cloud

Core

Access

Create a back-end backup network as a redundancy measure.

Implement SD-WAN to manage traffic on each ISP link.

Add additional internal firewalls to access OT devices.

Create more access policies to prevent unauthorized access.

PLCs use IEEE802.1Q protocol to communicate each other.

An administrator can create firewall policies in the switch to secure between PLCs.

This integration solution expands VLAN capabilities from Layer 2 to Layer 3.

There is no micro-segmentation in this topology.

IPS must be enabled to inspect application signatures.

The application filter overrides the default action of some IEC 104 signatures.

IEC 104 signatures are all allowed except the C.BO.NA 1 signature.

SSL Inspection must be set to deep-inspection to correctly apply application control.

Set a unique forward domain on each interface on the network.

Set FortiGate to operate in transparent mode.

Set a software switch on FortiGate to handle inter-VLAN traffic.

Set a FortiGate interface with the switch to operate as an 802.1 q trunk.

It uses OSI Layer 2 and the primary device sends data based on request from secondary device.

It uses OSI Layer 2 and both the primary/secondary devices always send data during the communication.

It uses OSI Layer 2 and both the primary/secondary devices send data based on a matching token ring.

It uses OSI Layer 2 and the secondary device sends data based on request from primary device.

Device inventory reports

Payment card industry (PCI) logging reports

Configuration management database (CMDB) operational reports

Business service reports

To isolate PLCs or RTUs in the event of external attacks

To configure event handlers and take further action on FortiGate

To determine which type of messages from the PLC or RTU causes issues in the plant

To help OT administrators configure the network and prevent breaches

port2, port2-vlan10, and port2-vlan1 are part of the software switch interface.

The VLAN ID of port1-vlan1 can be changed to the VLAN ID 10.

port1-vlan10 and port2-vlan10 are part of the same broadcast domain

port1, port1-vlan10, and port1-vlan1 are in different broadcast domains

You must set correct operator in event handler to trigger an event.

You can automate SOC tasks through playbooks.

Each playbook can include multiple triggers.

You cannot use Windows and Linux hosts security events with FortiSoC.

The switch on FGT-2 must be hardware to implement micro-segmentation.

Micro-segmentation on FGT-2 prevents direct device-to-device communication.

Traffic must be inspected by FGT-EDGE in OT networks.

FGT-2 controls intra-VLAN traffic through firewall policies.

Reduce security risk and threat attacks

Remove centralized network security policies

Enhance network performance of OT applications

Replace standard links with lower cost connections

Set a unique forward domain for each interface of the software switch.

Create a VLAN for each device and replace the current FGT-2 software switch members.

Enable explicit intra-switch policy to require firewall policies on FGT-2.

Implement policy routes on FGT-2 to control traffic between devices.

FortiGate has no IPS industrial signature database enabled.

The listed IPS signatures are classified as SCADA equipment.

All IPS signatures are overridden and must block traffic match signature patterns.

The IPS profile inspects only traffic originating from SCADA equipment.