10 ms·

Refer to the guidance suggested by Github themselves: https://developer.github.com/v3/guides/best-practices-for-integrators/#secure-payloads-delivered-from-gith

Refer to the guidance suggested by Github themselves: https://developer.github.com/v3/guides/best-practices-for-integrators/#secure-payloads-delivered-from-github https://developer.github.com/v3/guides/best-practices-for-in... That is, 1) put an SSL certificate on your endpoint and 2) only permit connections to 443/TCP from Github's IP address ranges.

avtar 8y ago
Suggested practice #3 is equally as important: > Provide a secret token to ensure payloads are definitely coming from GitHub. By enforcing a secret token, you're ensuring that any data received by your server is absolutely coming from GitHub
- deleted 8y ago
  [deleted]