WordPress Security: Q&A Session [Panel]
summary
Panel answers focus on concrete defenses: use a firewall plus a malware scanner as layered protection, scan server-side and database files, and investigate compromises rather than just remove malware. Cite tokenization and hashing to avoid storing sensitive data, keep plugins updated, and watch supply-chain risks when plugins change hands. Note Monero browser miners and server-side miners as common abuse, mention Atlanta’s ~$2.7M recovery cost and a hands-on CTF to practice attacks.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 3:38Crosssite scripting
- 7:05How to obscure data
- 11:57Examples of data
- 13:57Medical data
- 14:57BOTS
- 17:57Remediation
- 18:57Serverside scanner
- 19:57Agent
- 20:57Sakai
- 26:57Security mechanisms
- 27:57Cold supply chain attacks
- 28:57Plugins and reputation
- 29:57Tide project
- 30:57Plugins
- 31:57Research
- 32:57Research business model
- 33:57GDPR
- 34:57GDPR Audit
- 35:57GDPR Advice
- 36:57GDPR Complaints
- 38:57Why did they attack
- 39:57Serverside content mining
- 40:57Attacker targets website
- 41:57Smart refrigerators
- 42:57Drones
- 43:57Voting machines
- 44:57Stuxnet
