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
Mail Us support@pass4success.com
Location PL
Mob_nav_barsMENU

Eccouncil Exam 312-50 Topic 8 Question 65 Discussion

Actual exam question for Eccouncil's 312-50 exam
Question #: 65
Topic #: 8
[All 312-50 Questions]

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

How would you protect from these attacks?

Show Suggested Answer Hide Answer
Suggested Answer: B

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

Limited Time Offer

25%

Off

Get Premium 312-50 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Sol
1 months 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!
upvoted 0 times
...
Brinda
1 months 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!
upvoted 0 times
Dalene
13 days ago
User 1: I agree, those hex-encoded characters look suspicious.
upvoted 0 times
...
...
Denny
2 months ago
But wouldn't using SSL authentication on Web Servers also add an extra layer of security?
upvoted 0 times
...
Francoise
2 months 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!
upvoted 0 times
Mayra
1 months ago
User 2: Yeah, configuring the Web Server to deny requests with 'hex encoded' characters is the way to go.
upvoted 0 times
...
Jamal
1 months ago
User 1: I agree, option A seems like the best choice.
upvoted 0 times
...
...
Michal
2 months ago
I disagree, I believe option B is more effective in detecting strange Unicode requests.
upvoted 0 times
...
Dewitt
2 months 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?
upvoted 0 times
...
Margarett
2 months 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!
upvoted 0 times
Lorrine
1 months ago
Ryann: Let's make sure our defenses are strong against those sneaky attacks.
upvoted 0 times
...
Kate
1 months ago
User 3: Definitely, we need to configure the Web Server to deny those requests.
upvoted 0 times
...
Ryann
2 months ago
User 2: I agree, option A sounds like the best way to block them from getting in.
upvoted 0 times
...
Stephanie
2 months ago
User 1: Yeah, those attackers sure do love their hex-encoded characters.
upvoted 0 times
...
...
Denny
2 months ago
I think option A is the best choice to protect from these attacks.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77