Browser Security Tutorials

Chrome Flags which you need to checkout

Firefox becomes more and more a PR GAG and Mozilla doesn’t deliver what they promise – a secure Browser – so you might want to switch to Chrome, or a fork like Chromium instead in order to get a ‘clean’ Browser. However, you can tweak several about:flags options in order to harden your Chrome even more.

Chrome Flags

Why shouldn’t you use default settings (no matter which software)?

Hackers often test their attacks against the default settings which means if you leave everything how it was you then might risk that you’re vulnerable to known (or unknown) attacks.

The developers often test new features in a Browser in order so see if and how many people having problems using it and based on their comments it might get it’s release into the stable build or not.

Why isn’t everything from the beginning on maximum?

The reason here is simple, maximum security means that you might break some websites or functions – or in a worst case scenario – the Browser crashes or you extensions are non-functional. The thing is that ever user has other needs and different kind of security understandings, some of the options are really a benefit but they might cause some side-effects like slow-downs or longer loading times.

Some option might also taking more system resources and not every user ‘likes’ this due to different reasons, maybe he has an old systems or want a browser which doesn’t waste much energy which is a big point on mobile devices.

Why is Chrome superior over all other Browser since years?

Chrome is simple, fast and since the beginning more efficiency. It doesn’t have as much customization options like other Browser but most people these days want to Browse the web and this – if possible – secure. Google delivers what they promise since years and there less attacks because Chrome’s sandbox is already developed since years and gets constantly improved with the help of thousands of contributors. All other Browser mostly copy Google including the sandbox feature since there out of own ideas.

I’m not going to say everything is perfect, I guess no browser is perfect since this would require that everyone would have the same opinion but the fact that Chrome is less vulnerable and doesn’t come with ‘study’ shit is undeniable. Less functions means always less attack factors and this is proven yet again this year with Pwn2Own, Chrome wasn’t hacked.

Changing the about:flags

The process is really easy, just type in the URL address bar chrome://flags and that’s already it, you see the ‘hidden’ options.

I’m not going to explain each toggle because there already documented and a description is directly visible right next to the toggle. So let’s skip it and I show only the relevant flags, please keep in mind that the flags are might be not visible if you’re on an older (or newer) Chrome/Chromium version – because some options are maybe removed or added during the develop process, some options are also depending on which OS you’re.

Security related about:flags