Enhancing Authentication with Timestamp‑Based Device Verification

Beyond traditional user ID and password authentication, verifying the login device adds a critical layer of protection. This approach uses a timestamp‑based algorithm to ensure that only authorized devices can access the system—without requiring any user action.

How It Works

• Clock Synchronization: The authentication server and the client PC both synchronize their clocks with a trusted time source.

• Timestamp Generation: Each side uses the current timestamp down to the second, reducing one level of precision to account for network latency.

• Shared Transformation: Both the server and client apply the same transformation to the timestamp (for example, add 5, then multiply by 2).

• Value Verification: The client sends the transformed value; the server independently computes and verifies it.

• Algorithm Array: A shared array of transformation methods is stored on both ends. These methods can vary widely in complexity.

• Method Selection: After each successful login, the server randomly selects a method from the shared array for the next login and notifies the client of the new method.

• No User Intervention: The entire process is handled automatically by the authentication system—no passwords and no user interaction required.

• Initial Provisioning: Corporate IT configures the initial method during authorized device provisioning.

• Customizable Arrays: Each organization can define its own transformation‑method array based on its security policies.

Benefits of This Algorithm

• The end user does not need to remember any password or take any action.

• No additional hardware is required.

• Hackers cannot steal a password to gain access.

• The method supports password‑less authentication.

• Brute‑force attacks are ineffective.

• It can be used in IoT environments for device‑to‑device verification.

Additional Considerations for National Security

A device may be equipped with two separate clocks. The clock used for this verification method does not need to follow UTC standards and may operate at a different speed. A built‑in safety feature can also be added: if the device is stolen and cannot synchronize with the trusted time source, it will enter a self‑protective shutdown mode.

​​

US Patents: 10,826,912, and 10,848,489

Japanese Patent No. 7309880

European (EP) Patent No. EP3895043​

​

Future Innovations:

​

 

​Seeking business partners to develop this solution.

For inquiries, please send a USPS registered mail to

ChienSEC LLC

12400 SE 38TH ST #40151

Bellevue, WA 98015