95% of cloud breaches are due to misconfiguration

Cloud Security Assessment& Posture Management

Identify misconfigurations, eliminate vulnerabilities, and achieve continuous compliance across AWS, Azure, and Google Cloud. Our experts assess your cloud posture and deliver actionable remediation before attackers find what you missed.
  • AWS, Azure & GCP
  • CIS Benchmark Aligned
  • SOC 2 & HIPAA Mapping
A cloud engineer checking a server rack in a data centre aisle

Multi-Cloud Security Expertise

We secure your workloads across all major cloud providers with platform-specific expertise and cloud-native tooling.

AWS Security

  • IAM policy and role analysis
  • S3 bucket permission audits
  • VPC and security group review
  • CloudTrail and GuardDuty setup
  • KMS encryption validation
  • Well-Architected Security Pillar review

Azure Security

  • Azure AD and Entra ID audit
  • Network Security Group review
  • Key Vault configuration check
  • Azure Defender enablement
  • Storage account access control
  • Azure Policy compliance assessment

Google Cloud Security

  • IAM and service account audit
  • VPC firewall rule analysis
  • Cloud Storage permissions review
  • Security Command Center setup
  • Cloud KMS key management
  • Organization policy evaluation

What We Assess

Our assessment covers every critical layer of your cloud security posture, from identity to governance.

Identity & Access (IAM)

Audit user permissions, service accounts, role assignments, and access policies. Enforce least privilege and eliminate standing admin access.

Network Security

Review VPC configurations, firewall rules, security groups, and network segmentation. Identify overly permissive ingress and egress rules.

Data Protection

Validate encryption at rest and in transit, key management practices, and data classification. Ensure sensitive data is never publicly exposed.

Compliance Posture

Map your cloud environment against SOC 2, HIPAA, PCI DSS, and NIST frameworks. Identify compliance gaps and generate evidence reports.

Workload Security

Assess container, serverless, and VM configurations. Review image scanning, runtime protection, and workload isolation controls.

Cost & Governance

Identify unused resources, orphaned snapshots, and over-provisioned instances. Align security controls with cost optimization goals.

Our Assessment Methodology

A structured, repeatable process that delivers thorough coverage and actionable results every time.

01

Discovery & Inventory

Automated discovery of all cloud assets, accounts, subscriptions, and projects. Build a complete inventory of resources, configurations, and dependencies.

  • Multi-account and subscription enumeration
  • Resource tagging and ownership mapping
  • Network topology documentation
  • Third-party integration inventory
02

Configuration Audit

Systematic review of every resource configuration against CIS Benchmarks and cloud-native best practices. Flag deviations with severity ratings.

  • CIS Benchmark compliance checks
  • Cloud-native best practice validation
  • Security baseline comparison
  • Drift detection from approved configurations
03

Vulnerability Assessment

Identify exploitable weaknesses in your cloud environment including exposed services, misconfigured APIs, and insecure defaults.

  • External attack surface mapping
  • API security testing
  • Container image vulnerability scanning
  • Secrets and credential exposure checks
04

Remediation & Hardening

Prioritized remediation plan with step-by-step guidance. Implement automated guardrails to prevent misconfigurations from recurring.

  • Risk-prioritized remediation roadmap
  • Infrastructure-as-code security templates
  • Automated policy enforcement setup
  • Continuous monitoring configuration

Common Cloud Misconfigurations We Find

These are the most dangerous misconfigurations we discover during assessments. Any one of them can lead to a data breach.

Critical

Public S3 Buckets

Storage buckets exposed to the internet with public read or write access, risking data leaks and regulatory violations.

Critical

Overprivileged IAM Roles

Service accounts and user roles with excessive permissions, violating least privilege and enabling lateral movement.

High

Open Security Groups

Firewall rules allowing unrestricted inbound access (0.0.0.0/0) on sensitive ports like SSH, RDP, and database listeners.

High

Unencrypted Storage

Databases, volumes, and object storage without encryption at rest, leaving sensitive data vulnerable to unauthorized access.

Critical

Missing MFA

Root accounts and privileged users without multi-factor authentication enabled, vulnerable to credential theft attacks.

High

Excessive Admin Accounts

Too many users with full administrative privileges, increasing the blast radius of any compromised credential.

Why Invest in a Cloud Security Assessment

A proactive assessment saves money, prevents breaches, and accelerates compliance certifications.

Reduced Breach Risk

Identify and remediate the misconfigurations that cause 95% of cloud breaches. Reduce your attack surface by up to 80%.

Compliance Alignment

Map your cloud posture against SOC 2, HIPAA, PCI DSS, and NIST frameworks. Generate audit-ready compliance evidence.

Cost Optimization

Eliminate unused resources, right-size over-provisioned instances, and remove redundant security tools to reduce cloud spend.

Security Automation

Deploy automated guardrails, policy-as-code enforcement, and continuous compliance monitoring to prevent configuration drift.

Azure security, explained

How Azure controls fit together

Azure security is decided in four places: the hierarchy where policy is applied, the identities that hold roles, the network paths to your resources, and how data and secrets are stored.

Azure organizes resources as tenant, management groups, subscriptions, resource groups and resources. Role assignments and Azure Policy assignments made at a management group apply to every subscription beneath it, including subscriptions created next year by a team you have not hired yet.

Azure Policy can audit (report), deny (block the deployment), or deploy if not exists (fix it automatically, such as adding diagnostic settings). A practical baseline assigns the Microsoft cloud security benchmark in audit mode for visibility, then a short list of deny policies for the mistakes that should never reach production.

  • Management group hierarchy: platform, landing zones (prod, non-prod), sandbox
  • Allowed locations limited to Canada Central and Canada East where residency matters
  • Deny public IPs on NICs and internet-facing management ports except where approved
  • Deny storage accounts with anonymous blob access
  • Deploy diagnostic settings automatically to the central log workspace
  • Policy exemptions documented with an owner and an expiry date

Two role systems meet in Azure: Entra ID roles (Global Administrator, Privileged Role Administrator) govern the directory, and Azure RBAC roles (Owner, Contributor, User Access Administrator) govern resources. A Global Administrator can elevate themselves to User Access Administrator over every subscription, so both need protecting.

Privileged Identity Management (Entra ID P2 or ID Governance) turns standing access into eligible access: an engineer activates Owner for two hours, with MFA, a justification and, for the most powerful roles, an approver. Every activation is logged, which also gives the SOC a clean signal to correlate against.

  • No permanent Owner or User Access Administrator assignments for people
  • PIM activation with MFA, justification and approval for top roles
  • Two break-glass accounts with FIDO2 keys and sign-in alerts
  • Managed identities for Azure workloads; federated credentials for CI
  • Service principal secrets inventoried, owned and short-lived
  • Access reviews for privileged roles and guest users

Network security groups filter traffic to subnets and network interfaces. The finding to look for first is an inbound rule from Internet or Any to RDP (3389) or SSH (22): exposed RDP remains one of the most common ways ransomware operators get in. Azure Bastion or just-in-time VM access removes the need for those rules altogether.

PaaS services (Storage, Azure SQL, Key Vault, Cosmos DB) are reachable over the internet by default and protected only by authentication. A private endpoint gives the service a private IP inside your virtual network; with public network access disabled, a stolen key is useless from outside. Private DNS zones are the part that usually trips teams up, so plan them centrally.

  • No inbound internet rules to management or database ports
  • Azure Bastion or just-in-time access for administration
  • Private endpoints with public network access disabled for data services
  • Central private DNS zones linked to spoke networks
  • Azure Firewall or a network virtual appliance for egress control
  • Virtual network flow logs on for investigation

Storage account keys grant full access to everything in the account and do not expire. Prefer Entra ID authorization with RBAC, disable shared key access where your applications allow it, and never allow anonymous blob access for anything that is not deliberately public.

Key Vault should hold secrets, keys and certificates, with the Azure RBAC permission model, soft delete and purge protection. Applications read secrets through a managed identity, so connection strings stop appearing in app settings, pipeline variables and screenshots.

  • Anonymous blob access disabled at account level
  • Secure transfer and minimum TLS 1.2 required
  • Shared key access disabled or keys rotated on a schedule
  • Key Vault with RBAC, soft delete and purge protection
  • Customer-managed keys where a regulator or contract requires them

Common findings

Misconfiguration, fix, guardrail

Each fix comes with the Azure Policy or alert that stops the same finding coming back in the next subscription.
Common Azure misconfigurations with fixes and guardrails
What we findFixGuardrail that keeps it fixed
Permanent Owner on production subscriptions for several engineersEligible assignments through PIM with MFA and justificationAccess review each quarter; alert on new permanent privileged assignments
NSG allowing Internet to 3389Remove the rule; use Azure Bastion or just-in-time accessDeny policy on management ports from the internet at management group level
Storage account with a public container used for a one-off exportDisable anonymous access; share with a short-lived SAS or Entra IDDeny policy on anonymous blob access
Client secrets on service principals, some with multi-year expiryManaged identities and federated credentials; rotate what remainsAlert on new credentials added to apps; maximum secret lifetime
Activity log only in the portal, 90 days of historyDiagnostic settings to a central Log Analytics workspaceDeploy-if-not-exists policy adds diagnostic settings to new subscriptions
Defender for Cloud on the free tier only, recommendations unreadEnable plans for production workload types; assign owners to recommendationsSecure score reviewed monthly; high alerts sent to the SOC
Resources deployed to US regions by default templatesRedeploy or migrate to Canada Central or Canada EastAllowed locations policy at management group level

Defender for Cloud

What the free tier shows, and what the plans add

The free tier tells you what is misconfigured. The paid plans tell you when someone is abusing it. Enable the plans that match the workloads you actually run.

Included at no cost

  • Foundational posture management: recommendations and secure score
  • Microsoft cloud security benchmark assessment against your subscriptions
  • Asset inventory across subscriptions

Added by paid plans (examples)

  • Defender for Servers: endpoint detection, vulnerability assessment, just-in-time VM access
  • Defender for Storage: malware scanning on upload and alerts on unusual access
  • Defender for SQL and open-source databases: SQL injection and anomalous access alerts
  • Defender for Key Vault and Resource Manager: suspicious operations against keys and the control plane
  • Defender CSPM: attack path analysis and agentless scanning

Interactive tool

Azure Posture Quick Check

Eleven checks across governance, identity, network, data and detection. You get a score, each gap grouped by area with the fix, and the three to do this week.

0 of 11 checks answered

Governance

  1. 1. Are subscriptions organized under management groups, with Azure Policy assigned at that level (allowed locations, deny public IPs where not needed)?

Identity

  1. 2. Are Owner, User Access Administrator and Global Administrator held as eligible roles through PIM, not permanent assignments?
  2. 3. Is MFA required for every account that can sign in to the Azure portal, CLI or PowerShell, including break-glass accounts?
  3. 4. Do workloads use managed identities or workload identity federation instead of service principal client secrets?

Network and data

  1. 5. Are there no NSG rules allowing the internet to RDP (3389), SSH (22) or database ports?
  2. 6. Do Storage, SQL and Key Vault use private endpoints with public network access disabled where possible?
  3. 7. Do storage accounts block anonymous blob access, require secure transfer and limit shared key access?
  4. 8. Are secrets kept in Key Vault with RBAC, soft delete and purge protection, rather than in app settings or code?

Detection

  1. 9. Are Defender for Cloud plans enabled for your key workloads (servers, storage, SQL, Key Vault), with recommendations reviewed?
  2. 10. Are the Activity log and Entra sign-in and audit logs exported through diagnostic settings, and kept for more than 90 days?
  3. 11. Is someone alerted around the clock on role assignments, PIM activations, policy changes and Defender alerts?

Answer at least one check. “Not sure” is a valid answer.

Logging and monitoring

Azure logs into the GuardsArm SOC

Most Azure logs are either short-lived or off until you create a diagnostic setting. Knowing which is which decides what you can investigate later.
Azure log sources
SourceWhat it recordsDefault retention or state
Activity logControl plane: who created, changed or deleted what, role assignments, policy changes90 days in the portal; export for longer
Entra ID sign-in and audit logsWho signed in, from where, with which method; directory and role changes; PIM activationsShort in the portal and depends on licence; export for longer
Resource logsData plane: Key Vault secret reads, storage access, SQL auditOff until a diagnostic setting is created
Defender for Cloud alertsThreat detections from the enabled plansStream through continuous export
Virtual network flow logsNetwork connections in and out of your networksOff until enabled; useful in investigations
  1. Collect

    Diagnostic settings at tenant and subscription level send logs to a central Log Analytics workspace or event hub. Policy keeps new subscriptions connected.
  2. Forward

    Logs flow to the GuardsArm detection platform, with data kept in Canada, alongside your endpoint, identity and Microsoft 365 telemetry.
  3. Detect

    Detections cover privileged role assignments, PIM activations outside normal patterns, policy and diagnostic setting changes, key and secret access, and Defender alerts.
  4. Respond

    Analysts triage around the clock, escalate to your named contacts and, where pre-approved, disable accounts or revoke sessions while you decide on the rest.

Data residency

Azure in Canada

Two Canadian regions, one region pair, and policy to keep it that way.

Canada Central (Toronto) and Canada East (Québec City). They are a region pair, so geo-redundant storage replicates between them and recovery stays in the country. Canada Central offers more services and availability zones, so most organizations use it as primary.

Regional resources stay in their region. Some services are global (Entra ID, Front Door, parts of Defender), and some features process data elsewhere. Check the data residency notes for each service you use, and use the allowed locations policy so new resources cannot be created outside Canada by mistake.

Your Log Analytics workspace can sit in Canada Central. Logs forwarded to GuardsArm are stored and analysed on the GuardsArm detection platform in Canada, so monitoring does not move your data out of the country.

It shares the same Entra ID tenant, so identity work covers both. Conditional Access, PIM and break-glass accounts protect Azure and Microsoft 365 together. See Microsoft 365 security for the email and collaboration side.

Cloud Security Assessment FAQs

Common questions about cloud security assessments, CSPM, and multi-cloud security

Still Have Questions?

Our cybersecurity experts are here to help. Get personalized answers and a free security consultation.

Start Your Cloud Security Assessment

Do not wait for a breach to discover your cloud misconfigurations. Our certified experts will assess your AWS, Azure, or GCP environment and deliver a clear remediation roadmap within weeks.

No obligation. Pricing is confirmed after a short scoping call.

Cloud security assessment

Find the misconfigurations before someone else does

Cloud breaches are rarely the result of a flaw in the cloud provider. They come from how a tenant was set up: an administrator account without multi-factor authentication, a storage bucket readable by anyone, an access key committed to a repository, logging that was never switched on. These are quick to find and quick to fix once someone looks.

A GuardsArm cloud security assessment reviews identity, network exposure, data storage, logging and workload configuration across AWS, Microsoft Azure, Google Cloud and Microsoft 365 against the CIS Benchmarks and each provider’s own security guidance. Findings are confirmed by hand, ranked by what an attacker could actually reach, and delivered with the exact change to make.

The result is a prioritized remediation plan your engineers can work through, evidence for audits and customer questionnaires, and a baseline to measure against as the environment grows.

A cloud engineer checking a server rack in a data centre aisle

Identity first

Privileged roles, MFA coverage, unused accounts and keys, and trust between accounts and tenants.

Exposure

What is reachable from the internet: storage, databases, management ports and APIs.

Data protection

Encryption, key management, backups and who can read sensitive stores.

Logging and detection

Whether audit logs are on, retained and watched, so an intrusion can be seen and reconstructed.

Workloads and pipelines

Container, serverless and CI/CD configuration, including secrets handling.

Fixes your team can apply

Each finding comes with the setting or policy to change and why it matters.

Cloud assessment questions

What access do you need?

Read-only access to configuration and audit logs in the accounts or tenants in scope. No changes are made during the assessment.

How is this different from a cloud penetration test?

An assessment reviews configuration broadly against good practice. A penetration test attempts to exploit weaknesses to show what an attacker could reach. Many organizations do the assessment first and test afterwards.

Which platforms do you cover?

AWS, Microsoft Azure, Google Cloud and Microsoft 365, including multi-cloud environments.

How long does it take?

A single environment of moderate size is typically assessed and reported within two to three weeks of access being granted.

Will it help with compliance?

Yes. The report maps findings to common frameworks and gives you evidence for SOC 2, ISO/IEC 27001 and customer security questionnaires.