Follow Us on Google
The first thing Mariam Sanusi noticed wasn’t the scale, it was the silence. She was reviewing the cloud footprint of a growing healthcare analytics firm, and for all its polished dashboards and cross-region deployment charts, something critical was missing: safeguards.
The infrastructure looked efficient, but it lacked the kind of security posture necessary for a company handling sensitive patient data. The risks weren’t visible on the surface, but they were embedded deep in the architecture.
Her transition into IT Cloud Engineering came at a time when the industry was shifting rapidly toward cloud-native development. While many engineers focused on scalability, Mariam brought something different to the table: an insistence that security wasn’t an add-on, but a prerequisite.
At the healthcare firm, she was tasked with re-architecting their AWS-based infrastructure to support global operations without compromising compliance. The stakes were high, the firm needed to maintain HIPAA standards across multiple regions, and any slip could expose them to both legal and reputational fallout.
She approached the problem with precision. She began by implementing a zero-trust model across all environments, ensuring that every service, user, and data request was authenticated and authorized by design. AWS Identity and Access Management (IAM) roles were defined using least privilege principles.
CloudTrail and GuardDuty were configured for continuous monitoring, while data lakes were encrypted using AWS Key Management Service (KMS), with regional key segregation to maintain jurisdictional boundaries.
But beyond the tooling, what set her work apart was the clarity of the design. She didn’t just build infrastructure; she built policy into the foundation. Security groups were tightly scoped. Configuration drift was tracked using automation templates. And each deployment was governed by version-controlled blueprints that enforced compliance rules from the first line of code.
The firm’s leadership was quick to recognize the shift. Not only were they now meeting HIPAA compliance benchmarks across regions, they had a system that could pass security audits without last-minute patches or panicked updates. Their deployment velocity actually increased, because developers no longer had to choose between speed and safety. She had built a framework that made secure decisions the default.
In an era where businesses are racing to the cloud, she represents the kind of engineer who slows down just enough to get it right. Her background in cybersecurity gave her an edge, but it’s her ability to translate those principles into scalable architecture that has made her work stand out.
To her, cloud engineering isn’t just about moving workloads, it’s about building digital ecosystems where data can thrive without fear.
