I agree with the rest of the participants in this feature.

In fact, we have decided to quit Bitbucket and go to GitHub due to this severe security hole. We have been asking for a solution to Bitbucekt support for a couple of months and after having received a negative answer finally we were forced to migrate to another application.

This is very required feature. We are using Bitbucket Cloud Premium with Atlassian Access, since this feature is not available ip whitelisting becomes useless. Users could easily clone private repos to their own workspaces. This is major security risk.

Agreed. This is a major security risk as it allows managed employees to upload code to personally created repositories, without being flagged by firewalls and DLPs. 

This is a big problem that should be prioritized. 

I'm hoping this feature request is not vote driven due to the major security concerns it currently allows.  Bitbucket cloud Admins for orgs are shut out from being able to place constraints on personal workspaces. Today it's left up to the users vs. the account owners.

Currently, users can use repositories under their personal workspace to share with external parties. Which of course brakes companies security protocols amongst other vulnerabilities. 

Please view this request as a Major Security Risk rather than a simple feature request.

I'm moving this to Access because it is a feature that would be implemented within Access at an Org level. Workspace is the top level container within Bitbucket and one Workspace cannot manage a separate Workspace.