Linux Security / Basic: identity, resources, and evidence

Linux Security โ€” Basic: identity, resources, and evidence

Define workload boundaries and reason about credentials, DAC/ACL, paths, capabilities, and baselines.

6 lessons ยท No account required

What you will learn

  • Separate an application permission from a kernel-enforced boundary.
  • State a protected outcome and the evidence needed to support it.
  • Explain why a username string is not authority by itself.
  • Use scoped synthetic identities without reading or changing host accounts.

  1. Define Linux security boundaries and outcomes

    Connect a workloadโ€™s purpose to the authority, data, and evidence that should constrain it.

    Start learning

  2. Understand Linux identity and credential scope

    Separate names, numeric ids, process credentials, group context, and authentication evidence.

    Start learning

  3. Reason about permissions, ACLs, and creation masks

    Use bounded mode-bit calculations while recognizing the other layers a real access decision needs.

    Start learning

  4. Review paths, links, and resource identity

    Distinguish lexical path text from kernel resolution, object identity, and trusted directory boundaries.

    Start learning

  5. Review process authority and Linux capabilities

    Distinguish numeric identity, retained authority, capability sets, and privilege changes across execution.

    Start learning

  6. Build baselines and distinguish effective evidence

    Compare intended and declared observations without running host audits or confusing configuration text with enforcement.

    Start learning
Back to course