Hosting with us is first and foremost clear runtime in Sweden together with Cygrids. That makes it easier to reason about physical placement, operational responsibility, backup, patching and networking. If you connect third-party APIs, support tools, email or AI services outside the EU/EEA, they often carry a separate legal and technical risk picture on top of the hosting layer—especially for personal data where regulators expect you to demonstrate control (including third-country scenarios after Schrems II).
In practice “compliance for hosting” usually breaks down into: data map (what is personal data vs ops logs), access & keys (who, when, why), traceability (changes, incidents, restore) and sub-processor chain (DPA, SCC, region choice). In the quote we can separate: Cygrids/IWAB hosting, your apps, and surrounding flows that touch personal data.
Firewalls and network segmentation are part of platform protection: minimal surface, controlled ingress, and a clear boundary between your content and surrounding traffic. Certified management systems (e.g. ISO-related programmes where applicable) are documented in the operator’s own statement; scope and content at Cygrids follow their published materials—ask for current written evidence in procurement when paper proof is required; we align it with your hosting scope.
SOC 2 often comes up in cloud and platform conversations. What matters is that the SOC report primarily describes designed controls at a vendor; it does not replace GDPR, registers and real operational maturity in your process.
Some sectors add cyber resilience via NIS2 and industry rules. That shapes how hard you log, how you segment and how you respond to regulator and customer scrutiny—same as sizing your quote, not a table here.
Read more: NIS2 Directive (2022/2555) in EUR-Lex · IWAB: blog · privacy
Sources worth reading in order (EU + practice)