Skip to content

Sensitive Data Exposure categories - update business impact, steps#558

Merged
RRudder merged 3 commits into
bugcrowd:masterfrom
wesinator:business_impact_disc
Jun 18, 2026
Merged

Sensitive Data Exposure categories - update business impact, steps#558
RRudder merged 3 commits into
bugcrowd:masterfrom
wesinator:business_impact_disc

Conversation

@wesinator

Copy link
Copy Markdown
Contributor

This PR updates the Sensitive Data Exposure Categories templates:

  • I wanted to update the Business Impact section to highlight these vulnerabilities could enable exploitation leading to loss of product or service availability, which would lead to direct financial loss impact.
    Reputational risk, which is the curent focus of these business impact descriptions, is secondary and less important to potential impacts to service availability.
  • Updated the steps list so it doesn't show two step 1's next to each other. I see these templates typically list the observed/actual in its own step one, this makes less sense if there is only one StR step.

@RRudder

RRudder commented Feb 24, 2026

Copy link
Copy Markdown
Contributor

Thank you @wesinator for these updates.

What are your thoughts on this edit of the business impact?:
"This vulnerability could enable attacker exploitation that will disrupt product or service availability, leading to financial loss and impact customers’ trust in the application."

@wesinator

wesinator commented Feb 25, 2026

Copy link
Copy Markdown
Contributor Author

Hi, that looks good- I will update shortly

@RRudder RRudder self-requested a review June 17, 2026 21:53
@RRudder RRudder merged commit e2c14b0 into bugcrowd:master Jun 18, 2026
4 checks passed
@wesinator wesinator deleted the business_impact_disc branch June 18, 2026 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants