Setting up Content-Security-Policy for Atlassian products


I have been looking for the right setting of CSP (Content-Security-Policy). I couldn't find it so I first tried with

Content-Security-Policy "default-src 'self';

but then my pages were not rendered correctly aymore.

It seems to be workling now with the following setting:

Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline';  img-src 'self' data:";

Can anyone confirm this is the expected settings? Can I remove the unsafe-eval from the script?



3 answers

I'd love some recommendation for this also. 

I've been testing CSP lately in our test environment (confluence 6.4.3, jira 7.4.0, apache 2.4.18 proxy), and so far it seems the only way to get it working is to define almost all CSP flags (thanks to, it has good description of those).

Here's example from one of our subdomain's virtual host config:

Header set Content-Security-Policy " \
default-src 'self' *; \
script-src 'self' * 'unsafe-inline' 'unsafe-eval'; \
style-src 'self' * 'unsafe-inline'; \
img-src 'self' * data:; \
connect-src 'self' *; \
font-src 'self' *; \
object-src 'self' *; \
media-src 'self' *; \
frame-src 'self' *; \
child-src 'self' *; \
form-action 'self' *; \

We are using wildcard subdomain in CSP, this seems to allow our two subdomains (jira and confluence) to talk to each other.

We are still getting some errors from jira and confluence admin pages, because both local server instances are trying to load js file from, which is now blocked by CSP. Whether thats fatal or not is still under investigation. 


Thanks for you answer. I do not have the subdomain issue as I have and ;-)

The JS content retrieved from Atlassian should probably be reported as a bug to Atlassian. Imagine one day they have a technical issue, then your "on-premises" instance can also be affected, or worse, if they get hacked, hackers could then inject anything they want straight into your admin console ;-(

If you do raise a bug, provide me the reference I will vote for it ;-)



Did you managed to write a working CPS header?

0 votes
Ann Worley Atlassian Team Nov 06, 2017

CSPs are usually set at the reverse proxy in front of a webserver. It sounds like you are using Apache? Our doc doesn't have a recommendation for that setting: Proxying Atlassian server applications with Apache HTTP Server (mod_proxy_http)

CSP recommendations for several proxies, including Apache, are in this third party doc I found: Secure your website with Content Security Policy

I am not sure what the unsafe-eval is or which script it is in. Please let me know more about this question, I will be happy to research it.


Thanks for your answer.

I indeed set the headers at the reverse proxy (NGINX in my case).

Obviously the most secure approach is to use only scripts in external files (as it should be harder to create a file, than inject  content in a web page).

The eval method is used to execute the javaScript that is in a String. It is sometimes used to "parse" a JSON String to a JavaScript object. The issue is that if the reply contains actual JavaScript, it will be executed.

So if you want to reduce risk of JavaScript based attacks, it is safer to have all your javaScript in static files.

Best regards


Ann Worley Atlassian Team Nov 07, 2017

I am asking our security team about this, but most of them are in a different time zone, so it's slow going.

In the meantime, are the links in Branden's answer to the following question of help? Setting up Content Security Policy in JIRA

Thanks Ann, I have setup the Content Security Policy. it is mostly working, but I would like to know if it can be tighten.

Have a great (sunny) day in AU ;-)

Regards from cold Belgium ;-)

Ann Worley Atlassian Team Nov 07, 2017

Please let me know as specifically as possible what I should ask our security team to help you tighten it. That will help us get a better answer.

I am in Austin, TX! The security folks are in Sydney.

I would be happy to lend you some of our sunny weather. :)

Those links in Branden's answers refer to obsolete X-Frame-Options, CSP's are replacing them. And X-Frame-Options dont support wildcard domains on rules.

So any "official" guide to CSPs would be nice to have.

0 votes
Ann Worley Atlassian Team Nov 14, 2017

@Tero Laihia I got a response from the security team regarding an official recommendation for CSP settings. They let me know that 

we do not have a recommendation for CSP settings for our products and that adding in these headers can cause problems with functionality. While you may find a setting that works for a given product version, future updates may break that policy.

Based on this, it sounds like trial and error is the only way to find out what will work in your environment. If your team uses Content Security Policy headers, it makes it more important than ever to test any upgrades on a test system before upgrading Production applications.

So it is impossible for a confluence server to reach an A grade on

This is beyond the pale.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Tuesday in Confluence

Confluence Admin Certification now $150 for Community Members

More and more people are building their careers with Atlassian, and we want you to be at the front of this wave! Important Dates Start the Certification Prep Course by 2 April 2019 Take your e...

212 views 2 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you