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
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.
The level of access and control enterprise companies need today to keep their teams and information safe in the cloud is paramount. And it’s no wonder, in 2019, over 4 billion records were exposed by data breaches—just in the first half of the year. As companies scale, the room for bad actors grows with it as you allow more employees, vendors, and contractors to have access to your systems.
To support our admins in proactively managing security at scale, and to keep our customers and their information safe, IP allowlisting is now generally available to all of our Jira Software, Confluence, and Jira Service Desk Premium customers.
After sifting through hundreds of pieces of feedback and meeting with dozens of admins who manage Atlassian products at scale, we know that our customers have stringent security requirements and need their products to only be accessible by trusted company networks.
In late May we launched a beta program for IP allowlisting, and we’re excited to announce that it’s now available to all Premium customers! IP allowlisting keeps teams and their content secure by ensuring that use of Atlassian Premium products are restricted to VPN and office networks, even for external collaborators, and allows secure access for content consumers.
Access from sanctioned company networks
The risk companies expose themselves to when users access their Jira and Confluence sites from unprotected networks can be high and costly. Now, enterprise and regulated organizations can require all end-users to access Atlassian products from sanctioned company networks. If you have agreements with your own customers about the security of their data, rest assured it won’t be leaving the building.
Secure your external collaborators
Outside of traditional user permissions controls, there is very little admins can do to protect their organization from risky usage of external collaborators. Admins can’t enforce SSO, two step verification, session duration, or password policies on these accounts the same way they can for managed accounts (ie accounts with email addresses from the verified domain). With IP allowlisting, admins get much needed relief with the confidence that product access is restricted to specific networks, even for external accounts.
To add and access your allowlists, please visit admin.atlassian.com > Security > IP allowlisting. From here, add up to 100 IP addresses or network blocks per allowlist.
Learn more about IP allowlisting from our public documentation page, or if you have any suggestions for insights you’d like to see in the future, please leave a comment below and we’ll investigate it for our roadmap!
New to Premium? Learn more here.