Case-study library

Different problems. Different shapes. One operating method.

The strongest project leads. Supporting workstreams follow with the level of detail their evidence can sustain.

Tested with mixed results01

Flagship case study

On-Premises Home Lab and Isolated Restore Validation

Built and documented a personal Proxmox environment, then exercised selected Linux, Windows workstation, Active Directory domain controller, and pfSense backup archives through isolated restore workflows with preboot NIC isolation and controlled cleanup.

Proxmox VEpfSenseWindows ServerActive DirectoryUbuntuPowerShellSHA-256
Open full case studyReview restore evidenceTrace claims to proof
Objective
Test whether selected archives could be restored and inspected without connecting temporary guests to production networks.
Implementation
Created temporary VMs, verified link_down=1 before first boot, performed only authorized local checks, and removed temporary resources.
Result
Linux01 PASS; pfSense narrow PASS; WS01 and DC01 INCONCLUSIVE overall.
Boundary
Personal nonproduction environment. Full disaster recovery, RTO, RPO, application recovery, and production assurance were not proven.
Artifact-backed02

Microsoft 365 and Entra Administration

Organized personal-tenant evidence for identity, groups, licensing, roles, Conditional Access, sign-ins, audit activity, devices, applications, and service principals.

Evidence
CSV, JSON, screenshots, manifests, and hash records.
Boundary
Personal cloud lab only; no employer or client administration is implied.
Review Microsoft 365 proofOpen claim map
Documented03

Service Desk Troubleshooting and RCA

Structured incident records around symptoms, impact, troubleshooting decisions, root-cause framing, remediation, follow-through, and escalation-ready notes.

Method
Separate observations from assumptions, record actions, and keep unresolved questions visible.
Boundary
No unsupported production impact, availability, or resolution metrics are claimed.
Review RCA recordInspect evidence method
Executed and reviewed04

PowerShell Validation and Evidence Automation

Built checks for repository structure, parser integrity, evidence output, timeout handling, Git hygiene, secret patterns, and portfolio-to-operations drift.

Result
Repository and framework checks passed; drift analysis returned a partial match with named gaps.
Boundary
Timeout handling does not prove service availability, and drift gaps are not infrastructure failures.
Open repository validationOpen framework validationOpen drift analysis
Governed05

Repository and Deployment Quality

Maintained the portfolio as a static publication system with generated evidence pages, sitemap presentation, link checks, HTML and SEO validation, browser tests, and deployment workflows.

Validation
Repository scripts and browser checks cover generation consistency, links, metadata, responsive overflow, and evidence paths.
Boundary
Static quality checks do not replace independent security testing.
Review coverage dashboardInspect validation workflow