trasnlate other half

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

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

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

@@ -34,3 +34,5 @@ Or just remove the use of API keys.
 
 
 
+
+

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

@@ -44,3 +44,5 @@ By default this is disabled:
 
 
 
+
+

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

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

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

@@ -56,3 +56,5 @@ 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

@@ -99,3 +99,5 @@ aws ecr put-replication-configuration \
 
 
 
+
+

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

@@ -101,3 +101,5 @@ aws ecs create-service --service-name "undocumented-service" --task-definition "
 
 
 
+
+

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

@@ -23,3 +23,5 @@ 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

@@ -79,3 +79,5 @@ aws elasticbeanstalk update-environment --environment-name my-env --option-setti
 
 
 
+
+

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

@@ -51,3 +51,5 @@ 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

@@ -41,3 +41,5 @@ aws kms list-grants --key-id <key-id>
 
 
 
+
+

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

@@ -66,3 +66,5 @@ 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

@@ -44,3 +44,5 @@ 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

@@ -132,3 +132,5 @@ aws lambda remove-layer-version-permission --layer-name ExternalBackdoor --state
 
 
 
+
+

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

@@ -35,3 +35,5 @@ If domains are configured:
 
 
 
+
+

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

@@ -33,3 +33,5 @@ aws rds modify-db-snapshot-attribute --db-snapshot-identifier <snapshot-name> --
 
 
 
+
+

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

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

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

@@ -55,3 +55,5 @@ def generate_password():
 
 
 
+
+

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

@@ -83,3 +83,5 @@ aws sns subscribe --region <region> \
 
 
 
+
+

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

@@ -41,3 +41,5 @@ 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,3 +4,5 @@
 
 
 
+
+

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

@@ -23,3 +23,5 @@ 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

@@ -133,3 +133,5 @@ Write-Host "Role juggling check complete."
 
 
 
+
+