Cyber Insurance: Which Maintenance Records Count
Insurers scrutinise more closely: which patch reports, restore logs and MFA evidence prove the pledges from the risk questionnaire at the time of loss.
This is page 5 of the posts from our blog. The newer posts are on the pages before.
Each post explains one topic. Below the title there is a short text about it. Click on a post. Then you can read the whole text.
The posts are on more than one page. Below the list you can choose another page.
Insurers scrutinise more closely: which patch reports, restore logs and MFA evidence prove the pledges from the risk questionnaire at the time of loss.
Mini Shai-Hulud arrived via patch versions: 1,055 versions, 502 packages, no CVE. How to secure lockfiles, install scripts, registry mirrors and tokens.
The DENIC outage of 5 May 2026 showed: a shop can be unreachable while everything runs. Maintain the DNSSEC chain, domain locks and resolver-aware monitoring.
Shop updates without revenue loss: a low-traffic maintenance window, an SEO-safe HTTP 503 mode, cache warmup and a rollback plan with Git tag and DB dump.
Security headers like CSP and HSTS are not a one-time setup. Introduce them in report-only mode, harden to enforce and keep them stable across updates.
NIS2 requires patch, backup and access management, MFA, incident reporting and supply chain security - how an SLA contract turns the duties into practice.
Bulk-sender rules from Google, Yahoo and Microsoft: SPF, DKIM and DMARC decide the delivery of shop mails - and how to raise DMARC safely to p=reject.
Web skimming steals card data right in the browser. See how a script inventory, Subresource Integrity, CSP and tamper detection per PCI DSS 4.0 stop the attack.
Since 28 June 2025 the EAA/BFSG applies to shops. Why WCAG 2.2 AA conformance decays with each update and how recurring maintenance checks keep it intact.