translate 2

src/pentesting-cloud/aws-security/aws-persistence/README.md

@@ -4,5 +4,3 @@
 
 
 
-
-

src/pentesting-cloud/aws-security/aws-persistence/aws-api-gateway-persistence.md

@@ -35,4 +35,3 @@ Or just remove the use of API keys.
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-cognito-persistence.md

@@ -45,4 +45,3 @@ By default this is disabled:
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-dynamodb-persistence.md

@@ -66,4 +66,3 @@ The compromised instances or Lambda functions can periodically check the C2 tabl
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-ec2-persistence.md

@@ -57,4 +57,3 @@ Create a peering connection between the victim VPC and the attacker VPC so he wi
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-ecr-persistence.md

@@ -100,4 +100,3 @@ aws ecr put-replication-configuration \
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-ecs-persistence.md

@@ -102,4 +102,3 @@ aws ecs create-service --service-name "undocumented-service" --task-definition "
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-efs-persistence.md

@@ -24,4 +24,3 @@ You could **create an access point** (with root access to `/`) accessible from a
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-elastic-beanstalk-persistence.md

@@ -80,4 +80,3 @@ aws elasticbeanstalk update-environment --environment-name my-env --option-setti
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-iam-persistence.md

@@ -52,4 +52,3 @@ If the account is already trusting a common identity provider (such as Github) t
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-kms-persistence.md

@@ -42,4 +42,3 @@ aws kms list-grants --key-id <key-id>
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-lambda-persistence/README.md

@@ -67,4 +67,3 @@ Here you have some ideas to make your **presence in AWS more stealth by creating
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-lambda-persistence/aws-abusing-lambda-extensions.md

@@ -45,4 +45,3 @@ The tool [**lambda-spy**](https://github.com/clearvector/lambda-spy) was created
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-lambda-persistence/aws-lambda-layers-persistence.md

@@ -133,4 +133,3 @@ aws lambda remove-layer-version-permission --layer-name ExternalBackdoor --state
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-lightsail-persistence.md

@@ -36,4 +36,3 @@ If domains are configured:
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-rds-persistence.md

@@ -34,4 +34,3 @@ aws rds modify-db-snapshot-attribute --db-snapshot-identifier <snapshot-name> --
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-s3-persistence.md

@@ -28,4 +28,3 @@ Although usually ACLs of buckets are disabled, an attacker with enough privilege
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-secrets-manager-persistence.md

@@ -56,4 +56,3 @@ def generate_password():
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-sns-persistence.md

@@ -84,4 +84,3 @@ aws sns subscribe --region <region> \
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-sqs-persistence.md

@@ -42,4 +42,3 @@ The following policy gives everyone in AWS access to everything in the queue cal
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-ssm-perssitence.md

@@ -4,5 +4,3 @@
 
 
 
-
-

src/pentesting-cloud/aws-security/aws-persistence/aws-step-functions-persistence.md

@@ -24,4 +24,3 @@ If the AWS account is using aliases to call step functions it would be possible
 
 
 
-

src/pentesting-cloud/aws-security/aws-persistence/aws-sts-persistence.md

@@ -134,4 +134,3 @@ Write-Host "Role juggling check complete."
 
 
 
-