diff options
| author | G. Ann Campbell <ann.campbell@sonarsource.com> | 2018-07-16 09:36:02 -0400 |
|---|---|---|
| committer | SonarTech <sonartech@sonarsource.com> | 2018-07-17 20:21:27 +0200 |
| commit | 0763c1ecb3a3eaca803f0a04b28a424c65ecbcad (patch) | |
| tree | bef7273368c39c7bd3ac6ba537bee38e552ea52f /server/sonar-docs/src/pages/security-reports.md | |
| parent | abf8a0ad34b17c6879c3ba0469b90d0a1b4631e0 (diff) | |
| download | sonarqube-0763c1ecb3a3eaca803f0a04b28a424c65ecbcad.tar.gz sonarqube-0763c1ecb3a3eaca803f0a04b28a424c65ecbcad.zip | |
Correct punctuation
Diffstat (limited to 'server/sonar-docs/src/pages/security-reports.md')
| -rw-r--r-- | server/sonar-docs/src/pages/security-reports.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/server/sonar-docs/src/pages/security-reports.md b/server/sonar-docs/src/pages/security-reports.md index ea5355adb0e..f6aa0ebb0a0 100644 --- a/server/sonar-docs/src/pages/security-reports.md +++ b/server/sonar-docs/src/pages/security-reports.md @@ -19,7 +19,7 @@ If you look at the code where a Hotspot is raised and realize that there really ## What happens after my Hotspot becomes a Vulnerability? Once you've *Detect*ed that there really is a problem at a Hotspot location, it will be assigned to the appropriate developer, who will make a fix, and must then `Request Review` *via the UI*. That request moves the issue from Vulnerability back to Hotspot. From there, it's up to the security auditor to either *Accept* or *Reject* the fix. Accepting the fix will mark it "Won't Fix", and rejecting it will turn it back into a Vulnerability, putting it back in the developer's queue. -## What does it mean for a Hotspot to be marked "Won't Fix". +## What does it mean for a Hotspot to be marked "Won't Fix"? The Won't Fix designation is used to indicate that a Hotspot has been reviewed and there is no way, as of now, to exploit this piece of code to create an attack. ## Why don't I see any Hotspots? |