MENU
Which of the following event logs contains traces of brute force attempts performed by an attacker?
Suggested Answer: D
Get Premium GPEN Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
30 comments · newest first
OD
Odelia
10 months ago
I've seen brute force attempts logged in SecEvent.Evt too!
CL
Cletus
11 months ago
SysEvent.Evt is not relevant here, just saying.
FI
Filiberto
11 months ago
Wait, are we sure about that? What about WinEvent.Evt?
MO
Mollie
11 months ago
I agree, SecEvent.Evt is the right choice!
JU
Julio
11 months ago
Definitely SecEvent.Evt for brute force logs.
KA
Kati
11 months ago
I feel like I’ve seen similar questions before, and they often point to SecEvent.Evt for tracking unauthorized access attempts.
TI
Tijuana
12 months ago
I’m a bit confused; I thought WinEvent.Evt could also contain relevant information, but now I’m leaning towards SecEvent.Evt.
NA
Nakisha
12 months ago
I remember practicing a question about event logs, and I think brute force attempts are usually recorded in security logs.
FR
Francoise
12 months ago
I think it might be SecEvent.Evt since it deals with security logs, but I'm not completely sure.
LE
Leonor
12 months ago
I'm feeling pretty confident about this one. The security event log is where I'd expect to find traces of brute force attacks, so I'm going to go with that option.
EL
Elina
12 months ago
Okay, I've got a strategy for this. I'll start by eliminating the logs that are less likely to contain that kind of information, like the application log. Then I'll focus on the security and system event logs to see if I can find any clues about brute force attempts.
QU
Quentin
12 months ago
Hmm, I'm not totally sure about this one. I'll need to think through the different event logs and what kind of information they might contain related to brute force attacks.
GA
Gail
1 year ago
This one seems pretty straightforward. I'd focus on looking for logs that would contain information about failed login attempts or other suspicious activity.
MO
Mozelle
2 years ago
SecEvent.Evt, for sure. It's like the bouncer of the event logs, keeping the troublemakers out and the security team informed.
AR
Arletta
2 years ago
Hmm, I'd have to say SecEvent.Evt. That's the event log that's like the secret agent of the bunch, keeping an eye on all the undercover stuff going on.
SO
Sol
2 years ago
SecEvent.Evt is the one you want. That's where the security team keeps a close eye on any suspicious activity. Wouldn't want to miss out on those hacker shenanigans!
HA
Hana
2 years ago
Good to know! I'll be sure to pay extra attention to SecEvent.Evt from now on.
CO
Colton
2 years ago
Yeah, the security team always monitors SecEvent.Evt closely for any signs of hackers trying to break in.
CO
Corinne
2 years ago
Thanks for the tip! I'll make sure to keep an eye on SecEvent.Evt for any suspicious activity.
MA
Ma
2 years ago
SecEvent.Evt is definitely the one to check for those brute force attempts.
KE
Kerry
2 years ago
I think SysEvent.Evt might contain other types of logs, not necessarily brute force attempts.
JE
Jesusa
2 years ago
I'm not sure, but I think it could also be A) SysEvent.Evt.
MI
Micheal
2 years ago
I agree with Allene, SecEvent.Evt makes sense for brute force attempts.
LI
Lindsey
2 years ago
I'm going with D. SecEvent.Evt. That's the event log that records all the security-related activities, including those sneaky brute force attempts.
AM
Amie
2 years ago
Yeah, SecEvent.Evt is where you'll find those brute force attempts.
JU
Juan
2 years ago
I agree, D. SecEvent.Evt is the right choice for that.
AL
Allene
2 years ago
I think the answer is D) SecEvent.Evt.
SU
Suzan
2 years ago
SecEvent.Evt, definitely! That's where you'll find all the juicy details on those pesky hackers trying to crack into the system.
ZA
Zack
2 years ago
I agree, SecEvent.Evt is the right choice. It's important to keep an eye on those brute force attempts.
MA
Marshall
2 years ago
SecEvent.Evt, definitely! That's where you'll find all the juicy details on those pesky hackers trying to crack into the system.