Posture assessment
Every account or subscription reviewed against CIS Benchmarks and provider guidance, using Security Hub, Defender for Cloud or Security Command Center alongside manual checks.
Service · Cloud
Commission us to find and fix weaknesses in how your cloud accounts are configured: over-broad permissions, exposed storage, unmanaged secrets and missing audit logs. We deliver remediated configuration, preventive guardrails and evidence your auditors can follow.
Findings ranked by exploitability
Fixes delivered as code, not tickets
Controls mapped to your framework
Deliverables
Every account or subscription reviewed against CIS Benchmarks and provider guidance, using Security Hub, Defender for Cloud or Security Command Center alongside manual checks.
Unused permissions removed based on access analysis, wildcard policies replaced with scoped ones and long-lived access keys retired in favour of federated roles.
Credentials moved into Secrets Manager, Key Vault or Secret Manager with rotation configured, and hard-coded secrets purged from repositories and images.
Service control policies, Azure Policy or organisation policies that refuse public buckets, unencrypted volumes and unapproved regions before they exist.
Organisation-wide audit trails, centralised log storage with retention, and detection rules for high-risk events such as root sign-in or logging being disabled.
Early decisions
Whether controls map to ISO 27001, SOC 2, PCI DSS or a sector regulation, which shapes evidence format and priorities.
Which risks policy blocks outright and which are allowed but alerted on, balancing safety against teams’ ability to work.
Provider-managed keys or customer-managed keys in KMS or Key Vault, and who may use, rotate or disable them.
Just-in-time elevation, approval flows and session logging in place of standing administrator rights.
Which fixes we apply directly and which go to workload teams as ready-to-review code changes.
Engagement
We connect with audit-only roles, run automated scans and manually review identity, network, data and logging configuration.
Findings are ordered by how easily they could be exploited and what they would expose, and agreed with you before any change.
Fixes land as Terraform, CloudFormation, Bicep or policy changes through your pipeline, so they cannot quietly drift back.
Posture scanning stays switched on, drift alerts reach the owning team and we compile control evidence for your next audit.
Fit
SOC 2, ISO 27001 or an enterprise buyer’s review needs cloud controls you can actually demonstrate.
Many accounts, many administrators and no consistent policy usually means exposure nobody has measured.
A leaked key or a briefly public bucket is reason to review everything else configured the same way.
Alternatives
Flaws in authentication logic, input handling or dependencies call for application security work rather than cloud posture.
Open registerBuilding a landing zone with guardrails from the start is cheaper than hardening an unstructured estate.
Open registerKubernetes RBAC, pod security and image provenance are best handled within cluster operations.
Open registerAttackers rarely need a novel exploit when a storage bucket is public or an administrator key sits in a repository. Reviewing identity, storage exposure and logging closes the paths that are both common and easy to abuse.
Writing narrow IAM policies by hand often breaks applications. We use access analysis to see which permissions each role actually exercised over a period, then remove the rest in stages with monitoring in place.
Detection tools produce long finding lists that teams learn to ignore. Organisation-level policies that decline to create a public bucket or switch off encryption remove whole categories of findings permanently.
For each control we record the policy that enforces it, the log that proves it and the person responsible. Audit preparation then becomes exporting what already exists instead of gathering screenshots.
Emergency access accounts are necessary and dangerous in equal measure. We keep a small number of break-glass identities protected by hardware keys, store their credentials outside normal tooling, and alert the security owner the moment one signs in. Each use is reviewed afterwards and the credentials are rotated.
Vendors and contractors are a common blind spot. Monitoring tools, backup services and support partners often hold cross-account roles granted years ago. We list every external principal with access, confirm each still has a business reason, require external IDs or federation for those that remain, and remove the rest.
FAQ
Not for the assessment; read-only audit roles are enough. Remediation goes through your pipeline or is applied under a time-limited role you grant and then revoke.
No. This work reviews configuration and permissions in your cloud control plane. Testing applications for exploitable flaws belongs to our IT security service.
Yes. We assess AWS, Azure and Google Cloud and map findings to a single control set, so reporting stays consistent across providers. Equivalent controls differ in name and mechanism, such as service control policies versus Azure Policy, so we note where a provider can enforce a rule and where it can only be detected.
Automated posture checks keep running and route new findings to owners. We can return periodically to review drift and help assemble audit evidence.
Related services
Policy and secret scanning built into pipelines so problems are caught before deployment.
Open registerDestination controls verified before sensitive workloads move across.
Open registerBroader security strategy and vendor decisions beyond cloud configuration.
Open registerPrimary sources
Dated official documentation, standards, and research that support the factual claims on this page.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.