FortiSOAR Knowledge Base
FortiSOAR: Security Orchestration and Response software provides innovative case management, automation, and orchestration. It pulls together all of an organization's tools, helps unify operations, and reduce alert fatigue, context switching, and the mean time to respond to incidents.
Article Id 271868
Description This article provides a comprehensive guide for troubleshooting infrastructure issues before installing the Securonix connector within the FortiSOAR platform.

Infrastructure Layer Checks: To verify the connectivity status between the Securonix and FortiSOAR systems.


  1. To check if a network connection can be established to the server "" on port 443, commonly used for HTTPS traffic.



$ telnet 443


Expected Output:


Connected to
Escape character is '^]'.


  1. To check the SSL/TLS connection to the server '' on port 443 and display the server's SSL certificate details, including certificate chain and expiration dates.




$ openssl s_client -connect -showcerts | grep "CONNECTED"


Expected Output:




  1. The provided 'curl' command sends a GET request to the specified URL (``) with additional headers for authentication ('username' and 'password') and a validity duration of 365 days. It is likely used to generate an authentication token for accessing a service, possibly within the Securonix system.




$ curl --request GET --url '' --header 'password: FSR_LOGIN_PASSWORD' --header 'username: FSR_LOGIN_USERNAME' --header 'validity: 365'


Expected Output:




This response token confirms that the request is accepted for a particular user role within a specific tenant, ensuring proper authentication.


In summary,  three distinct perspectives have been determined: port-level checks, SSL verification, and API server responses, all of which collectively validate the flawless connectivity between Securonix and FortiSOAR from an infrastructure standpoint. 


Next step, proceed with the Connector Installation from the FortiSOAR's Content Hub Page.