Question 860
For the response to an incident affecting host-208, north Finance wants to customize a validated remediation script for quarantine a suspicious connection on a Linux server. Where are built-in and user-created remediation resources maintained?
- Only the Analytics Group By editor
- The Incident Resolution dropdown
- Resources > Remediations
- The CMDB user alias table
Explanation
Correct Answer
C:Considering remediation operation at the SOC for host-208: FortiSIEM includes remediation scripts in its Resources area and supports creating new remediation definitions there. A vetted script can be selected for later incident execution.
Incorrect Answers
A:In remediation operation at the SOC for host-208: The search editor aggregates event data, not the stored script resource used to enforce quarantine a suspicious connection.
B:For remediation operation at the SOC for host-208: Resolution captures true/false positive verdicts rather than the script body and execution parameters for Linux server.
D:Under remediation operation at the SOC for host-208: User aliases help identity/risk relationships and are not the library where management-device remediation scripts are defined.
Question 861
For Corporate HQ, an analyst must choose where a FortiSIEM ML job executes. Which pair of modes separates local execution from an AWS-backed execution option?
- CMDB and Incident Resolution modes
- Local and AWS machine-learning run modes
- Real-time Group By and Nested Lookup modes
- Email and SMS aggregation modes
Explanation
Correct Answer
B:FortiSIEM provides run-mode selections such as Local or AWS, with Auto variants. They determine execution location and automation characteristics for the nightly database write rate task.
Incorrect Answers
A:In machine-learning analysis at Corporate HQ: CMDB inventory and incident verdict fields are not the documented run-mode choices for executing machine-learning work.
C:Considering machine-learning analysis at Corporate HQ: These are analytics search features, not the named local-versus-cloud execution modes for a FortiSIEM ML job.
D:Under machine-learning analysis at Corporate HQ: Email and SMS are notification transports; neither selects local or AWS compute for the learner.
Question 862
Research imported a new maintenance state row into lookup table KnownScanners and immediately tested a rule, but the result still resembles the old table. No schema problem is present. What timing effect should be considered?
- Allow for the documented lookup-data propagation interval before retesting
- Assume a newly imported row permanently disables the correlation rule
- Delete every event from the historical database before retrying
- Change the FortiGate interface IP to force a CMDB rescan
Explanation
Correct Answer
A:In CMDB and lookup-table configuration at Research: Changes propagate through Supervisor/Worker Redis and are periodically reread by analytics. In FortiSIEM 7.2 this can take about 5–10 minutes, so an immediate rule result may be stale.
Incorrect Answers
B:For CMDB and lookup-table configuration at Research: Lookup updates do not by themselves disable a rule. A delay while the new maintenance state entry reaches analytics is a more consistent explanation.
C:Event deletion is not needed to refresh a lookup table and would destroy useful blocked request evidence for Research.
D:Under CMDB and lookup-table configuration at Research: An unrelated network address change does not accelerate lookup-table refresh on FortiSIEM analytics nodes.
Question 863
The City Branch administrator is editing a scheduled rule and wants to use Original Rule Does Not Trigger as a clear condition for rejected request. Why is a different approach required?
- That clear-condition option is not selectable for scheduled rules
- Notification policies are mandatory before any scheduled rule can save
- Scheduled rules have no concept of incidents
- All saved reports become invalid after a scheduled search
Explanation
Correct Answer
A:In rule deployment or exception at City Branch: FortiSIEM documents the Original Rule Does Not Trigger condition as unavailable for scheduled rules. A suitable explicit clear subpattern or lifecycle design is needed instead.
Incorrect Answers
B:For the requested clear condition for rejected request: For rule deployment or exception at City Branch: Rule incident definition is required, while alert routing is a separate automation task; it is not the reason this clear option is unavailable.
C:Considering rule deployment or exception at City Branch: Scheduled rules can generate incidents, so the issue is the specific clear method rather than an absence of incident output.
D:For the requested clear condition for rejected request: Under rule deployment or exception at City Branch: Report persistence has no direct bearing on the rule’s restricted Original Rule Does Not Trigger clear option.
Question 864
East Retail has six weeks of numeric hourly failed sign-ins for host-33 but no manually labeled malicious examples. The team wants to flag unusual future values. Which ML task fits best?
- A static CMDB lookup as the only analysis
- Supervised classification requiring known class labels
- Anomaly detection trained on the historical numeric behavior
- An event export with no model training
Explanation
Correct Answer
C:Anomaly detection can model a numeric baseline for hourly failed sign-ins without requiring preassigned malicious/benign labels. The analyst should verify seasonality and expected variance before treating flags as incidents.
Incorrect Answers
A:Inventory lookup resolves asset attributes, not statistical outliers in six weeks of hourly failed sign-ins telemetry for host-33.
B:Classification expects meaningful known labels for training. East Retail has only unlabeled behavior, so that prerequisite is not met in this case.
D:Exporting records preserves evidence but does not learn the baseline or infer whether new hourly failed sign-ins values are anomalous.
Question 865
Manufacturing knows a legitimate scheduled scanner will produce suspicious launch events on host-195 during a maintenance window. The detection should remain active for all other assets and times. Which rule feature targets the exception?
- Change the incident severity to low with no exception
- Disable the entire rule permanently
- Delete the parser for the log source
- A rule exception constrained by relevant attributes and an effective period
Explanation
Correct Answer
D:Rule exceptions suppress incidents for matching host-195 conditions during a defined single or recurring interval, preserving detection elsewhere.
Incorrect Answers
A:In correlation-rule investigation at Manufacturing for host-195: Lowering priority still creates incidents for the expected scan and does not delimit the approved maintenance period.
B:Global disablement discards all suspicious launch detections beyond the approved host-195 maintenance exception.
C:Considering correlation-rule investigation at Manufacturing for host-195: Removing event parsing would harm all observations from endpoint process alerts and is not a precise, time-bound exception.
Question 866
After opening one connection event from network flow records, an investigator wants other events having the same Source IP on host-36, not merely lines containing its spelling. How should the query be narrowed?
- Query CMDB for every inventoried asset instead of events
- Use only a free-text keyword extracted from the raw event
- Group all events by their ingestion minute
- Filter on the parsed Source IP event attribute with the exact value
Explanation
Correct Answer
D:A structured Event Attribute condition compares the normalized Source IP field, avoiding accidental text matches in unrelated portions of network flow records.
Incorrect Answers
A:CMDB can enrich host identity, yet it is not the normalized network flow records search that finds events sharing Source IP.
B:Keyword matching can find the same characters in messages that have a different parsed Source IP, weakening entity identity for host-36.
C:Considering historical or real-time event analysis at the SOC for host-36 using network flow records: Grouping by minute changes output granularity but does not enforce equality on Source IP for the related-event investigation.
Question 867
A security engineer is designing table MaintenanceExclusions at West Operations. The maintenance state field stores decimal scores. Which available lookup-table field type should be chosen?
- LONG
- DOUBLE
- BOOLEAN
- STRING
Explanation
Correct Answer
B:DOUBLE represents real-valued numbers, such as fractional maintenance state scores; it is unsuitable for arbitrary text or exact integer-only identifiers when LONG is intended.
Incorrect Answers
A:LONG represents integer values. It fits whole-number maintenance state identifiers but not free text or decimal fractions.
C:Considering CMDB and lookup-table configuration at West Operations: BOOLEAN is not one of the schema field types offered in the FortiSIEM 7.2 lookup table editor, which provides STRING, LONG, and DOUBLE.
D:STRING holds character data. It is suitable for textual maintenance state labels and avoids inappropriate numeric operations on identity values.
Question 868
A City Branch policy is configured to create cases automatically for sign-in incidents. Case creation remains unavailable in the policy editor. What prerequisite should be checked?
- Every host has an arbitrary text tag named case
- The rule has zero incident definitions
- A real-time Group By was enabled for the incident search
- Analyst Team and Case Management Policy are configured, and the action is at a supported scope
Explanation
Correct Answer
D:For A City Branch policy is configured to create cases automatically for sign-in incidents. Case creation remains unavailable in: Under Automation Policy workflow at City Branch: FortiSIEM 7.2 automated case creation requires analyst teams and case policy configuration and is not available at the organization level. Those prerequisites govern this option.
Incorrect Answers
A:For A City Branch policy is configured to create cases automatically for sign-in incidents. Case creation remains unavailable in: In Automation Policy workflow at City Branch: Host tags do not establish the required analyst team/assignment policy objects for case creation in City Branch.
B:For A City Branch policy is configured to create cases automatically for sign-in incidents. Case creation remains unavailable in: For Automation Policy workflow at City Branch: A valid incident-generating rule needs a defined incident; an empty definition would block rule save but does not establish case team configuration.
C:For A City Branch policy is configured to create cases automatically for sign-in incidents. Case creation remains unavailable in: Considering Automation Policy workflow at City Branch: Real-time Group By is unsupported and cannot register case management teams or resolve the policy editor prerequisite.
Question 869
An analyst at Corporate HQ determines a unauthorized change event is more urgent than its assigned severity suggests. Which incident action updates prioritization without changing the original matching rule logic?
- Change Severity for the selected incident
- Delete the {kind} event parser from its source
- Remove every active rule in the tenant
- Change the historical report time range
Explanation
Correct Answer
A:Incident List View includes a severity-change action. Raising urgency on this host-206 finding affects the current triage priority without rewriting the correlation filter.
Incorrect Answers
B:For correlation-rule investigation at Corporate HQ: Deleting normalization would affect future telemetry broadly and is unrelated to correcting urgency of one reviewed incident.
C:Considering correlation-rule investigation at Corporate HQ: Global rule removal is disproportionate and would destroy alerting coverage unrelated to the current severity adjustment.
D:Under correlation-rule investigation at Corporate HQ: Search interval changes which evidence is displayed but does not change the selected incident’s severity classification.
Question 870
The Logistics investigation tracks two events in SSH audit logs: a denied login P1 followed by a successful login P2. The rule is incorrectly matching different users. Which inter-subpattern constraint should be added?
- Removal of all grouping keys and inter-subpattern constraints
- A greater-than test between the two event message lengths
- Equality between the relevant Source IP identity attributes of P1 and P2
- Only a larger incident title text field
Explanation
Correct Answer
C:Considering subpattern correlation at Logistics using SSH audit logs: Inter-subpattern comparisons link matching entity keys across both behaviors. Requiring the same Source IP prevents a different user’s P2 from completing this sequence.
Incorrect Answers
A:Eliminating identity comparison makes cross-user false matches more likely in Logistics, not less.
B:For subpattern correlation at Logistics using SSH audit logs: Message length does not establish user or entity identity for the P1–P2 correlation.
D:Under subpattern correlation at Logistics using SSH audit logs: Title length affects labeling and cannot prevent a P2 from another Source IP being joined to the first event.