Pass the Fortinet Fortinet Certified Professional Security Operations NSE7_SOC_AR-7.6 Questions and answers with CertsForce

In FortiSOAR 7.6 , step utilities are advanced configurations applied to individual playbook steps to control logic, timing, and data processing. According to the Playbook Engine architecture:

Timeout (A): The Timeout utility allows an administrator to define a maximum duration for a step to complete. If the step does not finish within this designated window, the playbook engine terminates the step and the overall playbook execution to prevent hung processes and resource exhaustion.

Loop (B): The Loop utility is used for iterative processing (e.g., performing a lookup for every IP in a list). A playbook step can only contain one Loop utility configuration . If multiple iterations are required across different data sets, they must be handled in separate steps or nested child playbooks.

Condition (D): The Condition utility (Decision Step logic) behaves differently when a Loop is present. If there is no loop, the condition determines if the step executes once. If a loop is present, the condition is evaluated for each item in the loop, effectively acting as a filter for which iterations proceed.

Why other options are incorrect:

Variables (C): The Variables utility (Set Variable) is used to define new custom variables within the scope of that step for later use. It does not " store the output of the step directly in the step itself " ; step outputs are automatically stored in the vars.steps. < step_name > object by the engine regardless of the utility used.

Mock Output (E): The Mock Output utility is used for testing and development to simulate successful data returns without actually executing a connector. It uses JSON format , not HTML, to ensure the simulated data structure matches what the playbook engine expects for downstream Jinja processing.

Exact Extract: “INFO verbosity is recommended for well-established playbooks. It contains only the final playbook execution status and individual playbook step status.” The guide further states: “DEBUG verbosity is recommended for newer playbooks or for active troubleshooting. It contains detailed logging that includes execution information, such as step input, output, configuration, and other details.”

The correct answer is B . In the exhibit, the executed playbook shows Mode: INFO . INFO mode gives only high-level execution status and step status, which explains why the error panel shows only minimal details such as status: failed and execution time. To see connector input, output, configuration, and more useful troubleshooting details, the playbook logging verbosity must be changed to DEBUG .

A may cause a connector step to fail, but it does not explain why error details are missing. C is wrong because Ignore Error would allow the workflow to continue rather than fail normally. D could cause permission-related failure, but again it does not explain the lack of diagnostic detail. The visible clue is the logging mode.

Technical Deep Dive: For a newly built playbook, you should run tests in DEBUG mode until the workflow is stable. DEBUG logs expose step inputs, connector payloads, returned outputs, variable values, and configuration details. After validation, switch back to INFO in production to reduce log volume and storage usage. FortiGate NP/CP hardware offloading is irrelevant here because this is FortiSOAR workflow logging and connector execution diagnostics, not firewall data-plane traffic processing.

Exact Extract: “FortiSOAR assumes the Preparation phase is outside its incident handling scope because it is considered a pre-SOAR responsibility.”

Exact Extract: “In FortiSOAR, the Detection and Analysis phases are expanded into Detection, Identification, and Confirmation… In the Identification phase, analysts can evaluate the alerts tied to the incident, understand the context, and enrich indicators. In the Confirmation phase, an analyst can confirm whether the incident is a true positive or a false positive.”

The correct answers are B and D . NIST 800-61 Revision 2 uses broader incident handling phases, including Preparation , Detection and Analysis , Containment , Eradication , Recovery , and Post-Incident Activity . FortiSOAR modifies that model by treating Preparation as outside SOAR scope and splitting NIST’s Detection and Analysis into more operationally useful FortiSOAR phases: Detection , Identification , and Confirmation . Therefore, Identification and Confirmation are FortiSOAR-specific phase names that are not standalone NIST phases.

A is wrong because Preparation is a NIST phase, but FortiSOAR excludes it from its incident handling workflow. C is not the best answer because Detection is part of NIST’s combined Detection and Analysis phase and is also present in FortiSOAR.

Technical Deep Dive: FortiSOAR’s split is practical. Detection is when the alert or incident enters FortiSOAR. Identification is where analysts enrich, contextualize, and scope the issue. Confirmation is the decision point where the incident is validated as true positive or false positive. This granularity improves playbook design because different automation belongs in each phase. FortiGate NP/CP offloading has no relevance here because this is incident lifecycle modeling, not traffic processing.

Exact Extract: “MITRE ATT & CK classifies and describes cyberattacks and intrusions through 14 tactics… These categories are further broken down into specific techniques and subtechniques.”

Exact Extract: “The attacker then performs active reconnaissance using a mix of techniques, including port scanning and IP discovery, to find high-priority targets.”

The correct answers are A and D . The infected host first collected its own network configuration and connection details. That maps to System Network Connections Discovery , because MITRE defines this technique as attempting to list network connections to or from the compromised system. The later behavior—sending low-volume connection attempts to multiple internal addresses to identify responding hosts—maps best to Active Scanning , because MITRE describes active scanning as probing victim infrastructure through network traffic.

Network Sniffing is wrong because the scenario does not describe passive packet capture or monitoring traffic on an interface. Lateral Movement is also wrong because it is a MITRE tactic, not the best technique for host discovery activity. The host is still discovering reachable systems; it has not yet moved to another internal system.

Technical Deep Dive: In a Fortinet SOC investigation, this sequence is a classic post-compromise discovery pattern. Commands such as ipconfig, route print, netstat, Get-NetTCPConnection, or arp -a support System Network Connections Discovery. Low-rate probes to many internal IPs are often stealthier than noisy scans and may appear as sparse FortiGate traffic logs, Windows firewall events, or EDR telemetry. FortiSIEM should correlate this with source host, destination spread, port diversity, and time window. FortiGate NP/CP chips may accelerate allowed sessions, but detection occurs in FortiSIEM from logs and metadata, not inside the ASIC forwarding path.

Slot 1: data Slot 2: json_query Slot 3: ( " results[?type== ' FileHash-MD5 ' ] " ) Slot 4: value

Final Expression: {{ vars.artifacts.data | json_query( " results[?type== ' FileHash-MD5 ' ] " ) .value }}

In FortiSOAR 7.6 , advanced data manipulation within playbooks often requires the use of JMESPath queries via the json_query Jinja filter. To extract specific data from a complex JSON object (like the vars.artifacts dictionary shown in the exhibit), the analyst must follow the structural hierarchy:

Slot 1 (data): Based on the exhibit, the root of the artifact information is located under vars.artifacts.data. Therefore, " data " is the starting point for the filter.

Slot 2 (json_query): To perform advanced filtering (searching for a specific type), the json_query filter must be applied. This allows the playbook to traverse the list and find items matching a specific key-value pair.

Slot 3 ( " results[?type== ' FileHash-MD5 ' ] " ): This is the JMESPath expression. It looks into the results array and applies a filter [?...] to find only those objects where the type attribute exactly matches FileHash-MD5.

Slot 4 (value): Once the correct object(s) are found, the expression needs to return the actual hash. In the JSON exhibit, the MD5 string is stored in the key named value.

Why other options are incorrect:

tojson: This filter converts a dictionary/list into a JSON string, which would break the ability to further query the object for the " value " field.

results (as a standalone slot): While " results " is part of the path, it is handled inside the json_query string to allow for conditional filtering.

Understanding the Playbook Requirements:

The SOC analyst needs to design a playbook that filters for high severity events.

The playbook must also attach the event information to an existing incident.

Analyzing the Provided Exhibit:

The exhibit shows the available actions for a local connector within the playbook.

Actions listed include:

Update Asset and Identity

Get Events

Get Endpoint Vulnerabilities

Create Incident

Update Incident

Attach Data to Incident

Run Report

Get EPEU from Incident

Evaluating the Options:

Get Events: This action retrieves events but does not attach them to an incident.

Update Incident: This action updates an existing incident but is not specifically for attaching event data.

Update Asset and Identity: This action updates asset and identity information, not relevant for attaching event data to an incident.

Attach Data to Incident: This action is explicitly designed to attach additional data, such as event information, to an existing incident.

Conclusion:

The correct action to use in the playbook for filtering high severity events and attaching the event information to an incident is Attach Data to Incident .

Understanding the Threat Hunting Data :

The Threat Hunting Monitor in the provided exhibits shows various application services, their usage counts, and data metrics such as sent bytes, average sent bytes, and maximum sent bytes.

The second part of the exhibit lists connection attempts from a specific source IP (10.0.1.10) to a destination IP (8.8.8.8), with repeated " Connection Failed " messages.

Analyzing the Application Services :

DNS is the top application service with a significantly high count (251,400) and notable sent bytes (9.1 MB).

This large volume of DNS traffic is unusual for regular DNS queries and can indicate the presence of DNS tunneling.

DNS Tunneling :

DNS tunneling is a technique used by attackers to bypass security controls by encoding data within DNS queries and responses. This allows them to extract data from the local network without detection.

The high volume of DNS traffic, combined with the detailed metrics, suggests that DNS tunneling might be in use.

Connection Failures to 8.8.8.8 :

The repeated connection attempts from the source IP (10.0.1.10) to the destination IP (8.8.8.8) with connection failures can indicate an attempt to communicate with an external server.

Google DNS (8.8.8.8) is often used for DNS tunneling due to its reliability and global reach.

Conclusion :

Given the significant DNS traffic and the nature of the connection attempts, it is reasonable to conclude that DNS tunneling is being used to extract confidential data from the local network.

Why Other Options are Less Likely :

Spearphishing (A) : There is no evidence from the provided data that points to spearphishing attempts, such as email logs or phishing indicators.

Reconnaissance (C) : The data does not indicate typical reconnaissance activities, such as scanning or probing mail servers.

FTP C & C (D) : There is no evidence of FTP traffic or command-and-control communications using FTP in the provided data.

Understanding the Requirements :

The objective is to create an incident and generate a report based on malicious attachment events detected by FortiAnalyzer from FortiSandbox analysis.

The endpoint hosts are protected by FortiClient EMS, which is integrated with FortiSandbox. All logs are sent to FortiAnalyzer.

Key Components :

FortiAnalyzer : Centralized logging and analysis for Fortinet devices.

FortiSandbox : Advanced threat protection system that analyzes suspicious files and URLs.

FortiClient EMS : Endpoint management system that integrates with FortiSandbox for endpoint protection.

Playbook Analysis :

The playbook in the exhibit consists of three main actions: GET_EVENTS, RUN_REPORT, and CREATE_INCIDENT.

EVENT_TRIGGER : Starts the playbook when an event occurs.

GET_EVENTS : Fetches relevant events.

RUN_REPORT : Generates a report based on the events.

CREATE_INCIDENT : Creates an incident in the incident management system.

Selecting the Correct Connector :

The correct connector should allow fetching events related to malicious attachments analyzed by FortiSandbox and facilitate integration with FortiAnalyzer.

Connector Options :

FortiSandbox Connector :

Directly integrates with FortiSandbox to fetch analysis results and events related to malicious attachments.

Best suited for getting detailed sandbox analysis results.

Selected as it is directly related to the requirement of handling FortiSandbox analysis events.

FortiClient EMS Connector :

Used for managing endpoint security and integrating with endpoint logs.

Not directly related to fetching sandbox analysis events.

Not selected as it is not directly related to the sandbox analysis events.

FortiMail Connector :

Used for email security and handling email-related logs and events.

Not applicable for sandbox analysis events.

Not selected as it does not relate to the sandbox analysis.

Local Connector :

Handles local events within FortiAnalyzer itself.

Might not be specific enough for fetching detailed sandbox analysis results.

Not selected as it may not provide the required integration with FortiSandbox.

Implementation Steps :

Step 1 : Ensure FortiSandbox is configured to send analysis results to FortiAnalyzer.

Step 2 : Use the FortiSandbox connector in the playbook to fetch events related to malicious attachments.

Step 3 : Configure the GET_EVENTS action to use the FortiSandbox connector.

Step 4 : Set up the RUN_REPORT and CREATE_INCIDENT actions based on the fetched events.

NIST Cybersecurity Framework Overview :

The NIST Cybersecurity Framework provides a structured approach for managing and mitigating cybersecurity risks. Incident handling is divided into several phases to systematically address and resolve incidents.

Incident Handling Phases :

Preparation : Establishing and maintaining an incident response capability.

Detection and Analysis : Identifying and investigating suspicious activities to confirm an incident.

Containment, Eradication, and Recovery :

Containment: Limiting the impact of the incident.

Eradication: Removing the root cause of the incident.

Recovery: Restoring systems to normal operation.

Containment Phase :

The primary goal of the containment phase is to prevent the incident from spreading and causing further damage.

Quarantining a Compromised Host :

Quarantining involves isolating the compromised host from the rest of the network to prevent adversaries from moving laterally and causing more harm.

Techniques include network segmentation, disabling network interfaces, and applying access controls.

Exact Extract: “The Pyramid of Pain illustrates why focusing on adversary TTPs is important: They are the most descriptive IOCs of a given adversary and the toughest for threat actors to change.” The guide ranks Domain Names as “Simple” and IP Addresses as “Easy,” while TTPs are “Tough.”

Exact Extract: “As you progress from the top of the pyramid to the bottom, the disruption of an element becomes easier for the adversary to recover from… once those IP addresses start to be widely recognized as malicious and potentially blocked, it is easy for the attacker to start using other IP addresses.”

The correct answers are C and D . Blocking IP addresses and domains is useful, but it targets low-level observable indicators, not the adversary’s deeper behavior. In the Pyramid of Pain, IP addresses and domain names sit near the bottom because attackers can replace them quickly by rotating infrastructure, registering new domains, using compromised hosts, or changing hosting providers. Therefore, this approach focuses on network indicators and creates only limited disruption.

Option A is too strong. IPs and domains may reveal infrastructure, but blocking them does not necessarily identify strategic weaknesses in the adversary’s operation. Option B is wrong because high operational cost is associated with forcing adversaries to change tools or TTPs, not merely rotating IPs and domains.

Technical Deep Dive: In a Fortinet SOC, blocking phishing IPs/domains can be automated through FortiSOAR playbooks using FortiGate address objects, DNS filtering, FortiMail blocklists, or FortiGuard threat intelligence enrichment. That is good hygiene, but it is reactive. Higher-value hunting looks for reusable phishing tradecraft: lure themes, sender infrastructure patterns, attachment behaviors, command-and-control sequence, credential collection workflow, and post-compromise TTPs. ASIC offloading is not the key issue here; the security value comes from intelligence quality and detection depth, not packet acceleration.