ConfigCobra vs AWS Security Hub
AWS Security Hub is AWS's own service for collecting security findings and running standards-based checks inside AWS accounts, while ConfigCobra is a read-only assessment and inventory service that covers Microsoft 365, Azure, Google Cloud and AWS from one workspace. Security Hub suits AWS-centred teams that want findings in their own AWS automation; ConfigCobra suits teams that want one view across several clouds with reports for clients or auditors.
At a glance
This table compares what each product documents about itself. Where the other product's pages do not say, the cell reads Not documented.
| Topic | ConfigCobra | AWS Security Hub |
|---|---|---|
| What it is | A read-only configuration assessment and inventory service for Microsoft 365, Azure, Google Cloud and AWS. | AWS's service that gives a view of your security state in AWS, runs checks against security standards and collects findings from other AWS services and supported partner products. The documentation names it AWS Security Hub CSPM. |
| Clouds covered | Microsoft 365, Azure, Google Cloud, AWS. | AWS. The documentation lists an integration topic for Microsoft Azure. |
| Benchmarks / checks | CIS Microsoft 365 Foundations Benchmark v7.0.0 (160 controls); four CIS Azure benchmarks (339 controls); CIS Google Cloud Platform Foundation Benchmark v5.0.0 (93 controls); four CIS AWS benchmarks (306 controls). Evidence and a ConfigCobra severity estimate per finding. | Security controls grouped into standards, including the AWS Foundational Security Best Practices standard and CIS AWS Foundations Benchmark v5.0.0, v3.0.0, v1.4.0 and v1.2.0. Some CIS requirements are not supported and need manual review. |
| Asset inventory (what objects it collects) | One inventory across clouds with a per-cloud and an All clouds view. Microsoft 365: users, guests, admins, groups, devices, apps, mailboxes, SharePoint sites, policies, domains, licences, roles. Azure, Google Cloud and AWS: resources with security properties. | Not documented as an asset inventory. It collects security findings and shows the accounts and resources that need attention. |
| Risk views (inactive users, guests, app secrets…) | Built-in views such as users inactive 90 days, guests who never signed in, no MFA registered, expiring app credentials. | Insights and security scores. Microsoft 365 user views such as inactive users or guests: Not documented. |
| Cost and licence savings (unused paid licences, licences of inactive users, unattached disks) | Unused paid licences view, licence data next to inactive-user views, and an unattached disks view. | Not documented |
| Remediation impact analysis (what a fix changes before you apply it) | Yes: shows what a fix changes in your environment before you apply it, with an impact level of High, Medium, Low or None. | Not documented |
| Drift monitoring and scheduled scans | Scheduled scans (daily, weekly or monthly) or ad hoc scans; alerts when a control regresses. | Continuous, account-level configuration checks; the schedule is described on a separate documentation page. Drift monitoring: Not documented. |
| Notifications | Email notifications for findings and drift. | Amazon EventBridge rules can trigger actions such as an AWS Lambda function or an Amazon SNS topic notification. |
| Reports and evidence | PDF report, audit-ready evidence export, CSV export of the inventory, read-only auditor seat. | Console dashboard, API, AWS CLI and SDK access to findings. A PDF report or evidence export: Not documented. |
| AI assistant (MCP) | Yes: a native MCP server for MCP-compatible assistants, answering from live scan data. | Not documented |
| Multi-tenant / MSP use | Yes: multi-tenant workspace; Assessment License for MSPs and auditors. | Administrator and member accounts, and cross-Region aggregation, are documented. MSP use: Not documented. |
| How it runs (install, agent, SaaS, script) | No agents; connects with read-only access. | A service inside your AWS account, used through the console, API, CLI or SDKs; AWS Config must be enabled and recording for most control findings. |
| Access it needs | Read-only: Microsoft Graph read permissions; Reader plus a read-only Graph policy permission (Azure); read-only service account (Google Cloud); read-only assume-role (AWS). | Runs inside AWS and relies on AWS Config; permission details: Not documented here |
| Licence / pricing model | 14-day free trial with full access, then an annual subscription tiered by licensed Microsoft 365 user count, or a one-time per-tenant Assessment License. | Pay-as-you-go with a 30-day free trial per account; the pricing page describes charges by resource unit and by add-on. |
What AWS Security Hub does well
AWS Security Hub CSPM is part of AWS itself, and its documentation describes it as a way to collect security data across AWS accounts, AWS services and supported partner products.
- One place for findings. It normalises findings into the AWS Security Finding Format and receives findings from services such as Amazon GuardDuty, Amazon Inspector and Amazon Macie, so alerts and configuration checks sit together.
- Checks run continuously. It runs continuous, account-level configuration checks and uses the results to calculate security scores.
- Several standards. Alongside the AWS Foundational Security Best Practices standard, it supports four versions of the CIS AWS Foundations Benchmark (5.0.0, 3.0.0, 1.4.0 and 1.2.0) and you can enable more than one version at once.
- Automation inside AWS. Automation rules update findings in near real time, and Amazon EventBridge rules can invoke a Lambda function or notify an SNS topic.
- Multi-account and multi-Region. Administrator and member accounts and cross-Region aggregation are documented.
- Native fit. It is reached through the AWS console, API, CLI and SDKs, and can be created with CloudFormation.
For a team that lives in AWS and wants findings flowing into its own AWS automation, it is a natural fit. Note that the documentation says full CIS AWS Foundations checking requires enabling it in all supported Regions, and that most control findings need AWS Config enabled.
Where ConfigCobra is different
ConfigCobra is organised as modules, and each one is available on Microsoft 365, Azure, Google Cloud and AWS.
- CSPM. CIS benchmark assessment for all four clouds, with evidence and a severity estimate per finding and a dashboard showing the compliance score, passing and failing controls and the most severe failures. The severity is ConfigCobra's own estimate; CIS publishes no severity.
- Inventory & Insights. One inventory across clouds, built-in risk views, a relation graph showing how objects connect (membership, ownership, roles, licences, mailbox delegation, Conditional Access scope, Azure resource dependencies), findings linked to the objects they concern, and CSV export.
- Cost & licence optimisation. Views of the inventory for unused paid licences, inactive users and unattached disks.
- Remediation impact analysis. For a failing control, the affected users, groups, mailboxes, apps, policies, resources or identities, each with the expected effect, a confidence level and a prepare step.
- Monitoring & drift detection. Scheduled scans (daily, weekly or monthly, set by you) and ad hoc scans, with email notifications when a control regresses.
- Reports & evidence. A PDF report with findings, evidence and a timestamped snapshot, an audit-ready evidence export, and a read-only auditor seat for clients or external auditors.
- AI assistant. A native MCP server so an MCP-compatible assistant such as Claude or Cursor can answer questions from live scan data.
- Multi-tenant workspace. Assess subsidiaries or client tenants from one place.
ConfigCobra is read-only and never changes your tenant. Fixes are suggested as scripts or portal steps for you to apply.
The main differences are scope and shape. ConfigCobra assesses Microsoft 365, Azure and Google Cloud as well as AWS from one workspace, and it runs outside the AWS account with read-only assume-role access (AWS: four CIS benchmarks, 306 controls). Security Hub CSPM, by contrast, is focused on AWS and on aggregating findings from other AWS services, which ConfigCobra does not do.
Which one to choose
- Choose AWS Security Hub if your estate is mostly AWS, you want findings from GuardDuty, Inspector and Macie in one place, and you want to wire findings into your own AWS automation.
- Choose ConfigCobra if you also run Microsoft 365, Azure or Google Cloud and want one inventory, one set of risk views, licence and disk waste views, impact analysis before a fix, and reports with an auditor seat. It suits consultants who manage several tenants.
- Choose both if you want AWS-native finding aggregation and a separate, read-only benchmark and inventory view that also covers your other clouds.
How to move or run them side by side
- Leave Security Hub CSPM enabled. ConfigCobra does not alter its settings, standards or automations.
- Start the 14-day free trial, which has full access to every available module and control.
- In each AWS account, create a read-only IAM role with an external ID that ConfigCobra can assume. Add your other clouds the same way, with read-only access.
- Run an ad hoc scan and compare the failing controls with your Security Hub CSPM findings. The two follow different benchmark versions, so match by resource and by CIS requirement rather than by title.
- For each control you plan to fix, read the remediation impact analysis first, then apply the change through your own process. ConfigCobra never changes the tenant.
- Set a daily, weekly or monthly schedule with email notifications, and keep your EventBridge automations in AWS as they are.
Last checked against AWS's public documentation on 2026-11-09.
Sources
- docs.aws.amazon.comhttps://docs.aws.amazon.com/securityhub/latest/userguide/what-is-securityhub.html
- docs.aws.amazon.comhttps://docs.aws.amazon.com/securityhub/latest/userguide/cis-aws-foundations-benchmark.html
- docs.aws.amazon.comhttps://docs.aws.amazon.com/securityhub/latest/userguide/automations.html
- aws.amazon.comhttps://aws.amazon.com/security-hub/pricing/
Facts about AWS Security Hub come from its public documentation, last checked 8 Nov 2026. Product names and trademarks belong to their owners. Spotted something out of date? Tell us.
See where your cloud stands
ConfigCobra checks Microsoft 365, Azure, Google Cloud and AWS against the CIS benchmarks, read-only.