Keene Systems, Inc.

DNN Hosting and Security: A Practical Guide

Most DNN sites that get into trouble are not brought down by DNN. They are brought down by where they live and how they are looked after: a bargain host that does not know the platform, a backup nobody has tested, an update put off for three years. This guide covers what to look for in DNN hosting and the habits that keep a DotNetNuke site safe.

One thing up front: Keene Systems does not sell hosting. We have nothing to gain from where you host, and that lets us be blunt.

What DNN needs from a server

  • Windows Server with Microsoft’s web server, IIS.
  • The Microsoft .NET Framework, in the version your DNN release requires.
  • Microsoft SQL Server for the database.
  • Enough memory. DNN is a real application and it is slow when starved.

That rules out a large part of the budget hosting market, which is built around a different set of technologies. A host that says it “supports Windows” has not told you it knows DNN.

Three ways to host a DNN site

OptionGood forWatch out for
Shared hostingSmall sites with light traffic and no sensitive dataLittle control, noisy neighbors, and limits that can block upgrades
A dedicated or virtual serverSites with custom modules, integrations or steady trafficSomebody has to patch and watch the server
Microsoft AzureSites that must scale, or companies already in Microsoft’s cloudNeeds to be set up by someone who knows both Azure and DNN

Questions to ask a DNN host

  1. How many DNN sites do you host, and which versions?
  2. Which versions of Windows Server and SQL Server will my site run on?
  3. How often are the files and the database backed up, and how long are backups kept?
  4. Have you ever restored a DNN site from backup, and how long did it take?
  5. Can I have a second copy of the site for testing upgrades?
  6. Will my developers get the access they need to the web server and the database?
  7. Is an SSL certificate included and renewed automatically?
  8. Who answers the phone when the site is down?

The fourth question is the one that matters most. A backup that has never been restored is a hope, not a backup.

A DNN security checklist

  1. Keep DNN up to date. Each release closes known holes. This is the single most important item. See DNN upgrade services.
  2. Keep modules and the theme up to date. They are part of the site and carry their own fixes.
  3. Remove modules you do not use. Software that is not installed cannot be attacked.
  4. Guard the host account. The host, or superuser, can do anything. Keep the number of host accounts small, and remove those of people who have left.
  5. Use strong, individual passwords. No shared logins, so you always know who changed what.
  6. Run the whole site over HTTPS, including the login page.
  7. Review roles and permissions. Check who can edit what once or twice a year. People change jobs and permissions do not follow them.
  8. Limit what can be uploaded. Editors need to upload pictures and documents and nothing more.
  9. Run DNN’s built-in security check and act on what it reports.
  10. Keep the server patched. Windows, the web server and SQL Server all need their updates.
  11. Back up the files and the database together, and test a restore.
  12. Read the logs. DNN records failed logins and errors. Someone should look.

Signs your DNN site may already be compromised

  • Pages or links you did not create.
  • Visitors redirected to another website.
  • User accounts nobody recognizes, especially with administrator or host rights.
  • A warning from Google or a browser when the site loads.
  • A sudden slowdown with no change in traffic.

If you see any of these, get help before you start deleting things. What is on the server is the evidence of how the attacker got in.

Who is responsible for what

This is where sites fall through the cracks. The host looks after the building: power, network, the server. Someone else has to look after the site inside it: DNN, the modules, the accounts and the permissions. When that someone has left the company, nobody is doing it. If that is your situation, see DNN support and site takeover.

Need a hand?

We review DNN sites, bring them up to date, and can recommend a host that knows the platform. See our DotNetNuke development services or book a 20-minute call.

Frequently asked questions

Can DNN run on Linux hosting?

No. DNN needs Windows Server, the .NET Framework and SQL Server.

Can DNN run on Microsoft Azure?

Yes. It needs to be set up by someone who knows both.

Is DNN secure?

Its security is built into the core and is sound when the site is kept up to date. An unpatched site of any kind is at risk.

Does Keene Systems host DNN sites?

No. We work with your host, or recommend one that knows DNN well.

Previous Post
Next Post

Book an Appointment

Whether you are interested in starting a conversation around your current IT challenges or just have some questions about Keene Systems, please fill out our contact form below. We will respond within one business day.