cPVAL SentinelOne Key
Summary
This custom field at the organization level stores the Sentinel Site Key. The Site Key is used for organizing and managing endpoints based on their physical or logical network location within the organization.
Note:
- For Solution - SentinelOne Management Server Url Validation, there's no need to create this custom field if the partner is already using another custom field to store the SentinelOne installation token or key.
- Mandatory for Automation - SentinelOne Deployment
Details
| Label | Field Name | Definition Scope | Type | Required | Default Value | Technician Permission | Automation Permission | API Permission | Description | Tool Tip | Footer Text | Custom Field Tab Name |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| cPVAL SentinelOne Key | cpvalSentineloneKey | Organization | Text | True | Editable | Read/Write | Read/Write | Stores the Sentinel Site Key. The Site Key is used for organizing and managing endpoints based on their physical or logical network location within the organization. | Stores the Sentinel Site Key. The Site Key is used for organizing and managing endpoints based on their physical or logical network location within the organization. | SentinelOne Installation token. | SentinelOne |
Dependencies
Custom Field Creation
FAQ
-
Should this custom field be created if client is not using our script SentinelOne Deployment?
-> No. If they are not using our script for deployment and has a custom field already created with different name, then this custom field is not required to be created. -
Should I create this custom field if client wants both, our Solution - SentinelOne Management Server Url Validation and Automation - SentinelOne Deployment?
-> Yes. -
What if client is using different custom field to store the SentinelOne Key and wants to use our deployment script?
-> Create this custom field and migrate their key from the old to new if possible. Both the contents are using this custom field by default.