Security Fundamentals, From Packets to Platforms
Review a fictional document service from its TLS connections to its parser, platform evidence and credentials. Learn the mechanisms, interpret an incident evidence packet and finish with a prioritized service review and acceptance tests.
A browser's padlock does not describe the connection behind a proxy. A non-root process can still hold a powerful storage credential. A successful login does not authorize every document. This course teaches you to find those gaps by following one service through its actual boundaries.
EvidenceDesk is a fictional document-processing service. Across seven lessons, you trace its connections, constrain its parser, interpret platform evidence, investigate possible failures and review its credentials. Each lesson adds an artifact to your review packet rather than asking you to memorize a list of products.
You finish with a project: prioritize three corrections from an evidence packet, assign owner roles, write allowed and denied test cases, and revise the design when an external OCR requirement appears. A worked memo and rubric let you compare the quality of your reasoning. They do not certify the service or substitute for a review of a real deployment.
Begin with the two open network lessons. Creating a free account unlocks the parser-isolation lesson. The four Premium lessons cover platform evidence, incident reasoning, credential recovery and the service-review project. Throughout the course, three interactive diagrams, a runnable offline Python fixture and explained self-checks accompany every lesson. The fixtures inspect supplied evidence or model policy; they do not run scanners or prove deployment enforcement.
Work through the modules in order if the mechanisms are new to you. If you already know the foundations, start by drafting the final project memo, then use the earlier lessons to resolve gaps in your boundary map, evidence or acceptance tests.
When you finish, you can
- Map separate connections, TLS termination points and the authority that encryption does not establish
- Distinguish certificate path validation, service identity and application authorization
- Specify a parser's launch authority, isolation boundary and resource limits
- Write a platform-admission policy with explicit evidence coverage, freshness and identity binding
- Separate observed effects from hypotheses and choose evidence that distinguishes them
- Produce a credential-loss rehearsal and a service-review memo with meaningful acceptance tests
BEFORE YOU START · You can read application code and understand a basic client-server request. The course explains security mechanisms as they arise; no prior security role is required.
Syllabus
Trace connections and verify peers
Map the client, proxy and API as separate connections. Distinguish DNS privacy, TLS peer validation and application authorization, then write a connection table and certificate-failure matrix.
Constrain processes and appraise platform evidence
Inventory a parser's local and remote authority, choose an isolation boundary and define its job limits. Then write a platform-admission policy that states what boot evidence covers and what remains unknown.
Investigate failures and review the service
Interpret a fictional evidence packet, rehearse credential loss and prioritize service corrections. Finish with a review memo, acceptance tests and an explicit list of unresolved findings.