Method 1:
Click the Tunneling button above the application list in the application dashboard.
This opens the Cosmog configuration side panel.
Click on Create new profile button.
You can use either "Standard platforms" or "Kubernetes". (Steps for Kubernetes listed after this section)
In "Standard platform", by default, the port will be selected as 80 if you've selected "http".
When you're creating a new application, under the "Application URL accessibility" section, turn on the "This URL is only accessible within my local network and is not available publicly" toggle button.
From the drop-down list, select the Cosmog profile you've created.
Method 2:
Create a new application
After providing application details, turn on “This URL is only accessible within my local network and is not available publicly” radio button.
You can select or add a new Cosmog profile here.
To create a new Cosmog profile click on the "Add new" button.
You can use either "Standard platforms" or "Kubernetes". (Steps for Kubernetes listed after this section)
In "Standard platform", by default, the port will be selected as 80 if you've selected "http".
Kubernetes Integration for Tunnelling (Cosmog)
Select Kubernetes from the two available options.
Provide the necessary information
Click Save. Your profile will now be created.
From the created profile, click the Install button.
Copy the command shown in the pop-up box and run it in your Kubernetes environment.
The Pod will be set up in the default namespace (unless you specify otherwise).
You are now ready to start the test.
Once the test begins, the Cosmog server will start automatically.
The Cosmog client will connect to the server created from step 7.
Namespace: A Kubernetes namespace is a way to logically group and isolate resources within a cluster (e.g., dev, staging, prod).
Cluster domain: This is the DNS domain name for your Kubernetes cluster, usually ending with .svc.cluster.local, which ensures services can discover and communicate with each other.
Bridge IP address: A distinct IP address that must be assigned to the Cosmog client. Please make sure that the IP address is not already assigned to any internal device or system.
Test IP range: The IP address/IP range of the application(s) that need to be security tested. It should be specified as a CIDR range.
Read more: https://www.geeksforgeeks.org/classless-inter-domain-routing-cidr/
Understanding the errors that may occur when you start a test
Certain errors may occur when you initiate a test if your Cosmog profile or client is not set up correctly. Understanding the following conditions can help you fix the issues when starting a test.
Condition 1
Cosmog Server Status: Down
Cosmog Client Status: Down
Web Application Status: Down
This condition can occur due to any of the following reasons:
User did not click the Start Test button
User did not create a Cosmog profile which allocates an IP address to the Cosmog client
User must have deleted the created Cosmog profile
Condition 2
Cosmog Server Status: Up
Cosmog Client Status: Down
Web Application Status: Down
This condition can occur due to any of the following reasons:
User did not install the Cosmog client
Cosmog client may not be running properly. In such a case, please get in touch with our support team
Condition 3
Cosmog Server Status: Up
Cosmog Client Status: Up
Web Application Status: Down
This condition can occur when Beagle Security is not able to access the user’s application.
