A Linux host may have a public web page, maintenance access, and background services. Begin by writing down what each service does and who should reach it. You can then look for access that has no clear purpose.
Linux Hardening · Lesson 1
Attack Surface
Learn to identify what a Linux host needs to expose and which access paths deserve review.
Listing Intended Access
A simple inventory connects a resource to the people or programs that need it. Here is a practice host.
Resource Intended access
Public homepage Visitors
Maintenance SSH Operations team
Preview panel Local staff on this host only
An access path is a way a user or program reaches a resource. The set of reachable interfaces through which someone could affect a system is part of its attack surface.
Which resource in this inventory needs a public network path?
Comparing Intended and Observed Access
Suppose the preview panel is reachable over the network and the inventory still says local only. Check with the owner and verify the actual route before changing it. A service can need to run while having no need to accept remote requests.
Which observation deserves review under the stated policy?
Prioritizing What to Check
Start with access that is both unnecessary and consequential. In a practice example, a preview panel that can change the site is a higher priority than an unused service with no important data. Record the intended audience, the observed exposure, and the test that would confirm the proposed restriction works without disrupting legitimate users.
After changing preview access, which two observations would confirm that the restriction met the goal?
Lesson complete
You finished Attack Surface
You can now identify which access paths deserve hardening review.
Describe a resource and its intended audience.
Compare intended and observed access.
Verify both protection and legitimate use after a change.
Keep your learning progress
Create a free account to save this lesson and continue learning on any device.
Create a free account