# Security hotspot issue in sonarqube

**URL:** <https://community.sonarsource.com/t/security-hotspot-issue-in-sonarqube/105515>\
**Category:** SonarQube Server / Community Build\
**Created:** [December 5, 2023, 1:09pm UTC](https://community.sonarsource.com/t/security-hotspot-issue-in-sonarqube/105515 "2023-12-05T13:09:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shrikala\_Joshi](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/shrikala_joshi/32/46961_2.png) [@Shrikala\_Joshi](https://community.sonarsource.com/u/Shrikala_Joshi)\
**Post date:** [December 5, 2023, 1:09pm UTC](https://community.sonarsource.com/t/security-hotspot-issue-in-sonarqube/105515/1 "2023-12-05T13:09:04Z")

</div>

Hi,  
We are working with glue job and the unit test cases for this job.  
SonarQube is showing security hotspot in one file named logger.py as - “make sure that this logger’s configuration is safe”.  
logging.basicConfig(level=logging.INFO, format=‘%(message)s’)  
We didn’t find anything wrong in the code. Do you have any solution for this issue?

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [December 7, 2023, 9:18am UTC](https://community.sonarsource.com/t/security-hotspot-issue-in-sonarqube/105515/2 "2023-12-07T09:18:14Z")

</div>

Hey there.

[From the docs](https://docs.sonarsource.com/sonarqube/latest/user-guide/security-hotspots/):

> - With a hotspot, a security-sensitive piece of code is highlighted, but the overall application security may not be impacted. It’s up to the developer to review the code to determine whether or not a fix is needed to secure the code.

So it sounds like you need to mark the hotspot as **Safe!** A user who has **Administrator security hotspots** permission on project can perform this action.

> - **Safe** : A developer has reviewed the security hotspot and determined that no change is necessary (for example, because other more relevant protections are already in place).

---

<div class="post-metadata">

**Author:** ![Shrikala\_Joshi](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/shrikala_joshi/32/46961_2.png) [@Shrikala\_Joshi](https://community.sonarsource.com/u/Shrikala_Joshi)\
**Post date:** [December 7, 2023, 11:56am UTC](https://community.sonarsource.com/t/security-hotspot-issue-in-sonarqube/105515/3 "2023-12-07T11:56:01Z")

</div>

Hi Colin,  
Thanks for your reply. I will convey this to my technical lead.