Free Cisco 350-701 Practice Exam with Questions & Answers | Set: 10

Explanation

The TLS connections are recorded in the mail logs, along with other significant actions that are related to

messages, such as filter actions, anti-virus and anti-spam verdicts, and delivery attempts. If there is a

successful TLS connection, there will be a TLS success entry in the mail logs. Likewise, a failed TLS

connection produces a TLS failed entry. If a message does not have an associated TLS entry in the log file, that message was not delivered over a TLS connection.

The absence of a DNS record in User Activity Search shows that the query is not reaching Cisco’s DNS-layer enforcement. Cisco documents that an Internal Domains entry sends DNS queries to local resolvers and bypasses both the roaming security component and Umbrella DNS protection. By contrast, an External Domains entry bypasses the Secure Web Gateway proxy while retaining DNS-layer protection. Cisco’s Internal and External Domain Lists guidance therefore supports adding this public domain to the External Domains list so its DNS request is evaluated by the SIA DNS category policy. HTTPS inspection is irrelevant when the DNS request itself is missing. Intelligent proxy affects selective web proxying after DNS classification. Adding the domain to the Internal Domains list would preserve the bypass and continue preventing the DNS event from appearing.

================

A Port-Bounce Change of Authorization terminates the current session and administratively restarts the switch port. That link transition forces an agentless MAB endpoint to reconnect, repeat authentication, and restart its DHCP process, allowing it to obtain an address appropriate for the newly assigned IoT VLAN. A reauthentication CoA can rerun authorization while leaving the physical link up; many cameras and badge readers then retain the address learned on the original VLAN. A basic session termination similarly does not guarantee the link-state change required to trigger DHCP renewal. “CoA-Reconnect” is not the relevant Cisco ISE authorization-profile action, and an idle timeout would delay rather than immediately enforce the change. Consequently, the authorization profile must specify Port Bounce so the VLAN and IP configuration are both refreshed. Cisco ISE CoA guidance

Explanation

Phishing attacks are the practice of sending fraudulent communications that appear to come from a reputable

source. It is usually done through email. The goal is to steal sensitive data like credit card and login information,

or to install malware on the victim’s machine.

To force a session to be adjusted after a policy change is made, two configurations are required on Cisco ISE and on Cisco TrustSec devices: Dynamic Authorization and Change of Authorization (CoA). Dynamic Authorization allows Cisco ISE to send commands to network devices to change the authorization status of a user session. CoA is a feature that enables Cisco ISE to send a RADIUS message to a network device to reauthenticate or disconnect a user session. These two configurations enable Cisco ISE to apply the updated policy to the user session without requiring the user to log out and log in again.

According to the source book, the steps to configure Dynamic Authorization and CoA are as follows1:

On Cisco ISE, navigate to Administration > Network Resources > Network Devices and select the network device that supports TrustSec.

On the Edit Network Device page, select the Advanced TrustSec Settings tab and check the Support for CoA check box.

On the same tab, select the appropriate CoA type from the drop-down list. The options are RADIUS Disconnect, Port Bounce, and Reauth.

Click Submit to save the changes.

On the network device, enter the global configuration mode and issue the command aaa server radius dynamic-author to enable Dynamic Authorization.

Optionally, you can specify the source interface, authentication key, and port number for the Dynamic Authorization messages.

Exit the global configuration mode and save the configuration.

 1: Implementing and Operating Cisco Security Core Technologies (SCOR) v1.0, Module 4: Secure Connectivity, Lesson 4.2: Implementing TrustSec, Topic 4.2.3: Configuring TrustSec on Cisco ISE and Network Devices, pp. 4-83 to 4-85.

Time synchronization is one of the features that can be configured for managed devices in the device platform settings of the Firepower Management Center (FMC). Time synchronization ensures that the FMC and its managed devices have the same date and time settings, which is important for accurate event logging and reporting. The FMC can act as a Network Time Protocol (NTP) server for its managed devices, or it can use an external NTP server as a time source1. The FMC can also synchronize its time with the system clock of the device where it is installed2. References := 1: Firepower Management Center Device Configuration Guide, 7.1 - Platform Settings 2: Firepower Management Center Configuration Guide, Version 6.6 - Device Management Basics

Quarantine Failed reports the result of a specific quarantine attempt; it does not establish the file’s current presence or execution state. A quarantine can fail because the file was renamed, moved, deleted, locked, or otherwise unavailable when the connector attempted remediation. The artifact might therefore still exist, or it might already have been removed through another mechanism. The log shown does not provide enough trajectory or error-detail evidence to decide between those possibilities. Option B overstates the observation as failure of an entire configured remediation policy. Options C and D make even stronger unsupported claims that the file remained accessible or continued running. The analyst should review event details, device/file trajectory, the connector logs, and the endpoint itself before declaring containment or compromise. Therefore, A is the only defensible conclusion from the displayed data. Cisco Secure Endpoint quarantine-failure discussion

Explanation

Explanation

Cisco Firepower NGFW Virtual (NGFWv) is the virtualized version of Cisco’s Firepower next generation firewall.

The Cisco NGFW virtual appliance is available in the AWS and Azure marketplaces. In AWS, it can be

deployed in routed and passive modes. Passive mode design requires ERSPAN, the Encapsulated Remote Switched Port Analyzer, which is currently not available in Azure.

In passive mode, NGFWv inspects packets like an Intrusion Detection System (IDS) appliance, but no action can be taken on the packet.

In routed mode NGFWv acts as a next hop for workloads. It can inspect packets and also take action on the packet based on rule and policy definitions.

The amount of URI text that is stored in Cisco WSA log files is controlled by the log-entry size parameter, which can be configured using the advancedproxyconfig command. The log-entry size parameter specifies the maximum number of bytes of the URI that will be logged for each request. The default value is 1024 bytes, but it can be changed to any value between 1 and 4096 bytes. If the URI is longer than the log-entry size, it will be truncated and a plus sign (+) will be appended to indicate that the URI was cut off. Configuring a small log-entry size can reduce the disk space and bandwidth consumption of the log files, but it can also limit the visibility and analysis of the requests.

References :=

User Guide for AsyncOS 11.0 for Cisco Web Security Appliances, Customizing Access Logs

Cisco WSA CLI Reference Guide for AsyncOS 11.0, advancedproxyconfig Command

WSA FAQ: How can I view the logs on the Cisco WSA? - Cisco

Session hijacking succeeds when an attacker obtains or abuses a valid session identifier, commonly one stored in a browser cookie. Secure cookie controls directly protect that credential. The Secure attribute limits transmission to HTTPS, reducing exposure over cleartext connections; HttpOnly prevents client-side scripts from reading the cookie; and an appropriate SameSite setting limits cross-site sending. Strong session handling should also use unpredictable identifiers, rotation after authentication, expiration, and server-side revocation. Input validation primarily mitigates injection vulnerabilities. Least privilege can reduce the damage after compromise but does not stop theft of a session token. Anti-CSRF tokens prevent unauthorized cross-site requests made through a victim’s authenticated browser, but they are not the primary protection against capture of the session cookie itself. Therefore, secure cookies are the best answer. RFC 6265 HTTP cookie specification

The debug shows that IKE_SA_INIT completed successfully and the peers agreed on AES-256, SHA-256, and DH Group 14. That proves a mutually acceptable Phase 1 proposal was selected, so changing the DH group or removing SHA-384 is unnecessary. The failure occurs later during IKE_AUTH, where the peer returns AUTHENTICATION_FAILED notification type 24. Because the displayed authentication method is a pre-shared key, the first corrective action is to verify that both peers use exactly the same key; capitalization, whitespace, or character differences change the calculated AUTH value. RFC 7296 defines the AUTH value as being derived from the shared secret and states that an AUTHENTICATION_FAILED notification prevents creation of the IKE SA. Replacing PSK authentication with certificates is not required to correct a PSK mismatch. IETF IKEv2 specification

Custom clauses allow an administrator to express the event conditions that a Cisco Secure Workload forensic rule must match, so A is correct. A rule combines a forensic event type with optional attributes, comparison operators, actions, and severity. Cisco’s Secure Workload forensic-events guide instructs administrators to create a rule and enter its clause, and it explains that the feature applies user-defined rules to captured real-time events. Secure Workload also supplies default product rules and MITRE ATT & CK rules, but those are predefined examples rather than the capability used to configure an administrator’s own logic. “Windows or Linux application” describes neither a rule-building mechanism nor a valid clause type. Therefore, custom clauses provide the required configurable forensic detection capability.

================

MDM stands for Mobile Device Management, which is a system that performs compliance checks and remote wiping on mobile devices. MDM allows administrators to enforce security policies, monitor device status, and remotely manage devices in case of loss, theft, or compromise. MDM can also integrate with other Cisco security solutions, such as ISE, AMP, and Umbrella, to provide enhanced protection and visibility for mobile devices. References:

Mobile Device Management (MDM) - Cisco

Implementing and Operating Cisco Security Core Technologies (SCOR) - Module 5: Secure Network Access