We keep praise specific to modules and surfaces. A few notes include mild reservations — because perfect scores rarely describe real audit work.
“After the inventory lab in Vault Audit Fundamentals, we discovered three ‘archive’ folders that still accepted write access from a retired CI account. The retention module did not magically fix our policy board, but it gave me language that legal could argue with.”
4 / 5 · platform-style
Solid on access-path worksheets. Encryption chapter felt rushed if you have never touched LUKS before.
“I’m Hana from Daegu. The Field Notes checklist alone justified the time; I annotated our NAS export the same afternoon. Would have liked one more video on Windows ACL oddities.”
“Client in healthcare IT — we used the report wording templates during an internal dry run. No drama, just fewer vague adjectives.”
Case note: shared vault cleanup
Context
A twelve-person product studio kept design assets in an encrypted share. Quarterly “reviews” were screenshot collections with no access-path map.
What changed
Two engineers completed Vault Audit Fundamentals, then ran the inventory worksheet. They found guest links that outlived a contractor engagement by nine months. Findings were rewritten using the course template so the studio lead could re-check each step.
Limitation they still own
They postponed key rotation because a vendor API still required the old credential. The course made that risk visible; it did not remove the dependency.
Case note: logs before locks
Context
A logistics ops team in Korea trusted cabinet locks and disk encryption, yet overnight jobs kept failing with intermittent permission errors.
What changed
Using the access-log sampling approach from our blog and course, they identified a scheduled task running under a personal laptop profile synced through a stale VPN route. Physical locks were never the issue.
Testimonials describe educational experiences. They are not guarantees of security outcomes or financial results. Read Not Financial Advice.