Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Mastering Linux Security and Hardening

Mastering Linux Security and Hardening

Secure your Linux server and protect it from intruders, malware attacks, and other external threats
Turn a Linux server into a harder target, without mistaking a clean scan for safety.
by Donald A. Tevault 2018 376 pages
4.32
19 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

A safer starting point. Linux has useful security advantages: it separates ordinary users from administrators, supports strict file permissions, and includes tools such as SELinux or AppArmor. Those advantages are not immunity. Poor configuration, delayed updates, vulnerable applications, and stolen credentials still expose systems. Attackers have used Linux servers for denial-of-service botnets, ransomware, and unauthorized cryptocurrency mining. A carelessly exposed private key can be just as damaging as a software flaw.

Practice without risking production. The book recommends building Ubuntu and CentOS virtual machines, then taking snapshots before experiments. A snapshot makes it possible to restore a known-good system after a firewall rule or permission change goes wrong. Security is ongoing administration, not a feature switched on at installation.

Analysis

The useful distinction is between a secure-capable operating system and a secure deployment. Linux's user separation gives administrators strong tools, but those tools depend on choices about updates, services, and access. This resembles safety engineering: a reliable component cannot compensate for a hazardous system design. Virtual machines make experimentation safer, though they do not replace testing against the actual distribution and workload. The book's threat examples also broaden the picture beyond viruses. An attacker may want computing power, credentials, or access to other systems, not merely a way to infect a desktop.

Replace shared root access with logged, narrowly scoped sudo permissions

Separate identity from authority. The root account can alter nearly anything, so using it for routine work magnifies both mistakes and intrusions. The `sudo` utility lets administrators grant elevated rights to named users, groups, or aliases, while recording which commands they run. A backup administrator might receive backup commands, while a service operator can be limited to checking or restarting one daemon. Users authenticate with their own account credentials instead of sharing the root password.

Constrain the command, not just the person. A rule that grants an editor such as Vim may also grant a shell escape, which can become unrestricted root access. The book recommends `sudoedit` for controlled file editing and warns that broad permissions for tools such as `systemctl` can exceed the intended task. Avoid passwordless sudo as a default.

Analysis

This is least privilege made operational: access is attached to a person and a task, rather than to a communal superuser identity. The audit trail improves accountability, but it is not a complete record if users can enter a persistent root shell or exploit an allowed program to escape its limits. Sudo rules therefore need testing as carefully as application permissions. Narrow delegation can also reduce operational bottlenecks, provided the task definitions reflect real work instead of becoming so restrictive that staff invent unsafe workarounds.

Treat accounts, home directories, and passwords as separate attack surfaces

Close routine openings. User security includes more than choosing a password. The book contrasts restrictive home directories created by default on Red Hat-family systems with Ubuntu's more permissive defaults, and shows how administrators can set new homes to owner-only access. Temporary accounts should have explicit expiration dates, while departing or inactive users may need to be locked rather than deleted, especially when records must be retained.

Choose policy deliberately. PAM's `pwquality` module can enforce length and character rules. The book also notes the tension between complex, frequently changed passwords and memorable passphrases, recommending that administrators follow organizational requirements while avoiding predictable personal details. `chage` manages password and account expiration. PAM's `pam tally2` can lock accounts after repeated failures; the book demonstrates four failed attempts for a lab, but argues that production thresholds should avoid needless lockouts and help-desk burden.

Analysis

Account controls combine confidentiality, availability, and administration. Restrictive home directories prevent casual snooping, while expiration policies limit forgotten access. Password composition rules are less valuable when they encourage predictable substitutions or unsafe reuse; passphrases help only when they are unique and not built from public biographical facts. Lockouts create another tradeoff: they slow guessing but can let an attacker deny service by deliberately failing logins. A sound policy considers remote access protections, recovery procedures, and user behavior together rather than treating one password rule as the whole defense.

Build firewalls as explicit allowlists, then make rules survive reboot

Permit only required traffic. Linux's kernel firewall framework is Netfilter; tools such as `iptables`, Ubuntu's UFW, Red Hat-family `firewalld`, and `nftables` configure it in different ways. The basic host-firewall pattern is to allow loopback traffic and responses to connections the machine initiated, open only the required inbound services, and block other incoming traffic. Rule order matters: an early block can make a later allow rule useless.

Check both effect and persistence. UFW offers a simpler interface, while `firewalld` organizes rules into zones and named services. With `firewalld`, a runtime change may disappear after reboot unless it is saved as permanent and reloaded. The book also presents `nftables` as a unified approach for multiple network protocol families. Before changing a remote firewall, preserve a safe access path and verify the rules, including IPv6 where applicable.

Analysis

An allowlist turns a vague question, what should be blocked, into a more auditable one: which connections does this machine actually need? That is powerful, but firewall simplicity can hide dependencies. A server may rely on monitoring, backups, name resolution, or management traffic that is easy to overlook. Testing should therefore include normal service behavior, not just whether the administrator can still connect. The distinction between runtime and saved configuration is also a useful general operations lesson: security settings that vanish on restart are temporary defenses, not durable policy.

Encrypt stored data and harden SSH, because permissions alone cannot stop theft

Protect data in different states. File permissions control access while a system is running, but encryption can protect data if a drive or device is removed. The book covers GPG for individual files and signed messages, LUKS for encrypted disks or partitions, eCryptfs for encrypted directories, and VeraCrypt for portable encrypted containers shared across operating systems. Encryption also creates recovery duties: passphrases and recovery information must be protected, and backups must be tested.

Harden remote access. SSH encrypts remote sessions and file transfers, but password logins invite automated guessing. The book advises disabling obsolete SSH protocol version 1, using public-key authentication, and disallowing root login. Password authentication should be disabled only after key access has been tested. Protect private keys with a passphrase and keep them private; a public key can be shared, but it does not substitute for verifying whose key it is.

Analysis

Encryption protects against a different failure than permissions do. Permissions mediate ordinary access; full-disk encryption can reduce the consequences of physical loss, but it does not stop a compromised, unlocked machine from exposing data. Key handling is therefore part of the security design, not an afterthought. SSH keys likewise shift the authentication problem rather than erasing it: a stolen, unprotected private key can be as useful to an attacker as a password. The strongest arrangement matches each control to a threat and includes a tested route to recover legitimate access.

Combine Linux permissions, ACLs, and shared-folder safeguards deliberately

Use ordinary permissions first. Linux discretionary access control assigns file ownership and read, write, and execute permissions to an owner, a group, and others. The book explains numeric modes such as `700` for private owner access and warns that SUID or SGID on executables can grant unexpected privileges. Administrators can inventory these special files and investigate additions. Extended attributes can also make a file append-only or immutable, although they do not replace access controls.

Make collaboration safer. Access Control Lists, or ACLs, grant specific users or groups additional permissions. For a shared directory, SGID makes new files inherit the directory's group, while the sticky bit stops users from deleting one another's files. ACLs can restrict an individual file further. Backups must preserve ACL metadata: the book shows that `tar` needs its ACL option during both backup and restoration.

Analysis

The shared-directory example reveals that group access is a social design problem as much as a permissions puzzle. Members may need to create common files without gaining authority to erase one another's work. SGID and the sticky bit address those separate needs, while ACLs handle exceptions. Complexity has a cost, however: layered permissions become hard to reason about unless they are documented and audited. Backup fidelity belongs in the same design conversation, since restoring file contents but losing their access rules can silently undo the intended boundary.

Keep SELinux or AppArmor enforcing, and diagnose denials instead of disabling them

Add a second access boundary. Mandatory Access Control, or MAC, lets system policy restrict what processes may do even when ordinary file permissions would allow it. SELinux labels processes and objects with security contexts and applies policy to their interactions. AppArmor assigns profiles to applications and restricts access by path. The book uses a web server example: a file moved from a home directory can retain the wrong SELinux type, preventing Apache from reading it.

Fix the policy precisely. Tools such as `restorecon`, `semanage`, and SELinux troubleshooting messages can help correct labels or approved policy settings. AppArmor profiles can be inspected and adjusted when logs show a blocked operation. Permissive or complain modes can help reveal several violations during testing, but enforcement should be restored after troubleshooting. Disabling MAC to make an application work removes a valuable barrier against exploited services.

Analysis

MAC is valuable because it limits damage after an application is compromised. A web server that can read only intended content has fewer opportunities to expose unrelated files. That containment principle appears in sandboxing across operating systems. The practical challenge is that policy denials can resemble ordinary application failures, so good logs and a deliberate test process matter. Conversely, not every denial is a bug: a policy may be correctly blocking an unsafe behavior. The administrator's task is to distinguish a needed permission from a risky convenience, then grant the smallest adequate exception.

Audit sensitive actions, but do not mistake logs for prevention

Record meaningful events. The `auditd` system can watch a sensitive file or directory, track selected permissions, or record system calls associated with a user. Rules can be made persistent through configuration files. The book demonstrates watching `/etc/passwd` for changes and monitoring a protected shared directory. `ausearch` and `aureport` help turn audit records into searchable events and summaries.

Keep the signal usable. Auditing records activity; it does not stop a breach. Broad rules can generate a flood of records because ordinary logins and applications touch many files. The book's example of monitoring every file-open call for one user captures routine system activity as well as deliberate actions. Start with a specific question, choose a narrow rule, and correlate audit output with authentication or system logs before concluding that an event was malicious.

Analysis

Audit data is most useful when it answers a defined question: who changed this file, or who tried to enter this directory? Without that focus, abundant logs can make meaningful events harder to spot. This is the same signal-to-noise problem found in measurement systems: collecting more observations does not automatically produce more knowledge. Auditing also depends on retention, time synchronization, and protection of the logs themselves. The book's central distinction is essential: prevention controls reduce opportunities, while audit records support investigation and accountability after or during an event.

Use scans to discover vulnerabilities, not to certify safety

Match the scanner to the question. The book surveys ClamAV and Linux Malware Detect for malware checks, Rootkit Hunter for rootkit indicators, Lynis for local configuration review, OpenVAS for remote vulnerability assessment, and Nikto for web-server weaknesses. Snort monitors network traffic for suspicious patterns; Security Onion packages network monitoring tools into a ready-to-use environment. Each tool sees a different slice of risk, and a clean result from one is not evidence that other risks are absent.

Investigate findings. Scans can reveal obsolete services, weak SSH settings, risky web methods, or unexpected ports. Findings still require context: a service may be necessary, and a reported weakness may need verification. Keep signatures and software updated, check the configuration behind a warning, and fix confirmed issues. Network intrusion detection can alert or block according to its rules, but false positives and blind spots make human interpretation necessary.

Analysis

A scanner is a measurement instrument, not a verdict. Host-based tools can inspect details unavailable to a remote scanner, while network tools can reveal exposures administrators did not realize were reachable. Combining views reduces blind spots, but overlapping tools can also produce duplicate alerts and false confidence. A useful security program assigns ownership to findings, tracks remediation, and rescans to verify changes. Detection systems such as Snort add another layer, yet they cannot compensate for weak access control or unpatched software on the systems they observe.

Automate baselines, then verify the controls scripts cannot set

Apply a known standard. SCAP is a framework for expressing security guidance and checks. OpenSCAP can assess a Linux system against profiles such as PCI-DSS or government-oriented baselines, produce reports, and remediate some findings. The book shows that automated remediation can set password controls and install tools, but it can also report errors or leave items for an administrator. A compliance result is a starting point for review, not proof that a system is safe in its actual environment.

Plan before installation. Some requirements involve choices automation cannot easily repair, such as separating directories onto distinct partitions. A checklist should guide the initial design. Administrators should also review listening services with tools such as `systemctl`, `netstat`, or Nmap, and consider physical protections such as bootloader passwords, firmware settings, and disk encryption where the threat warrants them.

Analysis

Automation makes repeatable baselines practical, especially across many machines, but compliance and security are related rather than identical goals. A system can satisfy a checklist while retaining an unexamined application risk, and a scanner cannot infer every business need. The book's emphasis on planning before installation is therefore important: some security properties depend on architecture, not a late configuration toggle. Bootloader and firmware controls also illustrate that system security crosses the boundary between operating system and physical access. Standards provide structure, while threat modeling supplies the context.

Analysis

This book is best understood as a practical administrator's field guide, not a single theory of security. Its organizing idea is layered control: limit who can act, limit what exposed services can receive, protect data with encryption, constrain applications with mandatory policy, and gather evidence through audits and scans. The examples make that progression concrete, from a permissive home directory to a narrowly scoped shared folder, and from a firewall rule to a network scan that reveals which services are actually reachable.

The strongest lesson is that security depends on configuration and operational habits, not on choosing Linux. The book repeatedly distinguishes mechanisms that are easy to confuse: encryption protects stored information but does not govern every action on an unlocked system; auditing records behavior but does not prevent it; a firewall controls network paths but cannot repair unsafe application permissions. These distinctions help administrators assign each tool a realistic job.

The material also treats security as an administrative tradeoff. Narrow sudo rules, frequent password prompts, account lockouts, and strict MAC policies can reduce risk, but poorly designed restrictions can frustrate users or interrupt legitimate work. Effective hardening therefore requires testing, documentation, and a way to recover from mistakes. Virtual-machine snapshots provide a low-risk learning environment, while audit logs and scanners help reveal consequences in live systems. A limitation is that the book's command examples and distribution comparisons reflect Linux releases available in 2018. Package names, defaults, firewall backends, and security recommendations can change, so readers should verify procedures against their current distribution and organizational policy before applying them. The enduring value lies less in memorizing commands than in learning the questions behind them: who needs access, which traffic is necessary, what data must remain confidential, what behavior should be recorded, and how can a change be tested safely? A disciplined answer to those questions produces a more defensible system than any single hardening tool.

Summary in 30 Seconds
Linux security depends on careful configuration and continued maintenance, not the operating system alone. Limit elevated privileges to specific users and tasks, allow only necessary inbound traffic, and protect stored data and remote access with encryption and strong authentication. Use file permissions and application-level policies together. Logs record activity but do not prevent attacks, while scans reveal only the risks they are designed to find. Test changes and verify controls against the system's real needs.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.32 out of 5
Average of 19 ratings from Goodreads and Amazon.

Mastering Linux Security and Hardening has received positive reviews, with an overall rating of 4.23 out of 5 based on 13 reviews on Goodreads. Readers have praised it as one of the best books on Linux security. One reviewer specifically mentioned it as the best book they've read on the topic, giving it a rating of 4 out of 5. The book seems to be well-regarded by its audience for its comprehensive coverage of Linux security concepts and practical hardening techniques.

Your rating:
4.53
599 ratings
Want to read the full book?

Glossary

Discretionary Access Control

Owner-managed file access

Discretionary Access Control (DAC) is the conventional Linux model in which file owners and administrators set ownership and permissions for users, groups, and others. Basic permissions govern reading, writing, and execution. Access Control Lists extend this model with more specific grants, but DAC alone does not prevent a permitted process from accessing a file.

Mandatory Access Control

Policy-enforced access limits

Mandatory Access Control (MAC) applies system-enforced rules that users cannot override merely because they own a file or have ordinary access to it. Linux implementations such as SELinux and AppArmor constrain processes according to policy. MAC can limit the damage caused by a compromised service by denying access outside its approved scope.

Access Control List

Fine-grained permission entries

An Access Control List (ACL) adds named-user or named-group permissions to a file or directory beyond the standard owner, group, and other permission classes. ACLs can support specific collaboration needs, such as allowing one colleague to read a file while denying access to other members of a shared group. Linux tools include setfacl and getfacl.

SELinux

Label-based MAC system

SELinux is a Linux Mandatory Access Control system that assigns security contexts to processes and objects, including files, directories, and ports. Policy determines which process types may interact with which object types. Administrators can troubleshoot incorrect labels, inspect policy booleans, and add carefully scoped policy changes rather than disabling enforcement.

AppArmor

Path-based application confinement

AppArmor is a Mandatory Access Control system used by distributions including Ubuntu and SUSE. It confines applications through profiles that specify which paths and operations a program may access. Profiles can be enforced, placed in a complain mode that logs violations without blocking them, or disabled. Its path-based approach differs from SELinux's labeling model.

Linux Unified Key Setup

Linux disk encryption format

Linux Unified Key Setup (LUKS) is a standard mechanism for encrypting Linux block devices, such as partitions or whole disks. An encrypted device is opened with a passphrase or key and then used through a mapped device. LUKS can protect data at rest, including swap when configured appropriately, but recovery depends on safeguarding valid credentials.

eCryptfs

Encrypted directory filesystem

eCryptfs is a Linux filesystem-layer encryption system that can protect individual directories, including user home directories. Files appear in readable form when the encrypted directory is mounted with the appropriate key and appear encrypted when it is unmounted. Recovery information, such as a mount passphrase, must be stored securely.

Security Content Automation Protocol

Machine-readable security guidance

The Security Content Automation Protocol (SCAP) is a set of specifications for expressing security configuration checks and related guidance. OpenSCAP tools can evaluate a system against supported security profiles, create reports, and remediate some findings. SCAP helps standardize assessment, but cannot automatically resolve every architectural or environment-specific requirement.

auditd

Linux security event logging

auditd is the Linux auditing daemon that records events generated by the kernel audit system according to configured rules. Rules can watch files or directories, monitor selected permissions, or record specified system calls. ausearch and aureport help query and summarize events. Auditing supports detection and investigation, but does not itself block access.

Netfilter

Linux kernel packet filtering

Netfilter is the packet-filtering and network-processing framework built into the Linux kernel. Administrators manage it through tools such as iptables, UFW, firewalld, and nftables. These tools differ in syntax and features, but configure rules that accept, reject, or drop network traffic at defined points in packet processing.

firewalld zones

Trust-based firewall rule groups

In firewalld, zones are predefined or custom collections of firewall settings associated with network interfaces or sources. A zone expresses a level or context of trust by allowing selected services, ports, or other rules. Changes can affect the running configuration immediately, but must be saved as permanent and reloaded to persist across restarts.

OpenVAS

Remote vulnerability scanner

The Open Vulnerability Assessment Scanner (OpenVAS) assesses remote hosts or networks for known vulnerabilities and configuration weaknesses. It can scan one system or many and offers different scan profiles with different levels of depth. Results identify issues for investigation and remediation, but they do not establish that a system is free of vulnerabilities.

FAQ

What's Mastering Linux Security and Hardening about?

  • Comprehensive Security Guide: The book provides a detailed exploration of securing Linux systems against various threats, including intruders and malware.
  • Focus on Security Techniques: It covers security and hardening techniques applicable to any Linux-based server or workstation.
  • Practical Techniques: Includes hands-on labs and practical examples, allowing readers to apply security measures directly to their systems.
  • Target Audience: Designed for Linux administrators, regardless of their specialization in security, assuming basic knowledge of Linux command line and essentials.

Why should I read Mastering Linux Security and Hardening?

  • Career Advancement: Learning Linux security is a valuable career move, enhancing your skill set and opening up job opportunities in IT security.
  • Expert Insights: Authored by Donald A. Tevault, the book draws on extensive experience in Linux security, making it a reliable resource.
  • Practical Guidance: Offers hands-on exercises and practical advice, making it easier to implement security measures in real-world scenarios.
  • Stay Updated: Helps you understand the evolving threat landscape and equips you with the knowledge to protect Linux systems effectively.

What are the key takeaways of Mastering Linux Security and Hardening?

  • Layered Security Approach: Emphasizes the importance of a multi-layered security strategy, combining various techniques to protect systems.
  • User and Group Management: Highlights the importance of creating user groups and managing permissions effectively to control access to sensitive files.
  • Regular Auditing and Scanning: Stresses the need for regular system audits and vulnerability scans using tools like Lynis and OpenVAS.

What are the best quotes from Mastering Linux Security and Hardening and what do they mean?

  • "The only operating system you'll ever see that's totally, 100% secure will be installed on a computer that never gets turned on.": Underscores the reality that no system can be completely secure; security is about risk management.
  • "A standard, out-of-the-box configuration of a Linux server is actually quite insecure.": Emphasizes the need for proactive security measures, as default settings often leave systems vulnerable.
  • "Regular audits and scans are essential to maintaining a secure environment.": Encourages administrators to routinely check for vulnerabilities and compliance with security policies.

How does Mastering Linux Security and Hardening address user account security?

  • Dangers of Root Access: Explains the risks associated with logging in as the root user and advocates for using sudo to limit administrative privileges.
  • Password Policies: Emphasizes enforcing strong password criteria and setting up account expiration policies to enhance security.
  • Account Locking: Discusses techniques for locking user accounts and preventing unauthorized access, ensuring only authorized users can access sensitive information.

What firewall utilities are discussed in Mastering Linux Security and Hardening?

  • iptables Overview: Provides an overview of iptables, explaining its role in managing network traffic and setting up firewall rules.
  • firewalld for Red Hat: Covers firewalld, a newer firewall management tool for Red Hat systems, highlighting its dynamic management capabilities.
  • Uncomplicated Firewall (UFW): Discusses UFW as a simplified interface for managing iptables, making it easier to configure firewall settings.

How does Mastering Linux Security and Hardening explain encryption methods?

  • GPG for File Encryption: Introduces GNU Privacy Guard (GPG) for encrypting files and emails, emphasizing its strong encryption algorithms.
  • LUKS for Disk Encryption: Explains how to use LUKS to encrypt entire disks or partitions, providing a secure way to protect sensitive data at rest.
  • eCryptfs for Directory Encryption: Discusses eCryptfs for encrypting individual directories, allowing users to secure specific files without encrypting entire partitions.

What tools does Mastering Linux Security and Hardening recommend for vulnerability scanning?

  • Lynis: Recommended for performing security audits and vulnerability scans, providing a comprehensive overview of system security.
  • OpenVAS: Highlighted as a powerful tool for conducting remote vulnerability assessments, capable of scanning entire networks.
  • Nikto: Recommended for web server security, scanning for vulnerabilities specific to web applications.

How does Mastering Linux Security and Hardening address backup and restore procedures?

  • Importance of Backups: Stresses that regular backups are crucial for data recovery in case of security breaches or data loss.
  • Using tar with ACLs: Explains how to use the tar command with the --acls option to preserve ACLs during backup and restoration processes.
  • Testing Restore Procedures: Advises testing backup and restore procedures regularly to ensure they work as expected.

How does Mastering Linux Security and Hardening explain the use of SELinux and AppArmor?

  • SELinux Overview: Provides a comprehensive introduction to SELinux, explaining its role in enforcing mandatory access control policies.
  • AppArmor Basics: Contrasts SELinux with AppArmor, explaining how AppArmor uses pathname enforcement to control access to resources.
  • Troubleshooting: Includes troubleshooting tips for both SELinux and AppArmor, helping administrators resolve common issues.

What are the recommended practices for securing user accounts in Mastering Linux Security and Hardening?

  • Strong Password Policies: Advises implementing strong password policies, including complexity requirements and regular password expiration.
  • Account Lockout Mechanisms: Discusses the importance of setting up account lockout mechanisms to prevent brute-force attacks.
  • Monitoring User Activity: Emphasizes the need for monitoring user activity through auditing and logging, allowing administrators to detect suspicious behavior.

How does Mastering Linux Security and Hardening suggest handling system updates and patch management?

  • Regular Update Schedule: Recommends establishing a regular schedule for applying system updates and patches to ensure vulnerabilities are addressed promptly.
  • Using Package Managers: Explains how to use package managers like apt and yum to manage software updates efficiently.
  • Testing Updates: Advises testing updates in a staging environment before deploying them to production systems to ensure they do not disrupt critical services.

About the Author

Donald A. Tevault is the author of "Mastering Linux Security and Hardening." While specific information about the author is not provided in the given documents, it can be inferred that Tevault is knowledgeable in the field of Linux security and system administration. His work on this book suggests expertise in Linux operating systems, security practices, and hardening techniques. Tevault's ability to write a well-received book on such a technical subject indicates a deep understanding of the topic and likely stems from practical experience in the field. His contribution to Linux security literature has been appreciated by readers seeking to enhance their knowledge in this area.

Download PDF

To save this Mastering Linux Security and Hardening summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.32 MB     Pages: 22

Download EPUB

To read this Mastering Linux Security and Hardening summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.43 MB     Pages: 28
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 25,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...