Files
blue-team-tools/rules/cloud/aws/aws_sts_getsessiontoken_misuse.yml
T

29 lines
1.1 KiB
YAML
Raw Normal View History

2021-07-24 12:05:44 -05:00
title: AWS STS GetSessionToken Misuse
id: b45ab1d2-712f-4f01-a751-df3826969807
2022-10-09 16:54:04 +02:00
status: test
2021-07-24 12:05:44 -05:00
description: Identifies the suspicious use of GetSessionToken. Tokens could be created and used by attackers to move laterally and escalate privileges.
references:
- https://github.com/elastic/detection-rules/pull/1213
- https://docs.aws.amazon.com/STS/latest/APIReference/API_GetSessionToken.html
2022-10-09 16:54:04 +02:00
author: Austin Songer @austinsonger
date: 2021/07/24
modified: 2022/10/09
tags:
- attack.lateral_movement
- attack.privilege_escalation
- attack.t1548
- attack.t1550
- attack.t1550.001
2021-07-24 12:05:44 -05:00
logsource:
2021-11-14 09:56:59 +01:00
product: aws
2021-07-24 12:05:44 -05:00
service: cloudtrail
detection:
2021-07-24 16:18:06 -05:00
selection:
eventSource: sts.amazonaws.com
eventName: GetSessionToken
userIdentity.type: IAMUser
condition: selection
2021-07-24 12:05:44 -05:00
falsepositives:
2022-10-09 16:54:04 +02:00
- GetSessionToken may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. GetSessionToken from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
level: low