nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Recommendations for Internet facing deployment of Jira

Paul Ryan3

Hi all,

Our company is considering an Internet facing deployment of Jira. While I have read various articles including the best practices guides on the Atlassian and other web sites, I am wondering whether I should be considering 3rd party products to implement a layered security approach.

I notice from the web site that this software is deployed by quite a few multinationals and I cannot imagine, even for an internal deployment, there are relying 100% on the Jira application to ensure the security of the information in the portal.

Two things that come to mind to implement this approach are:

- Web Application Firewall (WAF)

- Identity Management solution integrated with the WAF and Jira

What have other users done?

Are there any recommendations on these? What works well? Not so well?

Thanks,

Paul

Accepted answers

Nic Brough -Adaptavist-

My clients have used:

Apache, SSL and certificates. The systems are on the raw internet, but you can't get past Apache without a valid certificate
Crowd for ID management, integrated with their firewall
VPNs to drill through corporate firewalls, so the systems aren't really on the internet, but people can use the internet to pretend that they're inside the company network

The approaches all have strengths and weaknesses. Integrating certificates into ID management is not fun, but it's a solid approach to security and authorisation. The raw Crowd+systems worked fine, except with the public access stuff, we ended up with a lot of spam accounts. VPNs work well, but it's not really putting your systems on the internet. I think the answer is "you need to do what suits you and your usage best". If it's an internal system, I'd look at a VPN first, as you'll be limiting it to just known users. The SSL certificates are good if it's your people, plus known external users, but you'll need an ID and certification system (Crowd doesn't do certs). I'm less convinced by just "atlassian systems raw on the internet", I think there's a strong argument for firewalling carefully and having human authorisation systems in place to approve new accounts at the very least. (Although, I must say, that was the only problem we had)

All comments

Nic Brough -Adaptavist-

My clients have used:

Apache, SSL and certificates. The systems are on the raw internet, but you can't get past Apache without a valid certificate
Crowd for ID management, integrated with their firewall
VPNs to drill through corporate firewalls, so the systems aren't really on the internet, but people can use the internet to pretend that they're inside the company network

Paul Ryan3

Thanks Nic for the response.

We have used #1 with client certificates before but it is inflexible for multiple device support and adds to the costs of support.

In relation to 2 "Crowd for ID management, integrated with their firewall", what was the configuration? Was it the web application firewall checked the user authentication data against Crowd before the request was sent to the Jira application? Do you want to mention the web application firewall vendor?

Thanks again,

Paul

Nic Brough -Adaptavist-

Yes, the certs stuff can be "fun" ;-)

I'm not entirely sure what the firewall vendor was, but I do know they had a set of dedicated Linux boxes that we had to tell Crowd to talk to. I don't think it was anything more complex than a username/password challenge, then the firewall would pass traffic from that source.