Content Security Policy: Putting the Browser on a Security Diet
Web applications have become remarkably powerful.
Read article: Content Security Policy: Putting the Browser on a Security Diet7 articles tagged Web Application Security.
Web applications have become remarkably powerful.
Read article: Content Security Policy: Putting the Browser on a Security DietThere is a special kind of optimism that exists in software development.
Read article: Input Validation: Because Users Are Creative, and Attackers Are More CreativeRegardless of your application architecture or front-end type, there are a variety of common attack types that the application security architecture’s capabilities must protect against. I’ve talked about these topics briefly before here, here, and here.
Read article: Prevent XSS and Other Common Attacks on Your AppAuthentication is described in this post.
Read article: Static Credentials Must Not Be Used In The BrowserThis post continues where “SECURELY USING THE OIDC AUTHORIZATION CODE FLOW AND A PUBLIC CLIENT WITH SINGLE PAGE APPLICATIONS” left off on the topic of securing Single Page Applications (SPAs). That post describes an architecture where the SPA running in the browser (User Agent)is acting as the…
Read article: More Single Page Application (SPA) and OAuth2 ThoughtsI’ve had to look up the HTML codes for special characters like space many times. In fact, while writing blog entries for Thinkmiddleware.com, I’ve had to stop and look up the HTML code for less-than sign and greater-than sign one to many times. I just haven’t bothered memorizing them.
Read article: URL & HTML Character RepresentationGoogle has released a Browser Security Handbook online. It can be found here.
Read article: Google Browser Security Handbook