Practice Exams:

Fortinet NSE4_FGT_AD-7.6 Dumps

EXAM: Fortinet NSE 4 - FortiOS 7.6 Administrator
Verified By Experts
Premium Bundle
$49.99

NSE4_FGT_AD-7.6 Premium ETE File


  • Premium File 94 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet NSE4_FGT_AD-7.6 Practice Test 49

Question 480

At a managed branch perimeter, a FortiGate running FortiOS 7.6 has this observation: A team needs to block a documented high-risk exploit while monitoring lower-severity signatures for false positives. The operator corrected the configuration by choosing to tune IPS sensor signature filters and actions to the approved threat coverage and severity. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Use approved synthetic exploit indicators and inspect IPS match and block actions.
  2. Check the IPS signature database timestamp and presence of the intended test signature.
  3. Require peer review for ips signature severity changes and an acceptance check that will use approved synthetic exploit indicators and inspect IPS match and block actions before relevant releases.
  4. Inspect the presented certificate chain on an affected endpoint and retest the managed trust path.
  5. Verify the policy ID and selected SSL profile during a controlled HTTPS test.

Explanation

Correct Answers

A:

It measures the operational result after the correction to tune IPS sensor signature filters and actions to the approved threat coverage and severity, and it directly checks the reported condition: a team needs to block a documented high-risk exploit while monitoring lower-severity signatures for false positives. For ips signature severity, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

C:

The organization already encountered the failure where a team needs to block a documented high-risk exploit while monitoring lower-severity signatures for false positives, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to use approved synthetic exploit indicators and inspect IPS match and block actions, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

B:

The proposed evidence, to check the IPS signature database timestamp and presence of the intended test signature, checks fortiguard ips update checks in a situation such as a newly published protection is absent from a firewall using an outdated IPS signature database, not the required ips signature severity acceptance. For the affected firewall behavior the directly discriminating check is to use approved synthetic exploit indicators and inspect IPS match and block actions, alongside a review of ips signature severity rather than fortiguard ips update checks settings.

D:

The proposed evidence, to inspect the presented certificate chain on an affected endpoint and retest the managed trust path, checks deep inspection trusted ca in a situation such as clients receive certificate trust warnings after the firewall begins deep inspecting outbound HTTPS traffic, not the required ips signature severity acceptance. For the affected firewall behavior the directly discriminating check is to use approved synthetic exploit indicators and inspect IPS match and block actions, alongside a review of ips signature severity rather than deep inspection trusted ca settings.

E:

The proposed evidence, to verify the policy ID and selected SSL profile during a controlled HTTPS test, checks ssl profile policy attachment in a situation such as a deep-inspection profile exists but the production policy still references no-inspection, not the required ips signature severity acceptance. For the affected firewall behavior the directly discriminating check is to use approved synthetic exploit indicators and inspect IPS match and block actions, alongside a review of ips signature severity rather than ssl profile policy attachment settings.

Question 481

A FortiOS 7.6 review of a datacenter security boundary reports the following condition: A production application is disrupted by one signature, but disabling the entire IPS profile would expose unrelated threats. The requirement concerns ips false positive handling while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Investigate the exact signature and apply a narrow reviewed exception or tuning change.
  2. Review SSL inspection validation actions and block or separately handle invalid upstream certificates under policy.
  3. Use deep SSL inspection with appropriate policy and endpoint trust when decrypted content inspection is necessary.
  4. Limit SSL exceptions to documented required destinations rather than exempting all TLS sessions.

Explanation

Correct Answer

A:

Choosing to investigate the exact signature and apply a narrow reviewed exception or tuning change changes the component implicated by that observation, rather than masking the symptom through a different firewall feature. Operators can substantiate the choice by carrying out this test: retest the application and confirm unrelated high-risk test signatures remain enforced.

Incorrect Answers

B:

Reviewing SSL inspection validation actions and block or separately handle invalid upstream certificates under policy would focus the new configuration on untrusted upstream certificate, for which a TLS destination presents an invalid or untrusted certificate and the policy must not silently accept that connection may be a valid concern, but this ips false positive handling configuration has a different failure. Evidence for ips false positive handling requires staff to retest the application and confirm unrelated high-risk test signatures remain enforced; the proposed untrusted upstream certificate change cannot deliver that ips false positive handling result by itself.

C:

Using deep SSL inspection with appropriate policy and endpoint trust when decrypted content inspection is necessary would focus the new configuration on certificate inspection visibility, for which a policy uses certificate inspection and administrators expect it to scan complete encrypted web page bodies may be a valid concern, but this ips false positive handling configuration has a different failure. Evidence for ips false positive handling requires staff to retest the application and confirm unrelated high-risk test signatures remain enforced; the proposed certificate inspection visibility change cannot deliver that ips false positive handling result by itself.

D:

Limiting SSL exceptions to documented required destinations rather than exempting all TLS sessions would focus the new configuration on tls decryption exception scope, for which a business-wide SSL exemption suppresses malware scanning on unrelated websites may be a valid concern, but this ips false positive handling configuration has a different failure. Evidence for ips false positive handling requires staff to retest the application and confirm unrelated high-risk test signatures remain enforced; the proposed tls decryption exception scope change cannot deliver that ips false positive handling result by itself.

Question 482

During FortiOS 7.6 operations at an enterprise gateway change window, the evidence is: A production application is disrupted by one signature, but disabling the entire IPS profile would expose unrelated threats. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this ips false positive handling failure?

  1. Disable every IPS rule across the subnet to solve one suspected false positive.
  2. Use a wildcard SSL exception that disables inspection on every internet destination.
  3. Configure SSL inspection to bypass all certificate validation warnings without review.
  4. Assume certificate-only inspection decrypts and reads every HTTPS payload.

Explanation

Correct Answer

A:

The problem arises when administrators disable every IPS rule across the subnet to solve one suspected false positive, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to investigate the exact signature and apply a narrow reviewed exception or tuning change.

Incorrect Answers

B:

The alternative cause involving tls decryption exception scope can produce a different failure, for example when a business-wide SSL exemption suppresses malware scanning on unrelated websites; it is not the ips false positive handling case. The more specific error here is the choice to disable every IPS rule across the subnet to solve one suspected false positive; check it by attempting to retest the application and confirm unrelated high-risk test signatures remain enforced before making an unrelated tls decryption exception scope change.

C:

The alternative cause involving untrusted upstream certificate can produce a different failure, for example when a TLS destination presents an invalid or untrusted certificate and the policy must not silently accept that connection; it is not the ips false positive handling case. The more specific error here is the choice to disable every IPS rule across the subnet to solve one suspected false positive; check it by attempting to retest the application and confirm unrelated high-risk test signatures remain enforced before making an unrelated untrusted upstream certificate change.

D:

The alternative cause involving certificate inspection visibility can produce a different failure, for example when a policy uses certificate inspection and administrators expect it to scan complete encrypted web page bodies; it is not the ips false positive handling case. The more specific error here is the choice to disable every IPS rule across the subnet to solve one suspected false positive; check it by attempting to retest the application and confirm unrelated high-risk test signatures remain enforced before making an unrelated certificate inspection visibility change.

Question 483

At a redundant regional firewall pair, a FortiGate running FortiOS 7.6 has this observation: A production application is disrupted by one signature, but disabling the entire IPS profile would expose unrelated threats. Investigators confirmed this cause: administrators chose to disable every IPS rule across the subnet to solve one suspected false positive. Which action MOST directly corrects the confirmed error?

  1. Investigate the exact signature and apply a narrow reviewed exception or tuning change.
  2. Review SSL inspection validation actions and block or separately handle invalid upstream certificates under policy.
  3. Limit SSL exceptions to documented required destinations rather than exempting all TLS sessions.
  4. Disable every IPS rule across the subnet to solve one suspected false positive.

Explanation

Correct Answer

A:

This addresses ips false positive handling without needlessly weakening separate security or routing controls. Given the observed condition—a production application is disrupted by one signature, but disabling the entire IPS profile would expose unrelated threats—the operator should then retest the application and confirm unrelated high-risk test signatures remain enforced.

Incorrect Answers

B:

Changing the mechanism to review SSL inspection validation actions and block or separately handle invalid upstream certificates under policy could be a sensible correction for untrusted upstream certificate when a TLS destination presents an invalid or untrusted certificate and the policy must not silently accept that connection. The targeted fix is to investigate the exact signature and apply a narrow reviewed exception or tuning change; a review of untrusted upstream certificate would not, by itself, prove that the team can retest the application and confirm unrelated high-risk test signatures remain enforced.

C:

Changing the mechanism to limit SSL exceptions to documented required destinations rather than exempting all TLS sessions could be a sensible correction for tls decryption exception scope when a business-wide SSL exemption suppresses malware scanning on unrelated websites. The targeted fix is to investigate the exact signature and apply a narrow reviewed exception or tuning change; a review of tls decryption exception scope would not, by itself, prove that the team can retest the application and confirm unrelated high-risk test signatures remain enforced.

D:

The proposal repeats the confirmed ips false positive handling error by choosing to disable every IPS rule across the subnet to solve one suspected false positive. A corrective change must instead investigate the exact signature and apply a narrow reviewed exception or tuning change and then produce the measurable result to retest the application and confirm unrelated high-risk test signatures remain enforced; repeating the failed setting cannot serve as a repair.

Question 484

A FortiOS 7.6 review of a remote-office migration reports the following condition: A production application is disrupted by one signature, but disabling the entire IPS profile would expose unrelated threats. The incident has been fixed, and the owner wants to prevent a recurrence of the ips false positive handling problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for untrusted upstream certificate changes and an acceptance check that will connect to a controlled untrusted-certificate server and confirm the intended block or exception before relevant releases.
  2. Require peer review for ips false positive handling changes and an acceptance check that will retest the application and confirm unrelated high-risk test signatures remain enforced before relevant releases.
  3. Require peer review for certificate inspection visibility changes and an acceptance check that will test with permitted synthetic HTTPS content and inspect which fields and payload are visible before relevant releases.
  4. Require peer review for tls decryption exception scope changes and an acceptance check that will test an exempt destination and a nonexempt destination for the expected profile actions before relevant releases.

Explanation

Correct Answer

B:

This change-control gate requires teams to require peer review for ips false positive handling changes and an acceptance check that will retest the application and confirm unrelated high-risk test signatures remain enforced before relevant releases, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to retest the application and confirm unrelated high-risk test signatures remain enforced.

Incorrect Answers

A:

A review gate for untrusted upstream certificate, such as require peer review for untrusted upstream certificate changes and an acceptance check that will connect to a controlled untrusted-certificate server and confirm the intended block or exception before relevant releases, can be useful where a TLS destination presents an invalid or untrusted certificate and the policy must not silently accept that connection, but it is not the approved ips false positive handling review. The preventive test must enforce that staff will investigate the exact signature and apply a narrow reviewed exception or tuning change and subsequently can retest the application and confirm unrelated high-risk test signatures remain enforced; the proposed untrusted upstream certificate gate would not check that same control.

C:

A review gate for certificate inspection visibility, such as require peer review for certificate inspection visibility changes and an acceptance check that will test with permitted synthetic HTTPS content and inspect which fields and payload are visible before relevant releases, can be useful where a policy uses certificate inspection and administrators expect it to scan complete encrypted web page bodies, but it is not the approved ips false positive handling review. The preventive test must enforce that staff will investigate the exact signature and apply a narrow reviewed exception or tuning change and subsequently can retest the application and confirm unrelated high-risk test signatures remain enforced; the proposed certificate inspection visibility gate would not check that same control.

D:

A review gate for tls decryption exception scope, such as require peer review for tls decryption exception scope changes and an acceptance check that will test an exempt destination and a nonexempt destination for the expected profile actions before relevant releases, can be useful where a business-wide SSL exemption suppresses malware scanning on unrelated websites, but it is not the approved ips false positive handling review. The preventive test must enforce that staff will investigate the exact signature and apply a narrow reviewed exception or tuning change and subsequently can retest the application and confirm unrelated high-risk test signatures remain enforced; the proposed tls decryption exception scope gate would not check that same control.

Question 485

During FortiOS 7.6 operations at a monitored business uplink, the evidence is: A production application is disrupted by one signature, but disabling the entire IPS profile would expose unrelated threats. The operator corrected the configuration by choosing to investigate the exact signature and apply a narrow reviewed exception or tuning change. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Test an exempt destination and a nonexempt destination for the expected profile actions.
  2. Connect to a controlled untrusted-certificate server and confirm the intended block or exception.
  3. Test with permitted synthetic HTTPS content and inspect which fields and payload are visible.
  4. Require peer review for ips false positive handling changes and an acceptance check that will retest the application and confirm unrelated high-risk test signatures remain enforced before relevant releases.
  5. Retest the application and confirm unrelated high-risk test signatures remain enforced.

Explanation

Correct Answers

D:

The organization already encountered the failure where a production application is disrupted by one signature, but disabling the entire IPS profile would expose unrelated threats, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to retest the application and confirm unrelated high-risk test signatures remain enforced, this gate checks future revisions without claiming that the current configuration is permanently correct.

E:

It measures the operational result after the correction to investigate the exact signature and apply a narrow reviewed exception or tuning change, and it directly checks the reported condition: a production application is disrupted by one signature, but disabling the entire IPS profile would expose unrelated threats. For ips false positive handling, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

Incorrect Answers

A:

The proposed evidence, to test an exempt destination and a nonexempt destination for the expected profile actions, checks tls decryption exception scope in a situation such as a business-wide SSL exemption suppresses malware scanning on unrelated websites, not the required ips false positive handling acceptance. For the affected firewall behavior the directly discriminating check is to retest the application and confirm unrelated high-risk test signatures remain enforced, alongside a review of ips false positive handling rather than tls decryption exception scope settings.

B:

The proposed evidence, to connect to a controlled untrusted-certificate server and confirm the intended block or exception, checks untrusted upstream certificate in a situation such as a TLS destination presents an invalid or untrusted certificate and the policy must not silently accept that connection, not the required ips false positive handling acceptance. For the affected firewall behavior the directly discriminating check is to retest the application and confirm unrelated high-risk test signatures remain enforced, alongside a review of ips false positive handling rather than untrusted upstream certificate settings.

C:

The proposed evidence, to test with permitted synthetic HTTPS content and inspect which fields and payload are visible, checks certificate inspection visibility in a situation such as a policy uses certificate inspection and administrators expect it to scan complete encrypted web page bodies, not the required ips false positive handling acceptance. For the affected firewall behavior the directly discriminating check is to retest the application and confirm unrelated high-risk test signatures remain enforced, alongside a review of ips false positive handling rather than certificate inspection visibility settings.

Question 486

At an internal application segment, a FortiGate running FortiOS 7.6 has this observation: IPS logs a critical exploit signature but the connection remains permitted because the signature action is Monitor. The requirement concerns ips block versus monitor while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Align the web-filter profile feature set with the firewall policy's chosen flow or proxy inspection mode.
  2. Deploy the approved deep-inspection CA certificate through managed endpoint trust stores.
  3. Create narrowly scoped SSL inspection exceptions for the protected category while maintaining permitted certificate checks.
  4. Change the targeted IPS signature action to Block under the approved security policy.

Explanation

Correct Answer

D:

Choosing to change the targeted IPS signature action to Block under the approved security policy changes the component implicated by that observation, rather than masking the symptom through a different firewall feature. Operators can substantiate the choice by carrying out this test: replay a controlled attack indicator and verify the connection is denied with an IPS block log.

Incorrect Answers

A:

Selecting align the web-filter profile feature set with the firewall policy's chosen flow or proxy inspection mode would focus the new configuration on flow versus proxy feature set, for which a proxy-based web filter profile cannot be selected on a firewall rule configured for flow-based inspection may be a valid concern, but this ips block versus monitor configuration has a different failure. Evidence for ips block versus monitor requires staff to replay a controlled attack indicator and verify the connection is denied with an IPS block log; the proposed flow versus proxy feature set change cannot deliver that ips block versus monitor result by itself.

B:

Selecting deploy the approved deep-inspection CA certificate through managed endpoint trust stores would focus the new configuration on deep inspection trusted ca, for which clients receive certificate trust warnings after the firewall begins deep inspecting outbound HTTPS traffic may be a valid concern, but this ips block versus monitor configuration has a different failure. Evidence for ips block versus monitor requires staff to replay a controlled attack indicator and verify the connection is denied with an IPS block log; the proposed deep inspection trusted ca change cannot deliver that ips block versus monitor result by itself.

C:

Creating narrowly scoped SSL inspection exceptions for the protected category while maintaining permitted certificate checks would focus the new configuration on sensitive https inspection exemption, for which a compliance policy prohibits decrypting specified financial transactions but still requires encrypted session visibility may be a valid concern, but this ips block versus monitor configuration has a different failure. Evidence for ips block versus monitor requires staff to replay a controlled attack indicator and verify the connection is denied with an IPS block log; the proposed sensitive https inspection exemption change cannot deliver that ips block versus monitor result by itself.

Question 487

A FortiOS 7.6 review of a hybrid-network deployment reports the following condition: IPS logs a critical exploit signature but the connection remains permitted because the signature action is Monitor. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this ips block versus monitor failure?

  1. Enable deep inspection without making its issuing CA trusted on affected clients.
  2. Deep-inspect all financial transactions without considering the documented exclusion.
  3. Attach a proxy-only profile to a flow-mode policy and assume all controls remain supported.
  4. Leave the signature set to Monitor and treat its log as evidence of dropped traffic.

Explanation

Correct Answer

D:

The problem arises when administrators leave the signature set to Monitor and treat its log as evidence of dropped traffic, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to change the targeted IPS signature action to Block under the approved security policy.

Incorrect Answers

A:

The alternative cause involving deep inspection trusted ca can produce a different failure, for example when clients receive certificate trust warnings after the firewall begins deep inspecting outbound HTTPS traffic; it is not the ips block versus monitor case. The more specific error here is the choice to leave the signature set to Monitor and treat its log as evidence of dropped traffic; check it by attempting to replay a controlled attack indicator and verify the connection is denied with an IPS block log before making an unrelated deep inspection trusted ca change.

B:

The alternative cause involving sensitive https inspection exemption can produce a different failure, for example when a compliance policy prohibits decrypting specified financial transactions but still requires encrypted session visibility; it is not the ips block versus monitor case. The more specific error here is the choice to leave the signature set to Monitor and treat its log as evidence of dropped traffic; check it by attempting to replay a controlled attack indicator and verify the connection is denied with an IPS block log before making an unrelated sensitive https inspection exemption change.

C:

The alternative cause involving flow versus proxy feature set can produce a different failure, for example when a proxy-based web filter profile cannot be selected on a firewall rule configured for flow-based inspection; it is not the ips block versus monitor case. The more specific error here is the choice to leave the signature set to Monitor and treat its log as evidence of dropped traffic; check it by attempting to replay a controlled attack indicator and verify the connection is denied with an IPS block log before making an unrelated flow versus proxy feature set change.

Question 488

During FortiOS 7.6 operations at an operations incident response, the evidence is: IPS logs a critical exploit signature but the connection remains permitted because the signature action is Monitor. Investigators confirmed this cause: administrators chose to leave the signature set to Monitor and treat its log as evidence of dropped traffic. Which action MOST directly corrects the confirmed error?

  1. Align the web-filter profile feature set with the firewall policy's chosen flow or proxy inspection mode.
  2. Change the targeted IPS signature action to Block under the approved security policy.
  3. Create narrowly scoped SSL inspection exceptions for the protected category while maintaining permitted certificate checks.
  4. Leave the signature set to Monitor and treat its log as evidence of dropped traffic.

Explanation

Correct Answer

B:

This addresses ips block versus monitor without needlessly weakening separate security or routing controls. Given the observed condition—iPS logs a critical exploit signature but the connection remains permitted because the signature action is Monitor—the operator should then replay a controlled attack indicator and verify the connection is denied with an IPS block log.

Incorrect Answers

A:

Changing the mechanism to align the web-filter profile feature set with the firewall policy's chosen flow or proxy inspection mode could be a sensible correction for flow versus proxy feature set when a proxy-based web filter profile cannot be selected on a firewall rule configured for flow-based inspection. The targeted fix is to change the targeted IPS signature action to Block under the approved security policy; a review of flow versus proxy feature set would not, by itself, prove that the team can replay a controlled attack indicator and verify the connection is denied with an IPS block log.

C:

Changing the mechanism to create narrowly scoped SSL inspection exceptions for the protected category while maintaining permitted certificate checks could be a sensible correction for sensitive https inspection exemption when a compliance policy prohibits decrypting specified financial transactions but still requires encrypted session visibility. The targeted fix is to change the targeted IPS signature action to Block under the approved security policy; a review of sensitive https inspection exemption would not, by itself, prove that the team can replay a controlled attack indicator and verify the connection is denied with an IPS block log.

D:

The proposal repeats the confirmed ips block versus monitor error by choosing to leave the signature set to Monitor and treat its log as evidence of dropped traffic. A corrective change must instead change the targeted IPS signature action to Block under the approved security policy and then produce the measurable result to replay a controlled attack indicator and verify the connection is denied with an IPS block log; repeating the failed setting cannot serve as a repair.

Question 489

At a network segmentation review, a FortiGate running FortiOS 7.6 has this observation: IPS logs a critical exploit signature but the connection remains permitted because the signature action is Monitor. The incident has been fixed, and the owner wants to prevent a recurrence of the ips block versus monitor problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for ips block versus monitor changes and an acceptance check that will replay a controlled attack indicator and verify the connection is denied with an IPS block log before relevant releases.
  2. Require peer review for flow versus proxy feature set changes and an acceptance check that will inspect policy mode and profile feature set, then run a representative filtered web request before relevant releases.
  3. Require peer review for deep inspection trusted ca changes and an acceptance check that will inspect the presented certificate chain on an affected endpoint and retest the managed trust path before relevant releases.
  4. Require peer review for sensitive https inspection exemption changes and an acceptance check that will test an exempt site and an ordinary site and verify different inspection behavior before relevant releases.

Explanation

Correct Answer

A:

This change-control gate requires teams to require peer review for ips block versus monitor changes and an acceptance check that will replay a controlled attack indicator and verify the connection is denied with an IPS block log before relevant releases, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to replay a controlled attack indicator and verify the connection is denied with an IPS block log.

Incorrect Answers

B:

A review gate for flow versus proxy feature set, such as require peer review for flow versus proxy feature set changes and an acceptance check that will inspect policy mode and profile feature set, then run a representative filtered web request before relevant releases, can be useful where a proxy-based web filter profile cannot be selected on a firewall rule configured for flow-based inspection, but it is not the approved ips block versus monitor review. The preventive test must enforce that staff will change the targeted IPS signature action to Block under the approved security policy and subsequently can replay a controlled attack indicator and verify the connection is denied with an IPS block log; the proposed flow versus proxy feature set gate would not check that same control.

C:

A review gate for deep inspection trusted ca, such as require peer review for deep inspection trusted ca changes and an acceptance check that will inspect the presented certificate chain on an affected endpoint and retest the managed trust path before relevant releases, can be useful where clients receive certificate trust warnings after the firewall begins deep inspecting outbound HTTPS traffic, but it is not the approved ips block versus monitor review. The preventive test must enforce that staff will change the targeted IPS signature action to Block under the approved security policy and subsequently can replay a controlled attack indicator and verify the connection is denied with an IPS block log; the proposed deep inspection trusted ca gate would not check that same control.

D:

A review gate for sensitive https inspection exemption, such as require peer review for sensitive https inspection exemption changes and an acceptance check that will test an exempt site and an ordinary site and verify different inspection behavior before relevant releases, can be useful where a compliance policy prohibits decrypting specified financial transactions but still requires encrypted session visibility, but it is not the approved ips block versus monitor review. The preventive test must enforce that staff will change the targeted IPS signature action to Block under the approved security policy and subsequently can replay a controlled attack indicator and verify the connection is denied with an IPS block log; the proposed sensitive https inspection exemption gate would not check that same control.

Question 490

A FortiOS 7.6 review of a managed branch perimeter reports the following condition: IPS logs a critical exploit signature but the connection remains permitted because the signature action is Monitor. The operator corrected the configuration by choosing to change the targeted IPS signature action to Block under the approved security policy. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Inspect the presented certificate chain on an affected endpoint and retest the managed trust path.
  2. Replay a controlled attack indicator and verify the connection is denied with an IPS block log.
  3. Require peer review for ips block versus monitor changes and an acceptance check that will replay a controlled attack indicator and verify the connection is denied with an IPS block log before relevant releases.
  4. Test an exempt site and an ordinary site and verify different inspection behavior.
  5. Inspect policy mode and profile feature set, then run a representative filtered web request.

Explanation

Correct Answers

B:

It measures the operational result after the correction to change the targeted IPS signature action to Block under the approved security policy, and it directly checks the reported condition: iPS logs a critical exploit signature but the connection remains permitted because the signature action is Monitor. For ips block versus monitor, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

C:

The organization already encountered the failure where iPS logs a critical exploit signature but the connection remains permitted because the signature action is Monitor, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to replay a controlled attack indicator and verify the connection is denied with an IPS block log, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

A:

The proposed evidence, to inspect the presented certificate chain on an affected endpoint and retest the managed trust path, checks deep inspection trusted ca in a situation such as clients receive certificate trust warnings after the firewall begins deep inspecting outbound HTTPS traffic, not the required ips block versus monitor acceptance. For the affected firewall behavior the directly discriminating check is to replay a controlled attack indicator and verify the connection is denied with an IPS block log, alongside a review of ips block versus monitor rather than deep inspection trusted ca settings.

D:

The proposed evidence, to test an exempt site and an ordinary site and verify different inspection behavior, checks sensitive https inspection exemption in a situation such as a compliance policy prohibits decrypting specified financial transactions but still requires encrypted session visibility, not the required ips block versus monitor acceptance. For the affected firewall behavior the directly discriminating check is to replay a controlled attack indicator and verify the connection is denied with an IPS block log, alongside a review of ips block versus monitor rather than sensitive https inspection exemption settings.

E:

The proposed evidence, to inspect policy mode and profile feature set, then run a representative filtered web request, checks flow versus proxy feature set in a situation such as a proxy-based web filter profile cannot be selected on a firewall rule configured for flow-based inspection, not the required ips block versus monitor acceptance. For the affected firewall behavior the directly discriminating check is to replay a controlled attack indicator and verify the connection is denied with an IPS block log, alongside a review of ips block versus monitor rather than flow versus proxy feature set settings.

Fortinet NSE 4 - FortiOS 7.6 Administrator (NSE4_FGT_AD-7.6) Practice Tests