admin/splunk-security_content
1
0
Fork 0
mirror of https://github.com/splunk/security_content synced 2026-06-08 17:32:49 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
96ca892fe80ca6b33ecbbe56bb6c4c7e5b129e9a
splunk-security_content/detections/cloud
T
History
Patrick Bareiss 96ca892fe8 version bump
2025-02-26 11:42:57 +01:00
..
abnormally_high_number_of_cloud_infrastructure_api_calls.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
abnormally_high_number_of_cloud_instances_destroyed.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
abnormally_high_number_of_cloud_instances_launched.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
abnormally_high_number_of_cloud_security_group_api_calls.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
amazon_eks_kubernetes_cluster_scan_detection.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
amazon_eks_kubernetes_pod_scan_detection.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
asl_aws_concurrent_sessions_from_different_ips.yml
Merge branch 'rba_migration' into strict_yml_from_rba
2025-01-15 14:16:35 -06:00
asl_aws_create_access_key.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_create_policy_version_to_allow_all_resources.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_credential_access_getpassworddata.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_credential_access_rds_password_reset.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_defense_evasion_delete_cloudtrail.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_defense_evasion_delete_cloudwatch_log_group.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_defense_evasion_impair_security_services.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_defense_evasion_putbucketlifecycle.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_defense_evasion_stop_logging_cloudtrail.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_defense_evasion_update_cloudtrail.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_detect_users_creating_keys_with_encrypt_policy_without_mfa.yml
Removal of fields from new detections
2025-01-15 15:17:50 -06:00
asl_aws_disable_bucket_versioning.yml
Removal of fields from new detections
2025-01-15 15:17:50 -06:00
asl_aws_ec2_snapshot_shared_externally.yml
Removal of fields from new detections
2025-01-15 15:17:50 -06:00
asl_aws_ecr_container_upload_outside_business_hours.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_ecr_container_upload_unknown_user.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_iam_accessdenied_discovery_events.yml
Removal of fields from new detections
2025-01-15 15:17:50 -06:00
asl_aws_iam_assume_role_policy_brute_force.yml
Removal of fields from new detections
2025-01-15 15:17:50 -06:00
asl_aws_iam_delete_policy.yml
Merge branch 'rba_migration' into strict_yml_from_rba
2025-01-15 14:16:35 -06:00
asl_aws_iam_failure_group_deletion.yml
Merge branch 'rba_migration' into strict_yml_from_rba
2025-01-15 14:16:35 -06:00
asl_aws_iam_successful_group_deletion.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_multi_factor_authentication_disabled.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_network_access_control_list_created_with_all_open_ports.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_network_access_control_list_deleted.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_new_mfa_method_registered_for_user.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
asl_aws_saml_update_identity_provider.yml
Removal of fields from new detections
2025-01-15 15:17:50 -06:00
asl_aws_updateloginprofile.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_ami_attribute_modification_for_exfiltration.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_concurrent_sessions_from_different_ips.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_console_login_failed_during_mfa_challenge.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_create_policy_version_to_allow_all_resources.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_createaccesskey.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_createloginprofile.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_credential_access_failed_login.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_credential_access_getpassworddata.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_credential_access_rds_password_reset.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_cross_account_activity_from_previously_unseen_account.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_defense_evasion_delete_cloudtrail.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_defense_evasion_delete_cloudwatch_log_group.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_defense_evasion_impair_security_services.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_defense_evasion_putbucketlifecycle.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_defense_evasion_stop_logging_cloudtrail.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_defense_evasion_update_cloudtrail.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_detect_attach_to_role_policy.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_detect_permanent_key_creation.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_detect_role_creation.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_detect_sts_assume_role_abuse.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_detect_sts_get_session_token_abuse.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_detect_users_creating_keys_with_encrypt_policy_without_mfa.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_detect_users_with_kms_keys_performing_encryption_s3.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_disable_bucket_versioning.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_ec2_snapshot_shared_externally.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_ecr_container_scanning_findings_high.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_ecr_container_scanning_findings_low_informational_unknown.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_ecr_container_scanning_findings_medium.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_ecr_container_upload_outside_business_hours.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_ecr_container_upload_unknown_user.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_excessive_security_scanning.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_exfiltration_via_anomalous_getobject_api_activity.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_exfiltration_via_batch_service.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_exfiltration_via_bucket_replication.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_exfiltration_via_datasync_task.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_exfiltration_via_ec2_snapshot.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_high_number_of_failed_authentications_for_user.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_high_number_of_failed_authentications_from_ip.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_iam_accessdenied_discovery_events.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_iam_assume_role_policy_brute_force.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_iam_delete_policy.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_iam_failure_group_deletion.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_iam_successful_group_deletion.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_lambda_updatefunctioncode.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_multi_factor_authentication_disabled.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_multiple_failed_mfa_requests_for_user.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_multiple_users_failing_to_authenticate_from_ip.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_network_access_control_list_created_with_all_open_ports.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_network_access_control_list_deleted.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_new_mfa_method_registered_for_user.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_password_policy_changes.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_s3_exfiltration_behavior_identified.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_saml_access_by_provider_user_and_principal.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_saml_update_identity_provider.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_setdefaultpolicyversion.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_successful_console_authentication_from_multiple_ips.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
aws_successful_single_factor_authentication.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_unusual_number_of_failed_authentications_from_ip.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
aws_updateloginprofile.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_active_directory_high_risk_sign_in.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_admin_consent_bypassed_by_service_principal.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_application_administrator_role_assigned.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_authentication_failed_during_mfa_challenge.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_azurehound_useragent_detected.yml
updating azure
2025-02-21 13:26:46 -08:00
azure_ad_block_user_consent_for_risky_apps_disabled.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_concurrent_sessions_from_different_ips.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_device_code_authentication.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_external_guest_user_invited.yml
updating versions
2025-02-05 10:49:03 -08:00
azure_ad_fullaccessasapp_permission_assigned.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_global_administrator_role_assigned.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_high_number_of_failed_authentications_for_user.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_high_number_of_failed_authentications_from_ip.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_multi_factor_authentication_disabled.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_multi_source_failed_authentications_spike.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_multiple_appids_and_useragents_authentication_spike.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_multiple_denied_mfa_requests_for_user.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_multiple_failed_mfa_requests_for_user.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_multiple_service_principals_created_by_sp.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_multiple_service_principals_created_by_user.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_multiple_users_failing_to_authenticate_from_ip.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_new_custom_domain_added.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_new_federated_domain_added.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_new_mfa_method_registered_for_user.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_new_mfa_method_registered.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_oauth_application_consent_granted_by_user.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_pim_role_assigned.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_pim_role_assignment_activated.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_privileged_authentication_administrator_role_assigned.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_privileged_graph_api_permission_assigned.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_privileged_role_assigned_to_service_principal.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_privileged_role_assigned.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_service_principal_authentication.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_service_principal_created.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_service_principal_enumeration.yml
updating versions
2025-02-05 10:49:03 -08:00
azure_ad_service_principal_new_client_credentials.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_service_principal_owner_added.yml
updating versions
2025-02-05 10:49:03 -08:00
azure_ad_service_principal_privilege_escalation.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_successful_authentication_from_different_ips.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_successful_powershell_authentication.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_successful_single_factor_authentication.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_tenant_wide_admin_consent_granted.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_unusual_number_of_failed_authentications_from_ip.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_ad_user_consent_blocked_for_risky_application.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_user_consent_denied_for_oauth_application.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
azure_ad_user_enabled_and_password_reset.yml
updating versions
2025-02-05 10:49:03 -08:00
azure_ad_user_immutableid_attribute_updated.yml
updating versions
2025-02-05 10:49:03 -08:00
azure_automation_account_created.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_automation_runbook_created.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
azure_runbook_webhook_created.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
circle_ci_disable_security_job.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
circle_ci_disable_security_step.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
cloud_api_calls_from_previously_unseen_user_roles.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
cloud_compute_instance_created_by_previously_unseen_user.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
cloud_compute_instance_created_in_previously_unused_region.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
cloud_compute_instance_created_with_previously_unseen_image.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
cloud_compute_instance_created_with_previously_unseen_instance_type.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
cloud_instance_modified_by_previously_unseen_user.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
cloud_provisioning_activity_from_previously_unseen_city.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
cloud_provisioning_activity_from_previously_unseen_country.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
cloud_provisioning_activity_from_previously_unseen_ip_address.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
cloud_provisioning_activity_from_previously_unseen_region.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
cloud_security_groups_modifications_by_user.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
detect_aws_console_login_by_new_user.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
detect_aws_console_login_by_user_from_new_city.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
detect_aws_console_login_by_user_from_new_country.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
detect_aws_console_login_by_user_from_new_region.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
detect_gcp_storage_access_from_a_new_ip.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
detect_new_open_gcp_storage_buckets.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
detect_new_open_s3_buckets_over_aws_cli.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
detect_new_open_s3_buckets.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
detect_s3_access_from_a_new_ip.yml
progress on input/output lookup
2025-01-03 16:35:39 -08:00
detect_spike_in_aws_security_hub_alerts_for_ec2_instance.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
detect_spike_in_aws_security_hub_alerts_for_user.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
detect_spike_in_blocked_outbound_traffic_from_your_aws.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
detect_spike_in_s3_bucket_deletion.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
gcp_authentication_failed_during_mfa_challenge.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
gcp_detect_gcploit_framework.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
gcp_kubernetes_cluster_pod_scan_detection.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
gcp_multi_factor_authentication_disabled.yml
gws
2025-02-21 13:29:48 -08:00
gcp_multiple_failed_mfa_requests_for_user.yml
updating version
2025-02-24 13:02:09 -08:00
gcp_multiple_users_failing_to_authenticate_from_ip.yml
updating version
2025-02-24 13:02:09 -08:00
gcp_successful_single_factor_authentication.yml
updating version
2025-02-24 13:02:09 -08:00
gcp_unusual_number_of_failed_authentications_from_ip.yml
updating version
2025-02-24 13:02:09 -08:00
gdrive_suspicious_file_sharing.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
github_actions_disable_security_workflow.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
github_commit_changes_in_master.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
github_commit_in_develop.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
github_dependabot_alert.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
github_pull_request_from_unknown_user.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
gsuite_drive_share_in_external_email.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
gsuite_email_suspicious_attachment.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
gsuite_email_suspicious_subject_with_attachment.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
gsuite_email_with_known_abuse_web_service_link.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
gsuite_outbound_email_with_attachment_to_external_domain.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
gsuite_suspicious_calendar_invite.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
gsuite_suspicious_shared_file_name.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
high_number_of_login_failures_from_a_single_source.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00
kubernetes_abuse_of_secret_by_unusual_location.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_abuse_of_secret_by_unusual_user_agent.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_abuse_of_secret_by_unusual_user_group.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_abuse_of_secret_by_unusual_user_name.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_access_scanning.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_anomalous_inbound_network_activity_from_process.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_anomalous_inbound_outbound_network_io.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_anomalous_inbound_to_outbound_network_io_ratio.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_anomalous_outbound_network_activity_from_process.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_anomalous_traffic_on_network_edge.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_aws_detect_suspicious_kubectl_calls.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_create_or_update_privileged_pod.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_cron_job_creation.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_daemonset_deployed.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_falco_shell_spawned.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_newly_seen_tcp_edge.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_newly_seen_udp_edge.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_nginx_ingress_lfi.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_nginx_ingress_rfi.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_node_port_creation.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_pod_created_in_default_namespace.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_pod_with_host_network_attachment.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_previously_unseen_container_image_name.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_previously_unseen_process.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_process_running_from_new_path.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_process_with_anomalous_resource_utilisation.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_process_with_resource_ratio_anomalies.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_scanner_image_pulling.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_scanning_by_unauthenticated_ip_address.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_shell_running_on_worker_node_with_cpu_activity.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_shell_running_on_worker_node.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_suspicious_image_pulling.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
kubernetes_unauthorized_access.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
microsoft_intune_device_health_scripts.yml
Removal of fields from new detections
2025-01-15 15:17:50 -06:00
microsoft_intune_devicemanagementconfigurationpolicies.yml
Removal of fields from new detections
2025-01-15 15:17:50 -06:00
microsoft_intune_manual_device_management.yml
Removal of fields from new detections
2025-01-15 15:17:50 -06:00
microsoft_intune_mobile_apps.yml
Removal of fields from new detections
2025-01-15 15:17:50 -06:00
o365_add_app_role_assignment_grant_user.yml
version bump
2025-02-26 11:42:57 +01:00
o365_added_service_principal.yml
version bump
2025-02-18 13:27:02 +01:00
o365_admin_consent_bypassed_by_service_principal.yml
version bump
2025-02-18 13:27:02 +01:00
o365_advanced_audit_disabled.yml
version bump
2025-02-26 11:42:57 +01:00
o365_application_available_to_other_tenants.yml
version bump
2025-02-26 11:42:57 +01:00
o365_application_registration_owner_added.yml
version bump
2025-02-18 13:30:23 +01:00
o365_applicationimpersonation_role_assigned.yml
version bump
2025-02-18 13:27:02 +01:00
o365_block_user_consent_for_risky_apps_disabled.yml
version bump
2025-02-18 13:27:02 +01:00
o365_bypass_mfa_via_trusted_ip.yml
version bump
2025-02-26 11:42:57 +01:00
o365_compliance_content_search_exported.yml
version bump
2025-02-26 11:42:57 +01:00
o365_compliance_content_search_started.yml
version bump
2025-02-26 11:42:57 +01:00
o365_concurrent_sessions_from_different_ips.yml
version bump
2025-02-18 13:30:23 +01:00
o365_cross_tenant_access_change.yml
version bump
2025-02-18 13:30:23 +01:00
o365_disable_mfa.yml
version bump
2025-02-18 13:30:23 +01:00
o365_dlp_rule_triggered.yml
Merge branch 'develop' into output_normalization_o365
2025-02-26 11:35:55 +01:00
o365_elevated_mailbox_permission_assigned.yml
version bump
2025-02-26 11:42:57 +01:00
o365_email_access_by_security_administrator.yml
Merge branch 'develop' into output_normalization_o365
2025-02-26 11:35:55 +01:00
o365_email_reported_by_admin_found_malicious.yml
Merge branch 'develop' into output_normalization_o365
2025-02-26 11:35:55 +01:00
o365_email_reported_by_user_found_malicious.yml
Merge branch 'develop' into output_normalization_o365
2025-02-26 11:35:55 +01:00
o365_email_security_feature_changed.yml
Merge branch 'develop' into output_normalization_o365
2025-02-26 11:35:55 +01:00
o365_email_suspicious_behavior_alert.yml
Merge branch 'develop' into output_normalization_o365
2025-02-26 11:35:55 +01:00
o365_email_transport_rule_changed.yml
rba message
2025-02-11 08:41:18 -08:00
o365_excessive_authentication_failures_alert.yml
version bump
2025-02-18 13:27:02 +01:00
o365_excessive_sso_logon_errors.yml
version bump
2025-02-18 13:30:23 +01:00
o365_exfiltration_via_file_access.yml
Update o365_exfiltration_via_file_access.yml
2025-02-02 12:30:38 -05:00
o365_exfiltration_via_file_download.yml
Update o365_exfiltration_via_file_download.yml
2025-02-02 12:31:04 -05:00
o365_exfiltration_via_file_sync_download.yml
Update o365_exfiltration_via_file_sync_download.yml
2025-02-02 12:31:31 -05:00
o365_external_guest_user_invited.yml
version bump
2025-02-18 13:30:23 +01:00
o365_external_identity_policy_changed.yml
version bump
2025-02-18 13:27:02 +01:00
o365_file_permissioned_application_consent_granted_by_user.yml
version bump
2025-02-18 13:30:23 +01:00
o365_fullaccessasapp_permission_assigned.yml
version bump
2025-02-18 13:27:02 +01:00
o365_high_number_of_failed_authentications_for_user.yml
version bump
2025-02-26 11:42:57 +01:00
o365_high_privilege_role_granted.yml
version bump
2025-02-26 11:42:57 +01:00
o365_mail_permissioned_application_consent_granted_by_user.yml
version bump
2025-02-18 13:30:23 +01:00
o365_mailbox_email_forwarding_enabled.yml
version bump
2025-02-26 11:42:57 +01:00
o365_mailbox_folder_read_permission_assigned.yml
version bump
2025-02-18 13:27:02 +01:00
o365_mailbox_folder_read_permission_granted.yml
version bump
2025-02-26 11:42:57 +01:00
o365_mailbox_inbox_folder_shared_with_all_users.yml
version bump
2025-02-18 13:27:02 +01:00
o365_mailbox_read_access_granted_to_application.yml
version bump
2025-02-18 13:27:02 +01:00
o365_multi_source_failed_authentications_spike.yml
version bump
2025-02-26 11:42:57 +01:00
o365_multiple_appids_and_useragents_authentication_spike.yml
version bump
2025-02-18 13:30:23 +01:00
o365_multiple_failed_mfa_requests_for_user.yml
version bump
2025-02-18 13:30:23 +01:00
o365_multiple_mailboxes_accessed_via_api.yml
version bump
2025-02-18 13:30:23 +01:00
o365_multiple_os_vendors_authenticating_from_user.yml
version bump
2025-02-26 11:42:57 +01:00
o365_multiple_service_principals_created_by_sp.yml
version bump
2025-02-18 13:27:02 +01:00
o365_multiple_service_principals_created_by_user.yml
version bump
2025-02-18 13:27:02 +01:00
o365_multiple_users_failing_to_authenticate_from_ip.yml
version bump
2025-02-26 11:42:57 +01:00
o365_new_email_forwarding_rule_created.yml
version bump
2025-02-18 13:27:02 +01:00
o365_new_email_forwarding_rule_enabled.yml
version bump
2025-02-18 13:27:02 +01:00
o365_new_federated_domain_added.yml
version bump
2025-02-26 11:42:57 +01:00
o365_new_forwarding_mailflow_rule_created.yml
version bump
2025-02-18 13:30:23 +01:00
o365_new_mfa_method_registered.yml
version bump
2025-02-18 13:27:02 +01:00
o365_oauth_app_mailbox_access_via_ews.yml
version bump
2025-02-18 13:30:23 +01:00
o365_oauth_app_mailbox_access_via_graph_api.yml
version bump
2025-02-18 13:27:02 +01:00
o365_privileged_graph_api_permission_assigned.yml
version bump
2025-02-18 13:27:02 +01:00
o365_privileged_role_assigned_to_service_principal.yml
version bump
2025-02-26 11:42:57 +01:00
o365_privileged_role_assigned.yml
version bump
2025-02-26 11:42:57 +01:00
o365_pst_export_alert.yml
version bump
2025-02-18 13:30:23 +01:00
o365_safe_links_detection.yml
Merge branch 'develop' into output_normalization_o365
2025-02-26 11:35:55 +01:00
o365_security_and_compliance_alert_triggered.yml
version bump
2025-02-26 11:42:57 +01:00
o365_service_principal_new_client_credentials.yml
version bump
2025-02-26 11:42:57 +01:00
o365_service_principal_privilege_escalation.yml
Merge branch 'develop' into output_normalization_o365
2025-02-26 11:35:55 +01:00
o365_sharepoint_allowed_domains_policy_changed.yml
Merge branch 'develop' into output_normalization_o365
2025-02-26 11:35:55 +01:00
o365_sharepoint_malware_detection.yml
Merge branch 'develop' into output_normalization_o365
2025-02-26 11:35:55 +01:00
o365_sharepoint_suspicious_search_behavior.yml
Update o365_sharepoint_suspicious_search_behavior.yml
2025-02-02 12:59:26 -05:00
o365_tenant_wide_admin_consent_granted.yml
version bump
2025-02-26 11:42:57 +01:00
o365_threat_intelligence_suspicious_email_delivered.yml
Merge branch 'develop' into output_normalization_o365
2025-02-26 11:35:55 +01:00
o365_threat_intelligence_suspicious_file_detected.yml
Merge branch 'develop' into output_normalization_o365
2025-02-26 11:35:55 +01:00
o365_user_consent_blocked_for_risky_application.yml
version bump
2025-02-18 13:27:02 +01:00
o365_user_consent_denied_for_oauth_application.yml
remove update_timestamps, confidence, impact,
2025-01-03 15:25:52 -08:00
o365_zap_activity_detection.yml
Merge branch 'develop' into output_normalization_o365
2025-02-26 11:35:55 +01:00
risk_rule_for_dev_sec_ops_by_repository.yml
Clean up MITRE Tagging. When a type is defined, such as T1003, DO NOT allow a subtype such as T1003.001 to be defined. Remove the generic type T1003 and keep the subtype T1003.001. However, it is acceptable for a subtype to be defined or for a type to be defined separately. It is also okay for multiple subtypes to be defined.
2025-02-10 12:28:22 -08:00