You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There are a number of Zero Trust solutions (for instance, zscaler) that can ensure some degree of device security posture before allowing a connection. We were trying to create similar behaviour (deny access outright if the device does not have SentinelOne running), but seem unable to do so
Describe the solution you'd like
A way to prevent users from connecting to if a certain process (or processes) are not running on the machine of the user
Describe alternatives you've considered
We have looked into creating a plugin, but it does not look like boundary supports external plugins yet, based on #2454. Or if it does, we couldn't find documentation for it anywhere
Explain any additional use-cases
It would be a pretty good feature for general adoption to ensure that a user is "secure enough" before allowing a connection
The text was updated successfully, but these errors were encountered:
Hi @SamuZad thank you for logging this feature request. I'll leave this item open to solicit additional feedback and 👍 to gauge interest from the community.
Is your feature request related to a problem? Please describe.
There are a number of Zero Trust solutions (for instance, zscaler) that can ensure some degree of device security posture before allowing a connection. We were trying to create similar behaviour (deny access outright if the device does not have SentinelOne running), but seem unable to do so
Describe the solution you'd like
A way to prevent users from connecting to if a certain process (or processes) are not running on the machine of the user
Describe alternatives you've considered
We have looked into creating a plugin, but it does not look like boundary supports external plugins yet, based on #2454. Or if it does, we couldn't find documentation for it anywhere
Explain any additional use-cases
It would be a pretty good feature for general adoption to ensure that a user is "secure enough" before allowing a connection
The text was updated successfully, but these errors were encountered: