GitHub SSH key added by suspicious IP

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Goal

Detect when a SSH key has been added from a suspicious IP.

Strategy

This rule monitors GitHub audit logs for when a SSH key has been added from a suspicious IP. A phishing campaign reported by Github’s security team indicated that attackers may try to add a SSH key once they have gained unauthorized access to an account to maintain access. Using Datadog threat intelligence the signals raised will have originated from IP addresses deemed to be suspicious.

Note: By default GitHub does not display the source IP address for events in your organization’s audit log. See this post for further information.

Triage and response

  1. Determine if the behavior is unusual for the user:
    • Is the @actor_location.country_code or @http.useragent different?
    • If IP addresses are available, is the @network.client.ip or @network.client.geoip.as.domain different than usual?
    • Speak with the user to verify if they added the SSH key.
  2. If the activity is suspicious:
    • Block the user in GitHub to prevent further access.
    • Begin your organization’s incident response process and investigate.
PREVIEWING: esther/docs-9478-fix-split-after-example