Merge PR #4734 from @clebron23 - Add new AWS rule related to GetSigninToken abuse

new: AWS Console GetSigninToken Potential Abuse
 
---------

Co-authored-by: nasbench <8741929+nasbench@users.noreply.github.com>

rules/cloud/aws/cloudtrail/aws_console_getsignintoken.yml

@@ -0,0 +1,28 @@
+title: AWS Console GetSigninToken Potential Abuse
+id: f8103686-e3e8-46f3-be72-65f7fcb4aa53
+status: experimental
+description: |
+    Detects potentially suspicious events involving "GetSigninToken".
+    An adversary using the "aws_consoler" tool can leverage this console API to create temporary federated credential that help obfuscate which AWS credential is compromised (the original access key) and enables the adversary to pivot from the AWS CLI to console sessions without the need for MFA using the new access key issued in this request.
+references:
+    - https://github.com/NetSPI/aws_consoler
+    - https://www.crowdstrike.com/blog/analysis-of-intrusion-campaign-targeting-telecom-and-bpo-companies/
+author: Chester Le Bron (@123Le_Bron)
+date: 2024/02/26
+tags:
+    - attack.lateral_movement
+    - attack.t1021.007
+    - attack.t1550.001
+logsource:
+    product: aws
+    service: cloudtrail
+detection:
+    selection:
+        eventSource: 'signin.amazonaws.com'
+        eventName: 'GetSigninToken'
+    filter_main_console_ua:
+        userAgent|contains: 'Jersey/${project.version}'
+    condition: selection and not 1 of filter_main_*
+falsepositives:
+    - GetSigninToken events will occur when using AWS SSO portal to login and will generate false positives if you do not filter for the expected user agent(s), see filter. Non-SSO configured roles would be abnormal and should be investigated.
+level: medium