You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello,
Could you please help me with the following,
How to configure bamboo server to remove public facing settings.
Thanks,
Bobby
Hello @bobby dammu
Can you please provide some context on "public facing settings"? What exactly are you trying to do/not do?
Regards,
Eduardo Alvarenga
Atlassian Support APAC
Thank you so much for the quick response.
Description:
Due to a security concern regarding 'log4j', we are looking options to mitigate risk. One option is re-configure the Bamboo server (and agents) to no longer be publicly accessible.
Thanks,
Bobby
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @bobby dammu,
Thanks for clarifying that.
Bamboo is not vulnerable to the recent Log4j CVEs. You can find more details below:
Though, if you still want to disable any "public" access to your Bamboo Server and Agents, you'll have to work with your external configurations such as blocking traffic on our Firewall, Load Balancer, etc.
Bamboo needs to listen to specific ports to work. There is no option to disable such services.
You can also create local firewall rules on each server that is part of your Bamboo solution to allow only trusted sources to reach its service ports:
You can also enable Tomcat's Client authentication to enforce only validated clients
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.