Graystum Labs
Uwasan Maku
I am a platform and security engineer in Toronto, and Graystum Labs is my studio. I build the infrastructure other engineers ship on and make it pass an audit without slowing them down.
Background
Seven years in, mostly on AWS and Azure. Payment systems first, then managed cloud for other people’s companies, then the platform under a security product, and lately big moves from virtual machines to Kubernetes.
Certifications: AWS Certified DevOps Engineer Professional, Certified Kubernetes Administrator.
Stories
Four I still tell.
- Kubernetes
The big move
650-odd virtual machines, seven flavours of operating system, all walked onto Kubernetes. Nothing fell over at cutover. I am still a little smug about it.
- Reliability
Getting good at boring
I ran a platform team of four. We aimed for dull: four nines of uptime, and pipelines that went green 99.9% of the time.
- Audits
The year of screenshots
SOC 2 prep used to eat a year. I got it down to four months, then got annoyed enough at the rest to start building Wardhand.
- Payments
Where the money moves
I started out on payment rails for 50,000+ small businesses. You learn fast what “it’s down” means when it is someone’s till.
How I work
- 1Everything is code, reviewed and reversible.
- 2Security controls belong in the pipeline, so compliance is a by-product of shipping.
- 3Automation is finished when the next team can run it without me.
Wardhand
In development. Design partners welcome.
Wardhand is the studio’s first product. I started it after running SOC 2 by hand and deciding the recurring work should belong to software.
It lives in your own AWS account and checks AWS and GitHub against SOC 2, using fixed rules and the policies you actually wrote. When something fails it prepares the fix, and a named person on your team signs it. Your data stays in your account. Azure is next.
More at wardhand.com.
An example
An illustration of a fix drafted by Wardhand. It is not output from a real account.
Turn on log file validation for the main audit trail
- Why
- Log file validation is off on the main CloudTrail trail, so an edit to past audit logs would go unnoticed.
- Evidence
- A read-only
DescribeTrailscall. The response is kept with the time and the query, so it can be run again. - Change
-
logging/cloudtrail.tf
resource "aws_cloudtrail" "main" {- enable_log_file_validation = false+ enable_log_file_validation = true }
- Signed
- Name and time of the person on your team who approves it