350-701 Exam Preparation Material | Implementing and Operating Cisco Security Core Technologies (SCOR)

Explanation:
DNS-layer protection evaluates domains before a connection is established, but a Secure Web Gateway provides deeper control after web traffic is proxied. URL filtering can allow or block requests according to the complete URL, category, reputation, or organizational policy, so A is correct. Secure Web Gateway inspection can also apply data loss prevention controls to web uploads and transfers, making C correct. Cisco describes URL filtering as a core Secure Web Gateway capability, while its Secure Access DLP documentation states that DLP protects sensitive data uploaded to the web or transferred externally. Blocking malware before DNS lookup belongs to DNS-layer enforcement, not an additional SWG benefit. Internal mail routing is an email-security function, and firewall DNS caching is not the requested Secure Access security capability.

Explanation:
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