---
title: "Discussion on \"Verifying Slack Request Signatures: HMAC, Timestamps, and Replay Defense\" | Hashnode"
description: "Discussion on \"Verifying Slack Request Signatures: HMAC, Timestamps, and Replay Defense\". Any POST that reaches your Slack endpoint could be forged. This walks through the HMAC-SHA256 signature Slack puts on every request, the 5-minute timestamp window that blocks replay, and the timing-safe comparison that keeps your verify pat"
url: "https://hashnode.com/posts/verifying-slack-request-signatures-hmac-timestamps-and-replay-defense/6a5384ae8228e8d3a4d330b5"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Verifying Slack Request Signatures: HMAC, Timestamps, and Replay Defense](https://sapotacorpvn.hashnode.dev/verifying-slack-request-signatures-hmac-timestamps-and-replay-defense?utm_source=hashnode&utm_medium=feed)

Any POST that reaches your Slack endpoint could be forged. This walks through the HMAC-SHA256 signature Slack puts on every request, the 5-minute timestamp window that blocks replay, and the timing-safe comparison that keeps your verify pat

Jul 12 · 9 min read · sapotacorpvn.hashnode.dev  
Read the article

-   [#slack](https://hashnode.com/tag/slack)
-   [#security](https://hashnode.com/tag/security)
-   [#hmac](https://hashnode.com/tag/hmac)
-   [#nodejs](https://hashnode.com/tag/nodejs)
-   [#python](https://hashnode.com/tag/python)

## Written by

[SapotaCorp](https://hashnode.com/@sapotacorpvn)

@sapotacorpvn · Hanoi, Vietnam

  
[View profile](https://hashnode.com/@sapotacorpvn)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
