If a transaction is validated by a code sent to the email or phone before being carried out, would this prevent the transaction from being carried out using only cookies?
Hmm without further context it's hard to definitively say yes or no but it sounds like yes that would help ensure the request is being done intentionally by someone and not maliciously by a bad actor. Essentially, when it comes to CSRF, having a way to validate the source of the request is key to mitigating the vulnerability. One common way to mitigate CSRF is using what's called the Synchronizer Token Pattern. That involves create a unique and random token that is included in the request and the server validates it before handling the request further.
Appreciate the feedback Chuck and I definitely understand disliking that sort of thing. What are the types of thumbnails that you prefer or find yourself clicking on more then? I'm continuously learning how things work on YT and lean on a partner of ours to help with the thumbnails so it'd be super helpful to hear your suggestions and discuss this further with them.
![[LIVE] BABYMONSTER(베이비몬스터) - DRIP | 두시탈출 컬투쇼](http://i.ytimg.com/vi/UG05pxLGwzc/mqdefault.jpg)
This is such valuable information for anyone looking to strengthen their cybersecurity knowledge. Big thanks for sharing!❤
Thank you so much for the comment! I'm glad to hear you found this valuable 👍
@@clarkio You're very welcome! I'm always excited to support your great content. Keep up the fantastic work! 👍
Thanks for uploading a video on this topic.
Thank you too for the question that inspired this video 👍
Also did this help answer your question? Do you have any further questions that come to mind? Hope it helped
@@clarkio Thanks. It did help. I will let you know if I have any further questions .
If a transaction is validated by a code sent to the email or phone before being carried out, would this prevent the transaction from being carried out using only cookies?
Hmm without further context it's hard to definitively say yes or no but it sounds like yes that would help ensure the request is being done intentionally by someone and not maliciously by a bad actor.
Essentially, when it comes to CSRF, having a way to validate the source of the request is key to mitigating the vulnerability. One common way to mitigate CSRF is using what's called the Synchronizer Token Pattern. That involves create a unique and random token that is included in the request and the server validates it before handling the request further.
Whenever I see a ridiculous "open mouth" thumbnail. I immediately hit "do not recommend channel."
Appreciate the feedback Chuck and I definitely understand disliking that sort of thing. What are the types of thumbnails that you prefer or find yourself clicking on more then? I'm continuously learning how things work on YT and lean on a partner of ours to help with the thumbnails so it'd be super helpful to hear your suggestions and discuss this further with them.