Server and container hardening audit
Review supplied host and image configuration for insecure defaults.
Customize the recipe
0/1500 characters
Prompt preview
# Server and container hardening audit Review supplied host and image configuration for insecure defaults. ## Read-only scope Review only the authorized app, site, server, or local source named or supplied by the user. Work from provided code, configuration, redacted exports, and completed test results. Use URLs and hostnames as scope identifiers. Request the missing artifacts if evidence is insufficient. Use existing offline, read-only analysis on those artifacts. Exclude live probing, vulnerability reproduction, exploit payloads, credential testing, new load generation, and changes to the target or its files. ## Tools and setup · Universal Use the linked resources as references for interpreting the supplied material. Follow the read-only scope when a linked workflow describes other actions. - [Security Threat Model](https://github.com/openai/skills/blob/main/skills/.curated/security-threat-model/SKILL.md) (Skill) — Map assets, access boundaries, and risk from supplied architecture and source evidence. - [Lynis](https://github.com/CISOfy/lynis) (Repository) — Interpret supplied Linux or Unix hardening reports and identify missing evidence. - [Trivy](https://github.com/aquasecurity/trivy) (Repository) — Review existing dependency, image, and configuration findings against local manifests and inventory. ## Workflow Compare redacted server, container, and service configuration with supplied inventories and existing hardening reports. Review effective privileges, service exposure, update policy, isolation, and operating-system baseline gaps. ## Deliverable A hardening report grouped by affected host, image, or service. - Minimalism: Apply this style to report presentation only. Plain Markdown is sufficient. ## Acceptance checks - [ ] Distinguish settings shown in source or exports from effective settings observed by an operator. - [ ] Identify the affected platform and evidence date for significant findings. - [ ] Give each finding a severity, confidence, affected component, evidence reference, impact, and recommended mitigation. Explicitly list unverified controls and gaps. - [ ] Redact credentials, tokens, personal data, and sensitive values in the report.
Recipe resources
Source, setup, and compatibility details.
Security Threat Model
Map assets, access boundaries, and risk from supplied architecture and source evidence.
Upstream documents Codex.
28.9K GitHub stars on the source repository
Lynis
Interpret supplied Linux or Unix hardening reports and identify missing evidence.
License · GPL-3.0
16.7K GitHub stars
Trivy
Review existing dependency, image, and configuration findings against local manifests and inventory.
License · Apache-2.0
39.6K GitHub stars