Who Changed It/Compliance
When WordPress falls inside an audit scope, the auditor asks the same question in four dialects: who can change this system, what did they change, and how do you know the record is intact? This page maps each framework's logging controls to what the plugin covers, and to what it leaves for the server and the people.
No plugin brings a site into compliance with anything. Frameworks certify an organisation's controls, and a control is a policy, a person who owns it, and evidence that it runs. Who Changed It supplies the third: an application-layer record of administrative activity that is hard to alter quietly and easy to hand over. Every table below has a third column for a reason.
One boundary applies throughout. The plugin sees what passes through WordPress. Web server access logs, database audit logs, operating-system logs, firewall and WAF logs, and file integrity monitoring are separate layers, and every framework here expects them.
| Control | What the plugin contributes | Still needed elsewhere |
|---|---|---|
| A.8.15 Logging | Produces logs of sign-ins, account and role changes, content, plugin, theme, core and settings changes. Protects them with a hash chain and a separate read capability. | Server, database and network logs. Central storage away from the web server. |
| A.8.16 Monitoring activities | Classifies every event and escalates on context: odd hours, an address new to that user, bursts of failed logins or deletions. Alerts by email, Slack, Discord or Telegram. | Monitoring of traffic, resources and the host. Someone assigned to respond. |
| A.8.17 Clock synchronisation | Timestamps are stored in UTC. | NTP on the server. The plugin trusts the system clock. |
| A.5.28 Collection of evidence | Signed CSV or JSON export with a manifest: filters, time bounds, record count, chain state at export. | A procedure for who exports, when, and where the file is kept. |
| A.8.32 Change management | Records that a change happened, who made it and the old and new values. | Approval and testing. The log shows a change was made, not that it was authorised. |
| A.5.18 Access rights | Records account creation, deletion and role changes, which is the evidence an access review needs. | The review itself. |
| A.5.34 Privacy and protection of PII | IP anonymisation, retention per event family, redaction for erasure requests. See the GDPR page. | Lawful basis and notices. |
SOC 2 examines a service organisation's system. A WordPress site is in scope when it is part of that system, for example a customer portal or documentation site with accounts, and usually out of scope when it is a brochure site. Settle that with your auditor before collecting evidence.
| Criterion | What the plugin contributes | Still needed elsewhere |
|---|---|---|
| CC6.2, CC6.3 Access provisioning and modification | A dated record of every account created or deleted and every role change, with who did it. | The approval ticket each change should trace back to. |
| CC7.2 Monitoring for anomalies | Severity classification with a written reason on each escalated event, and immediate alerts. | Infrastructure monitoring. The plugin watches WordPress, not the stack under it. |
| CC7.3 Evaluating security events | A daily or weekly digest listing every flagged event, sent even when nothing happened. | Evidence that somebody read it and what they decided. |
| CC7.4 Incident response | A filtered, signed export of the incident window as a timeline. | The response plan and the communication. |
| CC8.1 Change management | Plugin, theme and core installs, updates and removals, plus settings changes, each attributed. | Authorisation, testing and separation of duties. |
The NIS2 Directive applies to essential and important entities through each member state's own law, so the details depend on where you are established. Two parts concern logging. Article 21 requires risk-management measures that include incident handling. Article 23 sets reporting deadlines for significant incidents: an early warning within 24 hours of becoming aware, an incident notification within 72 hours, and a final report within one month.
Those deadlines are where a log earns its place. An early warning needs to say whether the incident looks malicious, and the 72-hour notification needs an initial assessment of severity and impact. With an intact record you can answer from the log instead of from reconstruction: which account, from which address, what it changed, and when. The evidence preservation guide covers what to capture in the first hour.
What NIS2 expects beyond this is broad: supply-chain security, business continuity, vulnerability handling, training. A WordPress plugin touches none of it.
For WooCommerce merchants. Which requirements apply to you depends on how you take payments and therefore which self-assessment questionnaire you complete; a store that sends shoppers to a hosted payment page has a far smaller scope than one that handles card data. Ask your acquirer or assessor. Where Requirement 10 does apply to the WordPress application, this is the honest map:
| Requirement | What the plugin contributes | Gap |
|---|---|---|
| 10.2.1.2 Actions by administrators | 57 event types covering accounts, roles, directly granted capabilities, application passwords, plugins, themes, core, watched settings, content, and WooCommerce prices, coupons, orders, refunds and gateway settings. | Not every admin action. Menus, widgets, comments and unwatched options are not recorded. |
| 10.2.1.4 Invalid access attempts | Failed logins with the username tried and the source address. | None at the WordPress layer. |
| 10.2.1.5 Changes to credentials and privileges | Account creation and deletion, role changes, password resets. | None at the WordPress layer. |
| 10.2.2 Detail in each entry | User, event type, UTC time, source IP and the object affected. | Failure is recorded as its own event type, not as a success flag on every row. |
| 10.3.1 Read access to logs | A dedicated capability; administrators can be excluded. | Database-level access is outside the plugin's control. |
| 10.3.2 Protection from modification | Hash chain detects edits and deletions. Purges and the plugin's own settings changes are logged and cannot be muted. | Detection, not prevention. Rows can still be changed by someone with database access. |
| 10.3.3 Backup to a central log server | An action hook fires on every event for forwarding. | Not built in. You need a few lines of code or a SIEM agent. |
| 10.4.1 Daily review | Immediate alerts and a daily digest. | A named reviewer and a record of the review. |
| 10.5.1 Twelve months of history | Retention is configurable per family, up to keeping everything. | The default is three months. Raise it before you rely on it. |
| 10.6 Time synchronisation | UTC timestamps. | NTP on the server. |
Payment gateway configuration changes are classified dangerous on sight and alert immediately, because redirecting payments is how a compromised store is monetised. Gateway keys and secrets are never written to the log.
If you need those layers assessed or built, that is consulting work, and it is what the plugin's author does at WP Server Guard. The plugin is free and does not depend on it.