Training Tracks by Industry

Healthcare sysadmins operate under a set of constraints that most IT professionals never deal with. HIPAA isn't a suggestion — it's a legal framework with financial penalties, and the auditors checking your work have seen every shortcut in the book. This track was built by instructors who've worked inside hospital IT departments, not by people who read the regulations and summarized them into slides.

We spend the first week on access controls. Not the theory of access controls — the practical work of building role-based access matrices, implementing least-privilege policies across mixed environments, and documenting everything in a format that satisfies both your security team and external auditors. Most participants tell us this is where the biggest gaps exist on their teams.

Weeks two and three cover audit preparation and encrypted data handling. We run simulated audit scenarios where your team has to produce evidence packets under time pressure. It's uncomfortable on purpose. The real thing is worse, and we'd rather you practice here than stumble during a live review.

The final week focuses on automated log retention and monitoring. Compliance requires keeping certain logs for defined periods, and doing that manually is a recipe for human error. We build the automation together in lab environments that mirror what a mid-size clinic or hospital system actually runs.

We've trained admins at 14 clinics and two hospital systems in the Pacific Northwest. The track works for organizations with 5 IT staff or 50 — the material scales, but the cohort stays small.

SOX compliance isn't something you study for — it's something you build into your daily operations. The financial services track teaches system administrators how to implement controls that hold up under examination, not just on paper but in the actual configuration of your systems. We work with banks, credit unions, insurance firms, and wealth management offices across Oregon and Washington.

Change management is the backbone of this track. In financial services, every configuration change needs a paper trail: who requested it, who approved it, what was changed, and what the rollback plan looks like. We've seen too many audit findings that boil down to "you did the right thing but didn't document it." That stops here.

Data retention is the other major focus. Financial regulations specify how long certain records must be kept, and the rules vary depending on the type of data and the regulatory body overseeing your organization. We build retention policies together in lab environments, and we test them — including the parts where you have to prove you can retrieve specific records from specific time periods on demand.

The convergence of operational technology and information technology is the defining challenge for manufacturing sysadmins right now. Shop-floor control systems that were never designed to be networked are now connected to corporate IT infrastructure, and the security implications are significant. This track addresses that reality head-on.

Network segmentation is where we start. Keeping production systems isolated from corporate networks — while still allowing the data flow that operations teams need — requires careful architecture. We work through real segmentation designs in our labs, using network topologies modeled after actual manufacturing environments: PLCs on one segment, SCADA on another, corporate email and ERP on a third, with controlled bridges between them.

Patch management in manufacturing is different from patching in an office environment. You can't reboot a production line at 2 AM on a Tuesday. We cover staged rollout strategies, maintenance window coordination, and the specific challenge of patching systems that run legacy operating systems because the vendor stopped supporting updates years ago. It's not glamorous work, but it's the work that keeps plants running.

The backup and recovery module focuses on systems where downtime has a direct cost measured in dollars per minute. We build backup strategies that account for machines running decades-old software, proprietary data formats, and recovery time objectives that leave very little room for error.