Compliance tasks
This folder holds 51 short, practical tasks for administrators, editors and developers of public bodies. Each task names who it is for, what you need before you start, the steps with real menu paths and commands, how to check that it worked, and how to go back. The background is in the Governments sections on accessibility, security, privacy and records; each task links to its section page.
Some tasks of the same family live in the people-and-permissions tasks, because they are about accounts and roles: Turn on two-step sign-in for staff, Help a user who lost their phone, Switch on account lockout, Unlock a locked account, Find accounts not used for months, Deactivate and move a leaver, Export the account list for a review and Give an auditor read access to the audit trail.
Contents
Tasks in this folder
| Group | Task | What it does |
|---|---|---|
| Passwords and sessions | Set the minimum password length to 12 | raise Exponential's minimum password length from the shipped 10 to 12 (the OWASP ASVS 4.0.3 level 1 value) or more, without locking anyone out, and check that new passwords follow it. |
| Passwords and sessions | Add your own words to the weak password list | make Exponential refuse passwords built from your organization's own words (its name, the site, the city) on top of the shipped list of well-known passwords, with WeakPasswordList[] or WeakPasswordFile. |
| Passwords and sessions | Sign out every session of a user | after a suspected account takeover or a lost device, end every session of one user in Exponential by changing the password (EndOtherSessions), disabling the account, or removing sessions under Setup > Sessions with the database session handler. |
| Passwords and sessions | Retire the shared admin login | replace the shared admin account with personal administrator accounts so the audit trail names people, then disable admin (after moving UserCreatorID) or make it unusable, and keep a tested break-glass procedure. |
| Passwords and sessions | Separate session cookies for the administration | give every siteaccess its own session cookie in Exponential (SessionNameHandler=custom), so a sign-in on the public site is not a sign-in in the administration, and check the result. |
| CSP, headers and network | Switch the administration's CSP to enforce | after the template audit and a period of clean reports, change the Content Security Policy of the administration siteaccess from report-only to enforce, deploy it to every process, and check the header. |
| CSP, headers and network | Review CSP reports | collect Content Security Policy violation reports with Exponential's own csp/report collector, read them in Setup > Log files, tell real problems from noise, and decide per source what to fix or allow. |
| CSP, headers and network | Roll back the CSP to report-only | when an enforced Content Security Policy blocks work, return the siteaccess to report-only in minutes, make every process send the new header, and keep collecting reports to fix the cause. |
| CSP, headers and network | Start CSP reporting on a public site | public siteaccesses get no Content Security Policy by default; switch one to report-only with Exponential's own report collector, so you learn what your design, content and embeds would need before enforcing. |
| CSP, headers and network | Add HSTS | turn on HTTP Strict Transport Security for a site that is fully HTTPS, with Exponential's SecurityHeaders setting (Apache, nginx) or Velocity's HSTSMaxAge, starting short and raising the value in stages. |
| CSP, headers and network | Set secure session cookies | on an HTTPS-only site, force the Secure flag on Exponential's session cookie, keep HttpOnly and SameSite=Lax, choose a session timeout with your editors, and check the flags with curl. |
| CSP, headers and network | Check the security headers | check from outside that every Exponential siteaccess sends the expected security headers and cookie flags, that internal files are not served, and record the result as evidence for an audit. |
| CSP, headers and network | Restrict the administration by network | limit the administration siteaccess of an Exponential site to your office network or VPN with Apache Require ip or nginx allow/deny, after giving it its own host name, and check from outside. |
| Audit trail | Review the audit trail for a user | see everything one user did (sign-ins, failed sign-ins, content moved, hidden or removed, role and setting changes) in Exponential's Audit console or with exp:audit search, narrow it by time and event, and note what you found. |
| Audit trail | Export audit records for an investigation | select the audit records an investigation needs, verify the chains, export them as a signed bundle or JSON lines with their sha256, and document the hand-over so the export can serve as evidence. |
| Audit trail | Verify the audit trail | check that no audit record was changed, removed or inserted with exp:audit verify or Verify now, add the check to monitoring by its exit code, and know what to do when a channel is broken. |
| Audit trail | Route audit alerts to a security mailbox | send Exponential's audit alerts (brute force, administrator role granted, mass delete, audit switched off, broken chain) to your security team's mailbox instead of the site's AdminEmail, and check the recipients. |
| Audit trail | Restore an archived audit day | read audit records older than the 90 live days by restoring the archived day with exp:audit restore, check it against its signed manifest, search it, and know what happens to the restored copy. |
| Audit trail | Record who published content | switch on the audit events content.object.create and content.object.publish, which Exponential leaves off by default, so the audit trail answers "who published this, and when?", and check that publishing is recorded. |
| Audit trail | Make the audit stricter for privacy | apply the audit guide's strict-privacy profile (hashed logins and addresses, no user agents, keys-only before and after values, 30 days to pseudonymization, shorter retention) where your data protection officer asks for less personal data in the audit. |
| Audit trail | Forward the audit trail to syslog | send Exponential's audit records to your central log collector or SIEM over TLS with the syslog sink, choose the channels, test delivery with exp:audit sinks test, and keep it running. |
| Audit trail | Rotate the audit signing key | replace the key that signs Exponential's audit checkpoints and archive manifests, yearly or at once after a suspected leak, while keeping old keys for old archives, and back up the result. |
| Audit trail | Extend audit retention | keep Exponential's audit archives longer than the shipped 730 days when your records schedule requires it, per channel, with an archive directory on write-once storage, and check the result. |
| Privacy requests | Answer an access request for mail preferences | give a person their e-mail preferences and full consent history from Exponential as JSON or CSV, from the administration or the console, check the file and hand it over safely. |
| Privacy requests | Export audit records about a person | for an access request, export every audit record made by or about one user (pseudonymized ones included) with exp:audit export --subject-user, review it for other people's data, and hand it over. |
| Privacy requests | Erase a user account | remove a user account for good after an erasure decision, knowing that users never go to the trash, that removal erases the account's mail preferences and anonymizes its consent log, and what to remove by hand before and after. |
| Privacy requests | Erase mail data for an address | erase the mail preferences and pending confirmations of an e-mail address and anonymize its consent log with exp:mail:preferences erase, for subscribers without an account, and decide whether to add a legal suppression entry. |
| Privacy requests | Stop all optional mail to an address | honor a "stop writing to me" request in Exponential with a suppression list entry (reason legal), which blocks every optional mail and confirmation to that address while storing only a hash, and check it. |
| Privacy requests | Set the sender details in the mail footer | fill in the organization name, postal address and privacy notice link that Exponential's mail gate adds to every optional mail (they ship empty), and check them on the status page and in a test mail. |
| Privacy requests | Export and remove form submissions | the periodic retention routine for web form submissions in Exponential: export what must be kept to your case or records system as CSV, then remove the collections on Setup > Collected information, and delete the export files. |
| Privacy requests | Reset search statistics | check which siteaccesses record search phrases, use the figures, and remove all recorded phrases with Reset statistics on Setup > Search statistics, because phrases can contain names and case numbers. |
| Logs and operations hygiene | Set log retention | give Exponential's kernel logs an age limit with MaxAgeDays per log (404, security and CSP have one already), schedule pruning with the logs cronjob part, and check with a dry run. |
| Logs and operations hygiene | Review the security log | the weekly read of Exponential's security.log in Setup > Log files - what the request classifier records, which lines need a closer look (injection or traversal with status 200 or 500), and what to do about them. |
| Logs and operations hygiene | Restrict debug output | make sure Exponential's debug output is off in production, and when a live problem needs it, switch it on for your own address only, then remove it again and check that nothing is shown to visitors. |
| Logs and operations hygiene | Lock settings with ManagedByDeployment | switch on ManagedByDeployment for the production administration siteaccess so the web interface cannot change settings, templates, extensions or packages, after moving those settings into version control, and check the lock. |
| Logs and operations hygiene | Run the file consistency check | compare every file of the installation with the release's checksum list in Setup > Upgrade check or on the command line, read the findings, and file the result after updates and incidents. |
| Logs and operations hygiene | Add a security.txt file | publish /.well-known/security.txt (RFC 9116) for your site, which Exponential does not ship, add the one rewrite rule the shipped Apache rules need to serve it, and check it with curl. |
| Logs and operations hygiene | Check that form tokens are active | confirm that the ezformtoken extension protecting every Exponential form against cross-site request forgery is active on all siteaccesses, and what to do if it is missing. |
| Logs and operations hygiene | List known vulnerabilities with composer audit | check the Composer dependencies locked for your Exponential installation against known vulnerability advisories with composer audit and see newer releases with composer outdated, because the project's CI runs no dependency scan, and file the result. |
| Accessibility | Check alternative text across images | find images without alternative text on a public site: with the optional Exponential Intelligence report "Missing alt text" where that extension is active, or with an accessibility checker on page samples where it is not, then fix them in drafts. |
| Accessibility | Require alternative text on an image field | switch on the class attribute option "Alternative text is required" (Exponential 6.0.15 and later) for the image fields editors use, so an image cannot be stored without alternative text, and check it in the edit form. |
| Accessibility | Run an accessibility spot check of a page | a 15-minute accessibility check of one public page (automated check with an axe-based browser tool, keyboard pass, zoom, a quick screen reader pass, content review), and how to record and route findings to template or content owners. |
| Accessibility | Publish an accessibility statement page | publish your accessibility statement as a page of your Exponential site (no template ships), with a stable address such as /accessibility, a link in every footer, a feedback route, and versions kept for the record. |
| Accessibility | Keep editors on the admin4 design | make admin4, the administration design Exponential tests against WCAG 2.2 AA, the design of the administration siteaccess, and limit the per-session design switch so staff with disabilities stay in the tested environment. |
| Records | Archive last year's notices | at the start of a year, move last year's notices into a year folder under an archive, so current lists stay short while the old notices keep their content, versions and redirecting addresses, and record what you did. |
| Records | Restore an archived page | bring a page back from the archive to the current site in Exponential, whichever way it was archived (moved to an archive folder, hidden, set to an archived state, or put into an archive section), and check that visitors see it. |
| Records | Restore an item from the trash | find a removed page in Exponential's trash by who trashed it and when, restore it to its original place (or choose another when the parent is gone), and check what the audit recorded. |
| Records | Bring back an earlier version of a page | restore the earlier wording of a page from Exponential's versions page by comparing versions and making a new draft from the old one, then publishing it, so the history keeps both the mistake and the correction. |
| Records | Keep trash items for 90 days | empty Exponential's trash on a schedule while keeping each item for a set number of days, with content.ini [TrashSettings] KeepItemsForDays and the trashpurge cronjob part (in no part by default), and check with the command line. |
| Records | Hide notices automatically on a date | let editors give each notice a hide date and have Exponential's hide.php cronjob hide it when the date has passed, by adding a date attribute to the class and configuring content.ini [HideSettings]. |
| Records | Raise the version limit for notices | keep more versions of official notices than Exponential's default 45 per object by setting VersionHistoryClass for that class, so earlier published wordings are not removed when new versions are published. |
Related pages
- Governments: start here and the tasks index (Tasks)
- Accessibility for public bodies, Security for public bodies, Privacy for public bodies, Records and archiving
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.