Wiki workshop · Γερμανικά και αγγλικά

Server Baseline Roles

This example is a controlled Ubuntu workshop lab. It is safe for local execution and does not change system configuration.

Παραδείγματα workshop σε ZIP
Πρόοδος μάθησης στη web app

Σημειώστε κεφάλαια ως αναγνωσμένα, δείτε την πρόοδο ανάγνωσης και ολοκληρώστε πρακτικές ενότητες αφού ενεργοποιήσετε την προαιρετική web app. Η πρόοδος του workshop υπολογίζεται από τα κεφάλαια όλων των σελίδων τεκμηρίωσης. Οι επιλογές μένουν σε αυτή τη συσκευή· δεν υπάρχει λογαριασμός ή συγχρονισμός με server. Δεν απαιτείται εγκατάσταση. Η ανάκληση στις Ρυθμίσεις απορρήτου διαγράφει την πρόοδο.

Πρόοδος ανάγνωσης0%
0%
0 / 6 κεφάλαια που διαβάστηκαν

Server Baseline Roles

Focus: Serverrollen und Baseline-Dokumentation.

Purpose

This example is a controlled Ubuntu workshop lab. It is safe for local execution and does not change system configuration.

01 / 06

Documentation

02 / 06

Files

03 / 06

Run

bash
./run.sh

The script writes temporary evidence below work/. The directory is ignored by Git.

04 / 06

Review Questions

    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
    1. How does this example demonstrate Serverrollen und Baseline-Dokumentation with safe Ubuntu operations?
05 / 06

Practice Appendix: Example Server Baseline Roles

This appendix is a working backlog for longer trainings, reviews and repetitions. Each task can be checked locally with sample configuration, shell commands and a Git repository.

A001. Serverrollen und Baseline-Dokumentation

  • Task: check release and support status and connect the observation explicitly to Serverrollen und Baseline-Dokumentation.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A002. Ubuntu

  • Task: evaluate package and repository risk and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A003. Operations

  • Task: explain service status and logs and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A004. Security

  • Task: document network assumption and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A005. Serverrollen und Baseline-Dokumentation

  • Task: review user and sudo rule and connect the observation explicitly to Serverrollen und Baseline-Dokumentation.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A006. Ubuntu

  • Task: evaluate firewall rule and exposure and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A007. Operations

  • Task: describe storage and backup path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A008. Security

  • Task: record patch and reboot window and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A009. Serverrollen und Baseline-Dokumentation

  • Task: mark security baseline and connect the observation explicitly to Serverrollen und Baseline-Dokumentation.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A010. Ubuntu

  • Task: name monitoring or alert rule and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A011. Operations

  • Task: record rollback or recovery path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A012. Security

  • Task: write team rule and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A013. Serverrollen und Baseline-Dokumentation

  • Task: check release and support status and connect the observation explicitly to Serverrollen und Baseline-Dokumentation.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A014. Ubuntu

  • Task: evaluate package and repository risk and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A015. Operations

  • Task: explain service status and logs and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A016. Security

  • Task: document network assumption and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A017. Serverrollen und Baseline-Dokumentation

  • Task: review user and sudo rule and connect the observation explicitly to Serverrollen und Baseline-Dokumentation.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A018. Ubuntu

  • Task: evaluate firewall rule and exposure and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A019. Operations

  • Task: describe storage and backup path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A020. Security

  • Task: record patch and reboot window and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A021. Serverrollen und Baseline-Dokumentation

  • Task: mark security baseline and connect the observation explicitly to Serverrollen und Baseline-Dokumentation.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A022. Ubuntu

  • Task: name monitoring or alert rule and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A023. Operations

  • Task: record rollback or recovery path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A024. Security

  • Task: write team rule and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A025. Serverrollen und Baseline-Dokumentation

  • Task: check release and support status and connect the observation explicitly to Serverrollen und Baseline-Dokumentation.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A026. Ubuntu

  • Task: evaluate package and repository risk and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A027. Operations

  • Task: explain service status and logs and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A028. Security

  • Task: document network assumption and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A029. Serverrollen und Baseline-Dokumentation

  • Task: review user and sudo rule and connect the observation explicitly to Serverrollen und Baseline-Dokumentation.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A030. Ubuntu

  • Task: evaluate firewall rule and exposure and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A031. Operations

  • Task: describe storage and backup path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A032. Security

  • Task: record patch and reboot window and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A033. Serverrollen und Baseline-Dokumentation

  • Task: mark security baseline and connect the observation explicitly to Serverrollen und Baseline-Dokumentation.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A034. Ubuntu

  • Task: name monitoring or alert rule and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A035. Operations

  • Task: record rollback or recovery path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A036. Security

  • Task: write team rule and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A037. Serverrollen und Baseline-Dokumentation

  • Task: check release and support status and connect the observation explicitly to Serverrollen und Baseline-Dokumentation.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A038. Ubuntu

  • Task: evaluate package and repository risk and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A039. Operations

  • Task: explain service status and logs and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A040. Security

  • Task: document network assumption and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A041. Serverrollen und Baseline-Dokumentation

  • Task: review user and sudo rule and connect the observation explicitly to Serverrollen und Baseline-Dokumentation.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A042. Ubuntu

  • Task: evaluate firewall rule and exposure and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A043. Operations

  • Task: describe storage and backup path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A044. Security

  • Task: record patch and reboot window and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A045. Serverrollen und Baseline-Dokumentation

  • Task: mark security baseline and connect the observation explicitly to Serverrollen und Baseline-Dokumentation.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A046. Ubuntu

  • Task: name monitoring or alert rule and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A047. Operations

  • Task: record rollback or recovery path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A048. Security

  • Task: write team rule and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A049. Serverrollen und Baseline-Dokumentation

  • Task: check release and support status and connect the observation explicitly to Serverrollen und Baseline-Dokumentation.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A050. Ubuntu

  • Task: evaluate package and repository risk and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.
06 / 06

UBU · Orthevs Academy

31 modules ως ενιαία διαδρομή μάθησης.

Η σειρά παραμένει αμετάβλητη: από τη βασική δομή του lab μέσω τεχνικών θεμελίων και λειτουργικών μοντέλων έως το τελικό troubleshooting. Τα τεχνικά ονόματα καταλόγων διατηρούνται σκόπιμα.

Orthevs – Η μηχανική ως βάση για όσα ακολουθούν.

Το Orthevs ως εφαρμογή

Εγκατάσταση του Orthevs

Η web app του Orthevs μπορεί να εγκατασταθεί σε υποστηριζόμενες κινητές συσκευές και browsers υπολογιστή.

iPhone και iPad

Ανοίξτε το Orthevs στο Safari. Πατήστε Κοινή χρήση και μετά Προσθήκη στην οθόνη αφετηρίας. Ενεργοποιήστε το Άνοιγμα ως web app, αν εμφανίζεται, και πατήστε Προσθήκη.

Android

Για τη web app, ανοίξτε το μενού του browser και επιλέξτε Εγκατάσταση εφαρμογής ή Προσθήκη στην αρχική οθόνη. Επιβεβαιώστε την εγκατάσταση.

Browser υπολογιστή

Ανοίξτε το μενού του browser ή το εικονίδιο εγκατάστασης στη γραμμή διευθύνσεων και επιλέξτε Εγκατάσταση εφαρμογής ή Προσθήκη στο Dock.

Η εγκατάσταση της web app εξαρτάται από τον browser. Αν δεν εμφανιστεί διάλογος εγκατάστασης, ακολουθήστε τα βήματα του browser που αναφέρονται παραπάνω.