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 10 Question 68 Discussion

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

An organization has implemented a control for Controlled Use of Administrative Privileges. They are collecting audit data for each login, logout, and location for the root account of their MySQL server, but they are unable to attribute each of these logins to a specific user. What action can they take to rectify this?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Chauncey at Mar 07, 2025, 08:36 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
Bulah
3 months ago
Blacklisting apps sounds like overkill for this situation.
upvoted 0 times
...
Laurena
3 months ago
SELinux is great, but it won't solve the user attribution problem.
upvoted 0 times
...
Barrie
3 months ago
Isn't it surprising they can't attribute logins? That's a basic security issue!
upvoted 0 times
...
Glenn
4 months ago
I disagree, forcing root access from the console seems too limiting.
upvoted 0 times
...
Dong
4 months ago
Option C is the best choice! Using 'sudo' is a good practice.
upvoted 0 times
...
Annett
4 months ago
I vaguely recall SELinux being mentioned in relation to security, but I can't remember how it ties into MySQL. Is turning it on really going to help with user attribution?
upvoted 0 times
...
Gennie
4 months ago
I feel like we covered something similar in practice questions. Using 'sudo' for privileged actions definitely helps with accountability, but I'm not confident if it's the best choice here.
upvoted 0 times
...
Arminda
4 months ago
I'm not entirely sure, but I think option A could help by restricting access to the console. But wouldn't that just make it harder for admins to manage the server?
upvoted 0 times
...
Latia
5 months ago
I remember discussing the importance of limiting root access in our last study group. Forcing users to use 'sudo' seems like a good way to track who is doing what.
upvoted 0 times
...
Alex
5 months ago
I've got this one! The solution is to turn on SELinux and user process accounting for the MySQL server. That way, they can monitor and attribute the root account activity to individual users.
upvoted 0 times
...
Leanna
5 months ago
Okay, let me think this through. I believe the answer is to force user accounts to use 'sudo' for privileged use, which would allow them to track which specific users are accessing the root account.
upvoted 0 times
...
Farrah
5 months ago
Hmm, I'm a bit confused by this one. I'm not sure which of these options would be the best way to address the issue of not being able to identify the specific users logging in as root.
upvoted 0 times
...
Ashton
5 months ago
This seems like a straightforward question about controlling administrative privileges. I think the key is to find a way to attribute the root account logins to specific users.
upvoted 0 times
...
Aleisha
9 months ago
Ah, the age-old question of how to properly attribute logins to users. I bet the person who wrote this question has never actually worked with a real-world MySQL server. Option C all the way!
upvoted 0 times
...
Deeanna
10 months ago
Haha, Blacklisting client applications from running in privileged mode? That's like trying to put a bandaid on a broken leg. Not a real solution if you ask me.
upvoted 0 times
Scarlet
8 months ago
C) Force user accounts to use 'sudo' for privileged use.
upvoted 0 times
...
Blossom
8 months ago
B) Turn on SELinux and user process accounting for the MySQL server.
upvoted 0 times
...
Christoper
8 months ago
A) Force the root account to only be accessible from the system console.
upvoted 0 times
...
...
Nickolas
10 months ago
I don't know, B seems like a really complex solution. Why not just force user accounts to use 'sudo' for privileged use? That seems like the simplest and most straightforward option.
upvoted 0 times
Yuonne
9 months ago
C) Force user accounts to use 'sudo' for privileged use.
upvoted 0 times
...
Reuben
10 months ago
B) Turn on SELinux and user process accounting for the MySQL server.
upvoted 0 times
...
Tess
10 months ago
A) Force the root account to only be accessible from the system console.
upvoted 0 times
...
...
Ceola
10 months ago
Option A seems like the best solution to me. By forcing the root account to only be accessible from the system console, they can ensure that all logins are properly attributed to a specific user.
upvoted 0 times
Laine
9 months ago
B) Turn on SELinux and user process accounting for the MySQL server.
upvoted 0 times
...
Yaeko
10 months ago
A) Force the root account to only be accessible from the system console.
upvoted 0 times
...
...
Cletus
11 months ago
I see both points, but I think option A could also work. By forcing the root account to only be accessible from the system console, it limits who can login and helps with attribution.
upvoted 0 times
...
Terrilyn
11 months ago
I disagree, I believe option C is the way to go. Forcing user accounts to use 'sudo' for privileged use will help track who is accessing the root account.
upvoted 0 times
...
Miss
11 months ago
I think option B is the best choice. Turning on SELinux and user process accounting can help attribute logins to specific users.
upvoted 0 times
...

Save Cancel