search

cloudfoundry / cf-deployment-concourse-tasks

Apache License 2.0
23 stars 76 forks source link

director created by the tasks is open to the world #33

Closed tinygrasshopper closed 6 years ago

tinygrasshopper commented 6 years ago

we are running bbl-up task to create our ENVs, we discovered that the director is accessible from everywhere. We would like to restrict this to a whitelisted set of IPs, is that a parameter that can be added to this task?

cf-gitbot commented 6 years ago

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/151713722

The labels on this github issue will be updated when the story is started.

dsabeti commented 6 years ago

Hey @tinygrasshopper. We don't currently have any support for that. However, I'm pretty sure that you'll get something close to what you want once we upgrade to bbl 5.0. With that update, all bosh directors created by bbl will be deployed to a private IP, with jumpbox that operators can use to access their director.

Would that satisfy your security needs, or do you have a specific reason to want a set of whitelisted IPs?

dsabeti commented 6 years ago

Hi @tinygrasshopper, any thoughts on whether the jumpbox provided by bbl 5.0 would satisfy your security needs?

dsabeti commented 6 years ago

Closed due to inactivity, but feel free to reopen.