Publishing the Solution

Security Scan Failure and Publishing Options

Even if the solution fails the security scan, you still have the option to publish it to Robility Manager. However, in such cases:

1. The solution will be flagged with the label: “Secure & Compliant Failed for Remote Logging.”

2. A notification prompt will appear, alerting the user that the solution is not certified for secure remote logging.

3. The user will be presented with two options:

a. Re-run the scan to attempt resolution of the identified vulnerabilities.
b. Skip the scan and proceed with publishing the solution, acknowledging the potential risks.

It is strongly recommended to address all flagged vulnerabilities before publishing to ensure compliance and mitigate security risks.