Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

EC-Council 312-50 Exam - Topic 8 Question 65 Discussion

Posted by Fletcher on Feb 03, 2023 at 01:56 AM

Take a look at the following attack on a Web Server using obstructed URL:

How would you protect from these attacks?

Suggested Answer: B

Get Premium 312-50 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
30 comments · newest first
LI
Lizbeth 11 months ago
Wait, people still use Active Scripts Detection? That's a bit outdated, right?
CA
Carole 11 months ago
Definitely need to configure the server to deny those hex characters!
AN
Antonio 12 months ago
Isn't hex encoding pretty common? Not sure if blocking it is the best move.
LA
Lai 12 months ago
I disagree, SSL alone (Option C) won't stop these attacks.
DO
Doug 1 year ago
Option B sounds solid, gotta monitor those Unicode requests!
PE
Peggie 1 year ago
Active Scripts Detection sounds familiar, but I can't recall if it directly relates to URL obfuscation. I might lean towards option B instead.
CA
Cathrine 1 year ago
I feel like SSL authentication is more about securing data in transit rather than preventing these specific attacks. So, I'm not sure about option C.
EL
Elfrieda 1 year ago
I'm not entirely sure, but I think IDS rules for Unicode requests could help detect these types of attacks. Option B might be the way to go.
AL
Alyssa 1 year ago
I remember studying about hex encoding and how it can be used to bypass filters, so option A seems like a solid choice.
LI
Lilli 1 year ago
I'm a little confused - option C talks about clicking on PowerPoint Presentations, but I'm not sure if that's the same as searching for PowerPoint files. I might try option D just to be safe.
TA
Tamra 1 year ago
Okay, I think I've got a handle on this. The key things to focus on are the privileges required, the provisioning process, and the differences between cloning and incremental recovery. I'm feeling pretty confident I can get this one right.
MA
Martina 1 year ago
Hmm, I'm a bit confused on this one. Is a zone the first domain that belongs to a company? Or is it a collection of domains? I'll have to think this through carefully.
VE
Verlene 1 year ago
This looks straightforward, I just need to add up the income items and subtract the deductions to get the AGI.
SO
Sol 1 year ago
Haha, I love how these hackers try to get all fancy with their URL obfuscation. But don't worry, I'm not falling for that nonsense. Option A is the way to go, my friends!
BR
Brinda 1 year ago
Well, this is a real head-scratcher. I'm gonna have to go with A too - those hex-encoded characters are just begging to be denied. Time to put the web server on a strict character diet!
CH
Chuck 1 year ago
↳ replying to Brinda
User 3: It's important to stay vigilant against these types of attacks.
SH
Shay 1 year ago
↳ replying to Brinda
User 2: Definitely, we should configure the Web Server to deny requests involving them.
DA
Dalene 1 year ago
↳ replying to Brinda
User 1: I agree, those hex-encoded characters look suspicious.
DE
Denny 2 years ago
But wouldn't using SSL authentication on Web Servers also add an extra layer of security?
FR
Francoise 2 years ago
Okay, let's see here. I don't think SSL authentication is gonna cut it for this one (C), and I'm not a big fan of active script detection either (D). Yep, gotta be option A all the way!
MA
Mayra 1 year ago
↳ replying to Francoise
User 2: Yeah, configuring the Web Server to deny requests with 'hex encoded' characters is the way to go.
JA
Jamal 1 year ago
↳ replying to Francoise
User 1: I agree, option A seems like the best choice.
MI
Michal 2 years ago
I disagree, I believe option B is more effective in detecting strange Unicode requests.
DE
Dewitt 2 years ago
Hmm, this one's tricky. I'm leaning towards B - setting up an IDS to catch those strange Unicode requests. Can't be too careful with these sneaky attacks, you know?
MA
Margarett 2 years ago
Ah, the classic obstructed URL attack. Gotta love how the bad guys try to sneak past our defenses with all those funky characters. I'd go with option A - keep those hex-encoded weirdos out of my web server!
LO
Lorrine 1 year ago
↳ replying to Margarett
Ryann: Let's make sure our defenses are strong against those sneaky attacks.
KA
Kate 1 year ago
↳ replying to Margarett
User 3: Definitely, we need to configure the Web Server to deny those requests.
RY
Ryann 1 year ago
↳ replying to Margarett
User 2: I agree, option A sounds like the best way to block them from getting in.
ST
Stephanie 1 year ago
↳ replying to Margarett
User 1: Yeah, those attackers sure do love their hex-encoded characters.
DE
Denny 2 years ago
I think option A is the best choice to protect from these attacks.
0/2000 characters

Save Cancel