pro
Adil Shahzad
Senior DevOps & DevSecOps Engineer · Cloud Security
Ready for work
Adil is ready for their next project!
Driving SAMA CSF maturity from Level 2 to Level 3
0
0
Fraud and abuse detection wired into a SIEM
Card-testing and brute-force detection routed to on-call with a runbook attached to every alert.
Who it was for: A payments platform exposed to automated card-testing traffic.
The problem. Automated enumeration against payment endpoints is both a fraud loss and an availability threat, and it doesn't announce itself. Without detection it looks like ordinary traffic until the chargebacks arrive.
What I did. Built the log pipeline into the SIEM, then wrote detections for card-testing patterns, brute force and anomalous transaction behaviour. Tuned edge rate-limiting and bot controls to cut volume at the perimeter. Every alert routes to on-call with a runbook attached, so whoever is paged at 3am has the next step in front of them.
The result. Repeat attempts are caught as they start rather than reconstructed afterward, and response is a documented procedure instead of improvisation.
0
41
Zero-downtime repository and pipeline migration
Around 70 enterprise repositories moved to a new platform with history, policies and access intact.
Who it was for: A large international organisation running enterprise development at scale.
The problem. Source control and CI/CD had to move platforms without stopping delivery. Losing commit history, branch protection or access mappings would have been worse than not moving at all.
What I did. Inventoried repositories and pipelines, then ran a staged cutover that preserved history, branch policies and access controls. Rebuilt pipelines on the target platform and wired in code scanning and quality gates on arrival, so the migration also raised the security baseline rather than just relocating it.
The result. Roughly 70 repositories migrated with no delivery downtime, and automated vulnerability detection in place from day one on the new platform.
0
53
FinOps automation across seven environments
Automated scheduling and rightsizing that took roughly $280k a year out of the cloud bill.
Who it was for: A large regional bank running seven cloud environments.
The problem. Seven environments, most of them idle outside working hours, and no visibility into which team was spending what. Cost conversations were happening after the invoice rather than before.
What I did. Established a cost baseline per environment, then automated resource scheduling so non-production stopped paying for nights and weekends. Rightsized the workloads that were provisioned for peaks that never came. Built daily and weekly cost reporting so stakeholders could see the trend without asking for it.
The result. Around $280k of annual run-rate removed, with ongoing reporting that keeps the saving from creeping back.
0
49