API Keys: IP Access Control
Fred Yates
I think it is great that Digital Ocean rolled out it's beta testing to provide custom scopes for personal access tokens shown here:
However, I think it is missing one hugely beneficial feature that could dramatically increase security in the event of a compromised token.
There should also be an option to allow tokens to only be used by authorized IP addresses and/or IP ranges. This way, attackers cannot use a compromised token to destroy resources regardless of customized granularity. It's a secondary protection layer to provide much stronger security.
Default setting should of course be to allow all IP ranges, but if a token grantor wishes to have greater security, allow them the option to limit it only to authorized IP addresses (ie. the IPs of their droplets or other resources from where they anticipate making the API calls).
The token-creator should be able to customize that IP list and/or IP range(s) accordingly.
W
Whitney Jutzin
Thank you so much for taking time to raise this product improvement idea to us! Though we are still working on the true ask here, we wanted to let you know that we have made some scoped access improvements that we think you'll be interested in trying out. You can learn more about it here: https://docs.digitalocean.com/reference/api/create-personal-access-token/ We will continue to work on the larger request in this Idea and will update you as soon as we have more information to share.