[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73C09YSMBC6EB81F7CT5DNG":3,"skill-same:01M73C09YSMBC6EB81F7CT5DNG":106},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M73C09YSMBC6EB81F7CT5DNG","hardening-docker-containers-for-production",null,"Hardening Docker containers for production involves applying security best practices aligned with CIS Docker Benchmark v1.8.0 to minimize attack surface, prevent privilege escalation, and enforce leas","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhardening-docker-containers-for-production\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhardening-docker-containers-for-production\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: hardening-docker-containers-for-production\ndescription: Hardening Docker containers for production involves applying security\n  best practices aligned with CIS Docker Benchmark v1.8.0 to minimize attack surface,\n  prevent privilege escalation, and enforce leas\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- containers\n- docker\n- security\n- hardening\n- CIS-benchmark\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.IR-01\n- ID.AM-08\n- DE.CM-01\nmitre_attack:\n- T1610\n- T1611\n- T1609\n- T1525\n- T1068\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\n---\n# Hardening Docker Containers for Production\n\n## Overview\n\nHardening Docker containers for production involves applying security best practices aligned with CIS Docker Benchmark v1.8.0 to minimize attack surface, prevent privilege escalation, and enforce least-privilege principles across Docker daemon, images, containers, and runtime configurations.\n\n\n## When to Use\n\n- When deploying or configuring hardening docker containers for production capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Docker Engine 24.0+ installed\n- Docker Compose v2\n- Linux host with kernel 5.10+\n- Root or sudo access on Docker host\n- docker-bench-security tool\n- Hadolint for Dockerfile linting\n- Dockle for image linting\n\n## Core Concepts\n\n### CIS Docker Benchmark Sections\n\n1. **Host Configuration** - Audit Docker daemon files, restrict access to \u002Fvar\u002Frun\u002Fdocker.sock\n2. **Docker Daemon Configuration** - Enable TLS, restrict inter-container communication, configure logging\n3. **Docker Daemon Configuration Files** - Set ownership and permissions on daemon.json\n4. **Container Images and Build File** - Use trusted base images, scan for vulnerabilities, multi-stage builds\n5. **Container Runtime** - Drop capabilities, read-only rootfs, restrict syscalls\n6. **Docker Security Operations** - Monitor, audit, and rotate credentials\n\n### Key Hardening Principles\n\n- **Least Privilege**: Run containers as non-root, drop all capabilities except required\n- **Immutability**: Use read-only root filesystem, tmpfs for writable directories\n- **Minimalism**: Use distroless or Alpine base images, multi-stage builds\n- **Isolation**: Apply seccomp profiles, AppArmor\u002FSELinux, namespace restrictions\n- **Auditability**: Enable content trust, log all container activity\n\n## Workflow\n\n### Step 1: Harden the Dockerfile\n\n```dockerfile\n# Use specific digest for reproducibility\nFROM python:3.12-slim@sha256:abc123... AS builder\n\nWORKDIR \u002Fapp\nCOPY requirements.txt .\nRUN pip install --no-cache-dir --user -r requirements.txt\n\n# Production stage - minimal image\nFROM gcr.io\u002Fdistroless\u002Fpython3-debian12\n\n# Copy only necessary artifacts\nCOPY --from=builder \u002Froot\u002F.local \u002Froot\u002F.local\nCOPY --from=builder \u002Fapp \u002Fapp\n\nWORKDIR \u002Fapp\n\n# Create non-root user\nUSER 65534:65534\n\n# Set read-only filesystem expectation\nLABEL org.opencontainers.image.source=\"https:\u002F\u002Fgithub.com\u002Forg\u002Fapp\"\n\nENTRYPOINT [\"python\", \"app.py\"]\n```\n\n### Step 2: Harden Docker Daemon Configuration\n\n```json\n{\n  \"icc\": false,\n  \"log-driver\": \"json-file\",\n  \"log-opts\": {\n    \"max-size\": \"10m\",\n    \"max-file\": \"3\"\n  },\n  \"live-restore\": true,\n  \"userland-proxy\": false,\n  \"no-new-privileges\": true,\n  \"default-ulimits\": {\n    \"nofile\": {\n      \"Name\": \"nofile\",\n      \"Hard\": 64000,\n      \"Soft\": 64000\n    },\n    \"nproc\": {\n      \"Name\": \"nproc\",\n      \"Hard\": 1024,\n      \"Soft\": 1024\n    }\n  },\n  \"seccomp-profile\": \"\u002Fetc\u002Fdocker\u002Fseccomp-default.json\",\n  \"tls\": true,\n  \"tlscacert\": \"\u002Fetc\u002Fdocker\u002Ftls\u002Fca.pem\",\n  \"tlscert\": \"\u002Fetc\u002Fdocker\u002Ftls\u002Fserver-cert.pem\",\n  \"tlskey\": \"\u002Fetc\u002Fdocker\u002Ftls\u002Fserver-key.pem\",\n  \"tlsverify\": true\n}\n```\n\n### Step 3: Harden Container Runtime\n\n```bash\ndocker run -d \\\n  --name production-app \\\n  --read-only \\\n  --tmpfs \u002Ftmp:rw,noexec,nosuid,size=100m \\\n  --tmpfs \u002Fvar\u002Frun:rw,noexec,nosuid,size=10m \\\n  --cap-drop ALL \\\n  --cap-add NET_BIND_SERVICE \\\n  --security-opt no-new-privileges:true \\\n  --security-opt seccomp=\u002Fetc\u002Fdocker\u002Fseccomp-default.json \\\n  --security-opt apparmor=docker-default \\\n  --pids-limit 100 \\\n  --memory 512m \\\n  --memory-swap 512m \\\n  --cpus 1.0 \\\n  --user 65534:65534 \\\n  --network custom-bridge \\\n  --restart on-failure:3 \\\n  --health-cmd \"curl -f http:\u002F\u002Flocalhost:8080\u002Fhealth || exit 1\" \\\n  --health-interval 30s \\\n  --health-timeout 10s \\\n  --health-retries 3 \\\n  myapp:latest\n```\n\n### Step 4: Enable Docker Content Trust\n\n```bash\nexport DOCKER_CONTENT_TRUST=1\nexport DOCKER_CONTENT_TRUST_SERVER=https:\u002F\u002Fnotary.example.com\n\n# Sign and push image\ndocker trust sign myregistry.com\u002Fmyapp:v1.0.0\n\n# Verify image signature before pull\ndocker trust inspect --pretty myregistry.com\u002Fmyapp:v1.0.0\n```\n\n### Step 5: Configure Host-Level Auditing\n\n```bash\n# Add audit rules for Docker files and directories\ncat >> \u002Fetc\u002Faudit\u002Frules.d\u002Fdocker.rules \u003C\u003C 'EOF'\n-w \u002Fusr\u002Fbin\u002Fdocker -k docker\n-w \u002Fvar\u002Flib\u002Fdocker -k docker\n-w \u002Fetc\u002Fdocker -k docker\n-w \u002Flib\u002Fsystemd\u002Fsystem\u002Fdocker.service -k docker\n-w \u002Flib\u002Fsystemd\u002Fsystem\u002Fdocker.socket -k docker\n-w \u002Fetc\u002Fdefault\u002Fdocker -k docker\n-w \u002Fetc\u002Fdocker\u002Fdaemon.json -k docker\n-w \u002Fusr\u002Fbin\u002Fcontainerd -k docker\n-w \u002Fusr\u002Fbin\u002Frunc -k docker\nEOF\n\nsystemctl restart auditd\n```\n\n## Validation Commands\n\n```bash\n# Run Docker Bench Security\ndocker run --rm --net host --pid host \\\n  --userns host --cap-add audit_control \\\n  -e DOCKER_CONTENT_TRUST=$DOCKER_CONTENT_TRUST \\\n  -v \u002Fetc:\u002Fetc:ro \\\n  -v \u002Fusr\u002Fbin\u002Fcontainerd:\u002Fusr\u002Fbin\u002Fcontainerd:ro \\\n  -v \u002Fusr\u002Fbin\u002Frunc:\u002Fusr\u002Fbin\u002Frunc:ro \\\n  -v \u002Fusr\u002Flib\u002Fsystemd:\u002Fusr\u002Flib\u002Fsystemd:ro \\\n  -v \u002Fvar\u002Flib:\u002Fvar\u002Flib:ro \\\n  -v \u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock:ro \\\n  docker\u002Fdocker-bench-security\n\n# Lint Dockerfile\nhadolint Dockerfile\n\n# Lint built image\ndockle myapp:latest\n\n# Verify no containers running as root\ndocker ps -q | xargs docker inspect --format '{{.Id}}: User={{.Config.User}}'\n```\n\n## Key Security Controls\n\n| Control | Implementation | CIS Section |\n|---------|---------------|-------------|\n| Non-root user | USER instruction in Dockerfile | 4.1 |\n| Read-only rootfs | --read-only flag | 5.12 |\n| Drop capabilities | --cap-drop ALL | 5.3 |\n| Resource limits | --memory, --cpus, --pids-limit | 5.10 |\n| No new privileges | --security-opt no-new-privileges | 5.25 |\n| Content trust | DOCKER_CONTENT_TRUST=1 | 4.5 |\n| TLS for daemon | daemon.json TLS config | 2.6 |\n| Audit logging | auditd rules | 1.1 |\n\n## References\n\n- [CIS Docker Benchmark](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fdocker)\n- [Docker Security Best Practices](https:\u002F\u002Fdocs.docker.com\u002Fengine\u002Fsecurity\u002F)\n- [Docker Bench Security Tool](https:\u002F\u002Fgithub.com\u002Fdocker\u002Fdocker-bench-security)\n- [Hadolint - Dockerfile Linter](https:\u002F\u002Fgithub.com\u002Fhadolint\u002Fhadolint)\n","# Hardening Docker Containers for Production\n\n## Overview\n\nHardening Docker containers for production involves applying security best practices aligned with CIS Docker Benchmark v1.8.0 to minimize attack surface, prevent privilege escalation, and enforce least-privilege principles across Docker daemon, images, containers, and runtime configurations.\n\n\n## When to Use\n\n- When deploying or configuring hardening docker containers for production capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Docker Engine 24.0+ installed\n- Docker Compose v2\n- Linux host with kernel 5.10+\n- Root or sudo access on Docker host\n- docker-bench-security tool\n- Hadolint for Dockerfile linting\n- Dockle for image linting\n\n## Core Concepts\n\n### CIS Docker Benchmark Sections\n\n1. **Host Configuration** - Audit Docker daemon files, restrict access to \u002Fvar\u002Frun\u002Fdocker.sock\n2. **Docker Daemon Configuration** - Enable TLS, restrict inter-container communication, configure logging\n3. **Docker Daemon Configuration Files** - Set ownership and permissions on daemon.json\n4. **Container Images and Build File** - Use trusted base images, scan for vulnerabilities, multi-stage builds\n5. **Container Runtime** - Drop capabilities, read-only rootfs, restrict syscalls\n6. **Docker Security Operations** - Monitor, audit, and rotate credentials\n\n### Key Hardening Principles\n\n- **Least Privilege**: Run containers as non-root, drop all capabilities except required\n- **Immutability**: Use read-only root filesystem, tmpfs for writable directories\n- **Minimalism**: Use distroless or Alpine base images, multi-stage builds\n- **Isolation**: Apply seccomp profiles, AppArmor\u002FSELinux, namespace restrictions\n- **Auditability**: Enable content trust, log all container activity\n\n## Workflow\n\n### Step 1: Harden the Dockerfile\n\n```dockerfile\n# Use specific digest for reproducibility\nFROM python:3.12-slim@sha256:abc123... AS builder\n\nWORKDIR \u002Fapp\nCOPY requirements.txt .\nRUN pip install --no-cache-dir --user -r requirements.txt\n\n# Production stage - minimal image\nFROM gcr.io\u002Fdistroless\u002Fpython3-debian12\n\n# Copy only necessary artifacts\nCOPY --from=builder \u002Froot\u002F.local \u002Froot\u002F.local\nCOPY --from=builder \u002Fapp \u002Fapp\n\nWORKDIR \u002Fapp\n\n# Create non-root user\nUSER 65534:65534\n\n# Set read-only filesystem expectation\nLABEL org.opencontainers.image.source=\"https:\u002F\u002Fgithub.com\u002Forg\u002Fapp\"\n\nENTRYPOINT [\"python\", \"app.py\"]\n```\n\n### Step 2: Harden Docker Daemon Configuration\n\n```json\n{\n  \"icc\": false,\n  \"log-driver\": \"json-file\",\n  \"log-opts\": {\n    \"max-size\": \"10m\",\n    \"max-file\": \"3\"\n  },\n  \"live-restore\": true,\n  \"userland-proxy\": false,\n  \"no-new-privileges\": true,\n  \"default-ulimits\": {\n    \"nofile\": {\n      \"Name\": \"nofile\",\n      \"Hard\": 64000,\n      \"Soft\": 64000\n    },\n    \"nproc\": {\n      \"Name\": \"nproc\",\n      \"Hard\": 1024,\n      \"Soft\": 1024\n    }\n  },\n  \"seccomp-profile\": \"\u002Fetc\u002Fdocker\u002Fseccomp-default.json\",\n  \"tls\": true,\n  \"tlscacert\": \"\u002Fetc\u002Fdocker\u002Ftls\u002Fca.pem\",\n  \"tlscert\": \"\u002Fetc\u002Fdocker\u002Ftls\u002Fserver-cert.pem\",\n  \"tlskey\": \"\u002Fetc\u002Fdocker\u002Ftls\u002Fserver-key.pem\",\n  \"tlsverify\": true\n}\n```\n\n### Step 3: Harden Container Runtime\n\n```bash\ndocker run -d \\\n  --name production-app \\\n  --read-only \\\n  --tmpfs \u002Ftmp:rw,noexec,nosuid,size=100m \\\n  --tmpfs \u002Fvar\u002Frun:rw,noexec,nosuid,size=10m \\\n  --cap-drop ALL \\\n  --cap-add NET_BIND_SERVICE \\\n  --security-opt no-new-privileges:true \\\n  --security-opt seccomp=\u002Fetc\u002Fdocker\u002Fseccomp-default.json \\\n  --security-opt apparmor=docker-default \\\n  --pids-limit 100 \\\n  --memory 512m \\\n  --memory-swap 512m \\\n  --cpus 1.0 \\\n  --user 65534:65534 \\\n  --network custom-bridge \\\n  --restart on-failure:3 \\\n  --health-cmd \"curl -f http:\u002F\u002Flocalhost:8080\u002Fhealth || exit 1\" \\\n  --health-interval 30s \\\n  --health-timeout 10s \\\n  --health-retries 3 \\\n  myapp:latest\n```\n\n### Step 4: Enable Docker Content Trust\n\n```bash\nexport DOCKER_CONTENT_TRUST=1\nexport DOCKER_CONTENT_TRUST_SERVER=https:\u002F\u002Fnotary.example.com\n\n# Sign and push image\ndocker trust sign myregistry.com\u002Fmyapp:v1.0.0\n\n# Verify image signature before pull\ndocker trust inspect --pretty myregistry.com\u002Fmyapp:v1.0.0\n```\n\n### Step 5: Configure Host-Level Auditing\n\n```bash\n# Add audit rules for Docker files and directories\ncat >> \u002Fetc\u002Faudit\u002Frules.d\u002Fdocker.rules \u003C\u003C 'EOF'\n-w \u002Fusr\u002Fbin\u002Fdocker -k docker\n-w \u002Fvar\u002Flib\u002Fdocker -k docker\n-w \u002Fetc\u002Fdocker -k docker\n-w \u002Flib\u002Fsystemd\u002Fsystem\u002Fdocker.service -k docker\n-w \u002Flib\u002Fsystemd\u002Fsystem\u002Fdocker.socket -k docker\n-w \u002Fetc\u002Fdefault\u002Fdocker -k docker\n-w \u002Fetc\u002Fdocker\u002Fdaemon.json -k docker\n-w \u002Fusr\u002Fbin\u002Fcontainerd -k docker\n-w \u002Fusr\u002Fbin\u002Frunc -k docker\nEOF\n\nsystemctl restart auditd\n```\n\n## Validation Commands\n\n```bash\n# Run Docker Bench Security\ndocker run --rm --net host --pid host \\\n  --userns host --cap-add audit_control \\\n  -e DOCKER_CONTENT_TRUST=$DOCKER_CONTENT_TRUST \\\n  -v \u002Fetc:\u002Fetc:ro \\\n  -v \u002Fusr\u002Fbin\u002Fcontainerd:\u002Fusr\u002Fbin\u002Fcontainerd:ro \\\n  -v \u002Fusr\u002Fbin\u002Frunc:\u002Fusr\u002Fbin\u002Frunc:ro \\\n  -v \u002Fusr\u002Flib\u002Fsystemd:\u002Fusr\u002Flib\u002Fsystemd:ro \\\n  -v \u002Fvar\u002Flib:\u002Fvar\u002Flib:ro \\\n  -v \u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock:ro \\\n  docker\u002Fdocker-bench-security\n\n# Lint Dockerfile\nhadolint Dockerfile\n\n# Lint built image\ndockle myapp:latest\n\n# Verify no containers running as root\ndocker ps -q | xargs docker inspect --format '{{.Id}}: User={{.Config.User}}'\n```\n\n## Key Security Controls\n\n| Control | Implementation | CIS Section |\n|---------|---------------|-------------|\n| Non-root user | USER instruction in Dockerfile | 4.1 |\n| Read-only rootfs | --read-only flag | 5.12 |\n| Drop capabilities | --cap-drop ALL | 5.3 |\n| Resource limits | --memory, --cpus, --pids-limit | 5.10 |\n| No new privileges | --security-opt no-new-privileges | 5.25 |\n| Content trust | DOCKER_CONTENT_TRUST=1 | 4.5 |\n| TLS for daemon | daemon.json TLS config | 2.6 |\n| Audit logging | auditd rules | 1.1 |\n\n## References\n\n- [CIS Docker Benchmark](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fdocker)\n- [Docker Security Best Practices](https:\u002F\u002Fdocs.docker.com\u002Fengine\u002Fsecurity\u002F)\n- [Docker Bench Security Tool](https:\u002F\u002Fgithub.com\u002Fdocker\u002Fdocker-bench-security)\n- [Hadolint - Dockerfile Linter](https:\u002F\u002Fgithub.com\u002Fhadolint\u002Fhadolint)\n",{"name":5,"tags":25,"author":31,"domain":32,"source":33,"license":15,"version":34,"nist_csf":35,"subdomain":40,"description":7,"mitre_attack":41,"source_commit":47},[26,27,28,29,30],"containers","docker","security","hardening","CIS-benchmark","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[36,37,38,39],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01","container-security",[42,43,44,45,46],"T1610","T1611","T1609","T1525","T1068","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fhardening-docker-containers-for-production",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill hardening-docker-containers-for-production",{"tool":64,"command":65},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill hardening-docker-containers-for-production",{"tool":67,"command":68},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill hardening-docker-containers-for-production","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhardening-docker-containers-for-production\u002FSKILL.md",true,[72,78,82,88,92,96,102],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"assets\u002Ftemplate.md","ASSET","资产文件",2822,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhardening-docker-containers-for-production\u002Fassets\u002Ftemplate.md",{"path":79,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fapi-reference.md","REFERENCE","参考文档",1818,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhardening-docker-containers-for-production\u002Freferences\u002Fapi-reference.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fstandards.md",3676,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhardening-docker-containers-for-production\u002Freferences\u002Fstandards.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fworkflows.md",4344,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhardening-docker-containers-for-production\u002Freferences\u002Fworkflows.md",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fagent.py","SCRIPT","脚本",5041,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhardening-docker-containers-for-production\u002Fscripts\u002Fagent.py",{"path":103,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fprocess.py",15194,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fhardening-docker-containers-for-production\u002Fscripts\u002Fprocess.py",[107,115,122,130,138,146],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]