Secure WordPress Without Coding Skills
summary
Asserts that simple, specific steps cut most risk: use 25-character passwords stored in a manager (one master password), enable two‑factor auth with Google Authenticator, keep core/plugins/themes updated and avoid abandoned add-ons, and disable open registration. Recommends HTTPS via Let's Encrypt and verifies backups work — hosting often provides daily backups kept 30 days but restore procedures must be tested and old backup copies pruned. Notes hosts block millions of bot requests with anti‑bot AI and recommends Wordfence.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:20Disclaimer
- 2:03Common Sense Dispenser
- 2:44Hack Story
- 3:41Security is a Process
- 4:06Who carries the attacks
- 6:06Why do they do it
- 6:35What they can do
- 8:40Effects of being hacked
- 9:49There is no chance of being hacked
- 10:09Passwords
- 12:59WordPressorg
- 13:32Update everything
- 14:55Backup
- 17:06HTTPS
- 18:40Memes
- 19:44TwoFactor Authentication
- 21:27Conclusion
- 22:52Off works
- 23:25WordPress plugin
- 23:40Backups
related talks
27mSecuring your WordPress sites
08mPractical web security
01h 01mSecurity: From basic principles to PHP specifics
36mHow the WordPress Ecosystem Handles Security and What You Can Learn from It
22m5 Tips To Optimise WordPress To Be Faster and More Secure
44mI've Been Hacked, Now What
43mI Had WordPress, but It Got Hacked
29mSecurity is not a Feature!