User enumerated AWS Systems Manager parameters - Anomaly
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel,
n'hésitez pas à nous contacter.
Goal
Detect when a user is attempting to retrieve a high number of parameters, through Cloudtrail’s GetParameter event.
Strategy
This rule sets a baseline for user activity in the GetParameter event, and enables detection of potentially anomalous activity when a user attempts to retrieve an anomalous volume of parameters.
An attacker may attempt to enumerate and access the AWS Systems Manager to gain access to Application Programming Interface (API) keys, database credentials, Identity and Access Management (IAM) permissions, Secure Shell (SSH) keys, certificates, and more. Once these credentials are obtained, they can be used to perform lateral movement and access restricted information.
Triage and response
- Investigate API activity for
{{@userIdentity.session_name}} to determine if the specific set of API calls are malicious.- Use the investigation queries on the suggested actions panel.
- Review any other security signals for
{{@userIdentity.session_name}}. - If the activity is deemed malicious:
- Rotate user credentials.
- Determine what other API calls were made by the user.
- Rotate any parameters that were accessed by the user with the
aws-cli command put-parameter. - Begin your organization’s incident response process and investigate.
- If the activity is benign:
- Use the linked blog post in the suggested actions panel to tune out noise.
