I see that no logs are collected (in the report), what do I need to do?

It might be because of following reason:

It is possible that your SBC is newly commissioned and has no logs to collect.
Incase of using an external syslog server for log aggregation, it is possible that the credentials to your syslog server is insufficient or the path incorrect.

If you have verified that none of the above apply to you, please report the issue to sbcsupport@assertion.cloud

Related Articles
I see failures in the summary report. What do I need to do now to remediate the failures?
You need to get the detailed report (available at a small fee), follow the instructions to remediate, and remediate the issues. Not all suggestions can be immediately acted upon. Remediate what you can immediately to contain the attack. Perform the ...
The summary report did not indicate any issues. Do I need to buy the detailed report?
No. If the summary report does not indicate any issues, you do not need to purchase the detailed report.
Do I need to buy the detailed report in a stipulated time frame?
Yes, you need to purchase the detailed report within 30 days of the date of scan.
How do I see my summary report?
You can login to the portal, click on the dashboard (four square icon on the left navigation bar), and locate your scan in the list of scans. Click the "View Summary Report" button to view the summary report of your scan.
I cannot see the “view” option for my scan on the dashboard.
This could happen if the scan is still under progress, or if the scan has aborted. If it is under 180 minutes of starting the scan, please wait and allow it to complete. You will receive an email notification once it completes, and it will be ...

Related Articles