Fortinet FCP_FAZ_AN-7.6 Questions & Answers

This safeguard, “Pair volume widgets with collection-health indicators for operational decisions”, reduces a different source-defined risk: After a logging outage, FortiView reports a sudden reduction in sessions and managers call it successful traffic reduction. That risk depends on: An ingestion gap can make traffic summaries fall even if actual network activity remains constant. The recurring problem here is a firewall change is suspected of increasing traffic through policy 41, and the team wants policy-specific evidence rather than a network-wide bandwidth total. The originally selected control “Check policy-specific traffic baselines after major rule changes” is more specific because policy-focused aggregation reveals which rules handle observed sessions and bytes.

This safeguard, “Verify source telemetry prerequisites for every new dashboard widget”, reduces a different source-defined risk: A FortiView widget displaying top attack categories is empty because the connected FortiGate forwards only basic traffic logs, not security-profile events. That risk depends on: Threat widgets require eligible threat/security log data; ordinary traffic logs need not contain IPS or antivirus detections. The recurring problem here is a firewall change is suspected of increasing traffic through policy 41, and the team wants policy-specific evidence rather than a network-wide bandwidth total. The originally selected control “Check policy-specific traffic baselines after major rule changes” is more specific because policy-focused aggregation reveals which rules handle observed sessions and bytes.

This safeguard, “Attach IoC supporting records before recommending endpoint quarantine”, reduces a different source-defined risk: An IoC monitor flags a suspicious host, but the analyst wants to see associated web-filter detections and threat ratings rather than treat the icon as conclusive. That risk depends on: A visual threat rating summarizes evidence; the underlying events are needed for incident-level conclusions. The recurring problem here is a firewall change is suspected of increasing traffic through policy 41, and the team wants policy-specific evidence rather than a network-wide bandwidth total. The originally selected control “Check policy-specific traffic baselines after major rule changes” is more specific because policy-focused aggregation reveals which rules handle observed sessions and bytes.

The action “Create a separate FortiView Custom View from a template or blank view and add only the needed widgets” addresses a separate source case: A custom FortiView dashboard is needed for an executive threat summary, but administrators overwrite the default threat view for all analysts. Its underlying reason is: Custom views preserve chosen dashboard widgets and filters without requiring changes to every predefined view. This question instead describes an analyst sees many threat alerts but needs to know the most frequently targeted servers rather than which detection signatures are globally common. The original answer “Review the FortiView Threats and Top Threat Destinations summaries with supporting source logs” targets that failure because threat-destination views aggregate the targets of security events, differing from signature-frequency charts.

The action “Confirm the active ADOM, selected device, and time filters match between the aggregate and detailed Log View” addresses a separate source case: A drill-down from a traffic dashboard seems to lead to unrelated sessions because the analyst changed ADOMs after the initial summary. Its underlying reason is: A drill-down is meaningful only when the same authorized data scope governs both summary and detail. This question instead describes an analyst sees many threat alerts but needs to know the most frequently targeted servers rather than which detection signatures are globally common. The original answer “Review the FortiView Threats and Top Threat Destinations summaries with supporting source logs” targets that failure because threat-destination views aggregate the targets of security events, differing from signature-frequency charts.

The action “Check the FortiSandbox detection action and associated delivery logs before treating the verdict as enforcement” addresses a separate source case: A FortiSandbox detections widget includes a malicious file but lists the action as Passthrough, and a responder assumes it must already have been blocked. Its underlying reason is: A malicious analysis verdict and the action applied to the file are separate recorded attributes. This question instead describes an analyst sees many threat alerts but needs to know the most frequently targeted servers rather than which detection signatures are globally common. The original answer “Review the FortiView Threats and Top Threat Destinations summaries with supporting source logs” targets that failure because threat-destination views aggregate the targets of security events, differing from signature-frequency charts.

The action “Dashboard layout controls presentation size and placement, not the underlying event aggregation” addresses a separate source case: A supervisor needs to compare the top five security threats and top affected destinations side by side, but a widget occupies nearly the entire dashboard. Its underlying reason is: Dashboard layout controls presentation size and placement, not the underlying event aggregation. This question instead describes an analyst sees many threat alerts but needs to know the most frequently targeted servers rather than which detection signatures are globally common. The original answer “Threat-destination views aggregate the targets of security events, differing from signature-frequency charts” targets that failure because threat-destination views aggregate the targets of security events, differing from signature-frequency charts.

The action “Application Control telemetry can group activity by detected application, not just network address” addresses a separate source case: An employee's laptop consumes unexpected bandwidth through a video-sharing application, but the SOC reports only the destination IP addresses. Its underlying reason is: Application Control telemetry can group activity by detected application, not just network address. This question instead describes an analyst sees many threat alerts but needs to know the most frequently targeted servers rather than which detection signatures are globally common. The original answer “Threat-destination views aggregate the targets of security events, differing from signature-frequency charts” targets that failure because threat-destination views aggregate the targets of security events, differing from signature-frequency charts.

The action “Threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event” addresses a separate source case: The FortiView Threat Map is blank even though internal-to-internal threats are present in logs, and the team concludes the feature is broken. Its underlying reason is: Threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event. This question instead describes an analyst sees many threat alerts but needs to know the most frequently targeted servers rather than which detection signatures are globally common. The original answer “Threat-destination views aggregate the targets of security events, differing from signature-frequency charts” targets that failure because threat-destination views aggregate the targets of security events, differing from signature-frequency charts.

The proposed observation “The changed policy shows the expected traffic trend and matching individual log records” would check a different original case: A firewall change is suspected of increasing traffic through policy 41, and the team wants policy-specific evidence rather than a network-wide bandwidth total. Its mechanism is: Policy-focused aggregation reveals which rules handle observed sessions and bytes. In the present case, an analyst sees many threat alerts but needs to know the most frequently targeted servers rather than which detection signatures are globally common; the more direct acceptance evidence is “The targeted server appears with its contributing detections and impact window” because threat-destination views aggregate the targets of security events, differing from signature-frequency charts.

The proposed observation “The candidate host's suspicious web destinations and matched indicators appear with timestamps” would check a different original case: An IoC monitor flags a suspicious host, but the analyst wants to see associated web-filter detections and threat ratings rather than treat the icon as conclusive. Its mechanism is: A visual threat rating summarizes evidence; the underlying events are needed for incident-level conclusions. In the present case, an analyst sees many threat alerts but needs to know the most frequently targeted servers rather than which detection signatures are globally common; the more direct acceptance evidence is “The targeted server appears with its contributing detections and impact window” because threat-destination views aggregate the targets of security events, differing from signature-frequency charts.

The proposed observation “The destination's hourly spike is visible without conflating it with older events” would check a different original case: A threat dashboard ranks one destination highly, but an analyst needs to isolate whether the spike occurred in the previous hour or over the whole week. Its mechanism is: Time filtering changes which log samples contribute to an aggregate, so rankings can differ by investigation interval. In the present case, an analyst sees many threat alerts but needs to know the most frequently targeted servers rather than which detection signatures are globally common; the more direct acceptance evidence is “The targeted server appears with its contributing detections and impact window” because threat-destination views aggregate the targets of security events, differing from signature-frequency charts.

This safeguard, “Review Application Control log coverage when using application-based monitors”, reduces a different source-defined risk: An employee's laptop consumes unexpected bandwidth through a video-sharing application, but the SOC reports only the destination IP addresses. That risk depends on: Application Control telemetry can group activity by detected application, not just network address. The recurring problem here is an analyst sees many threat alerts but needs to know the most frequently targeted servers rather than which detection signatures are globally common. The originally selected control “Maintain critical-server inventories for high-priority threat-destination triage” is more specific because threat-destination views aggregate the targets of security events, differing from signature-frequency charts.

This safeguard, “Distinguish temporary investigative filters from persistent shared-view configuration”, reduces a different source-defined risk: Analysts want to narrow one FortiView chart to a single risky destination while leaving unrelated saved dashboard definitions unchanged. That risk depends on: Interactive filters refine the visible aggregation without necessarily modifying the original saved dashboard. The recurring problem here is an analyst sees many threat alerts but needs to know the most frequently targeted servers rather than which detection signatures are globally common. The originally selected control “Maintain critical-server inventories for high-priority threat-destination triage” is more specific because threat-destination views aggregate the targets of security events, differing from signature-frequency charts.

This safeguard, “Test stored custom-view scope whenever monitored devices are renamed or replaced”, reduces a different source-defined risk: A SOC needs to keep a stable dashboard showing one FortiGate cluster for morning handover, but the current widget resets to all devices on every visit. That risk depends on: Custom View can retain device selection, widget choices, and time period as a repeatable analysis workspace. The recurring problem here is an analyst sees many threat alerts but needs to know the most frequently targeted servers rather than which detection signatures are globally common. The originally selected control “Maintain critical-server inventories for high-priority threat-destination triage” is more specific because threat-destination views aggregate the targets of security events, differing from signature-frequency charts.

The action “Expand the FortiView time range to include the incident period and keep the source device filters consistent” addresses a separate source case: The SOC has a valid alert list, yet the FortiView Threats panel does not display yesterday's events after an administrator set the view to Last 15 minutes. Its underlying reason is: FortiView aggregates records only inside the selected interval; an event outside the window is not counted. This question instead describes the FortiView Threat Map is blank even though internal-to-internal threats are present in logs, and the team concludes the feature is broken. The original answer “Check the map's public-address and positive threat-score display conditions together with the selected filters” targets that failure because threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event.

The action “Enable and validate the required security-profile logging upstream rather than merely changing graph colors” addresses a separate source case: A FortiView widget displaying top attack categories is empty because the connected FortiGate forwards only basic traffic logs, not security-profile events. Its underlying reason is: Threat widgets require eligible threat/security log data; ordinary traffic logs need not contain IPS or antivirus detections. This question instead describes the FortiView Threat Map is blank even though internal-to-internal threats are present in logs, and the team concludes the feature is broken. The original answer “Check the map's public-address and positive threat-score display conditions together with the selected filters” targets that failure because threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event.

The action “Inspect FortiView Applications for the user or source and examine classified application usage” addresses a separate source case: An employee's laptop consumes unexpected bandwidth through a video-sharing application, but the SOC reports only the destination IP addresses. Its underlying reason is: Application Control telemetry can group activity by detected application, not just network address. This question instead describes the FortiView Threat Map is blank even though internal-to-internal threats are present in logs, and the team concludes the feature is broken. The original answer “Check the map's public-address and positive threat-score display conditions together with the selected filters” targets that failure because threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event.

The action “Website request counts can include blocked attempts; aggregation alone does not establish successful page delivery” addresses a separate source case: The SOC's Top Websites widget reports a blocked phishing domain as the most visited site, but executives infer that users successfully accessed it. Its underlying reason is: Website request counts can include blocked attempts; aggregation alone does not establish successful page delivery. This question instead describes the FortiView Threat Map is blank even though internal-to-internal threats are present in logs, and the team concludes the feature is broken. The original answer “Threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event” targets that failure because threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event.

The action “Different widget types summarize different security-profile streams; one traffic chart cannot substitute for DLP or sandbox analyses” addresses a separate source case: A custom FortiView view must combine malware detections and data-loss indicators, but the author uses only a general traffic-volume chart. Its underlying reason is: Different widget types summarize different security-profile streams; one traffic chart cannot substitute for DLP or sandbox analyses. This question instead describes the FortiView Threat Map is blank even though internal-to-internal threats are present in logs, and the team concludes the feature is broken. The original answer “Threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event” targets that failure because threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event.

The action “FortiView aggregates records only inside the selected interval; an event outside the window is not counted” addresses a separate source case: The SOC has a valid alert list, yet the FortiView Threats panel does not display yesterday's events after an administrator set the view to Last 15 minutes. Its underlying reason is: FortiView aggregates records only inside the selected interval; an event outside the window is not counted. This question instead describes the FortiView Threat Map is blank even though internal-to-internal threats are present in logs, and the team concludes the feature is broken. The original answer “Threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event” targets that failure because threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event.

The proposed observation “The top source list identifies the high-volume endpoint and underlying traffic logs corroborate its bytes” would check a different original case: FortiView displays a sharp rise in source traffic volume, but the analyst wants to identify which internal IPs produced the increase instead of guessing from applications. Its mechanism is: A source-oriented FortiView aggregation groups traffic by origin; application summaries answer a different question. In the present case, the FortiView Threat Map is blank even though internal-to-internal threats are present in logs, and the team concludes the feature is broken; the more direct acceptance evidence is “An eligible public-IP test detection appears while private-only records remain available in other views” because threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event.

The proposed observation “The domain's event list separates denied attempts from allowed requests and reconciles the widget count” would check a different original case: The SOC's Top Websites widget reports a blocked phishing domain as the most visited site, but executives infer that users successfully accessed it. Its mechanism is: Website request counts can include blocked attempts; aggregation alone does not establish successful page delivery. In the present case, the FortiView Threat Map is blank even though internal-to-internal threats are present in logs, and the team concludes the feature is broken; the more direct acceptance evidence is “An eligible public-IP test detection appears while private-only records remain available in other views” because threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event.

The proposed observation “A controlled security profile detection appears in the intended threat widget after logging is enabled” would check a different original case: A FortiView widget displaying top attack categories is empty because the connected FortiGate forwards only basic traffic logs, not security-profile events. Its mechanism is: Threat widgets require eligible threat/security log data; ordinary traffic logs need not contain IPS or antivirus detections. In the present case, the FortiView Threat Map is blank even though internal-to-internal threats are present in logs, and the team concludes the feature is broken; the more direct acceptance evidence is “An eligible public-IP test detection appears while private-only records remain available in other views” because threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event.

This safeguard, “Review Application Control log coverage when using application-based monitors”, reduces a different source-defined risk: An employee's laptop consumes unexpected bandwidth through a video-sharing application, but the SOC reports only the destination IP addresses. That risk depends on: Application Control telemetry can group activity by detected application, not just network address. The recurring problem here is the FortiView Threat Map is blank even though internal-to-internal threats are present in logs, and the team concludes the feature is broken. The originally selected control “Document map eligibility limits before using the map as sole threat coverage evidence” is more specific because threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event.

This safeguard, “Annotate enforcement outcome when presenting website risk summaries”, reduces a different source-defined risk: The SOC's Top Websites widget reports a blocked phishing domain as the most visited site, but executives infer that users successfully accessed it. That risk depends on: Website request counts can include blocked attempts; aggregation alone does not establish successful page delivery. The recurring problem here is the FortiView Threat Map is blank even though internal-to-internal threats are present in logs, and the team concludes the feature is broken. The originally selected control “Document map eligibility limits before using the map as sole threat coverage evidence” is more specific because threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event.

This safeguard, “Record ADOM/device/time context when sharing dashboard screenshots or links”, reduces a different source-defined risk: A drill-down from a traffic dashboard seems to lead to unrelated sessions because the analyst changed ADOMs after the initial summary. That risk depends on: A drill-down is meaningful only when the same authorized data scope governs both summary and detail. The recurring problem here is the FortiView Threat Map is blank even though internal-to-internal threats are present in logs, and the team concludes the feature is broken. The originally selected control “Document map eligibility limits before using the map as sole threat coverage evidence” is more specific because threat Map geographic lines depend on eligible public-IP threat context and threat scoring, not every private-network event.

The action “Inspect FortiView Applications for the user or source and examine classified application usage” addresses a separate source case: An employee's laptop consumes unexpected bandwidth through a video-sharing application, but the SOC reports only the destination IP addresses. Its underlying reason is: Application Control telemetry can group activity by detected application, not just network address. This question instead describes a threat dashboard ranks one destination highly, but an analyst needs to isolate whether the spike occurred in the previous hour or over the whole week. The original answer “Change the FortiView time period and compare the same destination across equivalent shorter windows” targets that failure because time filtering changes which log samples contribute to an aggregate, so rankings can differ by investigation interval.

The action “Drill down from the compromised-host/IoC view to the contributing logs and indicator details” addresses a separate source case: An IoC monitor flags a suspicious host, but the analyst wants to see associated web-filter detections and threat ratings rather than treat the icon as conclusive. Its underlying reason is: A visual threat rating summarizes evidence; the underlying events are needed for incident-level conclusions. This question instead describes a threat dashboard ranks one destination highly, but an analyst needs to isolate whether the spike occurred in the previous hour or over the whole week. The original answer “Change the FortiView time period and compare the same destination across equivalent shorter windows” targets that failure because time filtering changes which log samples contribute to an aggregate, so rankings can differ by investigation interval.

The action “Confirm the active ADOM, selected device, and time filters match between the aggregate and detailed Log View” addresses a separate source case: A drill-down from a traffic dashboard seems to lead to unrelated sessions because the analyst changed ADOMs after the initial summary. Its underlying reason is: A drill-down is meaningful only when the same authorized data scope governs both summary and detail. This question instead describes a threat dashboard ranks one destination highly, but an analyst needs to isolate whether the spike occurred in the previous hour or over the whole week. The original answer “Change the FortiView time period and compare the same destination across equivalent shorter windows” targets that failure because time filtering changes which log samples contribute to an aggregate, so rankings can differ by investigation interval.

The action “An ingestion gap can make traffic summaries fall even if actual network activity remains constant” addresses a separate source case: After a logging outage, FortiView reports a sudden reduction in sessions and managers call it successful traffic reduction. Its underlying reason is: An ingestion gap can make traffic summaries fall even if actual network activity remains constant. This question instead describes a threat dashboard ranks one destination highly, but an analyst needs to isolate whether the spike occurred in the previous hour or over the whole week. The original answer “Time filtering changes which log samples contribute to an aggregate, so rankings can differ by investigation interval” targets that failure because time filtering changes which log samples contribute to an aggregate, so rankings can differ by investigation interval.

The action “Custom View can retain device selection, widget choices, and time period as a repeatable analysis workspace” addresses a separate source case: A SOC needs to keep a stable dashboard showing one FortiGate cluster for morning handover, but the current widget resets to all devices on every visit. Its underlying reason is: Custom View can retain device selection, widget choices, and time period as a repeatable analysis workspace. This question instead describes a threat dashboard ranks one destination highly, but an analyst needs to isolate whether the spike occurred in the previous hour or over the whole week. The original answer “Time filtering changes which log samples contribute to an aggregate, so rankings can differ by investigation interval” targets that failure because time filtering changes which log samples contribute to an aggregate, so rankings can differ by investigation interval.

The action “Website request counts can include blocked attempts; aggregation alone does not establish successful page delivery” addresses a separate source case: The SOC's Top Websites widget reports a blocked phishing domain as the most visited site, but executives infer that users successfully accessed it. Its underlying reason is: Website request counts can include blocked attempts; aggregation alone does not establish successful page delivery. This question instead describes a threat dashboard ranks one destination highly, but an analyst needs to isolate whether the spike occurred in the previous hour or over the whole week. The original answer “Time filtering changes which log samples contribute to an aggregate, so rankings can differ by investigation interval” targets that failure because time filtering changes which log samples contribute to an aggregate, so rankings can differ by investigation interval.