Cloud Security Monitoring and Assurance | ThreatDefence
Skip to content

Multi-Cloud Security Assurance

Detect cloud threats. Find exposed resources. Keep configurations secure.

Cloud Assurance, Continuously

Your cloud changes every day, so assurance has to keep up. ThreatDefence monitors activity and configuration across your cloud environments, connecting security weaknesses with the activity that could exploit them.

Agentless Monitoring

Connect cloud accounts and SaaS services through authorized integrations, with no agents needed for audit and configuration monitoring.

Cloud Threat Detection

Identify suspicious access, privilege changes, credential abuse, and attempts to disable security logging.

Configuration Assurance

Check supported environments against CIS benchmarks and track changes that weaken security.

Connected Investigation

Bring cloud findings together with identity, endpoint, and network evidence in the ThreatDefence AI SOC platform.

Every Cloud Account in One View

See connected accounts, incoming activity, security findings, and configuration status from one dashboard. Track when each source last reported and identify missing coverage before an investigation depends on it.

Monitor AWS, Azure, Microsoft 365, Entra ID, Google Workspace, Okta, Cloudflare, and Google Cloud through supported integrations. Each source adds evidence to the same operational view.

ThreatDefenceFAIR 62↓7.0Search pages…secops › acmeacme30d61
Cloud Accounts
Connected accounts
Control plane events, 24h1.44M
Open findings29
Agents installed0
Cloud posture86/100
Accountsread-only, authorized by acme-corp admins
SourceAccountMethodEventsFindingsLast
AWSacme-prodOrganization trail412,8807now
AWSacme-dataOrganization trail96,2143now
AWSacme-devOrganization trail58,70391m ago
AWSacme-securityOrganization trail31,402–now
AZUREacme-sub-prodActivity log, Event Hub131,5594now
AZUREacme-sub-sharedActivity log, Event Hub22,41712m ago
AZUREacme-sub-drActivity log, Event Hub6,143–4m ago
M365acme-corp.comManagement Activity API287,33021m ago
ENTRAacme-corp.comGraph sign-in and audit118,09211m ago
GWSacme-corp.comReports API14,906–3m ago
OKTAacme-corpSystem Log API41,228–1m ago
CFacme-corp.comLogpush205,6612now
GCPacme-analyticsCloud Audit Logs9,812–2m ago
Events by provider24h
AWS
599,199
Microsoft 365, Entra
405,422
Cloudflare
205,661
Azure
160,119
Okta
41,228
Google Workspace
14,906
Google Cloud
9,812
Coverageby layer
Control planeall accounts100%
Identity and accessEntra ID, Okta, IAM100%
SaaS audit3 of 3 services100%
Edge and webCloudflare, WAF100%
ConfigurationCIS checks92%

Secure Your Side of the Cloud

Cloud providers protect the underlying infrastructure, but your organization still has responsibilities for access, data, and configuration. The split varies by service: managing a virtual machine is different from securing a SaaS tenant.

ThreatDefence helps monitor the areas you control, from privileged access and storage permissions to audit logging and security settings. Findings reach your team with the evidence and recommended next steps.

LayerResponsibilityCoverage
Detection and response
You own it
Delivered by ThreatDefence alongside your team: 24x7 investigation, containment and reporting
Identity and access
You own it
Monitored: sign-ins, privileged roles, keys and consent grants. Response: revoke sessions, deactivate keys
Data
You own it
Monitored: storage permissions, sharing changes and bulk reads where logged. Response: restore access policies
Configuration
You own it
Monitored: CIS checks, security settings and audit logging. Response: prepared configuration changes
Workloads
Shared
Monitored: instance changes, security groups and workload findings, plus the endpoint agent where installed
Platform and physical infrastructure
Provider
Secured by your cloud provider
Your cloud providerYour responsibility, monitored by ThreatDefenceDelivered by ThreatDefence

Watch the Control Plane

Changes to cloud permissions, resources, and logging can give attackers access or help them hide. ThreatDefence examines administrative activity to identify risky changes and connect them with the account, session, and resources involved.

Review AWS CloudTrail, Azure activity logs, and SaaS audit records in dedicated dashboards. Move from an unusual API call to the surrounding activity without switching between provider consoles.

ThreatDefenceFAIR 62↓7.0Search pages…secops › acmeacme30d61
AWS CloudTrail
Failed calls412
Write actions18,906
Console sign-ins
Principals
AWS accounts3
CloudTrail risk scorelast 24h
68elevated
Trail tampering1
Keys used from a new network1
Policy made public1
Console sign-ins without MFA0
Root account activity1
By accountscore
acme-prod68
acme-dev41
acme-data22
Write actions over time30 days
30 Sep10 Oct20 Oct29 Oct
Top API callsevents
DescribeInstances
41,240
AssumeRole
18,862
GetObject
12,106
PutObject
6,418
UpdateFunctionCode
1,912
CreateAccessKey
6
Risky actions watchlistsorted by time
TimePrincipalActionAccountWhy it is here
02:13:44svc-deployCreateAccessKeyacme-prodnew ASN
02:21:37svc-deployPutBucketPolicyacme-prodpublic read
02:22:02svc-deployStopLoggingacme-prodtrail tampering
03:40:18ops-adminAttachUserPolicyacme-devAdministratorAccess
04:02:51build-runnerRunInstancesacme-devunused region
05:16:09rootConsoleLoginacme-dataMFA used
Privilege Changes

Investigate new administrative permissions, altered roles, and policy changes outside expected activity.

Credential Abuse

Detect suspicious key creation and credential use from unfamiliar networks or unexpected locations.

Public Exposure

Identify storage, databases, and services opened to broader access.

Resource Abuse

Find unexpected compute deployments, activity in unused regions, and other signs of unauthorized resource use.

Unusual Data Access

Examine bulk reads, downloads, and sharing changes where the relevant data-access logs are enabled.

Logging Tampering

Detect attempts to stop audit trails, alter logging configuration, or reduce security visibility.

Investigate Across Your Stack

A new access key may be routine administration or the start of a compromise. The surrounding activity makes the difference.

AI agents query connected cloud, identity, endpoint, and network sources to establish who created the key, how it was used, and what followed. Analysts receive an assessment with the timeline, supporting evidence, and response actions prepared.

Example: Suspicious Access Key. An illustrative investigation could connect:

  • An administrator signing in from an unfamiliar network.
  • A new key created for a service account.
  • The key being used from infrastructure outside the normal deployment process.
  • Unusual object access in a monitored storage bucket.
  • A policy change allowing public access.
  • An attempt to stop audit logging.

Together, those findings justify a different response from an isolated key-creation event. The platform retains the evidence behind the assessment and applies your approval rules to containment.

ThreatDefenceFAIR 62↓7.0Search pages…secops › acmeacme30d61
Investigation
CriticalAccess key created and used from a new networkopened 02:22:05
Evidence timelinecloud, identity, endpoint, network
02:11:52ENTRA

Sign-in by ops-admin from a new country, MFA satisfied by push

Identity
02:13:44AWS

CreateAccessKey for svc-deploy, created by ops-admin in the console

Control plane
02:15:09AWS

New key used from AS64511, a network never seen for this account

Control plane
02:18:30AWS

GetObject 1,842 times on acme-backups, 2.1 GB read

Data
02:21:37AWS

PutBucketPolicy opens acme-backups to public read

Exposure
02:22:02AWS

StopLogging on acme-org-trail

Tampering
02:22:40AGENT

ACM-ADM-02, the admin workstation, idle: no console or CLI session

Endpoint
02:22:41NDR

No traffic to AWS from the admin network in the window

Network
AI assessment5 sources queried

The key was created from a session that began with an unfamiliar sign-in, used from a network the account had never touched, and followed by a bulk read, a public policy and a logging stop. The admin workstation shows no matching activity.

VerdictMalicious
Confidence94%
To contain9 min
Responseinside your agreed authority
Deactivate access key for svc-deployDone
Revoke ops-admin sessions in Entra IDDone
Restore acme-backups bucket policyAwaiting approval
Re-enable logging on acme-org-trailAwaiting approval

Find and Fix Misconfigurations

ThreatDefence’s cloud security posture management capabilities check supported configurations against CIS benchmarks. See failing checks by account, resource, and severity, with the detail your administrators need to investigate and remediate them.

Benchmark Your Environment

Review supported AWS, Azure, and Microsoft 365 configuration checks, with results linked to the affected resources.

Track Security Drift

Identify changes that weaken protection, such as an exposed management port, broader storage access, or disabled security settings.

Prioritize Exposed Resources

Bring exposure and resource context into remediation decisions, helping teams address the most consequential findings first.

Verify Remediation

Confirm when a failing check passes and retain the result history for reporting and review.

ThreatDefenceFAIR 62↓7.0Search pages…secops › acmeacme30d61
Cloud CIS
Critical fails6
High fails23
Pass rate
Resources1,284
Unique checks312
Top failing checksranked by exposure
CheckSourceResourcesSeverity
S3 bucket allows public read accessAWS3Critical
Root account has an active access keyAWS1Critical
Network security group allows RDP from the internetAzure2Critical
CloudTrail not enabled in every regionAWS1High
Access keys older than 90 daysAWS9High
Storage account allows public blob accessAzure4High
Legacy authentication allowed for some usersM3656High
Key Vault without purge protectionAzure2Medium
Benchmark mixthis week
Passed 2,904Failed 302Manual 171
AWS
84%
Azure
79%
Microsoft 365
91%
Configuration driftas it happens
acme-web-nsgInbound 3389 from any source added
14 min ago
j.park
acme-logsVersioning suspended
2 h ago
svc-terraform
acme-corp.comSecurity defaults re-enabled
6 h ago
it-admin

Turn Findings Into Audit Evidence

Use configuration results, investigation records, and remediation history to support security assessments. Reports connect relevant findings with control requirements and preserve the evidence behind them.

Prepare technical reports for administrators, assurance summaries for customers, and evidence packs for assessors. Track outstanding findings and show what has changed between reviews.

Reporting can support frameworks such as ISO 27001, PCI DSS, NIST, and SOC 2, with the applicable scope and mappings agreed for your environment. Technical checks contribute evidence; organizational controls and formal assessments remain part of the wider compliance process.

ThreatDefenceFAIR 62↓7.0Search pages…secops › acmeacme30d61
Reports
Report library
ReportMapped controlsEvidence referencesOutstandingLast run
Cloud configuration, technicalCIS AWS, Azure, M3654121,89023Today, 06:00
ISO 27001 evidence packISO/IEC 27001:2022, Annex A38644928 Oct
PCI DSS evidence packPCI DSS v4.0.127418628 Oct
NIST control summaryNIST CSF 2.0467021121 Oct
SOC 2 evidence packTrust Services Criteria31509714 Oct
Customer assurance summaryPosture and open findings–962328 Oct
Report history
ISO 27001 evidence pack9 outstanding, 4 fewer than September
PCI DSS evidence pack6 outstanding, 2 resolved since last report
NIST control summary11 outstanding, 1 new failing check
SOC 2 evidence packShared with assessor

Make Cloud Risk Clear

Give leadership a view of cloud security they can act on. ThreatDefence brings configuration weaknesses, identity risks, vulnerabilities, and active findings into posture dashboards, with the underlying issues available to inspect.

See which accounts need attention, which findings remain unresolved, and whether remediation is improving the position over time. Cloud results also feed the wider cyber risk view alongside endpoint, network, and external exposure findings.

ThreatDefenceFAIR 62↓7.0Search pages…secops › acmeacme30d61
Security Posture
Composite postureall connected sources
of 100
Goodup 7 in 30 days

One score across exposure, vulnerabilities, identity, email, endpoint, network and cloud.

External exposure71
attack surface
Vulnerabilities64
patch and CVE state
Cloud and compliance86
CIS and frameworks
Identity and access82
MFA, roles, sign-ins
Email security90
mail threats and rules
Endpoint88
agents and EDR
Network79
firewall and sensors
Dark web93
leaked credentials
What moves the scorefix these first
+6Close public read on acme-backups and 2 other buckets
+4Enforce MFA for 3 AWS console users
+3Rotate 9 access keys older than 90 days
+2Block legacy authentication for 6 Microsoft 365 users

Respond With Control

Move from a confirmed finding to action across supported cloud and identity integrations. Deactivate compromised keys, revoke sessions, disable accounts, or prepare configuration changes under the authority you define.

Set Permissions Per Action

Monitoring connections use the access needed to collect evidence. Response requires separately authorized permissions.

Approve Before Execution

Review proposed changes with their targets, evidence, and expected impact before releasing them.

Automate Approved Actions

Allow specific actions to run within defined conditions and limits, with anything outside that scope escalated.

Track the Outcome

Keep requests, approvals, execution results, and follow-up checks in the same case.

Response plan, CASE-5127
Deactivate access keysvc-deploy, key created 02:41
AutomatedExecuted 02:52
Revoke sessionsops-admin, all active sessions
Approved by j.ortizExecuted 02:55
Stop public accessacme-backups bucket policy
Awaiting approvalPrepared
Restore audit loggingacme-org-trail
AutomatedExecuted 02:53
Recovery

Rotate the svc-deploy key in the deployment pipeline, then confirm CloudTrail delivery and the bucket policy pass their CIS checks.

Ownerplatform-teamFollow-up checkScheduled, 04:00

24x7 Cloud Security Operations

Cloud threats do not wait for your administrators to start work. ThreatDefence’s SOC investigates escalations around the clock, using the same platform evidence your team can access.

AI agents gather context and prepare findings. Analysts validate the assessment, coordinate response under your procedures, and contact the right people when a decision is needed.

Every investigation keeps its queries, evidence, actions, and analyst decisions together for review.

Explore Our Managed SOC

Built for MSPs and MSSPs

Deliver cloud security assurance across clients from one partner workspace. Each tenant retains separate accounts, data, permissions, response rules, and reporting.

Compare Client Posture

See open findings, configuration results, and reporting gaps across your assigned clients.

Apply Client Procedures

Use the escalation contacts, approval requirements, and response authority agreed for each environment.

Deliver Branded Reports

Provide client-specific dashboards and reports, with optional white-labeling under your brand and domain.

Work With Our SOC

Bring ThreatDefence analysts into client investigations under an agreed responsibility split.

MSP console
Clients7
Cloud accounts37
Critical fails37
Open cases10
ClientAccountsFailsPostureCases
acme-corp106
862
northwind711
743
harbor-health52
89–
bluegum-legal3–
93–
summit-retail614
684
kestrel-mining43
811
lumen-dental21
90–
Portal brand
ThreatDefenceNorthgate SOCHarbor Cyber
portal.yourbrand.com

Get Connected

Start with the accounts and services that matter most, then extend coverage as your environment grows.

1
Authorize integrationsConnect each source with scoped permissions approved by your administrator.
2
Confirm visibilityCheck that required audit logs, configuration data, and security findings are available.
3
Establish contextAdd expected automation, privileged accounts, critical resources, and escalation procedures.
4
Review initial findingsAssess configuration weaknesses and tune detections around legitimate activity.
5
Monitor and respondInvestigate ongoing findings and execute actions within your approved authority.

Expert Cloud Advisory

Work with cloud security specialists who can see the same findings as your team. Turn recurring issues into practical improvements to access, logging, architecture, and administration.

Maturity reviews

Establish current strengths and priorities.

Policy guidance

Review identity, key management, storage, and logging practices.

Architecture advice

Assess account structure, security boundaries, and monitoring coverage.

Remediation support

Assign owners, plan changes, and verify fixes.

See It in Action

    I'm an MSP, MSSP, or reseller

    By submitting this form, you accept the terms in our privacy policy.

    Frequently Asked Questions

    What is cloud security assurance?

    Cloud security assurance combines monitoring, configuration checks, and evidence to help an organization understand whether its cloud services are operating securely. ThreatDefence connects these findings with investigation, response, and reporting.

    Which clouds and services are supported?

    Supported integrations include AWS, Azure, Microsoft 365, Entra ID, Google Workspace, Okta, Cloudflare, and Google Cloud. Available audit, configuration, and response capabilities vary by source.

    Do we need to install agents?

    Cloud audit and configuration monitoring uses authorized integrations rather than endpoint agents. An endpoint agent can add process activity and forensic evidence from supported cloud virtual machines.

    What is the difference between CSPM and cloud threat detection?

    Cloud security posture management identifies configuration weaknesses. Cloud threat detection examines activity for signs of misuse or attack. ThreatDefence brings both into the investigation so analysts can connect an exposure with activity affecting it.

    Does connecting CloudTrail capture all AWS activity?

    No. Coverage depends on the event types, accounts, regions, and resources configured for logging. Object-level activity, such as S3 object access, requires the relevant data-event logging.

    Can ThreatDefence detect unusual downloads?

    Yes, where the connected service provides the required data-access or application audit records. Collection scope and logging settings determine which activity is visible.

    Can you take response actions?

    Yes, through supported integrations with separately authorized response permissions. Actions can require approval or run within explicitly approved limits.

    Do configuration reports prove compliance?

    They provide evidence for relevant technical controls. Compliance also depends on scope, policies, people, processes, and the requirements of the assessment.

    How do you reduce unnecessary alerts?

    Detections use account history, expected automation, business context, and related activity. Analyst feedback helps refine investigation methods and escalation rules.

    Can MSPs offer this under their own brand?

    Yes. The multi-tenant platform supports separate client environments and optional white-label portals, reports, and notifications.