Redirection and Attack Obfuscation GCPN Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   Which security control is most likely to be evaded by obfuscating the payload with encryption?

   • AAccount lockout policies
   • BMulti-factor authentication (MFA) on the target account
   • CNetwork-based intrusion detection systems (IDS) that inspect packet payloads
   • DHost-based firewall rules that block specific ports
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   In a cohesive attack chain that combines redirection and obfuscation, what is the typical role of the redirection component?

   • ATo bypass multi-factor authentication
   • BTo deliver the victim to the final malicious page while evading URL-based filters
   • CTo increase the speed of the credential brute-force attack
   • DTo encrypt the credential harvesting script
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   Which technique is commonly used to obfuscate a redirection payload by hiding the final destination URL from casual inspection?

   • AUsing an HTTP 200 status code
   • BAdding a comment in the HTML source
   • CIncreasing the meta refresh delay to 60 seconds
   • DUsing a URL shortener service
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   Which obfuscation technique involves generating a new, unique version of the malicious payload each time it is used, so that signature-based detection fails?

   • ASteganography
   • BBase64 encoding
   • CPolymorphism
   • DURL shortening
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   You are crafting a phishing campaign that uses a legitimate-looking URL to lure victims into entering credentials. The URL must appear trustworthy to the victim, but the actual credential harvesting page is on a different domain. Which approach best combines redirection and obfuscation to maintain a legitimate appearance while sending victims to the harvesting page?

   • AHost a legitimate-looking page on a subdomain of a compromised site and use a meta refresh to the harvesting page.
   • BEmbed the harvesting page in an iframe on the legitimate-looking page and hide the iframe borders.
   • CCreate a phishing page that uses a 301 redirect to the harvesting page, and rely on the victim not checking the final URL.
   • DUse a URL shortener that redirects to the harvesting page, and display the shortened URL in the email.
   Reveal Solution Discussion Select an answer first