# Evidence Integrity

Evidence Integrity is the preservation and verification of forensic artifacts so investigators can demonstrate that the evidence has not been improperly altered since collection.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/evidence-integrity

> Reliable incident response depends on logs and other artifacts remaining authentic, traceable, and protected throughout collection, storage, transfer, and analysis. Evidence integrity combines tamper detection, preservation controls, and documented handling so engineers can reconstruct events and support defensible conclusions.

Practice exams covering Evidence Integrity: [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Evidence Integrity

Evidence integrity depends on verifiable artifacts, protected originals, traceable handling, independent storage boundaries, sufficient collection coverage, and continued readability.

1. **Verifiable artifact consistency**: Compute cryptographic hashes at collection and verify them after transfer or retrieval. Protect the expected hashes with restricted storage or signed manifests so evidence and verification records cannot be silently replaced together.
2. **Protected originals and retention**: Preserve original artifacts separately from transformed analysis copies. Apply immutable retention or legal holds when required, and choose retention periods that cover investigation and organizational obligations.
3. **Provenance and chain of custody**: Record where an artifact originated, how and when it was captured, and which identities handled it. Document transfers and transformations so investigators can explain the artifact's history.
4. **Independent collection and access boundaries**: Forward logs to a repository outside the workload's administrative control. Separate collection, investigation, and retention administration permissions to reduce opportunities for evidence tampering.
5. **Collection coverage and time context**: Capture relevant system, application, identity, and network records, and alert on delivery gaps. Preserve timestamps and timezone information while accounting for clock skew and delayed delivery.
6. **Continued readability and validation**: Retain the keys, formats, metadata, and validation material required to read and verify evidence. Test retrieval and validation rather than assuming that successful storage guarantees usable forensic artifacts.

## Cloud services for Evidence Integrity

CloudWatch Logs collects configured system and application records, while CloudTrail captures supported AWS account activity. Preserve relevant records in an S3 evidence repository with suitable versioning, Object Lock retention, and access controls. Retain CloudTrail digest files and protected hash manifests alongside the artifacts, then validate evidence during retrieval and transfer. IAM separates delivery and investigation permissions from destructive administration privileges. KMS protects confidentiality, but its keys must remain accessible for the evidence retention period. Together, these services support preservation and verification only when collection coverage, custody records, and operational validation procedures are also maintained.

- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: S3 provides a central repository for forensic log files and associated manifests. Versioning and Object Lock support preservation of object versions, while bucket policies restrict access; choose governance mode, compliance mode, or legal holds according to the required retention controls.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: CloudTrail records supported AWS account activity and can deliver trail logs to S3. Enabling log file integrity validation produces signed digest files that investigators can use to detect modification or deletion of delivered log files; validation must be performed separately.

## Evidence Integrity exam questions

Real practice exam questions on Evidence Integrity, with the correct answer and its explanation.

### Question 1 (DEA-C01)

**Question:**

A company delivers AWS CloudTrail log files and digest files to an Amazon S3 bucket with log file integrity validation enabled. During a security review, engineers discover that a privileged administrator could permanently delete both the logs and their validation evidence. For all future deliveries, auditors require the original object versions to remain undeletable for at least 365 days after creation. No identity, including the bucket owner's root user, may shorten this protection or bypass it through S3 API operations. Authorized investigators must still be able to read the files. Which configuration meets these requirements?

**Correct answer:** Enable S3 Object Lock on the versioned bucket and configure default retention in compliance mode for 365 days for new objects, including both log files and digest files.

**Explanation:** Compliance-mode Object Lock prevents protected object versions from being deleted or having their retention shortened, even by the account's root user, until their retention expires. Default retention applies to new CloudTrail log and digest objects, while authorized users can continue reading them.

### Question 2 (SAP-C03)

**Question:**

A financial services company uses AWS Organizations to manage 120 accounts across three AWS Regions. Auditors require historical evidence of security group configurations, including configurations that are changed and reverted within the same day. Archived evidence must be retained for 7 years and must not be deletable during that period, even by the root user of the archive account. The security team also needs centralized visibility into whether security groups currently permit unrestricted inbound SSH access. Which solution meets these requirements with the LEAST custom development?

**Correct answer:** Use CloudFormation StackSets to enable continuous AWS Config recording and deploy the restricted-ssh managed rule in every account and Region. Configure an organization aggregator. Deliver configuration history to versioned S3 staging buckets without Object Lock, and configure S3 replication to an archive bucket with a default 7-year Object Lock retention period in compliance mode.

**Explanation:** Continuous recording preserves configuration changes, including changes that are reversed within a day. The managed rule evaluates unrestricted SSH access, and the organization aggregator centralizes compliance visibility. AWS Config cannot deliver directly to an Object Lock-enabled bucket. Supported staging buckets followed by S3 replication provide a managed delivery path into the archive. The archive bucket's default compliance-mode retention protects replicated object versions that have no source retention settings, preventing their deletion during retention even by the archive account's root user.

### Question 3 (SCS-C03)

**Question:**

During an application-compromise investigation, responders discover that a Standard-class Amazon CloudWatch Logs log group has an active log transformer. The transformer normalizes application records and removes HTTP request headers that investigators now need. An existing subscription filter forwards the transformed records to an operational analytics pipeline.

Responders must continuously archive every newly ingested event as received by CloudWatch Logs, before transformation, without interrupting or changing the operational pipeline. Historical collection is handled separately. The log group currently has only one subscription filter, and no data protection policy masks the records. An Amazon Data Firehose delivery stream and a protected Amazon S3 evidence bucket are already configured with the necessary permissions to retain the delivered payloads without modifying their contents.

Which solution meets these requirements?

**Correct answer:** Add a second subscription filter that sends records to the evidence delivery stream. Use an empty filter pattern and set applyOnTransformedLogs to false.

**Explanation:** A subscription filter with applyOnTransformedLogs set to false operates on the original log events rather than the transformer output. An empty filter pattern includes all newly ingested events. The second subscription can deliver these records to the evidence archive while the existing subscription continues serving the operational pipeline.

### Question 4 (DOP-C02)

**Question:**

A company collects application security log bundles through a trusted collector in a security account. The collector archives the original bundles in Amazon S3, where retention and access controls already meet company policy. A separate analytics account downloads the bundles through a staging system and normalizes timestamps before analysis.

Following a compromise of the staging system, investigators discover that an attacker could replace both staged files and their accompanying checksum files. The attacker cannot modify the trusted collector or use its AWS KMS signing key. Investigators must independently verify that retrieved original bundles match the bytes captured by the collector and that the associated source and collection details have not changed. Normalized records must remain available for analysis but must not replace the original evidence.

Which collection and verification workflow meets these requirements?

**Correct answer:** Have the collector calculate SHA-256 hashes of the original bundles and create a manifest containing those hashes, source identifiers, collection times, and collector identity. Sign the manifest with an asymmetric KMS signing key before handing data to staging. Verify the signature using the trusted public key and compare original-file hashes after transfers and before analysis. Keep normalized records as separate analysis copies.

**Explanation:** The trusted collector establishes the baseline before data enters the compromised boundary. Signing the manifest protects both the expected hashes and collection metadata against substitution. Signature verification with a trusted public key and hash comparisons establish consistency with that collection baseline. Separate analysis copies preserve the original byte representation. This does not claim that the application generated truthful records before collection.

## Practice Evidence Integrity in a full exam

Questions on Evidence Integrity in each practice exam, with every answer option and an explanation for each:

- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 10 questions
- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 5 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 3 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 2 questions
- [AIP-C01](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional): 1 question

## What is Evidence Integrity

Evidence integrity means preserving forensic artifacts and being able to demonstrate whether they have changed since collection. In cloud incident response, these artifacts include operating system logs, application logs, identity and API activity records, network flow records, and captured storage data. Investigators need more than a searchable copy: they need the original records, their provenance, and a reliable account of how they were collected and handled.

Collection should begin before an incident through centrally managed logging. Forward relevant system and application logs away from workloads to a protected destination, ideally in a separate security account or administrative boundary. This reduces the opportunity for an attacker who compromises a workload to erase its history. During an incident, capture additional artifacts before terminating instances or deleting ephemeral resources when operational safety permits. Record the source resource, account, region, collection time, collection method, and responsible identity.

Preserve original files and distinguish them from analysis copies. Parsing, decompressing, normalizing timestamps, or filtering records can change their byte representation even when the underlying information remains useful. Compute a cryptographic hash, such as SHA-256, for each collected file and record it in a protected manifest. Recompute hashes after transfers and before analysis. A matching hash demonstrates consistency with the recorded baseline, but it does not establish who created the file or whether the source was already compromised. Protect or digitally sign the manifest so an attacker cannot simply replace both the artifact and its expected hash.

Storage controls should prevent unauthorized modification and premature deletion. Use narrowly scoped access permissions, versioning, and write-once retention where appropriate. In Amazon S3, Object Lock protects specific object versions; compliance mode prevents deletion of a protected version during its retention period, including by the account root user. Governance mode allows authorized bypass, so it provides a different protection level. A legal hold remains in effect until an authorized principal removes it. These controls protect stored evidence, but they do not prevent attackers from disabling future collection or submitting misleading records.

For example, after suspected credential theft, responders can preserve CloudTrail records alongside host authentication logs and application request logs in a protected evidence repository. When CloudTrail log file integrity validation is enabled, its signed digest files support checking the integrity of delivered log files. Enabling this feature creates validation material; investigators must actually run validation to check the records. It does not validate arbitrary application logs or prove that every relevant event was captured.

Maintain a chain-of-custody record covering collection, access, transfers, and transformations. Preserve timestamps and timezone information, and account for clock skew and delivery delays when correlating events. Monitor missing log delivery and protect logging configuration changes. A trustworthy timeline requires collection coverage as well as unchanged files.

The main trade-offs are storage cost, retention obligations, privacy exposure, and restrictions on deletion. Excessively short retention can destroy evidence before an incident is discovered, while excessive retention increases cost and exposure of sensitive data. Encryption protects confidentiality but does not by itself establish forensic integrity. Preserve access to encryption keys throughout the retention period because immutable encrypted objects become unusable if their keys are destroyed. Finally, integrity controls support defensible investigations; they do not automatically establish legal admissibility or guarantee that a compromised source reported truthful events.

## Learn Evidence Integrity in lessons

7 short lessons on Evidence Integrity in 5 certification courses.

- DEA-C01: Evidence Integrity: preserving audit log exports (Premium), https://app.blowstack.com/lessons/evidence-integrity-preserving-audit-log-exports-dea-c01
- SAP-C03: Evidence Integrity: verifiable audit trail preservation (Premium), https://app.blowstack.com/lessons/evidence-integrity-verifiable-audit-trail-preservation-sap-c03
- AIP-C01: Evidence Integrity: verifiable forensic records (Premium), https://app.blowstack.com/lessons/evidence-integrity-verifiable-forensic-records-aip-c01
- SCS-C03: Evidence Integrity: preserving forensic log artifacts (Premium), https://app.blowstack.com/lessons/evidence-integrity-preserving-forensic-log-artifacts-scs-c03
- DOP-C02: Evidence Integrity: verifiable audit evidence (Premium), https://app.blowstack.com/lessons/evidence-integrity-verifiable-audit-evidence-dop-c02
- SCS-C03: Chain of Custody vs. Evidence Integrity (Premium), https://app.blowstack.com/lessons/chain-of-custody-vs-evidence-integrity-scs-c03
