Wednesday, October 18, 2017

Here´s my presentation I gave at Social Connections 12 in Vienna 17. October 2017.

Vienna was such a beautiful venue for the Social Connections 12 conference. Thanks to the #soccnx team for putting it all together!!

I´ve put my presentation up on SlideShare, and here it is:



Social Connections 12. We hired hackers to hack us from Robert Farstad

A small warning:
The section I talk about regarding tightening Header Security, setting the "Header set X-Frame-Options SAMEORIGIN". This might break your Sametime Awareness inside of IBM Connections. There is a X-Frame-Option "Allow From", where you can set the Sametime Proxy´s hostname to be allowed, but this one is not supported by Chrome. So, setting the "Header set X-Frame-Options SAMEORIGIN" will work for IBM Connections and IBM Docs, but not if you have Sametime Proxy integration into Connections.

5 comments:

Gunleif said...

Hei, jeg får ikke ta en fullscreen og dermed ikke fått lest presentasjonen

Robert Farstad said...

Heisann. Den er nedlastbar hvis du har en slideshare konto. Se her: https://www.slideshare.net/rockbert77/social-connections-12-we-hired-hackers-to-hack-us/1

Giannandrea said...

Hi Robert,
I started to study your recommended settings about headers to clearly understand their features, but now I kindly ask your help for a better understanding...

The following directives are (now) clear:
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
Header set Referrer-Policy "same-origin"
Header set X-Content-Type-Options "nosniff"
Header set X-XSS-Protection "1; mode=block"

Instead the following 2 lines:
Header set X-Frame-Options "DENY”
Header set X-Frame-Options SAMEORIGIN

left me uncertain because:
- they appear to me as 2 different settings for the same directive
- from what I learned DENY is the most restrictive (the page cannot be included in an IFRAME)
- while SAMEORIGIN is less restrictive (the page can be included in the IFRAME if the parent is from the same domain)

So I suppose that only this one:
Header set X-Frame-Options DENY
(maybe without "..." as for SAMEORIGIN) should be enough... but surely I'm wrong :-)
Please could you help me to solve these doubts?
Thanks again for posting so precious information.

Giannandrea

Giannandrea said...

Hi Robert,
I performed some additional tests and I would like to share them with you :-)

Using the following settings:
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
Header set Referrer-Policy "same-origin"
Header set X-Content-Type-Options "nosniff"
Header set X-XSS-Protection "1; mode=block"
Header set X-Frame-Options SAMEORIGIN
(I removed -> X-Frame-Options "DENY")

In this way I reached an "A" with SecurityHeaders.io
I read your warning about awareness connectivity broken when using SAMEORIGIN directive, but Sametime integration it's not present in my scenario, so it's not an issue.

After that, as recommended from SecurityHeaders.io I added also the following directive:
Header set Content-Security-Policy "default-src 'self';"
and I performed a new test, which has given me an "A+"

Needless to say, this setting breaks something important because I've not been able anymore to reach my Connections login page, so I had to remove this last setting.

An "A" is definitely a good score, but I think it would be interesting to discover which instructions Connections "loads" which are not compliant with this last setting.

Again a big thank you for sharing these information!

Giannandrea

Robert Farstad said...

Hi Giannandrea.
Thank you for sharing your testing result as well.

I agree, an "A" is a good score and I, as you, would like to know what exactly "breaks" Connections here.

I did create a PMR to IBM Support on this, where I asked if they have any suggested settings. After they asked the developers about it, the answer was that IBM does not have any recommended settings to share with us.

Which is weird, because if you test the site "apps.na.collabserv.com" which is the IBM Collab Cloud Address for North America, you get the grade "D" and not the default "F". Which means that IBM in fact has put in some of the header security stuff into the front-end servers they are running.