Sitecore sites are attractive targets: they often belong to large organizations, they're publicly visible, and attackers can easily tell a site runs Sitecore. Sitecore has published several critical security bulletins in recent years, including remote code execution issues. Sites that weren't patched quickly were scanned and attacked.
The good news is that most real risk comes from a short list of basics.
1. Apply security hotfixes
Sitecore publishes security bulletins on its support site, with hotfixes or instructions for each affected version. Many sites have never had a hotfix applied since go-live, because nobody owns the task.
What to do:
- Subscribe to Sitecore's security bulletin notifications, and make one named person responsible for reading them.
- Check every bulletin against your exact version, and record which hotfixes are installed in each environment.
- Treat critical bulletins as urgent. Have a process to test and deploy a hotfix within days, not months.
2. Lock down admin and login pages on public servers
On content delivery servers, the public shouldn't be able to reach the Sitecore login page, the admin pages under /sitecore/admin, or the Sitecore client. Sitecore's security hardening guide describes how to deny access to these paths. Yet it's still common to find them open on live sites.
What to do: try opening /sitecore/login and /sitecore/admin on your public domain from outside your network. If either loads, restrict them with IIS rules, a firewall or your CDN, and only allow content management from trusted networks or a VPN.
3. Remove default and shared accounts
The default admin account is the first thing attackers try. Shared logins also make it impossible to know who changed what.
What to do:
- Make sure the default admin password was changed, and consider disabling the account after creating named administrators.
- Give every person their own login, with only the roles they need.
- Remove accounts of people who left, including agency staff and contractors.
- If possible, connect Sitecore login to your identity provider so you get single sign-on and multi-factor authentication.
4. Follow the hardening guide
Sitecore's security hardening guide lists a set of configuration changes, such as removing unused handlers, restricting file uploads in the media library, protecting the media request handler, and securing cookies. Many were never applied because the site launched under deadline pressure.
What to do: go through the guide for your version as a checklist, and record which items are done. It's a good piece of work to schedule once a year.
5. Stay on a supported version
Once a Sitecore version leaves extended support, it no longer gets security fixes. New vulnerabilities found later stay open on that version. Some security teams and auditors flag unsupported software as a finding on its own.
What to do: check Sitecore's product support lifecycle page for your version's end dates, and plan the upgrade early. See the Sitecore 9.3 to 10.x upgrade checklist.
6. Patch everything around Sitecore
Sitecore runs on Windows, IIS, .NET, SQL Server and Solr, and your solution adds its own NuGet and JavaScript packages. Each needs updates.
What to do: include Sitecore servers in your normal Windows patching, keep Solr inside a private network and never expose it to the internet, and check your solution's packages for known vulnerabilities as part of each release.
7. Test it
A yearly penetration test, plus a quick check after major releases, catches problems before attackers do. Make sure the testers know they're testing a Sitecore site, so they check Sitecore-specific issues.
What to do next
Do the two quick checks today: try the login and admin URLs on your public domain, and look up the latest Sitecore security bulletins for your version. If you find gaps, or you'd like someone to own patching for you, it's part of my Sitecore support and maintenance service.
