AN0198: Analytic 0198
Detects remote write activity across cloud VMs or object storage buckets within the same region/account that correlate with data aggregation across hosts.
Analyst context for executives and security teams
Analytic 0198 matters because it points to a cloud data-movement pattern: remote write activity among IaaS virtual machines or object storage buckets in the same region/account, correlated with data aggregation across hosts. For leaders, the practical question is whether cloud logging and SOC workflows can distinguish expected internal data consolidation from unusual aggregation that could affect data governance, incident scope, and business continuity.
Executive priority
Prioritize this as a cloud security and incident readiness validation item. The business value is not a single alert, but evidence that teams can observe cross-resource write activity inside an account/region and quickly determine whether it is approved workload behavior, backup/ETL activity, or suspicious aggregation requiring escalation. This supports audit evidence for cloud monitoring coverage, incident scoping, and data-handling control validation.
Technical view
For SOC and detection engineering teams, validate visibility for IaaS environments where cloud VMs and object storage buckets can write remotely within the same account and region. Because ATT&CK provides no formal detection logic or tactic mapping for this analytic, implementation should focus on correlating remote write events with signs of data aggregation across multiple hosts. Tuning should account for legitimate internal workflows such as backups, replication, logging pipelines, and data-processing jobs.
Likely telemetry
- Cloud control-plane and data-plane logs for object storage write activity
- IaaS virtual machine activity logs or flow records showing remote writes between cloud resources
- Object storage access logs identifying source identity, source resource, destination bucket, region, and account
- Cloud identity and access logs for principals performing writes
- Asset and workload inventory mapping VMs, buckets, accounts, and regions
Detection direction
- Confirm that logging captures write activity to object storage buckets and relevant VM-to-resource write paths inside the same cloud account and region.
- Correlate write events with multiple source hosts or aggregated data sources rather than evaluating single writes in isolation.
- Baseline expected internal aggregation patterns, including backup, ETL, replication, logging, and analytics workloads, to reduce false positives.
- Validate that identities, source resources, destination buckets, timestamps, regions, and accounts are consistently present in telemetry.
- Look for blind spots where object storage data events, VM network visibility, or cloud identity logs are disabled, sampled, delayed, or retained for too short a period.
Mitigation priorities
- Inventory approved cloud data aggregation paths across VMs and object storage within each account and region.
- Enable and retain the cloud logs needed to reconstruct remote write activity and associated identities.
- Apply least-privilege access for principals that can write to object storage or other remote destinations.
- Use account, region, bucket, and workload segmentation to limit unnecessary cross-resource write paths.
- Document expected aggregation jobs so SOC and IR teams can rapidly separate normal operations from anomalous activity.
Analyst notes and limits
The supplied ATT&CK object is a detection analytic, not a technique, and includes only a short description. Its defensive value is strongest as a cloud telemetry validation and correlation use case for IaaS environments involving VMs and object storage buckets.
Official detection logic, tactic mapping, related techniques, and relationship context were not supplied. Local cloud architecture, logging configuration, workload inventory, and business-approved data movement patterns are required before this analytic can be tuned or assessed for coverage.
Analytic 0198
Detects remote write activity across cloud VMs or object storage buckets within the same region/account that correlate with data aggregation across hosts.
How security teams should use this page
Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.
All related ATT&CK context
No relationships are available in the current normalized data for this object.
Object version and sync metadata
The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates .
Imported snapshots across ATT&CK releases (1)
| Release | Bundle imported | Object version | Modified | Status | Raw hash |
|---|---|---|---|---|---|
| 19.1 | 1.0 | Current bundle | a904c080864c… |
Mirrored ATT&CK source object
The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.
External references and citations
MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.
-
[1]
mitre-attack AN0198Open source URL
Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.