Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
A CMS is software for managing a site's articles and images. The name stands for content management system. Without writing a specialist program, you can add articles and swap images from an admin screen. IPA's twenty-point checklist for safe website operation treats a web application as something built from software such as a framework or a CMS.
How does a CMS work?
It resembles a magazine editorial office. Manuscripts and photos go on a shared shelf (the admin screen), and a layout template (the theme) arranges the look. Missing functions are filled by add-on tools brought in from outside (plugins).
A CMS consists of a base that stores article data, an admin screen, a part that shapes the appearance, and add-on parts. Each of them receives updates, so if any one stays old, that spot can become an entrance.
IPA's twenty points include, as a checkpoint, whether vulnerability measures for the software that makes up the web application are taken regularly. They ask you to know which software you use and to take measures. Raising the versions of the OS, server software and middleware is a separate item.
The 2014 JPCERT/CC alert names, as a cause of tampering, web server software that keeps running at an old version. The measures are to update to the latest version and to move to a product that is still supported.
What a WordPress assessment covers is shown on the WordPress assessment page. The free URL check offers a look at the site from where a visitor stands.
Why does a CMS matter?
The advantage of a CMS is that the person in charge can do the update work. The effort of updating stays with that person as well. The more old versions, versions whose support has ended, and unused add-on parts pile up, the wider the surface that can be targeted.
IPA's twenty points also ask whether any unneeded services or applications remain. The content is to stop everything other than the minimum needed and to delete applications that are no longer required.
To make it a monthly habit, follow this order: look at the update notices in the admin screen, delete unused plugins and themes, and take stock of administrator accounts. Take a backup before updating.
Related terms
- Plugin: an add-on part that gives a CMS or other software more functions
- Patch management: applying software fixes on a planned schedule
- End of life: a state where the provider no longer releases fixes
- Unpatched software: a state where fixes have not been applied
Frequently asked questions
Does using a CMS weaken security?
Not necessarily. What matters more than whether you use a CMS is whether you update the version and the add-on parts in use, and remove features you do not need. IPA lists regular vulnerability measures for the software that makes up the site as a checkpoint.
I am afraid an update will break the display. What should I do?
Before updating, take a backup and, if possible, check the display in a test copy. IPA also says to verify in advance that the existing web application still works after a version upgrade.
Next step
Reviewing WordPress updates and add-on parts is described on the WordPress assessment page. If you would like to plan an update routine together, contact us.
Frequently asked questions
Does using a CMS weaken security?
Not necessarily. What matters more than whether you use a CMS is whether you update the version and the add-on parts in use, and remove features you do not need. IPA lists regular vulnerability measures for the software that makes up the site as a checkpoint.
I am afraid an update will break the display. What should I do?
Before updating, take a backup and, if possible, check the display in a test copy. IPA also says to verify in advance that the existing web application still works after a version upgrade.