Professional Documents
Culture Documents
SentinelOne User Guide v1.0
SentinelOne User Guide v1.0
Version 1.0
• The Access Control System will send an approval request to your Manager.
• Only local market Security Contacts and members of the IT teams will be allowed access
After your access has been granted you will be able to login to the
SentinelOne management console via OneLogin.
1. Search for a device in the management console (See section 2.1 Search for a device)
2. Click the endpoint to open its details.
3. In the Details window, click Actions > Agent Actions > Show Passphrase
The site token can be found at the top of the Packages tab.
• The site token is needed during the S1 agent installation process. It will not proceed without it.
• Persons who have access to multiple sites in the SentinelOne management console may need to
ensure a market site is selected, before the site token is visible at the top of the page.
1. Run the SentinelOne installation package you downloaded from the console. Administrator
access is required.
2. When prompted enter the Site Token copied from the management portal and click
Continue.
IMPORTANT: When the installation process is completed you should restart the system to ensure all
SentinelOne components are active.
2. Associate the Agent with the Site Token using the following command:
sudo /opt/sentinelone/bin/sentinelctl management token set <site_token>
NB: The passphrase “0” is used if the agent has never established a connection to the
management point otherwise use the agent specific passphrase which can be found on the
console.
4. The agent should now be able to route traffic via the proxy
5. Follow the steps in Section 5 Confirm SentinelOne Agent is connected to the Management
Console to confirm that the agent is now successfully connected to the management console
after completing the proxy configuration.
1. Open a terminal window and run the run the sudo command bellow
sudo /opt/sentinelone/bin/sentinelctl management proxy set http://172.19.138.198:80
2. The agent should now be able to route traffic via the proxy
For further information regarding proxy configuration or assistance with troubleshooting connectivity
issue please reach out to Group Security.
1. Open a terminal window and run the run the sudo command bellow
sudo /opt/sentinelone/bin/sentinelctl management status
2. Confirm that Connectivity is “On” and if configured the proxy details are correct
Restating devices
To easily restart a device from the SentinelOne management console:
1. Search for the device using the steps outlined in Section 2.1
2. Select Actions
3. Select Endpoint Actions
4. Click Reboot
5. Check the box to confirm the action and click Reboot
6. The device will now be reboot