Skip to content
MVPeopleGroup
Back to insightsCloud Security

What does a cloud security engineer do, and when to hire?

Mathijs VisserNovember 21, 20266 min read
What does a cloud security engineer do, and when to hire?

A cloud security engineer looks after the part of cloud security your provider leaves to you: identities and permissions, configuration, logging and network segmentation in Azure, AWS or Google Cloud. The provider secures its data centres. Whatever you switch on, configure and connect is yours to get right.

Where the provider stops and you start

Every cloud security role is built around the shared responsibility model. Microsoft's guidance on shared responsibility lists four things that always stay with the customer, whichever service model you pick: data, endpoints, accounts and access management. Amazon frames it as security of the cloud versus security in the cloud. Under the AWS shared responsibility model, customers manage their own data and encryption options and set permissions through IAM. Run a virtual server and patching the guest operating system and configuring its firewall rules fall to you as well.

That customer side is the cloud security engineer's patch, and it splits into four areas.

Identity and permissions

In the cloud, identity is the perimeter. An admin account without multi-factor authentication, or a service account with sweeping rights, is all an attacker needs. The engineer designs roles around least privilege, clears out orphaned accounts and stale keys, and makes sure admin rights are only ever granted for a limited time. Much of this sits close to identity and access management, so expect plenty of joint work with the IAM team. My piece on IAM consultants, engineers and architects covers those roles.

Configuration and guardrails

A storage bucket left open to the internet usually comes down to one wrong setting. The engineer puts policies in place that stop that kind of mistake before it reaches production, sets secure defaults for each environment and reviews infrastructure-as-code templates. Cloud security posture management (CSPM) tools flag where configuration has drifted. Deciding which of those findings matter, and getting them fixed, is the engineer's call.

Logging and detection

Without logs you cannot work out what happened after an incident. The engineer turns on audit and activity logging across every subscription and account, sets retention periods and feeds everything into the SOC's SIEM. In the Netherlands there is a legal angle too. The Cyberbeveiligingswet, the Dutch law that implements the EU's NIS2 directive, came into force on 15 August 2026 and requires organisations in scope to report significant incidents. You can only report what you can reconstruct.

Network segmentation

One compromised workload should not be able to reach everything else. The engineer separates production, test and development, restricts traffic with security groups and private endpoints, and keeps management interfaces off the public internet.

Cloud security engineer or architect?

The cloud security architect designs the landing zone, the identity model, the network layout and the tooling choices. The engineer builds that design, keeps it running and sorts out whatever breaks from day to day. For a new cloud environment or a large migration, start with an architect. If the platform is already live and findings keep piling up, you need an engineer.

Smaller organisations often look for one senior person who can do both. That can work, although the design work is usually the first thing to slip when something catches fire.

There is overlap with DevSecOps as well. A DevSecOps engineer secures the CI/CD pipeline through scanning, secrets handling and checks on infrastructure as code, while the cloud security engineer looks after the environment that code lands in. I set out the DevSecOps role in what a DevSecOps engineer does.

Put them in the platform team

My advice: place the cloud security engineer inside the platform team, not in a separate security function that reviews the work after the fact.

A security team at arm's length only spots a misconfiguration once it is live. Then comes a ticket, an argument about priority and a fix that drags on for weeks. An engineer who sits with the people building the landing zone and the pipelines makes security part of the default build, so every new environment gets the right logging, roles and network rules from the first day. The CISO or security officer still reviews, at the level of policy and risk, without checking every setting personally.

When to hire a cloud security engineer on an interim basis

Interim suits work with a clear start and finish. Moving out of your own data centre into Azure or AWS is the obvious case. An audit finding on cloud configuration that has to be closed within a few months is another.

Financial institutions have DORA to factor in. The EU's Digital Operational Resilience Act has applied since 17 January 2025 and calls for a sound, well-documented ICT risk management framework. ESMA counts managing ICT third-party risk, key contractual provisions with suppliers and a register of information on those arrangements among DORA's core elements. Your cloud provider is one of those ICT suppliers, so I would read those requirements as applying to your cloud estate. A cloud security engineer helps you show that your side of the shared model is in order. For Dutch organisations under the Cyberbeveiligingswet, the same goes for the duty of care: appropriate measures to keep services running.

If the work is ongoing because the platform keeps growing and changing, a permanent hire or a secondment is a better fit. Still weighing up what to hand to a provider and what to keep in-house? My comparison of MSSPs, interim specialists and secondment may help.

What to put in the brief

State the platform and the scale: Azure, AWS or Google Cloud, how many subscriptions or accounts, and whether a landing zone is already in place. Describe the problem and leave out the shopping list of tools. "Our CSPM tool throws up hundreds of findings and nobody picks them up" tells a candidate far more than "experience with cloud security tooling". Say which team the engineer will join and who they report to. I would firm that up before the first interview.

Looking for a cloud security engineer or architect for a migration or an audit finding? Have a look at our cloud security expertise and interim hiring through MVPeople, or call or email me and we will work out which profile fits.

Mathijs Visser

Mathijs Visser

Co-founder and Lead Consultant, MVPeople Group

Mathijs Visser founded MVPeople Group in 2022 and has recruited IT and cybersecurity professionals for Dutch enterprise organisations for more than 16 years. He specialises in interim CISO, IAM and GRC assignments.

Follow MVPeople Insights on Google

Add mvpeoplegroup.com as a preferred source to see our articles more often in Google's Top Stories and AI answers.

Want to know more?

Do you have questions about this article? Or would you like to discuss your specific situation? Get in touch with us, no strings attached.

READY TO FIND THE RIGHT CYBERSECURITY PROFESSIONAL?