Securing the AI Transformation at HelloFresh.

Stated assumptions backing this stack-rank

1. HelloFresh's AI exposure is currently dominated by SaaS LLM consumption (Claude, Gemini, ChatGPT) and Bedrock-hosted models, not in-house model training. The control set is weighted accordingly toward deployer obligations, not provider obligations under the EU AI Act.
2. HelloFresh, as a B2C company processing customer PII across DACH, NA, UK, and AU, treats GDPR and EU AI Act as binding; PCI DSS is in-scope only for payment-adjacent flows. NIS2 applies through the food/distribution-essential-services vertical.
3. Effort estimates assume the existing AppSec/IAM/DLP/SIEM stack and a security tribe of ~34 engineers is the baseline; estimates are FTE-weeks of net new work, not absolute hours.
4. "Residual risk" assumes the listed mitigation set is fully implemented and operating; it does not assume every commercial alternative is purchased — the named tools are reference architectures, not endorsements.
5. The stack-rank is a prerequisite ordering, not a strict severity ordering. #1 (governance) is highest priority because everything else depends on it; #10 (red-teaming) is critical-severity but can only validate controls #1–#9.
6. Hodor.ai is positioned as the agent identity-policy-audit reference for #5; based on its own product page (identity, policy, guardrails, audit trail for AI agents). Other named vendors are positioned to their public capability claims as of May 2026 — confirm via PoC, not marketing.
7. Risk ratings use a 5×5 probability × impact model with a complexity-of-exploitation modifier; complexity is treated as a probability discount, not a separate axis, to keep the heatmap two-dimensional.