| 1 | --- |
| 2 | title: Cloud security assessment (Scout Suite) |
| 3 | description: Run Scout Suite scans inside CoPilot to generate cloud posture reports (AWS supported; Azure/GCP may be limited depending on release). |
| 4 | --- |
| 5 | |
| 6 | CoPilot can run **Scout Suite** scans and surface the resulting report inside the UI. |
| 7 | |
| 8 | Scout Suite is an open-source cloud security assessment tool that scans a cloud account via provider APIs, identifies risky configurations, and generates a report with remediation guidance. |
| 9 | |
| 10 | --- |
| 11 | |
| 12 | ## Why this is a power feature |
| 13 | |
| 14 | Cloud posture assessment is not required for the initial SIEM bring-up, but it becomes valuable once your core pipeline is healthy. |
| 15 | |
| 16 | Use it for: |
| 17 | - periodic cloud posture reviews (monthly/quarterly) |
| 18 | - identifying misconfigurations and risky exposures |
| 19 | - producing a shareable “here’s what to fix next” report for stakeholders |
| 20 | |
| 21 | --- |
| 22 | |
| 23 | ## How it works in CoPilot (high level) |
| 24 | |
| 25 | 1) You create cloud credentials with read-only assessment permissions (provider-specific) |
| 26 | 2) In CoPilot, you create a new cloud assessment report |
| 27 | 3) CoPilot runs Scout Suite in the background |
| 28 | 4) When complete, the report is listed and can be opened/viewed in CoPilot |
| 29 | |
| 30 | --- |
| 31 | |
| 32 | ## Supported providers |
| 33 | |
| 34 | - **AWS** |
| 35 | - **Azure** |
| 36 | - **Google Cloud (GCP)** |
| 37 | |
| 38 | CoPilot can run Scout Suite scans for these providers as long as the appropriate credentials and API permissions are in place. |
| 39 | |
| 40 | --- |
| 41 | |
| 42 | ## Setup checklist (AWS / Azure / GCP) |
| 43 | |
| 44 | ### 1) Create a dedicated Scout Suite cloud principal |
| 45 | |
| 46 | Create a dedicated identity for assessments: |
| 47 | - **AWS:** IAM user/role |
| 48 | - **Azure:** App registration / service principal |
| 49 | - **GCP:** service account |
| 50 | |
| 51 | Guidance: |
| 52 | - Use **least privilege**. |
| 53 | - Prefer read-only where possible. |
| 54 | |
| 55 | Provider-specific credential setup (recommended): |
| 56 | - AWS: https://github.com/nccgroup/ScoutSuite/wiki/Amazon-Web-Services |
| 57 | - Azure: https://github.com/nccgroup/ScoutSuite/wiki/Azure |
| 58 | - GCP: https://github.com/nccgroup/ScoutSuite/wiki/Google-Cloud-Platform |
| 59 | |
| 60 | ### 2) Generate credentials |
| 61 | |
| 62 | Create the credentials required for the provider you’re scanning. |
| 63 | |
| 64 | Common patterns from the Scout Suite wiki: |
| 65 | - **AWS:** standard AWS credential sources (profiles in `~/.aws/credentials`, environment variables, role assumption, or explicit access keys) |
| 66 | - **Azure:** Azure CLI login, user-account browser login (MFA-friendly), or service principal (including file-based SDK auth) |
| 67 | - **GCP:** application-default user credentials or a service account key JSON |
| 68 | |
| 69 | ### 3) Run the scan in CoPilot |
| 70 | |
| 71 | In CoPilot: |
| 72 | 1) Open **Cloud security assessment** |
| 73 | 2) Select provider type (AWS / Azure / GCP) |
| 74 | 3) Set a report name |
| 75 | 4) Enter credentials |
| 76 | 5) Submit |
| 77 | |
| 78 | The scan runs in the background. Runtime depends on the size of the cloud environment. |
| 79 | |
| 80 | Operational tip (from the video): |
| 81 | - You can tail CoPilot container logs to see when report generation completes. |
| 82 | - Use Refresh in the UI; when done, the report appears in the list. |
| 83 | |
| 84 | --- |
| 85 | |
| 86 | ## Success criteria |
| 87 | |
| 88 | - [ ] You can create a report and the scan completes |
| 89 | - [ ] The report shows in the UI after refresh |
| 90 | - [ ] The report content is accessible to authorized users |
| 91 | |
| 92 | --- |
| 93 | |
| 94 | ## Safety / guardrails |
| 95 | |
| 96 | - Cloud posture reports can contain sensitive inventory details (accounts, resources, IAM relationships). |
| 97 | - Restrict access (RBAC) appropriately. |
| 98 | - Use dedicated credentials and rotate them. |
| 99 | - Avoid storing long-lived keys if your environment supports roles/short-lived credentials. |
| 100 | |
| 101 | --- |
| 102 | |
| 103 | ## Troubleshooting |
| 104 | |
| 105 | - Report never appears: |
| 106 | - confirm credentials are valid |
| 107 | - confirm required API permissions exist |
| 108 | - check CoPilot container logs for Scout Suite errors |
| 109 | |
| 110 | - Report takes a long time: |
| 111 | - large environments can take longer to enumerate |
| 112 | - rerun during a quieter window |
| 113 | |
| 114 | --- |
| 115 | |
| 116 | ## Video context |
| 117 | |
| 118 | Walkthrough + setup: |
| 119 | - https://www.youtube.com/watch?v=G3MDJSMvnRo |