Security Hotspots for Features and Merge Branches Are Greyed Out/Non-functional

security-hotspot

(David Wolff) #1

The recent Security Hotspots feature is one that I would like to use as part of our Pull Request process; however, the only branch where the Security Hotspots can be viewed is our project’s master branch (a.k.a. post merge of a PR).

Ideally I would like to have PR reviewers able to see all Security Hotspots that are a part of the changed portions of the feature branch and make assessments on all of them prior to approval and merge to master.

When viewing any branch results other than master the Security Hotspots filter is greyed out.
HotspotsGreyedOut

Is there a setting that I’m missing to enable Security Hotspots for review on feature and merge branches?


(Alexandre Gigleux) #4

Hello David,

There is no hidden feature to activate the “Security Hotspot” facet on PR. “Security Hotspots” are only available on Branches/Master, this is per design.

“Security Hotspots” are targeting Security Auditors, a position that may not exist inside a team/company and that is generally provided by specialized companies. We believe it would slow down the merge velocity if you need to request a review of the Security Hotspots before being authorized to merge. Also, you may not have enough files in the PR to decide if there is a security risk while reviewing a Security Hotspot.
In a nutshell, we could activate this feature, but we did not because we believe most of the developers will consider this as noise or won’t know what to do with these type of issues highlighting security-sensitive pieces of code.

FYI: Security Hotspots are also not visible on IDEs thru SonarLint.

Regards
Alex


(David Wolff) #6

Hi Alex,
Thanks for the response. It would be tremendously helpful if there were an option that would enable the Security Hotspots feature for feature branches. While a reviewer may not have the full view in the PR window, our reviewers always have access to the full source code and can dig to make sure that all is in order at the time of the pull request. To the greatest extent possible, we want to catch security issues prior to being merged into any of our long running branches.

Being able to see the flagged security hotspots prior to merge would be a tremendous help to streamlining our pull request checklist as it would be built into a tool that we are already using.

I hope you and your team will consider at least making this an option, if not the default.
Thanks,
Dave Wolff

(Also, I have seen security hotspots in the IntelliJ SonarLint tool and I actually like seeing them there until they are marked as a non-issue)


(Fabrice Bellingard) #7

Thanks @David_Wolff for you valuable feedback.


(Fabrice Bellingard) #8

@Alexandre_Gigleux Let’s keep this in mind for future evolutions.