Data Manipulation: Stored Data Manipulation T1565.001
Tactic: Impact
Adversaries may insert, delete, or manipulate data at rest in order to influence external outcomes or hide activity, thus threatening the integrity of the data. By manipulating stored data, adversaries may attempt to affect a business process, organizational understanding, and decision making.
Events covered
3 catalog events are tagged with this technique by at least one rule.
| Provider | Event | Title |
|---|---|---|
| Sysmon | Event ID 1 | Process creation |
| Security-Auditing | Event ID 4688 | A new process has been created. |
| Sysmon-for-Linux | Event ID 1 | Process Create |
Authoring guide
Patterns shared across the 26 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (42 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (163 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.
Exclusions (29 distinct)
Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 7 rules
- Azure Device or Configuration Modified or Deleted
- Azure DNS Zone Modified or Deleted
- Cisco Denial of Service
- Commands to Clear or Remove the Syslog - Builtin
- History File Deletion
- macOS Encryption Tool Usage
- Potential Suspicious Change To Sensitive/Critical Files
Elastic 15 rules
- AWS Bedrock Knowledge Base or RAG Data Source Tampering
- AWS CloudTrail Log Updated
- AWS EC2 Encryption Disabled
- AWS S3 Static Site JavaScript File Uploaded
- AWS S3 Unauthenticated Bucket Access by Rare Source
- Deprecated - M365 Security Compliance Potential Ransomware Activity
- GitHub Actions Unusual Bot Push to Repository
- High Number of Closed Pull Requests by User
- High Number of Protected Branch Force Pushes by User
- Hosts File Modified
- Kubernetes CoreDNS or Kube-DNS Configuration Modified
- Kubernetes Secret or ConfigMap Access via Azure Arc Proxy
- Potential AWS S3 Bucket Ransomware Note Uploaded
- Several Failed Protected Branch Force Pushes by User
- Suspicious Sysctl File Event