Configuring loggers is security-sensitive in every Build

[GPadmanabhan (Gowrilatha Padmanabhan)]

Version : 9.9 LTS

We are experiencing an issue with the rule csharpsquid:S4792. This rule was configured to review code by marking specific code as ‘Safe’ However, even after updating the status to ‘Safe,’ the pipeline continues to fail with the same error in subsequent builds. Our understanding is that, once the developer sets the status to ‘Safe,’ this error should not be triggered in future builds

[ganncamp (G Ann Campbell)]

Hi,

Welcome to the community!

To be clear, is the Security Hotspot being re-raised in new branches? Or again in the same branch? And which point version of 9.9 are you on? The latest is 9.9.7.

 
Thx,
Ann

[GPadmanabhan (Gowrilatha Padmanabhan)]

Yes, Security Hotspot is being re-raised in the Same branch . we are in 9.9.0

[ganncamp (G Ann Campbell)]

Hi,

@GPadmanabhan

in new branches in the Same branch

Does this mean both?

@GPadmanabhan

we are in 9.9

Do you mean 9.9.0?

 
Thx,
Ann

[GPadmanabhan (Gowrilatha Padmanabhan)]

sorry same branch

[ganncamp (G Ann Campbell)]

Hi,

Does this help?

Issue with Inheriting Reviewed Security Hotspots from Master Branch

Hi, We double-checked and security hotspot status are actually synchronized between branches: [image] We will update the documentation. Regarding your initial problem where the synchronization did not happen, it might be caused by multiple factors. One common case where issue sync between branches is not working is when files have been renamed. Another case could be multiple levels of branch “forking”. Like master → branchA → branchB. If you can reproduce it again, feel free to re-open a …

Also, and again, what point version of 9.9 are you on? Can you check your page footer? Does it say only “9.9”? Or is there a third digit?

 
Thx,
Ann