[New Rule] AWS Signin Single Factor Console Login via Federated Session

[terrancedejesus]

Pull Request

Issue link(s): https://github.com/elastic/ia-trade-team/issues/272

Summary - What I changed

Added a new detection rule for AWS regarding single factor console logins via a federated session or token (temporary credentials). This behavior is highly unusual to login from a federated session if permissions to access the console are applied to the existing IAM user or role.

How To Test

Script to Get Temporary Creds and Create Admin Console Login URL

The script will use the already authenticated IAM user with the local AWS cli and request a federated token (temp creds) from AWS with the AdministratorAccess policy attached. Once the output is saved, it will request a sign-in token from AWS' federated endpoint and create a login URL. Once the URL is output, it can be clicked to automatically authenticate into the console.

```shell #!/bin/bash # Get federated creds output=$(aws sts get-federation-token --name consoler --policy-arns arn=arn:aws:iam::aws:policy/AdministratorAccess) # Check if the previous command was successful if [ $? -ne 0 ]; then echo "The command 'aws sts get-federation-token --name consoler' failed." exit 1 fi # Parse the output session_id=$(echo "$output" | jq -r '.Credentials.AccessKeyId') session_key=$(echo "$output" | jq -r '.Credentials.SecretAccessKey') session_token=$(echo "$output" | jq -r '.Credentials.SessionToken') # Check if parsing was successful if [ -z "$session_id" ] || [ -z "$session_key" ] || [ -z "$session_token" ]; then echo "Failed to parse session credentials." exit 1 fi # Construct the JSON credentials string json_creds=$(echo -n "{\"sessionId\":\"$session_id\",\"sessionKey\":\"$session_key\",\"sessionToken\":\"$session_token\"}") # Define the AWS federation endpoint federation_endpoint="https://signin.aws.amazon.com/federation" # Make the HTTP request to get the sign-in token resp=$(curl -s "$federation_endpoint" \ --get \ --data-urlencode "Action=getSigninToken" \ --data-urlencode "SessionDuration=43200" \ --data-urlencode "Session=$json_creds" ) # Check if the curl command was successful if [ $? -ne 0 ]; then echo "The curl command failed." exit 1 fi # Extract the sign-in token signin_token=$(echo -n "$resp" | jq -r '.SigninToken') # Check if the sign-in token was extracted successfully if [ -z "$signin_token" ]; then echo "Failed to retrieve the sign-in token." exit 1 fi # URL encode the token for the login URL encoded_token=$(echo -n "$signin_token" | jq -sRr @uri) # Give the URL to login login_url="https://signin.aws.amazon.com/federation?Action=login&Issuer=example.com&Destination=https%3A%2F%2Fconsole.aws.amazon.com%2F&SigninToken=$encoded_token" echo "Login URL: $login_url" ```

Checklist

• [x] Added a label for the type of pr: bug, enhancement, schema, Rule: New, Rule: Deprecation, Rule: Tuning, Hunt: New, or Hunt: Tuning so guidelines can be generated
• [ ] Added the meta:rapid-merge label if planning to merge within 24 hours
• [x] Secret and sensitive material has been managed correctly
• [ ] Automated testing was updated or added to match the most common scenarios
• [ ] Documentation and comments were added for features that require explanation

Contributor checklist

• Have you signed the contributor license agreement?
• Have you followed the contributor guidelines?

[protectionsmachine]

Rule: New - Guidelines

These guidelines serve as a reminder set of considerations when proposing a new rule.

Documentation and Context

• [ ] Detailed description of the rule.
• [ ] List any new fields required in ECS/data sources.
• [ ] Link related issues or PRs.
• [ ] Include references.

Rule Metadata Checks

• [ ] creation_date matches the date of creation PR initially merged.
• [ ] min_stack_version should support the widest stack versions.
• [ ] name and description should be descriptive and not include typos.
• [ ] query should be inclusive, not overly exclusive, considering performance for diverse environments. Non ecs fields should be added to non-ecs-schema.json if not available in an integration.
• [ ] min_stack_comments and min_stack_version should be included if the rule is only compatible starting from a specific stack version.
• [ ] index pattern should be neither too specific nor too vague, ensuring it accurately matches the relevant data stream (e.g., use logs-endpoint.process-* for process data).
• [ ] integration should align with the index. If the integration is newly introduced, ensure the manifest, schemas, and new_rule.yaml template are updated.
• [ ] setup should include the necessary steps to configure the integration.
• [ ] note should include any additional information (e.g. Triage and analysis investigation guides, timeline templates).
• [ ] tags should be relevant to the threat and align/added to the EXPECTED_RULE_TAGS in the definitions.py file.
• [ ] threat, techniques, and subtechniques should map to ATT&CK always if possible.

New BBR Rules

• [ ] building_block_type should be included if the rule is a building block and the rule should be located in the rules_building_block folder.
• [ ] bypass_bbr_timing should be included if adding custom lookback timing to the rule.

Testing and Validation

• [ ] Provide evidence of testing and detecting the expected threat.
• [ ] Check for existence of coverage to prevent duplication.