Re:HTTP Observatory: analyze your website and review availab...
by rmdoss on Saturday August 27, 2016 @12:28PM
(#12373003)
Their description doesn't really match what they do:
"Observatory by Mozilla is a project designed to help developers, system administrators, and security professionals configure their sites safely and securely.
"
All they check is if you have a few security headers and consider that "secure".
There is a LOT more to website security than adding a few extra headers and HTTPS to your site. Even if you get an A, it doesn't mean anything.
To give an example, Google gets a D, CloudFlare a D, Youtube a C+, etc..
Re:HTTP Observatory: analyze your website and review availab...
by viraptor on Saturday August 27, 2016 @07:19PM
(#12374617)
I don't see a problem. They don't claim to be a one-stop integrated security scanner for all your website needs. I'd be happy if they explicitly included something like a link to OWASP with "get more detailed info here". But I don't think they're misrepresenting the service.
The Observatory measures site's compliance with the Web Security guidelines [1] and the Server Side TLS guidelines [2]. It's primarily meant as a helper for website developers and operators.
Re:HTTP Observatory: analyze your website and review availab...
by jvehent on Saturday August 27, 2016 @02:57PM
(#12373648)
You need https to guarantee data in transit is not being modified between your server and web clients. ISPs, for instance, have a bad tendency to inject tracking cookies in http traffic.
Re:HTTP Observatory: analyze your website and review availab...
by pbhjpbhj on Saturday August 27, 2016 @05:07PM
(#12374179)
It actually includes a summary result for https://securityheaders.io on the page. That site, your suggestion, says "A scotthelme.co.uk project - CC-BY-SA 4.0" so I wouldn't be surprised given the similarity in presentation if Observatory was based in some way on SecurityHeaders.io.
"Observatory by Mozilla is a project designed to help developers, system administrators, and security professionals configure their sites safely and securely. "
All they check is if you have a few security headers and consider that "secure".
There is a LOT more to website security than adding a few extra headers and HTTPS to your site. Even if you get an A, it doesn't mean anything.
To give an example, Google gets a D, CloudFlare a D, Youtube a C+, etc..
That is probably due to the non-trivial number of clients which don't support modern stuff (old browser, etc.).
Example run on addons.mozilla.org: https://observatory.mozilla.org/analyze.html?host=addons.moz...
The Observatory measures site's compliance with the Web Security guidelines [1] and the Server Side TLS guidelines [2]. It's primarily meant as a helper for website developers and operators.
[1] https://wiki.mozilla.org/Security/Guidelines/Web_Security
[2] https://wiki.mozilla.org/Security/Server_Side_TLS
(disclaimer: I work on security at Mozilla)
I run http only site, I installed everything from scratch and minimized all attack surfaces. I got F because I'm lacking https stuff.
But maybe I'm missing something. If you don't deal with user logins and no sessions. Do I need to get https?
Or is this site just assuming things?
> Score: 120/100
>Score: 40/100
https://observatory.mozilla.org/analyze.html?host=google.com
(Would take this rating with a grain of salt.)