Ironhelm Suite

Security

Logins, updates, firewalls and the habits that keep WordPress sites out of trouble.

Why every Ironhelm update is signed

How Ironhelm verifies every release with an Ed25519 signature before WordPress installs it, and why that matters even if our server were compromised.

An activity log you can trust: what to record and for how long

When something goes wrong on a WordPress site, the first question is who changed what. What a useful activity log records, why tamper evidence matters, and how long to keep it.

Why WordPress blocks SVG uploads, and how to allow them safely

SVG logos are sharp and tiny, but an SVG file can carry JavaScript. Why WordPress refuses them by default and what a safe SVG upload actually has to do.

Security headers explained for site owners

Five short HTTP headers tell browsers how to protect your visitors. What HSTS, CSP, X-Frame-Options and friends do, and how to add them without breaking the site.

Where WordPress vulnerabilities really come from

Over 11,000 new WordPress vulnerabilities were reported in 2025, almost all in plugins. What the data says, the 2024 supply chain attack, and what to do about it.

Passkeys for WordPress admins: how they work and when to use them

Passkeys replace the password with a key your phone or laptop keeps, bound to your site's domain. Why that defeats phishing, and what to watch out for.

Your login page is under constant attack. A sane lockout policy

Password-guessing bots hit every WordPress login, all day. How the attacks work, what a sensible lockout policy looks like, and the mistakes that lock out real people.

Two-step login on WordPress: what actually stops account takeover

A stolen password should not be enough to run your site. What the research says about two-step login, which methods hold up, and how to roll it out without a revolt.