You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pyproject.toml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
[project]
2
2
name = "detection_rules"
3
-
version = "1.5.23"
3
+
version = "1.5.24"
4
4
description = "Detection Rules is the home for rules used by Elastic Security. This repository is used for the development, maintenance, testing, validation, and release of rules for Elastic Security’s Detection Engine."
Copy file name to clipboardExpand all lines: rules/integrations/aws/credential_access_new_terms_secretsmanager_getsecretvalue.toml
+27-26Lines changed: 27 additions & 26 deletions
Original file line number
Diff line number
Diff line change
@@ -2,17 +2,17 @@
2
2
creation_date = "2020/07/06"
3
3
integration = ["aws"]
4
4
maturity = "production"
5
-
updated_date = "2025/12/12"
5
+
updated_date = "2025/12/16"
6
6
7
7
[rule]
8
8
author = ["Nick Jones", "Elastic"]
9
9
description = """
10
10
An adversary with access to a compromised AWS service such as an EC2 instance, Lambda function, or other service may
11
11
attempt to leverage the compromised service to access secrets in AWS Secrets Manager. This rule looks for the first time
12
-
a specific user identity has programmatically retrieved a secret value from Secrets Manager using the `GetSecretValue`
13
-
or `BatchGetSecretValue` actions. This rule assumes that AWS services such as Lambda functions and EC2 instances are
14
-
setup with IAM role's assigned that have the necessary permissions to access the secrets in Secrets Manager. An
15
-
adversary with access to a compromised AWS service would rely on its' attached role to access the secrets in Secrets Manager.
12
+
a specific user identity has programmatically retrieved a secret value from Secrets Manager using the GetSecretValue
13
+
action. This rule assumes that AWS services such as Lambda functions and EC2 instances are setup with IAM role's
14
+
assigned that have the necessary permissions to access the secrets in Secrets Manager. An adversary with access to a
15
+
compromised AWS service would rely on its' attached role to access the secrets in Secrets Manager.
16
16
"""
17
17
false_positives = [
18
18
"""
@@ -22,7 +22,6 @@ false_positives = [
22
22
]
23
23
from = "now-6m"
24
24
index = ["filebeat-*", "logs-aws.cloudtrail-*"]
25
-
interval = "5m"
26
25
language = "kuery"
27
26
license = "Elastic License v2"
28
27
name = "First Time Seen AWS Secret Value Accessed in Secrets Manager"
@@ -32,7 +31,7 @@ note = """## Triage and analysis
32
31
33
32
AWS Secrets Manager is a service that enables the replacement of hardcoded credentials in code, including passwords, with an API call to Secrets Manager to retrieve the secret programmatically.
34
33
35
-
This rule looks for the retrieval of credentials from Secrets Manager using `GetSecretValue` or `BatchGetSecretValue` API calls. This is a [New Terms](https://www.elastic.co/guide/en/security/current/rules-ui-create.html#create-new-terms-rule) rule indicating this is the first time a specific user identity has successfuly retrieved a secret value from Secrets Manager.
34
+
This rule looks for the retrieval of credentials from Secrets Manager using `GetSecretValue` API calls. This is a [New Terms](https://www.elastic.co/guide/en/security/current/rules-ui-create.html#create-new-terms-rule) rule indicating this is the first time a specific user identity has successfuly retrieved a secret value from Secrets Manager.
0 commit comments