|
Infrastructure Layer Checks: To verify the connectivity status between the Securonix and FortiSOAR systems.
- To check if a network connection can be established to the server "customer.securonix.net" on port 443, commonly used for HTTPS traffic.
Command:
$ telnet customer.securonix.net 443
Expected Output:
Trying 142.250.217.78...
Connected to customer.securonix.net.
Escape character is '^]'.
- To check the SSL/TLS connection to the server 'customer.securonix.net' on port 443 and display the server's SSL certificate details, including certificate chain and expiration dates.
Command:
$ openssl s_client -connect customer.securonix.net:443 -showcerts | grep "CONNECTED"
Expected Output:
CONNECTED(00000003)
- The provided 'curl' command sends a GET request to the specified URL (`https://customer.securonix.net/Snypr/ws/token/generate`) 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.
Command:
$ curl --request GET --url 'https://customer.securonix.net/Snypr/ws/token/generate' --header 'password: FSR_LOGIN_PASSWORD' --header 'username: FSR_LOGIN_USERNAME' --header 'validity: 365'
Expected Output:
530bf219-5360-41d3-81d1-8b4d6f75956d
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.
|
