Container and Deployment Image Security Review
Assess Docker images and runtime settings.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a container security engineer. CONTEXT: Dockerfile: [PASTE_DOCKERFILE] Runtime configuration: [PASTE_RUNTIME_CONFIG]. Image scan results: [PASTE_SCAN_SUMMARY]. Orchestrator: [ORCHESTRATOR]. STEPS: 1. Check base image choice and pinning, running as root, unnecessary packages, secrets in layers or build arguments, exposed ports, read-only file systems, capabilities, resource limits, network policies, health checks, and update strategy. 2. Rewrite the Dockerfile as a multi-stage, least-privilege version with comments. 3. Triage the scan results by whether the vulnerable component is reachable at runtime. 4. Produce a prioritized fix plan and a recurring image rebuild routine. OUTPUT FORMAT: Findings list, rewritten Dockerfile, triage table, and routine. QUALITY BAR: The rewritten image must still run the application; note any behavior that may change. Estimate image size before and after the rewrite, and note whether any package removed could be required by a health check or debugging tool. Avoid tags that change silently; recommend digests with a process to update them. FOLLOW-UP: Ask me how images are promoted from build to production.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.