Cloud security consultant contract work is mostly scoped reviews: a configuration review of an AWS, Azure or GCP environment against the CIS Benchmarks, an IAM review, a look at logging and network exposure, sometimes a Kubernetes or infrastructure-as-code review. The contractors who get repeat work hold access lightly, stay read-only, and write findings an engineer can fix the same week.
What cloud security contract work actually looks like
A client, or the firm that holds the client, has a reason to look at the cloud estate now: a SOC 2 or ISO 27001 audit is coming, a customer sent a security questionnaire with uncomfortable questions about the production account, a new engineering lead inherited an environment nobody documented, or an investor wants an outside view. The scope is usually one or more of these:
- Configuration review against the CIS Benchmarks. The CIS Foundations Benchmarks for AWS, Azure and Google Cloud give a shared, checkable baseline. The review is not the benchmark run. It is deciding which failures matter for this client and which are accepted design choices.
- Identity and access review. Who and what can do what: human users, federated roles, service accounts, workload identities, cross-account trust, long-lived access keys, standing administrator access and break-glass accounts.
- Logging and monitoring. Whether control-plane audit logs are on in every account, project and region that matters, whether they land somewhere an attacker with admin rights cannot quietly delete, how long they are kept, and whether anyone is alerted on the events that would matter in an incident.
- Network exposure. Security groups and firewall rules open to the internet, public storage buckets, databases with public endpoints, exposed management ports, and the gap between what the architecture diagram shows and what is actually reachable.
- Kubernetes and container reviews. Cluster configuration against the CIS Kubernetes Benchmark or the managed-service variants, RBAC, pod security settings, network policies, secrets handling, image provenance and the permissions the cluster's workloads hold in the cloud account itself.
- Infrastructure-as-code review. Terraform, CloudFormation, Bicep or Pulumi in the repository, reviewed for the same issues before they reach production, and for drift between what the code says and what is deployed.
- Evidence for SOC 2 and ISO 27001. Screenshots, configuration exports and written descriptions that an auditor can rely on, mapped to the controls the client has committed to.
Most engagements combine two or three of these. A pre-audit review for a SaaS company on one AWS organization might be IAM, logging and exposure, with a short section on evidence. Our buyer guide on the AWS security review before SOC 2 shows that scope from the client's side, which is worth reading before you quote one.
Read-only access discipline
The first decision on any cloud review is the access you ask for, and asking for too much is a quiet signal that you have not done this before. For a configuration or IAM review you need to read configuration, not change it. Each provider has a sensible starting point: the AWS managed SecurityAudit or ReadOnlyAccess policies, the Reader and Security Reader roles in Azure, and the Viewer and Security Reviewer roles in Google Cloud. Ask for the narrowest one that covers the scope, and say why if you need more.
Habits that keep you out of trouble:
- Federated, time-bound access. A role you assume from your own identity, or a guest account in the client's directory, with an expiry date. Avoid long-lived access keys created for you. If the client insists on one, note it as a finding about their own process and ask for it to be deleted at the end.
- No data-plane reads unless scoped. Read-only policies can still allow reading objects in storage or querying some data services. Being able to read a customer database is not the same as being authorized to. Stick to configuration unless the scope says otherwise.
- A written list of what you ran. Tool names, versions, the accounts or subscriptions they ran against, and when. If a monitoring alert fires during your review, the client should be able to match it to you in minutes.
- Clean exit. At the end, confirm the client has removed your role, and delete exported configuration from your machine on the schedule you agreed.
Active testing, such as probing exposed services or trying a privilege escalation path, is a penetration test. It needs written authorization from someone with authority over the account, a scope that names the targets, and attention to the provider's own testing policy, since AWS, Microsoft and Google each publish rules on what customers may test. In Canada, unauthorized access to a computer system is an offence under section 342.1 of the Criminal Code. If your scope changes from reading configuration to touching workloads, the paperwork changes too. Our post on contract penetration testing work covers that side in more detail.
Findings that engineers act on
A scanner can produce three hundred failed checks in an afternoon. Nobody pays a consultant for that list. They pay for the ten things that matter, explained well enough that the engineer who owns the account fixes them without a meeting.
A finding that gets fixed usually has:
- The specific resource. The role ARN, the subscription and resource group, the project and service account. Not "some IAM roles have broad permissions".
- The path, not the rule. "This CI role can assume the production admin role, so anyone who can change the pipeline can act as admin in production" lands harder than "role trust policy too permissive".
- Severity that reflects context. A public bucket that serves a marketing site's images is not the same finding as a public bucket with database backups. Say which one it is, and use a stated, consistent rating method.
- A fix in their tooling. If the environment is built with Terraform, give the change in Terraform terms. A console click-path fix will be reverted by the next apply.
Group the many low-value benchmark failures into one appendix with the raw output, and say plainly that they were reviewed. If you want a reference point for the whole document, our post on what a security deliverable looks like walks through the structure a client expects to receive.
Compliance-driven reviews
A large share of cloud review work in Canada comes from compliance. A SaaS company pursuing SOC 2 needs to show that access is restricted, changes are controlled, logs are kept and monitored, and data is encrypted. An ISO 27001 program needs the same kinds of controls reflected in its Statement of Applicability.
The auditor is a second reader of your work. That changes a few things. Dates matter, because evidence has to fall inside the audit period. Scope statements matter, because the auditor will ask whether the review covered every production account. And the line between your review and the client's controls matters: you can describe the configuration you observed, but the client owns the control and the ongoing evidence of it. Avoid language that sounds like you are certifying the environment. You reviewed it on a date, against a stated baseline, and reported what you found.
Credentials, tools and setup
Clients and firms engaging cloud contractors look for hands-on time in real environments first. Certifications help a CV get read and are a common shorthand:
- CCSP from ISC2, which is vendor-neutral and broad.
- AWS Certified Security Specialty.
- Microsoft's Azure security engineer certification.
- Google Professional Cloud Security Engineer.
- Kubernetes security credentials such as the CKS, for container-heavy work.
None of these is required by law, and none replaces the ability to read a messy IAM policy and say what it actually allows.
On tools, open-source scanners such as Prowler, ScoutSuite, kube-bench and Checkov cover a lot of the benchmark work and run comfortably with read-only access. Check the licence terms of anything you use commercially. Keep a dedicated work machine with full-disk encryption, do not keep client exports in personal cloud storage, and know your retention period before the engagement starts. If you incorporate or bill independently, you will need to register for GST/HST once you pass the small supplier threshold, and professional liability insurance is something most firms and direct clients will ask about.
Where the work comes from
Independent cloud consultants find work through roughly the same channels as other security contractors: subcontracting for consulting firms and MSPs that already hold the client, vetted associate networks, referrals from engineering leads you have helped before, and occasionally direct clients who found you through something you published. Our roundup of cybersecurity freelance platforms compares the main options, and the compliance side of the same market is covered in contract SOC 2 and ISO 27001 consulting work.
Where the TrazTech Associate Network fits
We run the TrazTech Associate Network, so weigh this accordingly. The Associate Network is how TrazTech brings independent practitioners into client work, and cloud and infrastructure is one of its practices, alongside offensive security, compliance readiness, security leadership, privacy, AI governance and audit. The full list of roles is on our careers page.
Associates are independent contractors, not employees. The work is remote, open to people in Canada and the US, part-time or full-time, with no exclusivity, so you keep your other work. You need at least five hours a week, and if you are employed, your employer has to allow side work. There is no experience minimum, and newer associates are paired with a paid senior mentor.
Applying takes about five minutes. If you hold a verified credential such as the CCSP or a cloud security specialty certification, you skip the simulated assessment. Otherwise you complete a simulated client engagement of about three hours of work, with 72 hours to submit. A selection call follows, then portal setup with the agreement signed online.
Work is offered as fixed-scope work orders. You see the scope and the fee before you accept, you can decline, and the fee is fixed per milestone and agreed before work starts. You are paid every Friday, by Interac e-Transfer or against your own invoice in CAD or USD. Larger engagements run as teams with a Lead, coverage checklists keep the work consistent, and a TrazTech Principal reviews and signs off every deliverable before the client sees it. All testing runs through the TrazTech VPN, and you use your own tools. You also get a TrazTech email address, a verified credential for LinkedIn, paid mentoring and Lead reviews, referral bonuses, and a path from Associate to Senior, Lead and the core team. Work follows client demand in your practice, so approval does not guarantee a volume of work.
Common questions about cloud security consultant contract work
What does a cloud security consultant do on a contract?
Usually a scoped review of one or more cloud environments: configuration against the CIS Benchmarks, identity and access, logging, network exposure, Kubernetes or infrastructure-as-code, often tied to a SOC 2 or ISO 27001 audit. The output is a prioritized findings report with fixes the client's engineers can apply.
What access should I ask for on a cloud configuration review?
The narrowest read-only role that covers the scope, such as SecurityAudit in AWS, Security Reader in Azure or Security Reviewer in Google Cloud, granted through federation with an expiry date. Avoid long-lived keys and do not read customer data unless the scope says so.
Which certifications help with cloud security contract work?
The CCSP and the provider security certifications from AWS, Microsoft and Google are the common ones, with the CKS for Kubernetes work. They help a CV get read, but firms weigh hands-on experience and sample findings at least as heavily.
Is a cloud configuration review the same as a cloud penetration test?
No. A configuration review reads settings with read-only access and reports weaknesses. A penetration test actively attempts to exploit them, which needs written authorization, a named scope and attention to the provider's testing policy.
Take scoped cloud review work as an independent associate. You see the scope and fee on every work order before you accept, and a verified cloud credential skips the simulated assessment.
Apply to the networkSee the role