1. Red
  2. Learn
  3. Compliance

Compliance guides for small sites: every article

Plain guidance for site owners and small vendors on the Cyber Resilience Act, PCI DSS scripts, ASV scans, SOC 2, insurers and customer questionnaires.

Compliance questions usually arrive as a deadline or a request: a regulator's date, a card-scheme rule, a customer questionnaire or an insurer at renewal. Each one asks for dated evidence about your website or product, and none of them is answered by a vague yes. This page lists the rules that moved recently and points you to the guide that fits your situation.

What matters right now

  • The EU Cyber Resilience Act reporting duty has applied since 11 September 2026. Makers of in-scope products must report actively exploited vulnerabilities, and the full product requirements start on 11 December 2027, per the Commission Q&A on the transition.
  • Reports go through ENISA's Single Reporting Platform: an early warning within 24 hours of becoming aware, a notification within 72 hours, then a final report, as set out in the SRP FAQ.
  • PCI DSS 4.0 was retired on 31 December 2024, and its future-dated requirements, including 6.4.3 and 11.6.1 for payment page scripts, took effect on 31 March 2025, according to the PCI SSC announcement.
  • For SAQ A merchants, PCI SSC FAQ 1588 says the script criterion applies to embedded iframe checkouts, and gives two ways to show you meet it.
  • A scan is not a penetration test in PCI terms. The council's penetration testing guidance defines the difference, and your assessor decides what counts for you.

Where to start

  • If you sell a plugin, theme or app in the EU, start with whether the CRA applies to you.
  • If you already know it applies, read what a small vendor files within 24 hours.
  • If you take cards through a hosted checkout, check how 6.4.3 and 11.6.1 apply to small stores.
  • If you embed a payment iframe or redirect to one, read the SAQ A script criterion explained.
  • If an ASV scan failed on a version string, see how to dispute a backport false positive.
  • If an auditor mentioned SOC 2 or PCI testing, read what is actually required before you buy anything.
  • If a customer wants a pentest document, see attestation, summary or full report.
  • If a questionnaire asks about a pentest you have not had, use this answering guide.
  • If an insurer is asking, see what to show at renewal.

The free scan on red.run.cloud gives you a dated record of what your site serves from outside, which is useful evidence to attach to any of these.

Every compliance guide

1 article, newest update first. Each one is dated and points at its primary sources.

Check your own site

The free scan reads the stack your site serves and matches each version to known vulnerabilities. Updated 4 November 2026.

Other topics