# Clock Skew

Clock skew is the difference between the times reported by two clocks at the same instant.

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

> Distributed systems use timestamps to decide whether requests, credentials, and authentication assertions are valid. When participating systems disagree about the current time, legitimate authentication can fail, audit timelines can become misleading, and poorly configured validation tolerances can weaken replay protection.

Practice exams covering Clock Skew: [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty).

## 6 key aspects of Clock Skew

Clock-skew management combines reliable time synchronization, protocol-aware validation, and correlated troubleshooting without weakening authentication controls.

1. **Relative clock disagreement**: Skew measures the difference between clocks, while drift describes how that difference changes over time. Compare systems against a trusted reference instead of relying on matching displayed time zones.
2. **Time-bounded authentication**: Signed requests, SAML assertions, JWTs, Kerberos exchanges, and time-based one-time passwords depend on time validation. Correct credentials and permissions cannot compensate for a timestamp outside the accepted window.
3. **Protocol-specific tolerances**: Acceptable skew depends on the protocol, service, and validator configuration. Do not apply a single assumed tolerance to every authentication path.
4. **Synchronization as an operational dependency**: Maintain approved time sources and monitor synchronization state and clock offset. For containers, investigate the underlying host; for domain members, verify the configured domain time hierarchy.
5. **Evidence-driven troubleshooting**: Compare trusted UTC time with host time and correlate client, identity-provider, and service-side records. Distinguish timestamp failures from expired credentials, invalid signatures, and authorization denials before changing access policies.
6. **Security versus tolerance**: A small permitted timing margin can reduce false rejections, but excessive tolerance can weaken freshness checks and replay defenses. Prefer correcting clocks over relaxing validation.

## Cloud services for Clock Skew

Amazon Time Sync Service helps keep workload clocks aligned, while AWS STS, IAM Identity Center, Amazon Cognito, and AWS Directory Service participate in authentication flows that depend on time-sensitive requests, assertions, tokens, or Kerberos exchanges. Troubleshoot the clock of each relevant participant, including external identity providers, application validators, domain members, and user devices where applicable. AWS CloudTrail supplies service-side evidence for recorded requests, complementing client errors and identity-provider logs. Together, accurate time and correlated evidence help distinguish clock problems from credential expiration, federation configuration errors, and insufficient permissions; changing access policies does not correct a timestamp validation failure.

- **[Amazon Cognito](https://blowstack.com/tools/cloud-services-hub/amazon-cognito)**: Issues user-pool tokens that applications validate using time-sensitive claims such as expiration. Keep application validator clocks accurate, and check device time when troubleshooting time-based one-time password failures.
- **[AWS Directory Service](https://blowstack.com/tools/cloud-services-hub/aws-directory-service)**: Directory environments using Active Directory rely on time synchronization for Kerberos authentication. Investigate member-system clocks, domain-controller time, and the configured time hierarchy when valid domain credentials fail.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: Provides service-side event timestamps, identity context, and error details for recorded activity. Correlate these records with client and identity-provider logs, recognizing that some authentication failures are not recorded and delivery can be delayed.

## Clock Skew exam questions

Real practice exam questions on Clock Skew, with the correct answer and its explanation.

### Question 1 (SCS-C03)

**Question:**

A company runs an on-premises security collector that uses temporary IAM role credentials and a custom Signature Version 4 signer to call AWS APIs. After the collector's virtual machine is restored from a snapshot, its requests fail with an error indicating that the signature is not yet current.

A security engineer verifies that the credentials are unexpired and that the signer uses the correct service, Region, and session token. The same credentials work from a separate diagnostic host. On the affected virtual machine, an AWS SDK test initially receives the same error but succeeds after the SDK automatically adjusts its signing-time offset. The custom collector continues to fail.

Which action should the engineer take to correct the underlying cause without weakening request validation?

**Correct answer:** Restore reliable time synchronization on the virtual machine and verify its UTC time against a trusted time source before retrying the collector.

**Explanation:** The future-dated signature and the SDK's successful signing-time adjustment indicate that the virtual machine's clock is ahead of AWS service time. Synchronizing the host corrects timestamps for the custom signer. An SDK's offset compensation does not repair the operating system clock.

## Practice Clock Skew in a full exam

Questions on Clock Skew 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

## What is Clock Skew

Clock skew is a difference in clock readings between systems, such as an application server and an identity provider. Clock drift is related but distinct: it is the rate at which a clock gains or loses time, potentially creating skew. Cloud authentication depends on reasonably synchronized clocks because signed requests, temporary credentials, federation assertions, and tokens have time-based validity conditions.

For example, an application can possess the correct AWS access key and secret key yet fail to authenticate because its AWS Signature Version 4 request contains a timestamp too far from the service's current time. Errors such as RequestTimeTooSkewed, RequestExpired, or a signature-not-yet-current message can indicate a time problem, depending on the service. Accepted timestamp windows vary by protocol and service; there is no universal AWS clock-skew allowance. Some SDKs compensate for detected skew when signing subsequent requests, but that does not synchronize the operating system or fix other authentication protocols.

Federation introduces additional clocks. A SAML assertion has validity conditions such as NotBefore and NotOnOrAfter. If an external identity provider's clock is incorrect, IAM Identity Center federation or an AWS STS AssumeRoleWithSAML request can fail even when certificates, role mappings, and user assignments are correct. IAM Identity Center permission sets determine access after authentication; changing a permission set does not repair an assertion that is outside its validity period.

Applications validating Amazon Cognito JWTs must evaluate expiration and any applicable time-based claims using a reliable clock, alongside signature, issuer, and audience or client checks appropriate to the token type. An application server whose clock is ahead can reject a still-valid token as expired. Time-based one-time passwords also depend on synchronized time. In AWS Directory Service environments, Kerberos authentication between domain members and domain controllers requires clocks to remain within the configured tolerance, commonly five minutes by default in Active Directory.

Troubleshooting starts by comparing the affected host's UTC time with a trusted reference and inspecting synchronization status. On Linux, chronyc tracking and chronyc sources can reveal synchronization failures and offsets; on Windows, w32tm can help inspect the time source and status. Check for blocked synchronization traffic, incorrect time sources, suspended virtual machines, and host clock problems. Containers generally share their host's clock, so the correction usually belongs on the host. A different displayed time zone is not itself skew if the underlying UTC instant is correct.

Correlate client errors, identity-provider logs, application token-validation failures, and available AWS CloudTrail events. CloudTrail provides service-side event timestamps and useful identity and error details, but not every rejected request produces an event, and event delivery time is not event occurrence time. Use request identifiers and inspect local timestamps rather than assuming all logs share an accurate clock.

Prevent recurrence with reliable time synchronization, offset monitoring, and checks after infrastructure changes. Increasing a configurable validation tolerance can accommodate small timing differences and transport delays, but accepting older timestamps increases the opportunity to reuse captured authentication material unless other replay controls prevent it. Fix synchronization rather than disabling expiration checks, extending credential lifetimes unnecessarily, or broadening IAM permissions. Use monotonic clocks for measuring elapsed durations inside applications; wall-clock corrections can otherwise distort timeout calculations.

## Learn Clock Skew in lessons

1 short lesson on Clock Skew in 1 certification course.

- SCS-C03: Clock Skew: authentication validity windows (Premium), https://app.blowstack.com/lessons/clock-skew-authentication-validity-windows-scs-c03
