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

GIAC GCCC Exam - Topic 8 Question 58 Discussion

Posted by Tijuana on Sep 14, 2024 at 08:40 AM

An organization is implementing a control for the Account Monitoring and Control CIS Control, and have set the Account Lockout Policy as shown below. What is the risk presented by these settings?

Suggested Answer: D

Get Premium GCCC Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
31 comments · newest first
DE
Delpha 10 months ago
Really? I doubt these settings are that bad.
MA
Malinda 11 months ago
D sounds extreme—how can they not be unlocked?
AD
Adolph 11 months ago
C seems unlikely; complexity rules shouldn't change with lockout settings.
LI
Lina 11 months ago
I think B is a bigger issue—users getting locked out is no joke!
LE
Lenna 11 months ago
A is definitely a risk, especially with weak passwords.
JA
Jannette 11 months ago
I vaguely remember a practice question where accounts could be permanently locked out if not configured correctly. That could be a risk too.
ED
Edwin 12 months ago
I think option C is tricky; I don't recall anything about password length being affected by lockout settings, but it sounds plausible.
GE
Genevieve 12 months ago
I'm not entirely sure, but I feel like if the settings are too strict, legitimate users could get locked out and that would be a big issue.
IR
Irene 12 months ago
I remember studying account lockout policies, and I think a shorter lockout duration might make brute-force attacks easier.
QU
Queen 12 months ago
I think the key here is to understand how the lockout policy interacts with password complexity and length requirements. That could be the key to identifying the main risk.
CH
Chauncey 12 months ago
Wait, I'm not sure I understand. Could the settings actually make brute-force attacks more effective? I'll need to think this through.
HE
Hermila 1 year ago
Okay, let's see here. The policy seems pretty strict, so I'm guessing the main risk is that legitimate users could get locked out of their accounts.
KA
Karol 1 year ago
Hmm, this looks like a tricky one. I'll need to carefully analyze the account lockout policy settings to determine the potential risks.
LI
Ligia 1 year ago
Okay, let me see. The All users group is likely used to grant access to common features and functionality that all users should have access to. I'm guessing the answer is D, Console and common features.
DA
Dan 1 year ago
I bet the organization's cybersecurity team was like, 'Let's make it so secure, even our own employees can't get in!' Brilliant!
CA
Carey 1 year ago
Once locked, accounts can't be unlocked? Wow, that's like a one-way ticket to the password graveyard. Guess the IT team will be busy resetting passwords all day.
TA
Tamekia 1 year ago
↳ replying to Carey
D) Once accounts are locked, they cannot be unlocked.
DA
Daren 1 year ago
↳ replying to Carey
C) Password length and complexity will be automatically reduced.
KE
Kenneth 1 year ago
↳ replying to Carey
B) Legitimate users could be unable to access resources.
FE
Felicidad 1 year ago
↳ replying to Carey
A) Brute-force password attacks could be more effective.
JA
Janessa 1 year ago
Password length and complexity reduced? Well, that's one way to make it easier for everyone to remember their passwords. Maybe they should just use '12345' instead.
JE
Jesusita 1 year ago
Okay, so legitimate users might get locked out? Sounds like a great way to keep them from accessing the resources they need. Productivity is overrated anyway.
BA
Barney 1 year ago
↳ replying to Jesusita
Carey: Exactly, finding the right balance is key to maintaining both security and productivity.
CA
Carey 1 year ago
↳ replying to Jesusita
User 2: Agreed, it's a fine line between security and usability. We don't want to lock out the people who actually need access.
UL
Ulysses 1 year ago
↳ replying to Jesusita
User 1: Yeah, setting the Account Lockout Policy too strict can definitely cause issues for legitimate users.
BA
Barrie 1 year ago
But wouldn't it also make brute-force password attacks more effective if the lockout policy is too lenient?
GA
Gail 1 year ago
I agree with Charlesetta. If the account lockout policy is too strict, it could prevent legitimate users from accessing their accounts.
MI
Mirta 1 year ago
Looks like these settings could make brute-force attacks a walk in the park. Might as well leave the door wide open for hackers!
HE
Helene 1 year ago
↳ replying to Mirta
B) Legitimate users could be unable to access resources.
HE
Helene 1 year ago
↳ replying to Mirta
A) Brute-force password attacks could be more effective.
CH
Charlesetta 2 years ago
I think the risk presented by these settings is that legitimate users could be unable to access resources.
0/2000 characters

Save Cancel