Dragon Compliance - CRA & NIS2 Compliance, SBOM Export & Vulnerability Scanner
| 开发者 | dragoncoreltd |
|---|---|
| 更新时间 | 2026年9月13日 09:03 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
The EU Cyber Resilience Act (CRA) and NIS2 directive expect businesses to know
what software they run, monitor it for known vulnerabilities, patch without
delay - and to be able to prove all of that. Dragon Compliance is the
WordPress compliance plugin that turns your site into something you can hand
to an auditor:
- Software inventory - WordPress core, every plugin and theme with version, author and license, plus the PHP/database/server environment.
- SBOM export - download a standards-compliant CycloneDX 1.6 JSON Software Bill of Materials, the artifact auditors and enterprise customers ask for.
- Vulnerability monitoring - a daily scan matches your inventory against the Wordfence Intelligence vulnerability database and lists affected components by severity. New critical findings can email the site admin.
- CRA readiness checklist - automatic checks (HTTPS, auto-updates coverage, debug mode, file editing, 2FA, default admin account, open criticals) plus manual attestations for process facts like your update policy and backups, with a completion score.
- Evidence log - every scan, detection, resolution and attestation change is recorded with a timestamp, building the audit trail regulators expect.
- White-label scheduled compliance reports
- SBOM snapshots with diffs, and SPDX 2.3 export
- Tamper-evident hash-chained evidence log
- Time-to-patch metrics
- Alert routing: multiple recipients, signed webhooks, Slack
- NIS2 mapping view
安装:
- Upload the plugin files to
/wp-content/plugins/dragon-compliance, or install through the WordPress plugins screen. - Activate the plugin through the 'Plugins' screen.
- Go to Tools → Compliance.
- (Optional, for vulnerability monitoring) Create a free wordfence.com account, generate an API token under Dashboard → Integrations, and paste it under Tools → Compliance → Settings.
屏幕截图:
常见问题:
Does the CRA apply to my site?
If your WordPress site is part of a commercial digital product or service offered in the EU, parts of the CRA and NIS2 likely apply to your business. This plugin gives you the technical evidence base - it is not legal advice.
Where does the vulnerability data come from?
From the Wordfence Intelligence Community Edition database, matched locally against your installed versions. Your inventory never leaves your server.
What SBOM formats are supported?
CycloneDX 1.6 JSON in the free plugin. Dragon Compliance Pro adds SPDX 2.3 and automatic SBOM snapshots with diffs.
What is an SBOM, and why would I need one?
A Software Bill of Materials lists every software component you run, with versions and licenses - like an ingredients label for your site. Auditors, enterprise customers and EU regulation increasingly ask for one. This plugin exports yours in the standard CycloneDX format in one click.
When do the CRA obligations start?
The Cyber Resilience Act's vulnerability and incident reporting obligations begin in September 2026, with the remaining requirements following in 2027. If the CRA touches your business, the evidence trail is worth starting now - findings and attestations only prove a history if they have one.
Will it slow down my site?
No. Scans run in the background once a day via WP-Cron, there is no front-end code at all, and the vulnerability match happens locally against a cached copy of the database.
Is this a malware scanner?
No. It matches your installed software versions against a database of publicly known vulnerabilities. It does not scan files for infections.
更新日志:
1.0.9
- An "Upgrade to Pro" link on the Plugins screen, a one-line pointer at the foot of the plugin's own screens, and a single dismissible note once the plugin has done its job. All three disappear when the Pro add-on is active; nothing in the free plugin is locked or changed.
- Fixed: an attestation whose database write failed was still logged as evidence and reported as saved. All four attestations are now stored in a single write that is read back before any evidence is recorded, evidence is recorded only for items that actually changed, and a refused write shows an error instead of "Attestations saved".
- Fixed: ignoring or reopening a finding recorded a status-change evidence entry even when the row did not change. Evidence is now recorded only when the status actually changed, and a no-op or failed update shows a notice instead of "Finding updated".
- Fixed: a scan whose "mark resolved" write failed still recorded resolution evidence and fired the resolved hook for every finding. Resolutions that were not stored are no longer reported, and the next scan retries them.
- Fixed: the database schema version was stamped even when a table could not be created, which stopped the plugin from retrying. Each table is now checked to exist before the version is recorded; a failure is retried every 10 minutes and shown to administrators as a notice naming the missing tables.
- Asks for a WordPress.org review once, only on the Compliance screen and only after a vulnerability scan has completed or an SBOM has been exported. "Maybe later" snoozes it for a month and "No thanks" is permanent.
- New
dragoncompliance_sbom_exportedaction fires when an SBOM download is generated. - Listing title, description and tags now say what the plugin does, so it is easier to find in the plugin directory.
- New: the vulnerability feed source can now be supplied by Dragon Compliance Pro, which downloads it from Dragon Core so licensed sites need no Wordfence account. The free plugin only accepts www.wordfence.com or api.dragoncore.ltd as a source - any other host is ignored.
- Improvement: the dashboard and Findings screens now say when monitoring is configured but no vulnerability data has been downloaded yet, and show why the last download failed, instead of looking healthy with nothing checked.
- Hardening: the feed request no longer follows redirects; the Wordfence token is attached to the request after the source is validated and is never exposed to other plugins; an oversized feed record aborts the refresh (keeping the last good data) rather than being read into memory; an empty local index is never revalidated with a conditional request.
- Free users: no change; your Wordfence token keeps working exactly as before.
- Security: the stored Wordfence Intelligence API token now uses authenticated encryption (tamper-detecting), so a modified ciphertext is rejected rather than decrypted.
- New: vulnerability monitoring re-scans immediately when a plugin or theme is installed, updated or removed, instead of waiting for the next daily run - newly added software is checked straight away.
- Expanded the plugin listing: clearer free vs Pro breakdown, fuller FAQ, and a live-preview blueprint.
- Added screenshots of every screen to the plugin listing.
- Compatibility: tested up to WordPress 7.1.
- Housekeeping: corrected the contributor name in the plugin readme.
- Performance: new database index keeps evidence sealing fast as the log grows.
- New: "Delete data on uninstall" checkbox in settings.
- Polish: helpful empty states on the Inventory and Evidence screens; accessibility improvements.
- Initial release: inventory, CycloneDX 1.6 SBOM export, daily vulnerability monitoring via Wordfence Intelligence, CRA readiness checklist with attestations, evidence log, critical-finding email alert.