✳ Choose your direction

Security in your world.

Start with core skills or follow an industry path. Each setting brings different assets, constraints, and consequences to the same security principles.

Same foundations; industry-specific decisions.

Find your context.

Choose a core engineering track or an industry field guide.

START WITH THE SHARED ENGINEERING SKILLS

Build a foundation. Develop a principal architect’s judgment.

Begin with Foundations, then advance through specialized tracks in SOC operations, AI agent security, software supply chain, GRC, identity federation, cryptography, network defense, and systems security.

10 LESSONS / beginner

Cybersecurity foundations

Ten core lessons and seven deep-dive electives build your first-principles engineering model across assets and the CIA triad, threat-vulnerability-risk math, DNS/TCP/TLS/HTTP protocol layers, identity and origin-bound authentication, evidence-grade logging, defense-in-depth segmentation, application trust boundaries, data resilience, cloud shared responsibility, and outcome-driven control design.

86 min reading

Explore this path ↗

4 LESSONS / intermediate

SOC operations and incident response

Four intermediate lessons take you inside Meridian’s Security Operations Center with Threat Hunter Nyx: prioritizing vulnerabilities by exploitability (EPSS, CISA KEV) and asset reachability, triaging identity anomalies against base rates, running the NIST SP 800-61 containment and verified recovery loop, and bounding AI assistants inside an Agentic SOC.

40 min reading

Explore this path ↗

3 LESSONS / intermediate

AI application and agent security

Three intermediate lessons establish defense-in-depth for LLM applications and autonomous tool-calling agents: isolating untrusted user and RAG data from instructions (OWASP LLM01:2026), enforcing deterministic Policy Enforcement Points against Excessive Agency (LLM03:2026), and wiring out-of-band human oversight gates mapped to the NIST AI RMF.

32 min reading

Explore this path ↗

4 LESSONS / intermediate

Application & software supply-chain security

Four intermediate lessons trace software security from whiteboard to runtime: STRIDE threat modeling across Data Flow Diagram trust boundaries, locking direct and transitive dependency trees, separating untrusted PR execution from signed production promotion in CI/CD, and binding SBOM inventories to running build digests.

34 min reading

Explore this path ↗

Foundations elective

After F4 / 1 lesson

Mailbox literacy: what SPF, DKIM, and DMARC prove

Focused single-lesson path unpacking how SPF validates the sending IP, DKIM verifies cryptographic header/body signatures, and DMARC enforces visible From-header alignment - plus why none of the three proves a message is benign.

8 min reading

Open this elective ↗

3 LESSONS / intermediate

Governance, risk, and compliance (GRC) in practice

Three intermediate lessons turn GRC from static paperwork into an engineering discipline: writing falsifiable four-part risk sentences with accountable business owners, pairing controls with automated Type II operating evidence, and running NIST CSF 2.0 Govern as a monthly cadence.

30 min reading

Explore this path ↗

Foundations elective

After F6b / 1 lesson

Privacy engineering vs security controls

Focused single-lesson path distinguishing system security (protecting data from unauthorized actors via encryption and IAM) from privacy engineering (governing authorized collection, purpose limitation, minimization, and data-subject rights).

10 min reading

Open this elective ↗

3 LESSONS / intermediate

OAuth 2.0, OIDC, and SAML federation security

Three core lessons and one protocol deep dive cover delegated API authorization and enterprise Single Sign-On: separating the four OAuth 2.0 roles and Resource Server token checks, mapping signed OIDC/SAML claims to least-privilege roles via immutable (iss, sub) keys, and defending against the five federation failure modes.

32 min reading

Explore this path ↗

11 LESSONS / intermediate

Security architecture, cryptography, and governance

Eleven lessons take an individual contributor from governance hierarchy, legal compliance, quantitative risk math, and data lifecycle engineering through formal state-machine models, hardware TCB isolation, cryptography, PKI, and physical facility defense.

114 min reading

Explore this path ↗

5 LESSONS / intermediate

Network architecture, protocol defense, and access models

Five lessons map the OSI and TCP/IP stacks to layer-specific protocol attacks, zero-trust segmentation, firewall and NAC architectures, IPsec and wireless cryptography, Kerberos and biometric identity lifecycles, and DAC, MAC, RBAC, and ABAC access models.

53 min reading

Explore this path ↗

6 LESSONS / intermediate

Security assessment, forensics, and software assurance

Six lessons cover SOC 1, SOC 2, and SOC 3 audit boundaries, penetration testing rules of engagement, SAST, DAST, IAST, and fuzzing pipelines, digital forensics order of volatility, disaster recovery sites and RAID math, and secure SDLC and database defense.

69 min reading

Explore this path ↗

INDUSTRY FIELD GUIDE / 01

Protect treasury settlement, third-party access, and ledger reconciliation

Practice out-of-band payment verification, least-privilege vendor boundaries, and cryptographic ledger reconciliation under settlement pressure.

  • Transaction integrity
  • Out-of-band authorization
  • Ledger reconciliation

3 applied lessons · 21 min · synthetic decision checks

Explore finance ↗

APPLIED LESSONS

  1. Verify a changed payment destination
  2. Constrain a vendor's financial access
  3. Restore service and reconcile the books

These scenarios model Meridian Space & Robotics treasury and financial settlement operations alongside U.S. financial sector controls; regulatory applicability depends on the specific institution, charter, regulator, and jurisdiction.

INDUSTRY FIELD GUIDE / 02

Preserve safe physical utility operations during cyber incidents

Practice operator-governed maintenance access, telemetry corroboration, and safety-first OT recovery.

  • Safety and service continuity
  • Operator-governed decisions
  • Trusted OT baselines

3 applied lessons · 21 min · synthetic decision checks

Explore utilities ↗

APPLIED LESSONS

  1. Approve a bounded OT maintenance session
  2. Corroborate operational telemetry and configuration logs
  3. Rehearse OT recovery with the operational owner

These scenarios model electric power and cooling water utility operations supporting Meridian's launch test stands using general NIST SP 800-82 Rev. 3 OT principles; electricity and water subsectors have distinct statutory requirements and site safety rules.

INDUSTRY FIELD GUIDE / 03

Protect precision production, CAD/CAM recipes, and quality release gates

Practice cryptographic recipe verification, dependency-aware shop-floor segmentation, and quality-gated production recovery.

  • Production and quality integrity
  • CAD/CAM recipe verification
  • Bounded supplier maintenance

3 applied lessons · 21 min · synthetic decision checks

Explore manufacturing ↗

APPLIED LESSONS

  1. Verify machine recipe provenance and authorization
  2. Segment supplier maintenance access by verified data flows
  3. Restore production with a formal quality release gate

These scenarios model Meridian Space & Robotics precision avionics and propulsion manufacturing cells using general engineering and NIST OT segmentation practices; aerospace, medical, automotive, and defense contracts impose additional quality and regulatory mandates.

INDUSTRY FIELD GUIDE / 04

Protect clinical continuity, biomedical device access, and ePHI workflows

Practice clinician-coordinated downtime response, biomedical vendor governance, and HL7/FHIR interface reconciliation.

  • Patient-care continuity
  • Biomedical device governance
  • Health-data boundaries

3 applied lessons · 21 min · synthetic decision checks

Explore healthcare ↗

APPLIED LESSONS

  1. Coordinate clinical downtime during an EHR outage
  2. Govern biomedical vendor maintenance access
  3. Reconcile clinical interface queues after a third-party outage

These scenarios model Meridian's occupational flight-medicine clinic and U.S. healthcare delivery environments; statutory obligations under HIPAA and other rules depend on the specific covered entity, business associate relationship, and data flow.

INDUSTRY FIELD GUIDE / 05

Protect student records, academic identity lifecycles, and open research

Practice data-classification boundaries for open collaboration, term-based identity governance, and deadline-critical service recovery.

  • Student record privacy
  • Open research boundaries
  • Cohort identity lifecycles

3 applied lessons · 24 min · synthetic decision checks

Explore education ↗

APPLIED LESSONS

  1. Separate student records from open research artifacts
  2. Govern academic identities and EdTech roster syncs across term boundaries
  3. Recover a course registration service during an enrollment deadline

These scenarios model Meridian's university propulsion research fellowship and U.S. educational institutions; FERPA applicability depends on U.S. Department of Education funding, and CISA K-12 guidance is voluntary.

INDUSTRY FIELD GUIDE / 06

Keep resident and civic services trustworthy, accountable, and accessible

Practice end-to-end civic service recovery, accountable MSP delegation, and public-records disclosure hygiene.

  • Essential resident services
  • Accountable supplier delegation
  • Public and confidential records

3 applied lessons · 24 min · synthetic decision checks

Explore public sector ↗

APPLIED LESSONS

  1. Recover the complete resident service, not just the front-end portal
  2. Keep managed service provider administration accountable
  3. Separate public transparency reporting from confidential investigation evidence

These scenarios model municipal and regional public-service operations coordinating with Meridian's spaceport authority using voluntary risk guidance; federal FISMA obligations do not automatically apply to every state or local agency.

INDUSTRY FIELD GUIDE / 07

Protect checkout script integrity, seasonal access, and order reconciliation

Practice governing payment-page script execution, bounding seasonal support authority, and reconciling orders across payment and fulfillment gateways.

  • Payment-page trust boundaries
  • Seasonal RBAC boundaries
  • Idempotent order reconciliation

3 applied lessons · 24 min · synthetic decision checks

Explore retail & e-commerce ↗

APPLIED LESSONS

  1. Inspect the checkout page script trust boundary
  2. Constrain seasonal customer-support refund privileges
  3. Reconcile payment captures and warehouse dispatches after a restore

These scenarios model Meridian's commercial ground-terminal storefront and retail e-commerce architectures; PCI DSS scope and validation paths depend on the exact payment integration architecture and acquirer program.

INDUSTRY FIELD GUIDE / 08

Preserve trustworthy dispatch routing, partner EDI boundaries, and safe degraded operations

Practice authenticating routing changes, lifecycle-bounding partner device integrations, and reconciling physical movement logs after degraded operations.

  • Dispatch routing integrity
  • Partner & fleet lifecycle boundaries
  • Controlled degraded recovery

3 applied lessons · 24 min · synthetic decision checks

Explore transport & logistics ↗

APPLIED LESSONS

  1. Verify an anomalous dispatch routing change
  2. Decommission retired scanner credentials and scope partner APIs
  3. Transition safely from manual degraded dispatch back to automation

These scenarios model Meridian Space & Robotics ground-transport and launch-hardware logistics alongside general NIST SP 800-82 Rev. 3 OT guidance; aviation, maritime, rail, road, and hazmat operations each carry distinct statutory safety rules.

INDUSTRY FIELD GUIDE / 09

Prove multi-tenant isolation, bound machine identities, and recover a single tenant

Practice evaluating multi-tenant isolation evidence, scoping machine-to-machine OAuth/API credentials, and executing single-tenant recovery without collateral rollback.

  • Tenant isolation evidence
  • Machine identity blast radius
  • Tenant-scoped recovery & exit

3 applied lessons · 24 min · synthetic decision checks

Explore technology/saas ↗

APPLIED LESSONS

  1. Prove a multi-tenant isolation boundary claim
  2. Bound machine identities and their cross-tenant blast radius
  3. Recover a single SaaS tenant and refresh its exit archive

These scenarios use Chronos Hub, Meridian's multi-tenant orbital telemetry and mission-planning SaaS platform, and two fictional customer tenants: Aegis SatCom and Helios Orbital. The Cloud Controls Matrix is a framework, not a statute. Privacy, breach notice, and contractual duties depend on the parties, the agreement, and the jurisdiction. A CAIQ answer is questionnaire evidence, not an audit opinion, and this path does not invent a SOC 2 report for any named product.

Find your next idea.

Tip: press / to open search. Escape closes this window.