Fortinet NSE7_SOC_AR-7.6 - Fortinet NSE 7 - Security Operations 7.6 Architect

Comprehensive and Detailed Explanation From FortiSOAR 7.6., FortiSIEM 7.3 Exact Extract study guide:

To establish a successful integration betweenFortiSOAR 7.6and aFortiGatefirewall via the FortiGate connector, specific administrative and network requirements must be met on the FortiGate side:

API Administrator and Key (D):FortiSOAR does not use standard UI login credentials. Instead, it requires aREST API Administratoraccount to be created on the FortiGate. This account must be assigned an administrative profile with the necessary permissions (e.g., Read/Write for Firewall policies or Address objects). Upon creation, the FortiGate generates a uniqueAPI Key, which must be entered into the "API Key" field of the FortiSOAR configuration wizard as shown in the exhibit.

HTTPS Management Access (C):The connector communicates with the FortiGate using REST API calls overHTTPS(port 443 by default). Therefore, the physical or logical interface on the FortiGate that corresponds to the "Hostname" IP (172.16.200.1) must haveHTTPSenabled under "Administrative Access" in its network settings. If HTTPS is disabled, the connection will time out or be refused.

Why other options are incorrect:

Trusted hosts (A):While it is a best practice to restrict API access to specific IPs (like the FortiSOAR IP), the integration can technically function without "Trusted hosts" enabled if the network allows the traffic. However, theabsenceof an API key or HTTPS access will definitively cause a failure regardless of trusted host settings.

VDOM name (B):In the exhibit, the VDOM field contains multiple values ("VDOM_1", "VDOM_2"). If VDOMs are disabled on the FortiGate, this field should generally be left blank or set to the default "root." Setting it specifically to "VDOM_1" when VDOMs are disabled is not a universal requirement for connectivity; the primary handshake depends on the API key and HTTPS connectivity.

Comprehensive and Detailed Explanation From FortiSOAR 7.6., FortiSIEM 7.3 Exact Extract study guide:

Based on the official documentation forFortiSIEM 7.3(which utilizes the MITRE ATT&CK mapping for incident correlation) andFortiSOAR 7.6(which uses these tactics for incident classification and playbook triggering):

Reconnaissance (Tactic TA0043):This tactic consists of techniques that involve adversaries actively or passively gathering information that can be used to support targeting. In this scenario, the attacker identifies "employee names, roles, and email patterns from public press releases." This is categorized underGather Victim Org Information (T1591)andSearch Open Technical Databases (T1596). Since this activity happens prior to the compromise and involves gathering intelligence, it is strictly Reconnaissance.

Initial Access (Tactic TA0001):This tactic covers techniques that use various entry vectors to gain an initial foothold within a network. The act of sending "tailored emails... to recipients to review an attached agenda using a link" is the definition ofPhishing: Spearphishing Link (T1566.002). This is the specific delivery mechanism used to gain the initial entry.

Why other options are incorrect:

Discovery (B):This tactic involves techniques an adversary uses to gain knowledge about the internal network after they have already gained access. Since the attacker is looking at public press releases, they are operating outside the perimeter.

Defense Evasion (D):This tactic consists of techniques that adversaries use to avoid detection throughout their compromise. While using an external link might bypass some basic reputation filters, the primary goal described in the report is the act of establishing contact and access, which is the core of the Initial Access tactic.

Overview of Indicators of Compromise (IoCs): Indicators of Compromise (IoCs) are pieces of evidence that suggest a system may have been compromised. These can include unusual network traffic patterns, the presence of known malicious files, or other suspicious activities.

FortiAnalyzer's Role: FortiAnalyzer aggregates logs from various Fortinet devices to provide comprehensive visibility and analysis of network events. It uses these logs to identify potential IoCs and compromised hosts.

Relevant Log Types:

DNS Filter Logs:

DNS requests are a common vector for malware communication. Analyzing DNS filter logs helps in identifying suspicious domain queries, which can indicate malware attempting to communicate with command and control (C2) servers.

Understanding the Playbook Configuration:

The playbook named "Update Asset and Identity Database" is designed to update the FortiAnalyzer Asset and Identity database with endpoint and user information.

The exhibit shows the playbook with three main components: ON_SCHEDULE STARTER, GET_ENDPOINTS, and UPDATE_ASSET_AND_IDENTITY.

Analyzing the Components:

ON_SCHEDULE STARTER:This component indicates that the playbook is triggered on a schedule, not on-demand.

GET_ENDPOINTS:This action retrieves information about endpoints, suggesting it interacts with an endpoint management system.

UPDATE_ASSET_AND_IDENTITY:This action updates the FortiAnalyzer Asset and Identity database with the retrieved information.

Evaluating the Options:

Option A:The actions shown in the playbook are standard local actions that can be executed by the FortiAnalyzer, indicating the use of a local connector.

Option B:There is no indication that the playbook uses a FortiMail connector, as the tasks involve endpoint and identity management, not email.

Option C:The playbook is using an "ON_SCHEDULE" trigger, which contradicts the description of an on-demand trigger.

Option D:The action "GET_ENDPOINTS" suggests integration with an endpoint management system, likely FortiClient EMS, which manages endpoints and retrieves information from them.

Conclusion:

The playbook is configured to use a local connector for its actions.

It interacts with FortiClient EMS to get endpoint information and update the FortiAnalyzer Asset and Identity database.

Comprehensive and Detailed Explanation From FortiSOAR 7.6., FortiSIEM 7.3 Exact Extract study guide:

InFortiSOAR 7.6, manual playbooks appear in theExecutemenu of a record only if they meet specific configuration criteria defined in theManual Triggerstep:

Module Scope (C):When creating a playbook with a manual trigger, the administrator must explicitly select which modules (e.g., Alerts, Incidents, Indicators) can execute the playbook. If theAlertsmodule is not selected in the "Applicable Modules" section of the trigger configuration, the playbook will remain hidden from the Execute menu when an analyst is viewing the Alerts module.

Trigger Execution Requirements (D):Manual triggers can be configured to execute onno records, asingle record, ormultiple records. If a playbook is configured with the "Requires record input to run" setting but is specifically restricted to a different input type (or if there is a mismatch in the selection logic), it will not appear in the menu unless the correct number of records are selected. Furthermore, if a playbook is designed to run only whennorecord is selected (global utility), it will not show up in the context-sensitive menu of a specific record.

Why other options are incorrect:

Publishing (A):FortiSOAR playbooks do not require a separate "publishing" step via an Application Editor to become visible. Once they aresavedandactive(toggled on), they are immediately available for use based on their trigger settings.

Concurrent Execution (B):FortiSOAR allows multiple instances of the same playbook to run simultaneously. An active execution of a playbook does not hide it from the menu for other analysts or subsequent runs.

Understanding the Playbook Configuration:

The playbook "FortiMail Sender Blocklist" is designed to manually input email addresses or IP addresses and add them to the FortiMail block list.

The playbook uses a FortiMail connector with the action ADD_SENDER_TO_BLOCKLIST.

Analyzing the Playbook Execution:

The configuration and actions provided show that the playbook is straightforward, starting with an ON_DEMAND STARTER and proceeding to the ADD_SENDER_TO_BLOCKLIST action.

The action description indicates it is intended to block senders based on email addresses or domains.

Evaluating the Options:

Option A:Using GET_EMAIL_STATISTICS is not required for the task of adding senders to a block list. This action retrieves email statistics and is unrelated to the block list configuration.

Option B:The primary reason for failure could be the requirement for a fully qualified domain name (FQDN). FortiMail typically expects precise information to ensure the correct entries are added to the block list.

Option C:The trust level of the client-side browser with FortiAnalyzer's self-signed certificate does not impact the execution of the playbook on FortiMail.

Option D:Incorrect connector credentials would result in an authentication error, but the problem described is more likely related to the format of the input data.

Conclusion:

The FortiMail Sender Blocklist playbook execution is failing because FortiMail is expecting a fully qualified domain name (FQDN).

Role of a Threat Hunter:

A threat hunter proactively searches for cyber threats that have evaded traditional security defenses. This role is crucial in identifying sophisticated and stealthy adversaries that bypass automated detection systems.

Key Responsibilities:

Proactive Threat Identification:

Threat hunters use advanced tools and techniques to identify hidden threats within the network. This includes analyzing anomalies, investigating unusual behaviors, and utilizing threat intelligence.