What is Web Security?
The web is not safe for every user, Daily we hear about websites becoming unavailable because of denial of service...
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
I don't think its necessary to know about CSP or CORS. You can build a perfectly secure website without any knowledge of these things; most websites I've worked on don't use these security hardening features.
One thing potentially worth mentioning is HSTS which can prevent downgrade attacks.
I disagree.
The fact that CSP is not widely use is a signal that developers - especially frontend devs - should be more educated on security topics.
Without a good Content Security Policy how confident are you that your customers are safe against XSS? For instance, how do you ensure that one of your users doesn't have a browser extension that logs their credentials as they type to a malicious server?
I suggest this article or this other (don't miss the video) from Troy Hunt.
CSP may not be the only option to counter these attacks, but one has to be aware of the risks that can originate from the client-side of our applications and websites.
I agree with you 👌
In practice, it isn't easy to implement CSP when libraries come into play. It is nice to add for hardening, but it isn't necessary, and should not be considered a primary form of defence against XSS.
Nothing about security is easy and the fact that one method is not easy to implement doesn't make it less valuable.
Also, you can always set the CSP as report-only if you're (correctly) worried about potentially breaking stuff. Implementing a good policy slowly over months is better than never doing it at all.
But anyway, if other methods are preferable in your view it's more constructive to explicitly say which ones, so people reading the comments can actually get value out of the discussion.
Cheers!
I consider CSP to be an advanced topic because it is a additional defence against XSS. I do not consider it a "must know". What I consider essential knowledge is how to reason about trusted and untrusted inputs, making sure to sanitize if your framework or library doesn't already do it.
Again, I don't consider this a "must know". I mean, its cool and all but I don't consider auditing something everyone should know about. I'd much rather have people know about ways you can actually completely shoot yourself in the foot than know about CSP.
Surely, although for me they really are different methods solving different but equally serious problems. But this is now more a personal opinion about what is and what is not a must know, so less valuable/interesting.
Thanks for keeping up the thread and replying with an informed opinion and a link to a reputable site.
I really appreciate it 👍👍👍
CORS is pretty important. one instance, we developed a web API, and a client both worked well in local but when moved to stagging env the app was not working reason CORS.
With the modern web, it really became a staple to consume resources from different origins, and understanding why the same-origin policy was introduced makes more sense
Yes, HSTS is useful to understand, I will add it in one of the following articles, but for CSP and CORS it is useful to understand them to increase your knowledge of web security and this knowledge what makes the differences between web developers.
A bunch of things I did not know. Thank you!
I noticed there was a huge sentence fragment here this chunk of your blog post:
I appreciate your help to improve this article, I will edit it now, thanks a lot
Cors is a browser enforced policy.
The server provide the the header during the preflight request made through an OPTION call.
The server does not send any error.
thanks for this information, i will update it and if there other informations in this Topic provide it to us
Cool, very useful info, animus...😁👍✌️
happy to help🤝
I have some feedback. I noticed that you weren't consistent with the acronym for Transport Layer Security. In some places, you wrote TLS, which is correct, while in others you wrote TSL, which is incorrect. You should go back through your article and change any instance of TSL to TLS to make it correct. Thank you.
Thank you for yor note 👌
Please, take note of the following (among others):
All in all, please review the article for possible grammar mistakes.
nice researched article
Thank you
Nice text, but please run a spellchecker before publishing
I will, thanks for the note
So usefull information
I am grateful for your review
Great info, thanks!
it's my pleasure to help you
There is some good information here, but surely you could get an English speaker to proofread / edit your copy. Reading this is pretty bad.
I Certain all the information here is very clear, and if you find any sentence difficult to understand or read, show me its place and I will try to improve it to be better. Finally, thank you for your note.
There are a ton of grammatical errors and word omissions. It’s missing a lot of articles, transitive verbs, and correct verb conjugations. I can extract the general information for the most part, but no, it is not very clear, and it is very jarring to read. Essentially every sentence needs to be read twice. Simply having an English speaker rewrite it would take your articles to another level and probably improve your English.
Ok.
Thank you for very good article...
Please publish the second part... If it is published already.... Could you please share the URL here
hi, thanks for the article. Found a typo 'It contains very import information about the owner' => 'It contains very important information about the owner'. thanks
Thanks for the note 👌