New Year Sale 2026! 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 US
Mob_nav_barsMENU

GIAC GCCC Exam - Topic 8 Question 58 Discussion

Actual exam question for GIAC's GCCC exam
Question #: 58
Topic #: 8
[All GCCC Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: D

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

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Delpha
3 months ago
Really? I doubt these settings are that bad.
upvoted 0 times
...
Malinda
3 months ago
D sounds extreme—how can they not be unlocked?
upvoted 0 times
...
Adolph
3 months ago
C seems unlikely; complexity rules shouldn't change with lockout settings.
upvoted 0 times
...
Lina
4 months ago
I think B is a bigger issue—users getting locked out is no joke!
upvoted 0 times
...
Lenna
4 months ago
A is definitely a risk, especially with weak passwords.
upvoted 0 times
...
Jannette
4 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.
upvoted 0 times
...
Edwin
4 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.
upvoted 0 times
...
Genevieve
4 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.
upvoted 0 times
...
Irene
5 months ago
I remember studying account lockout policies, and I think a shorter lockout duration might make brute-force attacks easier.
upvoted 0 times
...
Queen
5 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.
upvoted 0 times
...
Chauncey
5 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.
upvoted 0 times
...
Hermila
5 months 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.
upvoted 0 times
...
Karol
5 months ago
Hmm, this looks like a tricky one. I'll need to carefully analyze the account lockout policy settings to determine the potential risks.
upvoted 0 times
...
Ligia
5 months 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.
upvoted 0 times
...
Dan
9 months 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!
upvoted 0 times
...
Carey
9 months 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.
upvoted 0 times
Tamekia
8 months ago
D) Once accounts are locked, they cannot be unlocked.
upvoted 0 times
...
Daren
8 months ago
C) Password length and complexity will be automatically reduced.
upvoted 0 times
...
Kenneth
8 months ago
B) Legitimate users could be unable to access resources.
upvoted 0 times
...
Felicidad
9 months ago
A) Brute-force password attacks could be more effective.
upvoted 0 times
...
...
Janessa
10 months 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.
upvoted 0 times
...
Jesusita
10 months 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.
upvoted 0 times
Barney
8 months ago
Carey: Exactly, finding the right balance is key to maintaining both security and productivity.
upvoted 0 times
...
Carey
8 months ago
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.
upvoted 0 times
...
Ulysses
9 months ago
User 1: Yeah, setting the Account Lockout Policy too strict can definitely cause issues for legitimate users.
upvoted 0 times
...
...
Barrie
10 months ago
But wouldn't it also make brute-force password attacks more effective if the lockout policy is too lenient?
upvoted 0 times
...
Gail
10 months ago
I agree with Charlesetta. If the account lockout policy is too strict, it could prevent legitimate users from accessing their accounts.
upvoted 0 times
...
Mirta
11 months 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!
upvoted 0 times
Helene
10 months ago
B) Legitimate users could be unable to access resources.
upvoted 0 times
...
Helene
10 months ago
A) Brute-force password attacks could be more effective.
upvoted 0 times
...
...
Charlesetta
11 months ago
I think the risk presented by these settings is that legitimate users could be unable to access resources.
upvoted 0 times
...

Save Cancel