Workshop-Wiki · Englisch

Official Certificates and Exam Alignment: TLS (EN)

This document does not invent an official TLS core certificate. TLS skill is relevant in security, cloud, Linux, web, PKI and platform exams, but this workshop treats TLS as a practical core capability and not as a replacement for vendor…

Workshop-Beispiele als ZIP
Lernstand in der Web-App

Kapitel als gelesen markieren, Lesefortschritt sehen und Praxismodule abhaken: Diese Funktionen stehen nach Aktivierung der optionalen Web-App zur Verfügung. Der Workshop-Fortschritt ergibt sich automatisch aus den Kapiteln aller Dokumentseiten. Deine Auswahl bleibt auf diesem Gerät; es gibt kein Konto und keinen Serverabgleich. Eine Installation ist nicht erforderlich. Beim Widerruf in den Datenschutz-Einstellungen wird der Lernstand gelöscht.

Lesefortschritt0%
0%
0 / 6 Kapitel gelesen
Weitere SprachfassungDeutsch ↗Griechisch ↗

Official Certificates and Exam Alignment: TLS (EN)

Classification

This document does not invent an official TLS core certificate. TLS skill is relevant in security, cloud, Linux, web, PKI and platform exams, but this workshop treats TLS as a practical core capability and not as a replacement for vendor material.

Important for this workshop:

  • RFC 8446, RFC 9325, RFC 5280, CA/Browser Forum Baseline Requirements and NIST SP 800-52 Rev. 2 provide technical references.
  • Certificates in workshop artifacts are technical X.509 artifacts, not personal certifications.
  • Exam alignment comes through tasks about TLS versions, certificates, chains, mTLS, ACME, hardening, monitoring and incident response.
01 / 06

Competency Mapping

Competency Workshop Area Evidence in Repo
TLS and X.509 fundamentals Fundamentals Workshop 01, Exercises 01, Examples 00-06
handshake, chain and web server Intermediate Workshop 02, Examples 07-15
automation, ingress and mTLS Professional Workshop 03, Examples 13-23
hardening and incident response Advanced Security Workshop 04, Examples 24-30
02 / 06

Preparation Without Certification Claims

  1. Check current RFCs, CA/B Forum requirements and organization requirements.
  2. Practice OpenSSL analysis, chain verification, CSR creation, mTLS and expiration monitoring locally.
  3. Support decisions with commands, outputs and runbooks.
  4. Check vendor exams separately against their current objectives.
03 / 06

Sources and References

04 / 06

Review Checklist for Certificate Preparation

  • 01. check certificate and SAN: Record the affected service, certificate, key, chain and risk.
  • 02. review private-key protection: Record the affected service, certificate, key, chain and risk.
  • 03. validate complete chain: Record the affected service, certificate, key, chain and risk.
  • 04. review TLS version and cipher policy: Record the affected service, certificate, key, chain and risk.
  • 05. document trust-store assumption: Record the affected service, certificate, key, chain and risk.
  • 06. check expiration date and renewal path: Record the affected service, certificate, key, chain and risk.
  • 07. explain revocation model: Record the affected service, certificate, key, chain and risk.
  • 08. evaluate mTLS identity: Record the affected service, certificate, key, chain and risk.
  • 09. mark HSTS or header risk: Record the affected service, certificate, key, chain and risk.
  • 10. name monitoring or alert rule: Record the affected service, certificate, key, chain and risk.
  • 11. record incident recovery path: Record the affected service, certificate, key, chain and risk.
  • 12. write team rule: Record the affected service, certificate, key, chain and risk.
  • 13. check certificate and SAN: Record the affected service, certificate, key, chain and risk.
  • 14. review private-key protection: Record the affected service, certificate, key, chain and risk.
  • 15. validate complete chain: Record the affected service, certificate, key, chain and risk.
  • 16. review TLS version and cipher policy: Record the affected service, certificate, key, chain and risk.
  • 17. document trust-store assumption: Record the affected service, certificate, key, chain and risk.
  • 18. check expiration date and renewal path: Record the affected service, certificate, key, chain and risk.
  • 19. explain revocation model: Record the affected service, certificate, key, chain and risk.
  • 20. evaluate mTLS identity: Record the affected service, certificate, key, chain and risk.
  • 21. mark HSTS or header risk: Record the affected service, certificate, key, chain and risk.
  • 22. name monitoring or alert rule: Record the affected service, certificate, key, chain and risk.
  • 23. record incident recovery path: Record the affected service, certificate, key, chain and risk.
  • 24. write team rule: Record the affected service, certificate, key, chain and risk.
  • 25. check certificate and SAN: Record the affected service, certificate, key, chain and risk.
  • 26. review private-key protection: Record the affected service, certificate, key, chain and risk.
  • 27. validate complete chain: Record the affected service, certificate, key, chain and risk.
  • 28. review TLS version and cipher policy: Record the affected service, certificate, key, chain and risk.
  • 29. document trust-store assumption: Record the affected service, certificate, key, chain and risk.
  • 30. check expiration date and renewal path: Record the affected service, certificate, key, chain and risk.
  • 31. explain revocation model: Record the affected service, certificate, key, chain and risk.
  • 32. evaluate mTLS identity: Record the affected service, certificate, key, chain and risk.
  • 33. mark HSTS or header risk: Record the affected service, certificate, key, chain and risk.
  • 34. name monitoring or alert rule: Record the affected service, certificate, key, chain and risk.
  • 35. record incident recovery path: Record the affected service, certificate, key, chain and risk.
  • 36. write team rule: Record the affected service, certificate, key, chain and risk.
  • 37. check certificate and SAN: Record the affected service, certificate, key, chain and risk.
  • 38. review private-key protection: Record the affected service, certificate, key, chain and risk.
  • 39. validate complete chain: Record the affected service, certificate, key, chain and risk.
  • 40. review TLS version and cipher policy: Record the affected service, certificate, key, chain and risk.
05 / 06

Practice Appendix: Certificate Preparation

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

A001. TLS

  • Task: check certificate and SAN and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A002. RFC 8446

  • Task: review private-key protection and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A003. RFC 9325

  • Task: validate complete chain and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A004. X.509

  • Task: review TLS version and cipher policy and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A005. PKI

  • Task: document trust-store assumption and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A006. TLS

  • Task: check expiration date and renewal path and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A007. RFC 8446

  • Task: explain revocation model and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A008. RFC 9325

  • Task: evaluate mTLS identity and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A009. X.509

  • Task: mark HSTS or header risk and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A010. PKI

  • Task: name monitoring or alert rule and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A011. TLS

  • Task: record incident recovery path and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A012. RFC 8446

  • Task: write team rule and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A013. RFC 9325

  • Task: check certificate and SAN and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A014. X.509

  • Task: review private-key protection and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A015. PKI

  • Task: validate complete chain and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A016. TLS

  • Task: review TLS version and cipher policy and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A017. RFC 8446

  • Task: document trust-store assumption and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A018. RFC 9325

  • Task: check expiration date and renewal path and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A019. X.509

  • Task: explain revocation model and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A020. PKI

  • Task: evaluate mTLS identity and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A021. TLS

  • Task: mark HSTS or header risk and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A022. RFC 8446

  • Task: name monitoring or alert rule and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A023. RFC 9325

  • Task: record incident recovery path and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A024. X.509

  • Task: write team rule and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A025. PKI

  • Task: check certificate and SAN and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A026. TLS

  • Task: review private-key protection and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A027. RFC 8446

  • Task: validate complete chain and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A028. RFC 9325

  • Task: review TLS version and cipher policy and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A029. X.509

  • Task: document trust-store assumption and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A030. PKI

  • Task: check expiration date and renewal path and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A031. TLS

  • Task: explain revocation model and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A032. RFC 8446

  • Task: evaluate mTLS identity and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A033. RFC 9325

  • Task: mark HSTS or header risk and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A034. X.509

  • Task: name monitoring or alert rule and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A035. PKI

  • Task: record incident recovery path and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A036. TLS

  • Task: write team rule and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A037. RFC 8446

  • Task: check certificate and SAN and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A038. RFC 9325

  • Task: review private-key protection and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A039. X.509

  • Task: validate complete chain and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A040. PKI

  • Task: review TLS version and cipher policy and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A041. TLS

  • Task: document trust-store assumption and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A042. RFC 8446

  • Task: check expiration date and renewal path and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A043. RFC 9325

  • Task: explain revocation model and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A044. X.509

  • Task: evaluate mTLS identity and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A045. PKI

  • Task: mark HSTS or header risk and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A046. TLS

  • Task: name monitoring or alert rule and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A047. RFC 8446

  • Task: record incident recovery path and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A048. RFC 9325

  • Task: write team rule and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A049. X.509

  • Task: check certificate and SAN and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A050. PKI

  • Task: review private-key protection and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A051. TLS

  • Task: validate complete chain and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A052. RFC 8446

  • Task: review TLS version and cipher policy and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A053. RFC 9325

  • Task: document trust-store assumption and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A054. X.509

  • Task: check expiration date and renewal path and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A055. PKI

  • Task: explain revocation model and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A056. TLS

  • Task: evaluate mTLS identity and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A057. RFC 8446

  • Task: mark HSTS or header risk and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A058. RFC 9325

  • Task: name monitoring or alert rule and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A059. X.509

  • Task: record incident recovery path and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A060. PKI

  • Task: write team rule and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A061. TLS

  • Task: check certificate and SAN and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A062. RFC 8446

  • Task: review private-key protection and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A063. RFC 9325

  • Task: validate complete chain and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A064. X.509

  • Task: review TLS version and cipher policy and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A065. PKI

  • Task: document trust-store assumption and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A066. TLS

  • Task: check expiration date and renewal path and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A067. RFC 8446

  • Task: explain revocation model and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A068. RFC 9325

  • Task: evaluate mTLS identity and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A069. X.509

  • Task: mark HSTS or header risk and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A070. PKI

  • Task: name monitoring or alert rule and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A071. TLS

  • Task: record incident recovery path and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A072. RFC 8446

  • Task: write team rule and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A073. RFC 9325

  • Task: check certificate and SAN and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A074. X.509

  • Task: review private-key protection and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A075. PKI

  • Task: validate complete chain and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A076. TLS

  • Task: review TLS version and cipher policy and connect the observation explicitly to TLS.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A077. RFC 8446

  • Task: document trust-store assumption and connect the observation explicitly to RFC 8446.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A078. RFC 9325

  • Task: check expiration date and renewal path and connect the observation explicitly to RFC 9325.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A079. X.509

  • Task: explain revocation model and connect the observation explicitly to X.509.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.

A080. PKI

  • Task: evaluate mTLS identity and connect the observation explicitly to PKI.
  • Evidence: Record at least one OpenSSL- or curl-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 keys, certificates, chains, trust stores or headers would be critical?
  • Recovery: Describe whether reissue, renewal, revocation, trust-store repair, rollback or key rotation would be needed.
06 / 06

TLS · Orthevs Academy

31 Module als durchgängiger Lernpfad.

Die Reihenfolge bleibt unverändert: von der Laborgrundstruktur über fachliche Grundlagen und Betriebsmodelle bis zum abschließenden Troubleshooting. Die technischen Verzeichnisnamen werden bewusst beibehalten.

Orthevs – Engineering als Grundlage für das, was als Nächstes kommt.

Orthevs als App

Orthevs installieren

Die Orthevs Web-App kann auf unterstützten Mobilgeräten und Desktop-Browsern installiert werden.

iPhone und iPad

Öffnen Sie Orthevs in Safari. Tippen Sie auf Teilen, dann auf ‚Zum Home-Bildschirm‘. Aktivieren Sie gegebenenfalls ‚Als Web-App öffnen‘ und tippen Sie auf ‚Hinzufügen‘.

Android

Für die Web-App öffnen Sie das Browsermenü und wählen ‚App installieren‘ oder ‚Zum Startbildschirm hinzufügen‘. Bestätigen Sie die Installation.

Desktop-Browser

Öffnen Sie das Browsermenü oder das Installationssymbol in der Adressleiste und wählen Sie ‚App installieren‘ beziehungsweise ‚Zum Dock hinzufügen‘.

Die Web-App-Installation hängt vom Browser ab. Falls kein Installationsdialog erscheint, nutzen Sie die angezeigten Schritte im Browser.