U.S. Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25

- Free Preparation Discussions

Linux Foundation LFCA Exam - Topic 2 Question 38 Discussion

Actual exam question for Linux Foundation's LFCA exam

Question #: 38
Topic #: 2

[All LFCA Questions]

Which of the following is considered a best practice for hardening SSHD?

AUsing portknocking to protect ssh access for root

BCompletely disabling ssh access

CDisabling ssh access for root

DRenaming root to a random name

Show Suggested Answer

Suggested Answer: C

by Jina at Feb 06, 2025, 04:49 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Willow

7 months ago

Portknocking? I've heard of it, but does it really add that much security?

upvoted 0 times

...

Cassi

7 months ago

Completely disabling ssh access isn't practical for most setups.

upvoted 0 times

...

Valentine

7 months ago

Wait, renaming root? That sounds risky.

upvoted 0 times

...

Tawna

7 months ago

I agree, option C is the way to go!

upvoted 0 times

...

Orville

8 months ago

Disabling ssh access for root is definitely a best practice.

upvoted 0 times

...

Lavelle

8 months ago

Portknocking sounds familiar, but I can't recall if it's really considered a best practice for SSH hardening.

upvoted 0 times

...

Ezekiel

8 months ago

I feel like renaming root to a random name could be a security measure, but it seems a bit extreme.

upvoted 0 times

...

Lisandra

8 months ago

I remember practicing a question about hardening SSHD, and I think completely disabling SSH access isn't practical for most setups.

upvoted 0 times

...

Joye

8 months ago

I think disabling SSH access for root is a common recommendation, but I'm not entirely sure if it's the best practice.

upvoted 0 times

...

Fernanda

8 months ago

Renaming root to a random name? That's an interesting idea, but I'm not sure how effective that would be in practice.

upvoted 0 times

...

Nickole

8 months ago

Completely disabling SSH access doesn't seem like the right approach. We still need to be able to access the system remotely.

upvoted 0 times

...

Jovita

8 months ago

I'm not sure about using portknocking - that seems a bit complicated. I'll have to research that more.

upvoted 0 times

...

Marsha

8 months ago

Disabling SSH access for root seems like a good option to me. That would help prevent unauthorized access.

upvoted 0 times

...

Denna

9 months ago

Hmm, this seems like a tricky one. I'll need to think carefully about the best practices for hardening SSHD.

upvoted 0 times

...

Moon

1 year ago

Portknocking? What is this, the 90s? C is the way to go, folks. Keep it simple, keep it secure.

upvoted 0 times

Jacob

1 year ago

C) Disabling ssh access for root

upvoted 0 times

...

Lavera

1 year ago

A) Using portknocking to protect ssh access for root

upvoted 0 times

...

...

Hermila

1 year ago

Ah, the ol' 'security through obscurity' with option D. I'll stick to the proven method of C, thanks.

upvoted 0 times

Angelyn

1 year ago

User 2: I think option D can also be effective, it adds an extra layer of security.

upvoted 0 times

...

Eric

1 year ago

User 1: I prefer option C as well, it's a safer choice.

upvoted 0 times

...

...

Kenneth

1 year ago

I personally think using portknocking to protect ssh access for root is the best option.

upvoted 0 times

...

Salome

1 year ago

Disabling SSH altogether? B? No way, that's way too restrictive. Gotta go with C on this one.

upvoted 0 times

...

Alesia

1 year ago

I agree with Shawnee, disabling ssh access for root is a good security measure.

upvoted 0 times

...

Lennie

1 year ago

Renaming root? That's just asking for trouble. I'd go with C - simple and effective.

upvoted 0 times

Brunilda

1 year ago

Definitely, it's a simple and effective solution.

upvoted 0 times

...

Thomasena

1 year ago

Yeah, that sounds like a good idea.

upvoted 0 times

...

Peggie

1 year ago

I think disabling ssh access for root is the way to go.

upvoted 0 times

...

Odette

1 year ago

I agree, renaming root seems risky.

upvoted 0 times

...

...

Madelyn

1 year ago

Option C seems like the way to go. Disabling root access is a pretty standard security practice.

upvoted 0 times

Donte

1 year ago

Completely disabling ssh access might be too extreme in some cases.

upvoted 0 times

...

Minna

1 year ago

Using portknocking to protect ssh access for root is another option to consider.

upvoted 0 times

...

Evelynn

1 year ago

I think renaming root to a random name could also be effective.

upvoted 0 times

...

Albina

1 year ago

I agree, disabling root access is a good security measure.

upvoted 0 times

...

...

Shawnee

1 year ago

I think the best practice is to disable ssh access for root.

upvoted 0 times

...