MENU
Which of the following is considered a best practice for hardening SSHD?
Suggested Answer: C
Get Premium LFCA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
WI
Willow
11 months ago
Portknocking? I've heard of it, but does it really add that much security?
CA
Cassi
11 months ago
Completely disabling ssh access isn't practical for most setups.
VA
Valentine
12 months ago
Wait, renaming root? That sounds risky.
TA
Tawna
12 months ago
I agree, option C is the way to go!
OR
Orville
1 year ago
Disabling ssh access for root is definitely a best practice.
LA
Lavelle
1 year ago
Portknocking sounds familiar, but I can't recall if it's really considered a best practice for SSH hardening.
EZ
Ezekiel
1 year ago
I feel like renaming root to a random name could be a security measure, but it seems a bit extreme.
LI
Lisandra
1 year ago
I remember practicing a question about hardening SSHD, and I think completely disabling SSH access isn't practical for most setups.
JO
Joye
1 year ago
I think disabling SSH access for root is a common recommendation, but I'm not entirely sure if it's the best practice.
FE
Fernanda
1 year ago
Renaming root to a random name? That's an interesting idea, but I'm not sure how effective that would be in practice.
NI
Nickole
1 year ago
Completely disabling SSH access doesn't seem like the right approach. We still need to be able to access the system remotely.
JO
Jovita
1 year ago
I'm not sure about using portknocking - that seems a bit complicated. I'll have to research that more.
MA
Marsha
1 year ago
Disabling SSH access for root seems like a good option to me. That would help prevent unauthorized access.
DE
Denna
1 year ago
Hmm, this seems like a tricky one. I'll need to think carefully about the best practices for hardening SSHD.
MO
Moon
2 years ago
Portknocking? What is this, the 90s? C is the way to go, folks. Keep it simple, keep it secure.
JA
Jacob
2 years ago
C) Disabling ssh access for root
LA
Lavera
2 years ago
A) Using portknocking to protect ssh access for root
HE
Hermila
2 years ago
Ah, the ol' 'security through obscurity' with option D. I'll stick to the proven method of C, thanks.
AN
Angelyn
2 years ago
User 2: I think option D can also be effective, it adds an extra layer of security.
ER
Eric
2 years ago
User 1: I prefer option C as well, it's a safer choice.
KE
Kenneth
2 years ago
I personally think using portknocking to protect ssh access for root is the best option.
SA
Salome
2 years ago
Disabling SSH altogether? B? No way, that's way too restrictive. Gotta go with C on this one.
AL
Alesia
2 years ago
I agree with Shawnee, disabling ssh access for root is a good security measure.
LE
Lennie
2 years ago
Renaming root? That's just asking for trouble. I'd go with C - simple and effective.
BR
Brunilda
2 years ago
Definitely, it's a simple and effective solution.
TH
Thomasena
2 years ago
Yeah, that sounds like a good idea.
PE
Peggie
2 years ago
I think disabling ssh access for root is the way to go.
OD
Odette
2 years ago
I agree, renaming root seems risky.
MA
Madelyn
2 years ago
Option C seems like the way to go. Disabling root access is a pretty standard security practice.
DO
Donte
2 years ago
Completely disabling ssh access might be too extreme in some cases.
MI
Minna
2 years ago
Using portknocking to protect ssh access for root is another option to consider.
EV
Evelynn
2 years ago
I think renaming root to a random name could also be effective.
AL
Albina
2 years ago
I agree, disabling root access is a good security measure.
SH
Shawnee
2 years ago
I think the best practice is to disable ssh access for root.