Documentation fixes

Author: kmcquade

README.md

@@ -19,7 +19,7 @@ Use a one-liner command to backdoor an AWS account's resources with a rogue AWS
 
 ```bash
 # this will ruin your day
-endgame smash --service all --evil-principal "*" --dry-run
+endgame smash --service all --evil-principal "*"
 # This will show you how your day could have been ruined
 endgame smash --service all --evil-principal "*" --dry-run
 # Atone for your sins
@@ -224,7 +224,7 @@ We recommend that AWS take the following measures in response:
 * Increase Access Advisor Support to cover the resources that can be exposed via Resource-based Policy modification, AWS RAM resource sharing, and resource-specific sharing APIs (such as RDS snapshots, EBS snapshots, and EC2 AMIs)
 * Create GuardDuty rules that detect anomalous exposure of resources outside your AWS Organization.
 * Expand the current limit of 5 SCPs per AWS account to 200. (for comparison, the Azure equivalent - Azure Policies - has a limit of [200 Policy or Initiative Assignments per subscription](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-policy-limits))
-* Improve the AWS SCP service to support "Audit" mode, which will increase customer adoption and make it easier for customers to both pilot and roll out new guardrails.
+* Improve the AWS SCP service to support an "Audit" mode that would record in CloudTrail whether API calls would have been denied had the SCP not been in audit mode. This would increase customer adoption and make it easier for customers to both pilot and roll out new guardrails. (for comparison, the Azure Equivalent - Azure Policies - already [supports Audit mode](https://docs.microsoft.com/en-us/azure/governance/policy/concepts/effects#audit).
 * Support the usage of `sts:AssumeRole` to prevent calls from outside your AWS Organization, with targeted exceptions.
 
 ## Recommendations to Blue Teams

resources.md docs/appendices/permissions-management-actions.md

@@ -36,6 +36,7 @@ make integration-test
 ```
 
 This does the following:
+
 * Sets up your local dev environment (see `setup-dev`) in the `Makefile`
 * Creates the Terraform infrastructure (see `terraform-demo` in the `Makefile`)
 * Runs `list-resources`, `exploit --dry-run`, and `expose` against this live infrastructure

docs/roadmap.md docs/appendices/roadmap.md

@@ -2,8 +2,7 @@
 
 The IAM Permissions listed below are used to create these backdoors.
 
-> **NOTE**: You don't need **all** of these permissions to run the tool. You just need enough from each service. So, `s3:ListAllMyBuckets`, `s3:GetBucketPolicy`, and `s3:PutBucketPolicy` are all the permissions needed to leverage this tool to expose S3 buckets.
-
+You don't need **all** of these permissions to run the tool. You just need enough from each service. For example, `s3:ListAllMyBuckets`, `s3:GetBucketPolicy`, and `s3:PutBucketPolicy` are all the permissions needed to leverage this tool to expose S3 buckets.
 
 ```json
 {

docs/ua-detection.md docs/appendices/user-agent-detection.md

@@ -1,4 +1,4 @@
 endgame
 =======
 
-Introduction goes here.
+Introduction from the main README should go here after we iron it out.

docs/contributing/testing.md

@@ -1,4 +1,4 @@
-# SNS
+# SNS Topics
 
 * [Steps to Reproduce](#steps-to-reproduce)
 * [Exploitation](#exploitation)

docs/iam-permissions.md

@@ -1,4 +1,4 @@
-# SQS
+# SQS Queues
 
 * [Steps to Reproduce](#steps-to-reproduce)
 * [Exploitation](#exploitation)

docs/index.md

@@ -40,9 +40,9 @@ nav:
     - RDS Snapshots: 'risks/rds-snapshots.md'
     - S3 Buckets: 'risks/s3.md'
     - Secrets Manager: 'risks/secretsmanager.md'
-    - SES: 'risks/ses.md'
-    - SNS: 'risks/sns.md'
-    - SQS: 'risks/sqs.md'
+    - SES Authorized Senders: 'risks/ses.md'
+    - SNS Topics: 'risks/sns.md'
+    - SQS Queues: 'risks/sqs.md'
 
   - "<b>Contributing</b>":
     - Contributing: 'contributing/contributing.md'
@@ -51,3 +51,6 @@ nav:
   - "<b>Appendices</b>":
     - Terraform Demo Infrastructure: 'appendices/terraform-demo-infrastructure.md'
     - ACM PCA Activation: 'appendices/acm-pca-activation.md'
+    - User-Agent Detection: 'appendices/user-agent-detection.md'
+    - Roadmap: 'appendices/roadmap.md'
+    - FAQ: 'appendices/faq.md'