Skip to content

Commit e51aa9a

Browse files
committed
Fixed header
1 parent 6547c38 commit e51aa9a

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

content/aws/avoiding-detection/modify-guardduty-config.md

-2
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,6 @@
22
author: Ben Leembruggen
33
title: Modify GuardDuty Configuration
44
description: Modify existing GuardDuty configurations in the target account to hinder alerting and remediation capabilities.
5-
enableEditBtn: true
6-
editBaseURL: https://github.com/Hacking-the-Cloud/hackingthe.cloud/blob/main/content
75
---
86

97
When an account has been successfully compromised, an attacker can modify threat detection services like GuardDuty to reduce the likelihood of their actions triggering an alert. Modifying, as opposed to outright deleting, key attributes of GuardDuty may be less likely to raise alerts, and result in a similar degradation of effectiveness. The actions available to an attacker will largely depend on the compromised permissions available to the attacker, the GuardDuty architecture and the presence of higher level controls like Service Control Policies.

0 commit comments

Comments
 (0)