Free Practice Questions for Fortinet NSE7_SOC_AR-7.6 Exam

Understanding the MITRE ATT & CK Tactics:

The MITRE ATT & CK framework categorizes various tactics and techniques used by adversaries to achieve their objectives.

Tactics represent the objectives of an attack, while techniques represent how those objectives are achieved.

Analyzing the Incident Report:

Phishing Email Campaign: This tactic is commonly used for gaining initial access to a system.

Malicious Link and RAT Download: Clicking a malicious link and downloading a RAT is indicative of establishing initial access.

Remote Access Trojan (RAT): Once installed, the RAT allows attackers to maintain access over an extended period, which is a persistence tactic.

Mapping to MITRE ATT & CK Tactics:

Initial Access:

This tactic covers techniques used to gain an initial foothold within a network.

Techniques include phishing and exploiting external remote services.

The phishing campaign and malicious link click fit this category.

Persistence:

This tactic includes methods that adversaries use to maintain their foothold.

Techniques include installing malware that can survive reboots and persist on the system.

The RAT provides persistent remote access, fitting this tactic.

Exclusions:

Defense Evasion:

This involves techniques to avoid detection and evade defenses.

While potentially relevant in a broader context, the incident report does not specifically describe actions taken to evade defenses.

Lateral Movement:

This involves moving through the network to other systems.

The report does not indicate actions beyond initial access and maintaining that access.

Conclusion:

The incident report captures the tactics of Initial Access and Persistence.

Exact Extract: “Custom API Endpoint: Specify an arbitrary endpoint used to externally start a playbook. Uses a REST API POST action from another system. Supports token-based, basic, and no authentication.”

The correct answers are A and D. A Custom API Endpoint trigger allows an external system to start a FortiSOAR playbook through a defined arbitrary endpoint. It supports token-based authentication, basic authentication, or no authentication, depending on how you configure the trigger. C is wrong because the guide specifies REST API POST, not GET and PUT. B is not supported by the described trigger behavior; the endpoint is configured as a trigger for a playbook, not as a broadcast mechanism to trigger multiple playbooks simultaneously.

Technical Deep Dive: This trigger is useful when an external system cannot use a native FortiSOAR connector but can make an HTTP API call. Common use cases include webhook-style ingestion, third-party alert forwarding, and external workflow integration. Secure it properly; “no authentication” is possible but usually unacceptable in production unless protected by network controls.

Exact Extract: “The first step in creating a queue occurs on the Queue Definition page, where you define a name and description, and specify the modules that you want to associate with the queue… Note that for the module to be selectable under Module Types, you must enable the Queueable setting under Application Editor > Modules.”

The correct answer is A because FortiSOAR only allows a module to appear in the queue Module Types list when that module has the Queueable setting enabled under Application Editor > Modules. The issue is not the task priority or queue priority. A higher priority queue only affects tie-breaking when multiple queues match the same record criteria; it does not prevent a module from being selected. The Tasks module can be used as a FortiSOAR record module, so C is not the best answer. Shift-based assignment is also separate: it controls whether assignment follows shift availability after the queue exists, but it does not control whether the module appears in the Module Types list.

Technical Deep Dive: Queue and shift management is metadata-driven. First, the module must be queue-enabled. Then queue rules can match records, such as newly created low-priority tasks. After that, user assignment logic can assign records to the queue lead, leave them unassigned, or distribute them by round robin, optionally using shift-based availability. So the first fix is: Application Editor > Modules > Tasks > enable Queueable.

Step 1: FortiSIEM event log

Step 2: FortiSIEM incident

Step 3: FortiSOAR alert

Step 4: FortiSOAR incident

Exact Extract: “FortiSIEM: Event: An event refers to a single log or data point collected from a monitored device. It’s the most basic unit of information received by FortiSIEM, such as a firewall log or a system alert.” The guide also states: “Incident: An incident in FortiSIEM is created when a correlation rule is triggered.”

Exact Extract: “This slide explains how to map fields between FortiSIEM incidents and FortiSOAR alerts during the ingestion process. Use the wizard to define how FortiSIEM data populates FortiSOAR alert fields.”

Exact Extract: “FortiSOAR ingests FortiSIEM incidents as alerts… If the alert is not a valid threat, then the analyst can close it as a false positive. Otherwise, the analyst can open an incident.”

The correct sequence is FortiSIEM event log → FortiSIEM incident → FortiSOAR alert → FortiSOAR incident. FortiSIEM first receives raw event logs from monitored devices. If those events match a correlation rule, FortiSIEM creates a FortiSIEM incident. The FortiSOAR default data ingestion wizard then ingests FortiSIEM incidents into FortiSOAR as alerts, not as FortiSOAR incidents directly. After triage and validation, the analyst or playbook can escalate the alert into a FortiSOAR incident.

Technical Deep Dive: FortiSIEM and FortiSOAR use different object models. FortiSIEM “incident” means a correlation result from event analytics. FortiSOAR “alert” is the first SOAR-side record created from that SIEM incident. FortiSOAR “incident” is a higher-level case-management container used after validation. This separation is intentional: not every SIEM incident deserves full incident-response handling. FortiGate NP/CP offloading is irrelevant because this workflow is log ingestion and case orchestration, not firewall packet acceleration.

The correct answer is A. FortiSOAR Queue and Shift Management provides automated assignment of records to SOC analysts using queue membership and shift availability.

According to the study guide, the User Assignment configuration supports Leave Unassigned, Assign to Queue Lead, and Round Robin. Round Robin distributes records sequentially among queue members and restarts from the first member after reaching the last.

However, this standard distribution does not inherently restrict assignments to analysts currently working.

To enforce shift-aware routing, the administrator must enable shift-based assignment. FortiSOAR can then consider the active shift schedule when assigning incoming alerts.

The Queueable setting controls whether the module can participate in queue management. Automatic shift handover is a separate capability, and conflicting queue rules are not indicated by this behavior.

In FortiSOAR 7.6, the War Room is a collaborative space designed for high-priority incident investigation. The Evidences tab within the Investigate view (as shown in the exhibit) is specifically designed to highlight critical findings found during the investigation process.

Evidence Tagging: To populate the Action Logs Marked As Evidence section, an analyst must specifically tag a relevant log entry, a playbook output, or a comment within the collaboration workspace with the system-defined keyword " Evidence " .

Automatic Categorization: Once the tag is applied, FortiSOAR automatically parses these entries and displays them in this centralized view. This allows team members and stakeholders to quickly view substantiated facts and proof gathered during the " Root Cause Analysis " phase without sifting through all raw action logs.

Manual vs. Action Logs: The exhibit shows two distinct areas: " Manually Upload Evidences " (where files like the CSLAB document shown can be dragged and dropped) and " Action Logs Marked As Evidence. " The latter is reserved exclusively for system-generated logs or comments that have been promoted to evidence status via tagging.

Why other options are incorrect:

By linking an indicator to the war room (B): Linking indicators associates technical artifacts (like IPs or hashes) with the record, but it does not automatically classify them as evidence within the War Room action log view.

By creating an evidence collection task and attaching a file (C): While this is a valid step in an investigation, attaching a file to a task typically places it in the " Attachments " or " Manually Upload Evidences " area, rather than the " Action Logs " section specifically.

By executing a playbook with the Save Execution Logs option enabled (D): Saving execution logs ensures a trail of what the playbook did, but it does not mark the output as " Evidence " unless the specific logic or a manual analyst action applies the " Evidence " tag to the resulting log entry.

According to the FortiAnalyzer 7.4 SOC Analyst official training material (Lesson 5: Automation) and supporting documentation for FortiSOAR 7.6 and FortiSIEM 7.3 integration, the following best practices are recommended for playbook portability:

Disable playbooks before exporting (A): When a playbook is exported, its current status (Enabled or Disabled) is preserved in the export file. If an Enabled playbook is imported into a destination ADOM where its trigger conditions are immediately met, it will start executing automatically. Disabling the playbook before export is a critical best practice to prevent unintended automated actions from occurring in the new environment before the analyst has had a chance to verify local configurations.

Include the associated connector settings (B): FortiAnalyzer allows you to include required connector configurations during the export process. By selecting this option, the exported file includes the necessary metadata and configurations for the connectors that the playbook relies on to execute its tasks. This ensures the playbook remains functional and portable across different FortiAnalyzer units or ADOMs without requiring the manual recreation of every connector.

Why other options are incorrect:

Move playbooks between ADOMs (C): There is no native " Move " function for automation playbooks between ADOMs in the same sense as moving a device. The standard supported workflow for transferring automation logic is the Export and Import process.

Ensure names do not exist in target (D): While maintaining unique names is good practice, it is not a required " best practice " for the export process itself because FortiAnalyzer automatically handles name conflicts. If an imported playbook shares a name with an existing one, the system automatically appends a timestamp to the new playbook ' s name to avoid a conflict.

Understanding the FortiAnalyzer Fabric:

The FortiAnalyzer Fabric provides centralized log collection, analysis, and reporting for connected FortiGate devices.

Devices in a FortiAnalyzer Fabric can be organized into different Administrative Domains (ADOMs) to separate logs and management.

Analyzing the Exhibit:

FAZ-SiteA and FAZ-SiteB are FortiAnalyzer devices in the fabric.

FortiGate-B1 and FortiGate-B2 are shown under the Site-B-Fabric, indicating they are part of the same Security Fabric.

FAZ-SiteA has multiple entries under it: SiteA and MSSP-Local, suggesting multiple ADOMs are enabled.

Evaluating the Options:

Option A: FortiGate-B1 and FortiGate-B2 are under Site-B-Fabric, indicating they are indeed part of the same Security Fabric.

Option B: The presence of FAZ-SiteA and FAZ-SiteB as FortiAnalyzers does not preclude the existence of collectors. However, there is no explicit mention of a separate collector role in the exhibit.

Option C: Not all FortiGate devices are directly registered to the supervisor. The exhibit shows hierarchical organization under different sites and ADOMs.

Option D: The multiple entries under FAZ-SiteA (SiteA and MSSP-Local) indicate that FAZ-SiteA has two ADOMs enabled.

Conclusion:

FortiGate-B1 and FortiGate-B2 are in a Security Fabric.

FAZ-SiteA has two ADOMs enabled.

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.

Exact Extract: “You can investigate the war room by executing connector actions directly on the war room record. In the example shown on this slide, a Get Domain Reputation action was directly run with the VirusTotal connector on this record. You can select only relevant checkboxes or select Key to select all outputs.”

The correct answer is A. When running a connector action directly from the war room, FortiSOAR lets you choose which returned output keys to save. That is the correct way to limit what gets attached to the war room. B is wrong because a workspace filter affects display/collaboration, not what connector output is saved. C is incomplete; the Investigate tab is where you run the investigation, but the specific control is selecting output keys. D is wrong because playbook logging level does not control war room evidence attachment size.

Technical Deep Dive: War rooms are designed for focused collaboration during major incident response. Dumping full connector output into the record creates noise and slows review. Select only analyst-useful keys such as reputation score, category, detections, registrar, resolved IPs, or last analysis summary. This preserves evidence quality without flooding the team.