# Digital Signatures

Digital signatures are cryptographic proofs that bind data to a signing private key, allowing verification of its integrity and origin using the corresponding public key.

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

> A digital signature allows a recipient to detect changes to signed data and verify that the signature was produced by the holder of a particular private key. In cloud environments, signatures help validate software releases, stored files, and audit records, provided that verifiers trust the signing key and enforce verification.

Practice exams covering Digital Signatures: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-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 Digital Signatures

Digital signatures combine asymmetric cryptography, trusted key distribution, protected signing authority, and enforced verification to detect tampering and authenticate data origin.

1. **Asymmetric signing and verification**: The private key creates signatures, while the public key verifies them. This allows many consumers to verify artifacts without receiving a secret that would let them forge signatures.
2. **Integrity and authenticated origin**: Verification detects changes to the signed data and associates it with a signing key. Establish the key's trusted identity separately through approved keys, certificates, or another authenticated distribution mechanism.
3. **Protected signing authority**: Protect private keys with managed key services or hardware security modules, and tightly restrict signing permissions. Keeping a key nonexportable does not prevent misuse by a principal authorized to request signatures.
4. **Enforced verification**: Signatures provide protection only when consumers verify them and reject artifacts that violate policy. Verify the exact bytes being deployed and check approved signers, algorithms, and relevant artifact context.
5. **Complementary retention controls**: Signatures detect tampering but do not prevent deletion or replacement. Combine them with versioning, access controls, and immutable retention when stored artifacts or evidence must remain available.
6. **Key lifecycle and evidentiary limits**: Plan rotation, revocation or trust removal, and preservation of public verification material. Signatures can support nonrepudiation, but their evidentiary value depends on key custody, identity assurance, and applicable policy; they do not automatically prove signing time or content safety.

## Cloud services for Digital Signatures

A release pipeline can use AWS Signer for supported code-signing workflows or AWS KMS for application-defined signatures, then store artifacts and verification material in Amazon S3. Consumers verify the exact artifact version against an approved signer before use; Lambda can enforce code-signing policies for supported ZIP deployment packages. S3 Versioning and Object Lock add recovery and retention protection without replacing signature checks. Separately, CloudTrail signed digest files support validation of audit logs used to investigate signing activity. Together, these controls address artifact authenticity, evidence integrity, and preservation.

- **[AWS Signer](https://blowstack.com/tools/cloud-services-hub/aws-signer)**: AWS Signer provides managed code signing for supported platforms and artifact types. Signing profiles define signing settings, while downstream consumers must verify signatures and enforce their trust policies.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: CloudTrail log file integrity validation produces digitally signed digest files containing log file hashes and links to preceding digests. Validate these files and the referenced logs to detect modification or missing evidence; enabling the feature does not itself perform ongoing validation.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: Lambda code signing configurations can require supported ZIP deployment packages to carry valid signatures from approved AWS Signer signing profiles. Use enforcement rather than warning-only behavior when deployment must be blocked on signature policy failures.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: S3 can store signed artifacts, detached signatures, and audit evidence, while version IDs allow consumers to identify exact stored versions. S3 Object Lock and Versioning complement signature verification; S3 checksums and server-side encryption are not substitutes for publisher signatures.

## Digital Signatures exam questions

Real practice exam questions on Digital Signatures, with the correct answer and its explanation.

### Question 1 (SAP-C03)

**Question:**

A company deploys ZIP-based AWS Lambda functions through a release pipeline and an emergency deployment workflow. Both workflows use roles that can update function code but cannot change function security configurations. The release pipeline already blocks packages that fail dependency vulnerability checks. However, an audit finds that an emergency operator could substitute a different ZIP package after those checks.

The security team requires Lambda to reject deployment packages unless they were signed with the specific production signing profile version approved by the team. Other teams have valid signing profiles in the same account, but their packages must not be trusted for these functions. Emergency operators must retain permission to deploy approved packages but must not be able to sign new packages. The solution must minimize custom verification logic.

Which solution meets these requirements?

**Correct answer:** Allow only the release pipeline role to sign packages with the approved AWS Signer profile after the vulnerability gate passes. Deploy the signed output, and attach a Lambda code signing configuration that lists only the approved signing profile version ARN and sets the untrusted artifact policy to Enforce.

**Explanation:** AWS Signer supplies artifact authenticity and integrity, while the existing vulnerability gate assesses dependencies. Lambda's code signing configuration restricts trusted publishers to the approved profile version, and Enforce rejects unsigned, modified, or otherwise untrusted packages regardless of which deployment workflow submits them. Keeping signing permissions separate from deployment permissions prevents emergency operators from approving substitute packages.

### Question 2 (SCS-C03)

**Question:**

A company delivers AWS CloudTrail logs to an Amazon S3 bucket. During an incident review, a security engineer discovers that a deployment disabled log file integrity validation for 48 hours and then re-enabled it. The trail continued delivering logs throughout this period. All log files and all digest files that CloudTrail produced are still available.

Auditors require an assessment of whether the delivered logs have changed, based on cryptographic evidence generated by CloudTrail. The engineer must accurately identify any limits in that evidence.

Which approach should the engineer use?

**Correct answer:** Validate the available digest chains for the periods before and after the interruption. Report that CloudTrail-generated integrity evidence cannot establish the integrity of logs delivered while validation was disabled.

**Explanation:** CloudTrail does not produce digest files while log file integrity validation is disabled, and re-enabling it does not generate digests retroactively. Disabling validation breaks the digest chain. The engineer can validate the available evidence on either side of the interruption but must disclose the gap rather than claim continuous integrity verification.

### Question 3 (DOP-C02)

**Question:**

A company stores payment-service container images in Amazon ECR. A central deployment gate verifies a signature over each image digest before deploying that digest to production. Each signature includes a signing certificate. The gate currently accepts any certificate that chains to the company's internal certificate authority (CA).

Several application teams obtain signing certificates from the same CA. During a security test, an image signed with another team's legitimate certificate passes the payment-service deployment gate. Only the payment release authority should be able to authorize payment-service images. Repository administrators and other application teams must not gain this authority merely by publishing images or signature metadata. The payment release authority's private key and the deployment gate's configuration are managed separately from ECR publishing permissions.

Which change should a DevOps engineer make to the deployment gate?

**Correct answer:** Maintain an approved payment-release public-key allowlist in the gate's independently managed configuration. Require a valid signature from an allowlisted key over the image digest being deployed, and reject images if verification fails or no approved signature exists.

**Explanation:** An independently managed allowlist binds release authorization to the payment release authority's key rather than to any company-issued certificate. Verifying the signature over the deployed digest establishes integrity and the approved signer's identity. Failing closed prevents unsigned or unauthorized images from bypassing the control.

### Question 4 (ANS-C01)

**Question:**

A company hosts example.com in an Amazon Route 53 public hosted zone with DNSSEC signing enabled. The correct DS record is published in the parent zone. During a security exercise, an attacker injects a replacement A record set, an RRSIG generated with the attacker's private key, and a DNSKEY containing the corresponding public key. The injected signature verifies mathematically against the injected public key. The company's validating recursive resolver has a trusted root anchor and can authenticate the parent zone's records. Which resolver behavior correctly prevents clients from using the injected address?

**Correct answer:** Authenticate the zone's signing keys through the parent DS record and validate the A record set through those authenticated keys; return a validation failure if that trust chain cannot be established.

**Explanation:** The authenticated parent DS record binds the delegation to an authorized child-zone key. The resolver uses that relationship to authenticate the zone's DNSKEY record set and then validate signed answers. An attacker-controlled key cannot replace this chain merely by producing a mathematically valid signature. Bogus data normally results in SERVFAIL rather than an accepted address.

## Practice Digital Signatures in a full exam

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

- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 4 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 2 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 2 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 1 question

## What is Digital Signatures

A digital signature protects the integrity and authenticity of data through asymmetric cryptography. A signer uses a private key to generate a signature over a message, generally through an algorithm that incorporates a cryptographic hash. A verifier uses the corresponding public key, the message, and the signature to check validity. Changing the signed bytes causes verification to fail. The private key must remain protected, while the public key can be distributed to verifiers.

Successful verification establishes a relationship between the data and a particular key, not automatically a trusted person or organization. The verifier must obtain the public key through a trusted channel, validate an appropriate certificate chain, or use an explicitly approved key identifier. Accepting a public key supplied alongside an untrusted file without checking its provenance allows an attacker to replace the file, signature, and key together.

A practical cloud example is signing a release artifact before uploading it to object storage. A controlled build pipeline produces the artifact, requests a signature from a managed signing service or protected asymmetric key, and publishes the signature with the artifact. Before installation or deployment, a consumer verifies the signature against an approved public key. Verification must apply to the exact artifact that will be used; verifying one object version and subsequently downloading a different version creates a verification gap.

Digital signatures differ from encryption, checksums, and message authentication codes. Signing does not conceal data, and encryption alone should not be assumed to authenticate its producer. An ordinary checksum detects changes only when the expected checksum is trustworthy; an attacker who can replace both a file and its checksum can bypass that check. A message authentication code uses a shared secret, so any party able to verify with that secret can also generate valid codes. Public-key signature verification does not require possession of the signing secret.

For data at rest, signatures detect unauthorized changes but do not prevent overwrites or deletion. Amazon S3 Object Lock and S3 Glacier Vault Lock provide retention controls rather than digital signatures. S3 Versioning preserves object versions but does not authenticate their contents. These controls complement signing: retention protects evidence from removal, versioning supports recovery and precise artifact selection, and signatures support authenticity and integrity checks. Amazon S3 object checksums are useful for transfer and storage integrity, but they are not publisher signatures.

Audit validation is another application. AWS CloudTrail log file integrity validation delivers digitally signed digest files that reference log files and link successive digests. Running validation can detect changes to delivered logs and gaps in the digest chain. Enabling digest delivery alone does not continuously validate logs or stop an attacker from deleting them; retention controls and scheduled validation remain necessary.

Operational trade-offs include signing latency, service quotas, verification overhead, and key lifecycle management. Restrict signing permissions separately from verification permissions, because an attacker who can request signatures may authenticate malicious artifacts without extracting the key. Plan key rotation, trusted-key distribution, compromise response, and retention of verification material. A valid signature does not prove that software is safe, that data is current, or that an authorized signer acted correctly. Prevent replay or rollback by signing relevant context, such as artifact identity and version, and enforcing an acceptance policy.

## Learn Digital Signatures in lessons

5 short lessons on Digital Signatures in 3 certification courses.

- SAP-C03: Digital Signatures: trusted release artifacts (Premium), https://app.blowstack.com/lessons/digital-signatures-trusted-release-artifacts-sap-c03
- SCS-C03: Cryptographic Hashing vs Digital Signatures (Premium), https://app.blowstack.com/lessons/cryptographic-hashing-vs-digital-signatures-scs-c03
- DOP-C02: Digital Signatures: release artifact trust (Premium), https://app.blowstack.com/lessons/digital-signatures-release-artifact-trust-dop-c02
- SCS-C03: Digital Signatures: Trusted verification of stored artifacts (Premium), https://app.blowstack.com/lessons/digital-signatures-trusted-verification-of-stored-artifacts-scs-c03
- DOP-C02: Digital Signatures vs Encryption: authenticity and confidentiality (Premium), https://app.blowstack.com/lessons/digital-signatures-vs-encryption-authenticity-and-confidentiality-dop-c02
