Image scanning looks for known vulnerabilities, malware, embedded secrets, and policy violations before deployment, so teams can prevent unsafe artifacts from reaching production. Runtime monitoring observes active container behavior after launch, including file access, network connections, and resource use. Together they cover both preventive control and real-time detection across the container lifecycle.
Why image scanning and runtime monitoring answer different GDPR questions
Image scanning is a pre-deployment control. It checks the container artifact for known vulnerabilities, malware, embedded secrets, and policy violations before the image is promoted, which helps prevent unsafe software and sensitive data from entering environments that process personal data. Runtime monitoring is a post-launch control. It watches what the container actually does once it is running, so teams can see suspicious access patterns, unexpected network paths, or abnormal resource use.
For GDPR compliance, that split matters because compliance is not only about having secure code, but about maintaining appropriate technical and organisational measures across the full processing lifecycle. A clean scan does not prove a workload stays safe after release, and runtime visibility cannot compensate for a poorly built image that already carries risk into production.
What image scanning can prove, and what it cannot
Image scanning is strongest at finding issues that are already present in the packaged artifact. That makes it useful for catching vulnerable packages, default credentials, exposed tokens, stale dependencies, and configuration drift before deployment. It also supports release gates, because teams can stop an image that should not handle EU personal data from ever reaching a live environment.
It cannot, however, tell you how the container will behave under real traffic, whether it will access a database it should not touch, or whether a compromised process inside the container will begin exfiltrating data after startup. For GDPR, that means scanning is necessary for prevention, but it is not sufficient evidence that processing remains controlled after launch.
How runtime monitoring complements GDPR controls in production
Runtime monitoring focuses on observed behaviour. In a container estate, that means watching file activity, outbound connections, process execution, privilege changes, and resource spikes that may indicate misuse, compromise, or unintended data movement. When personal data is involved, this layer helps validate that the deployed workload is behaving within the bounds expected by policy and architecture.
It is especially valuable when teams use ephemeral containers, rapid deployments, or inherited base images, because risk can appear after build time through injected configuration, abused service dependencies, or runtime exploitation. NIST SP 800-190 Container Security is useful here because it treats container images, registries, orchestrators, runtimes, and hosts as distinct control surfaces that all need attention.
What changes when the workload processes personal data
When a container handles personal data, the operational question changes from “is this image clean?” to “can we show this workload is continuously constrained, observed, and recoverable if it misbehaves?” That is why the GDPR angle is broader than vulnerability management. Teams need evidence that the deployment follows data minimisation, access limitation, logging, and monitoring appropriate to the sensitivity of the data being processed.
Image scanning supports the build stage of that story, while runtime monitoring supports the live stage. Both become part of the evidence chain for due care, but neither should be treated as a standalone GDPR answer. The right control choice depends on whether the risk is pre-release contamination, post-release compromise, or both. For a broader compliance lens, the EU General Data Protection Regulation remains the primary reference for security of processing, and the CIS Controls v8 help translate that requirement into operational safeguards such as secure configuration, logging, and vulnerability management.
Risk and Threat Considerations
Container GDPR exposure usually comes from control gaps between build time and runtime. A clean image can still become risky if secrets are injected later, if the workload is granted broader network reach than intended, or if a compromised process can read or transmit personal data without detection. The opposite is also true: strong runtime tooling will not fix an image that already contains leaked credentials or known vulnerable components.
Failure mechanism: Organisations over-trust the artifact scan, then miss behaviour introduced after startup, such as unexpected outbound traffic, unauthorized file reads, or privilege escalation inside the container.
Impact: Personal data can be exposed, exfiltrated, or altered without timely detection, which increases breach risk and weakens the organisation’s ability to show appropriate processing safeguards.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | SI-2 — Flaw Remediation | Container scanning directly addresses known vulnerabilities before deployment. |
| SI-3 — Malicious Code Protection | Image scanning checks artifacts for malware and embedded threats before launch. | |
| AU-12 — Audit Record Generation | Runtime monitoring depends on logs and telemetry from active containers. | |
| Recommendation — Scan container images for known flaws and block release until remediation is complete. Inspect container images for malicious code and quarantine unsafe builds. Generate container audit records for file, network, and process activity. | ||
| ISO/IEC 27001:2022 | A.8.8 — Management of technical vulnerabilities | Image scanning is a technical vulnerability control for container artifacts. |
| Recommendation — Identify and remediate container vulnerabilities before promotion to production. | ||
Practitioner Guidance
What to prioritise: Use image scanning as a deployment gate, but pair it with runtime alerts that focus on data-access paths, egress destinations, and abnormal process behaviour. The useful question is not whether the container is running, but whether its live behaviour matches the sensitivity and purpose of the data it processes.
What to verify: Confirm that scan results are tied to the exact image digest promoted to production, and that runtime telemetry is sufficient to reconstruct who accessed what, when, and from where if a personal-data incident is suspected. If you cannot correlate build-time findings with live workload behaviour, your control picture is incomplete.
Practitioner takeaway: For GDPR, image scanning reduces the chance of deploying a bad container, but runtime monitoring is what helps prove the workload stayed within acceptable bounds after deployment.
Related resources from NHI Mgmt Group
- Guide: GDPR Compliance Guide for Security Teams
- Scanning
- Should teams rely on image scanning or runtime monitoring for container security?
- What breaks when image scanning, runtime enforcement, and application monitoring stay in separate workflows?
- What breaks when container image vulnerability scanning is not integrated with monitoring and alerting?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org