Free to read · Three levels

Linux Security: authority, boundaries, and effective evidence

A complete course connecting workload requirements to process identity, resource access, policies, updates, and verification, using synthetic local models only.

18 lessonsEnglish + ArabicContent reviewed
Start learning

In this course

Follow a fictional report worker reading public workshop schedules and writing scoped summaries. Basic lessons develop protected outcomes, identity domains, process credentials, mode permissions, ACLs, creation masks, path resolution, capabilities, and configuration baselines. Each lesson distinguishes requirement, mechanism, and evidence.

Intermediate lessons connect systemd execution boundaries, AppArmor states, network policy models, APT trust, runtime evidence, diagnostics, and remote access. Advanced lessons cover namespaces/seccomp, races, encryption, backups/recovery, incident decisions, verification, and a least-privilege worker package.

English and Arabic provide complete teaching with identical identifiers, code, and technical outputs. Complete programs operate on inert sets, dictionaries, integers, strings, and lexical paths. Platform configuration fragments remain non-runnable. The course neither audits the host nor changes an account, permission, firewall, identity, service, network, or device, and runs no scanner or dependency installation.

What you will learn

  • Define a workload’s purpose, required authority, and protected invariants.
  • Interpret identity scope, access layers, capabilities, and paths without universalizing simplified models.
  • Review services, policies, networking, packages, logs, and SSH under identified version assumptions.
  • Present verification, change, and recovery evidence distinguishing intent, loaded state, observed behavior, and missing evidence.

Your learning path

Three levels

Who this is for

  • Developers, systems engineers, and reviewers who want Linux security reasoning without blindly copying universal settings.
  • Learners connecting permissions, policies, and workload lifecycle to actual evidence and explicit limitations.

Before you start

  • Basic familiarity with files, processes, JSON, and programming functions.
  • Ability to read short Python and illustrative configuration fragments; validation uses an already available interpreter without package installation.