Skip to main content

AWS Account Accessed From a New Geolocation With a New AWS Event Type

This alert occurs when an AWS IAM user or role calls this AWS event type from this geolocation for the first time.

This alert indicates the presence of one of the following events, where the API request was successful:

Event TypeDescription
AwsApiCallAn API was called.
AwsApiCallMfaAn API was called with MFA.
AwsServiceEventThe service generated an event related to your trail. For example, this can occur when another account makes a call with a resource that you own.
AwsConsoleActionAn action was taken in the console that was not an API call.
AwsConsoleSignInA user in your account (root, IAM, federated, SAML, or SwitchRole) signed in to the AWS Management Console.
note

If multi-factor authentication (MFA) was used to authenticate, the term "Mfa" will be appended to the aforementioned possible values (for example, AwsApiCallMfa). These values are obtained directly from the CloudTrail event records.

Why this alert is important

If a user typically operates from two locations, such as the office and their home, using a new geolocation to access AWS may indicate potential unauthorized access by a malicious actor who has obtained the user's credentials.

Sophisticated or targeted attackers can employ VPNs or other hosting providers to acquire an IP address in proximity to their target, allowing them to bypass certain basic security checks. Therefore, it's crucial to not only consider the country but also the specific city or town associated with the location to enhance security measures.

Why this might be just fine

A user working remotely from a new location, whether due to vacation or VPN usage, may have their source IP address modified, associating it with a different geolocation.

Investigation

Use the steps below to investigate this alert:

  1. Review the Who section in the Alert Details to identify the user in question:
    • Determine if this is a user or an assumed role by reviewing the AWS User column. The portion before the slash (/) indicates the identity type. For example:
      • An IAM user: IAMUser/000000000001:username@example.com
      • An assumed role: AssumedRole/000000000001:AWSServiceRoleForAmazonSSM
    • Obtain the principal ID for each identity involved.
  2. Determine which actions were performed by the user during the alert time frame by clicking the IAM identity link in the Alert Description. You may need to expand the time frame to access additional relevant activity.

Resolution

The following are resolutions that you can implement:

  • Delete or rotate AWS access keys associated with the user.
  • Delete any console login profiles associated with the user.
  • Delete any unrecognized or unauthorized resources that were created.
  • Perform an analysis of any resources or data that was accessed.
  • Enable MFA.