About

The short version is on the home page. This is the long version, in the only documentation format I've ever actually enjoyed writing.

.SYNOPSIS

Identity and security engineer. 18+ years in infrastructure, operations, and security. Aurora, Illinois.

Unprofessionally? Much longer. Starting with BASIC on an Atari 800 XL.

.DESCRIPTION

Viciously enjoying learning and growing my skill set, I'm deeply passionate about technical problem solving. I've had the distinct pleasure of finding myself in interesting roles while wearing many hats, some of them fitting better than others.

Over the years, I've collaborated with exceptional engineers, architected and implemented systems, and continued learning almost every day.

Skill set includes PowerShell, Microsoft Graph, Entra ID, Active Directory, MSSQL, Bash, REST APIs, HTML, CSS, and Azure CLI. Broad foundations paired with deep dives.

Lots of comments.

I build infrastructure that matters, and in the process, inconvenience a fair number of electrons.

.PARAMETER Name

Set-AndrewGalbraithUnrestricted.ps1

.INPUTS

Technical and institutional knowledge. A career spent learning not just technologies, but the institutions that surround them: culture, process, failure modes, and incentives.

IAM workflow evaluation. Measuring identity workflows against the numbers that matter: onboarding time, access accuracy, audit success, operational friction.

Lifecycle management. The right access for the right people at the right time, then cleanly removing it, guided by least privilege and operational reality.

Industry and OWASP practice. Code review, configuration validation, and documentation as security controls, not afterthoughts.

Conventions. Perspective shaped by DEF CON, Microsoft Ignite, and technical summits. Equal parts inspiration, pattern recognition, and hard-earned caution.

.OUTPUTS

Systems people can audit. More resilient, more understandable, and easier to explain to the next person than they were before.

Access that's strict and livable. Conditional Access policy designed with the people who have to live under it, and a change process that survives contact with production.

Fewer tickets, fewer hands. Automation that removes toil: idempotent, -WhatIf-safe scripts that run the same way every time.

Failure modes caught early. Anticipating what breaks before it becomes an incident.

Shared vocabulary. Documentation and briefings that let engineering, security, and operations argue about the same thing instead of three different things.

.EXAMPLE

See Experience for the timeline and Projects for the work.

.NOTES

Currently living in Aurora, Illinois with my dog Lilith, who remains unimpressed by most engineering achievements but appreciates consistency, walks, and treats.

Firm believer that dogs should always be rewarded for not being people.

Routinely traveling. If you want to talk shop: LinkedIn, Mastodon, or Bluesky.