LoFP LoFP / t1486

t1486

TitleTags
backup software
cross-account kms key usage may be legitimate in multi-account aws organizations architectures where centralized encryption keys are used for data governance or auditing workflows. confirm whether the external kms key belongs to an expected account before taking action. data migration or cross-account backup workflows may legitimately re-encrypt s3 objects using a key in another account. ensure these workflows are documented, tied to known iam roles, and occur on predictable schedules.
dev, uat, sat environment. you should apply this rule with prod account only.
development or testing environments that simulate external key management scenarios. even in these cases, such activity is typically infrequent and should not add significant noise.
if cloud app security identifies, for example, a high rate of file uploads or file deletion activities it may represent an adverse encryption process.
legitimate powershell scripts which makes use of encryption.
legitimate use cases for imported key material are rare, but may include, organizations with hybrid cloud architectures that import external key material for compliance requirements.
legitimate use of server-side encryption with customer-provided keys (sse-c) to encrypt objects in an s3 bucket.
other legitimate windows processes not currently listed
processes related to software installation
system administrator activities
this rule uses matches regex patterns for common ransom note file names. ensure that the uploaded file is not part of a legitimate operation before taking action.
unknown
unlikely