Blog

#wcus @miriamschwab: Google's resources making it possible for more people to implement CSPs.

#wcus @miriamschwab: There are also WordPress plugins for this, not recommended because some are out-f-date, but easy way to get started.

#wcus @miriamschwab: CSP Mitigator from Google: Check http response headers, if no CSP present, will alert. If CSP… https://twitter.com/i/web/status/1071070901360361472

#wcus @miriamschwab: CSP can be added using meta tag or in theme's functions.php file. Also .htaccess. Use these if… https://twitter.com/i/web/status/1071070524502085633

#wcus @miriamschwab: Google has tools for CSPs: Strict Dynamic Test Bed, not sure of accessibility of tool will need to check later.

#wcus @miriamschwab: Keeping up with what's been added to pages manually is hard. Use Scrict Dynamic CSP instead. O… https://twitter.com/i/web/status/1071070100252446720

#wcus @miriamschwab: Google is "do-as-we-say-not-as-we-do" with regard to its CSP docs V. what it does with its Goo… https://twitter.com/i/web/status/1071069163681185794

#wcus @miriamschwab: If you research content security policies online, not a lot of upp-to-date information, CSPs h… https://twitter.com/i/web/status/1071068767654940672

#wcus @miriamschwab: Includes log of violations of content security policies. I'm going to love looking at this code.

#wcus @miriamschwab: Demonstrating code snippets which implement content security policies, will share slides later.

#wcus @miriamschwab: Content security policies: white-list sources via browser header, if a source is not white-lis… https://twitter.com/i/web/status/1071067380346949632

#wcus @miriamschwab: Magic Cart hacks scripts for the purpose of skimming credit card information.

#wcus @miriamschwab: Magic Cart: Going on for last three years, no one knows origination, attack ID's third-party s… https://twitter.com/i/web/status/1071066855375323148

#wcus @miriamschwab: Why is cryptomining from websites bad? Because it eats resources, plus governments shouldn't be cryptomining.