Skip to content

Commit 75a67ea

Browse files
kmcquadeclaude
andauthored
Remove stale triage CSV worksheet references from the report (+ refresh demo report) (#598)
* Remove stale triage CSV worksheet references from the in-report guidance The HTML report's Triaging guidance still told users to attach and fill out a "Triage CSV worksheet" that the scan no longer generates. Update the in-report guidance asset (2-triage-guidance.md) to ask reviewers to justify findings against the HTML report directly, and rebuild the committed Vue bundle so the generated report reflects it. Rebuilt with `npm run build` (not `just build-js`) to avoid regenerating example IAM fixtures; diff is limited to the asset and the dist bundle, no fixture drift. Mirrors the docs-site fix in #597. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Refresh the example report to embed the corrected triage guidance Re-render index.html from the existing committed fixture and the rebuilt Vue bundle so the demo report no longer shows the stale "Triage CSV worksheet" wording. Used generate_example_report.py (not generate-report) to avoid regenerating fixtures: compare-reports confirms 0 findings added/removed, and example-iam-data.json / sampleData.js are untouched. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 parent e8f36c9 commit 75a67ea

4 files changed

Lines changed: 12 additions & 12 deletions

File tree

cloudsplaining/output/dist/index.html

Lines changed: 2 additions & 2 deletions
Large diffs are not rendered by default.

cloudsplaining/output/dist/js/index.js

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

cloudsplaining/output/src/assets/2-triage-guidance.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -35,13 +35,13 @@ To recap: you've followed these steps to generate this report:
3535
An assessor can follow this general workflow:
3636

3737
* Open a ticket in your organization's project management tool of choice (for example, JIRA or Salesforce) in the AWS account owner's project
38-
* Attach the HTML report, JSON Data file, and CSV worksheet
39-
* Ask the service/account owner team to fill out the Triage worksheet
38+
* Attach the HTML report and the raw JSON data file
39+
* Ask the service/account owner team to review the findings and provide a justification for each
4040

41-
When you ask the service/account owner team to fill out the Triage CSV worksheet, you can use some text like the following:
41+
When you ask the service/account owner team to review the findings, you can use some text like the following:
4242

4343
> As part of our security assessment, our team ran Cloudsplaining on your AWS account. Cloudsplaining maps out the IAM risk landscape in a report, identifies where resource ARN constraints are not in use, and identifies other risks in IAM policies like Privilege Escalation, Data Exfiltration, and Resource Exposure/Permissions management. Remediating these issues, where applicable, will help to limit the blast radius in the case of compromised AWS credentials.
44-
> We request that you review the HTML report and fill out the "Justification" field in the Triage worksheet. Based on the corresponding details in the HTML report, provide either (1) A justification on why the result is a False Positive, or (2) Identify that it is a legitimate finding.
44+
> We request that you review the HTML report and, for each finding, provide either (1) A justification on why the result is a False Positive, or (2) Identification that it is a legitimate finding.
4545
4646
##### Triaging considerations
4747

index.html

Lines changed: 4 additions & 4 deletions
Large diffs are not rendered by default.

0 commit comments

Comments
 (0)