Skip to content

Commit 4c4b45d

Browse files
authored
Update ignore-findings.md
1 parent ce2313f commit 4c4b45d

File tree

1 file changed

+5
-24
lines changed

1 file changed

+5
-24
lines changed
Lines changed: 5 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,8 @@
11
# Ignore Findings
22

3-
#### Ignore a Specific Finding
3+
**The JFrog Security documentation has a new home!**\
4+
You can now find it [here](https://jfrog.com/help/p/security-home), including sections on:
45

5-
The SAST scanner allows you to ignore a vulnerability finding simply by placing an `jfrog-ignore` annotation directly in the code. Place the `jfrog-ignore` annotation as a comment above the `sink` line of the vulnerability (the final line in the data flow).
6-
7-
The following example shows how to ignore an unsafe-deserialization issue:
8-
9-
<pre class="language-javascript" data-line-numbers><code class="lang-javascript"><a data-footnote-ref href="#user-content-fn-1">export: (req, res)</a> => {
10-
res = set_cors(req, res)
11-
res.set('Cache-Control', 'no-store, no-cache, must-revalidate, private');
12-
payload = Buffer.from(req.body.data, "base64");
13-
<a data-footnote-ref href="#user-content-fn-2">// jfrog-ignore</a>
14-
var data = <a data-footnote-ref href="#user-content-fn-3">serialize.unserialize(payload.toString())</a>;
15-
</code></pre>
16-
17-
> **Bottom line:** Place the `jfrog-ignore` annotation above the finding's final line
18-
19-
#### Unignore Findings
20-
21-
To un-ignore a scan finding, simply remove the `jfrog-ignore` annotation from the finding's execution line and re-scan the project.
22-
23-
[^1]: The vulnerability starts here
24-
25-
[^2]: Adding ignore annotation to ignore the finding
26-
27-
[^3]: The vulnerability sink
6+
* [CLI](https://jfrog.com/help/r/jfrog-security-user-guide/developers/cli)
7+
* [Frogbot](https://jfrog.com/help/r/jfrog-security-user-guide/developers/frogbot)
8+
* [IDEs](https://jfrog.com/help/r/jfrog-security-user-guide/developers/ides)

0 commit comments

Comments
 (0)