Skip to content

Commit

Permalink
Fixed Vinay's review comments
Browse files Browse the repository at this point in the history
  • Loading branch information
cbehera-newrelic committed Dec 9, 2024
1 parent 1cf5924 commit c2d5b15
Show file tree
Hide file tree
Showing 4 changed files with 21 additions and 21 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -32,9 +32,9 @@ I don't see my application in the New Relic UI.

Possible reasons for not finding your application in the New Relic UI are:

* A wrong version of the APM agent.
* IAST flags are disabled.
* Proxy or firewall blocking access.
* Wrong TLS certificate.
* Lack of traffic on the application.
* Any unexpected error.
* A wrong version of the APM agent
* IAST flags are disabled

Check notice on line 36 in src/content/docs/iast/troubleshooting/unable-to-see-application.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/iast/troubleshooting/unable-to-see-application.mdx#L36

[Microsoft.Passive] 'are disabled' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'are disabled' looks like passive voice.", "location": {"path": "src/content/docs/iast/troubleshooting/unable-to-see-application.mdx", "range": {"start": {"line": 36, "column": 14}}}, "severity": "INFO"}
* Proxy or firewall blocking access
* Wrong TLS certificate
* Lack of traffic on the application
* Any unexpected error
Original file line number Diff line number Diff line change
Expand Up @@ -13,19 +13,19 @@ You can see your application in the New Relic UI and the security agent successf

## Solution

If this is a new app, firewalls could be preventing it from communicating with the New Relic platform. Check the service stats section in the file with the latest timestamp in `nr-security-home/logs/snapshots`. All six items in that list should say OK. If they don't, review the logs for more info or reach out to [New Relic Support](https://support.newrelic.com). You can also see the [standard firewall documentation](/docs/new-relic-solutions/get-started/networks/).
If this is a new app, firewalls could be preventing it from communicating with the New Relic platform. In the file with the latest timestamp in `nr-security-home/logs/snapshots`, check the **service stats** section. All six items in that list should say OK. If they don't, review the logs for more info or reach out to [New Relic Support](https://support.newrelic.com). For more information, refer the [standard firewall documentation](/docs/new-relic-solutions/get-started/networks/).


If you have configured your firewall correctly, check the following:

* **The level of efficiency for your application:** Go to <DNT>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > All Tests**</DNT>. Search for your application and check the summary section. If IAST analysis coverage is low for your application, add more test cases to your application to get a higher level of testing efficiency.
* **The level of efficiency for your application:** Go to <DNT>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > All Tests**</DNT>. Search for your application and check the **Summary** section. If IAST analysis coverage is low for your application, add more test cases to your application to get a higher level of testing efficiency.

* **The IAST coverage:** Go to <DNT>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > All Tests**</DNT>. Search for your application and click to view the summary section. Under the summary section, check if IAST analysis coverage is high and no vulnerabilities are detected, that means your application is secure.
* **The IAST coverage:** Go to <DNT>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > All Tests**</DNT>. Search for your application and click to view the **Summary** section. Under the summary section, check if IAST analysis coverage is high and no vulnerabilities are detected, that means your application is secure.

Check notice on line 23 in src/content/docs/iast/troubleshooting/unable-to-see-vulnerabilities.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/iast/troubleshooting/unable-to-see-vulnerabilities.mdx#L23

[Microsoft.Passive] 'are detected' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'are detected' looks like passive voice.", "location": {"path": "src/content/docs/iast/troubleshooting/unable-to-see-vulnerabilities.mdx", "range": {"start": {"line": 23, "column": 294}}}, "severity": "INFO"}

* **Your application is secure:** In this case, check your IAST analysis coverage in <DNT>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > All Tests**</DNT>. Search for your application and check the summary section. If IAST Analysis coverage is 100% and no vulnerabilities are detected, that means your application is secure.
* **Your application is secure:** In this case, check your **IAST Analysis coverage** in <DNT>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > All Tests**</DNT>. Search for your application and check the **Summary** section. If **IAST Analysis coverage** is 100% and no vulnerabilities are detected, that means your application is secure.

Check notice on line 25 in src/content/docs/iast/troubleshooting/unable-to-see-vulnerabilities.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/iast/troubleshooting/unable-to-see-vulnerabilities.mdx#L25

[Microsoft.Passive] 'are detected' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'are detected' looks like passive voice.", "location": {"path": "src/content/docs/iast/troubleshooting/unable-to-see-vulnerabilities.mdx", "range": {"start": {"line": 25, "column": 315}}}, "severity": "INFO"}

* **Your web socket connection is broken:** Please check the latest log file in your `nr-security-home/logs/snapshots/` folder, and look for the `Service stats -> websocket` line. The expected value is OK.
* **Your web socket connection is broken:** Check the latest log file in your `nr-security-home/logs/snapshots/` folder, and look for the `Service stats -> websocket` line. The expected value is OK.

Check notice on line 27 in src/content/docs/iast/troubleshooting/unable-to-see-vulnerabilities.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/iast/troubleshooting/unable-to-see-vulnerabilities.mdx#L27

[Microsoft.Passive] 'is broken' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'is broken' looks like passive voice.", "location": {"path": "src/content/docs/iast/troubleshooting/unable-to-see-vulnerabilities.mdx", "range": {"start": {"line": 27, "column": 34}}}, "severity": "INFO"}

* Your application's framework or vulnerability category isn't supported.

After checking these, if you don't see vulnerabilities in IAST, please contact [New Relic Support](https://support.newrelic.com/s/) and share your application's configuration and logs with our support team.
After checking these, if you don't see vulnerabilities in IAST, contact [New Relic Support](https://support.newrelic.com/s/) and share your application's configuration and logs with our support team.
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: Viewing false positive vulnerabilities
title: Seeing false positive vulnerabilities
tags:
- IAST
- New Relic IAST
Expand All @@ -16,13 +16,13 @@ I see a vulnerability that isn't an actual vulnerability (false positive) for my

Update the status of your vulnerability if you think IAST has reported a false positive. Follow these steps:

- Search your application: Go to <DNT>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > All Tests**</DNT>.
* Search for your application: Go to <DNT>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > All Tests**</DNT>.

- Click on the all applications tab and select the vulnerability that isn't an actual vulnerability.
* Click the **All applications** tab and select the vulnerability that isn't an actual vulnerability.

- Under the vulnerability details section, you can update the vulnerability status for the reported vulnerability. You can update its status to:
- False positive
- Resolved
- Unresolved
* Under the **Vulnerability details** section, you can update the vulnerability status for the reported vulnerability. You can update its status to:
* False positive
* Resolved
* Unresolved

- If you want to list out the vulnerabilities for which you updated the status, you can apply the filter in the detected exploitable vulnerabilities list.
* If you want to list out the vulnerabilities for which you updated the status, you can apply the filter in the detected exploitable vulnerabilities list.
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ I see unknown files and directories in my application directory and want to remo
## Solution

If your application has the functionality to create files and directories as part of serving an HTTP request, IAST will try to test the code path and hence, create such files and directories.

Check notice on line 17 in src/content/docs/iast/troubleshooting/viewing-unknown-files-and-directories.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/iast/troubleshooting/viewing-unknown-files-and-directories.mdx#L17

[Microsoft.SentenceLength] Try to keep sentences short (< 30 words).
Raw output
{"message": "[Microsoft.SentenceLength] Try to keep sentences short (\u003c 30 words).", "location": {"path": "src/content/docs/iast/troubleshooting/viewing-unknown-files-and-directories.mdx", "range": {"start": {"line": 17, "column": 1}}}, "severity": "INFO"}
The application code, under the influence of incoming HTTP requests, creates these files. The agent can't deleted them.
The application code, under the influence of incoming HTTP requests, creates these files. The agent can't delete them.

If you're sure that none of your APIs can create files and directories, share your application's configuration and logs with [New Relic Support](https://support.newrelic.com).

Expand Down

0 comments on commit c2d5b15

Please sign in to comment.